libperfuse(2) [netbsd man page]

LIBPERFUSE(2)						      BSD System Calls Manual						     LIBPERFUSE(2)

NAME

     perfuse_mount, perfuse_open -- Request a puffs(3) mount from perfused(8)

LIBRARY

     library ``libperfuse''

SYNOPSIS

     #include <perfuse.h>

     int
     perfuse_mount(const char *source, const char *dir, const char *filesystemtype, long int mountflags, void *data);

     int
     perfuse_open(const char *path, int flags);

DESCRIPTION

     perfuse_mount() sends a mount request to perfused(8).  It is intended as a drop-in replacement for mount(2) for FUSE file systems daemons and
     libraries, so that they can work with perfused(8).

     The function prototype mimics Linux's mount(2), with the following arguments:

     source  The source file system that will appear in df(1) and mount(8) listings.  Defaults to /dev/fuse if NULL.

     dir     The file system mount point.

     filesystemtype
	     The file system type, as displayed by df(1) and mount(8).	Defaults to ``fuse'' if NULL.

     mountflags
	     This contains the same value as a mount(2) flags argument.

     data    This contains the same value as a mount(2) data argument.

     perfuse_open() is a drop-in replacement for the open(2) system call where /dev/fuse is used.  If path is different than /dev/fuse,
     perfuse_open() handles control to the regular open(2).

RETURN VALUES

     perfuse_mount() returns a file descriptor to the /dev/fuse socket on success, and causes exit on failure.

SEE ALSO

     df(1), mount(2), open(2), mount(8), perfused(8)

AUTHORS

     The program was written by Emmanuel Dreyfus <manu@NetBSD.org>.

BSD
								  August 12, 2010							       BSD

DEVFS(5)						      BSD File Formats Manual							  DEVFS(5)

NAME

     devfs -- device file system

SYNOPSIS

     devfs   /dev    devfs rw 0 0

DESCRIPTION

     The device file system, or devfs, provides access to kernel's device namespace in the global file system namespace.  The conventional mount
     point is /dev.

     The file system includes several directories, links, symbolic links and devices, some of which can also be written.  In a chroot'ed environ-
     ment, devfs can be used to create a new /dev mount point.

     The mknod(8) tool can be used to recover deleted device entries under devfs.

     The fdescfs(5) filesystem is an alternate means for populating /dev/fd.  The character devices that both devfs and fdescfs(5) present in
     /dev/fd correspond to the open file descriptors of the process accessing the directory.  devfs only creates files for the standard file
     descriptors 0, 1 and 2.  fdescfs(5) creates files for all open descriptors.

     The options are as follows:

     -o options
	     Use the specified mount options, as described in mount(8).  The following devfs file system-specific options are available:

	     ruleset=ruleset
		     Set ruleset number ruleset as the current ruleset for the mount-point and apply all its rules.  If the ruleset number ruleset
		     does not exist, an empty ruleset with the number ruleset is created.  See devfs(8) for more information on working with devfs
		     rulesets.

FILES

     /dev	The normal devfs mount point.

EXAMPLES

     To mount a devfs volume located on /mychroot/dev:

	   mount -t devfs devfs /mychroot/dev

SEE ALSO

     fdescfs(5), devfs(8), mount(8)

HISTORY

     The devfs file system first appeared in FreeBSD 2.0.  It became the preferred method for accessing devices in FreeBSD 5.0 and the only method
     in FreeBSD 6.0.  The devfs manual page first appeared in FreeBSD 2.2.

AUTHORS

     The devfs manual page was written by Mike Pritchard <mpp@FreeBSD.org>.

BSD
								 February 9, 2012							       BSD