I suspect they would have had similar issues with other distros, but
that would have been years ago when udev made the change and eudev
decided not to merge it. That dates to around the time eudev started.
I honestly was afraid of this with running some updates lately.
Like... Not this specifically, but because someone was commenting
about eudev->udev causing problems... And then the problems I was
having a hard time with some updates on a relatively new instance, and
I noticed that was something that needed to be done for Gentoo
purposes... They do seem to be doing *somewhat* better for having
Gentoo workable than when I started looking at using them in part
because of that (yeah I know it's not recommended, and I don't really recommend it for anyone else, but it's what I like).
If you have a Gentoo machine running on Linode, take care to note that
the eudev => udev changeover requires some manual intervention before
the next reboot.
You will need to DISABLE the network autoconfiguration option for the
VM, and edit /etc/conf.d/net to specify the new, 'predictable' network interface name. This is because Linode's network autoconfigurator is hard-coded to generate a configuration using the traditional style of
network interface names, eg. eth0Â
Alternatively, you can make whatever changes are required to have the
system enumerate the network interfaces with the old style names.
If you do neither of those things, you will need to use the rescue
console in order to log into the machine and fix your network
configuration, as the system will not be able to bring up the network
on its next boot. Ask me how I learned this.
indeed being able to change this stuff is part of the appeal of
Gentoo. Besides, Gentoo users probably would want to be aware of it anyway...
I have been running eudev for as long as it has existed, and have also
been using the predictable interface names more or less since they
were introduced. The eudev ebuild also shows a message about this
every single time you emerge it (with ewarn messages in pkg_pretend).
This was apparently available in eudev within a month of the change
in systemd. No one should be surprised by this.
What made this affect me, I think the method is different to disable it
in udev than it is in eudev.
On Wednesday, 1 December 2021 20:44:48 CET Arve Barsnes wrote:
I have been running eudev for as long as it has existed, and have alsoYeah, I was wondering why people were hitting this problem, the
been using the predictable interface names more or less since they
were introduced. The eudev ebuild also shows a message about this
every single time you emerge it (with ewarn messages in pkg_pretend).
This was apparently available in eudev within a month of the change
in systemd. No one should be surprised by this.
predictable interface names have been in eudev as well for a
considerable while. I had them disabled with the same net.ifnames=0 that others are mentioning now to get the old names (mainly since they're
just easier to remember). I was maybe thinking that there could be a configuration option for it that didn't get changed on existing installs
when this was initially introduced in eudev, which would have explained
it since my installs aren't that old. But if it automatically used the
new names for you then I have no idea either. Nothing should have
changed in this regard with this update as far as I can tell...
-Marco
On Wed, Dec 1, 2021 at 7:15 PM Dale <rdalek1967@gmail.com> wrote:
root@fireball / # ls -al /etc/udev/rules.d/
-rw-r--r-- 1 root root 1903 Apr 4 2012 70-persistent-cd.rules
-rw-r--r-- 1 root root 814 Jan 1 2008 70-persistent-net.rules
-rw-r--r-- 1 root root 0 Mar 22 2015 80-net-name-slot.rules
I can't recall which of the two about net it is tho. Thing is, it seems
to work with eudev but not udev.
With udev the filenames you want are:
80-net-name-slot.rules
80-net-setup-link.rules
Or at least, that is what I am using with the systemd-bundled udev and
my physical interface is eth0.
Neil Bothwick wrote:
On Wed, 1 Dec 2021 17:27:32 -0600, Dale wrote:
What made this affect me, I think the method is different to disable itnet.ifnames=0 works on both udev and eudev, I've had it in my GRUB config for years and it needed no changes when switching from eudev to udev.
in udev than it is in eudev.
I'm pretty sure mine is done with a udev rules file. I never had mine
on the kernel line. This is the list of rules files I have:
root@fireball / # ls -al /etc/udev/rules.d/
total 20
drwxr-xr-x 2 root root 4096 Nov 28 13:29 .
drwxr-xr-x 4 root root 4096 Nov 28 13:29 ..
-rw-r--r-- 1 root root 2064 Apr 27 2021 69-libmtp.rules
-rw-r--r-- 1 root root 1903 Apr 4 2012 70-persistent-cd.rules
-rw-r--r-- 1 root root 814 Jan 1 2008 70-persistent-net.rules
-rw-r--r-- 1 root root 0 Mar 22 2015 80-net-name-slot.rules
-rw-r--r-- 1 root root 0 Nov 27 17:53 .keep_sys-fs_udev-0
root@fireball / #
I can't recall which of the two about net it is tho. Thing is, it seems
to work with eudev but not udev. I'd think it would but based on
experience, it doesn't. I guess if someone is switching a remote
machine, or any machine, and they want to be sure, add the option to the kernel line to be safe. That may be a more dependable method.
Either way, at least maybe these threads will help someone else avoid
the problem.
On Wed, 1 Dec 2021 17:27:32 -0600, Dale wrote:
What made this affect me, I think the method is different to disable itnet.ifnames=0 works on both udev and eudev, I've had it in my GRUB config
in udev than it is in eudev.
for years and it needed no changes when switching from eudev to udev.
root@fireball / # ls -al /etc/udev/rules.d/
-rw-r--r-- 1 root root 1903 Apr 4 2012 70-persistent-cd.rules
-rw-r--r-- 1 root root 814 Jan 1 2008 70-persistent-net.rules
-rw-r--r-- 1 root root 0 Mar 22 2015 80-net-name-slot.rules
I can't recall which of the two about net it is tho. Thing is, it seems
to work with eudev but not udev.
With udev the filenames you want are:
80-net-name-slot.rules
80-net-setup-link.rules
Or at least, that is what I am using with the systemd-bundled udev and
my physical interface is eth0.
Disregard that. I'm also using net.ifnames=0 - I'm guessing the
filename changed at some point. You probably can dig around in the package-supplied udev rules to figure out which one needs to be
overridden now.
On Wed, 1 Dec 2021 20:07:11 -0500, Rich Freeman wrote:
Disregard that.
I'm not using any udev rules for network devices. If all you want is the
old eth?/wlan? names back the kernel parameter is sufficient. This works
with openrc and systemd here.
On Thu, 2 Dec 2021 07:04:26 -0500, Rich Freeman wrote:
Disregard that.
I'm not using any udev rules for network devices. If all you want is
the old eth?/wlan? names back the kernel parameter is sufficient.
This works with openrc and systemd here.
Hence the reason I said "disregard that."
So what were your udev rules doing?
Disregard that.
I'm not using any udev rules for network devices. If all you want is
the old eth?/wlan? names back the kernel parameter is sufficient.
This works with openrc and systemd here.
Hence the reason I said "disregard that."
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 294 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 247:14:29 |
| Calls: | 6,626 |
| Calls today: | 2 |
| Files: | 12,175 |
| Messages: | 5,320,897 |