version 1, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
SYSFS |
|
|
2 |
!!!SYSFS |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
RETURN VALUE |
|
|
7 |
ERRORS |
|
|
8 |
CONFORMING TO |
|
|
9 |
NOTE |
|
|
10 |
BUGS |
|
|
11 |
---- |
|
|
12 |
!!NAME |
|
|
13 |
|
|
|
14 |
|
|
|
15 |
sysfs - get file system type information |
|
|
16 |
!!SYNOPSIS |
|
|
17 |
|
|
|
18 |
|
|
|
19 |
__int sysfs(int__ ''option''__, const char |
|
|
20 |
*__''fsname''__);__ |
|
|
21 |
|
|
|
22 |
|
|
|
23 |
__int sysfs(int__ ''option''__, unsigned int__ |
|
|
24 |
''fs_index''__, char |
|
|
25 |
*__''buf''__);__ |
|
|
26 |
|
|
|
27 |
|
|
|
28 |
__int sysfs(int__ ''option''__);__ |
|
|
29 |
!!DESCRIPTION |
|
|
30 |
|
|
|
31 |
|
|
|
32 |
__sysfs__ returns information about the file system types |
|
|
33 |
currently present in the kernel. The specific form of the |
|
|
34 |
__sysfs__ call and the information returned depends on |
|
|
35 |
the ''option'' in effect: |
|
|
36 |
|
|
|
37 |
|
|
|
38 |
__1__ |
|
|
39 |
|
|
|
40 |
|
|
|
41 |
Translate the file-system identifier string ''fsname'' |
|
|
42 |
into a file-system type index. |
|
|
43 |
|
|
|
44 |
|
|
|
45 |
__2__ |
|
|
46 |
|
|
|
47 |
|
|
|
48 |
Translate the file-system type index ''fs_index'' into a |
|
|
49 |
null-terminated file-system identifier string. This string |
|
|
50 |
will be written to the buffer pointed to by ''buf''. Make |
|
|
51 |
sure that ''buf'' has enough space to accept the |
|
|
52 |
string. |
|
|
53 |
|
|
|
54 |
|
|
|
55 |
__3__ |
|
|
56 |
|
|
|
57 |
|
|
|
58 |
Return the total number of file system types currently |
|
|
59 |
present in the kernel. |
|
|
60 |
|
|
|
61 |
|
|
|
62 |
The numbering of the file-system type indexes begins with |
|
|
63 |
zero. |
|
|
64 |
!!RETURN VALUE |
|
|
65 |
|
|
|
66 |
|
|
|
67 |
On success, __sysfs__ returns the file-system index for |
|
|
68 |
option __1__, zero for option __2__, and the number of |
|
|
69 |
currently configured file systems for option __3__. On |
|
|
70 |
error, -1 is returned, and ''errno'' is set |
|
|
71 |
appropriately. |
|
|
72 |
!!ERRORS |
|
|
73 |
|
|
|
74 |
|
|
|
75 |
__EINVAL__ |
|
|
76 |
|
|
|
77 |
|
|
|
78 |
''fsname'' is not a valid file-system type identifier; |
|
|
79 |
''fs_index'' is out-of-bounds; ''option'' is |
|
|
80 |
invalid. |
|
|
81 |
|
|
|
82 |
|
|
|
83 |
__EFAULT__ |
|
|
84 |
|
|
|
85 |
|
|
|
86 |
Either ''fsname'' or ''buf'' is outside your |
|
|
87 |
accessible address space. |
|
|
88 |
!!CONFORMING TO |
|
|
89 |
|
|
|
90 |
|
|
|
91 |
SVr4. |
|
|
92 |
!!NOTE |
|
|
93 |
|
|
|
94 |
|
|
|
95 |
On Linux with the ''proc'' filesystem mounted on |
|
|
96 |
''/proc'', the same information can be derived from |
|
|
97 |
''/proc/filesystems''. |
|
|
98 |
!!BUGS |
|
|
99 |
|
|
|
100 |
|
|
|
101 |
There is no libc or glibc support. There is no way to guess |
|
|
102 |
how large ''buf'' should be. |
|
|
103 |
---- |