Sponsored Content
Full Discussion: Hardware Upgrades..
Top Forums UNIX for Dummies Questions & Answers Hardware Upgrades.. Post 4035 by PravusMentis on Tuesday 17th of July 2001 11:37:07 AM
Old 07-17-2001
Hmm I'll be using the Red Hat 7.1 with I believe the 2.4 Kernel? Would I still need to do all of that?
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

RedHat remote upgrades

Is there an easy (and safe) way to upgrade RedHat versions remotely? I know the difference between 7.2 and 7.3 is just a bunch of newer .rpm file versions. Or is there more? Do I have to boot the CD and choose upgrade? What if I'm 100 miles from the server and would like to avoid traveling there?... (1 Reply)
Discussion started by: ArkiMage
1 Replies

2. SuSE

Linux(Suse) Upgrades

Hello, Anyone out there deal with updating OS on linux servers remotely? We use Suse but like to hear what someone else does with any linux version. We have network connectivity to our remote locations but it's just a DSL connection, so some will be fast and some will be slow. Thanks for... (1 Reply)
Discussion started by: benefactr
1 Replies

3. News, Links, Events and Announcements

Solaris 10 and live upgrades

two articles related to live upgrades that i found useful and noteworthy. Solaris 10 5/08 Live Upgrade Gotcha :: Col’s Tech Stuff Solaris Live Upgrade and Patches :: Col’s Tech Stuff (0 Replies)
Discussion started by: pupp
0 Replies

4. AIX

HMC upgrades

Hey!!! Has anyone done HMC patch installation remotely? I would love to know if that would be possible. I have been doing through CD/DVD but hate to do the additional work of finding someone in the DC and sending him the CD's. I have seen the option to supply remote site. can that be helpful?... (5 Replies)
Discussion started by: balaji_prk
5 Replies

5. AIX

How can I manage redundant HMC upgrades with firmware upgrades?

Lets says I have 2 HMC's A and B, connected to a p570 managed system. Right now the firmware level of the p570 is EM320_076 and that needs to be upgraded to EM340_095. Now the HMC's are at V7R3.3 and as per the code matrix the HMC's needs to be upgraded to V7R3.4 Servicepack 2. Now my... (5 Replies)
Discussion started by: balaji_prk
5 Replies

6. AIX

Need to confirm something regarding TL upgrades

Hi everyone, My current AIX OS level is "7100-01-06-1241" and I am planning to upgrade it to " 7100-02-03 ". Can i directly upgrade it to "7100-02-03" from 7100-01-06" ? or first i need to upgrade the "7100-01-06" LPAR to TL 02 and then reboot and then upgrade it to TL 02 SP03 ? ... (4 Replies)
Discussion started by: System Admin 77
4 Replies

7. What is on Your Mind?

Update on UNIX.COM Site Upgrades (Desktop)

This post is about the "Desktop" view, not "Mobile' ... First of all, I want to thank everyone for all the great comments, error checking and feature suggestions as we modernize the site, step-by-step. Also, thank you for your patience with me when as we make the site better. So far, we... (1 Reply)
Discussion started by: Neo
1 Replies

8. What is on Your Mind?

Discussion (Thread) Tagging Upgrades

Dear All, I have made significant progress coding new discussion thread tagging features. As always, we want all users to tag thread and moderators to tag threads with relevant keywords. Moving forward, in addition to the #1 important "human tagging", we will also auto tag threads with one... (4 Replies)
Discussion started by: Neo
4 Replies
LVMCREATE_INITRD(8)					      System Manager's Manual					       LVMCREATE_INITRD(8)

NAME
lvmcreate_initrd - create an initial ramdisk to boot with root on a logical volume SYNOPSIS
lvcmreate_initrd [-i|--iop IOP] [-D|--devfs] [-v|--verbose] [-V|--version] [KernelVersion] DESCRIPTION
lvmcreate_initrd creates a new compressed initial ramdisk /boot/initrd-lvm-KernelVersion.gz. The initial ramdisk contains all necessary binaries, shared libraries and a linuxrc file to switch to a logical volume based root filesystem. To build an initial ramdisk for a ker- nel other than the one currently running add the KernelVersion parameter (e.g. lvmcreate_initrd 2.3.25) on the command line. OPTIONS -h, --help Print a usage message on standard output and exit. -i, --iop IOP Specify the LVM kernel IOP version if you are using wrapper scripts in /sbin. This is only necessary if you are building an initrd for a kernel other than the current one, and you have tools for multiple IOP versions installed. -D, --devfs Force the use of devfs when building the initrd. lvmcreate_initrd by default probes for devfs by checking for /dev/.devfsd, which is created by devfsd when it is running. This option will force lvmcreate_initrd to do this, when devfsd is not currently running. -v, --verbose Gives verbose runtime information about the creation of the ram disk image. -V, --version Print version number and exit successfully. The necessary actions to change your system into a "root on logical volume" one are: Create a small (~20MB) partition which is BIOS reachable to hold the /boot filesystem (if you already have a small partition based root filesystem this can be used instead). If you want to boot standalone from this partition in an emergency, copy all the necessary binaries and libraries to that filesystem as well and create a corresponding /etc/lilo.conf entry. In order to be able to edit lilo.conf when booted standalone, you should move /etc/lilo.conf to /boot/lilo.conf and create a symbolic link to it in /etc. This is not needed if you have a boot/root floppy which contains the LVM binaries and the library. Create all logical volumes you need (for root, usr, opt etc.), create filesystems in them, mount them and transfer all files from the par- tition based filesystems into the logical volume based ones. Set up your /etc/lilo.conf with a boot configuration like: image = /boot/vmlinuz initrd = /boot/initrd-lvm-KernelVersion.gz root = /dev/YourVG/YourRootLV label = rootonlv append = 'ramdisk_size=8192' Replace YourVG and YourRootLV by your actual volume group and root logical volume names. You also need to change the ramdisk size to be at least as large as that reported while lvmcreate_initrd is run. If you have enough memory, it is OK if the ramdisk size in /etc/lilo.conf is larger than what lvmcreate_initrd reports (the memory is freed after booting). Also, your /etc/fstab in the root logical volume should contain entries for the root LV, and the boot partition, along with any other LVs you have configured: /dev/YourVG/YourRootLV / ext2 defaults 0 1 /dev/YourBootPartition /boot ext2 defaults 0 2 /dev/YourVG/YourUsrLV /usr ext2 defaults 0 3 /dev/YourVG/YourOptLV /opt ext2 defaults 0 4 etc. You can use other supported filesystem types as well (e.g. reiserfs) if you have support for those in your kernel. Run lilo, reboot and try... The partitions containing the former /usr, /opt etc. filesystems can now be used as physical volumes. Use pvcreate(8) to turn them into PVs and then use vgextend(8) to add them to e.g. YourVG. DIAGNOSTICS
lvcmcreate_initrd returns 0 for success. 1 is returned in all other cases. SEE ALSO
lilo(8), lilo.conf(5), fstab(5), lvm(8), pvcreate(8), vgextend(8), lvcreate(8), vgcreate(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS LVMCREATE_INITRD(8)
All times are GMT -4. The time now is 02:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy