From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: libs transition /usr/lib -> /lib questions
Date: Fri, 6 Jan 2012 09:59:33 -0600 [thread overview]
Message-ID: <4F071A65.90708@windriver.com> (raw)
In-Reply-To: <77ADD6E7-5632-4B1A-ABC3-6E4DAEEAE3B6@dominion.thruhere.net>
On 1/6/12 4:34 AM, Koen Kooi wrote:
>
> Op 6 jan. 2012, om 11:09 heeft Martin Jansa het volgende geschreven:
>
>> FWIW today I've noticed that systemd is going other way around
>> http://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
>
> And http://fedoraproject.org/wiki/Features/UsrMove
>
> I guess it's time to publish my angstrom branch doing that after the holidays :)
I respectfully disagree with both of the above URLs.
The root partition is still very useful as a "small" set of applications and
libraries required for booting.
Most systems these days contain a combined root and usr partition, which is
fine. However, there are a lot of systems that I've worked on in the past and I
expect in the future that, root being a small R/O system is necessary.
initramfs can solve some problems, but introduces other issues. Many of the
systems I've worked on simple don't have enough flash to be able to store the
bootloader, kernel and an initramfs [as well as other system items required by
the devices]. In this case a base rootfs makes the most sense.
So as I mentioned in my previous email -- there are really three options to
supporting this:
*) Move the libraries from /usr to /
*) Move the binaries from / to /usr
*) Reconfigure the binaries to no longer need the library in /usr
---
But with that said, we also should work on making it easier to generate an
initramfs that is capable of premounting all of the filesystems and doing other
actions for an "early boot" capability before handing off control to the real
system. (And I do believe systemd is the future of initscripts within Linux and
OE-Core for the majority of non-simple systems!)
--Mark
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-01-06 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 10:09 libs transition /usr/lib -> /lib questions Martin Jansa
2012-01-06 10:34 ` Koen Kooi
2012-01-06 15:59 ` Mark Hatle [this message]
2012-01-06 16:04 ` Chris Larson
2012-01-06 16:12 ` Mark Hatle
2012-01-06 16:16 ` Richard Purdie
2012-01-06 16:43 ` Koen Kooi
2012-01-06 16:51 ` Mark Hatle
-- strict thread matches above, loose matches on Subject: below --
2012-01-05 23:29 Andreas Müller
2012-01-06 3:35 ` Scott Garman
2012-01-06 13:33 ` Andreas Müller
2012-01-06 10:48 ` Enrico Scholz
2012-01-06 15:48 ` Mark Hatle
2012-01-22 0:05 ` Khem Raj
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=4F071A65.90708@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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