Alan McKinnon wrote: > On 31/03/2013 20:26, Dale wrote: >> Nuno J. Silva (aka njsg) wrote: >>> On 2013-03-31, Dale <[email protected]> wrote: >>>> Pandu Poluan wrote: >>>>> >>>>> Since it's obvious that upsteam has this "my way or the highway" >>>>> mentality, I'm curious about whether eudev (and mdev) exhibits the >>>>> same behavior... >>>>> >>>> I synced yesterday and I didn't see the news alert. Last eudev update >>>> was in Feb. so I *guess* not. It seems to be a "udev" thing. That is >>>> why I mentioned eudev to someone else that was having this issue with a >>>> server setup. >>> I'd guess eudev will eventually do the same, although I hope that, it >>> being a separate codebase, makes it easier to adopt some solution like >>> the old rule generator, instead of using udev's approach. >>> >>> The udev upstream may have its issues, but there's actually a point in >>> removing this, the approach there was so far was just a dirty hack. >>> >> >> Thing is, it works for me. The old udev worked, > It's more accurate to say it worked by accident rather than by design. > (Sort of like how the power utility gets power to your house - if yours > is anything like mine I get power despite their best efforts to not give > me any ...) > > Anyway, the old method sucked and it sort of works for you and I because > we don't add anything ourselves that trip it up. But this new method... > geez lads, I just dunno. > > How do Windows, Mac and Android deal with this stuff? They don't seem to > have any device naming problems, so what is the magic solution in use on > those platforms? > >
Well, it still works regardless of by accident or by design. On the rare occasion that I have to reboot/shutdown, when my system comes up, I still have the same network connection(s) I had before. I still have net.eth0 like I have had since I built this rig. On my old rig, same thing and I added networks cards to it, more than once I might add. Everything was consistent until I disabled the on board nic since it went bad then it got interesting because I had to configure things to let the first network card be the internet connection instead of the on board old one. I'm pretty sure that regardless of what was managing devices that I would still have had to tell it which interface to use tho. I mean, it can't exactly read my mind. lol Point is, just like the /usr mess, it's working just fine. Odd thing is, udev folks said it couldn't be fixed but the eudev folks seemed to have fixed it just fine. It seems Walter found his own fix too. Sort of like a plumber telling me I have to put with the drip when another plumber can replace the o-ring and stop the drip. So much for the first plumber. I'll loose his number for sure. Only with this, two plumbers had a better plan. One replaced the o-ring, one replaced the whole faucet. Still got rid of the drip tho. I generally look more at the results than the how. I'm not a programmer, just a user. End result is what I look for. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
