execve.2, fallocate.2, futex.2, sched_rr_get_interval.2, select_tut.2, shmget.2, timer_getoverrun.2, times.2, pthread_attr_init.3, pthread_attr_setaffinity_np.3, pthread_cleanup_push_defer_np.3, pthread_getattr_np.3, pthread_self.3, pthread_setaffinity_np.3, pthread_tryjoin_np.3, sem_open.3, stdin.3, rtc.4, tty_ioctl.4, unix.7: Global fix: s/non-portable/nonportable/

The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "non-" etc.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/execve.2

@@ -483,7 +483,7 @@ can be specified as NULL,
 which has the same effect as specifying this argument
 as a pointer to a list containing a single NULL pointer.
 .B "Do not take advantage of this misfeature!"
-It is nonstandard and non-portable:
+It is nonstandard and nonportable:
 on most other Unix systems doing this will result in an error
 .RB ( EFAULT ).
 .\" e.g., EFAULT on Solaris 8 and FreeBSD 6.1; but

man2/fallocate.2

@@ -14,7 +14,7 @@ fallocate \- manipulate file space
 ", off_t " len ");
 .fi
 .SH DESCRIPTION
-This is a non-portable, Linux-specific system call.
+This is a nonportable, Linux-specific system call.
 For the portable, POSIX.1-specified method of ensuring that space
 is allocated for a file, see
 .BR posix_fallocate ().

man2/futex.2

@@ -56,7 +56,7 @@ process to sleep or, conversely, waking a waiting process.
 Callers of this function are expected to adhere to the semantics as set out in
 .BR futex (7).
 As these
-semantics involve writing non-portable assembly instructions, this in turn
+semantics involve writing nonportable assembly instructions, this in turn
 probably means that most users will in fact be library authors and not
 general application developers.
 .PP

man2/sched_rr_get_interval.2

@@ -102,7 +102,7 @@ POSIX.1-2001.
 .\" appropriately.
 POSIX does not specify any mechanism for controlling the size of the
 round-robin time quantum.
-However, Linux provides a (non-portable) method of doing this.
+However, Linux provides a (nonportable) method of doing this.
 The quantum can be controlled by adjusting the process's nice value (see
 .BR setpriority (2)).
 Assigning a negative (i.e., high) nice value results in a longer quantum;

man2/select_tut.2

@@ -333,7 +333,7 @@ efficiently copes with this situation.
 Many people who try to use
 .BR select ()
 come across behavior that is
-difficult to understand and produces non-portable or borderline results.
+difficult to understand and produces nonportable or borderline results.
 For instance, the above program is carefully written not to
 block at any point, even though it does not set its file descriptors to
 nonblocking mode.

man2/shmget.2

@@ -231,7 +231,7 @@ SVr4, POSIX.1-2001.
 .\" SVr4 documents an additional error condition EEXIST.
 
 .B SHM_HUGETLB
-is a non-portable Linux extension.
+is a nonportable Linux extension.
 .SH NOTES
 .B IPC_PRIVATE
 isn't a flag field but a

man2/timer_getoverrun.2

@@ -104,7 +104,7 @@ structure (see
 .BR sigaction (2)).
 This allows an application to avoid the overhead of making
 a system call to obtain the overrun count,
-but is a non-portable extension to POSIX.1-2001.
+but is a nonportable extension to POSIX.1-2001.
 
 POSIX.1-2001 only discusses timer overruns in the context of
 timer notifications using signals.

man2/times.2

@@ -33,7 +33,7 @@
 .\" Modified 2004-12-08, mtk, in 2.6 times() return value changed
 .\" 2005-04-13, mtk
 .\"	Added notes on nonstandard behavior: Linux allows 'buf' to
-.\"	be NULL, but POSIX.1 doesn't specify this and it's non-portable.
+.\"	be NULL, but POSIX.1 doesn't specify this and it's nonportable.
 .\"
 .TH TIMES 2 2008-06-25 "Linux" "Linux Programmer's Manual"
 .SH NAME

man3/pthread_attr_init.3

@@ -80,7 +80,7 @@ The
 .I pthread_attr_t
 type should be treated as opaque:
 any access to the object other than via pthreads functions
-is non-portable and produces undefined results.
+is nonportable and produces undefined results.
 .SH EXAMPLE
 The program below optionally makes use of
 .BR pthread_attr_init ()

