A USB KNoppix that can handle a 10GB+ Android sorce code download.

[Capricorny]

I can only answer for myself and that's simple: Storage used for data not affected by OS versions do not, IMHO, belong to the OS installation proper. They belong somewhere else, i.e. on other partitions. For my use, 4GB cloop + 4GB persistent store is enough for the OS-version related stuff (including user configuration data and casual stored files). And in that case, the files may as well reside on a FAT32 partition. Typically, things like Android or Tizen SDKs, or virtual machines will never be installed on the OS version related space, but instead on one or more large partitions with suitable file systems. I use ext3/4, YMMV. Working "The Knoppix Way", we never really need to do formatting upon installing new OS versions, other than for setting up USB boot media w/new persistent store.

Using Knoppix, why bother at all with the native file system type where the Knoppix system files reside, as long as it works well?

[utu]

Working "The Knoppix Way", we never really need to do formatting upon installing new OS versions, other than for setting up USB boot media w/new persistent store.

Using Knoppix, why bother at all with the native file system type where the Knoppix system files reside, as long as it works well?

Still, two loose ends (on why Fat32) , I think:

1. A re-format of Fat32 is required if a previous OS is found there when making
a new LiveUSB on a USB containing an earlier or different OS; and

2. Even Klaus K has to split his overlays to do a DVD-size LiveUSB install on
Fat32; he wouldn't need to do that on ext or reiser.

I buy the argument that if it works, why change it, but the clever overlay solution
does seem like overkill and getting away from Fat32 altogether would have. some appeal.
in simplifying things.