Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pud(4) [netbsd man page]

PUD(4)							   BSD Kernel Interfaces Manual 						    PUD(4)

pud -- Pass-to-Userspace Device SYNOPSIS
pseudo-device pud pseudo-device putter DESCRIPTION
The pud driver enables the implementation of block and character device drivers as userspace daemons. The daemons register the device major number they wish to handle. Registering a character device is mandatory, supporting the block device interface for same major device is optional. The major number must be available, i.e. another driver must not be registered to handle the operation. After successful regis- tration the userspace daemon is supposed to handle the driver methods the kernel passes down to it. SEE ALSO
puffs(4), putter(9) BUGS
This document is in a hit-in-the-head style obviously not even near complete. The subsystem lacks a puffs-style library that servers can be written against. BSD
November 21, 2007 BSD

Check Out this Related Man Page

PTY(4)                                                     BSD Kernel Interfaces Manual                                                     PTY(4)

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
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
Man Page