| 1 |
Nuno J. Silva (aka njsg) wrote: |
| 2 |
> On 2013-03-31, Dale <rdalek1967@×××××.com> wrote: |
| 3 |
>> Pandu Poluan wrote: |
| 4 |
>>> |
| 5 |
>>> |
| 6 |
>>> Since it's obvious that upsteam has this "my way or the highway" |
| 7 |
>>> mentality, I'm curious about whether eudev (and mdev) exhibits the |
| 8 |
>>> same behavior... |
| 9 |
>>> |
| 10 |
>> I synced yesterday and I didn't see the news alert. Last eudev update |
| 11 |
>> was in Feb. so I *guess* not. It seems to be a "udev" thing. That is |
| 12 |
>> why I mentioned eudev to someone else that was having this issue with a |
| 13 |
>> server setup. |
| 14 |
> I'd guess eudev will eventually do the same, although I hope that, it |
| 15 |
> being a separate codebase, makes it easier to adopt some solution like |
| 16 |
> the old rule generator, instead of using udev's approach. |
| 17 |
> |
| 18 |
> The udev upstream may have its issues, but there's actually a point in |
| 19 |
> removing this, the approach there was so far was just a dirty hack. |
| 20 |
> |
| 21 |
|
| 22 |
|
| 23 |
Thing is, it works for me. The old udev worked, eudev works but I'm not |
| 24 |
sure what hoops I would have to go through to get the new udev working, |
| 25 |
most likely the same ones others here are going through now. For once, |
| 26 |
I'm not having to deal with some broken issue. < knock on wood > |
| 27 |
|
| 28 |
My current uptime is about 190 days. May hit it still but I'm certainly |
| 29 |
hoping I don't. |
| 30 |
|
| 31 |
Dale |
| 32 |
|
| 33 |
:-) :-) |
| 34 |
|
| 35 |
-- |
| 36 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
Archives