Re: zipl does not pick up "new" disks
Jim Sibley <jlsibley-r/[email protected]> Wed, 15 Oct 2003 09:57:08 -0700
| Newsgroups | gmane.linux.redhat.taroon |
|---|---|
| Message-ID | <OFF210A2F3.7FF5C115-ON88256DC0.005B7778-88256DC0.005D1F29@us.ibm.com> |
"You have to use mkinitrd to create a new /boot/initrd* file as the
information
is copied into it without any way to override it."
1) edit /etc/modules.conf for the new dasd addresses
1) cd /boot (without the the new initrd will end up in the directory
you issued the mkinitrd in)
2) mkinitrd newinitrd $(uname -r)
3) update /etc/zipl.conf
ramdisk=/boot/newinitrd
4) zipl (to update the ramdisk file name)
You can use the old name if you
- cd /boot
- mkinitrd -f initrd-$(uname -r).img $(uname -r)
note: the version number (uname -r) must be the same as the /lib/modules
subdirectory with the version modules. If not, then you need to use the
subdirecotry name of /lib/modules, i.e., if there is a /lib/modules/abcd,
used abcd as the release.
Regards, Jim
Linux S/390-zSeries Support, SEEL, IBM Silicon Valley Labs
t/l 543-4021, 408-463-4021, jlsibley-r/[email protected]
*** Grace Happens ***
--
Taroon-beta-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/taroon-beta-list