On Sat, 17 Jul 1999, Ed Harrison wrote:
> I got the latest unstable; it compiled without error; "make install" gave no
> errors.
>
> BUT, after insmod ftape works, "insmod zftape" and "insmod ftape-internal"
> produces a long column unresolved symbols.
>
> I am very new to Linux, newer to ftape. I have no idea what an unresolved
> symbol is, nor how to get them resolved.
>
I issued the same commands, and each of them was executed without an
"unresolved symbol" message. However, I got quite a bunch of them at the
end of the 'make install' command. As far as I could interpret they were
calls for modules I had not included when I built my kernel. Among them
were block/raid0.o, ../raid1.o and raid5.o, which I had not included in
my kernel.
Your question "what are these unresolved modules": ftape may call for ser-
vices the kernel should provide. But if your machine doesn't have the
hardware corresponding to these disk-arrays, the kernel can leave these
services out. And ftape issues a warning that it will break down if a call
to this module is maid. (So far my limping explanation that many people
certainly can improve on. I didn't worry about the warnings. Maybe you
should not either, maybe you should. Did you compile your own kernel?
Could you get ftape to execute any commands of mt (mt rewind -f /dev/... ,
etc)
----
Julien Michielsen [EMAIL PROTECTED]
