public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] udev-197: what to do
Date: Sat, 26 Jan 2013 13:30:56 -0500	[thread overview]
Message-ID: <yu97gmz23vj.fsf@nyu.edu> (raw)

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

I used that successfully when one of my testing systems went to
udev-197.  I would think it is needed (before reboot) on my stable
systems as well so I am surprised it is not in the news item.

thanks,
allan


             reply	other threads:[~2013-01-26 18:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-26 18:30 Allan Gottlieb [this message]
2013-01-26 23:52 ` [gentoo-user] Re: udev-197: what to do walt
2013-01-27  9:48 ` [gentoo-user] " Matthias Hanft
2013-01-27 10:36 ` Florian Philipp
2013-01-27 23:00 ` [gentoo-user] udev-197: what to do -- S0LVED Allan Gottlieb
2013-02-15 17:28   ` Stefan G. Weichinger
2013-02-15 17:41     ` [gentoo-user] " Nuno Silva
2013-02-15 17:45       ` Stefan G. Weichinger
2013-02-15 18:23         ` Stefan G. Weichinger
2013-02-15 19:07           ` Alex Schuster
2013-02-15 19:20             ` Stefan G. Weichinger
2013-02-15 19:39               ` [gentoo-user] Re: udev-197: what to do -- S0LVED for ME as well ;-) Stefan G. Weichinger

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=yu97gmz23vj.fsf@nyu.edu \
    --to=gottlieb@nyu.edu \
    --cc=gentoo-user@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