1 |
On Mon, Mar 3, 2014 at 11:15 AM, Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
2 |
> On 3/2/2014 1:10 PM, Rich Freeman <rich0@g.o> wrote: |
3 |
>> The big change in udev-210 is how persistent network device names are |
4 |
>> implemented. The file that implements the rules is changing names, |
5 |
>> which has an impact on your if you're trying to override it (your |
6 |
>> override will no longer work if you don't change the name to follow |
7 |
>> suit). Also, the new rule file now pulls in config settings from a |
8 |
>> file that contains "systemd" in the filename. |
9 |
> |
10 |
> <snip> |
11 |
> |
12 |
>> The file contains systemd in the name because it is also used by |
13 |
>> systemd for network settings. |
14 |
> |
15 |
> Well... !?@?#?$?% |
16 |
> |
17 |
> Here we go again. Talk about 'a driving force to subsume everything it |
18 |
> touches'!? |
19 |
|
20 |
The networkd simple network manager is a new development in systemd, |
21 |
not udev. They saw that both could share some configs, so they used |
22 |
the directory under /etc that the whole project (systemd) uses. That's |
23 |
all. |
24 |
|
25 |
> So, "we use some files, so we change the name of every file we use to have |
26 |
> our name in it?" |
27 |
|
28 |
They *added* new configuration options, and udev (as part of the |
29 |
systemd project) *followed through*. |
30 |
|
31 |
> In other words... why stop at that one file? |
32 |
> |
33 |
> How much sense does *that* make? Seriously, that *really* irks me... |
34 |
|
35 |
All the sense in the world, if you actually read the code and see how |
36 |
the new networkd works. |
37 |
|
38 |
> I think I'll go and Prepend 'Charles-' to the name of every document I've |
39 |
> ever created... can anyone say 'egotistical'? |
40 |
|
41 |
The project (like it or not) is called systemd. They are using the |
42 |
/etc/systemd directory for configuration (as per long Unix tradition). |
43 |
They haven't moved /etc/udev to /etc/systemd/udev for backwards |
44 |
compatibility, but they could do it, and I think they *will* do it at |
45 |
some point in the future. Again, nothing will change for udev, only |
46 |
your machine will have a (*GASP!*) systemd directory somewhere. |
47 |
|
48 |
>> Ok, just some definitions: |
49 |
>> udev - the upstream project that you're familiar with - it has |
50 |
>> recently merged with systemd, which has resulted in some changes that |
51 |
>> some find objectionable (changes in install paths, incorporation of |
52 |
>> systemd in file/path names, etc) |
53 |
> |
54 |
> This is I think the crux of the problem. |
55 |
> |
56 |
> Why did udev *merge* with systemd, if there is no long term goal of |
57 |
> completely and totally subsuming it such that you cannot use udev without |
58 |
> also using systemd? |
59 |
|
60 |
This is FUD, Tanstaafl; they have promised that udev will be able to |
61 |
work independently from systemd, and they have kept their promise. |
62 |
They merged the two projects to share code (which they do) and because |
63 |
systemd wants to be the basic plumbing of Linux; udev is obviously |
64 |
needed for that. |
65 |
|
66 |
But udev works without systemd, and it will continue to do so. The |
67 |
*only* change is that now udev can use (not sure if it's mandatory) |
68 |
some configuration files from /etc/systemd/network. Yo don't *need* |
69 |
systemd to get udev working, and if you feel that a |
70 |
/etc/systemd/network directory is going to give you the systemd |
71 |
cooties, I personally think that's incredible obsessive. It's just a |
72 |
directory *name*; it doesn't even contains executable code. |
73 |
|
74 |
You can do the job (a simple sed before compilation is enough) to |
75 |
exorcise the systemd name from all udev related files, but it's (IMHO) |
76 |
idiotic. The project *is* systemd, like it or not; but it's Free |
77 |
Software, go nuts and change all the "systemd" strings for "Charles" |
78 |
if you so desire (I think a dev is doing that in an overlay). |
79 |
|
80 |
> Imnsho, since it is a KERNEL thingie, it should have been maintained as a |
81 |
> totally separate package, or just admit the long term goal and be done with |
82 |
> it. |
83 |
|
84 |
There is a kernel component and a userpace component for udev; they |
85 |
are separated in the kernel and the systemd project. Also, the long |
86 |
term goal is clear from the very beginning: systemd wants to be the |
87 |
basic plumbing in Linux. That is orthogonal to having udev working |
88 |
without systemd, and they have promised to support that, and it still |
89 |
works that way and there is no sign whatsoever that it's going to |
90 |
change. |
91 |
|
92 |
If you get offended by a /etc/systemd/network directory, I think you |
93 |
have more important issues, and they are unrelated to systemd/udev. |
94 |
|
95 |
>> Udev is changing upstream - presumably because the new kernel features |
96 |
>> are helpful in some way. I haven't read the details. |
97 |
> |
98 |
> Now I'd really, really, REALLY like to hear what Linus thinks about |
99 |
> systemd/udev NOW. The only things I can find from him are 4 or so years old. |
100 |
> I can't imagine that stuff like this doesn't irk him too... |
101 |
|
102 |
I don't think Linus opinion matters at all; people wanting to write |
103 |
and use some free software projects will continue to do so |
104 |
independently of what Linus, RMS, ESR, or the Flying Spaghetti Monster |
105 |
says. Having said that, I would not be surprised if Linus actually |
106 |
likes the idea of an standardized Linux plumbing, even if he dislikes |
107 |
some particular implementation details, or its authors. |
108 |
|
109 |
> Would someone who stands a chance at getting a response out of him *please* |
110 |
> ping him for an opinion on this stuff? Blog or LKML post would be fine... |
111 |
|
112 |
It would be interesting to know what he thinks; but either way it |
113 |
doesn't really matters, like it didn't really mattered when he stopped |
114 |
using GNOME, nor when he started using it again. Few users, if any, |
115 |
stopped or started using GNOME because of that. |
116 |
|
117 |
Regards. |
118 |
-- |
119 |
Canek Peláez Valdés |
120 |
Posgrado en Ciencia e Ingeniería de la Computación |
121 |
Universidad Nacional Autónoma de México |