Mounting a NTFS partition with PCManFM in KNOPPIX 7.4.x

[superman]

Many thanks, utu.

Having no luck with toggling the option of Volume Management.

Have been repeating my own question in my head over and over, and the things just don't add up; having the privilege to un-mount the NTFS partition but to mount it! But, I did come across something bizarre.

I can mount and un-mount the partition as usual if the /KNOPPIX folder contains
-- KNOPPIX or,
-- KNOPPIX + knoppix-data.img or,
-- KNOPPIX + KNOPPIX1 + knoppix-data.img

The combo of KNOPPIX + KNOPPIX1 alone is a No-No!

The KNOPPIX1 contains the usual files seen in /ramdisk when booting with "KNOPPIX 2 noimage" plus a dummy file created by root with "dd bs=1M count=10 conv=notrunc if=/dev/zero of=/home/knoppix/dummy_file" . To create the compressed file, I simply followed the guide found on debian-knoppix mailing list https://lists.debian.org/debian-knop.../msg00005.html . That's all....

[utu]

I can mount and un-mount the partition as usual if the /KNOPPIX folder contains
-- KNOPPIX or,
-- KNOPPIX + knoppix-data.img or,
-- KNOPPIX + KNOPPIX1 + knoppix-data.img
The combo of KNOPPIX + KNOPPIX1 alone is a No-No!
[snip]
The KNOPPIX1 contains the usual files seen in /ramdisk when booting with "KNOPPIX 2 noimage" plus a dummy file created by root with "dd bs=1M count=10 conv=notrunc if=/dev/zero of=/home/knoppix/dummy_file" . To create the compressed file, I simply followed the guide found on debian-knoppix mailing list https://lists.debian.org/debian-knop.../msg00005.html . That's all....

This form of 're-mastering' has its hazards.
Klaus K uses the technique, but is quite careful not to get into difficulty.

The order of inclusion for KNOPPIX, KNOPPIX1 and knoppix-data.img is crucial.
This order is spelled-out in the init within minirt.gz, and not yours to control.
The last element actually added may write over something in a previous element
that had been different or missing. Elements being KNOPPIX, KNOPPIX1 and knoppix-data.img.

You may need to look at the expanded contents of each element in a linux filesystem
to see what files might be over-written.

Such problems do do not occur with actual re-mastering, such as Werner P Schulz
provides. His technique takes care of any possibility of improper combinations.

---------------

Another way of looking at Klaus K's shortcut process is it works predictably ONLY
if there is no overlap in the definiton of any filename's content among the several
separate filesystems being combined. Similarly contents of any folder like /ext /lib, and
so on must not overlap.