1 |
Thanks Rich. The picture is getting clearer and other than getting my |
2 |
backup SSD installation up to date it's good to know there's no |
3 |
difficult requirements for me to deal with at this time. Being that I |
4 |
have been (for the last 5-6 years anyway) a 'stable' Gentoo user it's |
5 |
to my advantage if things stay basically the same over time. |
6 |
|
7 |
After your and Canek's responses it's clear that within my framework I |
8 |
won't be moving to eudev or mdev. The only systemd question I might |
9 |
need to answer going forward is for my dad's machine. He's got 15 |
10 |
years of email traffic in Evolution and I've not investigated running |
11 |
Evolution in any desktop environment other than Gnome. There's no way |
12 |
at this point to move him away from Evolution so I just need to figure |
13 |
out over time (the next year maybe) how to best deal with that. |
14 |
|
15 |
Cheers, |
16 |
Mark |
17 |
|
18 |
On Sun, Mar 2, 2014 at 10:10 AM, Rich Freeman <rich0@g.o> wrote: |
19 |
> On Sun, Mar 2, 2014 at 11:57 AM, Mark Knecht <markknecht@×××××.com> wrote: |
20 |
>> In the last few days there is a news announcement about needing to |
21 |
>> change kernel my configuration to enable CONFIG_FHANDLE to support |
22 |
>> udev-210. I'm currently at udev-208 and virtual/udev-208-r1 so no big |
23 |
>> deal yet. However reading the news announcement it appears this has |
24 |
>> more to do with systemd than anything else and I don't use systemd so |
25 |
>> does/will this effect my machines? |
26 |
> |
27 |
> I'm going to avoid repeating Canek's points, which are basically |
28 |
> correct on the factual matters. |
29 |
> |
30 |
> However, I will clarify a little about why you probably think the news |
31 |
> has something to do with systemd. |
32 |
> |
33 |
> The big change in udev-210 is how persistent network device names are |
34 |
> implemented. The file that implements the rules is changing names, |
35 |
> which has an impact on your if you're trying to override it (your |
36 |
> override will no longer work if you don't change the name to follow |
37 |
> suit). Also, the new rule file now pulls in config settings from a |
38 |
> file that contains "systemd" in the filename. If you want to tweak |
39 |
> the persistent naming without disabling it entirely, it would make |
40 |
> sense to try to do so by editing that file, regardless of whether |
41 |
> you're using systemd. The file contains systemd in the name because |
42 |
> it is also used by systemd for network settings. So, you have udev (a |
43 |
> binary) loading a rule file (text) which loads a config file (text). |
44 |
> This is analogous to openrc running an init script which sources a |
45 |
> config file - editing the config file is preferable to editing the |
46 |
> script but nothing prevents you from doing either. |
47 |
> |
48 |
>> I think the Gentoo devs forked udev to make either mdev or eudev |
49 |
>> but when it was announced it was too new for me so I just let it go |
50 |
>> by. Maybe now it's time for me to look into making a change of some |
51 |
>> type? I see eudev in portage, but not mdev. |
52 |
> |
53 |
> Ok, just some definitions: |
54 |
> udev - the upstream project that you're familiar with - it has |
55 |
> recently merged with systemd, which has resulted in some changes that |
56 |
> some find objectionable (changes in install paths, incorporation of |
57 |
> systemd in file/path names, etc) |
58 |
> |
59 |
> eudev - a fork of udev that attempts to basically do the same thing as |
60 |
> udev, but preserving the paths/etc used in the project prior to the |
61 |
> systemd merge. |
62 |
> |
63 |
> mdev - shorthand for busybox mdev. This isn't a separate package. If |
64 |
> you have busybox installed you can use a function it supports which |
65 |
> will populate /dev based on detected devices, in a manner similar to |
66 |
> udev. It is much less functional that udev, but if you have a simple |
67 |
> system where you don't need hot-swap support and all the bells and |
68 |
> whistles, it will give you a /dev similar to what you probably would |
69 |
> find on most linux boxes 10 years ago. |
70 |
> |
71 |
>> A (really, really, really) quick scan of the current install docs |
72 |
>> makes me think sysvinit/OpenRC/udev is still the default for new |
73 |
>> installs. Is this true? If so why is this kernel change being |
74 |
>> required? |
75 |
> |
76 |
> Udev is changing upstream - presumably because the new kernel features |
77 |
> are helpful in some way. I haven't read the details. |
78 |
> |
79 |
>> Also, I seem to have virtual/udev installed which says it's about |
80 |
>> enabling switching between udev & eudev. However there are no files |
81 |
>> associated with virtual/udev. (equery files virtual/udev returns |
82 |
>> nothing) It appears I cannot install eudev without removing udev so |
83 |
>> this seems a big step to take: |
84 |
> |
85 |
> virtual/udev is a virtual package. Virtual packages are called |
86 |
> virtual because they don't install files. They exist for dependency |
87 |
> purposes - a package can depend on the virtual which lets you pick |
88 |
> whether you want to use udev or eudev or something else without lots |
89 |
> of things breaking. |
90 |
> |
91 |
> Eudev is a fork of udev and cannot co-exist with it. It would be like |
92 |
> installing mariadb and mysql on the same system, or openoffice and |
93 |
> libreoffice. So, if you want to install it portage will helpfully |
94 |
> suggest uninstalling udev. |
95 |
> |
96 |
> I won't tell you what you should be doing, but before you switch from |
97 |
> the defaults (openrc+udev+sysvinit) you should probably make sure you |
98 |
> understand what you're getting into. The upstream udev is certainly |
99 |
> what 99% of Linux users will be using in general for the foreseeable |
100 |
> future, though I can't really see you getting into trouble with eudev |
101 |
> or mdev (with many limitations on the latter). Migrating between them |
102 |
> isn't very hard at the moment, though if config files/etc start |
103 |
> diverging between eudev and udev that will make it harder to switch |
104 |
> (depending on how much you tweak on your system). |
105 |
> |
106 |
> Rich |
107 |
> |