From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] fs: clean the volatile /run and /tmp directories
Date: Sun, 7 Jun 2020 10:47:08 +0200 [thread overview]
Message-ID: <20200607104708.1eed13a9@windsurf> (raw)
In-Reply-To: <CADYdroO8PNfE=Cmd96rE-Kfd_nTq_7+h-JLdH-uUPGP3GmsBqg@mail.gmail.com>
On Sun, 7 Jun 2020 00:57:23 +0200
Norbert Lange <nolange79@gmail.com> wrote:
> > However, I'm not sure if removing all what they contain is the right
> > approach. Shouldn't we avoid creating things in /tmp and /run in the
> > first place ?
>
> Yeah we should avoid creating stuff there, but it's sometimes hard to do.
> One example is defining a user with home dir in /run, mkusers will
> then create a dir there
> (pretty late to clear it up otherwise)
But our skeleton has a fstab that always mounts a tmpfs filesystem on
/run, so how can it make sense for mkusers to create a home directory
in /run ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-07 8:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 22:48 [Buildroot] [PATCH 1/2] Makefile: remove /usr/lib/rpm directory on target Norbert Lange
2020-06-05 22:48 ` [Buildroot] [PATCH 2/2] fs: clean the volatile /run and /tmp directories Norbert Lange
2020-06-06 20:42 ` Thomas Petazzoni
2020-06-06 22:57 ` Norbert Lange
2020-06-07 8:47 ` Thomas Petazzoni [this message]
2020-06-07 18:41 ` Norbert Lange
2020-06-10 22:55 ` Norbert Lange
2022-01-09 9:11 ` Arnout Vandecappelle
2020-06-06 20:39 ` [Buildroot] [PATCH 1/2] Makefile: remove /usr/lib/rpm directory on target Thomas Petazzoni
2020-06-06 22:51 ` Norbert Lange
2020-06-07 18:43 ` 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=20200607104708.1eed13a9@windsurf \
--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;
as well as URLs for NNTP newsgroup(s).