dep stands for dependencies. It just sorta maps out what needs what...
similar to the modules.dep file in the installed modules directory
On Wed, 31 Jan 2001, Peter Peltonen wrote:
> "Michael R. Jinks" wrote:
> >
> > I think you have to do a 'make dep' first.
> >
> > Something that I think I've done before: after the dep, cd to the dir.
> > where the module's code lives and just type 'make' there. Should make a
> > module. Then copy to the appropriate place in your /lib/modules/`uname
> > -r`/ directory.
>
> Thanks! This was the tip I was looking for...
>
> Umm, about that 'make dep', what does it actually do?
>
> Somewhere I read I should always do 'make dep' after modifying modules.conf
> and from that I thought that it would check if I have the modules listed there
> loaded, but no. I had to reboot my machine to get the modules in modules.conf
> to be loaded (or use insmod).
>
> Peter
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
--
-Statux
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
