I found the driver of my wireless network card is loaded right after the
system boots up. I checked the /etc/modules and not found that driver. I had
thought that driver is loaded automatically by discover, so I disabled the
/etc/rcS.d/S36discover, but the driver is still be loaded automatically
after booting up. That driver is not used by any other modules. Do any other
mechanisms exist that cause drivers loaded automatically? Thanks.

On Wed, Jul 02, 2008 at 03:39:38PM +0800, ray wrote:
> I found the driver of my wireless network card is loaded right after the
> system boots up. I checked the /etc/modules and not found that driver. I had
> thought that driver is loaded automatically by discover, so I disabled the
> /etc/rcS.d/S36discover, but the driver is still be loaded automatically
> after booting up. That driver is not used by any other modules. Do any other
> mechanisms exist that cause drivers loaded automatically? Thanks.

The package discover? I don't even have it installed. The kernel has
it's own detection mechanisms and loads modules as needed. If you don't
want to load some of them you need to use a blacklist.

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkhrOIoACgkQqJyztHCFm9ltbACfdTqKI5UZ6q DVKQhMoO099NW/
AKkAnjHHuxJJJ0lDkWR8Ux63boTJujrn
=6+Pc
-----END PGP SIGNATURE-----

Yes, the discover package. Now I see the discover package can be removed
from my system and maybe can make my system boot up a little more quick.
I would like to know the details of the kernel's own detection mechanism. Do
you know where can I find the documentation about it?
Thank for you reply.

On Wed, Jul 2, 2008 at 4:12 PM, Andrei Popescu <andreimpopescu@gmail.com>
wrote:

> On Wed, Jul 02, 2008 at 03:39:38PM +0800, ray wrote:
> > I found the driver of my wireless network card is loaded right after the
> > system boots up. I checked the /etc/modules and not found that driver. I
> had
> > thought that driver is loaded automatically by discover, so I disabled
> the
> > /etc/rcS.d/S36discover, but the driver is still be loaded automatically
> > after booting up. That driver is not used by any other modules. Do any
> other
> > mechanisms exist that cause drivers loaded automatically? Thanks.
>
> The package discover? I don't even have it installed. The kernel has
> it's own detection mechanisms and loads modules as needed. If you don't
> want to load some of them you need to use a blacklist.
>
> Regards,
> Andrei
> --
> If you can't explain it simply, you don't understand it well enough.
> (Albert Einstein)
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkhrOIoACgkQqJyztHCFm9ltbACfdTqKI5UZ6q DVKQhMoO099NW/
> AKkAnjHHuxJJJ0lDkWR8Ux63boTJujrn
> =6+Pc
> -----END PGP SIGNATURE-----
>
>

El mié, 02-07-2008 a las 16:57 +0800, ray escribió:
> Yes, the discover package. Now I see the discover package can be
> removed from my system and maybe can make my system boot up a little
> more quick.
> I would like to know the details of the kernel's own detection
> mechanism. Do you know where can I find the documentation about it?
> Thank for you reply.
>

The kernel-level system used is hotplug. It generates events on hardware
detection and then user-level applications take care of those events.
That user-level application is usually udev. Check man udev for more
info on configuring it.

Here are some introductory articles. For advanced info, STFW.
http://lwn.net/Articles/242046/
http://wiki.linuxquestions.org/wiki/Hotplug
http://wiki.linuxquestions.org/wiki/Udev

I'm not sure if the info is up-to-date, they were just sitting in my
bookmarks.


[...]
>
>
--
Gabriel Parrondo
GNU/Linux User #404138
GnuPG Public Key ID: BED7BF43
JID: gabrielp@xmpp.us

"The only difference between theory and practice is that, in theory,
there's no difference between theory and practice."

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: GnuPG digital signature

iD8DBQBIa21+IOmrXr7Xv0MRAgU4AKCeie6g8AWJVfZwaEC56F PLTYeIjwCffpee
wqvCkDrHdbPZSs03EVB+EWg=
=pXzs
-----END PGP SIGNATURE-----

I have checked the udev. But I thought udev is responsible for creating the
device files after the modules have been loaded. Am I wrong?

On Wed, Jul 2, 2008 at 7:58 PM, Gabriel Parrondo <g.parrondo@gmail.com>
wrote:

> El mié, 02-07-2008 a las 16:57 +0800, ray escribió:
> > Yes, the discover package. Now I see the discover package can be
> > removed from my system and maybe can make my system boot up a little
> > more quick.
> > I would like to know the details of the kernel's own detection
> > mechanism. Do you know where can I find the documentation about it?
> > Thank for you reply.
> >
>
> The kernel-level system used is hotplug. It generates events on hardware
> detection and then user-level applications take care of those events.
> That user-level application is usually udev. Check man udev for more
> info on configuring it.
>
> Here are some introductory articles. For advanced info, STFW.
> http://lwn.net/Articles/242046/
> http://wiki.linuxquestions.org/wiki/Hotplug
> http://wiki.linuxquestions.org/wiki/Udev
>
> I'm not sure if the info is up-to-date, they were just sitting in my
> bookmarks.
>
>
> [...]
> >
> >
> --
> Gabriel Parrondo
> GNU/Linux User #404138
> GnuPG Public Key ID: BED7BF43
> JID: gabrielp@xmpp.us
>
> "The only difference between theory and practice is that, in theory,
> there's no difference between theory and practice."
>

On Wed, Jul 02, 2008 at 03:39:38PM +0800, ray wrote:
> I found the driver of my wireless network card is loaded right after the
> system boots up. I checked the /etc/modules and not found that driver. I had
> thought that driver is loaded automatically by discover, so I disabled the
> /etc/rcS.d/S36discover, but the driver is still be loaded automatically
> after booting up. That driver is not used by any other modules. Do any other
> mechanisms exist that cause drivers loaded automatically? Thanks.

When is "right after the system is loaded"? Any chance that this is the
initrd?

Try adding the extra boot parameter init=/bin/sh at grub's prompt.

Then you get to a shell prompt right after the kernel has loaded and the
initrd was loaded and its scripts executed.

Try running from there:

/sbin/lsmod

To resume normal boot:

exec /sbin/init

--
Tzafrir Cohen | tzafrir@jabber.org | VIM is
http://tzafrir.org.il | | a Mutt's
tzafrir@cohens.org.il | | best
ICQ# 16849754 | | friend


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org