02.07.2013 Views

A/UX® System Administrator's Reference Sections 1M, 7, and 8

A/UX® System Administrator's Reference Sections 1M, 7, and 8

A/UX® System Administrator's Reference Sections 1M, 7, and 8

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

intro(7) intro(7)<br />

NAME<br />

intro - introduction to device drivers <strong>and</strong> interfaces<br />

DESCRIPTION<br />

The entries in this section provide useful information for users <strong>and</strong><br />

programmers, although programmers may be able to benefit more.<br />

Users need to know what device files are typically associated with<br />

which devices or ports so that the comm<strong>and</strong>s that accept device<br />

files as arguments can be specified accurately. For example,<br />

/dev/ttyO <strong>and</strong> /dev/ttyl refer to serial ports, <strong>and</strong><br />

/dev/dsk/eOdOsO through /dev/dsk/e7dOsO refer to<br />

slice 0 of each of the hard disks set to SCSI ID 0 through 7.<br />

To rebuild or make custom-named device files, users need to<br />

know what major device numbers correspond to particular device<br />

drivers, as well as the operational or addressing modes selected by<br />

the minor device numbers associated with a particular device<br />

driver. Note that the NUX autoconfiguration utilities automatically<br />

create <strong>and</strong> remove device files (with default filenames)<br />

whenever necessary for a particular device configuration they are<br />

establishing (see autoeonfig(IM), neweonfig(IM), <strong>and</strong><br />

newunix(IM)).<br />

This section also includes information helpful to readers who wish<br />

to manipulate a device directly through its corresponding interface.<br />

For example, you can format a cartridge tape through the<br />

general rot device interface to tape devices. These device-level<br />

interfaces allow access to device-specific functions, such as cartridge<br />

tape formatting, that would not normally be available as a<br />

st<strong>and</strong>ard operation for all tape devices. Non-universal operations<br />

typically would not be available through the flag options for the<br />

st<strong>and</strong>ard programs, such as tar <strong>and</strong> epio, described in Section 1<br />

of A/UX Comm<strong>and</strong> <strong>Reference</strong>.<br />

Programmers who wish to write programs that can access all the<br />

peculiarities of specific devices may find the st<strong>and</strong>ard I/O library<br />

lacking the necessary capabilities. If you need to know this information,<br />

Section 7 describes the special system calls, or ioctls, associated<br />

with particular device drivers.<br />

The device files identified with the letter "P" following the section<br />

number are part of the NUX POSIX environment. The<br />

differences between the NUX environment <strong>and</strong> the A/UX POSIX<br />

environment are described in A/UX Guide to POSIX, which is provided<br />

in A/UX Programming Languages <strong>and</strong> Tools, Volume 1.<br />

February, 1990<br />

Revision C<br />

1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!