I got a message from Dave Wreski detailing how I could use alternative
methods for loading my ftape drivers, versus using an init script at
startup. I haven't tried that yet, but will (maybe...more on that in a
moment). He also suggested I should use modprobe to load the drivers in
the correct order, rather than using insmod directly. I tried that
immediately, and discovered that *modprobe* is the source of my
problems. It does not load the drivers in the order prescribed in ftape
3.0's documentation, and consequently, I get the "Unresolved symbols"
errors. Using insmod directly, and following the order listed in the
ftape documentation results in a working ftape. I saw something in the
install guide that said not to use MODVERSIONS when compiling ftape on
2.0.x kernels; that it only worked with 2.1.x kernels. So, is that part
of the problem with modprobe? Does modprobe expect the modules to be
compiled with MODVERSIONS turned on?
Now as to why I may not try Dave's suggestions regarding
/etc/conf.modules: I posted to the list about this before, and I don't
know if I got a response, because I don't have the patience to read all
my mail. I use the Communicator mail client, and when I fire up
Communicator, it makes my fonts go south. Every single time. So I may
be rolling back to Caldera (Damn!) unless someone can suggest a solution
(if you know a fix, email me privately...I read the private messages
first, and may not have the patience to get to the digest). I require
Communicator, and it won't run on my system. I can't read more than one
mail message before I have to shutdown X and restart it. It's not worth
it.
Anyway, thanks to all for the suggestions. I hope I can find a cure for
Communicator...otherwise your help has been wasted effort (but *much
appreciated* wasted effort ;-)).
Mike
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
