From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-user+bounces-144795-garchives=archives.gentoo.org@lists.gentoo.org> Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 11CCF1386F0 for <garchives@archives.gentoo.org>; Sun, 27 Jan 2013 23:00:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EEB5421C10D; Sun, 27 Jan 2013 23:00:40 +0000 (UTC) Received: from smtp.cs.nyu.edu (SMTP.CS.NYU.EDU [128.122.49.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 55EAC21C0FD for <gentoo-user@lists.gentoo.org>; Sun, 27 Jan 2013 23:00:39 +0000 (UTC) Received: from ajglap.localdomain (ool-182de1a5.dyn.optonline.net [24.45.225.165]) (authenticated bits=0) by smtp.cs.nyu.edu (8.14.3/8.14.4) with ESMTP id r0RN0Wm5029102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <gentoo-user@lists.gentoo.org>; Sun, 27 Jan 2013 18:00:35 -0500 (EST) Received: by ajglap.localdomain (Postfix, from userid 1502) id 0DF60703A9; Sun, 27 Jan 2013 18:00:30 -0500 (EST) From: Allan Gottlieb <gottlieb@nyu.edu> To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] udev-197: what to do -- S0LVED References: <yu97gmz23vj.fsf@nyu.edu> Date: Sun, 27 Jan 2013 18:00:30 -0500 In-Reply-To: <yu97gmz23vj.fsf@nyu.edu> (Allan Gottlieb's message of "Sat, 26 Jan 2013 13:30:56 -0500") Message-ID: <yu9r4l6tenl.fsf@nyu.edu> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) Precedence: bulk List-Post: <mailto:gentoo-user@lists.gentoo.org> List-Help: <mailto:gentoo-user+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-user.gentoo.org> X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain X-Archives-Salt: 1b9076ee-477f-4301-a900-3cb7293dddb3 X-Archives-Hash: cfda438aefa87da9e5790b324a485c93 On Sat, Jan 26 2013, Allan Gottlieb wrote: > I have read the news item and still have questions. The news item > covers several points. > > 1. remove udev-postmount: > I did this but worry that I now cannot reboot until I upgrade > udev. Is that correct? > > 2. Add CONFIG_DEVTMPFS=y. Easy. Kernel rebuilt and installed > in /boot (but have not rebooted). > > 3. Predictable network interface names. > I have the problematic udev rule. > Specifically 70-persistent-net.rules has (on one line) > > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:1e:c9:48:f9:a0", ATTR{type}=="1", > KERNEL=="eth*", NAME="eth0" > > I read the bug report, but it is not as clear as I would like. > Is it true that I can change my file to simply > > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:1e:c9:48:f9:a0", ATTR{type}=="1", > KERNEL=="eth*", NAME="net0" > > That is just change the NAME from eth0 to net0 ? > > 4. No support for kernels older than 2.6.39. No problem. > > 5. Separate /usr not affected. Good. > > The news item does not mention the problem of moving files > from /usr/lib/udev/rules.d to /lib/udev/rules.d. Am I correct in > believing that we still need one of the equivalents of > equery belongs -n /usr/lib/udev | xargs emerge -pv Thanks for all the suggestions. I did the following, which worked. 1. Built and installed kernel with CONFIG_DEVTMPFS=y 2. Moved udev-postmount back to /etc/init.d (I had moved it to /tmp). rc-update add udev-postmount default. 3. Reboot with new kernel (udev unchanged). Success. 4. Changed NAME=eth0 to NAME=net0 in 70-persistent-net.rules and eliminated clauses so have only (on one line) SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:1e:c9:48:f9:a0", NAME="net0" Corresponding changes to /etc/init.d /etc/runlevels/default 5. Emerge update world to get new udev (just -1 udev has blocks) 6. Change kernel configs as per udisks emerge output 7. /usr/lib/udev already empty (due to make world?) so nothing to do 8. Reboot with new kernel. Success allan