From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 23194-done@debbugs.gnu.org
Subject: bug#23194: Benign error in installation image: "stty: standard input: Input/output error"
Date: Thu, 07 Dec 2017 10:18:16 +0100 [thread overview]
Message-ID: <874lp2dhgn.fsf@gnu.org> (raw)
In-Reply-To: <87fuv1ctrz.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 04 Apr 2016 16:50:40 +0200")
Hi Chris,
ludo@gnu.org (Ludovic Courtès) skribis:
> Chris Marusich <cmmarusich@gmail.com> skribis:
>
>> In the installation image for GuixSD v0.10.0, I get some I/O errors on
>> the terminal just before/during/after the MOTD is displayed:
>>
>> "stty: standard input: Input/output error"
>
> These appear to come from the ‘unicode_start’ command, run by the
> ‘console-font’ services. ‘unicode_start’ is a shell script in the ‘kbd’
> package that does:
>
> stty iutf8
>
> In a ‘guix system vm gnu/system/install.scm’ VM in current master, I
> sometimes get a different message:
>
> unicode_start skipped on not a tty
>
> The “not a tty” string comes from the ‘tty’ command (Coreutils). We get
> it when:
>
> ttyname (STDIN_FILENO);
>
> returns NULL; this can happen if ‘tcgetattr’ returns NULL (see ttyname.c
> in libc.)
I’m happy to say that this is fixed in the 0.14.0 installation image:
https://git.savannah.gnu.org/cgit/guix.git/commit/?h=version-0.14.0&id=787e8a80d54d8bd5320d76276dc5f4bafe5b86c0
We now use our ‘tcsetattr’ bindings directly instead of invoking
‘unicode_start’. Additionally, we wait until the TTY really exists
(i.e., mingetty has become its session leader) by checking the return
value of ‘ttyname’.
Ludo’.
next prev parent reply other threads:[~2017-12-07 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 21:09 bug#23194: Benign error in installation image: "stty: standard input: Input/output error" Chris Marusich
2016-04-03 6:27 ` Efraim Flashner
2016-04-03 6:52 ` Chris Marusich
2016-04-04 14:50 ` Ludovic Courtès
2017-12-07 9:18 ` Ludovic Courtès [this message]
2016-04-04 15:10 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lp2dhgn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=23194-done@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).