From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7892] systemd-journald is broken
Date: Wed, 04 Jan 2017 21:42:14 +0000 [thread overview]
Message-ID: <bug-7892-163-Z7L4LXKv2A@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 #24 from Andrey Smirnov <andrew.smirnov@gmail.com> ---
(In reply to Yann E. MORIN from comment #23)
Yann,
Thank you, this is even better than I could've hoped for!
I have a custom PowerPC (e500) based system I emulate in QEMU (I didn't try
real HW since I could easily reproduce the bug in QEMU) and I did try out both
branches you mentioned. First one definitely fixed the journalctl problems,
second, given how it seem to be missing anything similar to "system: make
systemd work on a read-only rootfs", OTOH didn't (which was expected).
I would love to see your work go upstream sooner rather than later, so if
there's any meaningful way we can collaborate on this, besides me providing
"Tested-by" etc. for your commits, please let me know (feel free to contact me
via e-mail if that's more convenient)
Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-01-04 21:42 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
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 [this message]
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-Z7L4LXKv2A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.