public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] udev downgrade
Date: Thu, 3 Jan 2013 19:34:10 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130103T202419-425@post.gmane.org> (raw)

The thread "Ethernet Machinations"
is finished and all ethernet issues
are resolved.


I'm starting a new thread as to deal with what to
do about udev. The same system mentioned in
the previous ethernet thread had become upgraded to
udev-196-r1 (late one night when I was tired
AND NOT THINKING TOO WELL...............
I have since been on a roller_coaster ride with
udev, almost eudev and version dev experimentations
as an accident...........

From the last thread:
I don't know what version of udev you're running (sorry if I missed it,)
but the udev-186 elog says:
        "Upstream has removed the persistent-net and persistent-cd rules
         generator. If you need persistent names for these devices,
         place udev rules for them in /etc/udev/rules.d."



I just sync and I have only have these versions of udev:
 Available versions:  ~141-r1 ~146-r1^t ~149 ~151-r4 ~164-r2 171-r9 ~195^t
~196-r1^t **999


So unless somebody can give me good reason, I'm downgrading to
udev-171 asap on this (only) system running udev 196.......
(ps, I like to experiment, but not with udev et. al.)


I even thinking or running 'emerge -e system' just to ensure
nothing is missed?

Suggestions are most welcome.



             reply	other threads:[~2013-01-03 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 19:34 James [this message]
2013-01-04  2:54 ` [gentoo-user] Re: udev downgrade James
2013-01-04  3:09   ` Bruce Hill
2013-01-04  9:16     ` Matthias Hanft
2013-01-04  6:19   ` Dustin C. Hatch
2013-01-04 11:44     ` Bruce Hill
2013-01-04 16:23     ` James
2013-01-04 17:28       ` Mark Knecht
2013-01-04 19:52       ` Dustin C. Hatch
2013-01-04 20:31         ` Kevin Chadwick
2013-01-04 20:17           ` Dustin C. Hatch

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=loom.20130103T202419-425@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --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