From: Tom Gundersen <teg@jklm.no>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev: sync udev rules directories with systemd units directories
Date: Tue, 17 Jul 2012 11:46:17 +0000 [thread overview]
Message-ID: <CAG-2HqVV6P36pZR3Ci1vseYkCAKSENc2vgEhYXe3Kv4m7RdbJA@mail.gmail.com> (raw)
In-Reply-To: <1342214503-7931-1-git-send-email-w.d.hubbs@gmail.com>
On Tue, Jul 17, 2012 at 2:57 AM, William Hubbs <w.d.hubbs@gmail.com> wrote:
> Whoever was working on this back then decided that we should move most
> of the critical shared libraries to /lib or /lib64 and put linker
> scripts in /usr/lib*. That has to disappear before we can even think
> about the /usr merge.
>
> Also, remember that we are a rolling release distro. We do not have
> specific gentoo x.x releases; users just go along updating packages. So,
> I'm not sure how to force the /usr merge and symlink creation to happen
> on all of our users' systems in one go.
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 only step that caused any issues was the last one, and that was
due to users ignoring the upgrade instructions[0] and doing clever
things like "rm -rf /lib".
HTH,
Tom
[0]: <http://www.archlinux.org/news/the-lib-directory-becomes-a-symlink/>
next prev parent reply other threads:[~2012-07-17 11:46 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 [this message]
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=CAG-2HqVV6P36pZR3Ci1vseYkCAKSENc2vgEhYXe3Kv4m7RdbJA@mail.gmail.com \
--to=teg@jklm.no \
--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).