Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #210356 > unrolled thread
| Started by | Hans <hans.ullrich@loop.de> |
|---|---|
| First post | 2019-06-25 10:10 +0200 |
| Last post | 2019-06-25 22:30 +0200 |
| Articles | 5 on this page of 45 — 16 participants |
Back to article view | Back to linux.debian.user
New nomeclature of ethernet devices Hans <hans.ullrich@loop.de> - 2019-06-25 10:10 +0200
Re: New nomeclature of ethernet devices <tomas@tuxteam.de> - 2019-06-25 10:50 +0200
Re: New nomeclature of ethernet devices Hans <hans.ullrich@loop.de> - 2019-06-25 11:10 +0200
Re: New nomeclature of ethernet devices Michael Stone <mstone@debian.org> - 2019-06-25 14:20 +0200
Re: New nomeclature of ethernet devices The Wanderer <wanderer@fastmail.fm> - 2019-06-25 14:50 +0200
Re: New nomeclature of ethernet devices Greg Wooledge <wooledg@eeg.ccf.org> - 2019-06-25 15:10 +0200
Re: New nomeclature of ethernet devices Michael Stone <mstone@debian.org> - 2019-06-25 15:40 +0200
Re: New nomeclature of ethernet devices Greg Wooledge <wooledg@eeg.ccf.org> - 2019-06-25 15:50 +0200
Re: New nomeclature of ethernet devices Michael Stone <mstone@debian.org> - 2019-06-25 15:30 +0200
Re: New nomeclature of ethernet devices Dan Purgert <dan@djph.net> - 2019-06-25 16:10 +0200
Re: New nomeclature of ethernet devices Michael Stone <mstone@debian.org> - 2019-06-25 17:10 +0200
Re: New nomeclature of ethernet devices Nate Bargmann <n0nb@n0nb.us> - 2019-06-25 17:40 +0200
Re: New nomeclature of ethernet devices Nate Bargmann <n0nb@n0nb.us> - 2019-06-25 17:40 +0200
Re: New nomeclature of ethernet devices Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-06-26 01:10 +0200
Re: New nomeclature of ethernet devices The Wanderer <wanderer@fastmail.fm> - 2019-06-26 02:00 +0200
Re: New nomeclature of ethernet devices Richard Owlett <rowlett@cloud85.net> - 2019-06-26 12:40 +0200
Re: New nomeclature of ethernet devices Dan Purgert <dan@djph.net> - 2019-06-26 12:40 +0200
Re: New nomeclature of ethernet devices Greg Wooledge <wooledg@eeg.ccf.org> - 2019-06-26 14:20 +0200
Re: New nomeclature of ethernet devices Stefan Monnier <monnier@iro.umontreal.ca> - 2019-06-26 16:10 +0200
Re: New nomeclature of ethernet devices Reco <recoverym4n@enotuniq.net> - 2019-06-26 16:40 +0200
Re: New nomeclature of ethernet devices Michael Stone <mstone@debian.org> - 2019-06-26 21:00 +0200
Re: New nomeclature of ethernet devices The Wanderer <wanderer@fastmail.fm> - 2019-06-27 02:10 +0200
Re: New nomeclature of ethernet devices Michael Stone <mstone@debian.org> - 2019-06-27 13:40 +0200
Re: New nomeclature of ethernet devices David Wright <deblis@lionunicorn.co.uk> - 2019-06-27 04:30 +0200
Re: New nomeclature of ethernet devices Ric Moore <wayward4now@gmail.com> - 2019-06-27 09:00 +0200
Re: New nomeclature of ethernet devices David Wright <deblis@lionunicorn.co.uk> - 2019-06-27 16:10 +0200
Re: New nomeclature of ethernet devices "Martin S. Weber" <Ephaeton@gmx.net> - 2019-06-25 20:30 +0200
Re: New nomeclature of ethernet devices Michael Stone <mstone@debian.org> - 2019-06-25 21:00 +0200
Re: New nomeclature of ethernet devices David Wright <deblis@lionunicorn.co.uk> - 2019-06-25 20:10 +0200
Re: New nomeclature of ethernet devices Greg Wooledge <wooledg@eeg.ccf.org> - 2019-06-25 20:30 +0200
Re: New nomeclature of ethernet devices Richard Owlett <rowlett@cloud85.net> - 2019-06-25 12:10 +0200
Re: New nomeclature of ethernet devices <tomas@tuxteam.de> - 2019-06-25 12:20 +0200
Re: New nomeclature of ethernet devices Hans <hans.ullrich@loop.de> - 2019-06-25 13:00 +0200
Re: New nomeclature of ethernet devices <tomas@tuxteam.de> - 2019-06-25 13:20 +0200
Re: New nomeclature of ethernet devices Hans <hans.ullrich@loop.de> - 2019-06-25 13:40 +0200
Re: New nomeclature of ethernet devices <tomas@tuxteam.de> - 2019-06-25 13:50 +0200
Re: New nomeclature of ethernet devices Curt <curty@free.fr> - 2019-06-25 14:20 +0200
Re: New nomeclature of ethernet devices Celejar <celejar@gmail.com> - 2019-06-26 00:10 +0200
Re: New nomeclature of ethernet devices The Wanderer <wanderer@fastmail.fm> - 2019-06-26 01:40 +0200
Re: New nomeclature of ethernet devices Celejar <celejar@gmail.com> - 2019-06-26 01:50 +0200
Re: New nomeclature of ethernet devices Stefan Monnier <monnier@iro.umontreal.ca> - 2019-06-25 18:10 +0200
Re: New nomeclature of ethernet devices David Wright <deblis@lionunicorn.co.uk> - 2019-06-25 18:30 +0200
Re: New nomeclature of ethernet devices Michael Stone <mstone@debian.org> - 2019-06-25 18:30 +0200
Re: New nomeclature of ethernet devices Stefan Monnier <monnier@iro.umontreal.ca> - 2019-06-25 22:30 +0200
Re: New nomeclature of ethernet devices Michael Stone <mstone@debian.org> - 2019-06-25 22:30 +0200
Page 3 of 3 — ← Prev page 1 2 [3]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2019-06-25 18:10 +0200 |
| Message-ID | <ycWb8-2ol-5@gated-at.bofh.it> |
| In reply to | #210360 |
> For good description of the problem (unpredictable names) and the logic
> behind the chosen solution:
>> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
The one thing I can't understand is why we still don't have "network
interface aliases" (equivalent to symlinks), so that systemd can name my
interface enp2s0 *and* eth0 instead of having to choose between those
two, just like it has no problem naming my SSD /dev/sda and
/dev/disk/by-id/ata-FOOBAR (and a bunch of other names as well).
Stefan
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2019-06-25 18:30 +0200 |
| Message-ID | <ycWuu-2uM-7@gated-at.bofh.it> |
| In reply to | #210381 |
On Tue 25 Jun 2019 at 12:01:31 (-0400), Stefan Monnier wrote: > > For good description of the problem (unpredictable names) and the logic > > behind the chosen solution: > >> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ > > The one thing I can't understand is why we still don't have "network > interface aliases" (equivalent to symlinks), so that systemd can name my > interface enp2s0 *and* eth0 instead of having to choose between those > two, just like it has no problem naming my SSD /dev/sda and > /dev/disk/by-id/ata-FOOBAR (and a bunch of other names as well). Because disks are mounted into the unix filesystem, which understands links, whereas interfaces are not special files. I would imagine the kernel is going to have to be persuaded to support this sort of alias. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2019-06-25 18:30 +0200 |
| Message-ID | <ycWuu-2uM-9@gated-at.bofh.it> |
| In reply to | #210381 |
On Tue, Jun 25, 2019 at 12:01:31PM -0400, Stefan Monnier wrote: >> For good description of the problem (unpredictable names) and the logic >> behind the chosen solution: >>> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ > >The one thing I can't understand is why we still don't have "network >interface aliases" (equivalent to symlinks), so that systemd can name my >interface enp2s0 *and* eth0 instead of having to choose between those >two, just like it has no problem naming my SSD /dev/sda and >/dev/disk/by-id/ata-FOOBAR (and a bunch of other names as well). Because a decision was made decades ago not to access network interfaces via /dev and changing that now would break a lot.
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2019-06-25 22:30 +0200 |
| Message-ID | <yd0eJ-4Lb-1@gated-at.bofh.it> |
| In reply to | #210383 |
>>The one thing I can't understand is why we still don't have "network
>>interface aliases" (equivalent to symlinks), so that systemd can name my
>>interface enp2s0 *and* eth0 instead of having to choose between those
>>two, just like it has no problem naming my SSD /dev/sda and
>>/dev/disk/by-id/ata-FOOBAR (and a bunch of other names as well).
>
> Because a decision was made decades ago not to access network interfaces via
> /dev and changing that now would break a lot.
I wasn't suggesting to move network interfaces into the file-system
(e.g. via device files), but only to add a new feature to create
"network interface aliases".
Stefan
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2019-06-25 22:30 +0200 |
| Message-ID | <yd0eJ-4Lb-5@gated-at.bofh.it> |
| In reply to | #210392 |
On Tue, Jun 25, 2019 at 04:22:54PM -0400, Stefan Monnier wrote: >>>The one thing I can't understand is why we still don't have "network >>>interface aliases" (equivalent to symlinks), so that systemd can name my >>>interface enp2s0 *and* eth0 instead of having to choose between those >>>two, just like it has no problem naming my SSD /dev/sda and >>>/dev/disk/by-id/ata-FOOBAR (and a bunch of other names as well). >> >> Because a decision was made decades ago not to access network interfaces via >> /dev and changing that now would break a lot. > >I wasn't suggesting to move network interfaces into the file-system >(e.g. via device files), but only to add a new feature to create >"network interface aliases". Yes, but it isn't obvious how those would behave. For filesystems it's a well understood concept. Also, for filesystems, it doesn't really matter if there are multiple names. For network interfaces, since all of the operations require special commands, which interface is returned when you enumerate them, etc.? I suspect it would just cause even more confusion.
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | linux.debian.user
csiph-web