From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8746] At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error
Date: Thu, 10 Mar 2016 20:34:43 +0000 [thread overview]
Message-ID: <bug-8746-163-a6kHnvLqJd@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8746-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8746
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|ASSIGNED |RESOLVED
--- Comment #6 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Yes, since 2015.11, we have an option to merge /usr and /. From Buildroot's
CHANGES file:
- Add support for /bin, /sbin and /lib to be symlinks to their
corresponding directories in /usr. This is enforced for
systemd configurations, and optional for other
configurations.
As said above, this is mandatory for systemd (because systemd people expect
such a filesystem layout) and optional in other cases. Since you're using
systemd, this new organization has been automatically enabled.
I'll mark the patch as invalid then. Thanks for following up!
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-03-10 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 22:09 [Buildroot] [Bug 8746] New: At startup system stops with 'cannot set terminal process group (-1): Inappropriate ioctl for device' error bugzilla at busybox.net
2016-03-08 8:27 ` [Buildroot] [Bug 8746] " bugzilla at busybox.net
2016-03-09 1:16 ` bugzilla at busybox.net
2016-03-09 1:17 ` bugzilla at busybox.net
2016-03-10 14:55 ` bugzilla at busybox.net
2016-03-10 17:36 ` bugzilla at busybox.net
2016-03-10 20:34 ` bugzilla at busybox.net [this message]
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-8746-163-a6kHnvLqJd@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.