-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06 Jun 2003 21:45:35 -0400, Jeremy Petzold wrote:
> What does Redhat do with their set up? sheesh...I love the polish but > what is diffrent in the kernel set up proccess from debian to redhat? > > I am getting a new kernel panic now after I made the root=/dev/hda1 > change > > not I get: > > warning: unable to open initial console. > kernel panic: no init found. try passing "init=" option to kernel The good thing of partition labels is that you don't need to remember whether /dev/hda1 really is your root-partition. Is it? > I changed to lilo hoping I was just Grub but it is not...it is something > with how RH sets up the system that I am not privy to. > > here is my lilo.conf: > > prompt > timeout=50 > default=linux > boot=/dev/hda > map=/boot/map > install=/boot/boot.b > message=/boot/message > linear > > image=/boot/vmlinuz-2.4.20-8 > label=linux > initrd=/boot/initrd-2.4.20-8.img > read-only > append="hdc=ide-scsi root=LABEL=/" > > image=/boot/vmlinuz2.4.20-ck > label=linux-ck > read-only > append="hdc=ide-scsi root=/dev/hda1" > > does it have to do with the initrd? could some one explain to me what it > is that the initial ramdisk does? and why I need one if I do. > > also, "mkinitrd /boot/initrd2.4.20-ck.img linux-2.4.20" as I saw above > told me something about linux-2.4.20/<blah>/<blah>/ is not a directory. Try again without making type mistakes. It's mkinitrd /boot/initrd-2.4.20-ck.img 2.4.20-ck and requires that you have your kernel modules built and installed correctly. With LILO it requires that you edit lilo.conf and rewrite LILO (with e.g. lilo -v). - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+4aGK0iMVcrivHFQRApV9AJsERar9tDsy59BfNt3weqf+MtatbgCfVNdA jbCRDS16nTvAmfLRIGm2Kz0= =Ir6z -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list