install knoppix 6.2 in a cf-card

[adhikari]

Dear sir,, halo friends
I have a cf-card 2Gb size,, i want to insyall and run knoppix from this cf-card,(compct flash card), Can any body guide me in this regard..

[Capricorny]

First, I wouldn't really recommend something as small as 2GB. You may be asking for problems that way, I would have used at least a 4GB card. Second, have you tried simple, stupid install-to-flash? That would have been my first attempt. Letting Knoppix format the thing first.

[utu]

@adhikari

I'm presuming a cf-card is like what I call an SD Chip. If so, maybe the
following will be of use to you.

I'm using a 2Gb SD Chip myself. I chose to devote only 250m to additional space,
so my total persistent Knoppix 6.2.1 image (on the chip)is only about 1Gb.
This expands to 2Gb in ram. I've got 4Gb of ram, so it fits ok.

This is probably the probably the least workable amount (1Gb total) of SD Chip
memory devoted to Knoppix 6.2.1 that one can get by with. I have a crash now and
then when I get too bold, say with adding little things via Synaptic. In-between
crashes, this little rig works swell.

I expect to expand my additional space (on the chip) to 1-plus Gb next time I
crash and have to restore my SD Chip version of Knoppix 6.2.1. I expect my ram
will handle the expansion, but I'm not sure just how the math works between what's
on the SD chip and what goes and comes from ram. I suspect the stuff on the chip
is compressed about two-to-one, but I don't know this for a fact.

I've been thinking about a larger SD Chip, but because of the math uncertainty,
I'm just not sure how much additional will just fit in my 4Gb of ram. There's
really no other reason I need more ram, so I may not go that way.

Since you already have the 2Gb Chip, I suggest you play around with it for a while
before you get a larger chip. Also, be careful about going above 4Gb, since
there may be some fat32 limitations that make life difficult there.

[kl522]

I'm using a 2Gb SD Chip myself. I chose to devote only 250m to additional space,
so my total persistent Knoppix 6.2.1 image (on the chip)is only about 1Gb.
This expands to 2Gb in ram. I've got 4Gb of ram, so it fits ok.

I don't want to try to understand your calculation. Your calculation is definitely flawed. The compressed image is /mnt-system/KNOPPIX/KNOPPIX. The persistent store is /mnt-system/KNOPPIX/knoppix-data.img or knoppix-data.aes. KNOPPIX does not decompressed the compressed image everything at one go, ie a 1 GB compressed image is not expanded into 2 GB in ram. You have 4 GB of ram, which is a healthy amount of memory. You can use any sized flash, SD card of CF card, the last thing it gets filled up is your memory.

For a flash installation, if you provided a persistent store, KNOPPIX only uses persistent store. So the so-called additional space ( 250 MB in your case ) is not usable at all ( unless you purposedly write data to /mnt-system ). Considering you have a small flash, you are better off making your persistent image as big as possible, almost closed to filling up the entire flash.

[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.

[utu]

knoppix@Microknoppix:/mnt-system/KNOPPIX$ ls -l -h
total 933M
-rwxrwxrwx 1 root root 682M Jun 16 21:42 KNOPPIX
-rwxrwxrwx 1 root root 19K Jun 16 21:42 LICENSE.txt
-rwxrwxrwx 1 root root 4.1K Jun 16 21:42 README_Security.txt
-rwxrwxrwx 1 root root 1.2K Jun 16 21:42 SOURCES.txt
-rwxrwxrwx 1 root root 240K Jun 16 21:38 background.jpg
-rwxrwxrwx 1 root root 7.7K Jun 16 21:38 index_de.html
-rwxrwxrwx 1 root root 7.3K Jun 16 21:38 index_en.html
-rwxrwxrwx 1 root root 8.9K Jun 16 21:38 index_es.html
-rwxrwxrwx 1 root root 8.1K Jun 16 21:38 index_fr.html
-rwxrwxrwx 1 root root 8.0K Jun 16 21:38 index_it.html
-rwxrwxrwx 1 root root 8.4K Jun 16 21:42 knoppix-cheatcodes.txt
-rwxrwxrwx 1 root root 250M Jun 16 21:45 knoppix-data.img
-rwxrwxrwx 1 root root 32K Jun 16 21:42 knoppix-logo-medium.png
-rwxrwxrwx 1 root root 16K Jun 16 21:42 knoppix-logo-small.png
drwxrwxrwx 2 root root 4.0K Jun 16 21:42 modules
-rwxrwxrwx 1 root root 2.0K Jun 16 21:42 sha1sums

[kl522]

Haha your listing revealed a big misunderstand on your part. You are confused with the concept and terminology. You are overkilling yourself by keeping your knoppix-data.img small, 250M. Your flash is 2G, as we know, is considered small in this context, but you are making it worse by not able to fully utilizing your 2G because your knoppix-data.img is small, ie you are almost like having a 1 G flash, even though you have 2 G. Currently you have closed to 1G of empty space, but not useable by KNOPPIX.


Please expand your knoppix-data.img as big as possible as I mentioned earlier.

[Capricorny]

Haha your listing revealed a big misunderstand on your part. You are confused with the concept and terminology. You are overkilling yourself by keeping your knoppix-data.img small, 250M. Your flash is 2G, as we know, is considered small in this context, but you are making it worse by not able to fully utilizing your 2G because your knoppix-data.img is small, ie you are almost like having a 1 G flash, even though you have 2 G. Currently you have closed to 1G of empty space, but not useable by KNOPPIX.


Please expand your knoppix-data.img as big as possible as I mentioned earlier.

YES!
And I think it is just asking for trouble to count on the effective volume used in RAM will shrink enough before getting written to disk. Remember, persistent storage is NOT compressed, it is an ordinary loop-mount of a filesystem image,and one should really use the same ca 95% filling discipline as is often enforced in ordinary fs mounting. For that reason, 1GB is, I think, the bare minimum to use Knoppix for serious work, installing some extra programs etc.