[Buildroot] [PATCH] skeleton: make /run a proper directory/filesystem
danomimanchego123 at gmail.com
Tue Feb 3 16:04:13 UTC 2015
On Tue, Feb 3, 2015 at 9:58 AM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> Dear Gustavo Zacarias,
> On Thu, 27 Nov 2014 19:41:49 -0300, Gustavo Zacarias wrote:
>> Making /var/run and /run symlinks to /tmp is bad since the underlying
>> tmpfs filesystem is mode 1777 which leads to possible security attack
>> vectors via badly owned/mask-mode pidfiles and state files residing there.
>> So make /run a proper directory with /var/run symlinked to it.
>> Eventually all startup scripts and state info should be pointed to /run
>> directly as per the linux fhs and good practice.
>> Add a tmpfs filesystem entry for /run so that busybox inittab, systemv
>> inittab and systemd automount mounts it there to avoid breaking the
>> While at it fix inconsistent spacing in /etc/fstab by using tabs and
>> drop the "static file system information" header whatever that means.
>> Signed-off-by: Gustavo Zacarias <gustavo at zacarias.com.ar>
> Applied, thanks!
When I pulled, I got a broken symlink, to 'run?' instead of 'run'. Is
$ ls -al system/skeleton/var/run
lrwxrwxrwx 1 dano dano 7 Feb 3 11:00 system/skeleton/var/run -> ../run?
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> buildroot mailing list
> buildroot at busybox.net
More information about the buildroot