Age | Commit message (Collapse) | Author |
|
marked obsolete since the opendev() behaviour it turned on is now the
default.
'it can go' deraadt@
'no API of mine has ever made it into a standard' downsj@
|
|
nested getopt() calls. ok beck
|
|
check it's notion of access, avoiding problems on more tightly
coupled changers if the tape is already ejected - currently
these stupid devices return "Initialization Command Required"
sense codes but there is (as yet) no way to tell userland
that. checking the ACCESS changer flag appears safe in both
cases.
Adds support for "voltag" type for the source for a move, so
you can do "chio move voltag 0003B72 drive 0" to move a tape
with the corresponding bar code.
Documents the above, as well as status -vVa in the man page.
partly from freebsd, man page tweaks by jmc@
ok krw@
|
|
|
|
status command and options -v to request the primary volume tag, -V for
the alternate volume tag. Man page will follow shortly, along with move
support by volume tag.
|
|
|
|
|
|
changer - chio will then attempt to open the /dev/rstX device when doing
a move from a source of drive X, and will attempt to unload the tape.
this avoids issues where pickers madly attempt to grab a busy tape on
completely decoupled libraries, or fail to grab an unloaded tape
on tightly coupled libraries, the extra unload being harmless if the
media has already been ejected.
The mapping between st(4) devices and ch drives is by default a
simple mapping between picker drive X being mapped to /dev/rstX, however
for non-obvious or complicated configurations, we support a /etc/chio.conf
file in which the drives for a changer may have their corresponding
st(4) devices defined individually. chio will use the default
mapping if the /etc/chio.conf file is not present, or does not define
a st(4) device for a changer drive.
(example chio.conf and man page changes to come)
yacc parser for chio.conf written by henning@,
ok henning@, krw@
|
|
|
|
|
|
hand editing to make comments line up correctly. Another pass is forthcoming that handles the cases that could not be done automatically.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
to new SCSI changer driver.
|