All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] systemd: write-up and packaging questions
Date: Wed, 15 Oct 2014 20:24:27 +0200	[thread overview]
Message-ID: <543EBBDB.5010500@mind.be> (raw)
In-Reply-To: <543AC16C.7000100@mailerd.de>

On 12/10/14 19:59, Andr? Erdmann wrote:
> Hi,
> 
> Some of the issues pointed out below may be already known, but I couldn't
> find any report on this, so I'd like to share my experience with setting up a
> systemd-based system that does a little bit more than bringing up a console ;)
> Use case was tvheadend with avahi and nfs (+ dropbear etc.), running on a
> DreamPlug. Overall it works great, but requires some post-build actions:
> 
> * installation of additional service files
>   (I'll propose patches for them sooner or later)

 Sooner would be good, because we've had several other reports of systemd not
working.

> * changes to the default rootfs skeleton

 Actually this is the one that should be done soon.

> * optional: removal of /etc/init.d etc.

 Someone is working on that.

> 
> 
> Filesystem Layout
> =================
> 
> There are some issues with the default rootfs skeleton.
> For example, systemd-hostnamed fails to start with the error message
> "file exists", likely related to symlinks pointing to /tmp (/run, /var/...).
> After some trial-and-error I've figured out that both /run and /var/tmp
> symlinks must be replaced with real directories, and that it needs to be done
> before booting systemd (at build/image creation time or in initramfs/initrd).
> 
> So, the minimum amount of necessary changes seems to be:
> * create /run as directory
>   and make /var/run->../run, /var/lock->run/lock link to it;
>   /run gets automatically mounted on boot

 This is something that we can easily do. Except, we should then also mount a
tmpfs on /run in the non-systemd case.

> * create /var/tmp as directory;
>   needs manual mount setup (fstab or .mount unit)

 This also needs to be a tmpfs by the way. Very annoying to have all these tmpfses.

> * /var/lib/dbus is then a dead link pointing to /tmp/dbus,
>   not sure if /run/dbus would be the correct link dest

 Can't we just make /var/lib/dbus/machine-id a symlink to /tmp/machine-id? Or
does that not work?

[snip] Maxime already commented on the rest.


 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2014-10-15 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 17:59 [Buildroot] systemd: write-up and packaging questions André Erdmann
2014-10-12 19:12 ` Maxime Hadjinlian
2014-10-17  8:21   ` Paassen, Hiram van
2014-10-17  9:15     ` André Erdmann
2014-10-17 10:07     ` Maxime Hadjinlian
2014-10-21 18:41       ` Arnout Vandecappelle
2014-10-21 18:45         ` Maxime Hadjinlian
2014-10-15 18:24 ` Arnout Vandecappelle [this message]
2014-10-17  6:32   ` André Erdmann

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=543EBBDB.5010500@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.