From 1abe65d928440b3b23d25746b966dd4169c358b9 Mon Sep 17 00:00:00 2001 From: Steve Holme Date: Fri, 26 Dec 2014 20:45:21 +0000 Subject: code/docs: Use Unix rather than UNIX to avoid use of the trademark Use Unix when generically writing about Unix based systems as UNIX is the trademark and should only be used in a particular product's name. --- docs/INSTALL | 4 ++-- docs/KNOWN_BUGS | 2 +- docs/curl.1 | 8 ++++---- docs/examples/externalsocket.c | 4 ++-- docs/libcurl/curl_easy_setopt.3 | 2 +- docs/libcurl/curl_version_info.3 | 2 +- docs/libcurl/libcurl-tutorial.3 | 6 +++--- docs/libcurl/opts/CURLOPT_UNIX_SOCKET_PATH.3 | 14 +++++++------- 8 files changed, 21 insertions(+), 21 deletions(-) (limited to 'docs') diff --git a/docs/INSTALL b/docs/INSTALL index 48c2e6c1f..30dec5343 100644 --- a/docs/INSTALL +++ b/docs/INSTALL @@ -20,10 +20,10 @@ Building from git If you get your code off a git repository, see the GIT-INFO file in the root directory for specific instructions on how to proceed. -UNIX +Unix ==== - A normal unix installation is made in three or four steps (after you've + A normal Unix installation is made in three or four steps (after you've unpacked the source archive): ./configure diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index 0a6646152..778856773 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -200,7 +200,7 @@ may have been fixed since this was written! be to use a data structure other than a plain C string, one that can handle embedded NUL characters. From a practical standpoint, most FTP servers would not meaningfully support NUL characters within RFC 959 , - anyway (e.g., UNIX pathnames may not contain NUL). + anyway (e.g., Unix pathnames may not contain NUL). 14. Test case 165 might fail on a system which has libidn present, but with an old iconv version (2.1.3 is a known bad version), since it doesn't recognize diff --git a/docs/curl.1 b/docs/curl.1 index 1f5389a6b..0b9971cd2 100644 --- a/docs/curl.1 +++ b/docs/curl.1 @@ -813,12 +813,12 @@ the following places in this order: 1) curl tries to find the "home dir": It first checks for the CURL_HOME and then the HOME environment variables. Failing that, it uses getpwuid() on -UNIX-like systems (which returns the home dir given the current user in your +Unix-like systems (which returns the home dir given the current user in your system). On Windows, it then checks for the APPDATA variable, or as a last resort the '%USERPROFILE%\\Application Data'. 2) On windows, if there is no _curlrc file in the home dir, it checks for one -in the same dir the curl executable is placed. On UNIX-like systems, it will +in the same dir the curl executable is placed. On Unix-like systems, it will simply try to load .curlrc from the determined home dir. .nf @@ -1026,7 +1026,7 @@ in Metalink file, hash check will fail. .IP "-n, --netrc" Makes curl scan the \fI.netrc\fP (\fI_netrc\fP on Windows) file in the user's home directory for login name and password. This is typically used for FTP on -UNIX. If used with HTTP, curl will enable user authentication. See +Unix. If used with HTTP, curl will enable user authentication. See .BR netrc(4) or .BR ftp(1) @@ -1663,7 +1663,7 @@ If this option is used several times, the last one will be used. Prepends a time stamp to each trace or verbose line that curl displays. (Added in 7.14.0) .IP "--unix-socket " -(HTTP) Connect through this UNIX domain socket, instead of using the +(HTTP) Connect through this Unix domain socket, instead of using the network. (Added in 7.40.0) .IP "-u, --user " Specify the user name and password to use for server authentication. Overrides diff --git a/docs/examples/externalsocket.c b/docs/examples/externalsocket.c index 1b326c8b2..5486d1255 100644 --- a/docs/examples/externalsocket.c +++ b/docs/examples/externalsocket.c @@ -5,7 +5,7 @@ * | (__| |_| | _ <| |___ * \___|\___/|_| \_\_____| * - * Copyright (C) 1998 - 2012, Daniel Stenberg, , et al. + * Copyright (C) 1998 - 2014, Daniel Stenberg, , et al. * * This software is licensed as described in the file COPYING, which * you should have received as part of this distribution. The terms @@ -38,7 +38,7 @@ #include /* socket definitions */ #include #include /* inet (3) funtions */ -#include /* misc. UNIX functions */ +#include /* misc. Unix functions */ #endif #include diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index 71f681b70..ecfa38f39 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -188,7 +188,7 @@ Idle time before sending keep-alive. See \fICURLOPT_TCP_KEEPIDLE(3)\fP .IP CURLOPT_TCP_KEEPINTVL Interval between keep-alive probes. See \fICURLOPT_TCP_KEEPINTVL(3)\fP .IP CURLOPT_UNIX_SOCKET_PATH -Path to a UNIX domain socket. See \fICURLOPT_UNIX_SOCKET_PATH(3)\fP +Path to a Unix domain socket. See \fICURLOPT_UNIX_SOCKET_PATH(3)\fP .SH NAMES and PASSWORDS OPTIONS (Authentication) .IP CURLOPT_NETRC Enable .netrc parsing. See \fICURLOPT_NETRC(3)\fP diff --git a/docs/libcurl/curl_version_info.3 b/docs/libcurl/curl_version_info.3 index 6e553463e..1b8f9c119 100644 --- a/docs/libcurl/curl_version_info.3 +++ b/docs/libcurl/curl_version_info.3 @@ -147,7 +147,7 @@ libcurl was built with support for NTLM delegation to a winbind helper. libcurl was built with support for HTTP2. (Added in 7.33.0) .IP CURL_VERSION_UNIX_SOCKETS -libcurl was built with support for UNIX domain sockets. +libcurl was built with support for Unix domain sockets. (Added in 7.40.0) .RE \fIssl_version\fP is an ASCII string for the OpenSSL version used. If libcurl diff --git a/docs/libcurl/libcurl-tutorial.3 b/docs/libcurl/libcurl-tutorial.3 index d496e7027..11b019011 100644 --- a/docs/libcurl/libcurl-tutorial.3 +++ b/docs/libcurl/libcurl-tutorial.3 @@ -40,7 +40,7 @@ refer to their respective man pages. .SH "Building" There are many different ways to build C programs. This chapter will assume a -UNIX-style build process. If you use a different build system, you can still +Unix style build process. If you use a different build system, you can still read this to get general information that may apply to your environment as well. .IP "Compiling the Program" @@ -412,7 +412,7 @@ similar to the \fICURLOPT_USERPWD(3)\fP option like this: curl_easy_setopt(easyhandle, CURLOPT_PROXYUSERPWD, "myname:thesecret"); -There's a long time UNIX "standard" way of storing ftp user names and +There's a long time Unix "standard" way of storing FTP user names and passwords, namely in the $HOME/.netrc file. The file should be made private so that only the user may read it (see also the "Security Considerations" chapter), as it might contain the password in plain text. libcurl has the @@ -1402,7 +1402,7 @@ This happens on Windows machines when libcurl is built and used as a DLL. However, you can still do this on Windows if you link with a static library. .IP "[3]" -The curl-config tool is generated at build-time (on UNIX-like systems) and +The curl-config tool is generated at build-time (on Unix-like systems) and should be installed with the 'make install' or similar instruction that installs the library, header files, man pages etc. .IP "[4]" diff --git a/docs/libcurl/opts/CURLOPT_UNIX_SOCKET_PATH.3 b/docs/libcurl/opts/CURLOPT_UNIX_SOCKET_PATH.3 index f65676364..a659cd2ca 100644 --- a/docs/libcurl/opts/CURLOPT_UNIX_SOCKET_PATH.3 +++ b/docs/libcurl/opts/CURLOPT_UNIX_SOCKET_PATH.3 @@ -22,18 +22,18 @@ .\" .TH CURLOPT_UNIX_SOCKET_PATH 3 "09 Oct 2014" "libcurl 7.40.0" "curl_easy_setopt options" .SH NAME -CURLOPT_UNIX_SOCKET_PATH \- set UNIX domain socket +CURLOPT_UNIX_SOCKET_PATH \- set Unix domain socket .SH SYNOPSIS #include CURLcode curl_easy_setopt(CURL *handle, CURLOPT_UNIX_SOCKET_PATH, char *path); .SH DESCRIPTION -Enables the use of UNIX domain sockets as connection endpoint and sets the path -to \fIpath\fP. If \fIpath\fP is NULL, then UNIX domain sockets are disabled. An +Enables the use of Unix domain sockets as connection endpoint and sets the path +to \fIpath\fP. If \fIpath\fP is NULL, then Unix domain sockets are disabled. An empty string will result in an error at some point, it will not disable use of -UNIX domain sockets. +Unix domain sockets. -When enabled, cURL will connect to the UNIX domain socket instead of +When enabled, cURL will connect to the Unix domain socket instead of establishing a TCP connection to a host. Since no TCP connection is created, cURL does not need to resolve the DNS hostname in the URL. @@ -45,9 +45,9 @@ Proxy and TCP options such as are not supported. Proxy options such as .BR CURLOPT_PROXY "(3) have no effect either as these are TCP-oriented, and asking a proxy server to -connect to a certain UNIX domain socket is not possible. +connect to a certain Unix domain socket is not possible. .SH DEFAULT -Default is NULL, meaning that no UNIX domain sockets are used. +Default is NULL, meaning that no Unix domain sockets are used. .SH PROTOCOLS All protocols except for file:// and FTP are supported in theory. HTTP, IMAP, POP3 and SMTP should in particular work (including their SSL/TLS variants). -- cgit v1.2.3