From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt
Date: Fri, 29 Mar 2013 09:30:00 -0400 [thread overview]
Message-ID: <CAGfcS_kgEVnXnvWKT9rPr-tvOx32t=DZi4aMFd2uFwWVNRwxYQ@mail.gmail.com> (raw)
In-Reply-To: <201303291424.45080.dilfridge@gentoo.org>
On Fri, Mar 29, 2013 at 9:24 AM, Andreas K. Huettel
<dilfridge@gentoo.org> wrote:
> Not really. Every time I modified anything in there, it just took a few udev
> versions and suddenly I was flooded with deprecation warnings a la "things
> work different now, find out on your own how to fix it..."
Not to mention at least in the past it has tended to accumulate
orphans. I was getting tons of warnings on boot-up and discovered
that config protection left a ton of files in there from
who-knows-when. Granted, this is on a system that has been running
Gentoo for about a decade now (every part in it has changed several
times, but the OS has steadily migrated along).
Now I'm down to 5 files in there, and only one of them is my
local.rules file. If udev is going to stick stuff in /etc then it
really needs to have better communication when this stuff needs to be
modified/cleaned/etc, and what users are and aren't supposed to touch.
Rich
next prev parent reply other threads:[~2013-03-29 13:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 8:09 [gentoo-dev] Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt Samuli Suominen
2013-03-29 10:24 ` [gentoo-dev] " Duncan
2013-03-29 10:26 ` Samuli Suominen
2013-03-29 10:46 ` Diego Elio Pettenò
2013-03-29 10:50 ` Samuli Suominen
2013-03-29 11:01 ` Diego Elio Pettenò
2013-03-29 11:29 ` Samuli Suominen
2013-03-29 11:38 ` Diego Elio Pettenò
2013-03-29 12:20 ` Samuli Suominen
2013-03-29 12:33 ` Diego Elio Pettenò
2013-03-29 12:47 ` Michael Mol
2013-03-29 13:24 ` Andreas K. Huettel
2013-03-29 13:30 ` Rich Freeman [this message]
2013-03-29 13:44 ` Samuli Suominen
2013-03-29 14:35 ` Rich Freeman
2013-03-29 14:45 ` Samuli Suominen
2013-03-29 14:55 ` Rich Freeman
2013-03-31 8:41 ` Walter Dnes
2013-03-31 10:21 ` Nuno J. Silva (aka njsg)
2013-03-29 19:20 ` Ian Stakenvicius
2013-03-29 20:03 ` Diego Elio Pettenò
2013-03-31 1:06 ` Philip Webb
2013-03-31 1:17 ` Samuli Suominen
2013-03-31 1:20 ` Diego Elio Pettenò
2013-03-31 10:18 ` Nuno J. Silva (aka njsg)
2013-03-31 11:36 ` Andreas K. Huettel
2013-03-31 14:22 ` Philip Webb
2013-04-01 1:56 ` [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt : SOLVED Philip Webb
2013-04-01 9:23 ` Markos Chandras
2013-04-01 15:32 ` Philip Webb
2013-04-01 17:06 ` Markos Chandras
2013-04-01 19:53 ` Michael Mol
2013-04-01 20:14 ` Markos Chandras
2013-03-29 11:34 ` [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt Chí-Thanh Christopher Nguyễn
2013-03-29 11:40 ` Diego Elio Pettenò
2013-03-29 16:21 ` Nuno J. Silva (aka njsg)
2013-03-29 16:40 ` Markos Chandras
2013-03-29 17:38 ` Rich Freeman
2013-03-29 22:27 ` Walter Dnes
2013-03-29 18:03 ` Samuli Suominen
2013-03-29 18:59 ` Nuno J. Silva (aka njsg)
2013-03-29 11:13 ` [gentoo-dev] " Ulrich Mueller
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='CAGfcS_kgEVnXnvWKT9rPr-tvOx32t=DZi4aMFd2uFwWVNRwxYQ@mail.gmail.com' \
--to=rich0@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