public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* devfs vs. devpts
@ 2001-03-16 13:45 Ian Soboroff
  2001-03-16 15:43 ` John Jasen
  0 siblings, 1 reply; 3+ messages in thread
From: Ian Soboroff @ 2001-03-16 13:45 UTC (permalink / raw)
  To: linux-kernel


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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-03-16 17:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox