Consistent names changed yet again?

[Michael Hennebry]

Would someone explain this to me:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
wrote:
> For a longer time udev shipped support for assigning permanent "ethX"
> names to certain interfaces based on their MAC addresses.
> This turned out to have a multitude of problems, among them:
> this required a writable root directory which is generally not available;

Huh?  Why would that require a writeable root directory?

> the statelessness of the system is lost as booting an OS image on a
> system will result in changed configuration of the image;
> on many systems MAC addresses are not actually fixed,
> such as on a lot of embedded hardware and particularly

How do MAC addresses get changed on embedded systems?

> on all kinds of virtualization solutions.

My guess is that virtualization could screw up any scheme,
including the current system.
Does rebooting a virtual machine have to change MAC addresses?

On a machine with just one network interface,
is there any reason not to call it eth0, fred or whatever the user wants?

-- 
Michael   hennebry at web.cs.ndsu.NoDak.edu
"SCSI is NOT magic. There are *fundamental technical
reasons* why it is necessary to sacrifice a young
goat to your SCSI chain now and then."   --   John Woods