G'day Jim,
On Fri, 6 Feb 2004, Jim Sibley wrote:
Is it that the boot record has to be
updated by zipl to get to the new initrd module?
Yes. As I understand it, it goes like this...
When you ran mkinitrd, what's happened on the disk is that a new
file to contain your initrd has been
The default zipl.conf for Red Hat Enterprise Linux 3.0 AS is:
[defaultboot]
default=linux
target=/boot/
[linux]
This problem is getting to be a FAQ...
http://linuxvm.org/Info/HOWTOs/mkinitrd-notes.html
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Scully, William P
Sent: Friday, February 06, 2004 3:21 PM
To: [EMAIL PROTECTED]
Subject: zipl.conf for RH
But how do I make the change permanent in RH EL 3.0
AS?
The mkinitrd makes the /etc/modules.conf change
permanent in the /boot/initrd... module.
=
Jim Sibley
RHCT, Implementor of Linux on zSeries
Computer are useless.They can only give answers. Pablo Picasso
This problem is getting to be a FAQ...
I had that feeling when I encountered the change in
RHEL3 (RH 7.1/7.2 uses the same technique SuSE). Both
SuSE 8 and RHEL3 now use mkinitrd, but the syntax is
different.
I do need to update the page to allow for using labels
rather than /dev/dasd...; I'm
The mkinitrd makes the /etc/modules.conf change
permanent in the /boot/initrd... module.
Then running zipl will make it permanent in the boot sector of the IPL
disk.
-Mike MacIsaac, IBM mikemac at us.ibm.com (845) 433-7061
: Friday, February 06, 2004 3:55 PM
To: [EMAIL PROTECTED]
Subject: Re: zipl.conf for RH 3.0
The mkinitrd makes the /etc/modules.conf change
permanent in the /boot/initrd... module.
Then running zipl will make it permanent in the boot sector of the IPL
disk.
-Mike MacIsaac, IBM mikemac
The mkinitrd makes the /etc/modules.conf change
permanent in the /boot/initrd... module.
Then running zipl will make it permanent in the boot
sector of the IPL
disk.
If you use the same initrd name, then the zipl may not
be necessary. I think the zipl is only needed if the
/etc/zipl.conf
]
Subject: Re: zipl.conf for RH 3.0
The mkinitrd makes the /etc/modules.conf change
permanent in the /boot/initrd... module.
Then running zipl will make it permanent in the boot sector of the IPL
disk.
-Mike MacIsaac, IBM mikemac at us.ibm.com (845) 433-7061
I just did a quick experiment with RHEL3, mkinitrd,
and zipl.
1) I updated /etc/modules.conf, then did the mkinitrd
using the same name for /boot/initrd When I
rebooted, the new dasd were NOT there.
2) I then did a zipl and rebooted. The new dasd was
picked up.
Bottom line - both the
10 matches
Mail list logo