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: Wed, 18 Jul 2012 06:02:45 +0000 [thread overview]
Message-ID: <20120718060245.GA19035@linux1> (raw)
In-Reply-To: <1342214503-7931-1-git-send-email-w.d.hubbs@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2070 bytes --]
On Tue, Jul 17, 2012 at 04:50:48PM -0700, greg wrote:
> On Tue, Jul 17, 2012 at 06:44:00PM -0500, William Hubbs wrote:
> > On Tue, Jul 17, 2012 at 01:46:17PM +0200, Tom Gundersen wrote:
> > > We had a similar issue in Arch. What we did was the following:
> > >
> > > Patch udev+kmod+systemd (the last one was for free) to read from
> > > {/usr,}/lib/{modprobe.d,depmod.d,udev/rules.d,systemd/system}.
> > >
> > > We then rebuild all the packages that installed binaries to /lib/udev/
> > > and /lib/systemd to move them to their /usr/lib counterparts (as we
> > > did not want to patch udev/systemd to read the helpers from more than
> > > one location).
> > >
> > > Then we let people rebuild their packages to move things from /lib to
> > > /usr/lib on a package-by-package basis.
> > >
> > > Then we rebuilt all our kernels and pointed kmod/udev to
> > > /usr/lib/modules rather than /lib/modules.
> > >
> > > At this point only glibc owned stuff in /lib, so we rebuilt that to
> > > move it all to /usr/lib and replace /lib with a symlink to /usr/lib.
> >
> > The problem for us with these steps is that the building happens on
> > users' systems since we are source based, so we have to go about it
> > differently. We can't rebuild packages and send them down to the users.
>
> No, but we can fix all packages in the tree, and then update the udev
> version, with a big fat warning / error when we install the new udev
> package saying that the rules need to be fixed by updating the packages
> that placed them there.
>
> > This is why it would be very helpful if udev would keep some backward
> > compatibility and read rules from /lib/udev/rules.d as long as it was a
> > directory.
>
> I don't think this is really necessary, as long as we just fix up all
> packages in the tree that are doing things wrong. That shouldn't take
> very long (hint, if you need help, I'll be glad to do so.)
Hey greg,
write to me off list and let me know what we need to do and we can go
from there.
Thanks,
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-07-18 6:02 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
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 [this message]
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=20120718060245.GA19035@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 read-only IMAP folder(s) and NNTP newsgroup(s).