Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #575
Difficulty: Medium
If a program has poor memory management and fails to deallocate memory when it is no longer needed, the memory will not leak.
True or False?
Linux & Unix Commands - Search Man Pages

autoconfig(8) [bsd man page]

AUTOCONFIG(8)						      System Manager's Manual						     AUTOCONFIG(8)

NAME
autoconfig - configure the running system to the hardware SYNOPSIS
autoconfig [-i ifile] [-n nfile] [-k kfile] [-v] [-d] [-c] DESCRIPTION
Autoconfig is called by init(8) to configure the currently running system. Init checks the exit status of autoconfig to determine if the configuration was successful. Autoconfig reads the device table /etc/dtab for a list of devices which may be on the system. It first ver- ifies that the kernel has an attach routine for each device (and therefore has a device handler) and that the kernel has a probe routine. It then checks each of these devices to see if it is present, and if it is, attempts to make it interrupt (if possible) to verify that the interrupt vector is correct. The interrupt vector is checked to see that it has not previously been used. An interrupt through any of the device's consecutive vectors is sufficient. Devices which use programmable vectors (MSCP and TMSCP) are permitted to have a value of 0 in the dtab vector field. This special value tells autoconfig to call the kernel's get next available vector routine and assign that to the device. For programmable vector devices if the dtab vector field is non 0 then the value specified in the dtab file is used. In both cases the driver is called at its xxVec() rou- tine with the vector being assigned to the device. If the address and vector are correct, it then attaches the device by passing the address and unit number to the kernel's attach routine and setting up the interrupt vector according to the interrupt handlers and priority listed in the device table. If the unit number is given as a '?' in the device table, it will be assigned the next available unit number if the device exists. If the device is not present or the vector is incorrect, and if the unit number was specified (not a '?'), then the kernel is notified that that unit is not present, preventing accesses to a nonexistent device address. There are only a few flags which are mostly useful for debugging but for completeness, here they are. -i ifile Use ifile instead of /etc/dtab as the device table. -n nfile Use nfile instead of /unix for finding the namelist of the currently running kernel. -k kfile The file kfile should be used instead of /dev/kmem to alter and read kernel memory. -v Verbose output, indicates reason for rejecting any device in the device table. Normally only attached devices are reported. -c Report error messages for devices skipped because of problems with their interrupt vectors. -d Turn on debugging mode. Shows many gory details of autoconfig's internal processing. BUGS
Devices of the same type must be listed with ascending unit numbers or with wildcards. Disks that could be root devices must have their addresses and vectors initialized in the kernel; the kernel uses a root attach entry in the block device switch to allow disk drivers to do any probes necessary before autoconfiguration. Must be run only by init(8). There is a flag set in the kernel that autoconfig has already run, running autoconfig a second time results in the error: "namelist doesn't match running kernel." Autoconfig attempts to open /dev/kmem for write. If the kernel is in securelevel 1 or higher the open of /dev/kmem will fail. FILES
/etc/dtab device table /unix /dev/kmem SEE ALSO
ucall(2), nlist(3), dtab(5) 3rd Berkeley Distribution December 30, 1992 AUTOCONFIG(8)

Check Out this Related Man Page

DZ(4)							     Kernel Interfaces Manual							     DZ(4)

NAME
dz - DZ-11 communications multiplexer SYNOPSIS
/sys/conf/SYSTEM: NDZ dz_units # DZ11; NDZ is in units of boards (8 each) /etc/dtab: #Name Unit# Addr Vector Br Handler(s) # Comments dz ? 160100 310 5 dzrint dzdma # dz11 terminal mux major device number: raw: 2 minor device encoding: bits 0007 specify line on DZ unit bits 0170 specify DZ unit bit 0200 specifies non-blocking open (``CD always on'') DESCRIPTION
A DZ11 provides 8 communication lines with partial modem control, adequate for UNIX dialup use. Each line attached to the DZ11 communica- tions multiplexer behaves as described in tty(4) and may be set to run at any of 16 speeds; see tty(4) for the encoding. Bit 0200 of the minor device number for DZ lines may be set to say that a line is not properly connected, and that the line should be treated as hard-wired with carrier always present. Thus creating the special character device node "2, 130" via mknod /dev/tty02 c 2 130 would cause line tty02 to be treated in this way. The dz driver monitors the rate of input on each board, and switches between the use of character-at-a-time interrupts and input silos. While the silo is enabled during periods of high-speed input, the driver polls for input 30 times per second. FILES
/dev/tty[0-9][0-9] /dev/ttyd[0-9a-f] dialups /dev/MAKEDEV script to create special files /dev/MAKEDEV.local script to localize special files SEE ALSO
tty(4), dtab(5), autoconfig(8) DIAGNOSTICS
dz%d: silo overflow. The 64 character input silo overflowed before it could be serviced. This can happen if a hard error occurs when the CPU is running with elevated priority, as the system will then print a message on the console with interrupts disabled. It is not serious. 3rd Berkeley Distribution January 28, 1988 DZ(4)

Featured Tech Videos