Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 14:55:06 +0000	[thread overview]
Message-ID: <bug-8746-163-AFzxZ21zpT@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8746-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=8746

--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Your boot log shows that the kernel starts /bin/bash directly, but your
configuration shows that you're using systemd as the init system. So things
aren't matching really well here.

Are you booting with init=/bin/sh perhaps? If that's the case, then I believe
it's expected for bash (the shell chosen as the default one in your
configuration) to complain this way, because its standard input/output is
/dev/console.

See https://lists.gnu.org/archive/html/bug-bash/2013-10/msg00097.html for
example.

So, I believe this is not a bug in Buildroot, it is just a misconfiguration of
the system on your side.

Peter, what do you think?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2016-03-10 14:55 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 [this message]
2016-03-10 17:36 ` bugzilla at busybox.net
2016-03-10 20:34 ` 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-8746-163-AFzxZ21zpT@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