Hi Fred!Hi Guys!
Just discovered by accident.
Something`s going wrong regarding "Quick-Remaster" when choosing to merge (or not to merge) currently loaded Modules (.squashfs) into "Quick-Remaster"
Try to explain:
I prefer using programs as .squashfs Files created with AptToSfs and store them in the "base" casper/base Folder and load them at Startup also in Ram.(see below copy2ram in my kernel Line).
I prefer loading everything loaded/running in Ram (copy2ram)
In my case Smplayer/Smtube....i prefer modules over installing Programms from Synaptic-Packet Manager..
What`s my Point?
Set up Bionic Dog as described above (Smplayer/Smtube are are stored in "base" Folder).
After reboot those loaded modules (in base Folder) are working fine so far. Than (when booted with Modules loaded (in Ram)----
--- made a "Quick-Remaster" LZ4 Compression.
----Box "merge currently loaded modules....bla..bla.. into remaster...".....BOX NOT checked .(100%)....means NO MERGE chosen.
"Quick-Remaster" finished.
Reboot again.
Now what happens.
After "Quick-Remaster" ...Reboot again into session>>>>
Loaded modules are working everything is running fine.
Than I removed those squashfs modules (from base Folder) manually while being booted into Session ......reboot again....EXPECTING THOSE REMOVED Smplayer/Smtube Squashfs Modules no longer loaded and running.(after removing and rebooting)......
But they are still present and active/running......means----they are merged into the "Quick-Remaster"...despite i chose not to merge into the "Quick-Remaster".
How does this work out?
I am rather perplexed.
Maybe i did something wrong.
Here is my menu.lst :
title bionicdog64ohnenvidia-C- porteus-boot - save on EXIT changes=EXIT:/bionicdog64ohnenvidia-C/changes folder
find --set-root /bionicdog64ohnenvidia-C/casper/vmlinuz
kernel /bionicdog64ohnenvidia-C/casper/vmlinuz copy2ram from=/bionicdog64ohnenvidia-C noauto intel_pstate=enable changes=EXIT:/bionicdog64ohnenvidia-C/casper/ ramsize=100%
initrd /bionicdog64ohnenvidia-C/casper/initrd1.xz
Could it have something to do with the "copy2ram" in kernel Line?
This is in Bionic Dog....but did a Test in Fossa-Dog ...seems to be the same Situation.
Anybody else same Experience/Result ?.........any Idea??