Sterling James wrote:
(ex: mkinitrd /boot/initrd-2.2.5-15.img 2.2.5-15)
How do I get the new dasd added to this RedHat system?
Thanks to anyone who can help.
Check out http://kbase.redhat.com/faq/docs/DOC-2404, "How do I add a new
DASD to a Red Hat Enterprise Linux guest in z/VM (IBM's virtualization
manager)?"
Let me know if that helps
First, please excuse the lack of understanding but the url raised two
questions for me;
1) Is the "cp initrd-$(uname -r).img initrd-$(uname -r).img.orig", just, a
backup? Or am I missing it's intent?
Yep, this is optional and purely for backup purposes.
2) The "mkinitrd -f initrd-$(uname -r).img $(uname -r)"; assuming "uname
-r" returns the current level of the running kernel, if you're doing
several things during a small maintenance window, e.g. - applying patches,
adding dasd, and with this scenario existing;
You are correct. This command assumes you want to rebuild an initrd for
the currently running kernel. If you have multiple kernels installed,
or are building an initrd during a maintenance window where your running
kernel does not match your production kernel version, you'll have to
manually specify the kernel version instead of using $(uname -r).
[use...@localhost ~]$ ls /boot
bootmap symvers-2.6.18-128.el5.gz
config-2.6.18-128.7.1.el5 symvers-2.6.18-164.el5.gz
config-2.6.18-128.el5 System.map-2.6.18-128.7.1.el5
config-2.6.18-164.el5 System.map-2.6.18-128.el5
grub System.map-2.6.18-164.el5
initrd-2.6.18-128.7.1.el5.img tape0
initrd-2.6.18-128.el5.img vmlinuz-2.6.18-128.7.1.el5
initrd-2.6.18-164.el5.img vmlinuz-2.6.18-128.el5
lost+found vmlinuz-2.6.18-164.el5
symvers-2.6.18-128.7.1.el5.gz
[use...@localhost ~]$ cat /etc/zipl.conf
[defaultboot]
default=2.6.18-164.el5
target=/boot/
[2.6.18-164.el5]
image=/boot/vmlinuz-2.6.18-164.el5
ramdisk=/boot/initrd-2.6.18-164.el5.img
parameters="root=/dev/rootvg/rootvol"
[2.6.18-128.7.1.el5]
image=/boot/vmlinuz-2.6.18-128.7.1.el5
ramdisk=/boot/initrd-2.6.18-128.7.1.el5.img
parameters="root=/dev/rootvg/rootvol"
[linux]
image=/boot/vmlinuz-2.6.18-128.el5
ramdisk=/boot/initrd-2.6.18-128.el5.img
parameters="root=/dev/rootvg/rootvol"
"uname -r" would return 2.6.18-128.7.1.el5 which then the mkinitrd would
not accomplish the desired result.
If this is correct, srcipting a maintenance window becomes very tricky.
Thanks
-----------------------------------------
Please consider the environment before printing this email and any
attachments.
This e-mail and any attachments are intended only for the
individual or company to which it is addressed and may contain
information which is privileged, confidential and prohibited from
disclosure or unauthorized use under applicable law. If you are
not the intended recipient of this e-mail, you are hereby notified
that any use, dissemination, or copying of this e-mail or the
information contained in this e-mail is strictly prohibited by the
sender. If you have received this transmission in error, please
return the material received to the sender and delete all copies
from your system.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Brad Hinson <bhin...@redhat.com>
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
