Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The aim of my task is to eventually create a customized minimum red hat installation (only base/core packages)
I have downloaded the RHEL 5 distribution for 64 bit amd/x86 machines and I have copied off all the data from the CDs onto my local harddrive (a 32 bit RHEL 4) machine. I run the mkisofs command to create a bootable iso with CD1 contents in it.
When I burn this CD and try to install on the target machine, after the first couple of steps (Language, keyboard) I get a prompt saying : "What type of media contains the packages to be installed?" with a list of possible media types.
I select CD ROM and the next screen gives me the following error message :
"The Red Hat Enterprise Linux Server CD was not found in any of your CDROM drives. Please insert the Red Hat Enterprise Linux Server CD and press OK to retry."
At install time the other consoles show the following messages :
"starting to STEP_URL
trying to mount CD device hdc
"<7>ISO 9660 Extensions: Microsoft Joliet Level 3 <4>Unable to load NLS charset utf8 <4>Unable to load NLS charset utf8 <7>ISO 9660 Extensions: RRIP_1991A"
1. What causes this error?
2. Must I perform the packaging on an environment identical to the target machine? (i.e. a 64 bit RHEL5 env, as opposed to a 32bit one? - tried it, doesnt work)
3. The distro is currently copied to directories like CD1, CD2 etc. When I use mkisofs, do I need to have the files under a particular name (like it used to be i386 for older RHEL versions)?
4. Since RHEL5 has a completely different directory structure etc (such as Server/*rpms, no base dir, no RPMS dir, no hdlist* files), what is actually required to create my own iso? Can I just package the CD1 like that? Do I have to perform any further steps?
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Why???? This is already possible from the media without any changes. One just has to un-slect everything, if done correctly then only the first CD (or ISO image) is needed. After the first time then one can use the anaconda.ks.cfg file for additional installations.
This error was because I was missing the .discinfo file in the base directory. This is what anaconda looks for to determine that the CD is a valid Red Hat install CD. Once I put this in, the installation went through fine.
Lenard, I was trying to create a custom installer that installed basic Red Hat and then went ahead and installed our company software on it. It had to be an automated installation so that our boxes could be mass installed with it in production.
I was having the same issue, and the .discinfo file was indeed NOT in the root directory. I recreated an image with this file and was able to successfully load a system with a kickstart file on this new image.