From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] skeleton: make /run a directory
Date: Mon, 01 Dec 2014 18:32:29 -0300 [thread overview]
Message-ID: <547CDE6D.8040303@zacarias.com.ar> (raw)
In-Reply-To: <CAGrucu0UjiXt22U-CFKda+Da8fNMjhszXbh=yixZLTMJ5uTN1Q@mail.gmail.com>
On 12/01/2014 06:19 PM, Andr? Erdmann wrote:
> There are already tmpfiles.d rules for that, /usr/lib/tmpfiles.d/legacy.conf:
>
> d /run/lock 0755 root root -
> L /var/lock - - - - ../run/lock
>
> To make it work properly for systemd, /var/lock needs to be removed
> from the skeleton or point to /run/lock (or replace the "L" with "L+"
> in the tmpfiles.d rule).
Sure, but as i explained to Samuel on IRC this is just the tip of a
general cleanup regarding the base files.
Even though systemd ships that doing more symlinks won't help the
sysv-aspect of the cleanup since /run/lock won't exist whereas now lock
is still /tmp hence no breakage until the other patches are sent/applied.
The idea is to make a script to handle something similar to tmpfiles.d
for sysv-style so we can drop all the symlink hackery which is pointless
for systemd but necessary for sysv, we just stick is as S01basefiles or
some other preferred name.
And also to really move out all of the remaining files that make no
sense for systemd and/or sysv into a basefiles (or other nifty name)
package to avoid noise.
Regards.
next prev parent reply other threads:[~2014-12-01 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 16:48 [Buildroot] [PATCH 1/2] skeleton: make /run a directory Gustavo Zacarias
2014-11-27 16:48 ` [Buildroot] [PATCH 2/2] skeleton/fstab: add /run entry Gustavo Zacarias
2014-12-01 20:39 ` [Buildroot] [PATCH 1/2] skeleton: make /run a directory André Erdmann
2014-12-01 21:01 ` Samuel Martin
2014-12-01 21:12 ` Gustavo Zacarias
2014-12-01 21:19 ` André Erdmann
2014-12-01 21:32 ` Gustavo Zacarias [this message]
2014-12-01 21:59 ` 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=547CDE6D.8040303@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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.