From: Ian Soboroff <ian@cs.umbc.edu>
To: linux-kernel@vger.kernel.org
Subject: devfs vs. devpts
Date: 16 Mar 2001 08:45:35 -0500 [thread overview]
Message-ID: <87vgp9zv28.fsf@danube.cs.umbc.edu> (raw)
I'm running 2.4.2ac7, and am having problems with Unix98 ptys.
Occasionally rxvt and Eterm fail to run because they can't get
permission to create their entry in /dev/pts. So i wondered if i have
a devfs problem, which led me to the following...
In Documentation/filesystems/devfs/README, it is thus written:
Disable devpts
I've had a report of devpts mounted on /dev/pts
not working correctly. Since devfs will also manage /dev/pts,
there is no need to mount devpts as well. You should either
edit your /etc/fstab so devpts is not mounted, or disable
devfs from your kernel configuration.
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':
drivers/char/char.o: In function `pty_close':
drivers/char/char.o(.text+0x6646): undefined reference to `devpts_pty_kill'
make: *** [vmlinux] Error 1
so the devfs documentation is wrong; pty_close depends on
functionality from devpts. and secondly, has anyone else had problems
under 2.4.x creating entries in /dev/pts?
ian
--
----
Ian Soboroff ian@cs.umbc.edu
University of MD Baltimore County http://www.cs.umbc.edu/~ian
next reply other threads:[~2001-03-16 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 13:45 Ian Soboroff [this message]
2001-03-16 15:43 ` devfs vs. devpts John Jasen
2001-03-16 17:30 ` Nathan Walp
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=87vgp9zv28.fsf@danube.cs.umbc.edu \
--to=ian@cs.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