linux-kernel - set up new kernel with grub

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 4 Apr 2007 11:36:23 -0500
From:	"Michael" <gonwg@...mail.com>
To:	<linux-kernel@...r.kernel.org>
Subject: set up new kernel with grub

Hi,

I compiled a new kernel: 2.6.20.3, and hope to test it without removing 
my old kernel.

Here is what I did by following 
http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1204148,00.html :

I built the kernel in a local directory, say "mydir", with kernel 
"bzImage-2.6.20.3" and map file "System.map".

>su          (#become a root)

>cp mydir/bzImage-2.6.20.3 /boot/bzImage-2.6.20.3
>cp mydir/System.map /boot/System.map-2.6.20.3

>cd /boot
>ln -s /boot/bzImage-2.6.20.3 /boot/bzImage
>ln -s /boot/System.map-2.6.20.3 /boot/System.map

>vi grub/menu.lst

add a new entry as
**************************************
title Red Hat Linux (2.6.20.3)
    root (hd0, 0)
    kernel /boot/bzImage ro root=LABEL=/
    initrd /boot/initrd-2.6.20.3.img
**************************************

>create an initial ram disk image by
mkinitrd -k /boot/bzImage -i /boot/initrd-2.6.20.3

It reports wrong usage of "mkinitrd", and no initrd-2.6.20.3.img is 
created.

Any idea about what's wrong with the "mkinitrd" command ?

Thanks.

Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/