linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: Pavel Roskin <proski@gnu.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.68-bk1 crash in devfs_remove() for defpts files
Date: 21 Apr 2003 21:44:35 +0100	[thread overview]
Message-ID: <1050957875.1224.2.camel@flat41> (raw)
In-Reply-To: <Pine.LNX.4.55.0304211630230.2599@marabou.research.att.com>

On Mon, 2003-04-21 at 21:35, Pavel Roskin wrote:
> > Oh, I see now.  There's a longstanding bug in the handling of
> > TTY_DRIVER_NO_DEVFS that got exposed by this.
> >
> > Please try this patch additionally:
> 
> Applied.  Now I can log in by ssh and there are no problems with
> pseudoterminals.  However, all local terminals are gone:
> 
> INIT: Id "1" respawning too fast: disabled for 5 minutes
> INIT: Id "2" respawning too fast: disabled for 5 minutes
> INIT: Id "3" respawning too fast: disabled for 5 minutes
> INIT: Id "5" respawning too fast: disabled for 5 minutes
> INIT: Id "4" respawning too fast: disabled for 5 minutes
> INIT: Id "6" respawning too fast: disabled for 5 minutes
> INIT: Id "S0" respawning too fast: disabled for 5 minutes
> INIT: no more processes left in this runlevel
> 
you must mount devpts in /dev/pts
and change inittab :
[snip]
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run
X.
#
1:2345:respawn:/sbin/getty 38400 /dev/vc/1
2:23:respawn:/sbin/getty 38400 /dev/vc/2
3:23:respawn:/sbin/getty 38400 /dev/vc/3
4:23:respawn:/sbin/getty 38400 /dev/vc/4
5:23:respawn:/sbin/getty 38400 /dev/vc/5
6:23:respawn:/sbin/getty 38400 /dev/vc/6
[snip]

to use devfs only, it is funny but fe to open /dev/sound/* you need to
be root, or chmod it manually before use. (i've got seperate
/etc/init.d/chdevfsmod file to do that)

> The only entry under /dev/vc is /dev/vc/0.  /dev/tts is missing.
-- 
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 labs


  reply	other threads:[~2003-04-21 20:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-21 17:49 [PATCH] 2.5.68-bk1 crash in devfs_remove() for defpts files Pavel Roskin
2003-04-21 17:55 ` Christoph Hellwig
2003-04-21 17:58   ` Christoph Hellwig
2003-04-21 18:53     ` Pavel Roskin
2003-04-21 19:00       ` Christoph Hellwig
2003-04-21 19:44         ` Pavel Roskin
2003-04-21 19:56           ` Christoph Hellwig
2003-04-21 20:35             ` Pavel Roskin
2003-04-21 20:44               ` Grzegorz Jaskiewicz [this message]
2003-04-21 20:56                 ` Pavel Roskin
2003-04-24  7:39                 ` Martin Schlemmer
2003-04-24  7:57                   ` Grzegorz Jaskiewicz
2003-04-24 11:46                     ` Martin Schlemmer
2003-04-24 12:03                       ` Grzegorz Jaskiewicz
2003-04-21 20:57               ` Christoph Hellwig
2003-04-21 21:15                 ` Pavel Roskin
2003-04-21 21:23                   ` Christoph Hellwig
2003-04-21 21:45                     ` Pavel Roskin
2003-04-21 22:25                       ` Christoph Hellwig
2003-04-21 22:37                         ` Pavel Roskin
2003-04-22 10:12 Chuck Ebbert

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=1050957875.1224.2.camel@flat41 \
    --to=gj@pointblue.com.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.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 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 NNTP newsgroup(s).