mtools: miscellaneous flags

1 
1 3.5.6 General Purpose Drive Flags
1 ---------------------------------
1 
1 A flag can either be set to 1 (enabled) or 0 (disabled). If the value is
1 omitted, it is enabled.  For example, `scsi' is equivalent to `scsi=1'
1 
1 `nolock'
1      Instruct mtools to not use locking on this drive.  This is needed
1      on systems with buggy locking semantics.  However, enabling this
1      makes operation less safe in cases where several users may access
1      the same drive at the same time.
1 
1 `scsi'
1      When set to 1, this option tells mtools to use raw SCSI I/O
1      instead of the standard read/write calls to access the device.
1      Currently, this is supported on HP-UX, Solaris and SunOS.  This is
1      needed because on some architectures, such as SunOS or Solaris, PC
1      media can't be accessed using the `read' and `write' system calls,
1      because the OS expects them to contain a Sun specific "disk label".
1 
1      As raw SCSI access always uses the whole device, you need to
1      specify the "partition" flag in addition
1 
1      On some architectures, such as Solaris, mtools needs root
1      privileges to be able to use the `scsi' option.  Thus mtools
1      should be installed setuid root on Solaris if you want to access
1      Zip/Jaz drives.  Thus, if the `scsi' flag is given, `privileged'
1      is automatically implied, unless explicitly disabled by
1      `privileged=0'
1 
1      Mtools uses its root privileges to open the device, and to issue
1      the actual SCSI I/O calls.  Moreover, root privileges are only
1      used for drives described in a system-wide configuration file such
1      as `/etc/mtools.conf', and not for those described in
1      `~/.mtoolsrc' or `$MTOOLSRC'.
1 
1 `privileged'
1      When set to 1, this instructs mtools to use its setuid and setgid
1      privileges for opening the given drive.  This option is only valid
1      for drives described in the system-wide configuration files (such
1      as `/etc/mtools.conf', not `~/.mtoolsrc' or `$MTOOLSRC').
1      Obviously, this option is also a no op if mtools is not installed
1      setuid or setgid.  This option is implied by 'scsi=1', but again
1      only for drives defined in system-wide configuration files.
1      Privileged may also be set explicitly to 0, in order to tell
1      mtools not to use its privileges for a given drive even if
1      `scsi=1' is set.
1 
1      Mtools only needs to be installed setuid if you use the
1      `privileged' or `scsi' drive variables.  If you do not use these
1      options, mtools works perfectly well even when not installed
1      setuid root.
1 
1 `vold'
1      Instructs mtools to interpret the device name as a vold identifier
1      rather than as a filename.  The vold identifier is translated into
1      a real filename using the `media_findname()' and
1      `media_oldaliases()' functions of the `volmgt' library.  This flag
1      is only available if you configured mtools with the
1      `--enable-new-vold' option before compilation.
1 
1 `swap'
1      Consider the media as a word-swapped Atari disk.
1 
1 `use_xdf'
1      If this is set to a non-zero value, mtools also tries to access
1      this disk as an XDF disk. XDF is a high capacity format used by
1      OS/2. This is off by default. ⇒XDF, for more details.
1 
1 `mformat_only'
1      Tells mtools to use the geometry for this drive only for
1      mformatting and not for filtering.
1 
1 `filter'
1      Tells mtools to use the geometry for this drive both for
1      mformatting and filtering.
1 
1 `remote'
1      Tells mtools to connect to floppyd (⇒floppyd).
1