From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Fix dhcp symlink in target/var/lib/dhcp
Date: Mon, 24 Oct 2016 23:01:38 +0200 [thread overview]
Message-ID: <20161024230138.398810a4@free-electrons.com> (raw)
In-Reply-To: <25c03ce6-8771-cd39-32ef-b815ede292f6@mind.be>
Hello,
On Thu, 6 Oct 2016 01:20:56 +0200, Arnout Vandecappelle wrote:
> > Changing the symlink to "../../tmp" rather than "/tmp" references the
> > target's /tmp directory rather than the build machine's /tmp directory.
>
> The problem is that /var/lib itself may be a symlink to somewhere else. Some
> people need to have /var/lib in a writeable partition while /var itself is on
> the readonly rootfs. When /var/lib is a symlink, the ../.. will be interpreted
> relative to the target of that symlink, which may be a different number of
> levels down from root.
>
> Also, since /tmp always exists on the build machine, symlinking to /tmp just works.
Note that the skeleton already installs /var/lib/misc -> ../../tmp
However, since this is part of the skeleton, one can assume that those
folks who replace /var/lib with a symlink will adapt the skeleton
accordingly (by using their own custom skeleton).
However, there's one thing I'm not entirely happy with with the
current /var/lib -> /tmp symlink. It means that the Buildroot build
will potentially install random stuff in /tmp. This doesn't seem really
nice.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-10-24 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 16:07 [Buildroot] [PATCH] Fix dhcp symlink in target/var/lib/dhcp Root, Build
2016-10-05 23:20 ` Arnout Vandecappelle
2016-10-06 17:38 ` Jerry Van Baren
2016-10-06 19:22 ` Arnout Vandecappelle
2016-10-06 21:02 ` Jerry Van Baren
2016-10-24 21:01 ` Thomas Petazzoni [this message]
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=20161024230138.398810a4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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