Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #270068

Re: Please help me identify package so I can report an important bug

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Wed, Jun 12, 2024 at 03:16:41PM -0400, Greg Wooledge wrote:
> On Wed, Jun 12, 2024 at 09:01:44PM +0200, tomas@tuxteam.de wrote:

[...]

> > Mine loks like this:
> > 
> >   GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0"
> 
> People who are thinking of doing this should take a moment to consider
> whether it will be better or worse than the default.

Absolutely. I did, and I decided that in my case, this is the better
choice...

> For a machine that has exactly one ethernet interface, this is a vast
> improvement over the default.  Your interface will always be named
> "eth0" no matter what crazy things happen on the PCI bus.

...but it's not always, as you say.

> For a machine with multiple interfaces, however, the original problem
> that "predictable interface names" were supposed to solve is still an
> issue.  The kernel may not assign the names in the same order every
> time you boot.  In that situation, "net.ifnames=0" is not likely to
> be an improvement.  You'd be better off using systemd.link(5) files to
> customize your interface names according to your own specific needs.

I think PCI is not the worst offender. The worst is if you have a bunch
of adapters hanging off an USB tree. Then, as they say, God does play
dice :-)

Back Then (TM) (I think it was a Debian 3.x aka Sarge), a bunch of
us cobbled a "router thingy" together on some off-the-shelf hardware.
It had four Ethernets hanging off whatever PC bus was fashionable
back then (too lazy to look it up).

Not many of those were sold, luckily :-)

One was for "the bad Internet", the other three for "the inside".
Our big fear was that, after a BIOS upgrade the interfaces would
come up in a mangled order. That would have been a good application
of this scheme (provided it works at all: I'm somewhat sceptic.
Hardware and firmware are known to do... things).

We ended up going by the card's MAC addresses, at the price of
having a set up step on assembly. But then, if you change one
Ethernet card...

Alas, you can't do it right.

For my laptop, I very much prefer to say "sudo ifup eth0" than to
say "sudo ifup en0ps&&@*#!☠" thankyouverymuch :)

Cheers
-- 
t

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Please help me identify package so I can report an important bug Peter Goodall <pjgoodall@gmail.com> - 2024-06-12 08:30 +0200
  Re: Please help me identify package so I can report an important bug Richard <rrosner5@gmail.com> - 2024-06-12 13:00 +0200
    Re: Please help me identify package so I can report an important bug Jeffrey Walton <noloader@gmail.com> - 2024-06-12 17:20 +0200
      Re: Please help me identify package so I can report an important bug Richard <rrosner5@gmail.com> - 2024-06-12 19:00 +0200
        Re: Please help me identify package so I can report an important  bug debian-user@howorth.org.uk - 2024-06-12 21:50 +0200
    Re: Please help me identify package so I can report an important bug "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-06-12 20:50 +0200
      Re: Please help me identify package so I can report an important bug <tomas@tuxteam.de> - 2024-06-12 21:10 +0200
        Re: Please help me identify package so I can report an important bug Greg Wooledge <greg@wooledge.org> - 2024-06-12 21:20 +0200
          Predictable network device names [was: Please help me identify  package so I can report an important bug tomas@tuxteam.de - 2024-06-13 06:40 +0200
          Re: Please help me identify package so I can report an important bug <tomas@tuxteam.de> - 2024-06-13 06:40 +0200

csiph-web