Sugar on a Stick/Installation: Difference between revisions

mNo edit summary
No edit summary
Line 34: Line 34:
===with GNU/Linux===
===with GNU/Linux===
<span class="linkgroup">[[File:Gnulinux.png|link=Sugar on a Stick/Linux]]</span>
<span class="linkgroup">[[File:Gnulinux.png|link=Sugar on a Stick/Linux]]</span>
<ol start="0">
{{:Sugar on a Stick/Linux/Installation}}
<li>Use this script file [http://git.fedorahosted.org/git?p=hosted/livecd;a=blob_plain;f=tools/livecd-iso-to-disk.sh;hb=HEAD livecd-iso-to-disk] to create a bootable image.<br>(Run {{Code|chmod +x tools_livecd-iso-to-disk.sh}} after you download the script to make it executable.)</li>
<li>Execute, as the root user, in <u>one</u> command with arguments, the following:<br>
{{Code|./tools_livecd-iso-to-disk.sh --reset-mbr --overlay-size-mb '''300''' --home-size-mb '''175''' --delete-home --unencrypted-home '''/path/to/source.iso''' /dev/sd'''?'''1}}<br>
: where '{{Code|'''?'''}}' in the final parameter represents the target bootable device node, such as {{Code|sdb1}} or {{Code|sdc1}}, etc., and<br>
: make sure to replace {{Code|/path/to/source.iso}} with the path to the downloaded sugar-on-a-stick iso file.<br>
: The operating system will occupy ~520 MB, and the overlay and home size arguments, 300 and 175, were selected to fit in a 1 GB device, but may be adjusted according to your device capacity.
''Be certain of your USB/SD '''s'''csi '''d'''rive node name (such as sda, sdb, etc.) and partition (such as 1, 2, etc.).<br>
: Use the {{Code|df -Th}} command to confirm your devices before executing the script.
</li></ol>
{{Show|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;You should see something like the following:
|<pre>
[root@MyComputer ~]# df -Th
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/sda1    ext4    18G  6.6G  11G  38% /
tmpfs        tmpfs    1.6G  740K  1.6G  1% /dev/shm
/dev/sdc1    vfat    15G  697M  15G  5% /media/SANDY
/dev/sdb1    vfat    15G  2.0G  13G  14% /media/TOSHIBA
</pre>
:: where the mount point and filesystem sizes should help you identify what you want.
 
<pre>
$ sudo ./livecd-iso-to-disk.sh --reset-mbr --overlay-size-mb 300 --home-size-mb 200 --delete-home --unencrypted-home /mnt/VMs/Fedora-13-x86_64-Live-SoaS.iso /dev/sdb1
Verifying image...
/mnt/VMs/Fedora-13-x86_64-Live-SoaS.iso:  7bb43cb6237802347e06d636b5974796
Fragment sums: 5cb46db2dd7545c7154d99616eaa942ca515fb37188c34cf82564a498b68
Fragment count: 20
Press [Esc] to abort check.
Checking: 100.0%
 
The media check is complete, the result is: PASS.
 
It is OK to use this media.
Copying live image to USB stick
Updating boot config file
Initializing persistent overlay file
300+0 records in
300+0 records out
314572800 bytes (315 MB) copied, 35.3334 s, 8.9 MB/s
Initializing persistent /home
200+0 records in
200+0 records out
209715200 bytes (210 MB) copied, 24.2014 s, 8.7 MB/s
Formatting unencrypted /home
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
51200 inodes, 204800 blocks
10240 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
25 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729
 
Writing inode tables: done                           
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
 
This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
tune2fs 1.41.12 (17-May-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
Installing boot loader
USB stick set up as live image!
</pre>}}
:: (See [[Sugar on a Stick/Linux]] for more details.)
:: (See [[Sugar on a Stick/Linux]] for more details.)
:'''Note''': The graphical Liveusb-creator is an alternative installation method (see the first Windows [[#with Microsoft Windows |method]]), but it does not create the separate home.img filesystem, and so, the write-once persistent storage on the disk is more quickly consumed (see [[LiveOS image]]). If the USB device does not boot after running Liveusb-creator, the command {{Code|liveusb-creator --reset-mbr}} may help.
:'''Note''': The graphical Liveusb-creator is an alternative installation method (see the first Windows [[#with Microsoft Windows |method]]), but it does not create the separate home.img filesystem, and so, the write-once persistent storage on the disk is more quickly consumed (see [[LiveOS image]]). If the USB device does not boot after running Liveusb-creator, the command {{Code|liveusb-creator --reset-mbr}} may help.