Skip to contentSkip to conversation

2.6-test4 Traditional pty and devfs

DISCUSSION Albert Cahalan 2 participants 2 messages Sep 3, 2003

lore
Share & tools
lore
#0 lore raw
Quoted 6 lines · Christoph Hellwig
Quoted 4 lines · Andrew Morton
Quoted 3 lines

That's the magic use uid/gid of the process calling devfs_Register flag I killed. With a big HEADSUP and explanation on lkml..

Quoted 6 lines
Quoted 2 lines

So what is the impact here? That libc5 will break if the user is using devfs and old-style pty's?

If he removed the pt_chown logic that is present with a stock libc5, yes. I wouldn't know why someone would do that, though.

The problem may be more serious. There are lots of apps that use the old-style PTYs w/o any libc help.

a. because that's the historic BSD way
b. so the user can choose a specific pty

For example, there's a "remserial" program that abuses a PTY for giving access to a serial port over the network. Apps trying to use the port work pretty well, without any need for source code changes or new kernel drivers.

#1 lore raw
Quoted 2 lines · Albert Cahalan

The problem may be more serious. There are lots of apps that use the old-style PTYs w/o any libc help.

That's not a problem, just bad design. It continues to work as always, i.e. you don't get an automic chown. For that you either needs the libc interface with the pt_chown helper of UNIX98 ptys.