Hello,
If I'm not mistaken, the Redhat kernels do provide ext3 support, but
only as a module. Since you want your root filesystem to be mounted
ext3, you'll need ext3 support compiled into the kernel (or perhaps
you can get around it with ramdisks or something, but I wouldn't know
how). If you have any other filesystems (for example, /boot or
/home), you can try converting them. That's what I did--/boot, /home,
and /usr/share (I think) were all successfully mounted as ext3, but /
wasn't.
My solution was to compile the kernel myself. I avoided doing that
for a very long time, but finally had to in order to get a USB scanner
to work. Turns out that it isn't hard at all.
On Mon, Jan 07, 2002 at 06:22:42PM +1100, Andrew Smith wrote:
> rpm -Uvh kernel-source-2.4.9-12.i386.rpm
> (fails due to gcc version - assume that is OK - don't need it?)
I don't think that's a problem until you need to compile something. :)
> during the "init" rpm upgrade I got the error:
> "error: cannot remove /var/lib/rpm - directory not empty"
> but that seems harmless enough :-)
I would probably cd to /var/lib/rpm and see what's there. If it isn't
anything important, I'd remove the dir. I've gotten plenty of those
types of errors when upgrading things. The directory layout has
changed some, and sometimes I stuck a file somewhere (or modified one)
that causes this. It's a good safety feature IMHO.
HTH,
Ben
--
Ben Logan: ben at wblogan dot net
OpenPGP Key KeyID: A1ADD1F0
Violence is the last refuge of the incompetent.
-- Salvor Hardin
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
