Red HatThis forum is for the discussion of Red Hat Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I wanted to install RHE4 from an NFS server. So I followed the following steps:
1. #mkdir /mnt/inst
2. I inserted the first CD and issued the following command:
#mount /mnt/cdrom
3. # cp /mnt/cdrom/.discinfo /mnt/inst
4. # cp -ar /mnt/cdrom/RedHat /mnt/inst
5. #umount /mnt/cdrom
6. I then wanted to repeat steps 2 and 4 for the others CDs. But the following error returned
cp: overwrite '/mnt/inst/RedHat/RPMS/TRANS.TBL'?
obviously the RPMS/TRANS.TBL file exists in multiple CDs.
Whether I accept or reject the overwriting process, installating from the NFS didn't work with me. It returned an a fatal error.
What are the proper steps to copy the installation CDs into an NFS server in order to install RHES 4 successfully through netwoek?
i *think* all you have to copy from cds 2-4 are the rpms (into the inst/RedHat/RPMS directory). i know that you do not have to have one directory for each cd, but i could be wrong that there are no other files than rpms from cds 2-4 that are needed.
also, what error is returned when you try to install? it might be related to the nfs server not having exports configured correctly.
Distribution: Anything NOT SystemD (ie. M$) related.
Posts: 918
Rep:
i realize that the you don't *have* to have seperate directorys... but when the installer finds the first level it will dig deeper for any more files it looks for when it's time for it to change to the next set of data (cd's).
i suggested this as a 'possible' quick solution-- even tho frankly i'm not sure rh still implements it's install program like this since 7.x.
I had already followed the steps in the documentation and as in the link you provided me. Also, the error was not because of the NSF server because when I copied the CDs into different directories in the NFS server and changed the mount to sysimage every time the installer requires a specific CD, it worked fine. But of course this method is not practical because it involved manual interaction during the installation.
I'm trying to get Redhat Enterprise 4 AS installed now also. I've copied the RPMS and base directories off the installation DVD and have them shared in an NFS mount that has a RedHat/ directory that all these reside in.
When I boot off the RHEL3 Disc 1 that I have (using 'linux askmethod'), I'm able to set up networking and give the hostname and directory to look for the NFS mount, but every time it comes back and gives me the following error:
That directory does not seem to contain a Red Hat Linux installation tree.
What do I do? I have these files and a copy of the original .iso available to do this install.
I made sure the .diskinfo file was there. Still, I face the same problem. I don't know how the documentation said to copy /RedHat folder in every CD into a single directory whereas that folder in every CD has the same filename.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.