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