Re: systemd: some more questions
Brian writes:
> On Fri 14 Feb 2014 at 14:11:30 +0100, Gian Uberto Lauri wrote:
>
> > Ralf Mardorf writes:
> >
> > > During setting up Arch Linux with systemd the device name switched from
> > > eth0 to enp3s0 on my machine.
> >
> > Any reason for this?
>
> http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Interesting. But may I ask a full identification (manufacturer, model
at least) of an system that showed the problem of having the
interfaces have not a stable name between reboots? I am _really_
curious to know of one of them.
The ONLY time I have seen this was with a template VM. Each new vm
started from the base image had a different "hardware identification"
(MAC? - it was some years ago, can't remember the full details). that
changed eth0 to eth1, eth2... A quick fix to the udev scripts removed
the problem.
> > This could create "a certain amount of work" to people used to
> > automate things by means of shell scripts...
>
> After reading "I don't like this, how do I disable this?" very little
> work appears to be involved.
Hey, /etc/udev/rules.d/80-net-name-slot.rules seems the udev file I
worked on.
This does not change the amount of work in Miles forecasts, just
changes it.
--
ing. Gian Uberto Lauri
Solution Developer Senior
Direzione Ricerca e Innovazione
GianUberto.Lauri@eng.it
Sun Java Certified Programmer
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.517 | main(){printf(&unix["\021%six\012\0"],
Fax +39-049.8283.569 | (unix)["have"]+"fun"-0x60);}
http://www.eng.it | David Korn, AT&T Bell Labs
| ioccc best One Liner, 1987
Reply to: