Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #270053
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Please help me identify package so I can report an important bug |
| Date | 2024-06-12 21:20 +0200 |
| Message-ID | <IOBFL-2rCi-5@gated-at.bofh.it> (permalink) |
| References | <IOpEC-2keE-17@gated-at.bofh.it> <IOtRU-2mJx-7@gated-at.bofh.it> <IOBcJ-2rde-1@gated-at.bofh.it> <IOBw6-2rzb-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Jun 12, 2024 at 09:01:44PM +0200, tomas@tuxteam.de wrote: > No need. You can have your traditional names (I do). Just add > "net.ifnames=0" (if necessry separated by a space, should > other stuff be already there) to your GRUB_CMDLINE_LINUX_DEFAULT > in your /etc/default/grub, then ru update-grub. > > 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. 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. 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. > > > https://wiki.debian.org/NetworkInterfaceNames
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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