RE: ntfs

Nick Lindsell Mon, 17 Feb 2003 09:39:43 -0800

At 17:07 17/02/2003 +0000, you wrote:

From: Chris Mossner <[EMAIL PROTECTED]>
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: ntfs
Sender: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Date: Mon, 17 Feb 2003 17:07:42 -0000


thanks, but where is the thread??

It's on this list.

Essentially, when you build a custom kernel you have to rebuild initrd
*or* build the root filesytem driver and the drive controller driver into the kernel.

But to recap:-

At 06:00 17/02/2003 -0800, you wrote:

I have Red Hat 8 setup with all the kernel-devel packages installed.  I just
downloaded the 2.4.20 kernel and attempted to configure it. After I do setup
everything I rebooted. I am currently using the Grub boot manager and when I
boot it gives me the following error:
'Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS:
Unable to mount root on 00:00'

I did a make install to add the line into the grub.conf file but this error
still occurs. Any ideas?

Did you build the relevant root filesystem support into the kernel or make it
as a module and rebuilt initrd?


hih
nick@nexnix


At 06:19 17/02/2003 -0800, you wrote:

I compiled module support for ext3 which is the filesystem I use. I did not
rebuild initrd with mkinitrd but I thought that the make install did that
for me. Is this not correct?

Hmm - not sure if "make install" does rebuild initrd. That's not a standard
feature so unless RedHat tweaked the Makefile then I don't suppose it will.

Personally I build my kernels with hardwired support for the root filesystem and whatever
hardware i need (eg scsi raid controller) to access said filesystem. Some
say this is best others not..... YMMV.

At 06:58 17/02/2003 -0800, you wrote:

This was the first time I built a custom kernel so I went from the same
configuration that my current installed system used for these options.  Say
I didn't want to rely on the make install procedure... How would I rebuild
the initrd properly. This is the process I followed.
make clean
make mrproper
make menuconfig
make
make bzImage
make modules
make modules_install

copy bzImage from /usr/src/linux/arch/i386/boot to /boot
edit the grub.conf file by copying the previous entries and making a new
entry and changing the vmlinuz kernel pointer to the new bzImage filename.

All the above is quite correct although I do

"make dep clean && make bzImage modules && make modules_install"

as one command. (The && means "continue if last completed successfully")
This allows one to go and get coffee, returning to find a built kernel or the
reason why the build failed...

Then as you do, copy the new kernel to /boot and modify the bootloader
accordingly. As I build my root filesystem driver into the kernel I don't need
to update initrd - but I have seen it done and the process involves mkinitrd.
"man mkinitrd"  (sorry  ;> )

hih
nick@nexnix


There was no further dialogue, so I assume problem solved.

ttfn
nick@nexnix




--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

RE: ntfs

Reply via email to