Re-mastering Proof-of-Principle Effort

[Werner P. Schulz]

I feel more comfortable NOT modifying the HD on my laptop.
The underlying Win7 system works very well, and I don't feel confident enough to repair it if I break it.

What shall happen with NTFS from Windows7? Knoppix doesn't change or install anything; it creates a new directory "\knx" and writes some files and folders to it; that's all.

The 'lame duck' may have the potential of a self-contained
re-mastering capability.

It doesn't need external storage nor another OS to complete
the re-mastering. After the kn-recombine rsync phase,
dismount the 'duck and reboot IT with the option 'noimage'
and proceed with the kn-recombine write operation.

This doesn't work. On my page at position "Reassemble your flash disk" I wrote

The old files 'KNOPPIX' and 'knoppix-data.img' respectively 'knoppix-data.aes' (= persistent memory) will be removed.

You cannot exchange in a running Knoppix Live session the existing KNOPPIX with a new compressed filesystem Image (KNOPPIX).

Greetings Werner
http://www.wp-schulz.de/knoppix/recombine.html

[utu]

You cannot exchange in a running Knoppix Live session the existing KNOPPIX with a new compressed filesystem Image (KNOPPIX).
http://www.wp-schulz.de/knoppix/recombine.html

I have to keep proving this.
It seems SO un-necessary, since the COMPRESSED filesystem is not the ACTIVE system.
It seems the COMPRESSED system should be inert once the ACTIVE system is built.

[vkrishn]

Suggesting but not recommending:
1. How about re-mounting knoppix-data.img as readonly.
2. Then creating new Union with KNOPPIX and directly compressing the new Union.
I think this procedure can be scripted.

[kl522]

Suggesting but not recommending:
1. How about re-mounting knoppix-data.img as readonly.
2. Then creating new Union with KNOPPIX and directly compressing the new Union.
I think this procedure can be scripted.

The way Knoppix-data.img file system is mounted/structured, you can't remount it as read-only, you will get 'busy' error.

[Blacksimon]

might be interesting to divide the script into a further function:
1) rsync of Unions
2) generate the compressed filesystem
3) write to USB

Between the first and second feature I'd like to manually edit some files or folders in case I notice that you have a problem ....

Stupid silly example:
I customized the splash screeen Compiz (splash_backgroung.png & splash_logo.png) with my logo
I have placed in / KNOPPIX-DATA/usr/share/compiz and then I updated the path to two files in CompizConfig.
Well, by mistake the name of the file that I used had two capital letters than the original ....
result is that the new recombined Knoppix filesystem I found both the original file and my files ... and so I lost the customization ...
In order to fix the problem I should start all over again by launching the script again ... with a huge waste of time

[Werner P. Schulz]

Using your flash disk Installation with persistent memory you shall not edit '/KNOPPIX-DATA/'!

In your "silly example" write your modifications to '/usr/share/compiz' not to '/KNOPPIX-DATA/usr/share/compiz' and use this path in CompizConfig.

And before "recombine" Knoppix test your flash disk Installation as long as there are no errors.

Greetings Werner * http://www.wp-schulz.de/knoppix/summary.html
Own Rescue-CD (Knoppix V6.7.1 remaster).

[vkrishn]

The way Knoppix-data.img file system is mounted/structured, you can't remount it as read-only, you will get 'busy' error.

Remounting of Knoppix-data.img seems to work in 6.4.4
Only extra step was to create a new loop device.
I can post the method if useful.