----- Original Message -----
> From: "Rainer Weikusat" <rainerweikusat@???>
> Didier Kryn <kryn@???> writes:
>> Ethernet interfaces are maybe the only issue, which explains why
>> distros have implemented a solution by the means of udev rules. The
>> way it is implemented is secure: every new ethernet device is given a
>> new device name (ethX) and no entry is created in
>> /etc/network/interfaces; therefore the interface isn't connected
>> without an action of the admin. If it is a replacement, then the admin
>> should just edit the MAC address in
>> /etc/udev/rules.d/70-persistent-net.rules. Not a big deal, compared to
>> replacing the hardware.
>
> As I already wrote: A file
>
> /etc/udev/rules.d/75-persistent-net-generator.rules
>
> can be created (on Debian up to wheezy at least) to avoid this "install
> the system to new hardware and get a whole bunch of new ethN instead of
> the onese which aren't available anymore" mess altogether.
And if you forgot to create /etc/udev/rules.d/75-persistent-net-generator.rules
and have rebooted with your new network card installed, you may have another
option. If you only have a single network card, just delete
/etc/udev/rules.d/70-persistent-net.rules and reboot. It will be re-created
with your single network card defined as eth0.
-Rob
::
Re: [DNG] Purpose of an OS: was net…
