Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system/skeleton: make /var/run a symlink to /run
Date: Wed, 15 Jul 2020 15:43:38 +0200	[thread overview]
Message-ID: <20200715154338.1e52ffe5@windsurf.home> (raw)
In-Reply-To: <CADYdroM9wPyVGM2_oAcKcMYBHjYdfEPrd7YKL5QozGP3kDXPHA@mail.gmail.com>

On Tue, 14 Jul 2020 16:22:25 +0200
Norbert Lange <nolange79@gmail.com> wrote:

> chronological:
> 
> -   Buildroot uses /var/run as RUNTIME directory for SysV, and /run for systemd.
> -   I add the lttng patch above to use either /var/run/lttng or /run/lttng
> -   I consider doing the same for dbus as I get warnings otherwise
> (actually have a post_install script replacing /var/run with /run)
> -   I consider it would be alot easier to just use /run everywhere and
> add this patch to see if that's accepted, before doing more
> if-butt-ing like with lttng

But then, you have to anyway tweak lttng to pass:

LTTNG_LIBUST_CONF_OPTS += --with-lttng-system-rundir=/run/lttng

but unconditionally, and no longer depending on whether systemd is used
or not. Correct ?

But... /run is already a tmpfs in sysv-based systems, so what prevents
today from using /run/lttng even for sysv based systems ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-07-15 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 10:47 [Buildroot] [PATCH] system/skeleton: make /var/run a symlink to /run Norbert Lange
2020-06-29 10:52 ` Norbert Lange
2020-07-14 13:14 ` Thomas Petazzoni
2020-07-14 13:35   ` Norbert Lange
2020-07-14 13:52     ` Thomas Petazzoni
2020-07-14 14:22       ` Norbert Lange
2020-07-15 13:43         ` Thomas Petazzoni [this message]
2020-07-15 13:53           ` Norbert Lange
2020-07-15 15:38             ` Thomas Petazzoni
2020-07-16  9:42               ` Norbert Lange

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=20200715154338.1e52ffe5@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox