summaryrefslogtreecommitdiffstats
path: root/upstream/archlinux/man3p/uname.3p
blob: 34b82d2a18fe346236459f750119b0428735e170 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
'\" et
.TH UNAME "3P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
.\"
.SH PROLOG
This manual page is part of the POSIX Programmer's Manual.
The Linux implementation of this interface may differ (consult
the corresponding Linux manual page for details of Linux behavior),
or the interface may not be implemented on Linux.
.\"
.SH NAME
uname
\(em get the name of the current system
.SH SYNOPSIS
.LP
.nf
#include <sys/utsname.h>
.P
int uname(struct utsname *\fIname\fP);
.fi
.SH DESCRIPTION
The
\fIuname\fR()
function shall store information identifying the current system in the
structure pointed to by
.IR name .
.P
The
\fIuname\fR()
function uses the
.BR utsname
structure defined in
.IR <sys/utsname.h> .
.P
The
\fIuname\fR()
function shall return a string naming the current system in the
character array
.IR sysname .
Similarly,
.IR nodename
shall contain the name of this node within an implementation-defined
communications network. The arrays
.IR release
and
.IR version
shall further identify the operating system. The array
.IR machine
shall contain a name that identifies the hardware that the system
is running on.
.P
The format of each member is implementation-defined.
.SH "RETURN VALUE"
Upon successful completion, a non-negative value shall be returned.
Otherwise, \-1 shall be returned and
.IR errno
set to indicate the error.
.SH ERRORS
No errors are defined.
.LP
.IR "The following sections are informative."
.SH EXAMPLES
None.
.SH "APPLICATION USAGE"
The inclusion of the
.IR nodename
member in this structure does not imply that it is sufficient
information for interfacing to communications networks.
.SH RATIONALE
The values of the structure members are not constrained to have any
relation to the version of this volume of POSIX.1\(hy2017 implemented in the operating
system. An application should instead depend on _POSIX_VERSION
and related constants defined in
.IR <unistd.h> .
.P
This volume of POSIX.1\(hy2017 does not define the sizes of the members of the structure
and permits them to be of different sizes, although most
implementations define them all to be the same size: eight bytes plus
one byte for the string terminator. That size for
.IR nodename
is not enough for use with many networks.
.P
The
\fIuname\fR()
function originated in System III, System V, and related
implementations,
and it does not exist in Version 7 or
4.3 BSD. The values it returns are set at system compile time in those
historical implementations.
.P
4.3 BSD has
\fIgethostname\fR()
and
\fIgethostid\fR(),
which return a symbolic name and a numeric value, respectively. There
are related
\fIsethostname\fR()
and
\fIsethostid\fR()
functions that are used to set the values the other two functions
return. The former functions are included in this specification, the
latter are not.
.SH "FUTURE DIRECTIONS"
None.
.SH "SEE ALSO"
The Base Definitions volume of POSIX.1\(hy2017,
.IR "\fB<sys_utsname.h>\fP"
.\"
.SH COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form
from IEEE Std 1003.1-2017, Standard for Information Technology
-- Portable Operating System Interface (POSIX), The Open Group Base
Specifications Issue 7, 2018 Edition,
Copyright (C) 2018 by the Institute of
Electrical and Electronics Engineers, Inc and The Open Group.
In the event of any discrepancy between this version and the original IEEE and
The Open Group Standard, the original IEEE and The Open Group Standard
is the referee document. The original Standard can be obtained online at
http://www.opengroup.org/unix/online.html .
.PP
Any typographical or formatting errors that appear
in this page are most likely
to have been introduced during the conversion of the source files to
man page format. To report such errors, see
https://www.kernel.org/doc/man-pages/reporting_bugs.html .