Re: Linux vs. DOS

> My new problem is that when I execute run.64step378 I get a number of
> "command not found" errors. In poking through the run.64step378 file it
> looks like the problem is with the insmod command. If I try insmod at a
> command line I also get "command not found" and in searching the drive I
> find a bunch of copies of insmod.1 (the man page for insmod), but I cant
> find the actual file. Is there a module I may have missed installing?

OK:
1. You must be logged in as root to use insmod.
2. The insmod program lives at /sbin/insmod so make sure this file exists
(insmod is part of Linux itself, not the EMC).
3. If the insmod program exists then try doing a '/sbin/insmod' from the
command prompt. When insmod is run without any arguments you should get a
message like "Usage:..." then a detailed syntax diagram and brief
instructions.

Here the troubleshooting flowchart forks:

4a. If '/sbin/insmod' works, but 'insmod' by itself doesn't then the /sbin
directory isn't in your path. Check this by entering 'echo $PATH' at the
prompt and your path will be displayed. It might look like
"/do/re/mi:/sbin:/fa/so/la:...". If /sbin isn't there you can either add it
in your .bash_profile file in the /root directory (if you look at this and
it's not self evident how to do this, just let me know). I'm not sure where
the PATH is set initially, but if this is the problem I'll research it
further and figure out what to do. Many initialization files reside in
/etc. Another option would be to edit run.64step378 and change the lines
that start with insmod to /sbin/insmod.

4b. If /sbin/insmod doesn't exist then my initial reaction is to say
something along the lines of "Uh, like wow man, I dunno". Since this isn't
very helpful I think that you should (from a terminal window in X) do 'cd
/usr/src/linux' and then 'make xconfig'. Look in the "Loadable module
support" section and be sure that all three items in there are set to "y".
Also, and I'm stretching it here, check in the "General setup" section and
see if "Support for a.out binaries" and "Support for ELF binaries" are set
to "y" as well. If you change any of this you'll need to save the changes
and continue on with 'make dep', 'make clean', 'make zlmage', 'make
modules', 'make modules-install', and finally 'cp arch/i386/boot/zImage
/boot/vmlinuz'. I don't know whether this process actually creates the
/sbin/insmod file when loadable module support is enabled, or not, but it's
all I can think of right now. One other thing, when you installed Red Hat
5.2 did you pick "Everything" from the list of stuff to install, or did you
use the "Workstation" option or ... I always pick the "Custom" choice and
then install "Everything", although I can't imagine that insmod is optional
in any case as it's pretty important.

Let me know what happens ASAP and I'll try to get you going.

Thanks,

Matt Shaver
(410) 521-3715