Sponsored Content
Full Discussion: RHEL Installation using NIM
Operating Systems AIX RHEL Installation using NIM Post 302491949 by kah00na on Friday 28th of January 2011 05:36:40 PM
Old 01-28-2011
If you are creating your RedHat server as an LPAR behind a VIO server, you can upload the RH installation *.iso disk image to vio:/var/vio/VMLibrary, create a virtual CD drive for your RH LPAR, and "load" the .iso image into the virtual CD drive, and then boot from it. I did this and was able to install RedHat just fine. You have to open a console window to be able to go through all the prompts. They are kind of messed up spacing wise but you can get through them.
This User Gave Thanks to kah00na For This Post:
 

10 More Discussions You Might Find Interesting

1. AIX

migrate NIM server through NIM installation

I try to migrate a NIM server from one server to another. I try to do a mksysb on NIM server restore the NIM server's mksysb to a client through NIM installation shutdown NIM server start newly installed client as NIM server Does anyone do this before? who can give me some suggestion? (1 Reply)
Discussion started by: yanzhang
1 Replies

2. AIX

Problem with nim installation

Dear Frnz, I have a strange problem with nim installation. I am able to push the image from Nim server to the client and the Os is reinstalled successfully.But after the installation the client doesnt hold any host name or ip address.That is the host name is assigned as local host and ip is... (2 Replies)
Discussion started by: sriram.s
2 Replies

3. Red Hat

RHEL 5 installation problem

Hi everyone, I m new here and I have few questions regarding RHEL installation. The story goes like this... I have a PC with the following specifications: 1. ASUS P5N-MX motherboard with on-board GForce 7050/nforce 610i chipset 2. Intel Pentium Dual Core Processor 3. Two SATA HDD(250GB + 160GB)... (4 Replies)
Discussion started by: willa
4 Replies

4. Red Hat

RHEL Installation issue.

Hi Gurus I am trying to install RHEL linux enterprise Edition v5 on a Dell Optiplex 320 desktop. After the Grub menu,i get the error,Kernel could not be loaded. I am a newbie in linux and would appreciate any help in moving forward. Thanks HG (1 Reply)
Discussion started by: Hari_Ganesh
1 Replies

5. Red Hat

rhel installation

hi, i'm using rhel 5 .......we need to install RHEL 5 in many system and also we need install limited packages, for that we have to select the required packages will installing, this is very hectic( selecting packages).......so is there any option to make our own bootable DVD by seleting... (6 Replies)
Discussion started by: sagar_md
6 Replies

6. AIX

NIM client installation hangs at 0608

Hi All, I am facing very strange problem. I have created NIM server with 6.1 TL4SP3. I am having SPOT and MKsysb of the same version. I am able to install the client using this spot and mksysb. Now I got the requirement of installing the 5.3 ML11SP3 client. So using the mksysb of 5.3 ML11SP3, I... (3 Replies)
Discussion started by: falgun6666
3 Replies

7. Red Hat

RHEL installation on HP NetServer LH6000

Dear experts, Can any one suggest, whether RHEL is supported in HP NetServer LH6000 U3 Thanks (2 Replies)
Discussion started by: ./hari.sh
2 Replies

8. UNIX for Dummies Questions & Answers

rhel installation

just confused.im about to install red hat now however in partition, do I need to put /swap on Mount point? pls advise as Im confused (1 Reply)
Discussion started by: lhareigh890
1 Replies

9. AIX

AIX NIM installation

Could you please let me know, if it is possible to have NIM server running on one volume group and other applications like oracle running on other volume group. Do we need to have a dedicated server for only AIX NIM server?. I am new to AIX and planning to install NIM server on a test server. which... (3 Replies)
Discussion started by: saikiran_1984
3 Replies

10. Linux

Installation issue RHEL 6.5 on SAN

HI All I am facing issue in installation of Red Hat 6.5 on SAN.. i am having a partion of 2 TB in my SAN and i am installing the operating system after completed the installation it not booting and giving the error. (2 Replies)
Discussion started by: deviltech
2 Replies
MKRESCUE(8)                                                   System Manager's Manual                                                  MKRESCUE(8)

