From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] /lib/modprobe.d vs. /etc/modprobe.d
Date: Sun, 27 Jan 2013 11:00:51 -0500 [thread overview]
Message-ID: <CAGfcS_nNsV3+ivMpiMs2CHFCppknWh2ULcoVukmBBEXHShKC7g@mail.gmail.com> (raw)
In-Reply-To: <510542D6.3070007@gentoo.org>
On Sun, Jan 27, 2013 at 10:08 AM, Samuli Suominen <ssuominen@gentoo.org> wrote:
> I see a lot of packages installing /etc/modprobe.d when it should be treated
> like /etc/udev, so only generated files and users own files
On a related note, I just noticed that /etc/udev is loaded with
orphans in my case, and I can't imagine I'm the only one. When we
make moves like this we should include either news items or elogs or
something to tell users to clean out the cruft, otherwise config
protection tends to leave it there, and then users fail to get updates
since their cruft overrides them.
I assume that files that aren't user-edited can just be safely deleted?
Rich
next prev parent reply other threads:[~2013-01-27 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 15:08 [gentoo-dev] /lib/modprobe.d vs. /etc/modprobe.d Samuli Suominen
2013-01-27 16:00 ` Rich Freeman [this message]
2013-01-27 16:48 ` 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=CAGfcS_nNsV3+ivMpiMs2CHFCppknWh2ULcoVukmBBEXHShKC7g@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