memory and filesystem

[emninger]

When i checked the free diskspace by 'df' normally i got some lines with in the end sda1 (corrisponding to the first 9 lines). Now i
'm getting this:

Code: [Select]

Filesystem                Size      Used Available Use% Mounted on
rootfs                  899.6M    131.5M    768.1M  15% /
tmpfs                   499.8M         0    499.8M   0% /dev/shm
/dev/sda1                14.5G    682.8M     13.9G   5% /mnt/sda1
/dev/sda1                14.5G    682.8M     13.9G   5% /home
/dev/sda1                14.5G    682.8M     13.9G   5% /opt
/dev/loop0               20.0K     20.0K         0 100% /tmp/tcloop/libXdmcp
/dev/loop1               12.0K     12.0K         0 100% /tmp/tcloop/libXau
/dev/loop2              208.0K    208.0K         0 100% /tmp/tcloop/libxcb
/dev/loop3              968.0K    968.0K         0 100% /tmp/tcloop/libX11
/dev/loop4               16.0K     16.0K         0 100% /tmp/tcloop/libXrender
/dev/loop5               28.0K     28.0K         0 100% /tmp/tcloop/libXext
/dev/loop6               16.0K     16.0K         0 100% /tmp/tcloop/libXrandr
/dev/loop7               44.0K     44.0K         0 100% /tmp/tcloop/libXpm
/dev/loop8               36.0K     36.0K         0 100% /tmp/tcloop/libSM
/dev/loop9               40.0K     40.0K         0 100% /tmp/tcloop/libICE
/dev/loop10             156.0K    156.0K         0 100% /tmp/tcloop/libXt
/dev/loop11              52.0K     52.0K         0 100% /tmp/tcloop/libXmu
/dev/loop12              28.0K     28.0K         0 100% /tmp/tcloop/libXi
/dev/loop13              28.0K     28.0K         0 100% /tmp/tcloop/libfontenc
/dev/loop14             268.0K    268.0K         0 100% /tmp/tcloop/freetype
/dev/loop15             116.0K    116.0K         0 100% /tmp/tcloop/libXfont
/dev/loop16               1.2M      1.2M         0 100% /tmp/tcloop/Xlibs
/dev/loop17              92.0K     92.0K         0 100% /tmp/tcloop/libpng
/dev/loop18             116.0K    116.0K         0 100% /tmp/tcloop/libjpeg-turb  o
/dev/loop19             176.0K    176.0K         0 100% /tmp/tcloop/imlib2
/dev/loop20              56.0K     56.0K         0 100% /tmp/tcloop/imlib2-bin
.....
/dev/loop267             64.0K     64.0K         0 100% /tmp/tcloop/gettext-dev

Is that correct. In any case, since all this /dev/loop lines show up, i see that ram is much less used ... (??)

I'm aware, i've to learn a lot

[Misalf]

I don't see a problem.
What exactly would these "some lines" look like?

Did  df  not display any lines containing  /dev/loop  before? In that case you may have been using the copy2fs feature, which means extensions won't stay loop mounted but their content is copied to RAM, which obviously consumes more RAM. But I guess you would know if you used this feature.

[emninger]

I don't see a problem.
What exactly would these "some lines" look like?

Did  df  not display any lines containing  /dev/loop  before? In that case you may have been using the copy2fs feature, which means extensions won't stay loop mounted but their content is copied to RAM, which obviously consumes more RAM. But I guess you would know if you used this feature.

Thanks for the compliment, but you're overestimating my familiarity with tcl.

Makes sense to me what you're saying, indeed, before the loop lines where not displayed. But i'm unaware either to have activated or to have disactivated the copy2fs feature.

What are the advantages/disadvantages of copy2fs? Or could you gently point me to a link with some explanations?

[Misalf]

It's straight forward.
If the file  /etc/sysconfig/tcedir/copy2fs.flg  does exist, every extension that gets loaded will first be mounted, then its contents get copied to the file system in RAM, and finally the extension gets unmounted.
This makes it possible to remove the boot media and decreases access time to program files resulting in potentially increased overall system performance if plenty of RAM is available. Also results in slower boot times though.

[emninger]

It's straight forward.
If the file  /etc/sysconfig/tcedir/copy2fs.flg  does exist, every extension that gets loaded will first be mounted, then its contents get copied to the file system in RAM, and finally the extension gets unmounted.
This makes it possible to remove the boot media and decreases access time to program files resulting in potentially increased overall system performance if plenty of RAM is available. Also results in slower boot times though.

Remove the boot media is not really my case (i deal with a netbook ). 1 gig of ram, nowadays si not anymore a lot, but for Tiny Core still huge, i presume. What would be your advice: use it or not use it?

I'm still in the basic setup and not in the fine tuning. But i hope, i'll get hibernate and suspend working, so booting time is not that much of an issue. Moreover, this netbook has a small but fast sata flashdisk ...

[Misalf]

Then don't use it.
I use it with my USB stick install of Tiny Core but for my netbook install I currently don't, because I'm preferring faster boot times as I reboot quite often when messing with system files.