Well... I think I already gave this question a reply, but there
are some things I have to add.
On Sun, 14 Mar 1999, ^Mr^ wrote:
> i tried removing appletalk completely by doing a make xconfig , and
> setting the appletalk as off and not as a module .. then , i compiled my
> kernel normally , and /sbin/lilo
Yes, for the sake of clarity it's better to say in your message
the path as well. I hope you don't use it in your daily life. In scripts
is very usefull to give full path or else you will lose time as the shell
expands the path. In scripts, for portability you can use variables for
commands.
LILO=/sbin/lilo
$LILO
But this is only for portability - some distributions (or sysadms)
put executables in other places. When it comes to prompt, you lose time
by giving the full path. Really, the shell finds the file a lot faster
than anybody can type even a short string like /bin/.
> now , whenever i startup , i see the error msg :-
> /lib/modules*/appletalk : unresolved symbol ..
That is the result of running at boot time of depmod -a.
> i've searched everywhere for a file that sets which module are gonna be
> loaded , but coulnd't find a clue ..
> the only that i found was that appltalk.o was in
> /lib/modules/2.0.36/modules.dep
Isn't there a file named appltalk.o below /lib/modules.2.0.36? To
find out in no time use find.
> should i just remove that appletalk line in the modules.dep file ?
Editing modules dep can cause trouble. I mean for me it happens
all the time to make mistakes. This way once I did in vi something like I
gave the 'x' command (which is del) instead of ':x' (which means save
changes and exit). I type quite fast so I realised I was still in vi. I
didn't notice I erased a character. I repeated the command, but the
mistake was already done. My advice would be just erase modules.dep, than
run `depmod -a` to remake it. Could even go faster than editing the file
by hand.
> another question ...
> when i did a man xconfig , there were many stuff loaded as modules ...(
> including appletalk )
> when i start linux , the only modules i notice being started is
> appletalk , ipx ? how about the others ? how can i see what modules are
> started ?
As far as I see it modules are loaded at boot time (for check?)
than they are unloaded. So when you log on, there shouldn't be any
loaded. How can you see... try this:
# find / -name "*mod*" | grep "/man1/"
The above line will show you all the man pages that have a name
containing the string 'mod'. Of course not all are modules related ;-)
ex: chmod. But in case you don't know what the other commands do, than
checking them will be time well spent. In case you have procfs compiled
in than
# cat /proc/modules
will show you in a raw mode (no explanations) this. /proc/modules
is extremely useful if you want to make a script with inseting, removing
modules. Because it's easier to check a text file than to run a command.
And the absence of this file means there is no module support in that
kernel (monolithic kernel). Actually, it can prove itself a very good
idea to check the goodies under /proc.
Raider
--
``Liberate tu-temet ex inferis''