NAME
mkrescue - make rescue floppy or CD SYNOPSIS
/sbin/mkrescue makes a bootable rescue floppy or CD using the default kernel specified in lilo.conf. DESCRIPTION
mkrescue takes its specifation for the kernel from the default image specified in /etc/lilo.conf. If the actual default is an other= spec- ification, then use the first image= specification. Any associated initial ramdisk (initrd=), and append= options will also be used. The root directory will be taken to be the current root. A bootable floppy or CD-image will be created using LILO version 22.5.5 or later. mkrescue normally requires no options, unless a CD-image is desired (--iso). OPTIONS
--append <string> Override any append= options taken from the default image. If there is any doubt about whether the lilo.conf options are correct, then specify no kernel parameters by providing the null string (--append ""). --debug Provide verbose output of the operation of mkrescue, pausing to allow the setting of internal operating parameters to be viewed. <CR> must be hit to proceed from these pauses. --device <device> Make the floppy on a device other than /dev/fd0. The floppy disk will always be made to boot on BIOS device code 0x00 (A: drive), without regard to the drive on which it is created. --fast Use a faster method of creating the boot floppy. This involves first creating a file of --size 1k blocks (default is 1440) mounted using a loopback device, creating the bootable floppy, then copying the entire file to the disk. --fs [ ext2 | msdos | minix ] Specify the type of filesystem to create on the drive. ext2 is the default, but msdos and minix allow slightly more disk sectors for really big kernels. --help Print a short usage synopsis, including a list of command options. --image <label> Specifies the label or alias of the particular image from which the append, initial ramdisk, root, keytable, and kernel information is to be taken. --initrd <filepath> and --kernel <filepath> These options, which must be used together, allow specification of an arbitrary kernel file and initial ramdisk file to be used on the created boot floppy. Be sure you know what you are doing before you use these options. If no inital ramdisk is needed with a particular kernel, then you MUST specify --initrd "", meaning a null pathname. --install [ text | menu ] Allows overriding the default human interface used with the rescue bootloader (configuration file "install=" option). text is the default on 1.2MB and 1.44MB floppy disks, and menu is the default on 2.88MB floppies and HD emulation on CD-R media. --iso Create an ISO-9660 bootable CD image (El Torito Format) suitable for burning to a CD-R or CD-RW. The --device specification defaults to the filename rescue.iso, and the --size defaults to 2880. A utility such as "wodim" may be used to burn the ISO file to a recordable CD medium. With this ISO option, the --size HD option is allowed. --nocompact For faster kernel loading from a floppy, LILO map compaction is normally enabled. This option will disable map compaction by omit- ting the lilo -c switch. --noformat Suppresses creation of a new filesystem on the boot floppy. This option may be used ONLY when you know that the floppy you will be writing upon is formatted with the same filesystem as specified by --fs XXX (default is ext2). --root <device> Specify the root filesystem for the kernel on the boot floppy. The currently mounted root is taken as the default specification. --size [ 1440 | 1200 | 2880 | HD ] The default floppy disk size is 1440, meaning a 1.44MB floppy. When --iso is specified, the default size is 2880. Allowed specifi- cations are 1200, 1440, or 2880, meaning a 1.2MB, 1.44MB or 2.88MB floppy, respectively. No other floppy disk sizes are supported. The HD specification, meaning "hard disk", may only be used with the --iso option, to indicate a 16MB hard disk is to be generated for emulation. This allows for very large kernel/initial ramdisk combinations on CD-R. The hard disk image is created using loop- back devices /dev/loop0 and /dev/loop1, which must be free to utilize this size option. --version Print the version number of mkrescue, then terminate. SEE ALSO
cdrecord(1), dd(1), wodim(1), lilo.conf(5), lilo(8), mkfs(8), mkinitrd(8), mkisofs(8), mount(8) 6 Mar 2011 MKRESCUE(8)
All times are GMT -4. The time now is 03:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy