According to Ralph Stickley: While burning my CPU.
>
> Thanks to all for the info on info and other info from my previous request!
> But...
>
> The 'man ls' or several such commands says something like this:
>
> "This documentation is no longer being maintained and may be inaccurate or
> incomplete. The Texinfo documentation is now the authorative source"
Well the man page for 'ls' on my slackware-3.6 does not have that sentance,
however i do know what you mean, looking at man(1) command, that phrase can
be reapedly found.
To answer your origanal question on Texinfo, would be to read the man page
for 'setfdprm' it has some text relative to your question, altho' its still
quite hazy, but should help you a little further.
>
> Which I took to mean that the information was obsolete (my assumption). If I do
> 'info ls', the file displayed is the same, with the same disclaimer. How do I
> access the authorative source files ?
> ----
>
> Which of the 255 or so options for lynx allow me to open a .html file that is
> already on my hard disk ? Since I'm no longer on the net (see below), I can't
> access these files from some other computer...
lynx filename
>
> ----
> I had a working network card and set it up using 'netconf'. No problem, well, ok
> a few problems, but I got them fixed.
> Then I decided to upgrade to a newer, better, faster card :-0
> I then installed the new network driver module (gcc, install, insmod commands).
> When I ran 'netconf' and quit, I got some error messages all over my screen that
> didn't look to healthy, so I did an orderly shutdown <ctrl><alt><del>. As
> requested, I did the 'fsck /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.
>
> 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.
>
> 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 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.
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.
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]
