1 |
On Wed, Jul 21, 2004 at 06:34:21AM -0400, Travis Tilley wrote: |
2 |
> On Wednesday 21 July 2004 03:24 am, Travis Tilley wrote: |
3 |
> > On Wednesday 21 July 2004 01:28 am, Greg KH wrote: |
4 |
> > > On Sun, Jul 18, 2004 at 06:53:29PM -0400, Travis Tilley wrote: |
5 |
> > > If you have _any_ issues with udev, please let the developers and the |
6 |
> > > linux-hotplug-devel mailing list know about it. Otherwise it will not |
7 |
> > > get fixed, and you will never be happy. |
8 |
> > |
9 |
> > just dont -force- udev on me and i'll be happy. |
10 |
> > |
11 |
> > > Oh, and that reminds me to go make up a "delete devfs" kernel patch to |
12 |
> > > send off to lkml, just to force the issue :) |
13 |
> > |
14 |
> > heh. |
15 |
> |
16 |
> ok, trying to be just a bit more constructive. :) |
17 |
> |
18 |
> 1) udev is either ready or it isnt. |
19 |
|
20 |
No. udev is ready. It's the fact that the kernel might not be fully |
21 |
ready, depending on the devices you use. |
22 |
|
23 |
> the fact that you need to use a device |
24 |
> tarball for entries udev doesnt support shows me that it isnt ready. |
25 |
|
26 |
No, there is no way to support devices that don't have sysfs support. |
27 |
For some of them (like 3rd party drivers), that will never happen. |
28 |
|
29 |
> what's |
30 |
> the point of using a device management system if you're going to just dump a |
31 |
> bunch of extra dev entries in there anyway? if udev were ready, this wouldnt |
32 |
> be necessary. |
33 |
|
34 |
Great, I challenge you to fix this :) |
35 |
Or at least file bugs for it... |
36 |
|
37 |
But for me, and all of my machines, that tarball isn't needed at all. |
38 |
And for 95% of the world, it should work. It's that last 5% that is |
39 |
going to take some kernel work to fix, due to the scarcity of the |
40 |
hardware being used. |
41 |
|
42 |
> 2) |
43 |
> ayanami portcvs # ldd `which udevd` |
44 |
> libc.so.6 => /lib/libc.so.6 (0x0000002a9566d000) |
45 |
> /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 |
46 |
> (0x0000002a95556000) |
47 |
> ayanami portcvs # emerge udev -pv | grep static |
48 |
|
49 |
udev can be built with the included klibc library, which makes this |
50 |
whole issue moot. I've been hesitant to change the ebuild to do this, |
51 |
due to ia64 issues with klibc. Hopefully the next version of klibc (and |
52 |
hence udev) should fix this. Then I'll enable it for everyone. |
53 |
|
54 |
And, yes, I agree that this is an issue, that's why klibc is there :) |
55 |
|
56 |
> 3) devfs isnt going away any time soon, and there will be people like me who |
57 |
> dont think it's a good idea to risk bugs for no apparent benefit. |
58 |
|
59 |
devfs is broken, has known bugs, is unmaintained, and has security |
60 |
issues. What more do you want? |
61 |
|
62 |
Oh, and it will go away soon, see my lkml post. |
63 |
|
64 |
> 4) it makes sense to keep supporting devfs even after it's ripped out of the |
65 |
> kernel, which i think isnt until after the /next/ stable kernel series. |
66 |
|
67 |
The idea of a development/stable kernel series has just changed. See |
68 |
the lwn.net writeup of the kernel summit for more information about |
69 |
this. |
70 |
|
71 |
> bah, i've been suckered into installing udev... so i might as well keep it |
72 |
> until something breaks. i disabled the tarball hack since it was making /dev |
73 |
> ugly and cluttered... though i admit it seems to be more ready than i thought |
74 |
> it was. at least for now i can have both and always make devfs mount on |
75 |
> boot... please dont think seriously about removing support for that. at least |
76 |
> not until after we all move over to 2.10 anyways. :/ |
77 |
|
78 |
Good, glad it's working for you :) |
79 |
|
80 |
thanks, |
81 |
|
82 |
greg k-h |
83 |
|
84 |
-- |
85 |
gentoo-dev@g.o mailing list |