install knoppix 6.2 in a cf-card

[utu]

knoppix@Microknoppix:/$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 1.9G 939M 943M 50% /mnt-system
tmpfs 1.0G 0 1.0G 0% /ramdisk
/dev/cloop 1.9G 1.9G 0 100% /KNOPPIX
/dev/loop0 243M 46M 197M 19% /KNOPPIX-DATA
unionfs 243M 46M 197M 19% /UNIONFS
unionfs 243M 46M 197M 19% /home
tmpfs 10M 64K 10M 1% /UNIONFS/var/run
tmpfs 10M 0 10M 0% /UNIONFS/var/lock
tmpfs 100M 60K 100M 1% /UNIONFS/var/log
tmpfs 1.0G 20K 1.0G 1% /tmp
udev 20M 412K 20M 3% /dev
tmpfs 1.0G 4.0K 1.0G 1% /dev/shm

[kl522]

Post #5 quoted as below :-

knoppix@Microknoppix:/$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 1.9G 939M 943M 50% /mnt-system

Your partition /dev/sdb1 is 50% utilized, ie you have 1G of free space.

tmpfs 1.0G 0 1.0G 0% /ramdisk

This is the bug that I mentioned about in some other thread - something which is not used when there is a persistent store. You can safely ignore this, it does no harm. But if it is a eye-sore to you, you can safely umount it.

/dev/cloop 1.9G 1.9G 0 100% /KNOPPIX

cloop is hungry for virtual memory. A 682M /mnt-system/KNOPPIX/KNOPPIX compressed image translate to closed to 2G of virtual memory. But this is not physical memory usage !!!

/dev/loop0 243M 46M 197M 19% /KNOPPIX-DATA
unionfs 243M 46M 197M 19% /UNIONFS
unionfs 243M 46M 197M 19% /home

This corresponds to the size of /mnt-system/KNOPPIX/knoppix-data.img, aka your persistent store. Check other threads about how to resize your persistent store without needing a re-install. Make use of the 1G free space you have, put it into your persistent store, you can at least grow another 900M to your original 250M persistent store, making it a total size of 1400 MB. Then you will have a much healthier system, you will not be complaining about KNOPPIX crash for quite a while.