LiveOS image: Difference between revisions

Line 16:

==Storage==

When a Live CD or Live DVD (a LiveOS image on read-only disc media) is booted, temporary storage is prepared for the system in RAM on each boot by ~~the~~ [http://git.kernel.org/?p=boot/dracut/dracut.git;a=blob;f=modules.d/90dmsquash-live/dmsquash-live-root;hb=HEAD /sbin/dmsquash-live-root] in initrd0, the initial ram disk filesystem. An in-memory copy-on-write system overlay is used (see [[#File Systems|File Systems]] below).

When a Live CD or Live DVD (a LiveOS image on read-only disc media) is booted, temporary storage is prepared for the system in RAM on each boot by [http://git.kernel.org/?p=boot/dracut/dracut.git;a=blob;f=modules.d/90dmsquash-live/dmsquash-live-root;hb=HEAD /sbin/dmsquash-live-root] in initrd0, the initial ram disk filesystem. An in-memory, copy-on-write system overlay is used (see [[#File Systems|File Systems]] below).

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

Line 29:

===Home filesystem===

~~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 this particular~~ file space is not normally reusable.

One may find many advantages to installing Sugar on a Stick, or any LiveOS, 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, which can be consumed very quickly; and overlay file space is not normally reusable.

===Device filesystem===

@@ Line 16: / Line 16: @@
 ==Storage==
-When a Live CD or Live DVD (a LiveOS image on read-only disc media) is booted, temporary storage is prepared for the system in RAM on each boot by the [http://git.kernel.org/?p=boot/dracut/dracut.git;a=blob;f=modules.d/90dmsquash-live/dmsquash-live-root;hb=HEAD /sbin/dmsquash-live-root] in initrd0, the initial ram disk filesystem. An in-memory copy-on-write system overlay is used (see [[#File Systems|File Systems]] below).
+When a Live CD or Live DVD (a LiveOS image on read-only disc media) is booted, temporary storage is prepared for the system in RAM on each boot by [http://git.kernel.org/?p=boot/dracut/dracut.git;a=blob;f=modules.d/90dmsquash-live/dmsquash-live-root;hb=HEAD /sbin/dmsquash-live-root] in initrd0, the initial ram disk filesystem. An in-memory, copy-on-write system overlay is used (see [[#File Systems|File Systems]] below).
 The Fedora LiveOS system allows for persistent storage in 3 locations:
@@ Line 29: / Line 29: @@
 ===Home filesystem===
-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&mdash;all without consuming the write-once, overlay that can be consumed very quickly, because this particular file space is not normally reusable.
+One may find many advantages to installing Sugar on a Stick, or any LiveOS, 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&mdash;all without consuming the write-once, overlay, which can be consumed very quickly; and overlay file space is not normally reusable.
 ===Device filesystem===