Help - Search - Members - Calendar
Full Version: Oz 3.5.3 Off Filesystem Sizes
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > Angstrom & OpenZaurus
solarisjon
I downloaded the zImage fike from

http://www.openzaurus.org/official/unstabl.../sl5000,sl5500/

I tried a few of them but if my understanding is correct the

40-24 image for example should give me a root (40Mb) and a ram filesystem of
(24Mb).

Yet once I flash and boot and check the System Info->Storage screen i have

/dev/root = 14464Kb
Internal Memory = 31204kb

The problem is with such a small ammount of free space in root it fills up really
quickly.

Now its been a long time since I had my Zaurus 5500 powered up as it broke a year back
or so but after some surgery on the on/off contacts I managed to get it backinto life however
in that time OpenZaurus seems to have progressed a long way so this may just be my
relative newness back into Zaurus land..
lardman
The size of the root fs will always be c.16MB as this is the size of the flash memory.

The two numbers on the zImage are how the 64MB of RAM are split into a RAM-disk and 'normal' RAM used to run things.

QUOTE
40-24 image for example should give me a root (40Mb) and a ram filesystem of
(24Mb).


Will give you 40MB to run things in, and a 24MB RAM-disk mounted on /media/ram iirc.

QUOTE
The problem is with such a small ammount of free space in root it fills up really
quickly.


The limitation of the collie machines - I'd get yourself an SD card formatted as ext2 and install things there (or use the RAM-disk which you've created due to your choice of zImage).


Si
solarisjon
Thanks for that my misunderstanding. However if I run for example on a compleltly
clean flash of the 40-24 image for exaple

ipkg update
ipkg upgrade -d ram

I get to the 3rd or 4th download and then start getting no space on device messages

df after this fails is ...

/dev/mtdblock4 14.1M 14.0M 144.0k 99% /
/dev/mtdblock6 23.2M 18.0k 22.0M 0% /media/ram
tmpfs 18.7M 52.0k 18.6M 0% /var
/dev/mmcda1 14.0M 84.0k 13.9M 1% /media/card
/dev/hda1 121.9M 63.5M 58.4M 52% /media/cf

Guesing its writing into / despite the -d option ?

From ipkg.conf the mapping is

dest ram /media/ram/packages/

If I look in that dir it is complelty empty apart from the dir structure

/media/ram/packages/usr/lib/ipkg/info

Jon


QUOTE(lardman @ Aug 25 2005, 11:10 AM)
The size of the root fs will always be c.16MB as this is the size of the flash memory.

The two numbers on the zImage are how the 64MB of RAM are split into a RAM-disk and 'normal' RAM used to run things.

QUOTE
40-24 image for example should give me a root (40Mb) and a ram filesystem of
(24Mb).


Will give you 40MB to run things in, and a 24MB RAM-disk mounted on /media/ram iirc.

QUOTE
The problem is with such a small ammount of free space in root it fills up really
quickly.


The limitation of the collie machines - I'd get yourself an SD card formatted as ext2 and install things there (or use the RAM-disk which you've created due to your choice of zImage).


Si
*

lardman
QUOTE
Guesing its writing into / despite the -d option ?


Yes - the upgrade option will upgrade (all of) the packages where it finds them.

I'd only upgrade individual packages on the collie and then only if you need to as, as you've noticed, you'll run out of space.

If you were trying to upgrade the modules so you could flash the new kernel (without the suspend issues, etc.), then add the upgrades/collie part of the upgrades feed as a seperate feed (edit /etc/ipkg.conf) and comment out the other feeds (so that the upgrades/collie one is the only active feed); then 'ipkg update && ipkg upgrade'; then flash the new kernel and put ipkg.conf back to how it was.


Si
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2015 Invision Power Services, Inc.