XPost: comp.os.linux.development.system
In comp.os.linux.development.system Nate Eldredge wrote:
| phil-news-nospam@ipal.net writes:
|
|> In comp.os.linux.development.system J.O. Aho wrote:
|> | phil-news-nospam@ipal.net wrote:
|> |
|> |> | There is no automatically detection of your hardware and selection of
|> |> | modules/build in drivers, you can either use the default configuration
which
|> |> | will be like any other kernel you get with a all the binary
distributions, a
|> |> | kernel that has drivers for things you don't have.
|> |>
|> |> But the drivers are not all loaded. That's what a modular kernel is for,
|> |> so you don't have to load everything.
|> |
|> | There is no point in loading SATA drivers if you only have a Via MPV4
chipset
|> | which hardly do support ATA66. So no point in loading all the stuff you
don't
|> | need.
|>
|> Right. If you don't have device FOO you don't need driver FOO.
|
| What if device FOO is some sort of removable hardware that happens not
| to be installed right now, but which you intend to use regularly? Most
| USB devices would fall in this category. You can't even insist that
| someone install those devices before doing your autoconfiguration;
| perhaps I have a USB flash disk, scanner, cell phone, and printer, but
| only one USB port and no hub.
Good point. So maybe the BSDs is where I need to look to see what the do (in
general, since it won't be directly usable on Linux). I wonder what they do
for USB devices.
--
|WARNING: Due to extreme spam, googlegroups.com is blocked. Due to ignorance |
| by the abuse department, bellsouth.net is blocked. If you post to |
| Usenet from these places, find another Usenet provider ASAP. |
| Phil Howard KA9WGN (email for humans: first name in lower case at ipal.net) |
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
