Project: Merging Knoppix and Debian Live to get 64 bit Knoppix derivative?

[Capricorny]

Utu, believe just what you want to, I am using this the way it is advertised to work, Which does not work. Terrible is no exaggeration. I could also add "pathetic" for the ways the same types of errors keep on cropping up over and over again. And that the Debian standard kernel is at 3.2.0 - which in itself contributes to an own set of problems, not the least in networking.
Suffice to say that Klaus K has very good reasons for his policies with Knoppix. If you doubt, just give Debian-live a try, really using what are presented as the features.
Debian-live is designed for multiple overlays, but I doubt many use it. There are lots of bugs, and they are not benign.
The worst thing, is that you never know when and why things break. It has to do with all the promises that are not kept. For axample, you drop the overlay anywhere, the system just will find it. True? Not quite. I think I have experienced most of the possible combinations of errors during the last 24 hours. Overlay isn't mounted, it is mounted, but not used (that's a really terrible one), it is mounted and crashed, it is sandwich-mounted, it is not correctly updated, it is mounted, but not read correctly.

None of those problems were ever encoutered during 8 intensive years with Knoppix.

[utu]

the Debian standard kernel is at 3.2.0

I must admit, that's a bit of a shock.

[Capricorny]

I must admit, that's a bit of a shock.

Of course there have been a few upgrades to that version, but.. On the other hand, come on, it's still not three years old

user@live-debian:/media/sda8$ uname -a
Linux live-debian 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u1 x86_64 GNU/Linux
user@live-debian:/media/sda8$

The basic philosophy, their "paradigm", is worse, though. How can anyone hit on the idea to use partitions for persistent storage? Even on a small USB stick you would like to be able to place some files there too, outside of the image file. And the raw-copy-iso "installation" method makes it impossible to tweak parameters, while the creation of more user-friendly install versions is delegated to unetbootin et al. I'm not very fond of that bunch, they have been less than reliable to me.

There are a lot of comical aspects, too. Using gparted to partition the rest of the USB stick after raw copy of the ISO image, it is equipped with a label that Debian truthfully copies to the device name on automount of the stick.
Resulting in a mount point that the OS is often not able to handle correctly parsing commands, creating errors&problems.

So I have had to manually unmount, and remount using the more prosaic /media/sdb2. Problems gone.

[Capricorny]

The Debian-Live approach also provides some good opportunities. First and foremost, the very easy remastering makes it efficient to run with no persistent store quite often. For instance, upon remastering, I just start without the store, and the image I run is union-mounted with the persistence file and copied&compressed. Then I have to boot something else to copy the new squashfs image in place, but that's all that has to be done outside the system.

Boot the new image without persistence, create a new persistence file.
For further adaptations, the new persistence file can be mounted in an instance run under kvm, programs can be added and settings tweaked for an eventual new remastering.

Storing the series of squashfs-compressed images, one can always go back in this process if needed.