linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: separate /usr/broken with udev extras
Date: Sat, 30 Jul 2011 22:14:35 +0000	[thread overview]
Message-ID: <20110730221435.GA21706@linux1> (raw)
In-Reply-To: <20110730204023.GA21402@linux1>

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

On Sat, Jul 30, 2011 at 11:45:39PM +0200, Kay Sievers wrote:
> Some stuff is broken for years for all non-simple services. The real
> fix is just a cp -ax away, I guess. :)
> 
> As mentioned, the distro's fix is to mount /usr from initramfs, and
> that's the only realistic option for /{bin,lib} vs. /usr/{bin.lib}
> split, with the ever-growing use of tools from /usr during bootup.
> 
> The random split of tools tools in /{bin,lib} vs. /usr/{bin.lib} makes
> no sense today, what /{bin,lib} was for UNIX is the initramfs for
> Linux today.
> 
> We are actually currently planning to move all tools from the rootfs
> to /usr, where they belong and sort out the chaotic split of install
> locations. There will be only compat symlinks left in / then.

Why not go the other way and move things that udev needs from /usr to /?

That would be an easier transition imho than moving everything to /usr.

William

> 
> Kay
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2011-07-30 22:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30 20:40 separate /usr/broken with udev extras William Hubbs
2011-07-30 20:56 ` Kay Sievers
2011-07-30 21:23 ` Marco d'Itri
2011-07-30 21:45 ` Kay Sievers
2011-07-30 21:53 ` William Hubbs
2011-07-30 22:08 ` Kay Sievers
2011-07-30 22:14 ` William Hubbs [this message]
2011-07-30 22:20 ` Kay Sievers

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=20110730221435.GA21706@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).