1 |
On 2013-04-04 5:13 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> I gets so bad that people are starting to make shit up to be worried |
3 |
> about, instead of just reading the simple document that is right in |
4 |
> front of their eyes that already fully and completely answers the |
5 |
> question at hand.... |
6 |
|
7 |
But Alan, haven't you read the recent (past couple of DAYS) emails in |
8 |
this very thread from people who followed the current 'simple document' |
9 |
you refer to and it did not work as advertised? I don't think these |
10 |
people are making this stuff up - are you saying you do? |
11 |
|
12 |
Not to mention the fact that this final/current seemingly complete |
13 |
document was way, way too late for the many people who ended up with |
14 |
totally broken systems, and *that* is what caused all of the 'hysteria |
15 |
and mob-think' you so condescendingly speak of. |
16 |
|
17 |
It is these reports that is causing me all kinds of fear/trepidation at |
18 |
this seemingly simple/benign update (as you seem to believe it is). |
19 |
|
20 |
So, again, I would really, really like a very simple answer as to the |
21 |
*best* way to retain the old way that is least likely to cause problems |
22 |
down the road (ie, if/when udev is subsumed by systemd). Currently I |
23 |
count 3 different ways. |
24 |
|
25 |
Or, as an alternative, *how* to switch to eudev (their web page does |
26 |
*not* have simple/precise instructions on how to switch, only a |
27 |
description of what it is) - ie, do I just emerge -C udev && emerge -C |
28 |
virtual/udev && emerge eudev? Or is there more to it? |