所有的 network interface 變成 eth0/eth1 ….. ，不再是 predictable network interface names （可預測的網路介面名稱像是 ensp1 這樣的）

查了一下系統，發現 driver loading 都是正常的，想到 predictable network interface names 最主要的就是 udev ，試著重啟 udev 看看，沒想到所有的 interface 就變回來了

查了一下 Kernel option ，以前 Gentoo 用 predictable network interface names 要開 kernel option ，現在不用，想必已經預設是這樣了
下一步就是查一下之前用的 udev ，再編回來。沒想到，舊版的 236 從 portage 移除了，新版的 238 之後， compile error 都要 download systemd 放在裡面。這下原因大白了，八成是這個原因，因為 Gentoo 的老玩家都還在用 OpenRC。

之前在查其他東西的時候有注意到 eudev 這個東西，不過沒有特別注意，但是解法就在這邊

簡單的說， eudev 就是 Udev 的 Gentoo 版，給 OpenRC 這樣的舊系統用的，systemd 不要用。

真是 %@%@#$%@#$%@#$%#@%$

可能有一天真的要升級到 systemd ，我不想啊啊啊啊啊

以下 Copy 自 Gentoo Wiki
—
eudev is Gentoo’s fork of udev, systemd’s device file manager for the Linux kernel.^[1] It manages device nodes in /dev and handles all user space actions when adding or removing devices.

The goal of eudev is to obtain better compatibility with existing software such as the OpenRC init system, Upstart init system, older Linux kernels, various toolchains, and anything else required^[2] by (but not well supported through) udev.

Similar to ebuild, eclass, emerge, etc. eudev’s name follows the ‘E’ prefix convention started by Gentoo’s founder Daniel Robbins.

System configurations running systemd have no use for eudev.

Ref.

https://wiki.gentoo.org/wiki/Eudev

The post [Gentoo] Moved to eudev from udev appeared first on richliu's blog.

不過總之他們就是改了, 說什麼安全的問題啦, firewall 設定啦.

只是改了之後, 大家討論了很久, 也 try 了很久.
我也是這次因為一定要能動, 所以認真的研究了一下, 目前最安定的設定, 可以正確更改名稱的設定.
1. 在 kernel command line 加上 net.ifnames=0, 這樣就會變原來的 eth0… blah blah , 可是原先的更改名稱方式還是不能用.

Gentoo 使用者可以改 Kernel Config, 關掉這個選掉

Gentoo Linux  —>
[ ]   Linux dynamic and persistent device naming (userspace devfs) support

2. 請參照 Gentoo 文件 2.d. Network Interface Naming

# udevadm test-builtin net_id /sys/class/net/eth0 2>/dev/null
ID_NET_NAME_MAC=enxc80aa9429d76
ID_OUI_FROM_DATABASE=Quanta Computer Inc.

# vim /etc/udev/rules.d/70-net-name-use-custom.rules
# First one uses MAC information, and 70- number to be before other net rules
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="c8:0a:a9:42:9d:76", NAME="lan0"

# vim /etc/udev/rules.d/76-net-name-use-custom.rules
# Second one uses ID_NET_NAME_PATH information, and 76- number to be between
# 75-net-*.rules and 80-net-*.rules
SUBSYSTEM=="net", ACTION=="add", ENV{ID_NET_NAME_PATH}=="enp3s0", NAME="wifi0"

這樣就可以成功了.

The post udev 之後仍然想用原先的 network device rename 的方式修改 interface appeared first on richliu's blog.

# eselect news read 18
2013-01-23-udev-upgrade
Title Upgrading udev from 171 (or older) to 197
Author Samuli Suominen
Posted 2013-01-23
Revision 1
Upgrading udev from 171 (or older) to 197 will require special attention:

– Remove udev-postmount from runlevels.

– The need of CONFIG_DEVTMPFS=y in the kernel; need to verify the fstype for
possible /dev line in /etc/fstab is devtmpfs (and not, for example, tmpfs)

– The case of predictable network interface names; if the file
/etc/udev/rules.d/70-persistent-net.rules is being used for renaming
network interface names to already existing names, then you need to
read following bug[1] because it’s no longer possible. This won’t
be a problem with the new predictable network interface name scheme[2].

[1] http://bugs.gentoo.org/453494
[2] http://www.freedesktop.org/wiki/Software/systemd/
PredictableNetworkInterfaceNames

– Support for older kernels than 2.6.39 is dropped. If you need older kernel
we recommend you to look into sys-fs/eudev or use local overlay for keeping
the old ebuild. Remember to also get the distfiles where the patchsets are.
The upgrade into current stable version of gentoo-sources is recommended.

– The case of separate /usr; if it worked for you with 171 it will continue
to work for you with 197. We still recommend initramfs with separate /usr
mounting capabilities because you might need packages like sys-apps/kbd
(keymaps in /usr) or net-wireless/bluez (possible keyboard) in early boot.

And read every message printed by the emerge of udev and udev-init-scripts
to ensure the system is in order before booting as this news item might
not be complete.

Apologies if this news came too late for you.

The post Upgrading udev from 171 (or older) to 197 appeared first on richliu's blog.