SYSV_PTY(8) System Manager's Manual SYSV_PTY(8)NAME
SYSV_PTY - Makes the system use the SVR4 pseudo terminal name space
SYNOPSIS
/dev/SYSV_PTY
DESCRIPTION
The SYSV_PTY shell script activates the SVR4 pty (pseudo terminal) name space as the default. The SVR4 pty special files have a name in
the form of /dev/pts/N. The SYSV_PTY shell script takes no arguments. To reactivate the BSD pseudoterminal name space, invoke the MAKEDEV
command to create the pty special files.
SEE ALSO
Commands: MAKEDEV(8)
Files: pty(7)SYSV_PTY(8)
Check Out this Related Man Page
PTY(4) BSD Kernel Interfaces Manual PTY(4)NAME
pty -- BSD-style compatibility pseudo-terminal driver
SYNOPSIS
device pty
DESCRIPTION
The pty driver provides support for the traditional BSD naming scheme that was used for accessing pseudo-terminals. When the device
/dev/ptyXX is being opened, a new terminal shall be created with the pts(4) driver. A device node for this terminal shall be created, which
has the name /dev/ttyXX.
New code should not try to allocate pseudo-terminals using this interface. It is only provided for compatibility with older C libraries that
tried to open such devices when posix_openpt(2) was being called.
FILES
The BSD-style compatibility pseudo-terminal driver uses the following device names:
/dev/pty[l-sL-S][0-9a-v] Pseudo-terminal master devices.
/dev/tty[l-sL-S][0-9a-v] Pseudo-terminal slave devices.
DIAGNOSTICS
None.
SEE ALSO posix_openpt(2), pts(4), tty(4)HISTORY
A pseudo-terminal driver appeared in 4.2BSD.
BUGS
Unlike previous implementations, the master slave device nodes are destroyed when the PTY becomes unused. A call to stat(2) on a nonexistent
master device will already cause a new master device node to be created. The master device can only be destroyed by opening and closing it.
The pty driver cannot be unloaded, because it cannot determine if it is being used.
BSD August 20, 2008 BSD
Hi Folks,
Today hasn't been the best one of my career in IT.
I've been a contractor for a major utility company for a number of years, on a number of seperate IT contracts mostly Unix. The company had 10 different flavours of unix and multiple different varsions of most of them.
At the... (3 Replies)