Sponsored Content
Full Discussion: Redhat 7.3 Installation
Top Forums UNIX for Advanced & Expert Users Redhat 7.3 Installation Post 34298 by LivinFree on Friday 14th of February 2003 03:25:12 PM
Old 02-14-2003
Shouldn't you need to use SmartStart to install on Proliant servers?

Either way, the floppies are MS-DOS formatted, so you can pop them into a Windows box and take a look at the file it complains about - it should just be a text file. Can you perhaps post the KERNEL section of the file? I doubt it's the floppy image is bad if it's out of the box, but if it's been customized, it's very easy to break.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

oracle installation on redhat 7.0/7.1

can anybody tell me that whether oracle 8i is installable on redhat 7.0/7.1. for me it is only working successfully on redhat 6.1 but not later versions cheers (3 Replies)
Discussion started by: balu
3 Replies

2. UNIX for Dummies Questions & Answers

mysql installation error using redhat 7.2

i am a newbie to unix admin stuff so bare with me. -- i get this message when executing mysql_install_db during the installation of mysql. what is the cause of this and how can it be fixed. btw - i have tried installing as root and other accounts also. scripts/mysql_install_db:... (6 Replies)
Discussion started by: theDirtiest
6 Replies

3. Filesystems, Disks and Memory

re-partiton / re-installation on Redhat 7.3

Hello, me and a friend currently operate a dedicated server our /dev/hda2 is starting to get full and we have a lot of information in there we would like to keep, so we are thinking about adding an additional 120GB HD then reinstall the OS to re-partition the partitions, our current setup looks... (3 Replies)
Discussion started by: shaft
3 Replies

4. Red Hat

Python Installation problems on Redhat Enterprise Linux.

Hi All, I have to upgrade python installed on my Redhat enterprise Linux 4. I downloaded the latest python package from python website but not able to install the new package as the make command itself goes on running for more than a day. Can some help me regarding this. Is ther any method to... (2 Replies)
Discussion started by: Praveen H
2 Replies

5. Red Hat

"No Drives Found" error during Redhat Linux AS 4 installation

I'm trying to install Redhat LInux AS 4 update 4 on an IBM x306 series server. I keep getting following error: "No Drives Found. An error has occurred - no valid devices were found on which to create new file systems. Please check your hardware for the cause of this problem." I called IBM and... (2 Replies)
Discussion started by: pieman8080
2 Replies

6. Red Hat

remote redhat installation

Hi guys! I have fedora6 on server and i want redhell5 to be on it. The problem is that the server is located from me several hundred kilometers away. So the only access i have is ssh. On my notebook i have iso-image with redhell5. How can install redhell5 on it and deinstall fedora6? Thanks in... (8 Replies)
Discussion started by: smallman
8 Replies

7. Red Hat

Help with Redhat installation problem

Hello; I have 4 servers with RedHat Enterprise server 32-bit installed. i'm trying to install 64-bit system instead but the hardware has only CD drive (not DVD). When i tried to use external DVD drive and connect it to the USB to install the 64-bit system, it starts ok but then it ask for the... (2 Replies)
Discussion started by: Katkota
2 Replies

8. Red Hat

Redhat 9 installation problem

All, I am trying to install redhat9 to my system. I have 26 GB of unpartitioned space, and I do have xp-2 already installed on my system in c: . I am using external DVD-RW to install linux. I have booted the CD, chosen Graphical mode and now installation frizzed with below message: ... (5 Replies)
Discussion started by: joshilalit2004
5 Replies

9. UNIX for Beginners Questions & Answers

Redhat installation

Hi everyone, i am new to unix system. i got a project to install a web server (grafana)and database(influxdb) to install in redhat 7. The alloted space for my virtual machine is 1.3 TB . i don't have any idea how to allocate this space for redhat directories. DO i have to continue with the basic... (1 Reply)
Discussion started by: munnancs
1 Replies

10. Red Hat

Dependency Error for OpenSSL i686 installation in Redhat 7.4 x64

Hi, I am unable to install openssl package due to some of the dependencies: # rpm -i openssl098e-0.9.8e-29.el7_2.3.i686.rpm warning: openssl098e-0.9.8e-29.el7_2.3.i686.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY error: Failed dependencies: libcom_err.so.2 is needed by... (0 Replies)
Discussion started by: rsimpossible86
0 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 01:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy