.\" but does document which functions are presently AC-Safe.

.\" This documentation is provided for use

.\" by the GNU C Library developers.

.\" Just like signal handlers, cancellation cleanup routines must configure

.\" the floating point environment they require.

.\" The routines cannot assume a floating point environment,

this specific cause for the function to be regarded as MT-Unsafe.

If no other cause for that remains,

the function can then be safely called after other threads are started.

.\" Functions marked with

.\" .I init

.\" as an AS-Unsafe or AC-Unsafe feature use the GNU C Library internal

the objects are passed to the functions by users;

in others, they are used by the functions to return values to users;

in others, they are not even exposed to users.

.\" We consider access to objects passed as (indirect) arguments to

.\" functions to be data race free.

.\" The assurance of data race free objects

temporary signal;

blocking that signal before the call and resetting its

handler afterwards is recommended.

.\" There is no safe way to guarantee the original signal handler is

.\" restored in case of asynchronous cancellation,

.\" therefore so-marked functions are also AC-Unsafe.

The caller may use a single mutex for simplicity,

or use one mutex per terminal,

even if referenced by different file descriptors.

.\" Functions marked with

.\" .I term

.\" as an AC-Safety issue are supposed to

and so the locale can be considered effectively constant

in these contexts,

which makes the former safe.

.\" Should the locking strategy suggested under @code{const} be used,

.\" failure to guard locale uses is not as fatal as data races in

.\" general: unguarded uses will @emph{not} follow dangling pointers or

The 'rw' option tells the kernel to mount the root filesystem read/write.

This is the default.

.TP

.B "'resume=...'"

This tells the kernel the location of the suspend-to-disk data that you want the machine to resume from after hibernation.

.BR open_by_handle_at (2).

.RE

.PD

.TP

.B CAP_FOWNER

.PD 0

to explicitly defining the following:

cc \-D_BSD_SOURCE \-D_SVID_SOURCE \-D_POSIX_C_SOURCE=200809

.TP

.BR _ATFILE_SOURCE " (since glibc 2.4)"

Defining this macro with any value causes header files to expose

Bit definitions (see the Linux kernel source file

.IR include/linux/icmp.h ):

.RS 12

.TS

l l.

For example:

.SS Unicode under Linux

.SS Indentation of structure definitions, shell session logs, and so on

When structure definitions, shell session logs, and so on are included

in running text, indent them by 4 spaces (i.e., a block enclosed by

NLM_F_ACK:Request for an acknowledgment on success.

NLM_F_ECHO:Echo this request.

.TE

.\" No right adjustment for text blocks in tables

.TS

tab(:);

was reworked to eliminate the use of recursion,

so that the only limit that remains is the maximum of 40

resolutions for the entire pathname.

.SS Step 3: find the final entry

The lookup of the final component of the pathname goes just like

that of all other components, as described in the previous step,

See

.BR fcntl (2)

for more information.

.SS PIPE_BUF

POSIX.1 says that

.BR write (2)s

Suppose a stream socket has the following queued input data:

aabbccddeeff

.IP

The following sequence of

.BR recv (2)

for (;;) {

/* Wait for incoming connection. */

data_socket = accept(connection_socket, NULL, NULL);

exit(EXIT_FAILURE);

}

/* Receive result. */

ret = read(data_socket, buffer, BUFFER_SIZE);

exit(EXIT_SUCCESS);

}

.fi

.PP

For an example of the use of

You will frequently find it under the architecture-specific directory:

find arch/$ARCH/ -name '*vdso*.so*' -o -name '*gate*.so*'

.SS vDSO names

The name of the vDSO varies across architectures.

It will often show up in things like glibc's