MOUNT(2)                GENIX Programmer's Manual                MOUNT(2)



      NAME
           mount, umount - mount or remove file system

      SYNOPSIS
           mount(special, name, rwflag)
           char *special, *name;

           umount(special)
           char *special;

      DESCRIPTION
           Mount announces to the system that a removable file system has  been
           mounted  on  the block-structured special file special; from now on,
           references to file name will refer to the root  file  on  the  newly
           mounted  file  system.   Special  and  name  are  pointers  to null-
           terminated strings containing the appropriate path names.

           Name must exist already. Name must be a directory (unless  the  root
           of  the  mounted  file system is not a directory).  Its old contents
           are inaccessible while the file system is mounted.

           The rwflag argument determines whether the file system can be  writ-
           ten  on;  if  it  is 0 writing is allowed, if non-zero no writing is
           done.  Physically write-protected and  magnetic  tape  file  systems
           must be mounted read-only or errors will occur when access times are
           updated, whether or not any explicit write is attempted.

           Umount announces to the system that the special file is no longer to
           contain a removable file system.  The associated file reverts to its
           ordinary interpretation.

      SEE ALSO
           mount(8)

      DIAGNOSTICS
           Mount returns 0 if the action occurred; -1 if special is  inaccessi-
           ble  or  not an appropriate file; if name does not exist; if special
           is already mounted; if name is in use; or if there are  already  too
           many file systems mounted.

           Umount returns 0 if the action occurred; -1 if if the  special  file
           is  inaccessible or does not have a mounted file system, or if there
           are active files in the mounted file system.

      BUGS
           If a file containing holes (unallocated blocks) is read, even  on  a
           file  system  mounted  read-only, the system will attempt to fill in
           the holes by writing on the device.







      Printed 11/16/83                                                        1