sysfs(2) [osf1 man page]

sysfs(2)							System Calls Manual							  sysfs(2)

NAME

       sysfs - gather information about file system types

SYNOPSIS

       #include <sys/fstyp.h> #include <sys/fsid.h>

       int sysfs(
	       int opcode,
	       const char *fsname ); int sysfs(
	       int opcode,
	       int fs_index,
	       char *buf ); int sysfs(
	       int opcode );

PARAMETERS

       Points  to  the buffer where the file system type is placed.  The buffer size must be equal to FSTYPSZ as defined in <sys/fstyp.h>.  Speci-
       fies an index file system type.	Specifies a null-terminated file system type identifier.  Specifies an operation used to  obtain  informa-
       tion about the file system types.

DESCRIPTION

       This function gathers information about configured file system types.  Depending on the operation you want to perform, the opcode parameter
       may be specified by itself, or in combination with the other available parameters as shown in the SYNOPSIS section.

       The opcode parameter may be one of the following: Must be specified with the fsname parameter.  This operation changes the specified  null-
       terminated  file  system  type  identifier  to a file system type identifier.  Must be specified with the parameters fs_index and buf. This
       operation changes the specified file system type index to a null-terminated type file system type identifier and writes it into the  buffer
       specified.  Specified by itself, this operation requests the total number of file system types configured in the system to be returned.

RETURN VALUES

       The  following values are returned on success: If GETFSIND is specified, the file system type index is returned.  If GETFSTYP is specified,
       a value of zero (0) is returned.  If GETNFSTYP is specified, the number of file system types configured in the system is returned.

       On error, a value of -1 is returned and errno is set.

ERRORS

       One or more of the following may be returned on failure: Indicates an invalid file system identifier is pointed to  fsname,  the  specified
       fs_index  is either zero (0) or invalid, or the specified opcode is invalid.  Indicates that either fsname or buf is pointing to an invalid
       user address.  Indicates that a file system was installed with a name that exceeds the buffer size of FSTYPSZ.

																	  sysfs(2)

Check Out this Related Man Page

SYSFS(2)						     Linux Programmer's Manual							  SYSFS(2)

NAME

       sysfs - get filesystem type information

SYNOPSIS

       int sysfs(int option, const char *fsname);

       int sysfs(int option, unsigned int fs_index, char *buf);

       int sysfs(int option);

DESCRIPTION

       Note: if you are looking for information about the sysfs filesystem that is normally mounted at /sys, see sysfs(5).

       The  (obsolete)	sysfs()  system call returns information about the filesystem types currently present in the kernel.  The specific form of
       the sysfs() call and the information returned depends on the option in effect:

       1  Translate the filesystem identifier string fsname into a filesystem type index.

       2  Translate the filesystem type index fs_index into a null-terminated filesystem identifier string.  This string will be  written  to  the
	  buffer pointed to by buf.  Make sure that buf has enough space to accept the string.

       3  Return the total number of filesystem types currently present in the kernel.

       The numbering of the filesystem type indexes begins with zero.

RETURN VALUE

       On  success,  sysfs()  returns the filesystem index for option 1, zero for option 2, and the number of currently configured filesystems for
       option 3.  On error, -1 is returned, and errno is set appropriately.

ERRORS

       EFAULT Either fsname or buf is outside your accessible address space.

       EINVAL fsname is not a valid filesystem type identifier; fs_index is out-of-bounds; option is invalid.

CONFORMING TO

       SVr4.

NOTES

       This System-V derived system call is obsolete;  don't  use  it.	 On  systems  with  /proc,  the  same  information  can  be  obtained  via
       /proc/filesystems; use that interface instead.

BUGS

       There is no libc or glibc support.  There is no way to guess how large buf should be.

COLOPHON

       This  page is part of release 4.15 of the Linux man-pages project.  A description of the project, information about reporting bugs, and the
       latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.

Linux								    2017-09-15								  SYSFS(2)

Linux and UNIX Man Pages

sysfs(2) [osf1 man page]

Check Out this Related Man Page