Tiny Core Base > TCB Talk

Free partition space when running in RAM

(1/4) > >>

bmarkus:
Dear Core Team,

just one thought for TC 2.1 features.

There are applications not available in source as usual but come with their own installer, like Google Earth and few others. These are checking available free free space in certain directoriesl, like /opt, ~, etc. and find 0 available when TC is running in RAM. There are other cases also where frree / available 'partition' size mybe interesting and would be good to have available on a usual LINUX way.

As an example see Conky reporting 0 space:



Regards,

Lee:
I saw this with the gtm5 extension where the mupip utility would not create a database file in ~tc (in ram) because it detected zero free space.  I thought at the time it was a problem with mupip and worked around it by creating a database file on a physical disk filesystem, moving the file to ~tc and saving it (compressed) as part of the .tce (to be installed by the startup script if not already present).

An empty database compresses really well, but I could still shave a few KB off of the .tce if I could just create the database on the fly when needed.

roberts:
TC is running as an embedded system, i.e., we stay running in initramfs. Typically all 2.6 based systems will have a small initramfs which is used until switch to a mounted root fs. Therefore initramds is ignored by df command. There was much debate if df should display it as it would be confusing to typical non-embedded use. We can monitor busybox, which promotes initramfs use, to see if initramfs df detection will be implemented. Interesting that Rob Landley, a major busybox developer, did make a  change to df in toybox's df command to report on initramfs.

^thehatsrule^:
As a workaround, perhaps creating a wrapper for df could work (specificially targetting /) for those cases for now.

bmarkus:
Yes, this is what I wanted to propose also as a workaround.

Navigation

[0] Message Index

[#] Next page