Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: Why is systemd installed to / (was: [yocto] Export bitbake variables between recipes)
Date: Wed, 3 Dec 2014 09:46:34 -0600	[thread overview]
Message-ID: <547F305A.5060305@windriver.com> (raw)
In-Reply-To: <A612847CFE53224C91B23E3A5B48BAC7ACF18D42B6@xmail3.se.axis.com>

On 12/3/14, 9:36 AM, Peter Kjellerstedt wrote:
>>> Can anyone please explain why OE-core installs systemd to / rather
>>> than /usr? Because I have traced the recipe all the way back to its
>>> introduction in OE classic, and I cannot find any rationale for
>>> this odd decision. And it is extra weird given the systemd authors'
>>> agenda that everything should be in /usr (and /etc)...
>>
>> It's only strange compared to Fedora.  We're not Fedora.. and I've
>> got systems that need to boot from a small '/' before mounting '/usr'.
>
> Speaking of Fedora, would an official image feature, e.g., "unified-fs",
> be acceptable for OE-Core that sets up the file system with /bin, /sbin
> and /lib* as links to their /usr counterparts? That would alleviate our
> problems with the differences in how systemd is installed.

The system permits developers to set the paths for the various pieces.  To get a 
Fedora like unified filesystem, you could do something like:

* provide your own fs-perms.txt:

/usr/bin	link	${base_bindir}
/usr/sbin	link	${base_sbindir}
/usr/lib	link	${base_libdir}

Then in your local.conf:

bindir = "${base_bindir}"
sbindir = "${base_sbindir}"
libdir = "${base_libdir}"


This will result in /usr/bin, sbin and lib being linked to /bin, /sbin, /lib -- 
and all of the package produced for your configuration will only reference '/'.

This isn't that unusual of a configuration from what I've been told.

--Mark

>> (In prior discussions we've made the decision to not fix every library
>> or application, but there is a warning you can enable that will show
>> you what libraries and applications live in '/' but have obvious
>> linkage to '/usr'.)
>>
>>>> (Another alternative is pkg-config, but I don't think that really
>>>> applies in this situation.)
>>>
>>> Nope.
>>>
>>>> Cheers,
>>>> Paul
>>>>
>>>> --
>>>>
>>>> Paul Eggleton
>>>> Intel Open Source Technology Centre
>>>
>>> //Peter
>
> //Peter
>



  reply	other threads:[~2014-12-03 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 18:27 Why is systemd installed to / (was: [yocto] Export bitbake variables between recipes) Peter Kjellerstedt
2014-12-02 18:44 ` Mark Hatle
2014-12-03 15:36   ` Peter Kjellerstedt
2014-12-03 15:46     ` Mark Hatle [this message]
2014-12-04 13:34       ` Peter Kjellerstedt
2014-12-05  3:00         ` ChenQi
2014-12-05  3:46           ` Mark Hatle
2014-12-08  7:44             ` Adrian Freihofer
2014-12-08 13:37           ` Peter Kjellerstedt

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=547F305A.5060305@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    /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