1 |
Richard Fish posted |
2 |
<7573e9640604032014p7dbd2358raa41f90c21097021@××××××××××.com>, excerpted |
3 |
below, on Mon, 03 Apr 2006 20:14:43 -0700: |
4 |
|
5 |
> On 4/3/06, Jack Cuyler <jjvcuyler@×××××××××××××××.com> wrote: |
6 |
>> When booting, I get an error message that "find_free_number" doesn't |
7 |
>> work, will be removed, and shouldn't be used. I've googled, but the |
8 |
>> best I can find is something on a debian list to the effect of, "Yes, |
9 |
>> that's right. Don't use it." |
10 |
>> |
11 |
>> My question is, how do I disable it? |
12 |
> |
13 |
> Check /etc/udev/rules.d/*. If you have any rules with "%e" in them, you |
14 |
> will get this warning. Although, I see the cdrom rules in 50-udev.rules |
15 |
> is still using %e, so I'm personally waiting to see what replaces this |
16 |
> before I fix my rules... |
17 |
|
18 |
Interesting this should come up, as I was getting tired enough of the |
19 |
message myself to just be getting ready to go looking. Having not done so |
20 |
yet, the above confirms what I suspected, and I yet believe the following |
21 |
is safe to say... |
22 |
|
23 |
Greg KH, one of the guys on the Gentoo kernel team and the one that makes |
24 |
the most changes to our udev, according to the changelog, is one of two or |
25 |
three that were responsible for udev in the first place. He's no longer |
26 |
responsible for it upstream, as he has enough other stuff on his plate |
27 |
that likely didn't fit so well, but as the biggest proponent of udev (he's |
28 |
had several white papers and speeches on it, look it up) and one of the |
29 |
original three, it's safe to say he knows it inside and out and pretty |
30 |
well keeps up with upstream. |
31 |
|
32 |
Additionally, GKH is kernel lieutenant for device drivers -- /that's/ the |
33 |
big thing on his plate and a driving force behind the udev thing in the |
34 |
first place, for him. It's safe to say as a result of that he continues |
35 |
to cooperate very closely with the udev upstream, and they with him -- |
36 |
closely as in on a close to daily basis, or things will break as the |
37 |
kernel and udev will get out of sync. |
38 |
|
39 |
Finally, in addition to the volunteer hats he wears with Gentoo and as the |
40 |
mainline kernel drivers lieutenant, his paying job is I believe doing the |
41 |
/same/ things for Novell/SuSE. |
42 |
|
43 |
Suffice it to say that it's rather unlikely we'll be left high and dry |
44 |
with a udev implementation that doesn't work, unless you've modified your |
45 |
rules significantly beyond the default. That's the reason those warnings |
46 |
haven't been an urgent investigative matter, here. If something does get |
47 |
broken, it's going to be only for a very short period and as the result of |
48 |
normal development snafus. You'll only likely see it if you happen to |
49 |
sync in the period of hours that it's broken before it's caught, and |
50 |
happen to reboot then too. Even then, chances are it'll be something |
51 |
non-critical that breaks, something like CD/DVDs (in this case), that |
52 |
aren't necessary for maintenance mode. (Of course, if you have to boot |
53 |
your liveCD or whatever backup, you'll be using the old and well tested |
54 |
setup on the liveCD itself, not bleeding edge one that happened to break |
55 |
for a few hours, and you had the bad enough luck to catch the sync at |
56 |
exactly the wrong time.) |
57 |
|
58 |
The warnings are just that -- warnings of deprecation. No new use of the |
59 |
warned feature should be made, as the feature is deprecated. However, |
60 |
the process of deprecation is there precisely to allow some changeover |
61 |
time, so the system is working as it's supposed to. As long as you've not |
62 |
made your own customizations using that feature and as long as you |
63 |
properly etc-update after your udev upgrades, before rebooting, and as |
64 |
long as you always keep at least one known working kernel when you |
65 |
upgrade that (testing the new one before entirely removing the old |
66 |
one), you should be fine, barring the occasional routine breakage that |
67 |
should be expected running ~arch, if that's indeed what you /are/ |
68 |
running. (I don't believe stable would have the warning yet, but I may be |
69 |
wrong.) |
70 |
|
71 |
-- |
72 |
Duncan - List replies preferred. No HTML msgs. |
73 |
"Every nonfree program has a lord, a master -- |
74 |
and if you use the program, he is your master." Richard Stallman in |
75 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
76 |
|
77 |
|
78 |
-- |
79 |
gentoo-amd64@g.o mailing list |