Changes

The Fedora LiveOS system allows for persistent storage in 3 ways:

The Fedora LiveOS system allows for persistent storage in 3 ways:

# A general persistent overlay - a compressed, write-once, fixed-size file space that will save updates and changes to the LiveOS image (Activities, operating system changes, anything written in the LiveOS file space).

# An all-purpose, persistent overlay - a compressed, write-once, fixed-size file space that will save updates and changes to the LiveOS image (Activities, operating system changes, anything written in the LiveOS file space).

# Persistent Home folder - a re-sizable (with difficulty), uncompressed, optionally-encryptable, file space for anything that goes in the Learner's /home/ folder (all the Sugar Activities, logs, and good stuff).  A persistent home fold is an option that must be selected at the time of installation of the LiveOS image. This option is only available through the installation scripts, 'livecd-iso-to-disk' or 'modified_livecd-iso-to-disk'. The Windows and Fedora 'Live USB Creator' installers do not provide this option as of April 2010.

# Persistent home folder - a re-writable, re-sizable (with difficulty), uncompressed, optionally-encryptable, file space for anything that goes in the Learner's /home/ folder (all the Sugar Activities, logs, and good stuff).  A persistent home folder is an option that must be selected at the time of installation of the LiveOS image. This option is only available through the installation scripts, 'livecd-iso-to-disk' or 'modified_livecd-iso-to-disk'. The Windows and Fedora 'Live USB Creator' installers do not provide this option as of June 2010.

# Host device file space - this is the file system that is outside of the LiveOS file tree, but accessible through the /mnt/live folder mount point.  There, one finds the boot configuration files and anything else one had on the device before loading the SoaS image.  One may be save files here without consuming the other limited file spaces,  (limited by device capacity).

# Host device file space - this is the file system that is outside of the LiveOS file tree, but is accessible through the /mnt/live folder mount point.  There, one finds the boot configuration files and anything else one had on the device before loading the SoaS image.  One may save files here without consuming the other, limited file spaces. (This file space is limited by the device capacity).

The standard persistent overlay is needed for operating system changes and updates.

The all-purpose, persistent overlay is needed for operating system changes and updates.

But, one may find many advantages to installing Sugar on a Stick with a persistent home folder (using the --home-size-mb NN --delete-home options), which will hold all the Activities one wants to try and, perhaps later, throw away—all without consuming the write-once overlay that would fill up very quickly.

But, one may find many advantages to installing Sugar on a Stick with a persistent, home folder (using the --home-size-mb NN --delete-home options), which will hold all the Activities one wants to try and, perhaps later, throw away—all without consuming the write-once, overlay that can be consumed very quickly, because file space is un-reusable.

Additionally, keeping some storage space on the device disc outside of the LiveOS system will let you copy, carry, and delete large resource files, such as image.iso files, or anything you might want to use or share.  (We should adjust the Journal code to show this root mount to facilitate file sharing.)

Additionally, keeping some storage space on the device disc outside of the LiveOS system will let you copy, carry, and delete large resource files, such as image.iso files, or anything you might want to use or share.  (We should adjust the Journal code to show this root mount to facilitate file sharing.)

Sugar on a Stick may be installed on a 1-GB USB device using the following options with ''livecd-iso-to-disk'' or ''modified_livecd-iso-to-disk'' (on a single Terminal Activity or console command line, even though the wiki may wrap the following text according to your browser window size):

Sugar on a Stick may be installed on a 1-GB USB device using the following options with '''livecd-iso-to-disk''' or '''modified_livecd-iso-to-disk''' (on a single Terminal Activity or console command line, even though the wiki may wrap the following text in accord with your browser window size):

:{{Code|./livecd-iso-to-disk --overlay-size-mb 200 --home-size-mb 200 --delete-home --unencrypted-home /path/to/source/iso/or/device /dev/sd'''?'''1}}

:{{Code|./livecd-iso-to-disk --overlay-size-mb 200 --home-size-mb 200 --delete-home --unencrypted-home /path/to/source/iso/or/device /dev/sd'''?'''1}}

The above configuration would allow space for the home folder, the operating system, and a little on the device root.

The above configuration would allow space for the home folder, the operating system, and a little on the device root.

But with a larger storage device, one can allocate the resources to suit the anticipated use as described above.

But with a larger capacity device, one can allocate the resources to suit the anticipated use, as described above.

==File Systems==

==File Systems==