Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
en:guides:sdcard [2010/04/15 05:30] – created monzen:guides:sdcard [2010/08/22 22:14] (current) – linea
Line 1: Line 1:
-====Installing SliTaz to a MMC/SD-card====+====== Installing SliTaz to a MMC/SD-card ======
 SliTaz can be installed to a MMC/SD flash-memory card (the kind used in digital cameras) in either of two ways: in a LiveUSB version as used on a "memory-stick" (also called "thumb-drive", "flash-drive", or a variety of other names), or as a regular install as used on a hard-drive. There are advantages and disadvantages to both methods. SliTaz can be installed to a MMC/SD flash-memory card (the kind used in digital cameras) in either of two ways: in a LiveUSB version as used on a "memory-stick" (also called "thumb-drive", "flash-drive", or a variety of other names), or as a regular install as used on a hard-drive. There are advantages and disadvantages to both methods.
  
-====LiveUSB-type installation==== +===== LiveUSB-type installation ===== 
-A memory-stick uses NAND flash memory, which eventually wears out after about 100,000 read/write cycles. SliTaz tries to minimize this wear, and thus prolong the life of the memory-stick, by storing the entire main root-file-system ("rootfs") as a compressed image in one file (rootfs.gz), then uncompressing it into the machine's memory (RAM) when booting. Only the /home directory is normally written to on the memory-stick, unless the user issues this command:+A memory-stick uses NAND flash memory which eventually wears out after about 100,000 read/write cycles. SliTaz tries to minimize this wear, and thus prolong the life of the memory-stick, by storing the entire main root-file-system ("rootfs") as a compressed image in one file (rootfs.gz), then uncompressing it into the machine's memory (RAM) when booting. Only the /home directory is normally written onto the memory-stick, unless the user issues this command:
 <code> <code>
 # tazusb writefs [compression] # tazusb writefs [compression]
 </code> </code>
