From: Harald Hoyer <harald.hoyer@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: /usr merge
Date: Mon, 26 Mar 2012 11:35:05 +0000 [thread overview]
Message-ID: <4F705469.5090901@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.01.1203252258270.12550@myrtle>
Am 26.03.2012 04:59, schrieb Allin Cottrell:
> Sorry if this is off-topic but it seems that udev, systemd and the /usr merge
> are all connected at present.
>
> I'm very happy with current udev + systemd, and I'm also persuaded that the /usr
> merge is a good idea. I've already taken care of /bin (on my non-distro Linux
> system) and /sbin shouldn't be a problem, but I'm a bit more apprehensive about
> /lib, on account of all the symlinks from /usr/lib to files in /lib, created by
> glibc.
>
> Does anyone have a nice shell script to fold the content of /lib into /usr/lib?
>
http://git.kernel.org/?p=boot/dracut/dracut.git;a=blob_plain;f=modules.d/30convertfs/convertfs.sh
next prev parent reply other threads:[~2012-03-26 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 2:59 /usr merge Allin Cottrell
2012-03-26 11:35 ` Harald Hoyer [this message]
2012-03-26 11:36 ` Harald Hoyer
2012-03-26 12:23 ` Allin Cottrell
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=4F705469.5090901@gmail.com \
--to=harald.hoyer@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).