Quote Originally Posted by paradocs
I agree that a combined directory would be good --
just don't call it Program Files
If I did this, I would call it either klik or .klik - what would you like more? klik would be visible and therefore easier to locate for newbies, .klik would be more elegant and wouldn't clutter your home directory.

Why didn't I do this initially? It is important for me to make the user know that each application package (which can be one app or a set of related apps) is "encapsulated" in its own directory. Unlike kano's "dist" which essentially throws it all together and therefore makes it hard to debug and uninstall.

Quote Originally Posted by paradocs
I would be interested in trying a boot script from a floppy
that would pick up one or two instalations upon each boot.
But would that give you site too much unnecessary traffic?
Why don't you .tar.gz your klik packages, burn them on cd and expand them in your knoppix.sh upon boot? Would be way faster...

Quote Originally Posted by paradocs
The overlay file system will also be revolutionary.
Indeed!

Quote Originally Posted by paradocs
how about calling you site:
klik KNOPPIX LIVE INSTALLER KINGDOM
or KNOPPIX LIVE INSTALLER KONSOLE
KLIK LIVE INSTALLER KDE
KLIK LIVE INSTALLER KNOPPIX
even though klik is not really limited to Knoppix nor KDE