[iPAQ] Space requirements for intimate distribution.

Intimate is designed to start off filling a 340Mb udrive... But it's
probably better to have only 32Mb of swap on a 340Mb drive. (I'll update
docs to say that.)

There's plenty of stuff that can go to make space for whatever you want...

Just type 'dselect' and use the nice friendly menu driven debian packagement
system to remove any debian stuff you don't want.

dselect is good... dselect is your friend... dselect it the way of truth and
light...use dselect

The logic behind this was that working out what packages to install to get
gcc and everything else up and running properly for the first time was a
pain in the butt. I figured that people would rather have it there to begin
with and remove it when they wanted the space...dselect sorts out package
dependencies, so you see what you're breaking whenever you uninstall
something.

If you've got a working PPP/USBnet connection then dselect can also be used
to install stuff. Pick option '[0] Access' and overwrite the apt config with
the defaults it suggests.. (My dream is to have an ipaq debian archive to
use in addition to the debian one.).... Next... select [1] Update to get the
latest list of packages straight from debian. Then select [2] Select, and
use the cursor keys, + and - to add/remove packages. You can search with /
and repeat the search with \. Finally do [3] Install...

Before I upped the space requirements from 64Mb CF, I had a good long try at
using the stuff from jffs2 within the chrooted intimate environment, but
ended up with a messy load of symlinks and stuff. Maybe someone who
understands library paths etc should have a go... The jffs2 image ends up
mounted on /boot once intimate's booted up... We could probably save a lot
of duplication on libraries if the paths were set correctly...

Please.. someone who knows what they're doing... fix this :)

I've created a new bit on the Wiki for IntimateChanges for patches to the
base... Once there's a few of these, I'll (or if someone else can be
bothered) apply them to the base images and post a new set.

Lastly... If gzexe'd exceutables are causing a problem for anyone, you can
always do gzexe -d to decompress them again.

If only someone would write a mtd driver that uses an ide block device for
storage then we could use jffs2 on microdrives and significantly increase
the space available.

Think that about it.

Jim
Received on Fri Mar 30 15:55:24 2001