"But I just keep getting the error message on boot up and you know how error messages can just get under your nerves."
You can eliminate error messages by using redirection. Find the boot script that gives the error messages and then locate the actual command within the script. Then append the following to the command:
2> /dev/null
which will throw away any error messages that the command generates but not regular messages. For example if you have an annoying export HIYA command you could get rid of any error messages with:
export HIYA 2> /dev/null
"On a separate issue...how can one ensure that all the packages from the install are in fact completely installed. I had some difficulties installing and the install would hang sometimes trying to read the CD."
You can find out every package that was installed with:
rpm -qa | sort | less
I don't know how you could match that up with what you intended to install.
"...And, I'm using Redhat 9 (Shrike)...seems up2date doesn't work. I have a login on the RHN but for some reason I cannot send info to it telling them what I have installed. Should I skip the use of auto updating or is it worth the hassle."
It is quite possible to maintain your packages using a combination of gftp, rpm, kepackage, and your web browser. That is the way I do it. But learning to do it by hand is probably harder than learning to use up2date. Since I maintained my Linux box with rpm for several years before up2date was created I simply regard up2date as a modern inconvienience.
___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html
Steve Stites
