From: Pavel Roskin <proski@gnu.org>
To: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.68-bk1 crash in devfs_remove() for defpts files
Date: Mon, 21 Apr 2003 16:56:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.55.0304211647270.2742@marabou.research.att.com> (raw)
In-Reply-To: <1050957875.1224.2.camel@flat41>
On Mon, 21 Apr 2003, Grzegorz Jaskiewicz wrote:
> you must mount devpts in /dev/pts
It is mounted, in case if you missed the beginning of the discussion.
> 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
But I don't have /dev/vc/1 because ...
> > The only entry under /dev/vc is /dev/vc/0. /dev/tts is missing.
This was caused by Christoph's patch he posted in this thread. I'm not
familiar with internals of devfs and character devices. I'm just trying
to help Christoph to come to the right solution.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2003-04-21 20:44 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
2003-04-21 20:56 ` Pavel Roskin [this message]
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=Pine.LNX.4.55.0304211647270.2742@marabou.research.att.com \
--to=proski@gnu.org \
--cc=gj@pointblue.com.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 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).