| View previous topic :: View next topic |
| Author |
Message |
SamuliSuominen
Retired Dev
Joined: 30 Sep 2005
Posts: 2133
Location: Finland
|
 Posted: Fri Mar 29, 2013 9:50 am Post subject: |
 |
|
I wrote new news item today for stabilization of =sys-fs/udev-200, =sys-fs/udev-init-script-25 for https://bugs.gentoo.org/show_bug.cgi?id=463614
http://sources.gentoo.org/gitweb/?p=proj/gentoo-news.git;a=blob;f=2013/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt;hb=d1fef8f77766a9cb579241627f4e630adf300985
| Quote: |
Title: udev upgrade from 197 (or older) to 200 (or newer)
Author: Samuli Suominen <ssuominen@gentoo.org>
Content-Type: text/plain
Posted: 2013-03-29
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <sys-fs/udev-201
This will replace the earlier news item of udev 197 upgrade,
and describe the predictable networking names to more detail.
If you skip these four phases, either your system won't boot or
networking will be down, or both.
Pay attention also to every message printed by emerge of sys-fs/udev
and sys-fs/udev-init-scripts as this news item may not be complete.
1. Removed init script:
Remove udev-postmount init script from runlevels.
2. DEVTMPFS support, both kernel and fstab:
CONFIG_DEVTMPFS=y kernel option must be enabled (and for that you need
at least kernel 2.6.32) see gentoo udev guide[1] for menuconfig
example.
If you have own line for /dev in /etc/fstab, make sure it's also
fstype 'devtmpfs' and not fstype 'tmpfs' or remove the entire line
since it's automounted without entry there anyway.
[1] http://www.gentoo.org/doc/en/udev-guide.xml
3. Old networking rules:
If the system still has old network interface renaming rules in
/etc/udev/rules.d, like 70-persistent-net.rules, those will need
to be either modified or removed.
If you choose to modify them, you must use free namespace (like net*
or internet*) instead of kernel namespace (like eth* or wlan*)
because in-place renaming has been deprecated, see small
documentation of it if you like[1]
The file 70-persistent-net.rules, like the 70-persistent-cd.rules
should be removed, so if you modify, rename the file also to something
else like 70-my-network.rules to silence the deprecation warning coming
from end of sys-fs/udev emerge.
This is the old format with reserved namespace:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="yy:yy:yy:yy:yy:yy",
NAME="eth1"
This is the new format with free namespace:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx",
NAME="net0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="yy:yy:yy:yy:yy:yy",
NAME="net1"
4. The predictable network interface naming:
If /etc/udev/rules.d/80-net-name-slot.rules is a empty file, or if it's
a symlink to /dev/null, the new names will be disabled and kernel will
do all the interface naming, and the resulting names will vary by kernel
and hardware configuration, and may vary by kernel version.
Also, the forementioned old 70-persistent-net.rules might interfere with
the new enabling of the new predictable interface names!
You can get attributes of your networking interfaces using following
example command (replace eth0 with your current interface name):
# udevadm test-builtin net_id /sys/class/net/eth0 2> /dev/null
You can copy /lib/udev/rules.d/80-net-name-slot.rules to
/etc/udev/rules.d and specify what attributes and in which order
gets used for naming. See upstream wiki[2] for detailed list
of options.
You can prepare the system this way for the new names before booting,
like renaming /etc/init.d/net.* symlinks.
The feature can also be completely disabled using net.ifnames=0 kernel
commandline option.
If you only have one interface card, you don't necessarily have much
use for this feature as the name almost always stays at eth0, you can
easily disable it using forementioned methods.
In a normal new installation there are no files in /etc/udev/rules.d
and if you haven't edited any files you have in there, you should most
likely backup and delete them all if they don't belong to any packages.
This feature can also replace the functionality of sys-apps/biosdevname,
but you can still keep using it if you want.
The official wiki has dedicated page for udev upgrade notes[3].
[1] http://www.kernel.org/doc/htmldocs/device-drivers/
API-device-rename.html
[2] http://www.freedesktop.org/wiki/Software/systemd/
PredictableNetworkInterfaceNames
[3] http://wiki.gentoo.org/wiki/Udev/upgrade
|
So I've removed the old item and combined these. I hope it makes more sense than the original news item now. Don't shoot the messenger!
Last edited by SamuliSuominen on Fri Mar 29, 2013 3:18 pm; edited 1 time in total |
|
| Back to top |
|
 |
