Thanks to all for the help...slowly getting up to speed here..
a couple of quick questions:
>
> lynx filename
>
duh...should have thought of that..in face the first line on the man page
suggest this...if you read it closely...
> >
> > ----
/dev/hda1' and said yes to all the fixes.
>
> It would have been more informative to have explained what the error
> messages were after the use of netconf.
>
Hmmm...lots of stuff in there...unfortunately, when I did an fdisk to check the
drive, the table came up empty...so I don't really trust the system right now
> >
> > Now, when I did a reboot, I noticed that the modprobe file was not there and
> > several messages were left in /var/log/messages file. Soooo...I copied the
> > modprobe file from my RedHat disk and at boot up I get the message:
> >
> > modprobe is not an ELF file
>
> That means the file was made in a.out format, you would need to load the
> a.out module before using that file, it should reside in
> /lib/modules/2.0.34/fs and is called "binfmt_aout.o" .
>
> modprobe binfmt_aout.o
> Before trying to install the new driver module.
>
I thought that modprobe file was the problem, but your right, the message is an
output message from modprobe. Pretty helpful huh? If they would report the
offending module that would be a little better.
> >
> > Ummm...I only have one distribution CD, and this file worked when it was
> > installed...
> >
> > What magic is the install program doing that a simple copy doesn't do ?
> > Is there any way to determine which other system files were also corrupted ?
>
I used the rpm install for the modprobe, which I guess I should have done first
time, instead of copying a file from the RH disk...
> I doubt if they are corrupted, if you are using Kerneld to autoload modules
> then i suggest you read the mini-howto for Kerneld found in the /usr./doc/*
> directory's, that will explain how kerneld works and explain some "pit
> falls", one of which i myself have recently fallen into, the problem i have
> had was rather like many kerneld related problems asked about here on this
> list. Problems "will" arise if one has the /usr directory on another
> partition other than "/" (root), kerneld gets started before the /usr
> partition is mounted so kerneld does not get all the needed information, so
> it wount "autoload" modules the way it should.
>
What are the recommended partitions for RH ???
I'm faced with a re-install (Third time this week - obvious newbie here :-),
just to get back and working normally. When I boot now, the prompt is:
root@pm03a11
not sure what that means, but I think it is different from what it used to be...
and occasionally my fdisk comes up with an empty partition table...
> Normaly Redhat starts Kerneld at bootime, so i presume you are using
> kerneld.
> To check if it's running do;
> 'pidof kerneld'
> or
> 'ps ax | grep kerneld'
>
> > Are there other commands required to update the system ? (Just what does that
> > map file do anyway?)
>
> System.map is needed by depmod to make the dependancies file from the system
> calls it has registered, its also needed for debugging.
>
> If you make your own kernel then Sysytem.map can be left in
> /usr/src/linux HOWEVER if your redhat system has a symlink in /boot called
> System.map i suggest you delete it and relink it to /usr/src/linux/System.map
> as redhat-5.1 does not do that in its initscripts as far as i know.
>
> cd /boot
> rm System.map
> ln -s /usr/src/linux/System.map System.map
> Should do the trick.
> You could do that before rebooting.
>
Is this recommended for a new install ? I'm looking to download the newest
kernel and upgrading my system...any other suggestions ?
> If you are using the origanal installed kernel from the CD, then you can
> disregard the commands above.
>
> >
> > Hopeless lost again, Thanks for any help,
> > Ralph
> >
> > Using Red Hat 5.1 V2.0.34
> >
>
> --
> Regards Richard.
> [EMAIL PROTECTED]
Thanks for all your help.
Ralph
I don't know where I'm going, but I'm making good time!
