On Wed, 01 Dec 2021 19:15:36 -0500,
Dale wrote:
>
> 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 it
> >> in udev than it is in eudev.
> > net.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.
> >
> >
>
>
> 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.
I had this happen to me when I got this box, the 80.rules hack stopped
working, and so I gave up and used the "predictable" names. I must
have forgotten about the kernel command line parameter at the time.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
cov...@ccs.covici.com
