[meta-systemd] base-files and systemd services

[meta-systemd] base-files and systemd services

[Holger Hans Peter Freyther]

Good Morning,

I am playing with meta-oe's meta-systemd and have one issue with the
base-files provided by Poky. networking.service and syslog (busybox)
fail to run as directories like /var/log and /var/run do not exist. In
my images/packagegroup-core-boot I am not installing the the "initscripts"
so I have no LSB service to initialize these directories.

Taking a look at meta-angstrom I found a base-files.bbappend that removes
the "log lock tmp..." symlinks and instead just mounts /var/tmp and /var/run
as tmpfs. In "recent" Poky/OE-Core the syslogd service started to write to
/var/log under the assumption that this is a volatile directory...

I wonder how I should move forward:

a.) Use a tempfiles.d/volatile.conf to create these directories?
b.) Install initscripts in my systemd image?
c.) ???


comments/ideas?

holger

Re: [meta-systemd] base-files and systemd services

[Holger Hans Peter Freyther]

On Fri, Sep 14, 2012 at 10:16:44AM +0200, Holger Hans Peter Freyther wrote:
> Good Morning,
> 
> 
> a.) Use a tempfiles.d/volatile.conf to create these directories?

this does not work due the implementation of systemd-tmpfiles. It might
or might not (depending on the hash of the dir to be created) create the
/var/volatile/tmp dir before it creates /var/log/tmp/wtmp. I will have
to patch the tmp.conf.

> b.) Install initscripts in my systemd image?
> c.) ???

Re: [meta-systemd] base-files and systemd services

[Mark Hatle]

On 9/14/12 6:47 AM, Holger Hans Peter Freyther wrote:
> On Fri, Sep 14, 2012 at 10:16:44AM +0200, Holger Hans Peter Freyther wrote:
>> Good Morning,
>>
>>
>> a.) Use a tempfiles.d/volatile.conf to create these directories?
>
> this does not work due the implementation of systemd-tmpfiles. It might
> or might not (depending on the hash of the dir to be created) create the
> /var/volatile/tmp dir before it creates /var/log/tmp/wtmp. I will have
> to patch the tmp.conf.
>
>> b.) Install initscripts in my systemd image?
>> c.) ???

I'd suggest two possible fixes, the first is somewhat "obvious" to me.  Fix the 
setup/initialization scripts to make sure /var/volatile is setup/mounted before 
systemd starts doing it's stuff....

But the alternative (if that is not reasonable or possible), create a custom 
"fs-perms.txt" to describe a functional filesystem layout for a systemd based 
configuration.  (This can be carried in the systemd layer.)

--Mark

> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>