1 |
Apparently, though unproven, at 17:54 on Wednesday 05 January 2011, Peter |
2 |
Humphrey did opine thusly: |
3 |
|
4 |
> On Wednesday 05 January 2011 15:32:29 Alan McKinnon wrote: |
5 |
> > Now we need to figure out *why* it was causing your problems |
6 |
> |
7 |
> I could just hand it over to the devs via a bug report, but I ought to |
8 |
> do some detective work first, if only to decide which subsystem to log it |
9 |
> against. |
10 |
|
11 |
I think the system worked by design and the bug is in your config i.e you had |
12 |
a not particularly valid one by any reasonable definition of valid: |
13 |
|
14 |
# rc_hotplug is a list of services that we allow to be hotplugged. |
15 |
# By default we do not allow hotplugging. |
16 |
# A hotplugged service is one started by a dynamic dev manager when a matching |
17 |
# hardware device is found. |
18 |
# This service is intrinsically included in the boot runlevel. |
19 |
# To disable services, prefix with a ! |
20 |
# Example - rc_hotplug="net.wlan !net.*" |
21 |
# This allows net.wlan and any service not matching net.* to be plugged. |
22 |
# Example - rc_hotplug="*" |
23 |
# This allows all services to be hotplugged |
24 |
#rc_hotplug="*" |
25 |
|
26 |
Setting it to "!*" implies that the dev manager will do nothing. I imagine |
27 |
that if you have nvidia hardware and drivers, then you *do* want the kernel to |
28 |
find it and do the right thing for that hardware. This is a case where you |
29 |
must be pedantic about letting the kernel create only those things it needs to |
30 |
create, nothing more and nothing less. You cannot possibly improve on the |
31 |
kernel's own knowledge of the hardware :-) |
32 |
|
33 |
> |
34 |
> The trouble with that idea is that it implies that I must think. Not |
35 |
> altogether a good idea. ;-( |
36 |
|
37 |
Ooh dear. |
38 |
|
39 |
Sleeping dogs lying and all that, hey? |
40 |
|
41 |
;-) |
42 |
|
43 |
|
44 |
-- |
45 |
alan dot mckinnon at gmail dot com |