man3/pthread_attr_setaffinity_np.3

@@ -104,7 +104,7 @@ Could not allocate memory.
 These functions are provided by glibc since version 2.3.4.
 .SH CONFORMING TO
 These functions are nonstandard GNU extensions;
-hence the suffix "_np" (non-portable) in the names.
+hence the suffix "_np" (nonportable) in the names.
 .SH NOTES
 In glibc 2.3.3 only,
 versions of these functions were provided that did not have a

man3/pthread_cleanup_push_defer_np.3

@@ -97,7 +97,7 @@ pthread_cleanup_pop(execute);
 .\" Available since glibc 2.0
 .SH CONFORMING TO
 These functions are nonstandard GNU extensions;
-hence the suffix "_np" (non-portable) in the names.
+hence the suffix "_np" (nonportable) in the names.
 .SH SEE ALSO
 .BR pthread_cancel (3),
 .BR pthread_cleanup_push (3),

man3/pthread_getattr_np.3

@@ -94,7 +94,7 @@ resource limit is not supported.
 This function is available in glibc since version 2.2.3.
 .SH CONFORMING TO
 This function is a nonstandard GNU extension.
-hence the suffix "_np" (non-portable) in the name.
+hence the suffix "_np" (nonportable) in the name.
 .SH EXAMPLE
 The program below demonstrates the use of
 .BR pthread_getattr_np ().

man3/pthread_self.3

@@ -60,7 +60,7 @@ instead.
 
 Thread identifiers should be considered opaque:
 any attempt to use a thread ID other than in pthreads calls
-is non-portable and can lead to unspecified results.
+is nonportable and can lead to unspecified results.
 
 Thread IDs are only guaranteed to be unique within a process.
 A thread ID may be reused after a terminated thread has been joined,

man3/pthread_setaffinity_np.3

@@ -117,7 +117,7 @@ could be found.
 These functions are provided by glibc since version 2.3.4.
 .SH CONFORMING TO
 These functions are nonstandard GNU extensions;
-hence the suffix "_np" (non-portable) in the names.
+hence the suffix "_np" (nonportable) in the names.
 .SH NOTES
 After a call to
 .BR pthread_setaffinity_np (),

man3/pthread_tryjoin_np.3

@@ -109,7 +109,7 @@ never returns the error
 These functions first appeared in glibc in version 2.3.3.
 .SH CONFORMING TO
 These functions are nonstandard GNU extensions;
-hence the suffix "_np" (non-portable) in the names.
+hence the suffix "_np" (nonportable) in the names.
 .SH EXAMPLE
 The following code waits to join for up to 5 seconds:
 

man3/sem_open.3

@@ -158,7 +158,7 @@ and no semaphore with this
 .I name
 exists;
 or,
-.\" this error can occur if we have a name of the (non-portable) form
+.\" this error can occur if we have a name of the (nonportable) form
 .\" /dir/name, and the directory /dev/shm/dir does not exist.
 .B O_CREAT
 was specified, but

man3/stdin.3

@@ -94,7 +94,7 @@ Since the symbols
 .IR stdout ,
 and
 .I stderr
-are specified to be macros, assigning to them is non-portable.
+are specified to be macros, assigning to them is nonportable.
 The standard streams can be made to refer to different files
 with help of the library function
 .BR freopen (3),

man4/rtc.4

@@ -316,7 +316,7 @@ and 2069.
 Some RTCs support "wildcard" values in alarm fields, to support
 scenarios like periodic alarms at fifteen minutes after every hour,
 or on the first day of each month.
-Such usage is non-portable;
+Such usage is nonportable;
 portable user space code only expects a single alarm interrupt, and
 will either disable or reinitialize the alarm after receiving it.
 

man4/tty_ioctl.4

@@ -18,7 +18,7 @@ or \fIarg\fP.
 .LP
 Use of
 .I ioctl
-makes for non-portable programs.
+makes for nonportable programs.
 Use the POSIX interface described in
 .BR termios (3)
 whenever possible.

man7/unix.7

@@ -127,7 +127,7 @@ its length is
 and
 .I sun_path
 contains the abstract name.
-The abstract socket namespace is a non-portable Linux extension.
+The abstract socket namespace is a nonportable Linux extension.
 .SS Socket Options
 For historical reasons these socket options are specified with a
 .B SOL_SOCKET