^thehatsrule^

Group: Members
Posts: 3275
Joined: July 2006 |
 |
Posted: Dec. 06 2006,16:31 |
 |
Apparently the unionfs implementation "supermounts" on the /KNOPPIX cloop, which was previously uneditable. Not that I understand the implementation itself (yet) - but I can see how this can be handy if you are making remaster a lot without scripts.
Unfortunately doing it this way doesn't seem to work in all cases. My first test was with the XFree86.unc. It looks like a uci in the fact its also mounted in /opt, with a user.tar.gz - but I think unionfs kicks in here and the XF86 usr data is accessible through /KNOPPIX. However, user.tar.gz is mydsl-loaded 'normally' and only goes into /ramdisk , but unionfs doesn't touch it (therefore not in /KNOPPIX).
In addition, trying to remove a file from this... such as /usr/X11R6/bin/XFree86 (which would be on /ramdisk) results in a segfault, and consequent things, such as ls /usr/X11R6/bin will results in the program hanging. I assume you can only modified those loaded by unionfs to be modified through that interface.
This is how I understand it so far... feel free to explain, etc.
|