-where "[compression]" can be "lzma", "gzip", or "none". This command re-writes the rootfs.gz file onto the memory-stick, so that changes made to the system can be saved and used again at the next boot-up. The big advantage to using this method is obviously that it prolongs the life of the USB device. The big disadvantage is that booting takes a long time because of the use of compression, and the more packages you install to your rootfs system the longer it takes to boot. The rootfs can also be saved without compression (i.e., # tazusb writefs none), which will allow it to boot much faster. This was not such a good option when SliTaz 1.0 was release in 2008, because memory-sticks had much less storage space then, but with 4 GB memory-sticks common now, it's not as much of a problem. This same method can be used to install SliTaz to a MMC/SD card.+Where "[compression]" can be "lzma", "gzip", or "none". This command re-writes the rootfs.gz file onto the memory-stick, so that changes made to the system can be saved and used again at the next boot-up. The big advantage to using this method is obviously that it prolongs the life of the USB device. The big disadvantage is that booting takes a long time because of the use of compression, and the more packages you install to your rootfs system the longer it takes to boot. The rootfs can also be saved without compression (i.e., # tazusb writefs none), which will allow it to boot much faster. This was not such a good option when SliTaz 1.0 was released in 2008, because memory-sticks had much less storage space then, but with 4 GB memory-sticks common now, it's not as much of a problem. This same method can be used to install SliTaz to a MMC/SD card.
  
-====Regular "hard-drive"-type installation====+===== Regular "hard-drive"-type installation =====
 The other option is to treat the MMC/SD card as if it were a real hard-drive, and simply use: The other option is to treat the MMC/SD card as if it were a real hard-drive, and simply use:
 <code> <code>
Line 20: Line 20:
 to do the actual installation. Be sure to also allow the installer to install GRUB onto the card, so that you can boot from it the normal way, same as you would from a regular hard-drive. to do the actual installation. Be sure to also allow the installer to install GRUB onto the card, so that you can boot from it the normal way, same as you would from a regular hard-drive.
  
-====Example as used on my own Asus Eee-PC==== +===== Example as used on my own Asus Eee-PC ===== 
-The SliTaz installation which i put onto a MMC/SD-card (16 GB) was for my Asus Eee-PC 701, leaving the Eee's original Xandrox Linux installation intact on its SSD (solid-state drive), and keeping the MMC/SD-card with SliTaz always in the card-reader slot. The Eee's BIOS needed to be changed to allow the SD-card to be the first boot device, so that the machine would boot into GRUB before anything else. The /boot/grub/menu.lst is setup to allow me to boot from either Xandros or SliTaz on the GRUB menu: +The SliTaz installation which I put onto a MMC/SD-card (16 GB) was for my Asus Eee-PC 701, leaving the Eee's original Xandrox Linux installation intact on its SSD (solid-state drive), and keeping the MMC/SD-card with SliTaz always in the card-reader slot. The Eee's BIOS needed to be changed to allow the SD-card to be the first boot device, so that the machine would boot into GRUB before anything else. The /boot/grub/menu.lst is setup to allow me to boot from either Xandros or SliTaz on the GRUB menu: 
-<code menu.lst>+<file>
 # /boot/grub/menu.lst: GRUB boot loader configuration. # /boot/grub/menu.lst: GRUB boot loader configuration.
 # #
Line 35: Line 35:
 color yellow/brown light-green/black color yellow/brown light-green/black
  
-# to boot newest slitaz from : /dev/sdb5+# To boot newest slitaz from : /dev/sdb5
 # #
 title  SliTaz GNU/Linux (cooking - kernel 2.6.30.6) title  SliTaz GNU/Linux (cooking - kernel 2.6.30.6)
Line 44: Line 44:
 # GRUB boots into SliTaz with no problem using only the root (hd0,4) command # GRUB boots into SliTaz with no problem using only the root (hd0,4) command
  
-# to boot Asus eee pc Xandros+# To boot Asus eee pc Xandros
 # #
 title Xandros (kernel vmlinuz-2.6.21.4-eeepc) title Xandros (kernel vmlinuz-2.6.21.4-eeepc)
Line 50: Line 50:
   kernel /boot/vmlinuz-2.6.21.4-eeepc quiet rw vga=785 irqpoll i8042.noloop=1 root=/dev/sda1   kernel /boot/vmlinuz-2.6.21.4-eeepc quiet rw vga=785 irqpoll i8042.noloop=1 root=/dev/sda1
   initrd /boot/initramfs-eeepc.img   initrd /boot/initramfs-eeepc.img
-</code>+</file>
  
-The first 3 partitions on my MMC/SD-card were originally used as storage for various parts of the Eee's Xandros system, with the 4th partition formatted as an Extended Partition and further divided into two, with Partition 5 used for the SliTaz install and Partition 6 for Linux-Swap. But because this SliTaz installation has become my main one for the Eee, as i added more packages i finally decided to move parts of the SliTaz filesystem to other partitions and use this layout:+The first 3 partitions on my MMC/SD-card were originally used as storage for various parts of the Eee's Xandros system, with the 4th partition formatted as an Extended Partition and further divided into two, with Partition 5 used for the SliTaz install and Partition 6 for Linux-Swap. But because this SliTaz installation has become my main one for the Eee, as I added more packages I finally decided to move parts of the SliTaz filesystem to other partitions and use this layout:
 <code> <code>
 $ df -h $ df -h
Line 66: Line 66:
 The /home/shared directory is one which has documents shared by the Xandros system. The /home/shared directory is one which has documents shared by the Xandros system.
  
-The Eee-PC was already set-up to recognize and read the MMC/SD-card. But one day i accidentally moved the whole contents of /boot to another directory and thus was unable to boot SliTaz. When i inserted the card into a Toshiba Satellite A215-S5850 laptop (my biggest, most modern, and main laptop), i was surprised to find that the machine did not see the MMC/SD-card. It was necessary to add a kernel package:+The Eee-PC was already set-up to recognize and read the MMC/SD-card. But one day I accidentally moved the whole contents of /boot to another directory and thus was unable to boot SliTaz. When I inserted the card into a Toshiba Satellite A215-S5850 laptop (my biggest, most modern, and main laptop), I was surprised to find that the machine did not see the MMC/SD-card. It was necessary to add a kernel package:
 <code> <code>
 # tazpkg get-install linux-mmc # tazpkg get-install linux-mmc
Line 74: Line 74:
 # modprobe mmc_block # modprobe mmc_block
 </code> </code>
-After that, SliTaz was able to read the contents of the MMC/SD-card, and i was able to move the /boot files back to where they belonged and fix the system. If the output of+After that, SliTaz was able to read the contents of the MMC/SD-card, and I was able to move the /boot files back to where they belonged and fix the system. If the output of
 <code> <code>
 # lsmod # lsmod
Line 80: Line 80:
 does not show mmc_block, then that module must be loaded manually. To have SliTaz always load it at boot-up, simply add it to the LOAD_MODULES line of /etc/rcS.conf. does not show mmc_block, then that module must be loaded manually. To have SliTaz always load it at boot-up, simply add it to the LOAD_MODULES line of /etc/rcS.conf.
  
 +---- 
 +\\
 +^  Page Review Section  ^^ 
 +|Quality| Good  |
 +|Review| Minor Updates  |
 +|Priority| Medium |
 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
 +|How to Improve| Suggest briefly|
 +|::: |  |
 +
 +\\
 +----
 
en/guides/sdcard.1271309441.txt.gz · Last modified: (external edit)