[opensuse] Re: new network interfaqce naming scheme (result of systemd & initrd)

Hans Witvliet wrote:

From: Chuck Payne Are we going to the BSD style of naming? [... by driver name?] -----Original Message---- Absolutely horrible. It will break god-knows how many scripts.

It's worse than this.. it's going to the windows style of naming things by its hardware address... bustype-busnumber,slot,unit#... ... all that stuff that's in the windows registry and windows realized users didn't want to see.. so they give users stable name in the UI....but not w/systemd HW-addresses only! Which is a horrible choice for portability and maintenance... they try to claim it's good if you slip in a new card into the same slot. But more often, I add new cards and they are in different slots!... I repurpose the old .. but I don't want to have to change over all my scripts (fW, traffic flow/ management...etc)...That's just being evil to system admins (not to mention users)...

If they need to give the interfaces some other name, that is already bad enough. But keep all ethernet interfaces the same name!!!!!!!!

They are whining about not having access to a permanent storage to store the mappings in (like the: /etc/udev/rules.d/70-persistent-net.rules,

...

...

hard disk... <<<

THis is all related to booting from a ***ramdisk** -- no permanent storage... this brought this problem, so their fix is to do away with user allowed interfaces... Um, no one out there interested in pushing direct boot from hard disks as being required boot option? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org