From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: add options for /bin /sbin and /lib to be symlinks into /usr
Date: Fri, 4 Sep 2015 10:19:24 +0200 [thread overview]
Message-ID: <55E9540C.9060000@mind.be> (raw)
In-Reply-To: <20150904101128.4206779d@free-electrons.com>
On 04-09-15 10:11, Thomas Petazzoni wrote:
> Yann,
>
> On Fri, 4 Sep 2015 01:47:42 +0200, Yann E. MORIN wrote:
>
>> +config BR2_ROOTFS_MERGED_USR
>> + bool "Use symlinks to /usr for /bin, /sbin and /lib"
>
> Shouldn't we make this a blind option? I.e just do merged usr for
> systemd always, and never do it for !systemd.
I will always turn this option on, even in non-systemd, because it makes for a
better environment. See the Fedora document for a long explanation why split
/usr is just legacy baggage. Other parts of your system will also work better
when this option is turned on - no more confusion between busybox installing
something in /bin and the full package putting it in /usr/bin. No more worries
about a shebang being correct.
So no, I don't want this to be hidden.
Regards,
Arnout
--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-09-04 8:19 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 [this message]
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
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=55E9540C.9060000@mind.be \
--to=arnout@mind.be \
--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