From: William Hubbs <w.d.hubbs@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev: sync udev rules directories with systemd units directories
Date: Fri, 13 Jul 2012 22:48:27 +0000 [thread overview]
Message-ID: <20120713224827.GA8266@linux1> (raw)
In-Reply-To: <1342214503-7931-1-git-send-email-w.d.hubbs@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
On Fri, Jul 13, 2012 at 11:38:24PM +0200, Kay Sievers wrote:
> Udev will *never* look in /usr/local, that is no place for
> system-level software. My take on this is: early boot has absolutely
> zero business in /usr/local.
>
> I see that you just want to sync this, but I will not allow /usr/local
> happen to udev. It makes no sense, does not solve any problem, creates
> nothing but needless issues with custom setups and custom mounts
> (which are not uncommon) on /usr/local that are better avoided.
>
> I tried several times to talk Lennart out of that nonsense, but wasn't
> successful so far. :)
>
> > TEST_PREFIX UDEVLIBEXECDIR "/rules.d",
> > + TEST_PREFIX "/usr/lib/udev/rules.d",
> > +#ifdef HAVE_SPLIT_USR
> > + TEST_PREFIX "/lib/udev/rules.d",
> > +#endif
>
> I have no problem with that, even when I think it's the wrong way to
> do these things. It just creates mess, that is much bigger than the
> split-usr ever was. But we have it in systemd, and there is no real
> argument for me to make against it.
I'm personally not concerned with /usr/local, but the portion above is
the more important to me. For split /usr systems, there is a lot of
software that installs rules in /lib/udev, so I think we need to support
that directory.
Should I resubmit the patch?
Thanks,
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-07-13 22:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 21:21 [PATCH] udev: sync udev rules directories with systemd units directories William Hubbs
2012-07-13 21:38 ` Kay Sievers
2012-07-13 22:48 ` William Hubbs [this message]
2012-07-13 23:06 ` Kay Sievers
2012-07-14 0:33 ` William Hubbs
2012-07-14 3:46 ` Marco d'Itri
2012-07-14 5:42 ` William Hubbs
2012-07-14 5:52 ` Marco d'Itri
2012-07-14 7:21 ` William Hubbs
2012-07-15 17:03 ` Martin Pitt
2012-07-15 17:14 ` Marco d'Itri
2012-07-15 17:45 ` Martin Pitt
2012-07-15 23:09 ` William Hubbs
2012-07-16 0:02 ` Kay Sievers
2012-07-16 0:06 ` Marco d'Itri
2012-07-16 0:26 ` Kay Sievers
2012-07-17 0:57 ` William Hubbs
2012-07-17 1:14 ` William Hubbs
2012-07-17 7:03 ` Lucas De Marchi
2012-07-17 11:46 ` Tom Gundersen
2012-07-17 23:44 ` William Hubbs
2012-07-17 23:50 ` Greg KH
2012-07-18 6:02 ` William Hubbs
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=20120713224827.GA8266@linux1 \
--to=w.d.hubbs@gmail.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).