asturm
Developer
Joined: 05 Apr 2007
Posts: 8935
|
| Posted: Fri Mar 29, 2013 10:36 am Post subject: |
|
|
Reads fine enough without going grammar fascist.
//EDIT: In addition, I mastered the upgrade to udev-200 without a glitch by means of your news item. 
| ssuominen wrote: | | [...]but what I heard last was that they are going to package it just like we do, and they are going even futher with it, like packaging systemd-logind out from systemd's tarball to replace ConsoleKit but still use it on non-systemd systems.[...] |
I was wondering when that was going to happen eventually. Sounds fine to replace the increasingly bearded consolekit on Gentoo, let's have a look what they do. |
|
| Back to top |
|
|
SamuliSuominen
Retired Dev
Joined: 30 Sep 2005
Posts: 2133
Location: Finland
|
| Posted: Fri Mar 29, 2013 3:20 pm Post subject: |
|
|
| genstorm wrote: | Reads fine enough without going grammar fascist.
//EDIT: In addition, I mastered the upgrade to udev-200 without a glitch by means of your news item.
| ssuominen wrote: | | [...]but what I heard last was that they are going to package it just like we do, and they are going even futher with it, like packaging systemd-logind out from systemd's tarball to replace ConsoleKit but still use it on non-systemd systems.[...] |
I was wondering when that was going to happen eventually. Sounds fine to replace the increasingly bearded consolekit on Gentoo, let's have a look what they do. |
It's on top of my list too to look at if it's doable for us too; I mean trying to extract the systemd-logind from systemd for use with eg. OpenRC ... |
|
| Back to top |
|
|
jfp
Guru
Joined: 08 Jul 2007
Posts: 326
Location: Virginia, USA
|
| Posted: Sat Mar 30, 2013 2:18 pm Post subject: |
|
|
| Quote: | If you have own line for /dev in /etc/fstab, make sure it's also
fstype 'devtmpfs' and not fstype 'tmpfs' or remove the entire line
since it's automounted without entry there anyway. |
I have the following in my /etc/fstab:
| Quote: | # glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
|
Please excuse my ignorance (of which I have plenty), but does this line need to be removed or changed?
_________________
jfp |
|
| Back to top |
|
|
SamuliSuominen
Retired Dev
Joined: 30 Sep 2005
Posts: 2133
Location: Finland
|
| Posted: Sat Mar 30, 2013 2:24 pm Post subject: |
|
|
| jfp wrote: | | Quote: | If you have own line for /dev in /etc/fstab, make sure it's also
fstype 'devtmpfs' and not fstype 'tmpfs' or remove the entire line
since it's automounted without entry there anyway. |
I have the following in my /etc/fstab:
| Quote: | # glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
|
Please excuse my ignorance (of which I have plenty), but does this line need to be removed or changed? |
It means exactly /dev and not /dev/something. So this one isn't relavent for the upgrade.
However, as unrelated point, /dev/shm gets also automounted so I don't know why you have it in /etc/fstab. Perhaps some outdated guide told you to put it there? You can remove it:
| Code: |
ssuominen@null ~ $ grep shm /etc/fstab
ssuominen@null ~ $ mount |grep shm
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime)
|
|
|
| Back to top |
|
|
jfp
Guru
Joined: 08 Jul 2007
Posts: 326
Location: Virginia, USA
|
| Posted: Sat Mar 30, 2013 2:31 pm Post subject: |
|
|
| Quote: | | However, as unrelated point, /dev/shm gets also automounted so I don't know why you have it in /etc/fstab. Perhaps some outdated guide told you to put it there? You can remove it: |
Thanks very much for the answers. Yes, this computer's Gentoo was installed years ago (although it is regulary updated). That "shm" line was probably added a long time ago. I will delete it.
_________________
jfp |
|
| Back to top |
|
|
Punchcutter
Guru
Joined: 11 Feb 2007
Posts: 354
|
| Posted: Sat Apr 20, 2013 12:22 am Post subject: |
|
|
Thanks to ssuominen and any others who may have contributed to the improvement of the udev migration docs.
I made the upgrade last night and everything's working fine  |
|
| Back to top |
|
|
MoonWalker
Guru
Joined: 04 Jul 2002
Posts: 510
|
| Posted: Sat Apr 20, 2013 1:46 pm Post subject: |
|
|
| Punchcutter wrote: | Thanks to ssuominen and any others who may have contributed to the improvement of the udev migration docs.
I made the upgrade last night and everything's working fine |
Yes me too, R.I.P. Udev--171-r10
_________________
/Joakim
Living on earth is expensive, but it includes a free trip around the sun
every year. |
|
| Back to top |
|
|
Punchcutter
Guru
Joined: 11 Feb 2007
Posts: 354
|
| Posted: Sun Apr 21, 2013 9:15 pm Post subject: |
|
|
| MoonWalker wrote: | | Yes me too, R.I.P. Udev--171-r10 |
Yes, but it's only a matter of time before there's some other crap  |
|
| Back to top |
|
|
Punchcutter
Guru
Joined: 11 Feb 2007
Posts: 354
|
| Posted: Tue Apr 23, 2013 9:01 pm Post subject: |
|
|
Actually I was a little too hasty to post "all clear".... because my wifi is not working:
| Code: | # wpa_supplicant -iwlp3s0 -Dwext -c /etc/wpa_supplicant/wpa_supplicant.conf
Could not read interface wlp3s0 flags: No such device
Failed to initialize driver interface
# iwconfig wlp3s0
wlp3s0 No such device
# /etc/init.d/net.wlp3s0 start
* Bringing up interface wlp3s0
* ERROR: interface wlp3s0 does not exist
* Ensure that you have loaded the correct kernel module for your hardware
* ERROR: net.wlp3s0 failed to start
|
I'm assuming it's not anything related to the kernel, as none of that has changed since it was working prior to udev upgrade. Looks to me like everything's ok there:
| Code: | # lsmod | grep iwl
iwl4965 66192 0
iwlegacy 32836 1 iwl4965
mac80211 159833 2 iwl4965,iwlegacy
cfg80211 117755 3 iwl4965,iwlegacy,mac80211
|
Following seems to be relevant, but I'm not sure what to do about it:
| Code: | # ls -l /sys/class/net
total 0
lrwxrwxrwx 1 root root 0 Apr 22 07:35 enp0s25 -> ../../devices/pci0000:00/0000:00:19.0/net/enp0s25
lrwxrwxrwx 1 root root 0 Apr 23 10:51 lo -> ../../devices/virtual/net/lo
|
I've finded and grepped through /sys/devices, but can't find anything that looks like a wifi adaptor. The name wlp3s0 is the one reported to me by the udevadm command at time of upgrade.
Any clues about how to fix this are much appreciated. |
|
| Back to top |
|
|
BitJam
Advocate
Joined: 12 Aug 2003
Posts: 2508
Location: Silver City, NM
|
| Posted: Tue Apr 23, 2013 9:31 pm Post subject: |
|
|
The conflict between udev (post udev-171-r10 on Gentoo) and hal, and hence Amazon Prime Video, was part of a recent Slashdot article:
The Dark Side of Amazon's New Pilots: | Quote: | | This effectively kills access for everyone using GNU/Linux, even with the (officially unsupported) Adobe Flash plugin! The Adobe plugin relies on HAL for some DRM magic, but HAL is unmaintained, deprecated, and was removed from most major distros ages ago. You can't even install it by hand thanks to udev removing a few features HAL relied upon. |
On my system, simply installing >udev-171-r10 breaks hal making it impossible to watch Amazon videos. If I downgrade to udev-171-r10 then hal runs again and Amazon videos work again. |
|
| Back to top |
|
|
Gusar
Advocate
Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia
|
| Posted: Tue Apr 23, 2013 9:57 pm Post subject: |
|
|
Hal has been patched by an Arch user to work with newer udev versions many months ago. Grab the tarball here: https://aur.archlinux.org/packages/hal/, in particular the udev-update and hal-libudev-events patches are for interfacing with udev (udev-update needs to be adjusted to wherever a particular distro puts udevadm, Arch has it in a different place than Gentoo), but the other patches there are needed too.
But anyway, how is flash relying on tech that has been deprecated years ago a fault of udev? The fault is 100% with flash. The socket feature was removed from udev because only hal used it. With hal being deprecated, why keep the feature around, it only makes sense that it got removed. So basically, blame Adobe for abandoning flash for linux, not udev.
Oh, and blame Amazon for insisting on DRM. But well, while Amazon doesn't want your money, there's other places that will serve you - first comment at slashdot. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
