Hi Andreas - I have checked my notes and this has been "an issue" going back to at least SuSE Linux (a fine German product) in 2006. So, it is not Voyage-linux specific, but maybe Debian related. Here is at least one good reason for this: suppose you have a server running in a data center and you need to add some more Ethernet ports. You have the DC people put in the card and turn the machine back on. It would be very bad if the port assignment algorithm decided to assign one of the new ports to eth0. That new port would likely not even be plugged into a switch port at boot time and you would have to use the serial console (if you have one) to sort out the mess.
However, I agree that your situation was frustrating, and I have experienced it myself. Jon On Sat, Nov 26, 2016 at 2:15 PM, Andreas Delleske <delle...@vauban.de> wrote: > Hi Jon, > > > I don't think that this is a bug. Those rules keep your Ethernet port > names > > consistent over time. In my cloning notes I have a step to delete the > > appropriate lines before moving the disk / CF card to a new system. > > Objection, your honour :) > > At least when we chose DHCP I guess everyone wants the device working > at a new place in a new hardware. It's not even possible to swap a > broken board this way. Everyone should know this at least, and I think > this behaviour had been different in previous versions of voyage > (which is fantastic BTW). > > So I think the installer could offer to add your modification.. > > And yes, I would have expected at least an eth1 popping up .. > > -- > Andreas > -- Jon T. Meek, Ph.D. https://linkedin.com/in/meekjt https://meekj.github.io
_______________________________________________ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
