From: Karel Zak <kzak@redhat.com>
To: L A Walsh <lkml@tlinx.org>
Cc: util-linux@vger.kernel.org
Subject: Re: RFD: --enable-bindir-path ?
Date: Thu, 30 Aug 2018 10:45:56 +0200 [thread overview]
Message-ID: <20180830084556.ubvu5e5qhzih5fng@ws.net.home> (raw)
In-Reply-To: <5B82E969.6090409@tlinx.org>
On Sun, Aug 26, 2018 at 10:54:49AM -0700, L A Walsh wrote:
> Was wondering about the addition of an "enable-bindir-path" which would only
> use
> paths with /bin instead of /usr/bin for setups where /usr/bin -> /bin (like
> cygwin who mounts /bin and /lib on /usr/bin and /usr/lib -- using mounts
> instead of symlinks). The've had that since the beginning with nothing
> being
> installed in /usr/bin or /usr/lib.
So for this use-case /usr should be ignored at all, right? What about PATH
setting? Is it also without /usr? What about man pages, docs?
I have nothing against this feature, but question is if it's important
enough to implement and support it ;-)
> Was also wondering why that wasn't chosen as a default for merging, since
> /bin and /lib are almost always on the root file system so they are always
> there, versus /usr/{bin,lib{,64}} which may need to be mounted before it can
> be used...if it can't be mounted, having things in /bin & /lib pointed
> to /usr won't work so well.
I think originally /usr was also on the same FS as /{bin,lib,...}.
Anyway, now this no issue as we use initram images where is all
stuff that is necessary to assemble usable hierarchy of filesystems
(including RAIDs, NFS moutpoints, etc.)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2018-08-30 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 17:54 RFD: --enable-bindir-path ? L A Walsh
2018-08-30 8:45 ` Karel Zak [this message]
2018-08-31 22:55 ` L A Walsh
2018-09-03 10:17 ` Karel Zak
2018-09-04 9:41 ` Karel Zak
2018-09-07 2:52 ` L A Walsh
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=20180830084556.ubvu5e5qhzih5fng@ws.net.home \
--to=kzak@redhat.com \
--cc=lkml@tlinx.org \
--cc=util-linux@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).