Re: Enet names

2019-01-26 Thread David Wright
On Sat 26 Jan 2019 at 06:44:07 (-0500), rhkra...@gmail.com wrote: > On Saturday, January 26, 2019 06:18:59 AM Pascal Hambourg wrote: > > Network interfaces are not character nor block devices and do not have > > nodes in /dev. > > > > Reverting to the "natural" kernel names has issues : interface

Re: Enet names

2019-01-26 Thread tomas
On Sat, Jan 26, 2019 at 06:44:07AM -0500, rhkra...@gmail.com wrote: > On Saturday, January 26, 2019 06:18:59 AM Pascal Hambourg wrote: > > Network interfaces are not character nor block devices and do not have > > nodes in /dev. [...] > Hmm, from the peanut gallery (and, at this time in the

Re: Enet names

2019-01-26 Thread mick crane
On 2019-01-25 18:19, ghe wrote: Buster, computer with MAC identified Ethernet ports Is there a way to relabel Ethernet ports? Without changing things in a number of config files? I see on the web that changing udev used to do that, but now there are at least 2 files to modify. I'm gently

Re: Enet names

2019-01-26 Thread rhkramer
On Saturday, January 26, 2019 06:18:59 AM Pascal Hambourg wrote: > Network interfaces are not character nor block devices and do not have > nodes in /dev. > > Reverting to the "natural" kernel names has issues : interface names may > not be persistent and change across reboots. More details

Re: Enet names

2019-01-26 Thread Pascal Hambourg
Le 25/01/2019 à 19:19, ghe a écrit : Buster, computer with MAC identified Ethernet ports Is there a way to relabel Ethernet ports? Without changing things in a number of config files? Short answare : no. I'm gently moving to a new ISP, and I'm trying to set up new, virtual IP addresses on

Re: Enet names

2019-01-26 Thread Alexander V. Makartsev
On 26.01.2019 4:58, ghe wrote: > On 1/25/19 1:47 PM, Étienne Mollier wrote: > >> My apologies, on rereading I realize it is unclear that both >> assertions (modifying Grub entries or creating a systemd link) >> are two separate distinct solutions. > Very little prob. Doing vi /etc/default/grub, vi

Re: Enet names

2019-01-26 Thread deloptes
ghe wrote: > Futzing with systemd makes one wonder what MS has on some of the Linux > system programmers. :D

Re: Enet names

2019-01-25 Thread ghe
On 1/25/19 1:47 PM, Étienne Mollier wrote: > My apologies, on rereading I realize it is unclear that both > assertions (modifying Grub entries or creating a systemd link) > are two separate distinct solutions. Very little prob. Doing vi /etc/default/grub, vi /etc/network/interfaces, update-grub,

Re: Enet names

2019-01-25 Thread Étienne Mollier
On 1/25/19 9:29 PM, Étienne Mollier wrote: > If you are trying to say that you wish to go back to the ethN > network interface naming convention, then one way to do it is [...] > > > Now the interesting part, if you want to reliably identify your [...] My apologies, on rereading I realize it is

Re: Enet names

2019-01-25 Thread Étienne Mollier
Glenn English, onb 2019-01-25 : > Buster, computer with MAC identified Ethernet ports > > Is there a way to relabel Ethernet ports? Without changing things in a > number of config files? > > I see on the web that changing udev used to do that, but now there are > at least 2 files to modify. > >

Enet names

2019-01-25 Thread ghe
Buster, computer with MAC identified Ethernet ports Is there a way to relabel Ethernet ports? Without changing things in a number of config files? I see on the web that changing udev used to do that, but now there are at least 2 files to modify. I'm gently moving to a new ISP, and I'm trying to