>>>>> Marco d'Itri <m...@linux.it> writes:
>>>>> On Oct 24, Ivan Shmakov <i...@gray.siamics.net> wrote:
>> So, the kernel won't try to autoload a module when the corresponding
>> device gets accessed?
> Not for *hardware* drivers, since it cannot know which driver is
> needed.
Not even via modprobe.conf(5)?
>> I've never heard of that (and Googling for “linux equiv” doesn't
>> seem to return anything relevant to the problem.) What's it?
> I meant equivs.
Somehow, I've totally missed this one. Which, indeed, I've a
plenty uses for. Thanks!
> Anyway, I think that if you want to learn how udev works then you
> should send your questions to an users support mailing
> list/newsgroup/forum/etc.
Well, seems like there're little specific to Debian in how udev
works. Thanks.
--
FSF associate member #7257
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/8639eipe2m....@gray.siamics.net
