All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lech Szychowski <lech.szychowski@pse.pl>
To: linux-kernel@vger.kernel.org
Subject: getty problems
Date: Mon, 6 Aug 2001 14:27:04 +0200	[thread overview]
Message-ID: <20010806142703.A25428@lech.pse.pl> (raw)

In short: on 2.4.7-ac[3-7] getty cannot open /dev/ttyX,
while on 2.4.5 it can.

I've done "strace -o /tmp/GETTY-`uname -r` /sbin/getty tty9 vc linux"
in both cases and compared otput files. The big difference is here:

2.4.5:
open("/dev/tty9", O_RDWR|O_NONBLOCK)    = 0

2.4.7-ac7:
open("/dev/tty9", O_RDWR|O_NONBLOCK)    = -1 ENODEV (No such device)

And yes, I believe I have terminal support compiled in:

===
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
===

$ gcc -v      
Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/2.95.3/specs
gcc version 2.95.3 20010315 (release)

This problem hit me when I compiled and installed new kernel
(2.4.5 comes with the distribution) - I could not log in because
all gettys got disabled:

Aug  6 14:10:09 nnet /sbin/agetty[103]: /dev/tty6: cannot open as standard input: No such device
Aug  6 14:10:09 nnet init: Id "c4" respawning too fast: disabled for 5 minutes

-- 
	Leszek.

-- lech7@pse.pl 2:480/33.7          -- REAL programmers use INTEGERS --
-- speaking just for myself...

             reply	other threads:[~2001-08-06 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06 12:27 Lech Szychowski [this message]
2001-08-06 12:30 ` getty problems Chris Wedgwood
2001-08-06 13:45   ` Lech Szychowski
2001-08-06 14:09     ` Chris Wedgwood
2001-08-06 16:24       ` Lech Szychowski
2001-08-06 22:06         ` H. Peter Anvin
2001-08-06 23:17           ` Richard Gooch

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=20010806142703.A25428@lech.pse.pl \
    --to=lech.szychowski@pse.pl \
    --cc=linux-kernel@vger.kernel.org \
    /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.