From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7892] systemd-journald is broken
Date: Sat, 10 Sep 2016 13:19:25 +0000 [thread overview]
Message-ID: <bug-7892-163-y22A0VWiXN@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-7892-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=7892
--- Comment #18 from Floris Bos <bos@je-eigen-domein.nl> ---
(In reply to Maxime Hadjinlian from comment #15)
>maybe I need to find some SAMA5 board somewhere,
>maybe theres' something special about this board, but as is, I really can't reproduce
Minimal steps to reproduce if you do have a Pi 3 laying around:
make raspberrypi3_defconfig
make menuconfig
"toolchain" -> "c library" -> "glibc"
"system configuration" -> "init system" -> "systemd"
"system configuration" -> "getty" -> "TTY port" -> tty1 (the default value
"console" is currently broken with systemd)
"filesystem images" -> enable "initial RAM file system linked into linux
kernel"
make
Copy output/images/zImage output/images/*.dtb output/images/rpi-firmware/* to a
FAT formatted SD card, stick it in the Pi, and boot it
Type "journalctl" and notice that it claims that "No journal files were found."
I would argue that a configuration as simple as this should just work
out-of-the-box, without post-build anything.
In this example config buildroot produces the initramfs. But it also happens if
you have a normal file system, but there is another initramfs that mounts the
root filesystem rw, and passes control over to you with switch_root.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-09-10 13:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 9:54 [Buildroot] [Bug 7892] New: systemd-journald is broken bugzilla at busybox.net
2015-02-27 9:55 ` [Buildroot] [Bug 7892] " bugzilla at busybox.net
2015-02-27 9:55 ` bugzilla at busybox.net
2015-02-27 9:55 ` bugzilla at busybox.net
2015-02-27 9:58 ` bugzilla at busybox.net
2015-02-28 15:20 ` bugzilla at busybox.net
2015-02-28 15:55 ` bugzilla at busybox.net
2015-02-28 16:27 ` bugzilla at busybox.net
2015-03-01 20:39 ` bugzilla at busybox.net
2015-03-02 7:40 ` bugzilla at busybox.net
2015-03-02 7:55 ` bugzilla at busybox.net
2015-03-02 8:01 ` bugzilla at busybox.net
2015-03-02 8:02 ` bugzilla at busybox.net
2015-05-07 8:15 ` bugzilla at busybox.net
2015-08-08 16:04 ` bugzilla at busybox.net
2016-02-01 23:38 ` bugzilla at busybox.net
2016-09-10 11:14 ` bugzilla at busybox.net
2016-09-10 12:04 ` bugzilla at busybox.net
2016-09-10 13:19 ` bugzilla at busybox.net [this message]
2016-09-10 13:30 ` bugzilla at busybox.net
2016-09-10 13:46 ` bugzilla at busybox.net
2016-09-10 13:53 ` bugzilla at busybox.net
2017-01-03 19:45 ` bugzilla at busybox.net
2017-01-03 20:11 ` bugzilla at busybox.net
2017-01-04 21:42 ` bugzilla at busybox.net
2017-01-06 3:54 ` bugzilla at busybox.net
2017-08-02 19:07 ` 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-7892-163-y22A0VWiXN@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