What I found was that I had a lot of stuff under /lib
In particular, /lib/modules/2.4.2-2 etc
Looks to me as if the kernel updating part of up2date is leaving lots of
previous versions of things. Deleted all but the latest three, which
made a lot more space available, and was then able to run /sbin/lilo -v
-v sucessfully and then reboot and all is again well:
$ uname -a
Linux xxxxxx 2.4.18-24.7.x #1 Fri Jan 31 07:06:03 EST 2003 i686
unknown
$
By the way I also found (and deleted) a stack of kernel-2.4.8...i386.rpm
files in /etc - I can't imagine that I put them in so maybe that too is
down to up2date being 'funny'...
- steve
By the way, this whole business of multiple filesystems and having to
preset the sizes is A Real Pain for users used to any other OS - is
there any move to fix whatever obscure archaic reason there once was for
this requirement?
> -----Original Message-----
> From: David A. Mann [mailto:[EMAIL PROTECTED]]
> Sent: Monday, 10 February 2003 09:28
> To: [EMAIL PROTECTED]
> Subject: RE: Problems updating a kernel...
>
>
> Steve Brorens wrote:
>
> > Filesystem 1k-blocks Used Available Use% Mounted on
> > /dev/hda8 256667 256584 0 100% /
> > /dev/hda1 54416 9690 41917 19% /boot
> > /dev/hda6 1636544 7072 1546340 1% /home
> > /dev/hda5 1636544 821732 731680 53% /usr
> > /dev/hda7 256667 41814 201601 18% /var
> > none 30860 0 30860 0% /dev/shm
> >
> > I remember getting advice some time ago on the smart use of
> 'du' and
> > finding out that there's no easy way to strip all the GUI
> stuff out (I
> > installed it all initially, but I just telnet into this
> box, so it's
> > all unused - just taking up space) ...but I've forgotten
> all that so
> > maybe I'll just schedule to rebuild from scratch sometime
> with RH 7.3
> > (of which I have a full set of CD's), taking care to go down the
> > text-only path...
>
> I'm not enlightened in the Redhat Way but I seem to recall
> that most of X
> ends up under /usr so going text-only might not help you
> much. Now that
> I think about it there might be a whole load of X stuff under
> /opt (eg
> KDE, Gnome). This might be the major source of your trouble
> as there's
> not generally much outside of /lib, /home, /var and /usr.
> Try looking in
> /tmp and make sure there's nothing hogging space in there.
>
> If there's no alternative, here's what I do when running out
> of space on
> one partition: Create a directory on another partition which
> has lots of
> free space, and copy a big tree off the full partition into
> there. Then
> delete it off the full partition and symlink the copy back to its
> original location. For example I once placed my Squid cache under
> /home/squid in this way, with /usr/local/squid symlinked to
> /home/squid
> so I didn't need to change any scripts or config files. I recommend
> caution when doing this as moving/deleting files which are
> currently in
> use may be disastrous.
>
> BTW you need to be careful to preserve file ownerships and
> permissions.
> Check these before deleting the original files! I learned
> the hard way,
> when moving /home of all things... "cp -aR" may or may not be good
> enough. A quick test shows that it seems to work, but YMMV...
>
> Cheers,
>
> - Dave
>
http://www.digistar.com/~dmann/
=========================================================
http://www.commarc.co.nz
(This e-mail has been scanned by MailMarshal)
