Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!batcomputer!rpi!itsgw!steinmetz!uunet!auspex!guy
From: guy@auspex.UUCP (Guy Harris)
Newsgroups: comp.sys.next
Subject: Re: mount(2) and umount(2)
Message-ID: <1066@auspex.UUCP>
Date: 24 Feb 89 21:11:03 GMT
References: <1826@mace.cc.purdue.edu>
Reply-To: guy@auspex.UUCP (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 30


 >Has anyone managed to make the mount system call work?  All I ever
 >get is a "No device" error, using the syntax of the man page - e. g.,
 >
 >	mount("/dev/od0a", path, 0);
 >
 >Are there more arguments or a different order?

Possibly.  If you have a Sun handy, check its MOUNT(2) man page.  Check
both the 3.x and 4.0 man page; the interface was changed.

 >The umount syscall does not exist in libc.a.  There is a unmount
 >function there -- is its name a typo?

No.

The latter change looks like a change made by Sun when NFS was
introduced; since when mounting an NFS file system you don't specify a
block special file (since you're not mounting a disk partition), you
can't specify that as the sole argument on an unmount operation. 
"unmount" takes the name of the mount point as the argument, which is a
file-system-independent way of indicating what you want to unmount.

Given that, and given that NexT supports NFS, they may have adopted the
SunOS version of "mount" as well, which permits you to mount things
other than block special files (e.g., NFS-exported directories).

In any case, if the documentation is still the old 4.xBSD documentation,
complain to NExT and mention that the SunOS documentation (which may be
distributed with the NFS source distribution) may apply here....