Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: add options for /bin /sbin and /lib to be symlinks into /usr
Date: Mon, 14 Sep 2015 23:39:41 +0200	[thread overview]
Message-ID: <87vbbcznmq.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <55F73B74.1020708@mind.be> (Arnout Vandecappelle's message of "Mon, 14 Sep 2015 23:26:12 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

Hi,

>> Is there any reason why we explicitly add the symlinks for /bin / /sbin
 >> and /lib and don't just do:
 >> 
 >> ln -sf . usr

 >  Well, in Fedora I think the idea was that / could be an initramfs and /usr
 > would be mounted read-only. But since we don't directly support that use case,
 > making /usr a symlink would indeed be an option.

 >  However, I'm not really in favour of it. I don't see that it brings
 > a lot of benefit, other than reducing the number of symlinks from 3
 > to 1. But it does create /share and /local which looks weird could
 > potentially conflict with existing user directories (e.g. a
 > mountpoint for windows shares...). Also it makes it more complicated
 > for the user to implement a fedora-like mounted /usr.

Ok - fine, having 1 or 3 symlinks isn't really a big deal. Just symlinking /usr
seemed the simplest possible solution.

-- 
Venlig hilsen,
Peter Korsgaard 

  reply	other threads:[~2015-09-14 21:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 23:47 [Buildroot] [PATCH] system: add options for /bin /sbin and /lib to be symlinks into /usr Yann E. MORIN
2015-09-04  7:48 ` Vicente Olivert Riera
2015-09-04  8:16   ` Arnout Vandecappelle
2015-09-04 16:29     ` Yann E. MORIN
2015-09-04 19:05       ` Arnout Vandecappelle
2015-09-04 16:12   ` Yann E. MORIN
2015-09-04  8:11 ` Thomas Petazzoni
2015-09-04  8:19   ` Arnout Vandecappelle
2015-09-04 16:31     ` Yann E. MORIN
2015-09-14 21:12       ` Peter Korsgaard
2015-09-14 21:23         ` Yann E. MORIN
2015-09-14 21:26         ` Arnout Vandecappelle
2015-09-14 21:39           ` Peter Korsgaard [this message]
2015-10-07 16:19             ` Mike Williams
2015-10-07 22:03               ` Arnout Vandecappelle
2015-09-14 21:32         ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2015-09-01 22:55 Yann E. MORIN
2015-09-02  4:54 ` Baruch Siach
2015-09-02  7:10 ` Thomas Petazzoni
2015-09-02 13:50   ` Mike Williams
2015-09-02 14:04     ` Thomas Petazzoni
2015-09-02 14:05       ` Mike Williams
2015-09-02 14:28         ` Yann E. MORIN
2015-09-02 14:07       ` Vicente Olivert Riera
2015-09-02 14:11         ` Yann E. MORIN
2015-09-02 14:12         ` Thomas Petazzoni
2015-09-02 14:13           ` Vicente Olivert Riera
2015-09-02 20:59 ` Arnout Vandecappelle
2015-09-02 21:17   ` Arnout Vandecappelle
2015-09-02 22:09     ` Yann E. MORIN
2015-09-03 14:46       ` Mike Williams
2015-09-03 15:12         ` Vicente Olivert Riera
2015-09-03 15:57           ` Yann E. MORIN
2015-09-02 22:07   ` Yann E. MORIN

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=87vbbcznmq.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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