default=linux
image=/boot/vmlinuz-2.4.2-2
label=linux
initrd=/boot/initrd-2.4.2-2.img
read-only
root=/dev/md5
image=/boot/vmlinux-2.4.16
label=firewall
initrd=/boot/initrd-2.4.2-2.img
read-only
root=/dev/md5
Could it be that I didn't update anything with the initrd 2.4.2-2 version?
I've never had to touch it and yet have systems running quite fine..??
Should I be using mkinitrd, I've never created a new one (n00b he he)....
thanks,
George Vieira
Systems Manager
Citadel Computer Systems P/L
-----Original Message-----
From: Howard Lowndes [mailto:[EMAIL PROTECTED]]
Sent: Monday, 14 January 2002 8:12 AM
To: George Vieira
Cc: Sydney Linux Users Group (E-mail)
Subject: Re: [SLUG] RAID1 system boot problem after new kernel compile
Have you got the RAID elements included as monolithic or as modules?
If they are modules then you might need to build and use an initrd.
Just a stab in the dark.
On Mon, 14 Jan 2002, George Vieira wrote:
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
