public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-news:master commit in: 2013/2013-03-29-udev-upgrade/
Date: Sat, 30 Mar 2013 21:05:43 +0000 (UTC)	[thread overview]
Message-ID: <1364677521.cb17596416c100d7c8e18323cdfeb31c2cf4129b.williamH@gentoo> (raw)

commit:     cb17596416c100d7c8e18323cdfeb31c2cf4129b
Author:     William Hubbs <williamh <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 30 21:05:21 2013 +0000
Commit:     William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Sat Mar 30 21:05:21 2013 +0000
URL:        http://sources.gentoo.org/gitweb/?p=proj/gentoo-news.git;a=commit;h=cb175964

clean up udev upgrade news item

---
 .../2013-03-29-udev-upgrade.en.txt                 |   96 ++++++++++----------
 .../2013-03-29-udev-upgrade.en.txt.asc             |   10 +--
 2 files changed, 49 insertions(+), 57 deletions(-)

diff --git a/2013/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt b/2013/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt
index bc99e28..c21692d 100644
--- a/2013/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt
+++ b/2013/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt
@@ -2,35 +2,36 @@ Title: Upgrading udev to version >=200
 Author: Samuli Suominen <ssuominen@gentoo.org>
 Content-Type: text/plain
 Posted: 2013-03-29
-Revision: 1
+Revision: 2
 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.
+This replaces the earlier news item about the udev 197 upgrade and
+describes the predictable network interface names in more detail.
+
+If you skip anything in this news item, your system will not be
+bootable, or your networking will be down, or both.
 
-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.
+1. udev-postmount init script:
 
-2. DEVTMPFS support, both kernel and fstab:
+Remove the udev-postmount init script from your runlevels.
 
-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.
+2. devtmpfs support:
 
-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.
+You need at least version 2.6.32 of the kernel for devtmpfs
+functionality. Once you have this, make sure CONFIG_DEVTMPFS=y is set
+in the kernel configuration. See the gentoo udev guide for the option in
+make menuconfig [1].
 
-[1] http://www.gentoo.org/doc/en/udev-guide.xml
+If you have a line for /dev in /etc/fstab, make sure it is configured
+for file system type devtmpfs (not tmpfs or any other type). Also, you
+can remove this line if you prefer, since devtmpfs is mounted
+automatically.
 
-3. Old networking rules:
+3. Old interface naming rules:
 
 If the system still has old network interface renaming rules in
 /etc/udev/rules.d, like 70-persistent-net.rules, those will need
@@ -39,68 +40,63 @@ 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]
+documentation of it if you like[2].
 
 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.
+from the end of the 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"
+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"
+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:
+4. predictable network interface names:
 
-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.
+If /etc/udev/rules.d/80-net-name-slot.rules is an empty file or a
+symlink to /dev/null, the new names will be disabled and the kernel will
+do all the interface naming, and the resulting names may vary by kernel
+configuration, hardware configuration and kernel version.
 
 Also, the forementioned old 70-persistent-net.rules might interfere with
-the new enabling of the new predictable interface names!
+the new predictable interface names.
 
-You can get attributes of your networking interfaces using following
-example command (replace eth0 with your current interface name):
+You can get attributes of your network interfaces using a command like
+the following (replace eth0 with the name of the appropriate interface):
 
 # 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
+/etc/udev/rules.d and specify the attributes and in which order
+they will be used for naming. See upstream wiki[3] 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.
+You can prepare the system for the new names before booting for example
+by renaming /etc/init.d/net.* symlinks, editing /etc/conf.d/net, etc.
 
-The feature can also be completely disabled using net.ifnames=0 kernel
-commandline option.
+The feature can also be completely disabled using net.ifnames=0on the
+kernel command line.
 
 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.
 
+This feature can also replace the functionality of sys-apps/biosdevname,
+but you can still keep using it if you want.
+
 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 a dedicated page for udev upgrade notes[4].
 
-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
+[1] http://www.gentoo.org/doc/en/udev-guide.xml
+[2] http://www.kernel.org/doc/htmldocs/device-drivers/API-device-rename.html
+[3] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
+[4] http://wiki.gentoo.org/wiki/Udev/upgrade

diff --git a/2013/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt.asc b/2013/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt.asc
index 5275d57..e6de00a 100644
--- a/2013/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt.asc
+++ b/2013/2013-03-29-udev-upgrade/2013-03-29-udev-upgrade.en.txt.asc
@@ -1,11 +1,7 @@
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.19 (GNU/Linux)
 
-iQEcBAABAgAGBQJRVvIfAAoJEEdUh39IaPFNe6MH/jLqOxaJV6yw8YcoLjb8r8xP
-wJhsnPoh3BYwBr6pS3tCt7WPd4+UStJLHoJZmX7f8vuZTnTkMB3UMwvxDNmXwhpl
-Jt5DX7t0NYw30ofyW2YJt3rhYyTnvrfGTYdiOA+4nIMYLTPb3CZ4CgA3AiPH/nSU
-AVUa7OBHIpS04ngV4Ym8jKhpdGk4C92ZXf33d7djascEwSwZJO8HvImB+1FN+WH7
-wA520HzuGTmUeB+EYueBkZKmwJU6URObqxedhxYYqW5P+ab+Vvkz6RE32J4hfg00
-5ndwD5LoWlkdQbvm4YyWnfOfbxS6wABvc0dtzm39SFXsfOwNDWwiDxlHIgDz3UQ=
-=OVlU
+iEYEABECAAYFAlFXUtwACgkQblQW9DDEZTg9/gCgqBBMeGsnlhkZT8SFM3jWsvnX
+Hr0AnRySs7hPn9dUhyTP4LHG7H1Lfub/
+=QIIB
 -----END PGP SIGNATURE-----


             reply	other threads:[~2013-03-30 21:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-30 21:05 William Hubbs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-31 16:50 [gentoo-commits] proj/gentoo-news:master commit in: 2013/2013-03-29-udev-upgrade/ Samuli Suominen
2013-03-30 14:11 Samuli Suominen
2013-03-29 14:58 Samuli Suominen
2013-03-29 14:58 Samuli Suominen
2013-03-29 14:22 Samuli Suominen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1364677521.cb17596416c100d7c8e18323cdfeb31c2cf4129b.williamH@gentoo \
    --to=williamh@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox