From: Nathan Walp <faceprint@faceprint.com>
To: John Jasen <jjasen1@umbc.edu>
Cc: Ian Soboroff <ian@cs.umbc.edu>, linux-kernel@vger.kernel.org
Subject: Re: devfs vs. devpts
Date: Fri, 16 Mar 2001 12:30:46 -0500 [thread overview]
Message-ID: <3AB24DC6.BE0C4D2F@faceprint.com> (raw)
In-Reply-To: <Pine.SGI.4.31L.02.0103161039010.205553-100000@irix2.gl.umbc.edu>
John Jasen wrote:
>
> On 16 Mar 2001, Ian Soboroff wrote:
>
> > i don't have devpts mounted under 2.4.2 (debian checks whether you
> > have devfs before mounting devpts), so i tried building my kernel with
> > Unix 98 pty support but without the devpts filesystem. i get the
> > following error at the very end of 'make bzImage':
>
> snipped from .config:
>
> #
> # Character devices
> #
> CONFIG_VT=y
> CONFIG_VT_CONSOLE=y
> CONFIG_SERIAL=y
> # CONFIG_SERIAL_CONSOLE is not set
> # CONFIG_SERIAL_EXTENDED is not set
> # CONFIG_SERIAL_NONSTANDARD is not set
> CONFIG_UNIX98_PTYS=y
> CONFIG_UNIX98_PTY_COUNT=256
>
> #
> # File systems
> #
> CONFIG_DEVFS_FS=y
> CONFIG_DEVFS_MOUNT=y
> CONFIG_DEVFS_DEBUG=y
> ...
> # CONFIG_DEVPTS_FS is not set
>
> from my /etc/devfsd.conf, I have:
> REGISTER pts/.* MKOLDCOMPAT
> UNREGISTER pts/.* RMOLDCOMPAT
>
> and for permissions:
> REGISTER pts/.* IGNORE
>
I had the same problem, so i added those devfsd lines to my config
files, and everything's peachy now. I'm thinking it's a debian problem,
cause everything was fine till I ran a dist-upgrade. I didn't notice it
right away, and I did random kernel stuff before I did notice it. Ian,
which debian are you running, I'm using sid.
Nathan
prev parent reply other threads:[~2001-03-16 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 13:45 devfs vs. devpts Ian Soboroff
2001-03-16 15:43 ` John Jasen
2001-03-16 17:30 ` Nathan Walp [this message]
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=3AB24DC6.BE0C4D2F@faceprint.com \
--to=faceprint@faceprint.com \
--cc=ian@cs.umbc.edu \
--cc=jjasen1@umbc.edu \
--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