OESF Portables Forum

Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: starkruzr on November 14, 2005, 12:24:32 am

Title: Root Is Nearly Filled Right After Install?
Post by: starkruzr on November 14, 2005, 12:24:32 am

Cross-posting this here because I think I might have put it in the wrong place before.

Okay.  So this is what root on my 3.5.3 on SL-5500 looks like straight from install:

Code: [Select]

Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/mtdblock4           14464     13108      1356  91% /
After doing an ipkg update, it looks like this:

Code: [Select]

Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/mtdblock4           14464     13584       880  94% /
Is there supposed to be more room in here?  I don't remember older versions of OZ (3.2?) being quite so huge in root the first time around.  From experience it does not seem this is enough to even install things in /mnt/ram, because it makes enough configuration changes that affect /etc that this space fills up way too quickly.  Doing one ipkg upgrade after flashing to 3.5.3 maxes out my root about halfway through installing stuff.

Can someone help me clean root out so that I have room to install things?  Kismet and a little word processor would be nice.  

Thanks.

P.S. Here's what happens when I do ipkg upgrade:

Code: [Select]

root@collie:~# ipkg upgrade
Upgrading ipkg on root from 0.99.147-r1 to 0.99.148-r0...
Downloading [url=http://openzaurus.org/official/unstable/3.5.3/upgrades//ipkg_0.99.148-r0_arm.ipk]http://openzaurus.org/official/unstable/3.....148-r0_arm.ipk[/url]
Upgrading libipkg0 on root from 0.99.147-r1 to 0.99.148-r0...
Downloading [url=http://openzaurus.org/official/unstable/3.5.3/upgrades//libipkg0_0.99.148-r0_arm.ipk]http://openzaurus.org/official/unstable/3.....148-r0_arm.ipk[/url]
Not installing libipkg0 (0.99.148-r0) on root -- already installed.
Upgrading libqte2 on root from 2.3.10-r12 to 2.3.10-r14...
Downloading [url=http://openzaurus.org/official/unstable/3.5.3/upgrades//libqte2_2.3.10-r14_collie.ipk]http://openzaurus.org/official/unstable/3....-r14_collie.ipk[/url]
ipkg: write: No space left on device
Upgrading libts-0.0-0 on root from 0.0cvs20050403-r18 to 0.0cvs20050505-r18...
Downloading [url=http://openzaurus.org/official/unstable/3.5.3/upgrades//libts-0.0-0_0.0cvs20050505-r18_arm.ipk]http://openzaurus.org/official/unstable/3....505-r18_arm.ipk[/url]
ipkg: //usr/lib/ipkg/info/libts-0.0-0.control: No space left on device
ipkg: //usr/lib/ipkg/info/libts-0.0-0.postinst: No space left on device
ipkg: /usr/lib/ts/collie.so: No space left on device
ipkg: /usr/lib/ts/mk712.so: No space left on device
ipkg: /usr/lib/ts/pthres.so: No space left on device
ipkg: /usr/lib/ts/variance.so: No space left on device
ipkg: /usr/lib/ts/linear_h2200.so: No space left on device
ipkg: /usr/lib/ts/arctic2.so: No space left on device
ipkg: /usr/lib/ts/dejitter.so: No space left on device
ipkg: /usr/lib/ts/ucb1x00.so: No space left on device
ipkg: /usr/lib/ts/corgi.so: No space left on device
ipkg: /usr/lib/ts/linear.so: No space left on device
ipkg: /usr/lib/ts/h3600.so: No space left on device
ipkg: /usr/lib/ts/input.so: No space left on device
ipkg: Cannot create symlink from ./usr/lib/libts-0.0.so.0 to 'libts-0.0.so.0.1.1': No space left on device
ipkg: /usr/lib/libts-0.0.so.0.1.1: No space left on device
can't get //usr/lib/ipkg/info/libts-0.0-0.control open for read
Upgrading libz1 on root from 1.2.2-r5 to 1.2.3-r0...
Downloading [url=http://openzaurus.org/official/unstable/3.5.3/upgrades//libz1_1.2.3-r0_arm.ipk]http://openzaurus.org/official/unstable/3.....2.3-r0_arm.ipk[/url]
ipkg: //usr/lib/ipkg/info/libz1.control: No space left on device
ipkg: //usr/lib/ipkg/info/libz1.postinst: No space left on device
ipkg: Cannot create symlink from ./usr/lib/libz.so.1 to 'libz.so.1.2.3': No space left on device
ipkg: /usr/lib/libz.so.1.2.3: No space left on device
can't get //usr/lib/ipkg/info/libz1.control open for read
Configuring ipkg
/usr/bin/update-alternatives: 185: cannot create /usr/lib/ipkg/alternatives/ipkg.new: No space left on device
postinst script returned status 2
ERROR: ipkg.postinst returned 2
Configuring libipkg0
ldconfig: file /opt/QtPalmtop/lib/libqte.so.2 is truncated

ldconfig: file /opt/QtPalmtop/lib/libqte.so is truncated

ldconfig: file /opt/QtPalmtop/lib/libqte.so.2.3.10 is truncated

ldconfig: file /opt/QtPalmtop/lib/libqte.so.2.3 is truncated

ldconfig: Can't create temporary cache file /etc/ld.so.cache~: No space left on device
postinst script returned status 1
ERROR: libipkg0.postinst returned 1
Configuring libqte2
ldconfig: file /opt/QtPalmtop/lib/libqte.so.2 is truncated

ldconfig: file /opt/QtPalmtop/lib/libqte.so is truncated

ldconfig: file /opt/QtPalmtop/lib/libqte.so.2.3.10 is truncated

ldconfig: file /opt/QtPalmtop/lib/libqte.so.2.3 is truncated

ldconfig: Can't create temporary cache file /etc/ld.so.cache~: No space left on device
postinst script returned status 1
ERROR: libqte2.postinst returned 1
Configuring libts-0.0-0
Configuring libz1
ipkg_conf_write_status_files: Can't open status file: //usr/lib/ipkg/status for writing: No space left on device
ipkg_conf_write_status_files: Can't open status file: /media/cf/packages//usr/lib/ipkg/status for writing: No space left on device
ipkg_conf_write_status_files: Can't open status file: /media/card/packages//usr/lib/ipkg/status for writing: No space left on device
pkg_write_filelist pkg=ipkg returned 28
pkg_write_filelist pkg=libipkg0 returned 28
pkg_write_filelist pkg=libqte2 returned 28
pkg_write_filelist pkg=libts-0.0-0 returned 28
pkg_write_filelist pkg=libz1 returned 28


root@collie:~# df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/mtdblock4           14464     14352       112  99% /
/dev/mtdblock6           23797        18     22551   0% /media/ram
tmpfs                    19112        56     19056   0% /var
root@collie:~#

Title: Root Is Nearly Filled Right After Install?
Post by: lardman on November 14, 2005, 05:34:39 am

OZ is now rather large, more features, etc.

Don't perform an ipkg upgrade, this is bound to fill up the remaining space (see the recent thread on jffs2).

I'd get an SD/mmc card and install stuff to that, or remove some of the apps which came pre-installed, then try installing kismet, etc.


Si

Title: Root Is Nearly Filled Right After Install?
Post by: koen on November 14, 2005, 07:07:08 am

Or try the 3.5.4rc which stores the ipkg lists in RAM instead of flash.

Title: Root Is Nearly Filled Right After Install?
Post by: lardman on November 14, 2005, 07:15:28 am

Oops, I forgot about that one, thanks koen.

Si

Title: Root Is Nearly Filled Right After Install?
Post by: starkruzr on November 14, 2005, 01:11:44 pm

Quote

Or try the 3.5.4rc which stores the ipkg lists in RAM instead of flash.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=103602\"][{POST_SNAPBACK}][/a][/div]

So essentially the default installation of OZ on a 5500 is more or less unusable unless you

a) migrate root to SD
b) use 3.5.4 which, as I understand it, has no feeds?

Title: Root Is Nearly Filled Right After Install?
Post by: lardman on November 15, 2005, 05:35:29 am

Quote

So essentially the default installation of OZ on a 5500 is more or less unusable unless you

Quote

a) migrate root to SD

I wouldn't ever do what you suggest (personal preference). You can install files to the SD card and then link them into the main fs using ipkg-link.

Quote

use 3.5.4 which, as I understand it, has no feeds?

You should be able to use the majority of the 3.5.3 feeds with this Release Candidate.

In any case you can implement the same behaviour in 3.5.3 by adding a single line to /etc/ipkg.conf:

lists_dir ext /var/lib/ipkg

Note that you will need to flash an updated kernel as a suspend bug was fixed after the release of 3.5.3 - see the pinned threads.


Si