From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8081] New: systemd init system: /tmp is not mode 1777
Date: Sun, 3 May 2015 13:05:00 +0000 (UTC) [thread overview]
Message-ID: <bug-8081-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8081
Summary: systemd init system: /tmp is not mode 1777
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: bos at je-eigen-domein.nl
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Using:
- latest buildroot from git
- start with raspberrypi2_defconfig
- set systemd as init system
- initramfs linked into kernel
/tmp is not mode 1777 causing software that does not run as root and wants to
write to /tmp or (linked folders like /var/log) to fail.
==
# ls -ld /tmp
drwxr-xr-x 7 root root 220 Jan 1 00:00 /tmp
==
Also tmpfiles service fails to start:
==
systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static;
vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 1970-01-01 00:00:06 UTC; 2min
8s ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 131 ExecStart=/bin/systemd-tmpfiles --create --remove --boot
--exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 131 (code=exited, status=1/FAILURE)
==
And logging is not functional:
==
# journalctl
No journal files were found.
==
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2015-05-03 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 13:05 bugzilla at busybox.net [this message]
2015-07-07 21:02 ` [Buildroot] [Bug 8081] systemd init system: /tmp is not mode 1777 bugzilla at busybox.net
2015-08-04 19:01 ` bugzilla at busybox.net
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=bug-8081-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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