6 Aug
2023
6 Aug
'23
10:36 p.m.
Hi,
On Sun, Aug 06, 2023 at 09:33:23PM +0100, Jamie MacIsaac via BitFolk Users wrote:
1. I remembered to change the interface name from eth0
to enX0 but
couldn't connect to any regular network services (ssh, httpd)
after the system was rebooted. I used the Xen shell to change the
interface name back to eth0, and could connect again after a
reboot. Are some systems happy to stay as eth0? This is quite an
old system and has been upgraded in place over several years
(started as a Debian 5.x (Lenny) system in 2009.
As far as I'm aware eth0 will be renamed to enX0 unless you have
taken steps in the past to prevent this. So have you done any of the
things described here?
https://wiki.debian.org/NetworkInterfaceNames#How_to_get_it_back
On a bullseye VM this is what udev thinks about my eth0:
$ sudo udevadm test-builtin net_id /sys/class/net/eth0
Load module index
Parsed configuration file /lib/systemd/network/99-default.link
Parsed configuration file /lib/systemd/network/73-usb-net-by-mac.link
Created link configuration context.
Using default interface naming scheme 'v247'.
ID_NET_NAMING_SCHEME=v247
ID_NET_NAME_MAC=enxaa00004ba0c1
ID_OUI_FROM_DATABASE=DIGITAL EQUIPMENT CORPORATION
Unload module index
Unloaded link configuration context.
and on a bookworm VM this is what it thinks:
$ sudo udevadm test-builtin net_id /sys/class/net/enX0
Trying to open "/etc/systemd/hwdb/hwdb.bin"...
Trying to open "/etc/udev/hwdb.bin"...
Trying to open "/usr/lib/systemd/hwdb/hwdb.bin"...
Trying to open "/lib/systemd/hwdb/hwdb.bin"...
Trying to open "/lib/udev/hwdb.bin"...
=== trie on-disk ===
tool version: 252
file size: 11993513 bytes
header size 80 bytes
strings 2530377 bytes
nodes 9463056 bytes
Loading kernel module index.
Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
Found container virtualization none.
Using default interface naming scheme 'v252'.
Parsed configuration file "/usr/lib/systemd/network/99-default.link"
Parsed configuration file "/usr/lib/systemd/network/73-usb-net-by-mac.link"
Created link configuration context.
ID_NET_NAMING_SCHEME=v252
ID_NET_NAME_MAC=enx00165e000605
enX0: MAC address identifier: hw_addr=00:16:5e:00:06:05 → x00165e000605
ID_OUI_FROM_DATABASE=Precision I/O
sd-device: Failed to chase symlinks in "/sys/devices/vif-0/of_node".
ID_NET_NAME_SLOT=enX0
Unload kernel module index.
Unloaded link configuration context.
What does yours say?
2. The sysv-rc-conf package is being held back when I
apt-get
upgrade. If I try to upgrade it, apt wants to remove a load of
packages (about 30). Can I safely just remove the sysv-rc-conf
package? /sbin/init is a symlink to /lib/systemd/systemd, so I
presume I'm using systemd and don't need sysv-rc-conf?
Yes, you can remove it, it's not being used. It doesn't have
anything depending upon it either:
$ apt rdepends sysv-rc-conf
sysv-rc-conf
Reverse Depends:
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting