diff options
| author | Indrajith K L | 2022-12-03 17:00:20 +0530 |
|---|---|---|
| committer | Indrajith K L | 2022-12-03 17:00:20 +0530 |
| commit | f5c4671bfbad96bf346bd7e9a21fc4317b4959df (patch) | |
| tree | 2764fc62da58f2ba8da7ed341643fc359873142f /coreutils-5.3.0-bin/man/cat1 | |
| download | cli-tools-windows-f5c4671bfbad96bf346bd7e9a21fc4317b4959df.tar.gz cli-tools-windows-f5c4671bfbad96bf346bd7e9a21fc4317b4959df.tar.bz2 cli-tools-windows-f5c4671bfbad96bf346bd7e9a21fc4317b4959df.zip | |
Diffstat (limited to 'coreutils-5.3.0-bin/man/cat1')
93 files changed, 12058 insertions, 0 deletions
diff --git a/coreutils-5.3.0-bin/man/cat1/basename.1.txt b/coreutils-5.3.0-bin/man/cat1/basename.1.txt new file mode 100644 index 0000000..036ef43 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/basename.1.txt @@ -0,0 +1,46 @@ +BASENAME(1) User Commands BASENAME(1) + + + + + +NAME + basename - strip directory and suffix from filenames + +SYNOPSIS + basename NAME [SUFFIX] + basename OPTION + +DESCRIPTION + Print NAME with any leading directory components + removed. If specified, also remove a trailing SUFFIX. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by FIXME unknown. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for basename is maintained as a + Texinfo manual. If the info and basename programs are + properly installed at your site, the command + + info basename + + should give you access to the complete manual. + + + +basename 5.3.0 November 2004 BASENAME(1) diff --git a/coreutils-5.3.0-bin/man/cat1/cat.1.txt b/coreutils-5.3.0-bin/man/cat1/cat.1.txt new file mode 100644 index 0000000..3672f0f --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/cat.1.txt @@ -0,0 +1,73 @@ +CAT(1) User Commands CAT(1) + + + + + +NAME + cat - concatenate files and print on the standard output + +SYNOPSIS + cat [OPTION] [FILE]... + +DESCRIPTION + Concatenate FILE(s), or standard input, to standard out- + put. + + -A, --show-all + equivalent to -vET + + -b, --number-nonblank + number nonblank output lines + + -e equivalent to -vE + + -E, --show-ends + display $ at end of each line + + -n, --number + number all output lines + + -s, --squeeze-blank + never more than one single blank line + + -t equivalent to -vT + + -T, --show-tabs + display TAB characters as ^I + + -u (ignored) + + -v, --show-nonprinting + use ^ and M- notation, except for LFD and TAB + + --help display this help and exit + + --version + output version information and exit + + With no FILE, or when FILE is -, read standard input. + +AUTHOR + Written by Torbjorn Granlund and Richard M. Stallman. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for cat is maintained as a Tex- + info manual. If the info and cat programs are properly + installed at your site, the command + + info cat + + should give you access to the complete manual. + + + diff --git a/coreutils-5.3.0-bin/man/cat1/chgrp.1.txt b/coreutils-5.3.0-bin/man/cat1/chgrp.1.txt new file mode 100644 index 0000000..9ba4c4a --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/chgrp.1.txt @@ -0,0 +1,91 @@ +CHGRP(1) User Commands CHGRP(1) + + + + + +NAME + chgrp - change group ownership + +SYNOPSIS + chgrp [OPTION]... GROUP FILE... + chgrp [OPTION]... --reference=RFILE FILE... + +DESCRIPTION + Change the group of each FILE to GROUP. With --refer- + ence, change the group of each FILE to that of RFILE. + + -c, --changes + like verbose but report only when a change is + made + + --dereference + affect the referent of each symbolic link, rather + than the symbolic link itself (this is the + default) + + -h, --no-dereference + affect each symbolic link instead of any refer- + enced file (useful only on systems that can + change the ownership of a symlink) + + --no-preserve-root do not treat `/' specially (the + default) + + --preserve-root + fail to operate recursively on `/' + + -f, --silent, --quiet + suppress most error messages + + --reference=RFILE + use RFILE's group rather than the specifying + GROUP value + + -R, --recursive + operate on files and directories recursively + + -v, --verbose + output a diagnostic for every file processed + + The following options modify how a hierarchy is tra- + versed when the -R option is also specified. If more + than one is specified, only the final one takes effect. + + -H if a command line argument is a symbolic link to + a directory, traverse it + + -L traverse every symbolic link to a directory + encountered + + -P do not traverse any symbolic links (default) + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie and Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for chgrp is maintained as a Tex- + info manual. If the info and chgrp programs are prop- + erly installed at your site, the command + + info chgrp + + should give you access to the complete manual. + + + +chgrp 5.3.0 November 2004 CHGRP(1) diff --git a/coreutils-5.3.0-bin/man/cat1/chmod.1.txt b/coreutils-5.3.0-bin/man/cat1/chmod.1.txt new file mode 100644 index 0000000..273bb40 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/chmod.1.txt @@ -0,0 +1,143 @@ +CHMOD(1) User Commands CHMOD(1) + + + + + +NAME + chmod - change file access permissions + +SYNOPSIS + chmod [OPTION]... MODE[,MODE]... FILE... + chmod [OPTION]... OCTAL-MODE FILE... + chmod [OPTION]... --reference=RFILE FILE... + +DESCRIPTION + This manual page documents the GNU version of chmod. + chmod changes the permissions of each given file accord- + ing to mode, which can be either a symbolic representa- + tion of changes to make, or an octal number representing + the bit pattern for the new permissions. + + The format of a symbolic mode is `[ugoa...][[+-=][rwxXs- + tugo...]...][,...]'. Multiple symbolic operations can + be given, separated by commas. + + A combination of the letters `ugoa' controls which + users' access to the file will be changed: the user who + owns it (u), other users in the file's group (g), other + users not in the file's group (o), or all users (a). If + none of these are given, the effect is as if `a' were + given, but bits that are set in the umask are not + affected. + + The operator `+' causes the permissions selected to be + added to the existing permissions of each file; `-' + causes them to be removed; and `=' causes them to be the + only permissions that the file has. + + The letters `rwxXstugo' select the new permissions for + the affected users: read (r), write (w), execute (or + access for directories) (x), execute only if the file is + a directory or already has execute permission for some + user (X), set user or group ID on execution (s), sticky + (t), the permissions granted to the user who owns the + file (u), the permissions granted to other users who are + members of the file's group (g), and the permissions + granted to users that are in neither of the two preced- + ing categories (o). + + A numeric mode is from one to four octal digits (0-7), + derived by adding up the bits with values 4, 2, and 1. + Any omitted digits are assumed to be leading zeros. The + first digit selects the set user ID (4) and set group ID + (2) and sticky (1) attributes. The second digit selects + permissions for the user who owns the file: read (4), + write (2), and execute (1); the third selects permis- + sions for other users in the file's group, with the same + values; and the fourth for other users not in the file's + group, with the same values. + + chmod never changes the permissions of symbolic links; + the chmod system call cannot change their permissions. + This is not a problem since the permissions of symbolic + links are never used. However, for each symbolic link + listed on the command line, chmod changes the permis- + sions of the pointed-to file. In contrast, chmod + ignores symbolic links encountered during recursive + directory traversals. + +STICKY FILES + On older Unix systems, the sticky bit caused executable + files to be hoarded in swap space. This feature is not + useful on modern VM systems, and the Linux kernel + ignores the sticky bit on files. Other kernels may use + the sticky bit on files for system-defined purposes. On + some systems, only the superuser can set the sticky bit + on files. + +STICKY DIRECTORIES + When the sticky bit is set on a directory, files in that + directory may be unlinked or renamed only by root or + their owner. Without the sticky bit, anyone able to + write to the directory can delete or rename files. The + sticky bit is commonly found on directories, such as + /tmp, that are world-writable. + +OPTIONS + Change the mode of each FILE to MODE. + + -c, --changes + like verbose but report only when a change is + made + + --no-preserve-root + do not treat `/' specially (the default) + + --preserve-root + fail to operate recursively on `/' + + -f, --silent, --quiet + suppress most error messages + + -v, --verbose + output a diagnostic for every file processed + + --reference=RFILE + use RFILE's mode instead of MODE values + + -R, --recursive + change files and directories recursively + + --help display this help and exit + + --version + output version information and exit + + Each MODE is one or more of the letters ugoa, one of the + symbols +-= and one or more of the letters rwxXstugo. + +AUTHOR + Written by David MacKenzie and Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for chmod is maintained as a Tex- + info manual. If the info and chmod programs are prop- + erly installed at your site, the command + + info chmod + + should give you access to the complete manual. + + + +chmod 5.3.0 November 2004 CHMOD(1) diff --git a/coreutils-5.3.0-bin/man/cat1/chown.1.txt b/coreutils-5.3.0-bin/man/cat1/chown.1.txt new file mode 100644 index 0000000..9daec34 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/chown.1.txt @@ -0,0 +1,122 @@ +CHOWN(1) User Commands CHOWN(1) + + + + + +NAME + chown - change file owner and group + +SYNOPSIS + chown [OPTION]... [OWNER][:[GROUP]] FILE... + chown [OPTION]... --reference=RFILE FILE... + +DESCRIPTION + This manual page documents the GNU version of chown. + chown changes the user and/or group ownership of each + given file, according to its first non-option argument, + which is interpreted as follows. If only a user name + (or numeric user ID) is given, that user is made the + owner of each given file, and the files' group is not + changed. If the user name is followed by a colon or dot + and a group name (or numeric group ID), with no spaces + between them, the group ownership of the files is + changed as well. If a colon or dot but no group name + follows the user name, that user is made the owner of + the files and the group of the files is changed to that + user's login group. If the colon or dot and group are + given, but the user name is omitted, only the group of + the files is changed; in this case, chown performs the + same function as chgrp. + +OPTIONS + Change the owner and/or group of each FILE to OWNER + and/or GROUP. With --reference, change the owner and + group of each FILE to those of RFILE. + + -c, --changes + like verbose but report only when a change is + made + + --dereference + affect the referent of each symbolic link, rather + than the symbolic link itself (this is the + default) + + -h, --no-dereference + affect each symbolic link instead of any refer- + enced file (useful only on systems that can + change the ownership of a symlink) + + --from=CURRENT_OWNER:CURRENT_GROUP + change the owner and/or group of each file only + if its current owner and/or group match those + specified here. Either may be omitted, in which + case a match is not required for the omitted + attribute. + + --no-preserve-root do not treat `/' specially (the + default) + + --preserve-root + fail to operate recursively on `/' + + -f, --silent, --quiet + suppress most error messages + + --reference=RFILE + use RFILE's owner and group rather than the spec- + ifying OWNER:GROUP values + + -R, --recursive + operate on files and directories recursively + + -v, --verbose + output a diagnostic for every file processed + + The following options modify how a hierarchy is tra- + versed when the -R option is also specified. If more + than one is specified, only the final one takes effect. + + -H if a command line argument is a symbolic link to + a directory, traverse it + + -L traverse every symbolic link to a directory + encountered + + -P do not traverse any symbolic links (default) + + --help display this help and exit + + --version + output version information and exit + + Owner is unchanged if missing. Group is unchanged if + missing, but changed to login group if implied by a `:' + following a symbolic OWNER. OWNER and GROUP may be + numeric as well as symbolic. + +AUTHOR + Written by David MacKenzie and Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for chown is maintained as a Tex- + info manual. If the info and chown programs are prop- + erly installed at your site, the command + + info chown + + should give you access to the complete manual. + + + +chown 5.3.0 November 2004 CHOWN(1) diff --git a/coreutils-5.3.0-bin/man/cat1/chroot.1.txt b/coreutils-5.3.0-bin/man/cat1/chroot.1.txt new file mode 100644 index 0000000..c9a639f --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/chroot.1.txt @@ -0,0 +1,49 @@ +CHROOT(1) User Commands CHROOT(1) + + + + + +NAME + chroot - run command or interactive shell with special + root directory + +SYNOPSIS + chroot NEWROOT [COMMAND...] + chroot OPTION + +DESCRIPTION + Run COMMAND with root directory set to NEWROOT. + + --help display this help and exit + + --version + output version information and exit + + If no command is given, run ``${SHELL} -i'' (default: + /bin/sh). + +AUTHOR + Written by Roland McGrath. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for chroot is maintained as a + Texinfo manual. If the info and chroot programs are + properly installed at your site, the command + + info chroot + + should give you access to the complete manual. + + + +chroot 5.3.0 November 2004 CHROOT(1) diff --git a/coreutils-5.3.0-bin/man/cat1/cksum.1.txt b/coreutils-5.3.0-bin/man/cat1/cksum.1.txt new file mode 100644 index 0000000..b21f41f --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/cksum.1.txt @@ -0,0 +1,45 @@ +CKSUM(1) User Commands CKSUM(1) + + + + + +NAME + cksum - checksum and count the bytes in a file + +SYNOPSIS + cksum [FILE]... + cksum [OPTION] + +DESCRIPTION + Print CRC checksum and byte counts of each FILE. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Q. Frank Xia. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for cksum is maintained as a Tex- + info manual. If the info and cksum programs are prop- + erly installed at your site, the command + + info cksum + + should give you access to the complete manual. + + + +cksum (coreutils) 5.3.0 November 2004 CKSUM(1) diff --git a/coreutils-5.3.0-bin/man/cat1/comm.1.txt b/coreutils-5.3.0-bin/man/cat1/comm.1.txt new file mode 100644 index 0000000..f2ac7f2 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/comm.1.txt @@ -0,0 +1,55 @@ +COMM(1) User Commands COMM(1) + + + + + +NAME + comm - compare two sorted files line by line + +SYNOPSIS + comm [OPTION]... FILE1 FILE2 + +DESCRIPTION + Compare sorted files FILE1 and FILE2 line by line. + + With no options, produce three-column output. Column + one contains lines unique to FILE1, column two contains + lines unique to FILE2, and column three contains lines + common to both files. + + -1 suppress lines unique to FILE1 + + -2 suppress lines unique to FILE2 + + -3 suppress lines that appear in both files + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Richard Stallman and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for comm is maintained as a Tex- + info manual. If the info and comm programs are properly + installed at your site, the command + + info comm + + should give you access to the complete manual. + + + +comm 5.3.0 December 2004 COMM(1) diff --git a/coreutils-5.3.0-bin/man/cat1/cp.1.txt b/coreutils-5.3.0-bin/man/cat1/cp.1.txt new file mode 100644 index 0000000..c30a403 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/cp.1.txt @@ -0,0 +1,167 @@ +CP(1) User Commands CP(1) + + + + + +NAME + cp - copy files and directories + +SYNOPSIS + cp [OPTION]... [-T] SOURCE DEST + cp [OPTION]... SOURCE... DIRECTORY + cp [OPTION]... -t DIRECTORY SOURCE... + +DESCRIPTION + Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY. + + Mandatory arguments to long options are mandatory for + short options too. + + -a, --archive + same as -dpR + + --backup[=CONTROL] + make a backup of each existing destination file + + -b like --backup but does not accept an argument + + --copy-contents + copy contents of special files when recursive + + -d same as --no-dereference --preserve=link + + --no-dereference + never follow symbolic links + + -f, --force + if an existing destination file cannot be opened, + remove it and try again + + -i, --interactive + prompt before overwrite + + -H follow command-line symbolic links + + -l, --link + link files instead of copying + + -L, --dereference + always follow symbolic links + + -p same as --preserve=mode,ownership,timestamps + + --preserve[=ATTR_LIST] + preserve the specified attributes (default: + mode,ownership,timestamps), if possible addi- + tional attributes: links, all + + --no-preserve=ATTR_LIST + don't preserve the specified attributes + + --parents + append source path to DIRECTORY + + -P same as `--no-dereference' + + -R, -r, --recursive + copy directories recursively + + --remove-destination + remove each existing destination file before + attempting to open it (contrast with --force) + + --reply={yes,no,query} + specify how to handle the prompt about an exist- + ing destination file + + --sparse=WHEN + control creation of sparse files + + --strip-trailing-slashes remove any trailing slashes + from each SOURCE + argument + + -s, --symbolic-link + make symbolic links instead of copying + + -S, --suffix=SUFFIX + override the usual backup suffix + + -t, --target-directory=DIRECTORY + copy all SOURCE arguments into DIRECTORY + + -T, --no-target-directory + treat DEST as a normal file + + -u, --update + copy only when the SOURCE file is newer than the + destination file or when the destination file is + missing + + -v, --verbose + explain what is being done + + -x, --one-file-system + stay on this file system + + --help display this help and exit + + --version + output version information and exit + + By default, sparse SOURCE files are detected by a crude + heuristic and the corresponding DEST file is made sparse + as well. That is the behavior selected by + --sparse=auto. Specify --sparse=always to create a + sparse DEST file whenever the SOURCE file contains a + long enough sequence of zero bytes. Use --sparse=never + to inhibit creation of sparse files. + + The backup suffix is `~', unless set with --suffix or + SIMPLE_BACKUP_SUFFIX. The version control method may be + selected via the --backup option or through the VER- + SION_CONTROL environment variable. Here are the values: + + none, off + never make backups (even if --backup is given) + + numbered, t + make numbered backups + + existing, nil + numbered if numbered backups exist, simple other- + wise + + simple, never + always make simple backups + + As a special case, cp makes a backup of SOURCE when the + force and backup options are given and SOURCE and DEST + are the same name for an existing, regular file. + +AUTHOR + Written by Torbjorn Granlund, David MacKenzie, and Jim + Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for cp is maintained as a Texinfo + manual. If the info and cp programs are properly + installed at your site, the command + + info cp + + should give you access to the complete manual. + + + +cp 5.3.0 November 2004 CP(1) diff --git a/coreutils-5.3.0-bin/man/cat1/csplit.1.txt b/coreutils-5.3.0-bin/man/cat1/csplit.1.txt new file mode 100644 index 0000000..e0061fc --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/csplit.1.txt @@ -0,0 +1,90 @@ +CSPLIT(1) User Commands CSPLIT(1) + + + + + +NAME + csplit - split a file into sections determined by con- + text lines + +SYNOPSIS + csplit [OPTION]... FILE PATTERN... + +DESCRIPTION + Output pieces of FILE separated by PATTERN(s) to files + `xx01', `xx02', ..., and output byte counts of each + piece to standard output. + + Mandatory arguments to long options are mandatory for + short options too. + + -b, --suffix-format=FORMAT use sprintf FORMAT instead of + %02d + + -f, --prefix=PREFIX + use PREFIX instead of `xx' + + -k, --keep-files + do not remove output files on errors + + -n, --digits=DIGITS + use specified number of digits instead of 2 + + -s, --quiet, --silent + do not print counts of output file sizes + + -z, --elide-empty-files + remove empty output files + + --help display this help and exit + + --version + output version information and exit + + Read standard input if FILE is -. Each PATTERN may be: + + INTEGER + copy up to but not including specified line num- + ber + + /REGEXP/[OFFSET] + copy up to but not including a matching line + + %REGEXP%[OFFSET] + skip to, but not including a matching line + + {INTEGER} + repeat the previous pattern specified number of + times + + {*} repeat the previous pattern as many times as pos- + sible + + A line OFFSET is a required `+' or `-' followed by a + positive integer. + +AUTHOR + Written by Stuart Kemp and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for csplit is maintained as a + Texinfo manual. If the info and csplit programs are + properly installed at your site, the command + + info csplit + + should give you access to the complete manual. + + + +csplit 5.3.0 December 2004 CSPLIT(1) diff --git a/coreutils-5.3.0-bin/man/cat1/cut.1.txt b/coreutils-5.3.0-bin/man/cat1/cut.1.txt new file mode 100644 index 0000000..c706e6e --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/cut.1.txt @@ -0,0 +1,95 @@ +CUT(1) User Commands CUT(1) + + + + + +NAME + cut - remove sections from each line of files + +SYNOPSIS + cut [OPTION]... [FILE]... + +DESCRIPTION + Print selected parts of lines from each FILE to standard + output. + + Mandatory arguments to long options are mandatory for + short options too. + + -b, --bytes=LIST + select only these bytes + + -c, --characters=LIST + select only these characters + + -d, --delimiter=DELIM + use DELIM instead of TAB for field delimiter + + -f, --fields=LIST + select only these fields; also print any line + that contains no delimiter character, unless the + -s option is specified + + -n (ignored) + + --complement + complement the set of selected bytes, characters + or fields. + + -s, --only-delimited + do not print lines not containing delimiters + + --output-delimiter=STRING + use STRING as the output delimiter the default is + to use the input delimiter + + --help display this help and exit + + --version + output version information and exit + + Use one, and only one of -b, -c or -f. Each LIST is + made up of one range, or many ranges separated by com- + mas. Selected input is written in the same order that + it is read, and is written exactly once. Each range is + one of: + + N N'th byte, character or field, counted from 1 + + N- from N'th byte, character or field, to end of + line + + N-M from N'th to M'th (included) byte, character or + field + + -M from first to M'th (included) byte, character or + field + + With no FILE, or when FILE is -, read standard input. + +AUTHOR + Written by David Ihnat, David MacKenzie, and Jim Meyer- + ing. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for cut is maintained as a Tex- + info manual. If the info and cut programs are properly + installed at your site, the command + + info cut + + should give you access to the complete manual. + + + +cut 5.3.0 December 2004 CUT(1) diff --git a/coreutils-5.3.0-bin/man/cat1/date.1.txt b/coreutils-5.3.0-bin/man/cat1/date.1.txt new file mode 100644 index 0000000..8e98235 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/date.1.txt @@ -0,0 +1,180 @@ +DATE(1) User Commands DATE(1) + + + + + +NAME + date - print or set the system date and time + +SYNOPSIS + date [OPTION]... [+FORMAT] + date [-u|--utc|--universal] [MMDDhhmm[[CC]YY][.ss]] + +DESCRIPTION + Display the current time in the given FORMAT, or set the + system date. + + -d, --date=STRING + display time described by STRING, not `now' + + -f, --file=DATEFILE + like --date once for each line of DATEFILE + + --iso-8601[=TIMESPEC] output date/time in ISO 8601 for- + mat. + TIMESPEC=`date' for date only (the default), + `hours', `minutes', `seconds', or `ns' for date + and time to the indicated precision. + + -r, --reference=FILE + display the last modification time of FILE + + -R, --rfc-2822 + output RFC-2822 compliant date string + + -s, --set=STRING + set time described by STRING + + -u, --utc, --universal + print or set Coordinated Universal Time + + --help display this help and exit + + --version + output version information and exit + + FORMAT controls the output. The only valid option for + the second form specifies Coordinated Universal Time. + Interpreted sequences are: + + %% a literal % + + %a locale's abbreviated weekday name (Sun..Sat) + + %A locale's full weekday name, variable length (Sun- + day..Saturday) + + %b locale's abbreviated month name (Jan..Dec) + + %B locale's full month name, variable length (Jan- + uary..December) + + %c locale's date and time (Sat Nov 04 12:02:33 EST + 1989) + + %C century (year divided by 100 and truncated to an + integer) [00-99] + + %d day of month (01..31) + + %D date (mm/dd/yy) + + %e day of month, blank padded ( 1..31) + + %F same as %Y-%m-%d + + %g the 2-digit year corresponding to the %V week + number + + %G the 4-digit year corresponding to the %V week + number + + %h same as %b + + %H hour (00..23) + + %I hour (01..12) + + %j day of year (001..366) + + %k hour ( 0..23) + + %l hour ( 1..12) + + %m month (01..12) + + %M minute (00..59) + + %n a newline + + %N nanoseconds (000000000..999999999) + + %p locale's upper case AM or PM indicator (blank in + many locales) + + %P locale's lower case am or pm indicator (blank in + many locales) + + %r time, 12-hour (hh:mm:ss [AP]M) + + %R time, 24-hour (hh:mm) + + %s seconds since `00:00:00 1970-01-01 UTC' (a GNU + extension) + + %S second (00..60); the 60 is necessary to accommo- + date a leap second + + %t a horizontal tab + + %T time, 24-hour (hh:mm:ss) + + %u day of week (1..7); 1 represents Monday + + %U week number of year with Sunday as first day of + week (00..53) + + %V week number of year with Monday as first day of + week (01..53) + + %w day of week (0..6); 0 represents Sunday + + %W week number of year with Monday as first day of + week (00..53) + + %x locale's date representation (mm/dd/yy) + + %X locale's time representation (%H:%M:%S) + + %y last two digits of year (00..99) + + %Y year (1970...) + + %z RFC-2822 style numeric timezone (-0500) (a non- + standard extension) + + %Z time zone (e.g., EDT), or nothing if no time zone + is determinable + + By default, date pads numeric fields with zeroes. GNU + date recognizes the following modifiers between `%' and + a numeric directive. + + `-' (hyphen) do not pad the field `_' (under- + score) pad the field with spaces + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for date is maintained as a Tex- + info manual. If the info and date programs are properly + installed at your site, the command + + info date + + should give you access to the complete manual. + + + +date 5.3.0 November 2004 DATE(1) diff --git a/coreutils-5.3.0-bin/man/cat1/dd.1.txt b/coreutils-5.3.0-bin/man/cat1/dd.1.txt new file mode 100644 index 0000000..0a89f04 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/dd.1.txt @@ -0,0 +1,164 @@ +DD(1) User Commands DD(1) + + + + + +NAME + dd - convert and copy a file + +SYNOPSIS + dd [OPERAND]... + dd OPTION + +DESCRIPTION + Copy a file, converting and formatting according to the + operands. + + bs=BYTES + force ibs=BYTES and obs=BYTES + + cbs=BYTES + convert BYTES bytes at a time + + conv=CONVS + convert the file as per the comma separated sym- + bol list + + count=BLOCKS + copy only BLOCKS input blocks + + ibs=BYTES + read BYTES bytes at a time + + if=FILE + read from FILE instead of stdin + + iflag=FLAGS + read as per the comma separated symbol list + + obs=BYTES + write BYTES bytes at a time + + of=FILE + write to FILE instead of stdout + + oflag=FLAGS + write as per the comma separated symbol list + + seek=BLOCKS + skip BLOCKS obs-sized blocks at start of output + + skip=BLOCKS + skip BLOCKS ibs-sized blocks at start of input + + status=noxfer + suppress transfer statistics + + BLOCKS and BYTES may be followed by the following multi- + plicative suffixes: xM M, c 1, w 2, b 512, kB 1000, K + 1024, MB 1000*1000, M 1024*1024, GB 1000*1000*1000, G + 1024*1024*1024, and so on for T, P, E, Z, Y. + + Each CONV symbol may be: + + ascii from EBCDIC to ASCII + + ebcdic from ASCII to EBCDIC + + ibm from ASCII to alternate EBCDIC + + block pad newline-terminated records with spaces to + cbs-size + + unblock + replace trailing spaces in cbs-size records with + newline + + lcase change upper case to lower case + + nocreat + do not create the output file + + excl fail if the output file already exists + + notrunc + do not truncate the output file + + ucase change lower case to upper case + + swab swap every pair of input bytes + + noerror + continue after read errors + + sync pad every input block with NULs to ibs-size; when + used + + with block or unblock, pad with spaces rather + than NULs + + fdatasync physically write output file data + before finishing fsync likewise, but also + write metadata + + Each FLAG symbol may be: + + append append mode (makes sense only for output) + + direct use direct I/O for data + + dsync use synchronized I/O for data + + sync likewise, but also for metadata + + nonblock + use non-blocking I/O + + nofollow + do not follow symlinks + + noctty do not assign controlling terminal from file + + Sending a SIGUSR1 signal to a running `dd' process makes + it print I/O statistics to standard error, then to + resume copying. + + $ dd if=/dev/zero of=/dev/null& pid=$! + $ kill -USR1 $pid; sleep 1; kill $pid + + 18335302+0 records in 18335302+0 records out + 9387674624 bytes (9.4 GB) copied, 34.6279 sec- + onds, 271 MB/s + + Options are: + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Paul Rubin, David MacKenzie, and Stuart Kemp. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for dd is maintained as a Texinfo + manual. If the info and dd programs are properly + installed at your site, the command + + info dd + + should give you access to the complete manual. + + + +dd (coreutils) 5.3.0 November 2004 DD(1) diff --git a/coreutils-5.3.0-bin/man/cat1/df.1.txt b/coreutils-5.3.0-bin/man/cat1/df.1.txt new file mode 100644 index 0000000..e2b42a4 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/df.1.txt @@ -0,0 +1,113 @@ +DF(1) User Commands DF(1) + + + + + +NAME + df - report file system disk space usage + +SYNOPSIS + df [OPTION]... [FILE]... + +DESCRIPTION + This manual page documents the GNU version of df. df + displays the amount of disk space available on the file + system containing each file name argument. If no file + name is given, the space available on all currently + mounted file systems is shown. Disk space is shown in + 1K blocks by default, unless the environment variable + POSIXLY_CORRECT is set, in which case 512-byte blocks + are used. + + If an argument is the absolute file name of a disk + device node containing a mounted file system, df shows + the space available on that file system rather than on + the file system containing the device node (which is + always the root file system). This version of df cannot + show the space available on unmounted file systems, + because on most kinds of systems doing so requires very + nonportable intimate knowledge of file system struc- + tures. + +OPTIONS + Show information about the file system on which each + FILE resides, or all file systems by default. + + Mandatory arguments to long options are mandatory for + short options too. + + -a, --all + include file systems having 0 blocks + + -B, --block-size=SIZE use SIZE-byte blocks + + -h, --human-readable + print sizes in human readable format (e.g., 1K + 234M 2G) + + -H, --si + likewise, but use powers of 1000 not 1024 + + -i, --inodes + list inode information instead of block usage + + -k like --block-size=1K + + -l, --local + limit listing to local file systems + + --no-sync + do not invoke sync before getting usage info + (default) + + -P, --portability + use the POSIX output format + + --sync invoke sync before getting usage info + + -t, --type=TYPE + limit listing to file systems of type TYPE + + -T, --print-type + print file system type + + -x, --exclude-type=TYPE + limit listing to file systems not of type TYPE + + -v (ignored) + + --help display this help and exit + + --version + output version information and exit + + SIZE may be (or may be an integer optionally followed + by) one of following: kB 1000, K 1024, MB 1000*1000, M + 1024*1024, and so on for G, T, P, E, Z, Y. + +AUTHOR + Written by Torbjorn Granlund, David MacKenzie, and Paul + Eggert. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for df is maintained as a Texinfo + manual. If the info and df programs are properly + installed at your site, the command + + info df + + should give you access to the complete manual. + + + +df 5.3.0 November 2004 DF(1) diff --git a/coreutils-5.3.0-bin/man/cat1/dir.1.txt b/coreutils-5.3.0-bin/man/cat1/dir.1.txt new file mode 100644 index 0000000..64b3972 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/dir.1.txt @@ -0,0 +1,233 @@ +DIR(1) User Commands DIR(1) + + + + + +NAME + dir - list directory contents + +SYNOPSIS + dir [OPTION]... [FILE]... + +DESCRIPTION + List information about the FILEs (the current directory + by default). Sort entries alphabetically if none of + -cftuSUX nor --sort. + + Mandatory arguments to long options are mandatory for + short options too. + + -a, --all + do not ignore entries starting with . + + -A, --almost-all + do not list implied . and .. + + --author + with -l, print the author of each file + + -b, --escape + print octal escapes for nongraphic characters + + --block-size=SIZE + use SIZE-byte blocks + + -B, --ignore-backups + do not list implied entries ending with ~ + + -c with -lt: sort by, and show, ctime (time of last + modification of file status information) with -l: + show ctime and sort by name otherwise: sort by + ctime + + -C list entries by columns + + --color[=WHEN] + control whether color is used to distinguish file + types. WHEN may be `never', `always', or `auto' + + -d, --directory + list directory entries instead of contents, and + do not dereference symbolic links + + -D, --dired + generate output designed for Emacs' dired mode + + -f do not sort, enable -aU, disable -lst + + -F, --classify + append indicator (one of */=@|) to entries + + --format=WORD + across -x, commas -m, horizontal -x, long -l, + single-column -1, verbose -l, vertical -C + + --full-time + like -l --time-style=full-iso + + -g like -l, but do not list owner + + -G, --no-group + like -l, but do not list group + + -h, --human-readable + with -l, print sizes in human readable format + (e.g., 1K 234M 2G) + + --si likewise, but use powers of 1000 not 1024 + + -H, --dereference-command-line + follow symbolic links listed on the command line + + --dereference-command-line-symlink-to-dir + follow each command line symbolic link that + points to a directory + + --hide=PATTERN + do not list implied entries matching shell PAT- + TERN (overridden by -a or -A) + + --indicator-style=WORD append indicator with style WORD + to entry names: + none (default), classify (-F), file-type (-p) + + -i, --inode + with -l, print the index number of each file + + -I, --ignore=PATTERN + do not list implied entries matching shell PAT- + TERN + + -k like --block-size=1K + + -l use a long listing format + + -L, --dereference + when showing file information for a symbolic + link, show information for the file the link ref- + erences rather than for the link itself + + -m fill width with a comma separated list of entries + + -n, --numeric-uid-gid + like -l, but list numeric UIDs and GIDs + + -N, --literal + print raw entry names (don't treat e.g. control + characters specially) + + -o like -l, but do not list group information + + -p, --file-type + append indicator (one of /=@|) to entries + + -q, --hide-control-chars + print ? instead of non graphic characters + + --show-control-chars + show non graphic characters as-is (default unless + program is `ls' and output is a terminal) + + -Q, --quote-name + enclose entry names in double quotes + + --quoting-style=WORD + use quoting style WORD for entry names: literal, + locale, shell, shell-always, c, escape + + -r, --reverse + reverse order while sorting + + -R, --recursive + list subdirectories recursively + + -s, --size + with -l, print size of each file, in blocks + + -S sort by file size + + --sort=WORD + extension -X, none -U, size -S, time -t, version + -v, status -c, time -t, atime -u, access -u, use + -u + + --time=WORD + with -l, show time as WORD instead of modifica- + tion time: atime, access, use, ctime or status; + use specified time as sort key if --sort=time + + --time-style=STYLE + with -l, show times using style STYLE: full-iso, + long-iso, iso, locale, +FORMAT. FORMAT is inter- + preted like `date'; if FORMAT is FORMAT1<new- + line>FORMAT2, FORMAT1 applies to non-recent files + and FORMAT2 to recent files; if STYLE is prefixed + with `posix-', STYLE takes effect only outside + the POSIX locale + + -t sort by modification time + + -T, --tabsize=COLS + assume tab stops at each COLS instead of 8 + + -u with -lt: sort by, and show, access time with -l: + show access time and sort by name otherwise: sort + by access time + + -U do not sort; list entries in directory order + + -v sort by version + + -w, --width=COLS + assume screen width instead of current value + + -x list entries by lines instead of by columns + + -X sort alphabetically by entry extension + + -1 list one file per line + + --help display this help and exit + + --version + output version information and exit + + SIZE may be (or may be an integer optionally followed + by) one of following: kB 1000, K 1024, MB 1000*1000, M + 1024*1024, and so on for G, T, P, E, Z, Y. + + By default, color is not used to distinguish types of + files. That is equivalent to using --color=none. Using + the --color option without the optional WHEN argument is + equivalent to using --color=always. With --color=auto, + color codes are output only if standard output is con- + nected to a terminal (tty). + + Exit status is 0 if OK, 1 if minor problems, 2 if seri- + ous trouble. + +AUTHOR + Written by Richard Stallman and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for dir is maintained as a Tex- + info manual. If the info and dir programs are properly + installed at your site, the command + + info dir + + should give you access to the complete manual. + + + +dir 5.3.0 December 2004 DIR(1) diff --git a/coreutils-5.3.0-bin/man/cat1/dircolors.1.txt b/coreutils-5.3.0-bin/man/cat1/dircolors.1.txt new file mode 100644 index 0000000..ab466c6 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/dircolors.1.txt @@ -0,0 +1,60 @@ +DIRCOLORS(1) User Commands DIRCOLORS(1) + + + + + +NAME + dircolors - color setup for ls + +SYNOPSIS + dircolors [OPTION]... [FILE] + +DESCRIPTION + Output commands to set the LS_COLORS environment vari- + able. + + Determine format of output: + -b, --sh, --bourne-shell + output Bourne shell code to set LS_COLORS + + -c, --csh, --c-shell + output C shell code to set LS_COLORS + + -p, --print-database + output defaults + + --help display this help and exit + + --version + output version information and exit + + If FILE is specified, read it to determine which colors + to use for which file types and extensions. Otherwise, + a precompiled database is used. For details on the for- + mat of these files, run `dircolors --print-database'. + +AUTHOR + Written by H. Peter Anvin. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for dircolors is maintained as a + Texinfo manual. If the info and dircolors programs are + properly installed at your site, the command + + info dircolors + + should give you access to the complete manual. + + + +dircolors 5.3.0 November 2004 DIRCOLORS(1) diff --git a/coreutils-5.3.0-bin/man/cat1/dirname.1.txt b/coreutils-5.3.0-bin/man/cat1/dirname.1.txt new file mode 100644 index 0000000..a0e0a5a --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/dirname.1.txt @@ -0,0 +1,47 @@ +DIRNAME(1) User Commands DIRNAME(1) + + + + + +NAME + dirname - strip non-directory suffix from file name + +SYNOPSIS + dirname NAME + dirname OPTION + +DESCRIPTION + Print NAME with its trailing /component removed; if NAME + contains no /'s, output `.' (meaning the current direc- + tory). + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie and Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for dirname is maintained as a + Texinfo manual. If the info and dirname programs are + properly installed at your site, the command + + info dirname + + should give you access to the complete manual. + + + +dirname 5.3.0 November 2004 DIRNAME(1) diff --git a/coreutils-5.3.0-bin/man/cat1/du.1.txt b/coreutils-5.3.0-bin/man/cat1/du.1.txt new file mode 100644 index 0000000..ede7f2b --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/du.1.txt @@ -0,0 +1,137 @@ +DU(1) User Commands DU(1) + + + + + +NAME + du - estimate file space usage + +SYNOPSIS + du [OPTION]... [FILE]... + du [OPTION]... --files0-from=F + +DESCRIPTION + Summarize disk usage of each FILE, recursively for + directories. + + Mandatory arguments to long options are mandatory for + short options too. + + -a, --all + write counts for all files, not just directories + + --apparent-size + print apparent sizes, rather than disk usage; + although the apparent size is usually smaller, it + may be larger due to holes in (`sparse') files, + internal fragmentation, indirect blocks, and the + like + + -B, --block-size=SIZE use SIZE-byte blocks + + -b, --bytes + equivalent to `--apparent-size --block-size=1' + + -c, --total + produce a grand total + + -D, --dereference-args + dereference FILEs that are symbolic links + + --files0-from=F + summarize disk usage of the NUL-terminated file + names specified in file F + + -H like --si, but also evokes a warning; will soon + change to be equivalent to --dereference-args + (-D) + + -h, --human-readable + print sizes in human readable format (e.g., 1K + 234M 2G) + + --si like -h, but use powers of 1000 not 1024 + + -k like --block-size=1K + + -l, --count-links + count sizes many times if hard linked + + -L, --dereference + dereference all symbolic links + + -P, --no-dereference + don't follow any symbolic links (this is the + default) + + -0, --null + end each output line with 0 byte rather than new- + line + + -S, --separate-dirs + do not include size of subdirectories + + -s, --summarize + display only a total for each argument + + -x, --one-file-system + skip directories on different file systems + + -X FILE, --exclude-from=FILE + Exclude files that match any pattern in FILE. + + --exclude=PATTERN Exclude files that match PATTERN. + + --max-depth=N + print the total for a directory (or file, with + --all) only if it is N or fewer levels below the + command line argument; --max-depth=0 is the same + as --summarize + + --help display this help and exit + + --version + output version information and exit + + SIZE may be (or may be an integer optionally followed + by) one of following: kB 1000, K 1024, MB 1000*1000, M + 1024*1024, and so on for G, T, P, E, Z, Y. + +PATTERNS + PATTERN is a shell pattern (not a regular expression). + The pattern ? matches any one character, whereas * + matches any string (composed of zero, one or multiple + characters). For example, *.o will match any files + whose names end in .o. Therefore, the command + + du --exclude='*.o' + + will skip all files and subdirectories ending in .o + (including the file .o itself). + +AUTHOR + Written by Torbjorn Granlund, David MacKenzie, Paul + Eggert, and Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2005 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for du is maintained as a Texinfo + manual. If the info and du programs are properly + installed at your site, the command + + info du + + should give you access to the complete manual. + + + +du 5.3.0 January 2005 DU(1) diff --git a/coreutils-5.3.0-bin/man/cat1/echo.1.txt b/coreutils-5.3.0-bin/man/cat1/echo.1.txt new file mode 100644 index 0000000..472d132 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/echo.1.txt @@ -0,0 +1,79 @@ +ECHO(1) User Commands ECHO(1) + + + + + +NAME + echo - display a line of text + +SYNOPSIS + echo [OPTION]... [STRING]... + +DESCRIPTION + NOTE: your shell may have its own version of echo which + will supersede the version described here. Please refer + to your shell's documentation for details about the + options it supports. + + Echo the STRING(s) to standard output. + + -n do not output the trailing newline + + -e enable interpretation of backslash escapes + + -E disable interpretation of backslash escapes + (default) + + --help display this help and exit + + --version + output version information and exit + + If -e is in effect, the following sequences are recog- + nized: + + \0NNN the character whose ASCII code is NNN (octal) + + \\ backslash + + \a alert (BEL) + + \b backspace + + \c suppress trailing newline + + \f form feed + + \n new line + + \r carriage return + + \t horizontal tab + + \v vertical tab + +AUTHOR + Written by FIXME unknown. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for echo is maintained as a Tex- + info manual. If the info and echo programs are properly + installed at your site, the command + + info echo + + should give you access to the complete manual. + + + +echo 5.3.0 November 2004 ECHO(1) diff --git a/coreutils-5.3.0-bin/man/cat1/env.1.txt b/coreutils-5.3.0-bin/man/cat1/env.1.txt new file mode 100644 index 0000000..1c70d33 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/env.1.txt @@ -0,0 +1,54 @@ +ENV(1) User Commands ENV(1) + + + + + +NAME + env - run a program in a modified environment + +SYNOPSIS + env [OPTION]... [-] [NAME=VALUE]... [COMMAND [ARG]...] + +DESCRIPTION + Set each NAME to VALUE in the environment and run COM- + MAND. + + -i, --ignore-environment + start with an empty environment + + -u, --unset=NAME + remove variable from the environment + + --help display this help and exit + + --version + output version information and exit + + A mere - implies -i. If no COMMAND, print the resulting + environment. + +AUTHOR + Written by Richard Mlynarik and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for env is maintained as a Tex- + info manual. If the info and env programs are properly + installed at your site, the command + + info env + + should give you access to the complete manual. + + + +env 5.3.0 November 2004 ENV(1) diff --git a/coreutils-5.3.0-bin/man/cat1/expand.1.txt b/coreutils-5.3.0-bin/man/cat1/expand.1.txt new file mode 100644 index 0000000..721fb19 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/expand.1.txt @@ -0,0 +1,61 @@ +EXPAND(1) User Commands EXPAND(1) + + + + + +NAME + expand - convert tabs to spaces + +SYNOPSIS + expand [OPTION]... [FILE]... + +DESCRIPTION + Convert tabs in each FILE to spaces, writing to standard + output. With no FILE, or when FILE is -, read standard + input. + + Mandatory arguments to long options are mandatory for + short options too. + + -i, --initial + do not convert tabs after non blanks + + -t, --tabs=NUMBER + have tabs NUMBER characters apart, not 8 + + -t, --tabs=LIST + use comma separated list of explicit tab posi- + tions + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + unexpand(1) + + The full documentation for expand is maintained as a + Texinfo manual. If the info and expand programs are + properly installed at your site, the command + + info expand + + should give you access to the complete manual. + + + +expand 5.3.0 November 2004 EXPAND(1) diff --git a/coreutils-5.3.0-bin/man/cat1/expr.1.txt b/coreutils-5.3.0-bin/man/cat1/expr.1.txt new file mode 100644 index 0000000..71d0e8d --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/expr.1.txt @@ -0,0 +1,121 @@ +EXPR(1) User Commands EXPR(1) + + + + + +NAME + expr - evaluate expressions + +SYNOPSIS + expr EXPRESSION + expr OPTION + +DESCRIPTION + --help display this help and exit + + --version + output version information and exit + + Print the value of EXPRESSION to standard output. A + blank line below separates increasing precedence groups. + EXPRESSION may be: + + ARG1 | ARG2 + ARG1 if it is neither null nor 0, otherwise ARG2 + + ARG1 & ARG2 + ARG1 if neither argument is null or 0, otherwise + 0 + + ARG1 < ARG2 + ARG1 is less than ARG2 + + ARG1 <= ARG2 + ARG1 is less than or equal to ARG2 + + ARG1 = ARG2 + ARG1 is equal to ARG2 + + ARG1 != ARG2 + ARG1 is unequal to ARG2 + + ARG1 >= ARG2 + ARG1 is greater than or equal to ARG2 + + ARG1 > ARG2 + ARG1 is greater than ARG2 + + ARG1 + ARG2 + arithmetic sum of ARG1 and ARG2 + + ARG1 - ARG2 + arithmetic difference of ARG1 and ARG2 + + ARG1 * ARG2 + arithmetic product of ARG1 and ARG2 + + ARG1 / ARG2 + arithmetic quotient of ARG1 divided by ARG2 + + ARG1 % ARG2 + arithmetic remainder of ARG1 divided by ARG2 + + STRING : REGEXP + anchored pattern match of REGEXP in STRING + + match STRING REGEXP + same as STRING : REGEXP + + substr STRING POS LENGTH + substring of STRING, POS counted from 1 + + index STRING CHARS + index in STRING where any CHARS is found, or 0 + + length STRING + length of STRING + + + TOKEN + interpret TOKEN as a string, even if it is a + + keyword like `match' or an operator like `/' + + ( EXPRESSION ) + value of EXPRESSION + + Beware that many operators need to be escaped or quoted + for shells. Comparisons are arithmetic if both ARGs are + numbers, else lexicographical. Pattern matches return + the string matched between \( and \) or null; if \( and + \) are not used, they return the number of characters + matched or 0. + + Exit status is 0 if EXPRESSION is neither null nor 0, 1 + if EXPRESSION is null or 0, 2 if EXPRESSION is syntacti- + cally invalid, and 3 if an error occurred. + +AUTHOR + Written by Mike Parker. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for expr is maintained as a Tex- + info manual. If the info and expr programs are properly + installed at your site, the command + + info expr + + should give you access to the complete manual. + + + +expr 5.3.0 November 2004 EXPR(1) diff --git a/coreutils-5.3.0-bin/man/cat1/factor.1.txt b/coreutils-5.3.0-bin/man/cat1/factor.1.txt new file mode 100644 index 0000000..93cc432 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/factor.1.txt @@ -0,0 +1,52 @@ +FACTOR(1) User Commands FACTOR(1) + + + + + +NAME + factor - factor numbers + +SYNOPSIS + factor [NUMBER]... + factor OPTION + +DESCRIPTION + Print the prime factors of each NUMBER. + + --help display this help and exit + + --version + output version information and exit + + Print the prime factors of all specified integer NUM- + BERs. + If no arguments + + are specified on the command line, they are read + from standard input. + +AUTHOR + Written by Paul Rubin. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for factor is maintained as a + Texinfo manual. If the info and factor programs are + properly installed at your site, the command + + info factor + + should give you access to the complete manual. + + + +factor 5.3.0 December 2004 FACTOR(1) diff --git a/coreutils-5.3.0-bin/man/cat1/false.1.txt b/coreutils-5.3.0-bin/man/cat1/false.1.txt new file mode 100644 index 0000000..6f12187 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/false.1.txt @@ -0,0 +1,47 @@ +FALSE(1) User Commands FALSE(1) + + + + + +NAME + false - do nothing, unsuccessfully + +SYNOPSIS + false [ignored command line arguments] + false OPTION + +DESCRIPTION + Exit with a status code indicating failure. + + These option names may not be abbreviated. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for false is maintained as a Tex- + info manual. If the info and false programs are prop- + erly installed at your site, the command + + info false + + should give you access to the complete manual. + + + +false 5.3.0 November 2004 FALSE(1) diff --git a/coreutils-5.3.0-bin/man/cat1/fmt.1.txt b/coreutils-5.3.0-bin/man/cat1/fmt.1.txt new file mode 100644 index 0000000..9be5e44 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/fmt.1.txt @@ -0,0 +1,70 @@ +FMT(1) User Commands FMT(1) + + + + + +NAME + fmt - simple optimal text formatter + +SYNOPSIS + fmt [-DIGITS] [OPTION]... [FILE]... + +DESCRIPTION + Reformat each paragraph in the FILE(s), writing to stan- + dard output. If no FILE or if FILE is `-', read stan- + dard input. + + Mandatory arguments to long options are mandatory for + short options too. + + -c, --crown-margin + preserve indentation of first two lines + + -p, --prefix=STRING + reformat only lines beginning with STRING, reat- + taching the prefix to reformatted lines + + -s, --split-only + split long lines, but do not refill + + -t, --tagged-paragraph + indentation of first line different from second + + -u, --uniform-spacing + one space between words, two after sentences + + -w, --width=WIDTH + maximum line width (default of 75 columns) + + --help display this help and exit + + --version + output version information and exit + + With no FILE, or when FILE is -, read standard input. + +AUTHOR + Written by Ross Paterson. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for fmt is maintained as a Tex- + info manual. If the info and fmt programs are properly + installed at your site, the command + + info fmt + + should give you access to the complete manual. + + + +fmt 5.3.0 November 2004 FMT(1) diff --git a/coreutils-5.3.0-bin/man/cat1/fold.1.txt b/coreutils-5.3.0-bin/man/cat1/fold.1.txt new file mode 100644 index 0000000..17fc668 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/fold.1.txt @@ -0,0 +1,57 @@ +FOLD(1) User Commands FOLD(1) + + + + + +NAME + fold - wrap each input line to fit in specified width + +SYNOPSIS + fold [OPTION]... [FILE]... + +DESCRIPTION + Wrap input lines in each FILE (standard input by + default), writing to standard output. + + Mandatory arguments to long options are mandatory for + short options too. + + -b, --bytes + count bytes rather than columns + + -s, --spaces + break at spaces + + -w, --width=WIDTH + use WIDTH columns instead of 80 + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for fold is maintained as a Tex- + info manual. If the info and fold programs are properly + installed at your site, the command + + info fold + + should give you access to the complete manual. + + + +fold 5.3.0 November 2004 FOLD(1) diff --git a/coreutils-5.3.0-bin/man/cat1/gawk.1.txt b/coreutils-5.3.0-bin/man/cat1/gawk.1.txt new file mode 100644 index 0000000..a431e7b --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/gawk.1.txt @@ -0,0 +1,1972 @@ +GAWK(1) Utility Commands GAWK(1) + + + +NAME + gawk - pattern scanning and processing language + +SYNOPSIS + gawk [ POSIX or GNU style options ] -f program-file [ -- + ] file ... + gawk [ POSIX or GNU style options ] [ -- ] program-text + file ... + + pgawk [ POSIX or GNU style options ] -f program-file [ + -- ] file ... + pgawk [ POSIX or GNU style options ] [ -- ] program-text + file ... + +DESCRIPTION + Gawk is the GNU Project's implementation of the AWK pro- + gramming language. It conforms to the definition of the + language in the POSIX 1003.1 Standard. This version in + turn is based on the description in The AWK Programming + Language, by Aho, Kernighan, and Weinberger, with the + additional features found in the System V Release 4 ver- + sion of UNIX awk. Gawk also provides more recent Bell + Laboratories awk extensions, and a number of GNU-spe- + cific extensions. + + Pgawk is the profiling version of gawk. It is identical + in every way to gawk, except that programs run more + slowly, and it automatically produces an execution pro- + file in the file awkprof.out when done. See the --pro- + file option, below. + + The command line consists of options to gawk itself, the + AWK program text (if not supplied via the -f or --file + options), and values to be made available in the ARGC + and ARGV pre-defined AWK variables. + +OPTION FORMAT + Gawk options may be either traditional POSIX one letter + options, or GNU-style long options. POSIX options start + with a single "-", while long options start with "--". + Long options are provided for both GNU-specific features + and for POSIX-mandated features. + + Following the POSIX standard, gawk-specific options are + supplied via arguments to the -W option. Multiple -W + options may be supplied Each -W option has a correspond- + ing long option, as detailed below. Arguments to long + options are either joined with the option by an = sign, + with no intervening spaces, or they may be provided in + the next command line argument. Long options may be + abbreviated, as long as the abbreviation remains unique. + +OPTIONS + Gawk accepts the following options, listed by frequency. + + -F fs + --field-separator fs + Use fs for the input field separator (the value + of the FS predefined variable). + + -v var=val + --assign var=val + Assign the value val to the variable var, before + execution of the program begins. Such variable + values are available to the BEGIN block of an AWK + program. + + -f program-file + --file program-file + Read the AWK program source from the file pro- + gram-file, instead of from the first command line + argument. Multiple -f (or --file) options may be + used. + + -mf NNN + -mr NNN + Set various memory limits to the value NNN. The + f flag sets the maximum number of fields, and the + r flag sets the maximum record size. These two + flags and the -m option are from an earlier ver- + sion of the Bell Laboratories research version of + UNIX awk. They are ignored by gawk, since gawk + has no pre-defined limits. + + -W compat + -W traditional + --compat + --traditional + Run in compatibility mode. In compatibility + mode, gawk behaves identically to UNIX awk; none + of the GNU-specific extensions are recognized. + The use of --traditional is preferred over the + other forms of this option. See GNU EXTENSIONS, + below, for more information. + + -W copyleft + -W copyright + --copyleft + --copyright + Print the short version of the GNU copyright + information message on the standard output and + exit successfully. + + -W dump-variables[=file] + --dump-variables[=file] + Print a sorted list of global variables, their + types and final values to file. If no file is + provided, gawk uses a file named awkvars.out in + the current directory. + Having a list of all the global variables is a + good way to look for typographical errors in your + programs. You would also use this option if you + have a large program with a lot of functions, and + you want to be sure that your functions don't + inadvertently use global variables that you meant + to be local. (This is a particularly easy mis- + take to make with simple variable names like i, + j, and so on.) + + -W exec file + --exec file + Similar to -f, however, this is option is the + last one processed. This should be used with #! + scripts, particularly for CGI applications, to + avoid passing in options or source code (!) on + the command line from a URL. This option dis- + ables command-line variable assignments. + + -W gen-po + --gen-po + Scan and parse the AWK program, and generate a + GNU .po format file on standard output with + entries for all localizable strings in the pro- + gram. The program itself is not executed. See + the GNU gettext distribution for more information + on .po files. + + -W help + -W usage + --help + --usage + Print a relatively short summary of the available + options on the standard output. (Per the GNU + Coding Standards, these options cause an immedi- + ate, successful exit.) + + -W lint[=value] + --lint[=value] + Provide warnings about constructs that are dubi- + ous or non-portable to other AWK implementations. + With an optional argument of fatal, lint warnings + become fatal errors. This may be drastic, but + its use will certainly encourage the development + of cleaner AWK programs. With an optional argu- + ment of invalid, only warnings about things that + are actually invalid are issued. (This is not + fully implemented yet.) + + -W lint-old + --lint-old + Provide warnings about constructs that are not + portable to the original version of Unix awk. + + -W non-decimal-data + --non-decimal-data + Recognize octal and hexadecimal values in input + data. Use this option with great caution! + + -W posix + --posix + This turns on compatibility mode, with the fol- + lowing additional restrictions: + + · \x escape sequences are not recognized. + + · Only space and tab act as field separators when + FS is set to a single space, newline does not. + + · You cannot continue lines after ? and :. + + · The synonym func for the keyword function is + not recognized. + + · The operators ** and **= cannot be used in + place of ^ and ^=. + + · The fflush() function is not available. + + -W profile[=prof_file] + --profile[=prof_file] + Send profiling data to prof_file. The default is + awkprof.out. When run with gawk, the profile is + just a "pretty printed" version of the program. + When run with pgawk, the profile contains execu- + tion counts of each statement in the program in + the left margin and function call counts for each + user-defined function. + + -W re-interval + --re-interval + Enable the use of interval expressions in regular + expression matching (see Regular Expressions, + below). Interval expressions were not tradition- + ally available in the AWK language. The POSIX + standard added them, to make awk and egrep con- + sistent with each other. However, their use is + likely to break old AWK programs, so gawk only + provides them if they are requested with this + option, or when --posix is specified. + + -W source program-text + --source program-text + Use program-text as AWK program source code. + This option allows the easy intermixing of + library functions (used via the -f and --file + options) with source code entered on the command + line. It is intended primarily for medium to + large AWK programs used in shell scripts. + + -W use-lc-numeric + --use-lc-numeric + This forces gawk to use the locale's decimal + point character when parsing input data. + Although the POSIX standard requires this behav- + ior, and gawk does so when --posix is in effect, + the default is to follow traditional behavior and + use a period as the decimal point, even in + locales where the period is not the decimal point + character. This option overrides the default + behavior, without the full draconian strictness + of the --posix option. + + -W version + --version + Print version information for this particular + copy of gawk on the standard output. This is + useful mainly for knowing if the current copy of + gawk on your system is up to date with respect to + whatever the Free Software Foundation is dis- + tributing. This is also useful when reporting + bugs. (Per the GNU Coding Standards, these + options cause an immediate, successful exit.) + + -- Signal the end of options. This is useful to + allow further arguments to the AWK program itself + to start with a "-". This provides consistency + with the argument parsing convention used by most + other POSIX programs. + In compatibility mode, any other options are flagged as + invalid, but are otherwise ignored. In normal opera- + tion, as long as program text has been supplied, unknown + options are passed on to the AWK program in the ARGV + array for processing. This is particularly useful for + running AWK programs via the "#!" executable interpreter + mechanism. +AWK PROGRAM EXECUTION + An AWK program consists of a sequence of pattern-action + statements and optional function definitions. + pattern { action statements } + function name(parameter list) { statements } + Gawk first reads the program source from the program- + file(s) if specified, from arguments to --source, or + from the first non-option argument on the command line. + The -f and --source options may be used multiple times + on the command line. Gawk reads the program text as if + all the program-files and command line source texts had + been concatenated together. This is useful for building + libraries of AWK functions, without having to include + them in each new AWK program that uses them. It also + provides the ability to mix library functions with com- + mand line programs. + The environment variable AWKPATH specifies a search path + to use when finding source files named with the -f + option. If this variable does not exist, the default + path is ".:/usr/local/share/awk". (The actual directory + may vary, depending upon how gawk was built and + installed.) If a file name given to the -f option con- + tains a "/" character, no path search is performed. + Gawk executes AWK programs in the following order. + First, all variable assignments specified via the -v + option are performed. Next, gawk compiles the program + into an internal form. Then, gawk executes the code in + the BEGIN block(s) (if any), and then proceeds to read + each file named in the ARGV array. If there are no + files named on the command line, gawk reads the standard + input. + If a filename on the command line has the form var=val + it is treated as a variable assignment. The variable + var will be assigned the value val. (This happens after + any BEGIN block(s) have been run.) Command line vari- + able assignment is most useful for dynamically assigning + values to the variables AWK uses to control how input is + broken into fields and records. It is also useful for + controlling state if multiple passes are needed over a + single data file. + If the value of a particular element of ARGV is empty + (""), gawk skips over it. + For each record in the input, gawk tests to see if it + matches any pattern in the AWK program. For each pat- + tern that the record matches, the associated action is + executed. The patterns are tested in the order they + occur in the program. + Finally, after all the input is exhausted, gawk executes + the code in the END block(s) (if any). +VARIABLES, RECORDS AND FIELDS + AWK variables are dynamic; they come into existence when + they are first used. Their values are either floating- + point numbers or strings, or both, depending upon how + they are used. AWK also has one dimensional arrays; + arrays with multiple dimensions may be simulated. Sev- + eral pre-defined variables are set as a program runs; + these are described as needed and summarized below. + Records + Normally, records are separated by newline characters. + You can control how records are separated by assigning + values to the built-in variable RS. If RS is any single + character, that character separates records. Otherwise, + RS is a regular expression. Text in the input that + matches this regular expression separates the record. + However, in compatibility mode, only the first character + of its string value is used for separating records. If + RS is set to the null string, then records are separated + by blank lines. When RS is set to the null string, the + newline character always acts as a field separator, in + addition to whatever value FS may have. + Fields + As each input record is read, gawk splits the record + into fields, using the value of the FS variable as the + field separator. If FS is a single character, fields + are separated by that character. If FS is the null + string, then each individual character becomes a sepa- + rate field. Otherwise, FS is expected to be a full reg- + ular expression. In the special case that FS is a sin- + gle space, fields are separated by runs of spaces and/or + tabs and/or newlines. (But see the section POSIX COM- + PATIBILITY, below). NOTE: The value of IGNORECASE (see + below) also affects how fields are split when FS is a + regular expression, and how records are separated when + RS is a regular expression. + If the FIELDWIDTHS variable is set to a space separated + list of numbers, each field is expected to have fixed + width, and gawk splits up the record using the specified + widths. The value of FS is ignored. Assigning a new + value to FS overrides the use of FIELDWIDTHS, and + restores the default behavior. + Each field in the input record may be referenced by its + position, $1, $2, and so on. $0 is the whole record. + Fields need not be referenced by constants: + n = 5 + print $n + prints the fifth field in the input record. + The variable NF is set to the total number of fields in + the input record. + References to non-existent fields (i.e. fields after + $NF) produce the null-string. However, assigning to a + non-existent field (e.g., $(NF+2) = 5) increases the + value of NF, creates any intervening fields with the + null string as their value, and causes the value of $0 + to be recomputed, with the fields being separated by the + value of OFS. References to negative numbered fields + cause a fatal error. Decrementing NF causes the values + of fields past the new value to be lost, and the value + of $0 to be recomputed, with the fields being separated + by the value of OFS. + Assigning a value to an existing field causes the whole + record to be rebuilt when $0 is referenced. Similarly, + assigning a value to $0 causes the record to be resplit, + creating new values for the fields. + Built-in Variables + Gawk's built-in variables are: + ARGC The number of command line arguments (does + not include options to gawk, or the program + source). + ARGIND The index in ARGV of the current file being + processed. + ARGV Array of command line arguments. The array + is indexed from 0 to ARGC - 1. Dynamically + changing the contents of ARGV can control + the files used for data. + BINMODE On non-POSIX systems, specifies use of + "binary" mode for all file I/O. Numeric + values of 1, 2, or 3, specify that input + files, output files, or all files, respec- + tively, should use binary I/O. String val- + ues of "r", or "w" specify that input files, + or output files, respectively, should use + binary I/O. String values of "rw" or "wr" + specify that all files should use binary + I/O. Any other string value is treated as + "rw", but generates a warning message. + CONVFMT The conversion format for numbers, "%.6g", + by default. + ENVIRON An array containing the values of the cur- + rent environment. The array is indexed by + the environment variables, each element + being the value of that variable (e.g., ENV- + IRON["HOME"] might be /home/arnold). Chang- + ing this array does not affect the environ- + ment seen by programs which gawk spawns via + redirection or the system() function. + ERRNO If a system error occurs either doing a + redirection for getline, during a read for + getline, or during a close(), then ERRNO + will contain a string describing the error. + The value is subject to translation in non- + English locales. + FIELDWIDTHS A white-space separated list of fieldwidths. + When set, gawk parses the input into fields + of fixed width, instead of using the value + of the FS variable as the field separator. + FILENAME The name of the current input file. If no + files are specified on the command line, the + value of FILENAME is "-". However, FILENAME + is undefined inside the BEGIN block (unless + set by getline). + FNR The input record number in the current input + file. + FS The input field separator, a space by + default. See Fields, above. + IGNORECASE Controls the case-sensitivity of all regular + expression and string operations. If + IGNORECASE has a non-zero value, then string + comparisons and pattern matching in rules, + field splitting with FS, record separating + with RS, regular expression matching with ~ + and !~, and the gensub(), gsub(), index(), + match(), split(), and sub() built-in func- + tions all ignore case when doing regular + expression operations. NOTE: Array sub- + scripting is not affected. However, the + asort() and asorti() functions are affected. + Thus, if IGNORECASE is not equal to zero, + /aB/ matches all of the strings "ab", "aB", + "Ab", and "AB". As with all AWK variables, + the initial value of IGNORECASE is zero, so + all regular expression and string operations + are normally case-sensitive. Under Unix, + the full ISO 8859-1 Latin-1 character set is + used when ignoring case. As of gawk 3.1.4, + the case equivalencies are fully locale- + aware, based on the C <ctype.h> facilities + such as isalpha(), and toupper(). + LINT Provides dynamic control of the --lint + option from within an AWK program. When + true, gawk prints lint warnings. When false, + it does not. When assigned the string value + "fatal", lint warnings become fatal errors, + exactly like --lint=fatal. Any other true + value just prints warnings. + NF The number of fields in the current input + record. + NR The total number of input records seen so + far. + OFMT The output format for numbers, "%.6g", by + default. + OFS The output field separator, a space by + default. + ORS The output record separator, by default a + newline. + PROCINFO The elements of this array provide access to + information about the running AWK program. + On some systems, there may be elements in + the array, "group1" through "groupn" for + some n, which is the number of supplementary + groups that the process has. Use the in + operator to test for these elements. The + following elements are guaranteed to be + available: + PROCINFO["egid"] the value of the gete- + gid(2) system call. + PROCINFO["euid"] the value of the + geteuid(2) system call. + PROCINFO["FS"] "FS" if field splitting + with FS is in effect, or + "FIELDWIDTHS" if field + splitting with FIELD- + WIDTHS is in effect. + PROCINFO["gid"] the value of the get- + gid(2) system call. + PROCINFO["pgrpid"] the process group ID of + the current process. + PROCINFO["pid"] the process ID of the + current process. + PROCINFO["ppid"] the parent process ID of + the current process. + PROCINFO["uid"] the value of the + getuid(2) system call. + PROCINFO["version"] + The version of gawk. + This is available from + version 3.1.4 and later. + RS The input record separator, by default a + newline. + RT The record terminator. Gawk sets RT to the + input text that matched the character or + regular expression specified by RS. + RSTART The index of the first character matched by + match(); 0 if no match. (This implies that + character indices start at one.) + RLENGTH The length of the string matched by match(); + -1 if no match. + SUBSEP The character used to separate multiple sub- + scripts in array elements, by default + "\034". + TEXTDOMAIN The text domain of the AWK program; used to + find the localized translations for the pro- + gram's strings. + Arrays + Arrays are subscripted with an expression between square + brackets ([ and ]). If the expression is an expression + list (expr, expr ...) then the array subscript is a + string consisting of the concatenation of the (string) + value of each expression, separated by the value of the + SUBSEP variable. This facility is used to simulate mul- + tiply dimensioned arrays. For example: + i = "A"; j = "B"; k = "C" + x[i, j, k] = "hello, world\n" + assigns the string "hello, world\n" to the element of + the array x which is indexed by the string + "A\034B\034C". All arrays in AWK are associative, i.e. + indexed by string values. + The special operator in may be used to test if an array + has an index consisting of a particular value. + if (val in array) + print array[val] + If the array has multiple subscripts, use (i, j) in + array. + The in construct may also be used in a for loop to iter- + ate over all the elements of an array. + An element may be deleted from an array using the delete + statement. The delete statement may also be used to + delete the entire contents of an array, just by specify- + ing the array name without a subscript. + Variable Typing And Conversion + Variables and fields may be (floating point) numbers, or + strings, or both. How the value of a variable is inter- + preted depends upon its context. If used in a numeric + expression, it will be treated as a number; if used as a + string it will be treated as a string. + To force a variable to be treated as a number, add 0 to + it; to force it to be treated as a string, concatenate + it with the null string. + When a string must be converted to a number, the conver- + sion is accomplished using strtod(3). A number is con- + verted to a string by using the value of CONVFMT as a + format string for sprintf(3), with the numeric value of + the variable as the argument. However, even though all + numbers in AWK are floating-point, integral values are + always converted as integers. Thus, given + CONVFMT = "%2.2f" + a = 12 + b = a "" + the variable b has a string value of "12" and not + "12.00". + When operating in POSIX mode (such as with the --posix + command line option), beware that locale settings may + interfere with the way decimal numbers are treated: the + decimal separator of the numbers you are feeding to gawk + must conform to what your locale would expect, be it a + comma (,) or a period (.). + Gawk performs comparisons as follows: If two variables + are numeric, they are compared numerically. If one + value is numeric and the other has a string value that + is a "numeric string," then comparisons are also done + numerically. Otherwise, the numeric value is converted + to a string and a string comparison is performed. Two + strings are compared, of course, as strings. + Note that string constants, such as "57", are not + numeric strings, they are string constants. The idea of + "numeric string" only applies to fields, getline input, + FILENAME, ARGV elements, ENVIRON elements and the ele- + ments of an array created by split() that are numeric + strings. The basic idea is that user input, and only + user input, that looks numeric, should be treated that + way. + Uninitialized variables have the numeric value 0 and the + string value "" (the null, or empty, string). + Octal and Hexadecimal Constants + Starting with version 3.1 of gawk , you may use C-style + octal and hexadecimal constants in your AWK program + source code. For example, the octal value 011 is equal + to decimal 9, and the hexadecimal value 0x11 is equal to + decimal 17. + String Constants + String constants in AWK are sequences of characters + enclosed between double quotes ("). Within strings, + certain escape sequences are recognized, as in C. These + are: + \\ A literal backslash. + \a The "alert" character; usually the ASCII BEL char- + acter. + \b backspace. + \f form-feed. + \n newline. + \r carriage return. + \t horizontal tab. + \v vertical tab. + \xhex digits + The character represented by the string of hexadec- + imal digits following the \x. As in ANSI C, all + following hexadecimal digits are considered part of + the escape sequence. (This feature should tell us + something about language design by committee.) + E.g., "\x1B" is the ASCII ESC (escape) character. + \ddd The character represented by the 1-, 2-, or 3-digit + sequence of octal digits. E.g., "\033" is the + ASCII ESC (escape) character. + \c The literal character c. + The escape sequences may also be used inside constant + regular expressions (e.g., /[ \t\f\n\r\v]/ matches + whitespace characters). + In compatibility mode, the characters represented by + octal and hexadecimal escape sequences are treated lit- + erally when used in regular expression constants. Thus, + /a\52b/ is equivalent to /a\*b/. +PATTERNS AND ACTIONS + AWK is a line-oriented language. The pattern comes + first, and then the action. Action statements are + enclosed in { and }. Either the pattern may be missing, + or the action may be missing, but, of course, not both. + If the pattern is missing, the action is executed for + every single record of input. A missing action is + equivalent to + { print } + which prints the entire record. + Comments begin with the "#" character, and continue + until the end of the line. Blank lines may be used to + separate statements. Normally, a statement ends with a + newline, however, this is not the case for lines ending + in a ",", {, ?, :, &&, or ||. Lines ending in do or + else also have their statements automatically continued + on the following line. In other cases, a line can be + continued by ending it with a "\", in which case the + newline will be ignored. + Multiple statements may be put on one line by separating + them with a ";". This applies to both the statements + within the action part of a pattern-action pair (the + usual case), and to the pattern-action statements them- + selves. + Patterns + AWK patterns may be one of the following: + BEGIN + END + /regular expression/ + relational expression + pattern && pattern + pattern || pattern + pattern ? pattern : pattern + (pattern) + ! pattern + pattern1, pattern2 + BEGIN and END are two special kinds of patterns which + are not tested against the input. The action parts of + all BEGIN patterns are merged as if all the statements + had been written in a single BEGIN block. They are exe- + cuted before any of the input is read. Similarly, all + the END blocks are merged, and executed when all the + input is exhausted (or when an exit statement is exe- + cuted). BEGIN and END patterns cannot be combined with + other patterns in pattern expressions. BEGIN and END + patterns cannot have missing action parts. + For /regular expression/ patterns, the associated state- + ment is executed for each input record that matches the + regular expression. Regular expressions are the same as + those in egrep(1), and are summarized below. + A relational expression may use any of the operators + defined below in the section on actions. These gener- + ally test whether certain fields match certain regular + expressions. + The &&, ||, and ! operators are logical AND, logical + OR, and logical NOT, respectively, as in C. They do + short-circuit evaluation, also as in C, and are used for + combining more primitive pattern expressions. As in + most languages, parentheses may be used to change the + order of evaluation. + The ?: operator is like the same operator in C. If the + first pattern is true then the pattern used for testing + is the second pattern, otherwise it is the third. Only + one of the second and third patterns is evaluated. + The pattern1, pattern2 form of an expression is called a + range pattern. It matches all input records starting + with a record that matches pattern1, and continuing + until a record that matches pattern2, inclusive. It + does not combine with any other sort of pattern expres- + sion. + Regular Expressions + Regular expressions are the extended kind found in + egrep. They are composed of characters as follows: + c matches the non-metacharacter c. + \c matches the literal character c. + . matches any character including newline. + ^ matches the beginning of a string. + $ matches the end of a string. + [abc...] character list, matches any of the characters + abc.... + [^abc...] negated character list, matches any character + except abc.... + r1|r2 alternation: matches either r1 or r2. + r1r2 concatenation: matches r1, and then r2. + r+ matches one or more r's. + r* matches zero or more r's. + r? matches zero or one r's. + (r) grouping: matches r. + r{n} + r{n,} + r{n,m} One or two numbers inside braces denote an + interval expression. If there is one number + in the braces, the preceding regular expres- + sion r is repeated n times. If there are two + numbers separated by a comma, r is repeated n + to m times. If there is one number followed + by a comma, then r is repeated at least n + times. + Interval expressions are only available if + either --posix or --re-interval is specified + on the command line. + + \y matches the empty string at either the begin- + ning or the end of a word. + + \B matches the empty string within a word. + + \< matches the empty string at the beginning of + a word. + + \> matches the empty string at the end of a + word. + + \w matches any word-constituent character (let- + ter, digit, or underscore). + + \W matches any character that is not word-con- + stituent. + + \` matches the empty string at the beginning of + a buffer (string). + + \' matches the empty string at the end of a + buffer. + + The escape sequences that are valid in string constants + (see below) are also valid in regular expressions. + + Character classes are a feature introduced in the POSIX + standard. A character class is a special notation for + describing lists of characters that have a specific + attribute, but where the actual characters themselves + can vary from country to country and/or from character + set to character set. For example, the notion of what + is an alphabetic character differs in the USA and in + France. + + A character class is only valid in a regular expression + inside the brackets of a character list. Character + classes consist of [:, a keyword denoting the class, and + :]. The character classes defined by the POSIX standard + are: + + [:alnum:] Alphanumeric characters. + + [:alpha:] Alphabetic characters. + + [:blank:] Space or tab characters. + + [:cntrl:] Control characters. + + [:digit:] Numeric characters. + + [:graph:] Characters that are both printable and visi- + ble. (A space is printable, but not visible, + while an a is both.) + + [:lower:] Lower-case alphabetic characters. + + [:print:] Printable characters (characters that are not + control characters.) + + [:punct:] Punctuation characters (characters that are + not letter, digits, control characters, or + space characters). + + [:space:] Space characters (such as space, tab, and + formfeed, to name a few). + + [:upper:] Upper-case alphabetic characters. + + [:xdigit:] Characters that are hexadecimal digits. + + For example, before the POSIX standard, to match + alphanumeric characters, you would have had to write + /[A-Za-z0-9]/. If your character set had other alpha- + betic characters in it, this would not match them, and + if your character set collated differently from ASCII, + this might not even match the ASCII alphanumeric charac- + ters. With the POSIX character classes, you can write + /[[:alnum:]]/, and this matches the alphabetic and + numeric characters in your character set, no matter what + it is. + + Two additional special sequences can appear in character + lists. These apply to non-ASCII character sets, which + can have single symbols (called collating elements) that + are represented with more than one character, as well as + several characters that are equivalent for collating, or + sorting, purposes. (E.g., in French, a plain "e" and a + grave-accented "`" are equivalent.) + + Collating Symbols + A collating symbol is a multi-character collating + element enclosed in [. and .]. For example, if + ch is a collating element, then [[.ch.]] is a + regular expression that matches this collating + element, while [ch] is a regular expression that + matches either c or h. + + Equivalence Classes + An equivalence class is a locale-specific name + for a list of characters that are equivalent. + The name is enclosed in [= and =]. For example, + the name e might be used to represent all of "e," + "´," and "`." In this case, [[=e=]] is a regular + expression that matches any of e, ´, or `. + + These features are very valuable in non-English speaking + locales. The library functions that gawk uses for regu- + lar expression matching currently only recognize POSIX + character classes; they do not recognize collating sym- + bols or equivalence classes. + + The \y, \B, \<, \>, \w, \W, \`, and \' operators are + specific to gawk; they are extensions based on facili- + ties in the GNU regular expression libraries. + + The various command line options control how gawk inter- + prets characters in regular expressions. + + No options + In the default case, gawk provide all the facili- + ties of POSIX regular expressions and the GNU + regular expression operators described above. + However, interval expressions are not supported. + + --posix + Only POSIX regular expressions are supported, the + GNU operators are not special. (E.g., \w matches + a literal w). Interval expressions are allowed. + + --traditional + Traditional Unix awk regular expressions are + matched. The GNU operators are not special, + interval expressions are not available, and nei- + ther are the POSIX character classes ([[:alnum:]] + and so on). Characters described by octal and + hexadecimal escape sequences are treated liter- + ally, even if they represent regular expression + metacharacters. + + --re-interval + Allow interval expressions in regular expres- + sions, even if --traditional has been provided. + + Actions + Action statements are enclosed in braces, { and }. + Action statements consist of the usual assignment, con- + ditional, and looping statements found in most lan- + guages. The operators, control statements, and + input/output statements available are patterned after + those in C. + + Operators + The operators in AWK, in order of decreasing precedence, + are + + + (...) Grouping + + $ Field reference. + + ++ -- Increment and decrement, both prefix and + postfix. + + ^ Exponentiation (** may also be used, and **= + for the assignment operator). + + + - ! Unary plus, unary minus, and logical nega- + tion. + + * / % Multiplication, division, and modulus. + + + - Addition and subtraction. + + space String concatenation. + + | |& Piped I/O for getline, print, and printf. + + < > + <= >= + != == The regular relational operators. + + ~ !~ Regular expression match, negated match. + NOTE: Do not use a constant regular expres- + sion (/foo/) on the left-hand side of a ~ or + !~. Only use one on the right-hand side. + The expression /foo/ ~ exp has the same + meaning as (($0 ~ /foo/) ~ exp). This is + usually not what was intended. + + in Array membership. + + && Logical AND. + + || Logical OR. + + ?: The C conditional expression. This has the + form expr1 ? expr2 : expr3. If expr1 is + true, the value of the expression is expr2, + otherwise it is expr3. Only one of expr2 + and expr3 is evaluated. + + = += -= + *= /= %= ^= Assignment. Both absolute assignment (var = + value) and operator-assignment (the other + forms) are supported. + + Control Statements + The control statements are as follows: + + if (condition) statement [ else statement ] + while (condition) statement + do statement while (condition) + for (expr1; expr2; expr3) statement + for (var in array) statement + break + continue + delete array[index] + delete array + exit [ expression ] + { statements } + + I/O Statements + The input/output statements are as follows: + + + close(file [, how]) Close file, pipe or co-process. + The optional how should only be + used when closing one end of a + two-way pipe to a co-process. It + must be a string value, either + "to" or "from". + + getline Set $0 from next input record; set + NF, NR, FNR. + + getline <file Set $0 from next record of file; + set NF. + + getline var Set var from next input record; + set NR, FNR. + + getline var <file Set var from next record of file. + + command | getline [var] + Run command piping the output + either into $0 or var, as above. + + command |& getline [var] + Run command as a co-process piping + the output either into $0 or var, + as above. Co-processes are a gawk + extension. (command can also be a + socket. See the subsection Spe- + cial File Names, below.) + + next Stop processing the current input + record. The next input record is + read and processing starts over + with the first pattern in the AWK + program. If the end of the input + data is reached, the END block(s), + if any, are executed. + + nextfile Stop processing the current input + file. The next input record read + comes from the next input file. + FILENAME and ARGIND are updated, + FNR is reset to 1, and processing + starts over with the first pattern + in the AWK program. If the end of + the input data is reached, the END + block(s), if any, are executed. + + print Prints the current record. The + output record is terminated with + the value of the ORS variable. + + print expr-list Prints expressions. Each expres- + sion is separated by the value of + the OFS variable. The output + record is terminated with the + value of the ORS variable. + + print expr-list >file Prints expressions on file. Each + expression is separated by the + value of the OFS variable. The + output record is terminated with + the value of the ORS variable. + + printf fmt, expr-list Format and print. + + printf fmt, expr-list >file + Format and print on file. + + system(cmd-line) Execute the command cmd-line, and + return the exit status. (This may + not be available on non-POSIX sys- + tems.) + + fflush([file]) Flush any buffers associated with + the open output file or pipe file. + If file is missing, then standard + output is flushed. If file is the + null string, then all open output + files and pipes have their buffers + flushed. + + Additional output redirections are allowed for print and + printf. + + print ... >> file + Appends output to the file. + + print ... | command + Writes on a pipe. + + print ... |& command + Sends data to a co-process or socket. (See also + the subsection Special File Names, below.) + + The getline command returns 0 on end of file and -1 on + an error. Upon an error, ERRNO contains a string + describing the problem. + + NOTE: If using a pipe, co-process, or socket to getline, + or from print or printf within a loop, you must use + close() to create new instances of the command or + socket. AWK does not automatically close pipes, sock- + ets, or co-processes when they return EOF. + + The printf Statement + The AWK versions of the printf statement and sprintf() + function (see below) accept the following conversion + specification formats: + + %c An ASCII character. If the argument used for %c + is numeric, it is treated as a character and + printed. Otherwise, the argument is assumed to + be a string, and the only first character of + that string is printed. + + %d, %i A decimal number (the integer part). + + %e, %E A floating point number of the form + [-]d.dddddde[+-]dd. The %E format uses E + instead of e. + + %f, %F A floating point number of the form + [-]ddd.dddddd. If the system library supports + it, %F is available as well. This is like %f, + but uses capital letters for special "not a num- + ber" and "infinity" values. If %F is not avail- + able, gawk uses %f. + + %g, %G Use %e or %f conversion, whichever is shorter, + with nonsignificant zeros suppressed. The %G + format uses %E instead of %e. + + %o An unsigned octal number (also an integer). + + %u An unsigned decimal number (again, an integer). + + %s A character string. + + %x, %X An unsigned hexadecimal number (an integer). + The %X format uses ABCDEF instead of abcdef. + + %% A single % character; no argument is converted. + + NOTE: When using the integer format-control letters for + values that are outside the range of a C long integer, + gawk switches to the %0f format specifier. If --lint is + provided on the command line gawk warns about this. + Other versions of awk may print invalid values or do + something else entirely. + + Optional, additional parameters may lie between the % + and the control letter: + + count$ Use the count'th argument at this point in the + formatting. This is called a positional speci- + fier and is intended primarily for use in trans- + lated versions of format strings, not in the + original text of an AWK program. It is a gawk + extension. + + - The expression should be left-justified within + its field. + + space For numeric conversions, prefix positive values + with a space, and negative values with a minus + sign. + + + The plus sign, used before the width modifier + (see below), says to always supply a sign for + numeric conversions, even if the data to be for- + matted is positive. The + overrides the space + modifier. + + # Use an "alternate form" for certain control let- + ters. For %o, supply a leading zero. For %x, + and %X, supply a leading 0x or 0X for a nonzero + result. For %e, %E, %f and %F, the result always + contains a decimal point. For %g, and %G, trail- + ing zeros are not removed from the result. + + 0 A leading 0 (zero) acts as a flag, that indicates + output should be padded with zeroes instead of + spaces. This applies even to non-numeric output + formats. This flag only has an effect when the + field width is wider than the value to be + printed. + + width The field should be padded to this width. The + field is normally padded with spaces. If the 0 + flag has been used, it is padded with zeroes. + + .prec A number that specifies the precision to use when + printing. For the %e, %E, %f and %F, formats, + this specifies the number of digits you want + printed to the right of the decimal point. For + the %g, and %G formats, it specifies the maximum + number of significant digits. For the %d, %o, + %i, %u, %x, and %X formats, it specifies the min- + imum number of digits to print. For %s, it spec- + ifies the maximum number of characters from the + string that should be printed. + + The dynamic width and prec capabilities of the ANSI C + printf() routines are supported. A * in place of either + the width or prec specifications causes their values to + be taken from the argument list to printf or sprintf(). + To use a positional specifier with a dynamic width or + precision, supply the count$ after the * in the format + string. For example, "%3$*2$.*1$s". + + Special File Names + When doing I/O redirection from either print or printf + into a file, or via getline from a file, gawk recognizes + certain special filenames internally. These filenames + allow access to open file descriptors inherited from + gawk's parent process (usually the shell). These file + names may also be used on the command line to name data + files. The filenames are: + + /dev/stdin The standard input. + + /dev/stdout The standard output. + + /dev/stderr The standard error output. + + /dev/fd/n The file associated with the open file + descriptor n. + + These are particularly useful for error messages. For + example: + + print "You blew it!" > "/dev/stderr" + + whereas you would otherwise have to use + + print "You blew it!" | "cat 1>&2" + + The following special filenames may be used with the |& + co-process operator for creating TCP/IP network connec- + tions. + + /inet/tcp/lport/rhost/rport File for TCP/IP connection + on local port lport to + remote host rhost on remote + port rport. Use a port of + 0 to have the system pick a + port. + + /inet/udp/lport/rhost/rport Similar, but use UDP/IP + instead of TCP/IP. + + /inet/raw/lport/rhost/rport Reserved for future use. + + Other special filenames provide access to information + about the running gawk process. These filenames are now + obsolete. Use the PROCINFO array to obtain the informa- + tion they provide. The filenames are: + + /dev/pid Reading this file returns the process ID of + the current process, in decimal, terminated + with a newline. + + /dev/ppid Reading this file returns the parent process + ID of the current process, in decimal, ter- + minated with a newline. + + /dev/pgrpid Reading this file returns the process group + ID of the current process, in decimal, ter- + minated with a newline. + + /dev/user Reading this file returns a single record + terminated with a newline. The fields are + separated with spaces. $1 is the value of + the getuid(2) system call, $2 is the value + of the geteuid(2) system call, $3 is the + value of the getgid(2) system call, and $4 + is the value of the getegid(2) system call. + If there are any additional fields, they are + the group IDs returned by getgroups(2). + Multiple groups may not be supported on all + systems. + + Numeric Functions + AWK has the following built-in arithmetic functions: + + + atan2(y, x) Returns the arctangent of y/x in radians. + + cos(expr) Returns the cosine of expr, which is in + radians. + + exp(expr) The exponential function. + + int(expr) Truncates to integer. + + log(expr) The natural logarithm function. + + rand() Returns a random number N, between 0 and + 1, such that 0 <= N < 1. + + sin(expr) Returns the sine of expr, which is in + radians. + + sqrt(expr) The square root function. + + srand([expr]) Uses expr as a new seed for the random + number generator. If no expr is provided, + the time of day is used. The return value + is the previous seed for the random number + generator. + + String Functions + Gawk has the following built-in string functions: + + + asort(s [, d]) Returns the number of elements + in the source array s. The con- + tents of s are sorted using + gawk's normal rules for compar- + ing values, and the indices of + the sorted values of s are + replaced with sequential inte- + gers starting with 1. If the + optional destination array d is + specified, then s is first + duplicated into d, and then d is + sorted, leaving the indices of + the source array s unchanged. + + asorti(s [, d]) Returns the number of elements + in the source array s. The + behavior is the same as that of + asort(), except that the array + indices are used for sorting, + not the array values. When + done, the array is indexed + numerically, and the values are + those of the original indices. + The original values are lost; + thus provide a second array if + you wish to preserve the origi- + nal. + + gensub(r, s, h [, t]) Search the target string t for + matches of the regular expres- + sion r. If h is a string begin- + ning with g or G, then replace + all matches of r with s. Other- + wise, h is a number indicating + which match of r to replace. If + t is not supplied, $0 is used + instead. Within the replacement + text s, the sequence \n, where n + is a digit from 1 to 9, may be + used to indicate just the text + that matched the n'th parenthe- + sized subexpression. The + sequence \0 represents the + entire matched text, as does the + character &. Unlike sub() and + gsub(), the modified string is + returned as the result of the + function, and the original tar- + get string is not changed. + + gsub(r, s [, t]) For each substring matching the + regular expression r in the + string t, substitute the string + s, and return the number of sub- + stitutions. If t is not sup- + plied, use $0. An & in the + replacement text is replaced + with the text that was actually + matched. Use \& to get a lit- + eral &. (This must be typed as + "\\&"; see GAWK: Effective AWK + Programming for a fuller discus- + sion of the rules for &'s and + backslashes in the replacement + text of sub(), gsub(), and gen- + sub().) + + index(s, t) Returns the index of the string + t in the string s, or 0 if t is + not present. (This implies that + character indices start at one.) + + length([s]) Returns the length of the string + s, or the length of $0 if s is + not supplied. Starting with + version 3.1.5, as a non-standard + extension, with an array argu- + ment, length() returns the num- + ber of elements in the array. + + match(s, r [, a]) Returns the position in s where + the regular expression r occurs, + or 0 if r is not present, and + sets the values of RSTART and + RLENGTH. Note that the argument + order is the same as for the ~ + operator: str ~ re. If array a + is provided, a is cleared and + then elements 1 through n are + filled with the portions of s + that match the corresponding + parenthesized subexpression in + r. The 0'th element of a con- + tains the portion of s matched + by the entire regular expression + r. Subscripts a[n, "start"], + and a[n, "length"] provide the + starting index in the string and + length respectively, of each + matching substring. + + split(s, a [, r]) Splits the string s into the + array a on the regular expres- + sion r, and returns the number + of fields. If r is omitted, FS + is used instead. The array a is + cleared first. Splitting + behaves identically to field + splitting, described above. + + sprintf(fmt, expr-list) Prints expr-list according to + fmt, and returns the resulting + string. + + strtonum(str) Examines str, and returns its + numeric value. If str begins + with a leading 0, strtonum() + assumes that str is an octal + number. If str begins with a + leading 0x or 0X, strtonum() + assumes that str is a hexadeci- + mal number. + + sub(r, s [, t]) Just like gsub(), but only the + first matching substring is + replaced. + + substr(s, i [, n]) Returns the at most n-character + substring of s starting at i. + If n is omitted, the rest of s + is used. + + tolower(str) Returns a copy of the string + str, with all the upper-case + characters in str translated to + their corresponding lower-case + counterparts. Non-alphabetic + characters are left unchanged. + + toupper(str) Returns a copy of the string + str, with all the lower-case + characters in str translated to + their corresponding upper-case + counterparts. Non-alphabetic + characters are left unchanged. + + As of version 3.1.5, gawk is multibyte aware. This + means that index(), length(), substr() and match() all + work in terms of characters, not bytes. + + Time Functions + Since one of the primary uses of AWK programs is pro- + cessing log files that contain time stamp information, + gawk provides the following functions for obtaining time + stamps and formatting them. + + + mktime(datespec) + Turns datespec into a time stamp of the same + form as returned by systime(). The datespec + is a string of the form YYYY MM DD HH MM SS[ + DST]. The contents of the string are six or + seven numbers representing respectively the + full year including century, the month from 1 + to 12, the day of the month from 1 to 31, the + hour of the day from 0 to 23, the minute from + 0 to 59, and the second from 0 to 60, and an + optional daylight saving flag. The values of + these numbers need not be within the ranges + specified; for example, an hour of -1 means 1 + hour before midnight. The origin-zero Grego- + rian calendar is assumed, with year 0 preced- + ing year 1 and year -1 preceding year 0. The + time is assumed to be in the local timezone. + If the daylight saving flag is positive, the + time is assumed to be daylight saving time; if + zero, the time is assumed to be standard time; + and if negative (the default), mktime() + attempts to determine whether daylight saving + time is in effect for the specified time. If + datespec does not contain enough elements or + if the resulting time is out of range, + mktime() returns -1. + + strftime([format [, timestamp[, utc-flag]]]) + Formats timestamp according to the specifica- + tion in format. If utc-flag is present and is + non-zero or non-null, the result is in UTC, + otherwise the result is in local time. The + timestamp should be of the same form as + returned by systime(). If timestamp is miss- + ing, the current time of day is used. If for- + mat is missing, a default format equivalent to + the output of date(1) is used. See the speci- + fication for the strftime() function in ANSI C + for the format conversions that are guaranteed + to be available. + + systime() Returns the current time of day as the number + of seconds since the Epoch (1970-01-01 + 00:00:00 UTC on POSIX systems). + + Bit Manipulations Functions + Starting with version 3.1 of gawk, the following bit + manipulation functions are available. They work by con- + verting double-precision floating point values to + uintmax_t integers, doing the operation, and then con- + verting the result back to floating point. The func- + tions are: + + and(v1, v2) Return the bitwise AND of the values + provided by v1 and v2. + + compl(val) Return the bitwise complement of + val. + + lshift(val, count) Return the value of val, shifted + left by count bits. + + or(v1, v2) Return the bitwise OR of the values + provided by v1 and v2. + + rshift(val, count) Return the value of val, shifted + right by count bits. + + xor(v1, v2) Return the bitwise XOR of the values + provided by v1 and v2. + + + Internationalization Functions + Starting with version 3.1 of gawk, the following func- + tions may be used from within your AWK program for + translating strings at run-time. For full details, see + GAWK: Effective AWK Programming. + + bindtextdomain(directory [, domain]) + Specifies the directory where gawk looks for the + .mo files, in case they will not or cannot be + placed in the ``standard'' locations (e.g., dur- + ing testing). It returns the directory where + domain is ``bound.'' + The default domain is the value of TEXTDOMAIN. + If directory is the null string (""), then bind- + textdomain() returns the current binding for the + given domain. + + dcgettext(string [, domain [, category]]) + Returns the translation of string in text domain + domain for locale category category. The default + value for domain is the current value of TEXTDO- + MAIN. The default value for category is "LC_MES- + SAGES". + If you supply a value for category, it must be a + string equal to one of the known locale cate- + gories described in GAWK: Effective AWK Program- + ming. You must also supply a text domain. Use + TEXTDOMAIN if you want to use the current domain. + + dcngettext(string1 , string2 , number [, domain [, cate- + gory]]) + Returns the plural form used for number of the + translation of string1 and string2 in text domain + domain for locale category category. The default + value for domain is the current value of TEXTDO- + MAIN. The default value for category is "LC_MES- + SAGES". + If you supply a value for category, it must be a + string equal to one of the known locale cate- + gories described in GAWK: Effective AWK Program- + ming. You must also supply a text domain. Use + TEXTDOMAIN if you want to use the current domain. + +USER-DEFINED FUNCTIONS + Functions in AWK are defined as follows: + + function name(parameter list) { statements } + + Functions are executed when they are called from within + expressions in either patterns or actions. Actual + parameters supplied in the function call are used to + instantiate the formal parameters declared in the func- + tion. Arrays are passed by reference, other variables + are passed by value. + + Since functions were not originally part of the AWK lan- + guage, the provision for local variables is rather + clumsy: They are declared as extra parameters in the + parameter list. The convention is to separate local + variables from real parameters by extra spaces in the + parameter list. For example: + + function f(p, q, a, b) # a and b are local + { + ... + } + + /abc/ { ... ; f(1, 2) ; ... } + + The left parenthesis in a function call is required to + immediately follow the function name, without any inter- + vening white space. This avoids a syntactic ambiguity + with the concatenation operator. This restriction does + not apply to the built-in functions listed above. + + Functions may call each other and may be recursive. + Function parameters used as local variables are initial- + ized to the null string and the number zero upon func- + tion invocation. + + Use return expr to return a value from a function. The + return value is undefined if no value is provided, or if + the function returns by "falling off" the end. + + If --lint has been provided, gawk warns about calls to + undefined functions at parse time, instead of at run + time. Calling an undefined function at run time is a + fatal error. + + The word func may be used in place of function. + +DYNAMICALLY LOADING NEW FUNCTIONS + Beginning with version 3.1 of gawk, you can dynamically + add new built-in functions to the running gawk inter- + preter. The full details are beyond the scope of this + manual page; see GAWK: Effective AWK Programming for the + details. + + + extension(object, function) + Dynamically link the shared object file named by + object, and invoke function in that object, to + perform initialization. These should both be + provided as strings. Returns the value returned + by function. + + This function is provided and documented in GAWK: Effec- + tive AWK Programming, but everything about this feature + is likely to change eventually. We STRONGLY recommend + that you do not use this feature for anything that you + aren't willing to redo. + +SIGNALS + pgawk accepts two signals. SIGUSR1 causes it to dump a + profile and function call stack to the profile file, + which is either awkprof.out, or whatever file was named + with the --profile option. It then continues to run. + SIGHUP causes pgawk to dump the profile and function + call stack and then exit. + +EXAMPLES + Print and sort the login names of all users: + + BEGIN { FS = ":" } + { print $1 | "sort" } + + Count lines in a file: + + { nlines++ } + END { print nlines } + + Precede each line by its number in the file: + + { print FNR, $0 } + + Concatenate and line number (a variation on a theme): + + { print NR, $0 } + Run an external command for particular lines of data: + + tail -f access_log | + awk '/myhome.html/ { system("nmap " $1 ">> logdir/myhome.html") }' + +INTERNATIONALIZATION + String constants are sequences of characters enclosed in + double quotes. In non-English speaking environments, it + is possible to mark strings in the AWK program as + requiring translation to the native natural language. + Such strings are marked in the AWK program with a lead- + ing underscore ("_"). For example, + + gawk 'BEGIN { print "hello, world" }' + + always prints hello, world. But, + + gawk 'BEGIN { print _"hello, world" }' + + might print bonjour, monde in France. + + There are several steps involved in producing and run- + ning a localizable AWK program. + + 1. Add a BEGIN action to assign a value to the TEXTDO- + MAIN variable to set the text domain to a name asso- + ciated with your program. + + BEGIN { TEXTDOMAIN = "myprog" } + + This allows gawk to find the .mo file associated with + your program. Without this step, gawk uses the messages + text domain, which likely does not contain translations + for your program. + + 2. Mark all strings that should be translated with + leading underscores. + + 3. If necessary, use the dcgettext() and/or bindtextdo- + main() functions in your program, as appropriate. + + 4. Run gawk --gen-po -f myprog.awk > myprog.po to gen- + erate a .po file for your program. + + 5. Provide appropriate translations, and build and + install the corresponding .mo files. + + The internationalization features are described in full + detail in GAWK: Effective AWK Programming. + +POSIX COMPATIBILITY + A primary goal for gawk is compatibility with the POSIX + standard, as well as with the latest version of UNIX + awk. To this end, gawk incorporates the following user + visible features which are not described in the AWK + book, but are part of the Bell Laboratories version of + awk, and are in the POSIX standard. + + The book indicates that command line variable assignment + happens when awk would otherwise open the argument as a + file, which is after the BEGIN block is executed. How- + ever, in earlier implementations, when such an assign- + ment appeared before any file names, the assignment + would happen before the BEGIN block was run. Applica- + tions came to depend on this "feature." When awk was + changed to match its documentation, the -v option for + assigning variables before program execution was added + to accommodate applications that depended upon the old + behavior. (This feature was agreed upon by both the + Bell Laboratories and the GNU developers.) + + The -W option for implementation specific features is + from the POSIX standard. + + When processing arguments, gawk uses the special option + "--" to signal the end of arguments. In compatibility + mode, it warns about but otherwise ignores undefined + options. In normal operation, such arguments are passed + on to the AWK program for it to process. + + The AWK book does not define the return value of + srand(). The POSIX standard has it return the seed it + was using, to allow keeping track of random number + sequences. Therefore srand() in gawk also returns its + current seed. + + Other new features are: The use of multiple -f options + (from MKS awk); the ENVIRON array; the \a, and \v escape + sequences (done originally in gawk and fed back into the + Bell Laboratories version); the tolower() and toupper() + built-in functions (from the Bell Laboratories version); + and the ANSI C conversion specifications in printf (done + first in the Bell Laboratories version). + +HISTORICAL FEATURES + There are two features of historical AWK implementations + that gawk supports. First, it is possible to call the + length() built-in function not only with no argument, + but even without parentheses! Thus, + + a = length # Holy Algol 60, Batman! + + is the same as either of + + a = length() + a = length($0) + + This feature is marked as "deprecated" in the POSIX + standard, and gawk issues a warning about its use if + --lint is specified on the command line. + + The other feature is the use of either the continue or + the break statements outside the body of a while, for, + or do loop. Traditional AWK implementations have + treated such usage as equivalent to the next statement. + Gawk supports this usage if --traditional has been spec- + ified. + +GNU EXTENSIONS + Gawk has a number of extensions to POSIX awk. They are + described in this section. All the extensions described + here can be disabled by invoking gawk with the --tradi- + tional or --posix options. + + The following features of gawk are not available in + POSIX awk. + + · No path search is performed for files named via the -f + option. Therefore the AWKPATH environment variable is + not special. + + · The \x escape sequence. (Disabled with --posix.) + + · The fflush() function. (Disabled with --posix.) + + · The ability to continue lines after ? and :. (Dis- + abled with --posix.) + + · Octal and hexadecimal constants in AWK programs. + + · The ARGIND, BINMODE, ERRNO, LINT, RT and TEXTDOMAIN + variables are not special. + + · The IGNORECASE variable and its side-effects are not + available. + + · The FIELDWIDTHS variable and fixed-width field split- + ting. + + · The PROCINFO array is not available. + + · The use of RS as a regular expression. + + · The special file names available for I/O redirection + are not recognized. + + · The |& operator for creating co-processes. + + · The ability to split out individual characters using + the null string as the value of FS, and as the third + argument to split(). + + · The optional second argument to the close() function. + + · The optional third argument to the match() function. + + · The ability to use positional specifiers with printf + and sprintf(). + + · The ability to pass an array to length(). + + · The use of delete array to delete the entire contents + of an array. + + · The use of nextfile to abandon processing of the cur- + rent input file. + + · The and(), asort(), asorti(), bindtextdomain(), + compl(), dcgettext(), dcngettext(), gensub(), + lshift(), mktime(), or(), rshift(), strftime(), str- + tonum(), systime() and xor() functions. + + · Localizable strings. + + · Adding new built-in functions dynamically with the + extension() function. + + The AWK book does not define the return value of the + close() function. Gawk's close() returns the value from + fclose(3), or pclose(3), when closing an output file or + pipe, respectively. It returns the process's exit sta- + tus when closing an input pipe. The return value is -1 + if the named file, pipe or co-process was not opened + with a redirection. + + When gawk is invoked with the --traditional option, if + the fs argument to the -F option is "t", then FS is set + to the tab character. Note that typing gawk -F\t ... + simply causes the shell to quote the "t," and does not + pass "\t" to the -F option. Since this is a rather ugly + special case, it is not the default behavior. This + behavior also does not occur if --posix has been speci- + fied. To really get a tab character as the field sepa- + rator, it is best to use single quotes: gawk -F'\t' .... + + If gawk is configured with the --enable-switch option to + the configure command, then it accepts an additional + control-flow statement: + switch (expression) { + case value|regex : statement + ... + [ default: statement ] + } + + If gawk is configured with the --disable-directories- + fatal option, then it will silently skip directories + named on the command line. Otherwise, it will do so + only if invoked with the --traditional option. + +ENVIRONMENT VARIABLES + The AWKPATH environment variable can be used to provide + a list of directories that gawk searches when looking + for files named via the -f and --file options. + + If POSIXLY_CORRECT exists in the environment, then gawk + behaves exactly as if --posix had been specified on the + command line. If --lint has been specified, gawk issues + a warning message to this effect. + +SEE ALSO + egrep(1), getpid(2), getppid(2), getpgrp(2), getuid(2), + geteuid(2), getgid(2), getegid(2), getgroups(2) + + The AWK Programming Language, Alfred V. Aho, Brian W. + Kernighan, Peter J. Weinberger, Addison-Wesley, 1988. + ISBN 0-201-07981-X. + + GAWK: Effective AWK Programming, Edition 3.0, published + by the Free Software Foundation, 2001. The current ver- + sion of this document is available online at + http://www.gnu.org/software/gawk/manual. + +BUGS + The -F option is not necessary given the command line + variable assignment feature; it remains only for back- + wards compatibility. + + Syntactically invalid single character programs tend to + overflow the parse stack, generating a rather unhelpful + message. Such programs are surprisingly difficult to + diagnose in the completely general case, and the effort + to do so really is not worth it. + +AUTHORS + The original version of UNIX awk was designed and imple- + mented by Alfred Aho, Peter Weinberger, and Brian + Kernighan of Bell Laboratories. Brian Kernighan contin- + ues to maintain and enhance it. + + Paul Rubin and Jay Fenlason, of the Free Software Foun- + dation, wrote gawk, to be compatible with the original + version of awk distributed in Seventh Edition UNIX. + John Woods contributed a number of bug fixes. David + Trueman, with contributions from Arnold Robbins, made + gawk compatible with the new version of UNIX awk. + Arnold Robbins is the current maintainer. + + The initial DOS port was done by Conrad Kwok and Scott + Garfinkle. Scott Deifik is the current DOS maintainer. + Pat Rankin did the port to VMS, and Michal Jaegermann + did the port to the Atari ST. The port to OS/2 was done + by Kai Uwe Rommel, with contributions and help from Dar- + rel Hankerson. Juan M. Guerrero now maintains the OS/2 + port. Fred Fish supplied support for the Amiga, and + Martin Brown provided the BeOS port. Stephen Davies + provided the original Tandem port, and Matthew Woehlke + provided changes for Tandem's POSIX-compliant systems. + +VERSION INFORMATION + This man page documents gawk, version 3.1.6. + +BUG REPORTS + If you find a bug in gawk, please send electronic mail + to bug-gawk@gnu.org. Please include your operating sys- + tem and its revision, the version of gawk (from gawk + --version), what C compiler you used to compile it, and + a test program and data that are as small as possible + for reproducing the problem. + + Before sending a bug report, please do the following + things. First, verify that you have the latest version + of gawk. Many bugs (usually subtle ones) are fixed at + each release, and if yours is out of date, the problem + may already have been solved. Second, please see if + setting the environment variable LC_ALL to LC_ALL=C + causes things to behave as you expect. If so, it's a + locale issue, and may or may not really be a bug. + Finally, please read this man page and the reference + manual carefully to be sure that what you think is a bug + really is, instead of just a quirk in the language. + + Whatever you do, do NOT post a bug report in + comp.lang.awk. While the gawk developers occasionally + read this newsgroup, posting bug reports there is an + unreliable way to report bugs. Instead, please use the + electronic mail addresses given above. + + If you're using a GNU/Linux system or BSD-based system, + you may wish to submit a bug report to the vendor of + your distribution. That's fine, but please send a copy + to the official email address as well, since there's no + guarantee that the bug will be forwarded to the gawk + maintainer. + +ACKNOWLEDGEMENTS + Brian Kernighan of Bell Laboratories provided valuable + assistance during testing and debugging. We thank him. + +COPYING PERMISSIONS + Copyright © 1989, 1991, 1992, 1993, 1994, 1995, 1996, + 1997, 1998, 1999, 2001, 2002, 2003, 2004, 2005, 2007 + Free Software Foundation, Inc. + + Permission is granted to make and distribute verbatim + copies of this manual page provided the copyright notice + and this permission notice are preserved on all copies. + + Permission is granted to copy and distribute modified + versions of this manual page under the conditions for + verbatim copying, provided that the entire resulting + derived work is distributed under the terms of a permis- + sion notice identical to this one. + + Permission is granted to copy and distribute transla- + tions of this manual page into another language, under + the above conditions for modified versions, except that + this permission notice may be stated in a translation + approved by the Foundation. + + + +Free Software Foundation Oct 19 2007 GAWK(1) diff --git a/coreutils-5.3.0-bin/man/cat1/groups.1.txt b/coreutils-5.3.0-bin/man/cat1/groups.1.txt new file mode 100644 index 0000000..f08bc6d --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/groups.1.txt @@ -0,0 +1,44 @@ +GROUPS(1) User Commands GROUPS(1) + + + + + +NAME + groups - print the groups a user is in + +SYNOPSIS + groups [OPTION]... [USERNAME]... + +DESCRIPTION + --help display this help and exit + + --version + output version information and exit + + Same as id -Gn. If no USERNAME, use current process. + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for groups is maintained as a + Texinfo manual. If the info and groups programs are + properly installed at your site, the command + + info groups + + should give you access to the complete manual. + + + +groups 5.3.0 November 2004 GROUPS(1) diff --git a/coreutils-5.3.0-bin/man/cat1/head.1.txt b/coreutils-5.3.0-bin/man/cat1/head.1.txt new file mode 100644 index 0000000..851f555 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/head.1.txt @@ -0,0 +1,69 @@ +HEAD(1) User Commands HEAD(1) + + + + + +NAME + head - output the first part of files + +SYNOPSIS + head [OPTION]... [FILE]... + +DESCRIPTION + Print the first 10 lines of each FILE to standard out- + put. With more than one FILE, precede each with a + header giving the file name. With no FILE, or when FILE + is -, read standard input. + + Mandatory arguments to long options are mandatory for + short options too. + + -c, --bytes=[-]N + print the first N bytes of each file; with the + leading `-', print all but the last N bytes of + each file + + -n, --lines=[-]N + print the first N lines instead of the first 10; + with the leading `-', print all but the last N + lines of each file + + -q, --quiet, --silent + never print headers giving file names + + -v, --verbose + always print headers giving file names + + --help display this help and exit + + --version + output version information and exit + + N may have a multiplier suffix: b 512, k 1024, m + 1024*1024. + +AUTHOR + Written by David MacKenzie and Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for head is maintained as a Tex- + info manual. If the info and head programs are properly + installed at your site, the command + + info head + + should give you access to the complete manual. + + + +head 5.3.0 November 2004 HEAD(1) diff --git a/coreutils-5.3.0-bin/man/cat1/hostid.1.txt b/coreutils-5.3.0-bin/man/cat1/hostid.1.txt new file mode 100644 index 0000000..57f4b2c --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/hostid.1.txt @@ -0,0 +1,48 @@ +HOSTID(1) User Commands HOSTID(1) + + + + + +NAME + hostid - print the numeric identifier for the current + host + +SYNOPSIS + hostid + + hostid OPTION + +DESCRIPTION + Print the numeric identifier (in hexadecimal) for the + current host. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for hostid is maintained as a + Texinfo manual. If the info and hostid programs are + properly installed at your site, the command + + info hostid + + should give you access to the complete manual. + + + +hostid 5.3.0 November 2004 HOSTID(1) diff --git a/coreutils-5.3.0-bin/man/cat1/hostname.1.txt b/coreutils-5.3.0-bin/man/cat1/hostname.1.txt new file mode 100644 index 0000000..e774633 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/hostname.1.txt @@ -0,0 +1,46 @@ +HOSTNAME(1) User Commands HOSTNAME(1) + + + + + +NAME + hostname - set or print the name of the current host + system + +SYNOPSIS + hostname [NAME] + hostname OPTION + +DESCRIPTION + Print or set the hostname of the current system. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for hostname is maintained as a + Texinfo manual. If the info and hostname programs are + properly installed at your site, the command + + info hostname + + should give you access to the complete manual. + + + +hostname 5.3.0 November 2004 HOSTNAME(1) diff --git a/coreutils-5.3.0-bin/man/cat1/id.1.txt b/coreutils-5.3.0-bin/man/cat1/id.1.txt new file mode 100644 index 0000000..6f2d40f --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/id.1.txt @@ -0,0 +1,65 @@ +ID(1) User Commands ID(1) + + + + + +NAME + id - print real and effective UIDs and GIDs + +SYNOPSIS + id [OPTION]... [USERNAME] + +DESCRIPTION + Print information for USERNAME, or the current user. + + -a ignore, for compatibility with other versions + + -g, --group + print only the effective group ID + + -G, --groups + print all group IDs + + -n, --name + print a name instead of a number, for -ugG + + -r, --real + print the real ID instead of the effective ID, + with -ugG + + -u, --user + print only the effective user ID + + --help display this help and exit + + --version + output version information and exit + + Without any OPTION, print some useful set of identified + information. + +AUTHOR + Written by Arnold Robbins and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for id is maintained as a Texinfo + manual. If the info and id programs are properly + installed at your site, the command + + info id + + should give you access to the complete manual. + + + +id 5.3.0 November 2004 ID(1) diff --git a/coreutils-5.3.0-bin/man/cat1/igawk.1.txt b/coreutils-5.3.0-bin/man/cat1/igawk.1.txt new file mode 100644 index 0000000..c3d142c --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/igawk.1.txt @@ -0,0 +1,53 @@ +IGAWK(1) Utility Commands IGAWK(1) + + + +NAME + igawk - gawk with include files + +SYNOPSIS + igawk [ all gawk options ] -f program-file [ -- ] file + ... + igawk [ all gawk options ] [ -- ] program-text file ... + +DESCRIPTION + Igawk is a simple shell script that adds the ability to + have ``include files'' to gawk(1). + + AWK programs for igawk are the same as for gawk, except + that, in addition, you may have lines like + + @include getopt.awk + + in your program to include the file getopt.awk from + either the current directory or one of the other direc- + tories in the search path. + +OPTIONS + See gawk(1) for a full description of the AWK language + and the options that gawk supports. + +EXAMPLES + cat << EOF > test.awk + @include getopt.awk + + BEGIN { + while (getopt(ARGC, ARGV, "am:q") != -1) + ... + } + EOF + + igawk -f test.awk + +SEE ALSO + gawk(1) + + Effective AWK Programming, Edition 1.0, published by the + Free Software Foundation, 1995. + +AUTHOR + Arnold Robbins (arnold@skeeve.com). + + + +Free Software Foundation Nov 3 1999 IGAWK(1) diff --git a/coreutils-5.3.0-bin/man/cat1/install.1.txt b/coreutils-5.3.0-bin/man/cat1/install.1.txt new file mode 100644 index 0000000..369116e --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/install.1.txt @@ -0,0 +1,114 @@ +INSTALL(1) User Commands INSTALL(1) + + + + + +NAME + install - copy files and set attributes + +SYNOPSIS + install [OPTION]... [-T] SOURCE DEST + install [OPTION]... SOURCE... DIRECTORY + install [OPTION]... -t DIRECTORY SOURCE... + install [OPTION]... -d DIRECTORY... + +DESCRIPTION + In the first three forms, copy SOURCE to DEST or multi- + ple SOURCE(s) to the existing DIRECTORY, while setting + permission modes and owner/group. In the 4th form, cre- + ate all components of the given DIRECTORY(ies). + + Mandatory arguments to long options are mandatory for + short options too. + + --backup[=CONTROL] make a backup of each existing desti- + nation file + + -b like --backup but does not accept an argument + + -c (ignored) + + -d, --directory + treat all arguments as directory names; create + all components of the specified directories + + -D create all leading components of DEST except the + last, then copy SOURCE to DEST + + -g, --group=GROUP + set group ownership, instead of process' current + group + + -m, --mode=MODE + set permission mode (as in chmod), instead of + rwxr-xr-x + + -o, --owner=OWNER + set ownership (super-user only) + + -p, --preserve-timestamps + apply access/modification times of SOURCE files + to corresponding destination files + + -s, --strip + strip symbol tables + + -S, --suffix=SUFFIX override the usual backup suffix + + -t, --target-directory=DIRECTORY + copy all SOURCE arguments into DIRECTORY + + -T, --no-target-directory + treat DEST as a normal file + + -v, --verbose + print the name of each directory as it is created + + --help display this help and exit + + --version + output version information and exit + + The backup suffix is `~', unless set with --suffix or + SIMPLE_BACKUP_SUFFIX. The version control method may be + selected via the --backup option or through the VER- + SION_CONTROL environment variable. Here are the values: + + none, off + never make backups (even if --backup is given) + + numbered, t + make numbered backups + + existing, nil + numbered if numbered backups exist, simple other- + wise + + simple, never + always make simple backups + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for install is maintained as a + Texinfo manual. If the info and install programs are + properly installed at your site, the command + + info install + + should give you access to the complete manual. + + + +install 5.3.0 November 2004 INSTALL(1) diff --git a/coreutils-5.3.0-bin/man/cat1/join.1.txt b/coreutils-5.3.0-bin/man/cat1/join.1.txt new file mode 100644 index 0000000..32597ba --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/join.1.txt @@ -0,0 +1,87 @@ +JOIN(1) User Commands JOIN(1) + + + + + +NAME + join - join lines of two files on a common field + +SYNOPSIS + join [OPTION]... FILE1 FILE2 + +DESCRIPTION + For each pair of input lines with identical join fields, + write a line to standard output. The default join field + is the first, delimited by whitespace. When FILE1 or + FILE2 (not both) is -, read standard input. + + -a FILENUM + print unpairable lines coming from file FILENUM, + where FILENUM is 1 or 2, corresponding to FILE1 + or FILE2 + + -e EMPTY + replace missing input fields with EMPTY + + -i, --ignore-case ignore differences in case when com- + paring fields + + -j FIELD + equivalent to `-1 FIELD -2 FIELD' + + -o FORMAT + obey FORMAT while constructing output line + + -t CHAR + use CHAR as input and output field separator + + -v FILENUM + like -a FILENUM, but suppress joined output lines + + -1 FIELD + join on this FIELD of file 1 + + -2 FIELD + join on this FIELD of file 2 + + --help display this help and exit + + --version + output version information and exit + + Unless -t CHAR is given, leading blanks separate fields + and are ignored, else fields are separated by CHAR. Any + FIELD is a field number counted from 1. FORMAT is one + or more comma or blank separated specifications, each + being `FILENUM.FIELD' or `0'. Default FORMAT outputs + the join field, the remaining fields from FILE1, the + remaining fields from FILE2, all separated by CHAR. + + Important: FILE1 and FILE2 must be sorted on the join + fields. + +AUTHOR + Written by Mike Haertel. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for join is maintained as a Tex- + info manual. If the info and join programs are properly + installed at your site, the command + + info join + + should give you access to the complete manual. + + + +join 5.3.0 December 2004 JOIN(1) diff --git a/coreutils-5.3.0-bin/man/cat1/kill.1.txt b/coreutils-5.3.0-bin/man/cat1/kill.1.txt new file mode 100644 index 0000000..9c7f87b --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/kill.1.txt @@ -0,0 +1,66 @@ +KILL(1) User Commands KILL(1) + + + + + +NAME + kill - send signals to processes, or list signals + +SYNOPSIS + kill [-s SIGNAL | -SIGNAL] PID... + kill -l [SIGNAL]... + kill -t [SIGNAL]... + +DESCRIPTION + Send signals to processes, or list signals. + + Mandatory arguments to long options are mandatory for + short options too. + + -s, --signal=SIGNAL, -SIGNAL + + specify the name or number of the signal to be + sent + + -l, --list + list signal names, or convert signal names + to/from numbers + + -t, --table + print a table of signal information + + --help display this help and exit + + --version + output version information and exit + + SIGNAL may be a signal name like `HUP', or a signal num- + ber like `1', or an exit status of a process terminated + by a signal. PID is an integer; if negative it identi- + fies a process group. + +AUTHOR + Written by Paul Eggert. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for kill is maintained as a Tex- + info manual. If the info and kill programs are properly + installed at your site, the command + + info kill + + should give you access to the complete manual. + + + +kill 5.3.0 November 2004 KILL(1) diff --git a/coreutils-5.3.0-bin/man/cat1/link.1.txt b/coreutils-5.3.0-bin/man/cat1/link.1.txt new file mode 100644 index 0000000..13e16f6 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/link.1.txt @@ -0,0 +1,46 @@ +LINK(1) User Commands LINK(1) + + + + + +NAME + link - call the link function to create a link to a file + +SYNOPSIS + link FILE1 FILE2 + link OPTION + +DESCRIPTION + Call the link function to create a link named FILE2 to + an existing FILE1. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Michael Stone. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for link is maintained as a Tex- + info manual. If the info and link programs are properly + installed at your site, the command + + info link + + should give you access to the complete manual. + + + +link 5.3.0 November 2004 LINK(1) diff --git a/coreutils-5.3.0-bin/man/cat1/ln.1.txt b/coreutils-5.3.0-bin/man/cat1/ln.1.txt new file mode 100644 index 0000000..b83cfff --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/ln.1.txt @@ -0,0 +1,110 @@ +LN(1) User Commands LN(1) + + + + + +NAME + ln - make links between files + +SYNOPSIS + ln [OPTION]... [-T] TARGET LINK_NAME (1st form) + ln [OPTION]... TARGET (2nd form) + ln [OPTION]... TARGET... DIRECTORY (3rd form) + ln [OPTION]... -t DIRECTORY TARGET... (4th form) + +DESCRIPTION + In the 1st form, create a link to TARGET with the name + LINK_NAME. In the 2nd form, create a link to TARGET in + the current directory. In the 3rd and 4th forms, create + links to each TARGET in DIRECTORY. Create hard links by + default, symbolic links with --symbolic. When creating + hard links, each TARGET must exist. + + Mandatory arguments to long options are mandatory for + short options too. + + --backup[=CONTROL] + make a backup of each existing destination file + + -b like --backup but does not accept an argument + + -d, -F, --directory + allow the superuser to attempt to hard link + directories (note: will probably fail due to sys- + tem restrictions, even for the superuser) + + -f, --force + remove existing destination files + + -n, --no-dereference + treat destination that is a symlink to a direc- + tory as if it were a normal file + + -i, --interactive + prompt whether to remove destinations + + -s, --symbolic + make symbolic links instead of hard links + + -S, --suffix=SUFFIX + override the usual backup suffix + + -t, --target-directory=DIRECTORY + specify the DIRECTORY in which to create the + links + + -T, --no-target-directory + treat LINK_NAME as a normal file + + -v, --verbose + print name of each file before linking + + --help display this help and exit + + --version + output version information and exit + + The backup suffix is `~', unless set with --suffix or + SIMPLE_BACKUP_SUFFIX. The version control method may be + selected via the --backup option or through the + VERSION_CONTROL environment variable. Here are the val- + ues: + + none, off + never make backups (even if --backup is given) + + numbered, t + make numbered backups + + existing, nil + numbered if numbered backups exist, simple other- + wise + + simple, never + always make simple backups + +AUTHOR + Written by Mike Parker and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for ln is maintained as a Texinfo + manual. If the info and ln programs are properly + installed at your site, the command + + info ln + + should give you access to the complete manual. + + + +ln 5.3.0 November 2004 LN(1) diff --git a/coreutils-5.3.0-bin/man/cat1/logname.1.txt b/coreutils-5.3.0-bin/man/cat1/logname.1.txt new file mode 100644 index 0000000..1f75c71 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/logname.1.txt @@ -0,0 +1,44 @@ +LOGNAME(1) User Commands LOGNAME(1) + + + + + +NAME + logname - print user's login name + +SYNOPSIS + logname [OPTION] + +DESCRIPTION + Print the name of the current user. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by FIXME: unknown. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for logname is maintained as a + Texinfo manual. If the info and logname programs are + properly installed at your site, the command + + info logname + + should give you access to the complete manual. + + + +logname 5.3.0 November 2004 LOGNAME(1) diff --git a/coreutils-5.3.0-bin/man/cat1/ls.1.txt b/coreutils-5.3.0-bin/man/cat1/ls.1.txt new file mode 100644 index 0000000..0240658 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/ls.1.txt @@ -0,0 +1,233 @@ +LS(1) User Commands LS(1) + + + + + +NAME + ls - list directory contents + +SYNOPSIS + ls [OPTION]... [FILE]... + +DESCRIPTION + List information about the FILEs (the current directory + by default). Sort entries alphabetically if none of + -cftuSUX nor --sort. + + Mandatory arguments to long options are mandatory for + short options too. + + -a, --all + do not ignore entries starting with . + + -A, --almost-all + do not list implied . and .. + + --author + with -l, print the author of each file + + -b, --escape + print octal escapes for nongraphic characters + + --block-size=SIZE + use SIZE-byte blocks + + -B, --ignore-backups + do not list implied entries ending with ~ + + -c with -lt: sort by, and show, ctime (time of last + modification of file status information) with -l: + show ctime and sort by name otherwise: sort by + ctime + + -C list entries by columns + + --color[=WHEN] + control whether color is used to distinguish file + types. WHEN may be `never', `always', or `auto' + + -d, --directory + list directory entries instead of contents, and + do not dereference symbolic links + + -D, --dired + generate output designed for Emacs' dired mode + + -f do not sort, enable -aU, disable -lst + + -F, --classify + append indicator (one of */=@|) to entries + + --format=WORD + across -x, commas -m, horizontal -x, long -l, + single-column -1, verbose -l, vertical -C + + --full-time + like -l --time-style=full-iso + + -g like -l, but do not list owner + + -G, --no-group + like -l, but do not list group + + -h, --human-readable + with -l, print sizes in human readable format + (e.g., 1K 234M 2G) + + --si likewise, but use powers of 1000 not 1024 + + -H, --dereference-command-line + follow symbolic links listed on the command line + + --dereference-command-line-symlink-to-dir + follow each command line symbolic link that + points to a directory + + --hide=PATTERN + do not list implied entries matching shell PAT- + TERN (overridden by -a or -A) + + --indicator-style=WORD append indicator with style WORD + to entry names: + none (default), classify (-F), file-type (-p) + + -i, --inode + with -l, print the index number of each file + + -I, --ignore=PATTERN + do not list implied entries matching shell PAT- + TERN + + -k like --block-size=1K + + -l use a long listing format + + -L, --dereference + when showing file information for a symbolic + link, show information for the file the link ref- + erences rather than for the link itself + + -m fill width with a comma separated list of entries + + -n, --numeric-uid-gid + like -l, but list numeric UIDs and GIDs + + -N, --literal + print raw entry names (don't treat e.g. control + characters specially) + + -o like -l, but do not list group information + + -p, --file-type + append indicator (one of /=@|) to entries + + -q, --hide-control-chars + print ? instead of non graphic characters + + --show-control-chars + show non graphic characters as-is (default unless + program is `ls' and output is a terminal) + + -Q, --quote-name + enclose entry names in double quotes + + --quoting-style=WORD + use quoting style WORD for entry names: literal, + locale, shell, shell-always, c, escape + + -r, --reverse + reverse order while sorting + + -R, --recursive + list subdirectories recursively + + -s, --size + with -l, print size of each file, in blocks + + -S sort by file size + + --sort=WORD + extension -X, none -U, size -S, time -t, version + -v, status -c, time -t, atime -u, access -u, use + -u + + --time=WORD + with -l, show time as WORD instead of modifica- + tion time: atime, access, use, ctime or status; + use specified time as sort key if --sort=time + + --time-style=STYLE + with -l, show times using style STYLE: full-iso, + long-iso, iso, locale, +FORMAT. FORMAT is inter- + preted like `date'; if FORMAT is FORMAT1<new- + line>FORMAT2, FORMAT1 applies to non-recent files + and FORMAT2 to recent files; if STYLE is prefixed + with `posix-', STYLE takes effect only outside + the POSIX locale + + -t sort by modification time + + -T, --tabsize=COLS + assume tab stops at each COLS instead of 8 + + -u with -lt: sort by, and show, access time with -l: + show access time and sort by name otherwise: sort + by access time + + -U do not sort; list entries in directory order + + -v sort by version + + -w, --width=COLS + assume screen width instead of current value + + -x list entries by lines instead of by columns + + -X sort alphabetically by entry extension + + -1 list one file per line + + --help display this help and exit + + --version + output version information and exit + + SIZE may be (or may be an integer optionally followed + by) one of following: kB 1000, K 1024, MB 1000*1000, M + 1024*1024, and so on for G, T, P, E, Z, Y. + + By default, color is not used to distinguish types of + files. That is equivalent to using --color=none. Using + the --color option without the optional WHEN argument is + equivalent to using --color=always. With --color=auto, + color codes are output only if standard output is con- + nected to a terminal (tty). + + Exit status is 0 if OK, 1 if minor problems, 2 if seri- + ous trouble. + +AUTHOR + Written by Richard Stallman and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for ls is maintained as a Texinfo + manual. If the info and ls programs are properly + installed at your site, the command + + info ls + + should give you access to the complete manual. + + + +ls 5.3.0 December 2004 LS(1) diff --git a/coreutils-5.3.0-bin/man/cat1/md5sum.1.txt b/coreutils-5.3.0-bin/man/cat1/md5sum.1.txt new file mode 100644 index 0000000..ecd8d68 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/md5sum.1.txt @@ -0,0 +1,70 @@ +MD5SUM(1) User Commands MD5SUM(1) + + + + + +NAME + md5sum - compute and check MD5 message digest + +SYNOPSIS + md5sum [OPTION] [FILE]... + md5sum [OPTION] --check [FILE] + +DESCRIPTION + Print or check MD5 (128-bit) checksums. With no FILE, + or when FILE is -, read standard input. + + -b, --binary + read files in binary mode (default on DOS/Win- + dows) + + -c, --check + check MD5 sums against given list + + -t, --text + read files in text mode (default) + + The following two options are useful only when verifying + checksums: + --status + don't output anything, status code shows success + + -w, --warn + warn about improperly formated checksum lines + + --help display this help and exit + + --version + output version information and exit + + The sums are computed as described in RFC 1321. When + checking, the input should be a former output of this + program. The default mode is to print a line with + checksum, a character indicating type (`*' for binary, ` + ' for text), and name for each FILE. + +AUTHOR + Written by Ulrich Drepper and Scott Miller. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for md5sum is maintained as a + Texinfo manual. If the info and md5sum programs are + properly installed at your site, the command + + info md5sum + + should give you access to the complete manual. + + + +md5sum 5.3.0 November 2004 MD5SUM(1) diff --git a/coreutils-5.3.0-bin/man/cat1/mkdir.1.txt b/coreutils-5.3.0-bin/man/cat1/mkdir.1.txt new file mode 100644 index 0000000..fb87537 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/mkdir.1.txt @@ -0,0 +1,58 @@ +MKDIR(1) User Commands MKDIR(1) + + + + + +NAME + mkdir - make directories + +SYNOPSIS + mkdir [OPTION] DIRECTORY... + +DESCRIPTION + Create the DIRECTORY(ies), if they do not already exist. + + Mandatory arguments to long options are mandatory for + short options too. + + -m, --mode=MODE + set permission mode (as in chmod), not rwxrwxrwx + - umask + + -p, --parents + no error if existing, make parent directories as + needed + + -v, --verbose + print a message for each created directory + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for mkdir is maintained as a Tex- + info manual. If the info and mkdir programs are prop- + erly installed at your site, the command + + info mkdir + + should give you access to the complete manual. + + + +mkdir 5.3.0 November 2004 MKDIR(1) diff --git a/coreutils-5.3.0-bin/man/cat1/mkfifo.1.txt b/coreutils-5.3.0-bin/man/cat1/mkfifo.1.txt new file mode 100644 index 0000000..ec00be3 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/mkfifo.1.txt @@ -0,0 +1,51 @@ +MKFIFO(1) User Commands MKFIFO(1) + + + + + +NAME + mkfifo - make FIFOs (named pipes) + +SYNOPSIS + mkfifo [OPTION] NAME... + +DESCRIPTION + Create named pipes (FIFOs) with the given NAMEs. + + Mandatory arguments to long options are mandatory for + short options too. + + -m, --mode=MODE + set permission mode (as in chmod), not a=rw - + umask + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for mkfifo is maintained as a + Texinfo manual. If the info and mkfifo programs are + properly installed at your site, the command + + info mkfifo + + should give you access to the complete manual. + + + +mkfifo 5.3.0 November 2004 MKFIFO(1) diff --git a/coreutils-5.3.0-bin/man/cat1/mknod.1.txt b/coreutils-5.3.0-bin/man/cat1/mknod.1.txt new file mode 100644 index 0000000..f494bbf --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/mknod.1.txt @@ -0,0 +1,63 @@ +MKNOD(1) User Commands MKNOD(1) + + + + + +NAME + mknod - make block or character special files + +SYNOPSIS + mknod [OPTION]... NAME TYPE [MAJOR MINOR] + +DESCRIPTION + Create the special file NAME of the given TYPE. + + Mandatory arguments to long options are mandatory for + short options too. + + -m, --mode=MODE + set permission mode (as in chmod), not a=rw - + umask + + --help display this help and exit + + --version + output version information and exit + + Both MAJOR and MINOR must be specified when TYPE is b, + c, or u, and they must be omitted when TYPE is p. If + MAJOR or MINOR begins with 0x or 0X, it is interpreted + as hexadecimal; otherwise, if it begins with 0, as + octal; otherwise, as decimal. TYPE may be: + + b create a block (buffered) special file + + c, u create a character (unbuffered) special file + + p create a FIFO + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for mknod is maintained as a Tex- + info manual. If the info and mknod programs are prop- + erly installed at your site, the command + + info mknod + + should give you access to the complete manual. + + + +mknod 5.3.0 November 2004 MKNOD(1) diff --git a/coreutils-5.3.0-bin/man/cat1/mv.1.txt b/coreutils-5.3.0-bin/man/cat1/mv.1.txt new file mode 100644 index 0000000..05c0293 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/mv.1.txt @@ -0,0 +1,106 @@ +MV(1) User Commands MV(1) + + + + + +NAME + mv - move (rename) files + +SYNOPSIS + mv [OPTION]... [-T] SOURCE DEST + mv [OPTION]... SOURCE... DIRECTORY + mv [OPTION]... -t DIRECTORY SOURCE... + +DESCRIPTION + Rename SOURCE to DEST, or move SOURCE(s) to DIRECTORY. + + Mandatory arguments to long options are mandatory for + short options too. + + --backup[=CONTROL] + make a backup of each existing destination file + + -b like --backup but does not accept an argument + + -f, --force + do not prompt before overwriting (equivalent to + --reply=yes) + + -i, --interactive + prompt before overwrite (equivalent to + --reply=query) + + --reply={yes,no,query} + specify how to handle the prompt about an exist- + ing destination file + + --strip-trailing-slashes remove any trailing slashes + from each SOURCE + argument + + -S, --suffix=SUFFIX + override the usual backup suffix + + -t, --target-directory=DIRECTORY + move all SOURCE arguments into DIRECTORY + + -T, --no-target-directory + treat DEST as a normal file + + -u, --update + move only when the SOURCE file is newer than the + destination file or when the destination file is + missing + + -v, --verbose + explain what is being done + + --help display this help and exit + + --version + output version information and exit + + The backup suffix is `~', unless set with --suffix or + SIMPLE_BACKUP_SUFFIX. The version control method may be + selected via the --backup option or through the VER- + SION_CONTROL environment variable. Here are the values: + + none, off + never make backups (even if --backup is given) + + numbered, t + make numbered backups + + existing, nil + numbered if numbered backups exist, simple other- + wise + + simple, never + always make simple backups + +AUTHOR + Written by Mike Parker, David MacKenzie, and Jim Meyer- + ing. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for mv is maintained as a Texinfo + manual. If the info and mv programs are properly + installed at your site, the command + + info mv + + should give you access to the complete manual. + + + +mv 5.3.0 November 2004 MV(1) diff --git a/coreutils-5.3.0-bin/man/cat1/nice.1.txt b/coreutils-5.3.0-bin/man/cat1/nice.1.txt new file mode 100644 index 0000000..d41ac21 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/nice.1.txt @@ -0,0 +1,50 @@ +NICE(1) User Commands NICE(1) + + + + + +NAME + nice - run a program with modified scheduling priority + +SYNOPSIS + nice [OPTION] [COMMAND [ARG]...] + +DESCRIPTION + Run COMMAND with an adjusted nice value, which affects + the scheduling priority. With no COMMAND, print the + current nice value. Nice values range from -20 (most + favorable scheduling) to 19 (least favorable). + + -n, --adjustment=N + add integer N to the nice value (default 10) + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for nice is maintained as a Tex- + info manual. If the info and nice programs are properly + installed at your site, the command + + info nice + + should give you access to the complete manual. + + + +nice 5.3.0 November 2004 NICE(1) diff --git a/coreutils-5.3.0-bin/man/cat1/nl.1.txt b/coreutils-5.3.0-bin/man/cat1/nl.1.txt new file mode 100644 index 0000000..2baa72b --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/nl.1.txt @@ -0,0 +1,106 @@ +NL(1) User Commands NL(1) + + + + + +NAME + nl - number lines of files + +SYNOPSIS + nl [OPTION]... [FILE]... + +DESCRIPTION + Write each FILE to standard output, with line numbers + added. With no FILE, or when FILE is -, read standard + input. + + Mandatory arguments to long options are mandatory for + short options too. + + -b, --body-numbering=STYLE + use STYLE for numbering body lines + + -d, --section-delimiter=CC + use CC for separating logical pages + + -f, --footer-numbering=STYLE + use STYLE for numbering footer lines + + -h, --header-numbering=STYLE + use STYLE for numbering header lines + + -i, --page-increment=NUMBER + line number increment at each line + + -l, --join-blank-lines=NUMBER + group of NUMBER empty lines counted as one + + -n, --number-format=FORMAT + insert line numbers according to FORMAT + + -p, --no-renumber + do not reset line numbers at logical pages + + -s, --number-separator=STRING + add STRING after (possible) line number + + -v, --first-page=NUMBER + first line number on each logical page + + -w, --number-width=NUMBER + use NUMBER columns for line numbers + + --help display this help and exit + + --version + output version information and exit + + By default, selects -v1 -i1 -l1 -sTAB -w6 -nrn -hn -bt + -fn. CC are two delimiter characters for separating + logical pages, a missing second character implies :. + Type \\ for \. STYLE is one of: + + a number all lines + + t number only nonempty lines + + n number no lines + + pBRE number only lines that contain a match for the + basic regular + + expression, BRE + + FORMAT is one of: + + ln left justified, no leading zeros + + rn right justified, no leading zeros + + rz right justified, leading zeros + +AUTHOR + Written by Scott Bartram and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for nl is maintained as a Texinfo + manual. If the info and nl programs are properly + installed at your site, the command + + info nl + + should give you access to the complete manual. + + + +nl 5.3.0 November 2004 NL(1) diff --git a/coreutils-5.3.0-bin/man/cat1/nohup.1.txt b/coreutils-5.3.0-bin/man/cat1/nohup.1.txt new file mode 100644 index 0000000..4a28728 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/nohup.1.txt @@ -0,0 +1,46 @@ +NOHUP(1) User Commands NOHUP(1) + + + + + +NAME + nohup - run a command immune to hangups, with output to + a non-tty + +SYNOPSIS + nohup COMMAND [ARG]... + nohup OPTION + +DESCRIPTION + Run COMMAND, ignoring hangup signals. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for nohup is maintained as a Tex- + info manual. If the info and nohup programs are prop- + erly installed at your site, the command + + info nohup + + should give you access to the complete manual. + + + +nohup 5.3.0 November 2004 NOHUP(1) diff --git a/coreutils-5.3.0-bin/man/cat1/od.1.txt b/coreutils-5.3.0-bin/man/cat1/od.1.txt new file mode 100644 index 0000000..7e73270 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/od.1.txt @@ -0,0 +1,147 @@ +OD(1) User Commands OD(1) + + + + + +NAME + od - dump files in octal and other formats + +SYNOPSIS + od [OPTION]... [FILE]... + od [-abcdfilosx]... [FILE] [[+]OFFSET[.][b]] + od --traditional [OPTION]... [FILE] [[+]OFFSET[.][b] + [+][LABEL][.][b]] + +DESCRIPTION + Write an unambiguous representation, octal bytes by + default, of FILE to standard output. With more than one + FILE argument, concatenate them in the listed order to + form the input. With no FILE, or when FILE is -, read + standard input. + + All arguments to long options are mandatory for short + options. + + -A, --address-radix=RADIX + decide how file offsets are printed + + -j, --skip-bytes=BYTES + skip BYTES input bytes first + + -N, --read-bytes=BYTES + limit dump to BYTES input bytes + + -S, --strings[=BYTES] + output strings of at least BYTES graphic chars + + -t, --format=TYPE + select output format or formats + + -v, --output-duplicates + do not use * to mark line suppression + + -w, --width[=BYTES] + output BYTES bytes per output line + + --traditional + accept arguments in traditional form + + --help display this help and exit + + --version + output version information and exit + + Traditional format specifications may be intermixed; they + accumulate: + -a same as -t a, select named characters + + -b same as -t o1, select octal bytes + + -c same as -t c, select ASCII characters or back- + slash escapes + + -d same as -t u2, select unsigned decimal 2-byte + units + + -f same as -t fF, select floats + + -i same as -t dI, select decimal ints + + -l same as -t dL, select decimal longs + + -o same as -t o2, select octal 2-byte units + + -s same as -t d2, select decimal 2-byte units + + -x same as -t x2, select hexadecimal 2-byte units + + If first and second call formats both apply, the second + format is assumed if the last operand begins with + or + (if there are 2 operands) a digit. An OFFSET operand + means -j OFFSET. LABEL is the pseudo-address at first + byte printed, incremented when dump is progressing. For + OFFSET and LABEL, a 0x or 0X prefix indicates hexadeci- + mal; suffixes may be . for octal and b for multiply by + 512. + + TYPE is made up of one or more of these specifications: + + a named character + + c ASCII character or backslash escape + + d[SIZE] + signed decimal, SIZE bytes per integer + + f[SIZE] + floating point, SIZE bytes per integer + + o[SIZE] + octal, SIZE bytes per integer + + u[SIZE] + unsigned decimal, SIZE bytes per integer + + x[SIZE] + hexadecimal, SIZE bytes per integer + + SIZE is a number. For TYPE in doux, SIZE may also be C + for sizeof(char), S for sizeof(short), I for sizeof(int) + or L for sizeof(long). If TYPE is f, SIZE may also be F + for sizeof(float), D for sizeof(double) or L for + sizeof(long double). + + RADIX is d for decimal, o for octal, x for hexadecimal + or n for none. BYTES is hexadecimal with 0x or 0X pre- + fix, it is multiplied by 512 with b suffix, by 1024 with + k and by 1048576 with m. Adding a z suffix to any type + adds a display of printable characters to the end of + each line of output. --string without a number implies + 3. --width without a number implies 32. By default, od + uses -A o -t d2 -w 16. + +AUTHOR + Written by Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for od is maintained as a Texinfo + manual. If the info and od programs are properly + installed at your site, the command + + info od + + should give you access to the complete manual. + + + +od 5.3.0 November 2004 OD(1) diff --git a/coreutils-5.3.0-bin/man/cat1/paste.1.txt b/coreutils-5.3.0-bin/man/cat1/paste.1.txt new file mode 100644 index 0000000..deb8194 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/paste.1.txt @@ -0,0 +1,56 @@ +PASTE(1) User Commands PASTE(1) + + + + + +NAME + paste - merge lines of files + +SYNOPSIS + paste [OPTION]... [FILE]... + +DESCRIPTION + Write lines consisting of the sequentially corresponding + lines from each FILE, separated by TABs, to standard + output. With no FILE, or when FILE is -, read standard + input. + + Mandatory arguments to long options are mandatory for + short options too. + + -d, --delimiters=LIST + reuse characters from LIST instead of TABs + + -s, --serial + paste one file at a time instead of in parallel + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David M. Ihnat and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for paste is maintained as a Tex- + info manual. If the info and paste programs are prop- + erly installed at your site, the command + + info paste + + should give you access to the complete manual. + + + +paste 5.3.0 November 2004 PASTE(1) diff --git a/coreutils-5.3.0-bin/man/cat1/pathchk.1.txt b/coreutils-5.3.0-bin/man/cat1/pathchk.1.txt new file mode 100644 index 0000000..b023561 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/pathchk.1.txt @@ -0,0 +1,48 @@ +PATHCHK(1) User Commands PATHCHK(1) + + + + + +NAME + pathchk - check whether file names are valid or portable + +SYNOPSIS + pathchk [OPTION]... NAME... + +DESCRIPTION + Diagnose unportable constructs in NAME. + + -p, --portability + check for all POSIX systems, not only this one + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Paul Eggert, David MacKenzie, and Jim Meyer- + ing. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for pathchk is maintained as a + Texinfo manual. If the info and pathchk programs are + properly installed at your site, the command + + info pathchk + + should give you access to the complete manual. + + + +pathchk 5.3.0 November 2004 PATHCHK(1) diff --git a/coreutils-5.3.0-bin/man/cat1/pgawk.1.txt b/coreutils-5.3.0-bin/man/cat1/pgawk.1.txt new file mode 100644 index 0000000..a431e7b --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/pgawk.1.txt @@ -0,0 +1,1972 @@ +GAWK(1) Utility Commands GAWK(1) + + + +NAME + gawk - pattern scanning and processing language + +SYNOPSIS + gawk [ POSIX or GNU style options ] -f program-file [ -- + ] file ... + gawk [ POSIX or GNU style options ] [ -- ] program-text + file ... + + pgawk [ POSIX or GNU style options ] -f program-file [ + -- ] file ... + pgawk [ POSIX or GNU style options ] [ -- ] program-text + file ... + +DESCRIPTION + Gawk is the GNU Project's implementation of the AWK pro- + gramming language. It conforms to the definition of the + language in the POSIX 1003.1 Standard. This version in + turn is based on the description in The AWK Programming + Language, by Aho, Kernighan, and Weinberger, with the + additional features found in the System V Release 4 ver- + sion of UNIX awk. Gawk also provides more recent Bell + Laboratories awk extensions, and a number of GNU-spe- + cific extensions. + + Pgawk is the profiling version of gawk. It is identical + in every way to gawk, except that programs run more + slowly, and it automatically produces an execution pro- + file in the file awkprof.out when done. See the --pro- + file option, below. + + The command line consists of options to gawk itself, the + AWK program text (if not supplied via the -f or --file + options), and values to be made available in the ARGC + and ARGV pre-defined AWK variables. + +OPTION FORMAT + Gawk options may be either traditional POSIX one letter + options, or GNU-style long options. POSIX options start + with a single "-", while long options start with "--". + Long options are provided for both GNU-specific features + and for POSIX-mandated features. + + Following the POSIX standard, gawk-specific options are + supplied via arguments to the -W option. Multiple -W + options may be supplied Each -W option has a correspond- + ing long option, as detailed below. Arguments to long + options are either joined with the option by an = sign, + with no intervening spaces, or they may be provided in + the next command line argument. Long options may be + abbreviated, as long as the abbreviation remains unique. + +OPTIONS + Gawk accepts the following options, listed by frequency. + + -F fs + --field-separator fs + Use fs for the input field separator (the value + of the FS predefined variable). + + -v var=val + --assign var=val + Assign the value val to the variable var, before + execution of the program begins. Such variable + values are available to the BEGIN block of an AWK + program. + + -f program-file + --file program-file + Read the AWK program source from the file pro- + gram-file, instead of from the first command line + argument. Multiple -f (or --file) options may be + used. + + -mf NNN + -mr NNN + Set various memory limits to the value NNN. The + f flag sets the maximum number of fields, and the + r flag sets the maximum record size. These two + flags and the -m option are from an earlier ver- + sion of the Bell Laboratories research version of + UNIX awk. They are ignored by gawk, since gawk + has no pre-defined limits. + + -W compat + -W traditional + --compat + --traditional + Run in compatibility mode. In compatibility + mode, gawk behaves identically to UNIX awk; none + of the GNU-specific extensions are recognized. + The use of --traditional is preferred over the + other forms of this option. See GNU EXTENSIONS, + below, for more information. + + -W copyleft + -W copyright + --copyleft + --copyright + Print the short version of the GNU copyright + information message on the standard output and + exit successfully. + + -W dump-variables[=file] + --dump-variables[=file] + Print a sorted list of global variables, their + types and final values to file. If no file is + provided, gawk uses a file named awkvars.out in + the current directory. + Having a list of all the global variables is a + good way to look for typographical errors in your + programs. You would also use this option if you + have a large program with a lot of functions, and + you want to be sure that your functions don't + inadvertently use global variables that you meant + to be local. (This is a particularly easy mis- + take to make with simple variable names like i, + j, and so on.) + + -W exec file + --exec file + Similar to -f, however, this is option is the + last one processed. This should be used with #! + scripts, particularly for CGI applications, to + avoid passing in options or source code (!) on + the command line from a URL. This option dis- + ables command-line variable assignments. + + -W gen-po + --gen-po + Scan and parse the AWK program, and generate a + GNU .po format file on standard output with + entries for all localizable strings in the pro- + gram. The program itself is not executed. See + the GNU gettext distribution for more information + on .po files. + + -W help + -W usage + --help + --usage + Print a relatively short summary of the available + options on the standard output. (Per the GNU + Coding Standards, these options cause an immedi- + ate, successful exit.) + + -W lint[=value] + --lint[=value] + Provide warnings about constructs that are dubi- + ous or non-portable to other AWK implementations. + With an optional argument of fatal, lint warnings + become fatal errors. This may be drastic, but + its use will certainly encourage the development + of cleaner AWK programs. With an optional argu- + ment of invalid, only warnings about things that + are actually invalid are issued. (This is not + fully implemented yet.) + + -W lint-old + --lint-old + Provide warnings about constructs that are not + portable to the original version of Unix awk. + + -W non-decimal-data + --non-decimal-data + Recognize octal and hexadecimal values in input + data. Use this option with great caution! + + -W posix + --posix + This turns on compatibility mode, with the fol- + lowing additional restrictions: + + · \x escape sequences are not recognized. + + · Only space and tab act as field separators when + FS is set to a single space, newline does not. + + · You cannot continue lines after ? and :. + + · The synonym func for the keyword function is + not recognized. + + · The operators ** and **= cannot be used in + place of ^ and ^=. + + · The fflush() function is not available. + + -W profile[=prof_file] + --profile[=prof_file] + Send profiling data to prof_file. The default is + awkprof.out. When run with gawk, the profile is + just a "pretty printed" version of the program. + When run with pgawk, the profile contains execu- + tion counts of each statement in the program in + the left margin and function call counts for each + user-defined function. + + -W re-interval + --re-interval + Enable the use of interval expressions in regular + expression matching (see Regular Expressions, + below). Interval expressions were not tradition- + ally available in the AWK language. The POSIX + standard added them, to make awk and egrep con- + sistent with each other. However, their use is + likely to break old AWK programs, so gawk only + provides them if they are requested with this + option, or when --posix is specified. + + -W source program-text + --source program-text + Use program-text as AWK program source code. + This option allows the easy intermixing of + library functions (used via the -f and --file + options) with source code entered on the command + line. It is intended primarily for medium to + large AWK programs used in shell scripts. + + -W use-lc-numeric + --use-lc-numeric + This forces gawk to use the locale's decimal + point character when parsing input data. + Although the POSIX standard requires this behav- + ior, and gawk does so when --posix is in effect, + the default is to follow traditional behavior and + use a period as the decimal point, even in + locales where the period is not the decimal point + character. This option overrides the default + behavior, without the full draconian strictness + of the --posix option. + + -W version + --version + Print version information for this particular + copy of gawk on the standard output. This is + useful mainly for knowing if the current copy of + gawk on your system is up to date with respect to + whatever the Free Software Foundation is dis- + tributing. This is also useful when reporting + bugs. (Per the GNU Coding Standards, these + options cause an immediate, successful exit.) + + -- Signal the end of options. This is useful to + allow further arguments to the AWK program itself + to start with a "-". This provides consistency + with the argument parsing convention used by most + other POSIX programs. + In compatibility mode, any other options are flagged as + invalid, but are otherwise ignored. In normal opera- + tion, as long as program text has been supplied, unknown + options are passed on to the AWK program in the ARGV + array for processing. This is particularly useful for + running AWK programs via the "#!" executable interpreter + mechanism. +AWK PROGRAM EXECUTION + An AWK program consists of a sequence of pattern-action + statements and optional function definitions. + pattern { action statements } + function name(parameter list) { statements } + Gawk first reads the program source from the program- + file(s) if specified, from arguments to --source, or + from the first non-option argument on the command line. + The -f and --source options may be used multiple times + on the command line. Gawk reads the program text as if + all the program-files and command line source texts had + been concatenated together. This is useful for building + libraries of AWK functions, without having to include + them in each new AWK program that uses them. It also + provides the ability to mix library functions with com- + mand line programs. + The environment variable AWKPATH specifies a search path + to use when finding source files named with the -f + option. If this variable does not exist, the default + path is ".:/usr/local/share/awk". (The actual directory + may vary, depending upon how gawk was built and + installed.) If a file name given to the -f option con- + tains a "/" character, no path search is performed. + Gawk executes AWK programs in the following order. + First, all variable assignments specified via the -v + option are performed. Next, gawk compiles the program + into an internal form. Then, gawk executes the code in + the BEGIN block(s) (if any), and then proceeds to read + each file named in the ARGV array. If there are no + files named on the command line, gawk reads the standard + input. + If a filename on the command line has the form var=val + it is treated as a variable assignment. The variable + var will be assigned the value val. (This happens after + any BEGIN block(s) have been run.) Command line vari- + able assignment is most useful for dynamically assigning + values to the variables AWK uses to control how input is + broken into fields and records. It is also useful for + controlling state if multiple passes are needed over a + single data file. + If the value of a particular element of ARGV is empty + (""), gawk skips over it. + For each record in the input, gawk tests to see if it + matches any pattern in the AWK program. For each pat- + tern that the record matches, the associated action is + executed. The patterns are tested in the order they + occur in the program. + Finally, after all the input is exhausted, gawk executes + the code in the END block(s) (if any). +VARIABLES, RECORDS AND FIELDS + AWK variables are dynamic; they come into existence when + they are first used. Their values are either floating- + point numbers or strings, or both, depending upon how + they are used. AWK also has one dimensional arrays; + arrays with multiple dimensions may be simulated. Sev- + eral pre-defined variables are set as a program runs; + these are described as needed and summarized below. + Records + Normally, records are separated by newline characters. + You can control how records are separated by assigning + values to the built-in variable RS. If RS is any single + character, that character separates records. Otherwise, + RS is a regular expression. Text in the input that + matches this regular expression separates the record. + However, in compatibility mode, only the first character + of its string value is used for separating records. If + RS is set to the null string, then records are separated + by blank lines. When RS is set to the null string, the + newline character always acts as a field separator, in + addition to whatever value FS may have. + Fields + As each input record is read, gawk splits the record + into fields, using the value of the FS variable as the + field separator. If FS is a single character, fields + are separated by that character. If FS is the null + string, then each individual character becomes a sepa- + rate field. Otherwise, FS is expected to be a full reg- + ular expression. In the special case that FS is a sin- + gle space, fields are separated by runs of spaces and/or + tabs and/or newlines. (But see the section POSIX COM- + PATIBILITY, below). NOTE: The value of IGNORECASE (see + below) also affects how fields are split when FS is a + regular expression, and how records are separated when + RS is a regular expression. + If the FIELDWIDTHS variable is set to a space separated + list of numbers, each field is expected to have fixed + width, and gawk splits up the record using the specified + widths. The value of FS is ignored. Assigning a new + value to FS overrides the use of FIELDWIDTHS, and + restores the default behavior. + Each field in the input record may be referenced by its + position, $1, $2, and so on. $0 is the whole record. + Fields need not be referenced by constants: + n = 5 + print $n + prints the fifth field in the input record. + The variable NF is set to the total number of fields in + the input record. + References to non-existent fields (i.e. fields after + $NF) produce the null-string. However, assigning to a + non-existent field (e.g., $(NF+2) = 5) increases the + value of NF, creates any intervening fields with the + null string as their value, and causes the value of $0 + to be recomputed, with the fields being separated by the + value of OFS. References to negative numbered fields + cause a fatal error. Decrementing NF causes the values + of fields past the new value to be lost, and the value + of $0 to be recomputed, with the fields being separated + by the value of OFS. + Assigning a value to an existing field causes the whole + record to be rebuilt when $0 is referenced. Similarly, + assigning a value to $0 causes the record to be resplit, + creating new values for the fields. + Built-in Variables + Gawk's built-in variables are: + ARGC The number of command line arguments (does + not include options to gawk, or the program + source). + ARGIND The index in ARGV of the current file being + processed. + ARGV Array of command line arguments. The array + is indexed from 0 to ARGC - 1. Dynamically + changing the contents of ARGV can control + the files used for data. + BINMODE On non-POSIX systems, specifies use of + "binary" mode for all file I/O. Numeric + values of 1, 2, or 3, specify that input + files, output files, or all files, respec- + tively, should use binary I/O. String val- + ues of "r", or "w" specify that input files, + or output files, respectively, should use + binary I/O. String values of "rw" or "wr" + specify that all files should use binary + I/O. Any other string value is treated as + "rw", but generates a warning message. + CONVFMT The conversion format for numbers, "%.6g", + by default. + ENVIRON An array containing the values of the cur- + rent environment. The array is indexed by + the environment variables, each element + being the value of that variable (e.g., ENV- + IRON["HOME"] might be /home/arnold). Chang- + ing this array does not affect the environ- + ment seen by programs which gawk spawns via + redirection or the system() function. + ERRNO If a system error occurs either doing a + redirection for getline, during a read for + getline, or during a close(), then ERRNO + will contain a string describing the error. + The value is subject to translation in non- + English locales. + FIELDWIDTHS A white-space separated list of fieldwidths. + When set, gawk parses the input into fields + of fixed width, instead of using the value + of the FS variable as the field separator. + FILENAME The name of the current input file. If no + files are specified on the command line, the + value of FILENAME is "-". However, FILENAME + is undefined inside the BEGIN block (unless + set by getline). + FNR The input record number in the current input + file. + FS The input field separator, a space by + default. See Fields, above. + IGNORECASE Controls the case-sensitivity of all regular + expression and string operations. If + IGNORECASE has a non-zero value, then string + comparisons and pattern matching in rules, + field splitting with FS, record separating + with RS, regular expression matching with ~ + and !~, and the gensub(), gsub(), index(), + match(), split(), and sub() built-in func- + tions all ignore case when doing regular + expression operations. NOTE: Array sub- + scripting is not affected. However, the + asort() and asorti() functions are affected. + Thus, if IGNORECASE is not equal to zero, + /aB/ matches all of the strings "ab", "aB", + "Ab", and "AB". As with all AWK variables, + the initial value of IGNORECASE is zero, so + all regular expression and string operations + are normally case-sensitive. Under Unix, + the full ISO 8859-1 Latin-1 character set is + used when ignoring case. As of gawk 3.1.4, + the case equivalencies are fully locale- + aware, based on the C <ctype.h> facilities + such as isalpha(), and toupper(). + LINT Provides dynamic control of the --lint + option from within an AWK program. When + true, gawk prints lint warnings. When false, + it does not. When assigned the string value + "fatal", lint warnings become fatal errors, + exactly like --lint=fatal. Any other true + value just prints warnings. + NF The number of fields in the current input + record. + NR The total number of input records seen so + far. + OFMT The output format for numbers, "%.6g", by + default. + OFS The output field separator, a space by + default. + ORS The output record separator, by default a + newline. + PROCINFO The elements of this array provide access to + information about the running AWK program. + On some systems, there may be elements in + the array, "group1" through "groupn" for + some n, which is the number of supplementary + groups that the process has. Use the in + operator to test for these elements. The + following elements are guaranteed to be + available: + PROCINFO["egid"] the value of the gete- + gid(2) system call. + PROCINFO["euid"] the value of the + geteuid(2) system call. + PROCINFO["FS"] "FS" if field splitting + with FS is in effect, or + "FIELDWIDTHS" if field + splitting with FIELD- + WIDTHS is in effect. + PROCINFO["gid"] the value of the get- + gid(2) system call. + PROCINFO["pgrpid"] the process group ID of + the current process. + PROCINFO["pid"] the process ID of the + current process. + PROCINFO["ppid"] the parent process ID of + the current process. + PROCINFO["uid"] the value of the + getuid(2) system call. + PROCINFO["version"] + The version of gawk. + This is available from + version 3.1.4 and later. + RS The input record separator, by default a + newline. + RT The record terminator. Gawk sets RT to the + input text that matched the character or + regular expression specified by RS. + RSTART The index of the first character matched by + match(); 0 if no match. (This implies that + character indices start at one.) + RLENGTH The length of the string matched by match(); + -1 if no match. + SUBSEP The character used to separate multiple sub- + scripts in array elements, by default + "\034". + TEXTDOMAIN The text domain of the AWK program; used to + find the localized translations for the pro- + gram's strings. + Arrays + Arrays are subscripted with an expression between square + brackets ([ and ]). If the expression is an expression + list (expr, expr ...) then the array subscript is a + string consisting of the concatenation of the (string) + value of each expression, separated by the value of the + SUBSEP variable. This facility is used to simulate mul- + tiply dimensioned arrays. For example: + i = "A"; j = "B"; k = "C" + x[i, j, k] = "hello, world\n" + assigns the string "hello, world\n" to the element of + the array x which is indexed by the string + "A\034B\034C". All arrays in AWK are associative, i.e. + indexed by string values. + The special operator in may be used to test if an array + has an index consisting of a particular value. + if (val in array) + print array[val] + If the array has multiple subscripts, use (i, j) in + array. + The in construct may also be used in a for loop to iter- + ate over all the elements of an array. + An element may be deleted from an array using the delete + statement. The delete statement may also be used to + delete the entire contents of an array, just by specify- + ing the array name without a subscript. + Variable Typing And Conversion + Variables and fields may be (floating point) numbers, or + strings, or both. How the value of a variable is inter- + preted depends upon its context. If used in a numeric + expression, it will be treated as a number; if used as a + string it will be treated as a string. + To force a variable to be treated as a number, add 0 to + it; to force it to be treated as a string, concatenate + it with the null string. + When a string must be converted to a number, the conver- + sion is accomplished using strtod(3). A number is con- + verted to a string by using the value of CONVFMT as a + format string for sprintf(3), with the numeric value of + the variable as the argument. However, even though all + numbers in AWK are floating-point, integral values are + always converted as integers. Thus, given + CONVFMT = "%2.2f" + a = 12 + b = a "" + the variable b has a string value of "12" and not + "12.00". + When operating in POSIX mode (such as with the --posix + command line option), beware that locale settings may + interfere with the way decimal numbers are treated: the + decimal separator of the numbers you are feeding to gawk + must conform to what your locale would expect, be it a + comma (,) or a period (.). + Gawk performs comparisons as follows: If two variables + are numeric, they are compared numerically. If one + value is numeric and the other has a string value that + is a "numeric string," then comparisons are also done + numerically. Otherwise, the numeric value is converted + to a string and a string comparison is performed. Two + strings are compared, of course, as strings. + Note that string constants, such as "57", are not + numeric strings, they are string constants. The idea of + "numeric string" only applies to fields, getline input, + FILENAME, ARGV elements, ENVIRON elements and the ele- + ments of an array created by split() that are numeric + strings. The basic idea is that user input, and only + user input, that looks numeric, should be treated that + way. + Uninitialized variables have the numeric value 0 and the + string value "" (the null, or empty, string). + Octal and Hexadecimal Constants + Starting with version 3.1 of gawk , you may use C-style + octal and hexadecimal constants in your AWK program + source code. For example, the octal value 011 is equal + to decimal 9, and the hexadecimal value 0x11 is equal to + decimal 17. + String Constants + String constants in AWK are sequences of characters + enclosed between double quotes ("). Within strings, + certain escape sequences are recognized, as in C. These + are: + \\ A literal backslash. + \a The "alert" character; usually the ASCII BEL char- + acter. + \b backspace. + \f form-feed. + \n newline. + \r carriage return. + \t horizontal tab. + \v vertical tab. + \xhex digits + The character represented by the string of hexadec- + imal digits following the \x. As in ANSI C, all + following hexadecimal digits are considered part of + the escape sequence. (This feature should tell us + something about language design by committee.) + E.g., "\x1B" is the ASCII ESC (escape) character. + \ddd The character represented by the 1-, 2-, or 3-digit + sequence of octal digits. E.g., "\033" is the + ASCII ESC (escape) character. + \c The literal character c. + The escape sequences may also be used inside constant + regular expressions (e.g., /[ \t\f\n\r\v]/ matches + whitespace characters). + In compatibility mode, the characters represented by + octal and hexadecimal escape sequences are treated lit- + erally when used in regular expression constants. Thus, + /a\52b/ is equivalent to /a\*b/. +PATTERNS AND ACTIONS + AWK is a line-oriented language. The pattern comes + first, and then the action. Action statements are + enclosed in { and }. Either the pattern may be missing, + or the action may be missing, but, of course, not both. + If the pattern is missing, the action is executed for + every single record of input. A missing action is + equivalent to + { print } + which prints the entire record. + Comments begin with the "#" character, and continue + until the end of the line. Blank lines may be used to + separate statements. Normally, a statement ends with a + newline, however, this is not the case for lines ending + in a ",", {, ?, :, &&, or ||. Lines ending in do or + else also have their statements automatically continued + on the following line. In other cases, a line can be + continued by ending it with a "\", in which case the + newline will be ignored. + Multiple statements may be put on one line by separating + them with a ";". This applies to both the statements + within the action part of a pattern-action pair (the + usual case), and to the pattern-action statements them- + selves. + Patterns + AWK patterns may be one of the following: + BEGIN + END + /regular expression/ + relational expression + pattern && pattern + pattern || pattern + pattern ? pattern : pattern + (pattern) + ! pattern + pattern1, pattern2 + BEGIN and END are two special kinds of patterns which + are not tested against the input. The action parts of + all BEGIN patterns are merged as if all the statements + had been written in a single BEGIN block. They are exe- + cuted before any of the input is read. Similarly, all + the END blocks are merged, and executed when all the + input is exhausted (or when an exit statement is exe- + cuted). BEGIN and END patterns cannot be combined with + other patterns in pattern expressions. BEGIN and END + patterns cannot have missing action parts. + For /regular expression/ patterns, the associated state- + ment is executed for each input record that matches the + regular expression. Regular expressions are the same as + those in egrep(1), and are summarized below. + A relational expression may use any of the operators + defined below in the section on actions. These gener- + ally test whether certain fields match certain regular + expressions. + The &&, ||, and ! operators are logical AND, logical + OR, and logical NOT, respectively, as in C. They do + short-circuit evaluation, also as in C, and are used for + combining more primitive pattern expressions. As in + most languages, parentheses may be used to change the + order of evaluation. + The ?: operator is like the same operator in C. If the + first pattern is true then the pattern used for testing + is the second pattern, otherwise it is the third. Only + one of the second and third patterns is evaluated. + The pattern1, pattern2 form of an expression is called a + range pattern. It matches all input records starting + with a record that matches pattern1, and continuing + until a record that matches pattern2, inclusive. It + does not combine with any other sort of pattern expres- + sion. + Regular Expressions + Regular expressions are the extended kind found in + egrep. They are composed of characters as follows: + c matches the non-metacharacter c. + \c matches the literal character c. + . matches any character including newline. + ^ matches the beginning of a string. + $ matches the end of a string. + [abc...] character list, matches any of the characters + abc.... + [^abc...] negated character list, matches any character + except abc.... + r1|r2 alternation: matches either r1 or r2. + r1r2 concatenation: matches r1, and then r2. + r+ matches one or more r's. + r* matches zero or more r's. + r? matches zero or one r's. + (r) grouping: matches r. + r{n} + r{n,} + r{n,m} One or two numbers inside braces denote an + interval expression. If there is one number + in the braces, the preceding regular expres- + sion r is repeated n times. If there are two + numbers separated by a comma, r is repeated n + to m times. If there is one number followed + by a comma, then r is repeated at least n + times. + Interval expressions are only available if + either --posix or --re-interval is specified + on the command line. + + \y matches the empty string at either the begin- + ning or the end of a word. + + \B matches the empty string within a word. + + \< matches the empty string at the beginning of + a word. + + \> matches the empty string at the end of a + word. + + \w matches any word-constituent character (let- + ter, digit, or underscore). + + \W matches any character that is not word-con- + stituent. + + \` matches the empty string at the beginning of + a buffer (string). + + \' matches the empty string at the end of a + buffer. + + The escape sequences that are valid in string constants + (see below) are also valid in regular expressions. + + Character classes are a feature introduced in the POSIX + standard. A character class is a special notation for + describing lists of characters that have a specific + attribute, but where the actual characters themselves + can vary from country to country and/or from character + set to character set. For example, the notion of what + is an alphabetic character differs in the USA and in + France. + + A character class is only valid in a regular expression + inside the brackets of a character list. Character + classes consist of [:, a keyword denoting the class, and + :]. The character classes defined by the POSIX standard + are: + + [:alnum:] Alphanumeric characters. + + [:alpha:] Alphabetic characters. + + [:blank:] Space or tab characters. + + [:cntrl:] Control characters. + + [:digit:] Numeric characters. + + [:graph:] Characters that are both printable and visi- + ble. (A space is printable, but not visible, + while an a is both.) + + [:lower:] Lower-case alphabetic characters. + + [:print:] Printable characters (characters that are not + control characters.) + + [:punct:] Punctuation characters (characters that are + not letter, digits, control characters, or + space characters). + + [:space:] Space characters (such as space, tab, and + formfeed, to name a few). + + [:upper:] Upper-case alphabetic characters. + + [:xdigit:] Characters that are hexadecimal digits. + + For example, before the POSIX standard, to match + alphanumeric characters, you would have had to write + /[A-Za-z0-9]/. If your character set had other alpha- + betic characters in it, this would not match them, and + if your character set collated differently from ASCII, + this might not even match the ASCII alphanumeric charac- + ters. With the POSIX character classes, you can write + /[[:alnum:]]/, and this matches the alphabetic and + numeric characters in your character set, no matter what + it is. + + Two additional special sequences can appear in character + lists. These apply to non-ASCII character sets, which + can have single symbols (called collating elements) that + are represented with more than one character, as well as + several characters that are equivalent for collating, or + sorting, purposes. (E.g., in French, a plain "e" and a + grave-accented "`" are equivalent.) + + Collating Symbols + A collating symbol is a multi-character collating + element enclosed in [. and .]. For example, if + ch is a collating element, then [[.ch.]] is a + regular expression that matches this collating + element, while [ch] is a regular expression that + matches either c or h. + + Equivalence Classes + An equivalence class is a locale-specific name + for a list of characters that are equivalent. + The name is enclosed in [= and =]. For example, + the name e might be used to represent all of "e," + "´," and "`." In this case, [[=e=]] is a regular + expression that matches any of e, ´, or `. + + These features are very valuable in non-English speaking + locales. The library functions that gawk uses for regu- + lar expression matching currently only recognize POSIX + character classes; they do not recognize collating sym- + bols or equivalence classes. + + The \y, \B, \<, \>, \w, \W, \`, and \' operators are + specific to gawk; they are extensions based on facili- + ties in the GNU regular expression libraries. + + The various command line options control how gawk inter- + prets characters in regular expressions. + + No options + In the default case, gawk provide all the facili- + ties of POSIX regular expressions and the GNU + regular expression operators described above. + However, interval expressions are not supported. + + --posix + Only POSIX regular expressions are supported, the + GNU operators are not special. (E.g., \w matches + a literal w). Interval expressions are allowed. + + --traditional + Traditional Unix awk regular expressions are + matched. The GNU operators are not special, + interval expressions are not available, and nei- + ther are the POSIX character classes ([[:alnum:]] + and so on). Characters described by octal and + hexadecimal escape sequences are treated liter- + ally, even if they represent regular expression + metacharacters. + + --re-interval + Allow interval expressions in regular expres- + sions, even if --traditional has been provided. + + Actions + Action statements are enclosed in braces, { and }. + Action statements consist of the usual assignment, con- + ditional, and looping statements found in most lan- + guages. The operators, control statements, and + input/output statements available are patterned after + those in C. + + Operators + The operators in AWK, in order of decreasing precedence, + are + + + (...) Grouping + + $ Field reference. + + ++ -- Increment and decrement, both prefix and + postfix. + + ^ Exponentiation (** may also be used, and **= + for the assignment operator). + + + - ! Unary plus, unary minus, and logical nega- + tion. + + * / % Multiplication, division, and modulus. + + + - Addition and subtraction. + + space String concatenation. + + | |& Piped I/O for getline, print, and printf. + + < > + <= >= + != == The regular relational operators. + + ~ !~ Regular expression match, negated match. + NOTE: Do not use a constant regular expres- + sion (/foo/) on the left-hand side of a ~ or + !~. Only use one on the right-hand side. + The expression /foo/ ~ exp has the same + meaning as (($0 ~ /foo/) ~ exp). This is + usually not what was intended. + + in Array membership. + + && Logical AND. + + || Logical OR. + + ?: The C conditional expression. This has the + form expr1 ? expr2 : expr3. If expr1 is + true, the value of the expression is expr2, + otherwise it is expr3. Only one of expr2 + and expr3 is evaluated. + + = += -= + *= /= %= ^= Assignment. Both absolute assignment (var = + value) and operator-assignment (the other + forms) are supported. + + Control Statements + The control statements are as follows: + + if (condition) statement [ else statement ] + while (condition) statement + do statement while (condition) + for (expr1; expr2; expr3) statement + for (var in array) statement + break + continue + delete array[index] + delete array + exit [ expression ] + { statements } + + I/O Statements + The input/output statements are as follows: + + + close(file [, how]) Close file, pipe or co-process. + The optional how should only be + used when closing one end of a + two-way pipe to a co-process. It + must be a string value, either + "to" or "from". + + getline Set $0 from next input record; set + NF, NR, FNR. + + getline <file Set $0 from next record of file; + set NF. + + getline var Set var from next input record; + set NR, FNR. + + getline var <file Set var from next record of file. + + command | getline [var] + Run command piping the output + either into $0 or var, as above. + + command |& getline [var] + Run command as a co-process piping + the output either into $0 or var, + as above. Co-processes are a gawk + extension. (command can also be a + socket. See the subsection Spe- + cial File Names, below.) + + next Stop processing the current input + record. The next input record is + read and processing starts over + with the first pattern in the AWK + program. If the end of the input + data is reached, the END block(s), + if any, are executed. + + nextfile Stop processing the current input + file. The next input record read + comes from the next input file. + FILENAME and ARGIND are updated, + FNR is reset to 1, and processing + starts over with the first pattern + in the AWK program. If the end of + the input data is reached, the END + block(s), if any, are executed. + + print Prints the current record. The + output record is terminated with + the value of the ORS variable. + + print expr-list Prints expressions. Each expres- + sion is separated by the value of + the OFS variable. The output + record is terminated with the + value of the ORS variable. + + print expr-list >file Prints expressions on file. Each + expression is separated by the + value of the OFS variable. The + output record is terminated with + the value of the ORS variable. + + printf fmt, expr-list Format and print. + + printf fmt, expr-list >file + Format and print on file. + + system(cmd-line) Execute the command cmd-line, and + return the exit status. (This may + not be available on non-POSIX sys- + tems.) + + fflush([file]) Flush any buffers associated with + the open output file or pipe file. + If file is missing, then standard + output is flushed. If file is the + null string, then all open output + files and pipes have their buffers + flushed. + + Additional output redirections are allowed for print and + printf. + + print ... >> file + Appends output to the file. + + print ... | command + Writes on a pipe. + + print ... |& command + Sends data to a co-process or socket. (See also + the subsection Special File Names, below.) + + The getline command returns 0 on end of file and -1 on + an error. Upon an error, ERRNO contains a string + describing the problem. + + NOTE: If using a pipe, co-process, or socket to getline, + or from print or printf within a loop, you must use + close() to create new instances of the command or + socket. AWK does not automatically close pipes, sock- + ets, or co-processes when they return EOF. + + The printf Statement + The AWK versions of the printf statement and sprintf() + function (see below) accept the following conversion + specification formats: + + %c An ASCII character. If the argument used for %c + is numeric, it is treated as a character and + printed. Otherwise, the argument is assumed to + be a string, and the only first character of + that string is printed. + + %d, %i A decimal number (the integer part). + + %e, %E A floating point number of the form + [-]d.dddddde[+-]dd. The %E format uses E + instead of e. + + %f, %F A floating point number of the form + [-]ddd.dddddd. If the system library supports + it, %F is available as well. This is like %f, + but uses capital letters for special "not a num- + ber" and "infinity" values. If %F is not avail- + able, gawk uses %f. + + %g, %G Use %e or %f conversion, whichever is shorter, + with nonsignificant zeros suppressed. The %G + format uses %E instead of %e. + + %o An unsigned octal number (also an integer). + + %u An unsigned decimal number (again, an integer). + + %s A character string. + + %x, %X An unsigned hexadecimal number (an integer). + The %X format uses ABCDEF instead of abcdef. + + %% A single % character; no argument is converted. + + NOTE: When using the integer format-control letters for + values that are outside the range of a C long integer, + gawk switches to the %0f format specifier. If --lint is + provided on the command line gawk warns about this. + Other versions of awk may print invalid values or do + something else entirely. + + Optional, additional parameters may lie between the % + and the control letter: + + count$ Use the count'th argument at this point in the + formatting. This is called a positional speci- + fier and is intended primarily for use in trans- + lated versions of format strings, not in the + original text of an AWK program. It is a gawk + extension. + + - The expression should be left-justified within + its field. + + space For numeric conversions, prefix positive values + with a space, and negative values with a minus + sign. + + + The plus sign, used before the width modifier + (see below), says to always supply a sign for + numeric conversions, even if the data to be for- + matted is positive. The + overrides the space + modifier. + + # Use an "alternate form" for certain control let- + ters. For %o, supply a leading zero. For %x, + and %X, supply a leading 0x or 0X for a nonzero + result. For %e, %E, %f and %F, the result always + contains a decimal point. For %g, and %G, trail- + ing zeros are not removed from the result. + + 0 A leading 0 (zero) acts as a flag, that indicates + output should be padded with zeroes instead of + spaces. This applies even to non-numeric output + formats. This flag only has an effect when the + field width is wider than the value to be + printed. + + width The field should be padded to this width. The + field is normally padded with spaces. If the 0 + flag has been used, it is padded with zeroes. + + .prec A number that specifies the precision to use when + printing. For the %e, %E, %f and %F, formats, + this specifies the number of digits you want + printed to the right of the decimal point. For + the %g, and %G formats, it specifies the maximum + number of significant digits. For the %d, %o, + %i, %u, %x, and %X formats, it specifies the min- + imum number of digits to print. For %s, it spec- + ifies the maximum number of characters from the + string that should be printed. + + The dynamic width and prec capabilities of the ANSI C + printf() routines are supported. A * in place of either + the width or prec specifications causes their values to + be taken from the argument list to printf or sprintf(). + To use a positional specifier with a dynamic width or + precision, supply the count$ after the * in the format + string. For example, "%3$*2$.*1$s". + + Special File Names + When doing I/O redirection from either print or printf + into a file, or via getline from a file, gawk recognizes + certain special filenames internally. These filenames + allow access to open file descriptors inherited from + gawk's parent process (usually the shell). These file + names may also be used on the command line to name data + files. The filenames are: + + /dev/stdin The standard input. + + /dev/stdout The standard output. + + /dev/stderr The standard error output. + + /dev/fd/n The file associated with the open file + descriptor n. + + These are particularly useful for error messages. For + example: + + print "You blew it!" > "/dev/stderr" + + whereas you would otherwise have to use + + print "You blew it!" | "cat 1>&2" + + The following special filenames may be used with the |& + co-process operator for creating TCP/IP network connec- + tions. + + /inet/tcp/lport/rhost/rport File for TCP/IP connection + on local port lport to + remote host rhost on remote + port rport. Use a port of + 0 to have the system pick a + port. + + /inet/udp/lport/rhost/rport Similar, but use UDP/IP + instead of TCP/IP. + + /inet/raw/lport/rhost/rport Reserved for future use. + + Other special filenames provide access to information + about the running gawk process. These filenames are now + obsolete. Use the PROCINFO array to obtain the informa- + tion they provide. The filenames are: + + /dev/pid Reading this file returns the process ID of + the current process, in decimal, terminated + with a newline. + + /dev/ppid Reading this file returns the parent process + ID of the current process, in decimal, ter- + minated with a newline. + + /dev/pgrpid Reading this file returns the process group + ID of the current process, in decimal, ter- + minated with a newline. + + /dev/user Reading this file returns a single record + terminated with a newline. The fields are + separated with spaces. $1 is the value of + the getuid(2) system call, $2 is the value + of the geteuid(2) system call, $3 is the + value of the getgid(2) system call, and $4 + is the value of the getegid(2) system call. + If there are any additional fields, they are + the group IDs returned by getgroups(2). + Multiple groups may not be supported on all + systems. + + Numeric Functions + AWK has the following built-in arithmetic functions: + + + atan2(y, x) Returns the arctangent of y/x in radians. + + cos(expr) Returns the cosine of expr, which is in + radians. + + exp(expr) The exponential function. + + int(expr) Truncates to integer. + + log(expr) The natural logarithm function. + + rand() Returns a random number N, between 0 and + 1, such that 0 <= N < 1. + + sin(expr) Returns the sine of expr, which is in + radians. + + sqrt(expr) The square root function. + + srand([expr]) Uses expr as a new seed for the random + number generator. If no expr is provided, + the time of day is used. The return value + is the previous seed for the random number + generator. + + String Functions + Gawk has the following built-in string functions: + + + asort(s [, d]) Returns the number of elements + in the source array s. The con- + tents of s are sorted using + gawk's normal rules for compar- + ing values, and the indices of + the sorted values of s are + replaced with sequential inte- + gers starting with 1. If the + optional destination array d is + specified, then s is first + duplicated into d, and then d is + sorted, leaving the indices of + the source array s unchanged. + + asorti(s [, d]) Returns the number of elements + in the source array s. The + behavior is the same as that of + asort(), except that the array + indices are used for sorting, + not the array values. When + done, the array is indexed + numerically, and the values are + those of the original indices. + The original values are lost; + thus provide a second array if + you wish to preserve the origi- + nal. + + gensub(r, s, h [, t]) Search the target string t for + matches of the regular expres- + sion r. If h is a string begin- + ning with g or G, then replace + all matches of r with s. Other- + wise, h is a number indicating + which match of r to replace. If + t is not supplied, $0 is used + instead. Within the replacement + text s, the sequence \n, where n + is a digit from 1 to 9, may be + used to indicate just the text + that matched the n'th parenthe- + sized subexpression. The + sequence \0 represents the + entire matched text, as does the + character &. Unlike sub() and + gsub(), the modified string is + returned as the result of the + function, and the original tar- + get string is not changed. + + gsub(r, s [, t]) For each substring matching the + regular expression r in the + string t, substitute the string + s, and return the number of sub- + stitutions. If t is not sup- + plied, use $0. An & in the + replacement text is replaced + with the text that was actually + matched. Use \& to get a lit- + eral &. (This must be typed as + "\\&"; see GAWK: Effective AWK + Programming for a fuller discus- + sion of the rules for &'s and + backslashes in the replacement + text of sub(), gsub(), and gen- + sub().) + + index(s, t) Returns the index of the string + t in the string s, or 0 if t is + not present. (This implies that + character indices start at one.) + + length([s]) Returns the length of the string + s, or the length of $0 if s is + not supplied. Starting with + version 3.1.5, as a non-standard + extension, with an array argu- + ment, length() returns the num- + ber of elements in the array. + + match(s, r [, a]) Returns the position in s where + the regular expression r occurs, + or 0 if r is not present, and + sets the values of RSTART and + RLENGTH. Note that the argument + order is the same as for the ~ + operator: str ~ re. If array a + is provided, a is cleared and + then elements 1 through n are + filled with the portions of s + that match the corresponding + parenthesized subexpression in + r. The 0'th element of a con- + tains the portion of s matched + by the entire regular expression + r. Subscripts a[n, "start"], + and a[n, "length"] provide the + starting index in the string and + length respectively, of each + matching substring. + + split(s, a [, r]) Splits the string s into the + array a on the regular expres- + sion r, and returns the number + of fields. If r is omitted, FS + is used instead. The array a is + cleared first. Splitting + behaves identically to field + splitting, described above. + + sprintf(fmt, expr-list) Prints expr-list according to + fmt, and returns the resulting + string. + + strtonum(str) Examines str, and returns its + numeric value. If str begins + with a leading 0, strtonum() + assumes that str is an octal + number. If str begins with a + leading 0x or 0X, strtonum() + assumes that str is a hexadeci- + mal number. + + sub(r, s [, t]) Just like gsub(), but only the + first matching substring is + replaced. + + substr(s, i [, n]) Returns the at most n-character + substring of s starting at i. + If n is omitted, the rest of s + is used. + + tolower(str) Returns a copy of the string + str, with all the upper-case + characters in str translated to + their corresponding lower-case + counterparts. Non-alphabetic + characters are left unchanged. + + toupper(str) Returns a copy of the string + str, with all the lower-case + characters in str translated to + their corresponding upper-case + counterparts. Non-alphabetic + characters are left unchanged. + + As of version 3.1.5, gawk is multibyte aware. This + means that index(), length(), substr() and match() all + work in terms of characters, not bytes. + + Time Functions + Since one of the primary uses of AWK programs is pro- + cessing log files that contain time stamp information, + gawk provides the following functions for obtaining time + stamps and formatting them. + + + mktime(datespec) + Turns datespec into a time stamp of the same + form as returned by systime(). The datespec + is a string of the form YYYY MM DD HH MM SS[ + DST]. The contents of the string are six or + seven numbers representing respectively the + full year including century, the month from 1 + to 12, the day of the month from 1 to 31, the + hour of the day from 0 to 23, the minute from + 0 to 59, and the second from 0 to 60, and an + optional daylight saving flag. The values of + these numbers need not be within the ranges + specified; for example, an hour of -1 means 1 + hour before midnight. The origin-zero Grego- + rian calendar is assumed, with year 0 preced- + ing year 1 and year -1 preceding year 0. The + time is assumed to be in the local timezone. + If the daylight saving flag is positive, the + time is assumed to be daylight saving time; if + zero, the time is assumed to be standard time; + and if negative (the default), mktime() + attempts to determine whether daylight saving + time is in effect for the specified time. If + datespec does not contain enough elements or + if the resulting time is out of range, + mktime() returns -1. + + strftime([format [, timestamp[, utc-flag]]]) + Formats timestamp according to the specifica- + tion in format. If utc-flag is present and is + non-zero or non-null, the result is in UTC, + otherwise the result is in local time. The + timestamp should be of the same form as + returned by systime(). If timestamp is miss- + ing, the current time of day is used. If for- + mat is missing, a default format equivalent to + the output of date(1) is used. See the speci- + fication for the strftime() function in ANSI C + for the format conversions that are guaranteed + to be available. + + systime() Returns the current time of day as the number + of seconds since the Epoch (1970-01-01 + 00:00:00 UTC on POSIX systems). + + Bit Manipulations Functions + Starting with version 3.1 of gawk, the following bit + manipulation functions are available. They work by con- + verting double-precision floating point values to + uintmax_t integers, doing the operation, and then con- + verting the result back to floating point. The func- + tions are: + + and(v1, v2) Return the bitwise AND of the values + provided by v1 and v2. + + compl(val) Return the bitwise complement of + val. + + lshift(val, count) Return the value of val, shifted + left by count bits. + + or(v1, v2) Return the bitwise OR of the values + provided by v1 and v2. + + rshift(val, count) Return the value of val, shifted + right by count bits. + + xor(v1, v2) Return the bitwise XOR of the values + provided by v1 and v2. + + + Internationalization Functions + Starting with version 3.1 of gawk, the following func- + tions may be used from within your AWK program for + translating strings at run-time. For full details, see + GAWK: Effective AWK Programming. + + bindtextdomain(directory [, domain]) + Specifies the directory where gawk looks for the + .mo files, in case they will not or cannot be + placed in the ``standard'' locations (e.g., dur- + ing testing). It returns the directory where + domain is ``bound.'' + The default domain is the value of TEXTDOMAIN. + If directory is the null string (""), then bind- + textdomain() returns the current binding for the + given domain. + + dcgettext(string [, domain [, category]]) + Returns the translation of string in text domain + domain for locale category category. The default + value for domain is the current value of TEXTDO- + MAIN. The default value for category is "LC_MES- + SAGES". + If you supply a value for category, it must be a + string equal to one of the known locale cate- + gories described in GAWK: Effective AWK Program- + ming. You must also supply a text domain. Use + TEXTDOMAIN if you want to use the current domain. + + dcngettext(string1 , string2 , number [, domain [, cate- + gory]]) + Returns the plural form used for number of the + translation of string1 and string2 in text domain + domain for locale category category. The default + value for domain is the current value of TEXTDO- + MAIN. The default value for category is "LC_MES- + SAGES". + If you supply a value for category, it must be a + string equal to one of the known locale cate- + gories described in GAWK: Effective AWK Program- + ming. You must also supply a text domain. Use + TEXTDOMAIN if you want to use the current domain. + +USER-DEFINED FUNCTIONS + Functions in AWK are defined as follows: + + function name(parameter list) { statements } + + Functions are executed when they are called from within + expressions in either patterns or actions. Actual + parameters supplied in the function call are used to + instantiate the formal parameters declared in the func- + tion. Arrays are passed by reference, other variables + are passed by value. + + Since functions were not originally part of the AWK lan- + guage, the provision for local variables is rather + clumsy: They are declared as extra parameters in the + parameter list. The convention is to separate local + variables from real parameters by extra spaces in the + parameter list. For example: + + function f(p, q, a, b) # a and b are local + { + ... + } + + /abc/ { ... ; f(1, 2) ; ... } + + The left parenthesis in a function call is required to + immediately follow the function name, without any inter- + vening white space. This avoids a syntactic ambiguity + with the concatenation operator. This restriction does + not apply to the built-in functions listed above. + + Functions may call each other and may be recursive. + Function parameters used as local variables are initial- + ized to the null string and the number zero upon func- + tion invocation. + + Use return expr to return a value from a function. The + return value is undefined if no value is provided, or if + the function returns by "falling off" the end. + + If --lint has been provided, gawk warns about calls to + undefined functions at parse time, instead of at run + time. Calling an undefined function at run time is a + fatal error. + + The word func may be used in place of function. + +DYNAMICALLY LOADING NEW FUNCTIONS + Beginning with version 3.1 of gawk, you can dynamically + add new built-in functions to the running gawk inter- + preter. The full details are beyond the scope of this + manual page; see GAWK: Effective AWK Programming for the + details. + + + extension(object, function) + Dynamically link the shared object file named by + object, and invoke function in that object, to + perform initialization. These should both be + provided as strings. Returns the value returned + by function. + + This function is provided and documented in GAWK: Effec- + tive AWK Programming, but everything about this feature + is likely to change eventually. We STRONGLY recommend + that you do not use this feature for anything that you + aren't willing to redo. + +SIGNALS + pgawk accepts two signals. SIGUSR1 causes it to dump a + profile and function call stack to the profile file, + which is either awkprof.out, or whatever file was named + with the --profile option. It then continues to run. + SIGHUP causes pgawk to dump the profile and function + call stack and then exit. + +EXAMPLES + Print and sort the login names of all users: + + BEGIN { FS = ":" } + { print $1 | "sort" } + + Count lines in a file: + + { nlines++ } + END { print nlines } + + Precede each line by its number in the file: + + { print FNR, $0 } + + Concatenate and line number (a variation on a theme): + + { print NR, $0 } + Run an external command for particular lines of data: + + tail -f access_log | + awk '/myhome.html/ { system("nmap " $1 ">> logdir/myhome.html") }' + +INTERNATIONALIZATION + String constants are sequences of characters enclosed in + double quotes. In non-English speaking environments, it + is possible to mark strings in the AWK program as + requiring translation to the native natural language. + Such strings are marked in the AWK program with a lead- + ing underscore ("_"). For example, + + gawk 'BEGIN { print "hello, world" }' + + always prints hello, world. But, + + gawk 'BEGIN { print _"hello, world" }' + + might print bonjour, monde in France. + + There are several steps involved in producing and run- + ning a localizable AWK program. + + 1. Add a BEGIN action to assign a value to the TEXTDO- + MAIN variable to set the text domain to a name asso- + ciated with your program. + + BEGIN { TEXTDOMAIN = "myprog" } + + This allows gawk to find the .mo file associated with + your program. Without this step, gawk uses the messages + text domain, which likely does not contain translations + for your program. + + 2. Mark all strings that should be translated with + leading underscores. + + 3. If necessary, use the dcgettext() and/or bindtextdo- + main() functions in your program, as appropriate. + + 4. Run gawk --gen-po -f myprog.awk > myprog.po to gen- + erate a .po file for your program. + + 5. Provide appropriate translations, and build and + install the corresponding .mo files. + + The internationalization features are described in full + detail in GAWK: Effective AWK Programming. + +POSIX COMPATIBILITY + A primary goal for gawk is compatibility with the POSIX + standard, as well as with the latest version of UNIX + awk. To this end, gawk incorporates the following user + visible features which are not described in the AWK + book, but are part of the Bell Laboratories version of + awk, and are in the POSIX standard. + + The book indicates that command line variable assignment + happens when awk would otherwise open the argument as a + file, which is after the BEGIN block is executed. How- + ever, in earlier implementations, when such an assign- + ment appeared before any file names, the assignment + would happen before the BEGIN block was run. Applica- + tions came to depend on this "feature." When awk was + changed to match its documentation, the -v option for + assigning variables before program execution was added + to accommodate applications that depended upon the old + behavior. (This feature was agreed upon by both the + Bell Laboratories and the GNU developers.) + + The -W option for implementation specific features is + from the POSIX standard. + + When processing arguments, gawk uses the special option + "--" to signal the end of arguments. In compatibility + mode, it warns about but otherwise ignores undefined + options. In normal operation, such arguments are passed + on to the AWK program for it to process. + + The AWK book does not define the return value of + srand(). The POSIX standard has it return the seed it + was using, to allow keeping track of random number + sequences. Therefore srand() in gawk also returns its + current seed. + + Other new features are: The use of multiple -f options + (from MKS awk); the ENVIRON array; the \a, and \v escape + sequences (done originally in gawk and fed back into the + Bell Laboratories version); the tolower() and toupper() + built-in functions (from the Bell Laboratories version); + and the ANSI C conversion specifications in printf (done + first in the Bell Laboratories version). + +HISTORICAL FEATURES + There are two features of historical AWK implementations + that gawk supports. First, it is possible to call the + length() built-in function not only with no argument, + but even without parentheses! Thus, + + a = length # Holy Algol 60, Batman! + + is the same as either of + + a = length() + a = length($0) + + This feature is marked as "deprecated" in the POSIX + standard, and gawk issues a warning about its use if + --lint is specified on the command line. + + The other feature is the use of either the continue or + the break statements outside the body of a while, for, + or do loop. Traditional AWK implementations have + treated such usage as equivalent to the next statement. + Gawk supports this usage if --traditional has been spec- + ified. + +GNU EXTENSIONS + Gawk has a number of extensions to POSIX awk. They are + described in this section. All the extensions described + here can be disabled by invoking gawk with the --tradi- + tional or --posix options. + + The following features of gawk are not available in + POSIX awk. + + · No path search is performed for files named via the -f + option. Therefore the AWKPATH environment variable is + not special. + + · The \x escape sequence. (Disabled with --posix.) + + · The fflush() function. (Disabled with --posix.) + + · The ability to continue lines after ? and :. (Dis- + abled with --posix.) + + · Octal and hexadecimal constants in AWK programs. + + · The ARGIND, BINMODE, ERRNO, LINT, RT and TEXTDOMAIN + variables are not special. + + · The IGNORECASE variable and its side-effects are not + available. + + · The FIELDWIDTHS variable and fixed-width field split- + ting. + + · The PROCINFO array is not available. + + · The use of RS as a regular expression. + + · The special file names available for I/O redirection + are not recognized. + + · The |& operator for creating co-processes. + + · The ability to split out individual characters using + the null string as the value of FS, and as the third + argument to split(). + + · The optional second argument to the close() function. + + · The optional third argument to the match() function. + + · The ability to use positional specifiers with printf + and sprintf(). + + · The ability to pass an array to length(). + + · The use of delete array to delete the entire contents + of an array. + + · The use of nextfile to abandon processing of the cur- + rent input file. + + · The and(), asort(), asorti(), bindtextdomain(), + compl(), dcgettext(), dcngettext(), gensub(), + lshift(), mktime(), or(), rshift(), strftime(), str- + tonum(), systime() and xor() functions. + + · Localizable strings. + + · Adding new built-in functions dynamically with the + extension() function. + + The AWK book does not define the return value of the + close() function. Gawk's close() returns the value from + fclose(3), or pclose(3), when closing an output file or + pipe, respectively. It returns the process's exit sta- + tus when closing an input pipe. The return value is -1 + if the named file, pipe or co-process was not opened + with a redirection. + + When gawk is invoked with the --traditional option, if + the fs argument to the -F option is "t", then FS is set + to the tab character. Note that typing gawk -F\t ... + simply causes the shell to quote the "t," and does not + pass "\t" to the -F option. Since this is a rather ugly + special case, it is not the default behavior. This + behavior also does not occur if --posix has been speci- + fied. To really get a tab character as the field sepa- + rator, it is best to use single quotes: gawk -F'\t' .... + + If gawk is configured with the --enable-switch option to + the configure command, then it accepts an additional + control-flow statement: + switch (expression) { + case value|regex : statement + ... + [ default: statement ] + } + + If gawk is configured with the --disable-directories- + fatal option, then it will silently skip directories + named on the command line. Otherwise, it will do so + only if invoked with the --traditional option. + +ENVIRONMENT VARIABLES + The AWKPATH environment variable can be used to provide + a list of directories that gawk searches when looking + for files named via the -f and --file options. + + If POSIXLY_CORRECT exists in the environment, then gawk + behaves exactly as if --posix had been specified on the + command line. If --lint has been specified, gawk issues + a warning message to this effect. + +SEE ALSO + egrep(1), getpid(2), getppid(2), getpgrp(2), getuid(2), + geteuid(2), getgid(2), getegid(2), getgroups(2) + + The AWK Programming Language, Alfred V. Aho, Brian W. + Kernighan, Peter J. Weinberger, Addison-Wesley, 1988. + ISBN 0-201-07981-X. + + GAWK: Effective AWK Programming, Edition 3.0, published + by the Free Software Foundation, 2001. The current ver- + sion of this document is available online at + http://www.gnu.org/software/gawk/manual. + +BUGS + The -F option is not necessary given the command line + variable assignment feature; it remains only for back- + wards compatibility. + + Syntactically invalid single character programs tend to + overflow the parse stack, generating a rather unhelpful + message. Such programs are surprisingly difficult to + diagnose in the completely general case, and the effort + to do so really is not worth it. + +AUTHORS + The original version of UNIX awk was designed and imple- + mented by Alfred Aho, Peter Weinberger, and Brian + Kernighan of Bell Laboratories. Brian Kernighan contin- + ues to maintain and enhance it. + + Paul Rubin and Jay Fenlason, of the Free Software Foun- + dation, wrote gawk, to be compatible with the original + version of awk distributed in Seventh Edition UNIX. + John Woods contributed a number of bug fixes. David + Trueman, with contributions from Arnold Robbins, made + gawk compatible with the new version of UNIX awk. + Arnold Robbins is the current maintainer. + + The initial DOS port was done by Conrad Kwok and Scott + Garfinkle. Scott Deifik is the current DOS maintainer. + Pat Rankin did the port to VMS, and Michal Jaegermann + did the port to the Atari ST. The port to OS/2 was done + by Kai Uwe Rommel, with contributions and help from Dar- + rel Hankerson. Juan M. Guerrero now maintains the OS/2 + port. Fred Fish supplied support for the Amiga, and + Martin Brown provided the BeOS port. Stephen Davies + provided the original Tandem port, and Matthew Woehlke + provided changes for Tandem's POSIX-compliant systems. + +VERSION INFORMATION + This man page documents gawk, version 3.1.6. + +BUG REPORTS + If you find a bug in gawk, please send electronic mail + to bug-gawk@gnu.org. Please include your operating sys- + tem and its revision, the version of gawk (from gawk + --version), what C compiler you used to compile it, and + a test program and data that are as small as possible + for reproducing the problem. + + Before sending a bug report, please do the following + things. First, verify that you have the latest version + of gawk. Many bugs (usually subtle ones) are fixed at + each release, and if yours is out of date, the problem + may already have been solved. Second, please see if + setting the environment variable LC_ALL to LC_ALL=C + causes things to behave as you expect. If so, it's a + locale issue, and may or may not really be a bug. + Finally, please read this man page and the reference + manual carefully to be sure that what you think is a bug + really is, instead of just a quirk in the language. + + Whatever you do, do NOT post a bug report in + comp.lang.awk. While the gawk developers occasionally + read this newsgroup, posting bug reports there is an + unreliable way to report bugs. Instead, please use the + electronic mail addresses given above. + + If you're using a GNU/Linux system or BSD-based system, + you may wish to submit a bug report to the vendor of + your distribution. That's fine, but please send a copy + to the official email address as well, since there's no + guarantee that the bug will be forwarded to the gawk + maintainer. + +ACKNOWLEDGEMENTS + Brian Kernighan of Bell Laboratories provided valuable + assistance during testing and debugging. We thank him. + +COPYING PERMISSIONS + Copyright © 1989, 1991, 1992, 1993, 1994, 1995, 1996, + 1997, 1998, 1999, 2001, 2002, 2003, 2004, 2005, 2007 + Free Software Foundation, Inc. + + Permission is granted to make and distribute verbatim + copies of this manual page provided the copyright notice + and this permission notice are preserved on all copies. + + Permission is granted to copy and distribute modified + versions of this manual page under the conditions for + verbatim copying, provided that the entire resulting + derived work is distributed under the terms of a permis- + sion notice identical to this one. + + Permission is granted to copy and distribute transla- + tions of this manual page into another language, under + the above conditions for modified versions, except that + this permission notice may be stated in a translation + approved by the Foundation. + + + +Free Software Foundation Oct 19 2007 GAWK(1) diff --git a/coreutils-5.3.0-bin/man/cat1/pinky.1.txt b/coreutils-5.3.0-bin/man/cat1/pinky.1.txt new file mode 100644 index 0000000..637be84 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/pinky.1.txt @@ -0,0 +1,68 @@ +PINKY(1) User Commands PINKY(1) + + + + + +NAME + pinky - lightweight finger + +SYNOPSIS + pinky [OPTION]... [USER]... + +DESCRIPTION + -l produce long format output for the specified + USERs + + -b omit the user's home directory and shell in long + format + + -h omit the user's project file in long format + + -p omit the user's plan file in long format + + -s do short format output, this is the default + + -f omit the line of column headings in short format + + -w omit the user's full name in short format + + -i omit the user's full name and remote host in + short format + + -q omit the user's full name, remote host and idle + time in short format + + --help display this help and exit + + --version + output version information and exit + + A lightweight `finger' program; print user information. + The utmp file will be /var/run/utmp. + +AUTHOR + Written by Joseph Arceneaux, David MacKenzie, and Kaveh + Ghazi. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for pinky is maintained as a Tex- + info manual. If the info and pinky programs are prop- + erly installed at your site, the command + + info pinky + + should give you access to the complete manual. + + + +pinky 5.3.0 November 2004 PINKY(1) diff --git a/coreutils-5.3.0-bin/man/cat1/pr.1.txt b/coreutils-5.3.0-bin/man/cat1/pr.1.txt new file mode 100644 index 0000000..ed02e0b --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/pr.1.txt @@ -0,0 +1,150 @@ +PR(1) User Commands PR(1) + + + + + +NAME + pr - convert text files for printing + +SYNOPSIS + pr [OPTION]... [FILE]... + +DESCRIPTION + Paginate or columnate FILE(s) for printing. + + Mandatory arguments to long options are mandatory for + short options too. + + +FIRST_PAGE[:LAST_PAGE], --pages=FIRST_PAGE[:LAST_PAGE] + begin [stop] printing with page FIRST_[LAST_]PAGE + + -COLUMN, --columns=COLUMN + output COLUMN columns and print columns down, + unless -a is used. Balance number of lines in the + columns on each page. + + -a, --across + print columns across rather than down, used + together with -COLUMN + + -c, --show-control-chars + use hat notation (^G) and octal backslash nota- + tion + + -d, --double-space + double space the output + + -D, --date-format=FORMAT + use FORMAT for the header date + + -e[CHAR[WIDTH]], --expand-tabs[=CHAR[WIDTH]] + expand input CHARs (TABs) to tab WIDTH (8) + + -F, -f, --form-feed + use form feeds instead of newlines to separate + pages (by a 3-line page header with -F or a + 5-line header and trailer without -F) + + -h HEADER, --header=HEADER + use a centered HEADER instead of filename in page + header, -h "" prints a blank line, don't use -h"" + + -i[CHAR[WIDTH]], --output-tabs[=CHAR[WIDTH]] + replace spaces with CHARs (TABs) to tab WIDTH (8) + + -J, --join-lines + merge full lines, turns off -W line truncation, + no column alignment, --sep-string[=STRING] sets + separators + + -l PAGE_LENGTH, --length=PAGE_LENGTH + set the page length to PAGE_LENGTH (66) lines + (default number of lines of text 56, and with -F + 63) + + -m, --merge + print all files in parallel, one in each column, + truncate lines, but join lines of full length + with -J + + -n[SEP[DIGITS]], --number-lines[=SEP[DIGITS]] + number lines, use DIGITS (5) digits, then SEP + (TAB), default counting starts with 1st line of + input file + + -N NUMBER, --first-line-number=NUMBER + start counting with NUMBER at 1st line of first + page printed (see +FIRST_PAGE) + + -o MARGIN, --indent=MARGIN + offset each line with MARGIN (zero) spaces, do + not affect -w or -W, MARGIN will be added to + PAGE_WIDTH + + -r, --no-file-warnings + omit warning when a file cannot be opened + + -s[CHAR],--separator[=CHAR] + separate columns by a single character, default + for CHAR is the <TAB> character without -w and + 'no char' with -w -s[CHAR] turns off line trunca- + tion of all 3 column options (-COLUMN|-a -COL- + UMN|-m) except -w is set + + -SSTRING, --sep-string[=STRING] + separate columns by STRING, without -S: Default + separator <TAB> with -J and <space> otherwise + (same as -S" "), no effect on column options + + -t, --omit-header omit page headers and trailers + + -T, --omit-pagination + omit page headers and trailers, eliminate any + pagination by form feeds set in input files + + -v, --show-nonprinting + use octal backslash notation + + -w PAGE_WIDTH, --width=PAGE_WIDTH + set page width to PAGE_WIDTH (72) characters for + multiple text-column output only, -s[char] turns + off (72) + + -W PAGE_WIDTH, --page-width=PAGE_WIDTH + set page width to PAGE_WIDTH (72) characters + always, truncate lines, except -J option is set, + no interference with -S or -s + + --help display this help and exit + + --version + output version information and exit + + -T implied by -l nn when nn <= 10 or <= 3 with -F. With + no FILE, or when FILE is -, read standard input. + +AUTHOR + Written by Pete TerMaat and Roland Huebner. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2005 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for pr is maintained as a Texinfo + manual. If the info and pr programs are properly + installed at your site, the command + + info pr + + should give you access to the complete manual. + + + +pr 5.3.0 January 2005 PR(1) diff --git a/coreutils-5.3.0-bin/man/cat1/printenv.1.txt b/coreutils-5.3.0-bin/man/cat1/printenv.1.txt new file mode 100644 index 0000000..ec917ed --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/printenv.1.txt @@ -0,0 +1,45 @@ +PRINTENV(1) User Commands PRINTENV(1) + + + + + +NAME + printenv - print all or part of environment + +SYNOPSIS + printenv [VARIABLE]... + printenv OPTION + +DESCRIPTION + If no environment VARIABLE specified, print them all. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie and Richard Mlynarik. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for printenv is maintained as a + Texinfo manual. If the info and printenv programs are + properly installed at your site, the command + + info printenv + + should give you access to the complete manual. + + + +printenv 5.3.0 November 2004 PRINTENV(1) diff --git a/coreutils-5.3.0-bin/man/cat1/printf.1.txt b/coreutils-5.3.0-bin/man/cat1/printf.1.txt new file mode 100644 index 0000000..c6a7719 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/printf.1.txt @@ -0,0 +1,96 @@ +PRINTF(1) User Commands PRINTF(1) + + + + + +NAME + printf - format and print data + +SYNOPSIS + printf FORMAT [ARGUMENT]... + printf OPTION + +DESCRIPTION + NOTE: your shell may have its own version of printf + which will supersede the version described here. Please + refer to your shell's documentation for details about + the options it supports. + + Print ARGUMENT(s) according to FORMAT. + + --help display this help and exit + + --version + output version information and exit + + FORMAT controls the output as in C printf. Interpreted + sequences are: + + \" double quote + + \NNN character with octal value NNN (1 to 3 digits) + + \\ backslash + + \a alert (BEL) + + \b backspace + + \c produce no further output + + \f form feed + + \n new line + + \r carriage return + + \t horizontal tab + + \v vertical tab + + \xHH byte with hexadecimal value HH (1 to 2 digits) + + \uHHHH Unicode (ISO/IEC 10646) character with hex value + HHHH (4 digits) + + \UHHHHHHHH + Unicode character with hex value HHHHHHHH (8 dig- + its) + + %% a single % + + %b ARGUMENT as a string with `\' escapes inter- + preted, + + except that octal escapes are of the form \0 or + \0NNN + + and all C format specifications ending with one of + diouxXfeEgGcs, with ARGUMENTs converted to proper type + first. Variable widths are handled. + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for printf is maintained as a + Texinfo manual. If the info and printf programs are + properly installed at your site, the command + + info printf + + should give you access to the complete manual. + + + +printf 5.3.0 November 2004 PRINTF(1) diff --git a/coreutils-5.3.0-bin/man/cat1/ptx.1.txt b/coreutils-5.3.0-bin/man/cat1/ptx.1.txt new file mode 100644 index 0000000..74c4538 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/ptx.1.txt @@ -0,0 +1,105 @@ +PTX(1) User Commands PTX(1) + + + + + +NAME + ptx - produce a permuted index of file contents + +SYNOPSIS + ptx [OPTION]... [INPUT]... (without -G) + ptx -G [OPTION]... [INPUT [OUTPUT]] + +DESCRIPTION + Output a permuted index, including context, of the words + in the input files. + + Mandatory arguments to long options are mandatory for + short options too. + + -A, --auto-reference + output automatically generated references + + -C, --copyright + display Copyright and copying conditions + + -G, --traditional + behave more like System V `ptx' + + -F, --flag-truncation=STRING + use STRING for flagging line truncations + + -M, --macro-name=STRING + macro name to use instead of `xx' + + -O, --format=roff + generate output as roff directives + + -R, --right-side-refs + put references at right, not counted in -w + + -S, --sentence-regexp=REGEXP + for end of lines or end of sentences + + -T, --format=tex + generate output as TeX directives + + -W, --word-regexp=REGEXP + use REGEXP to match each keyword + + -b, --break-file=FILE + word break characters in this FILE + + -f, --ignore-case + fold lower case to upper case for sorting + + -g, --gap-size=NUMBER + gap size in columns between output fields + + -i, --ignore-file=FILE + read ignore word list from FILE + + -o, --only-file=FILE + read only word list from this FILE + + -r, --references + first field of each line is a reference + + -t, --typeset-mode - not implemented - + + -w, --width=NUMBER + output width in columns, reference excluded + + --help display this help and exit + + --version + output version information and exit + + With no FILE or if FILE is -, read Standard Input. `-F + /' by default. + +AUTHOR + Written by F. Pinard. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for ptx is maintained as a Tex- + info manual. If the info and ptx programs are properly + installed at your site, the command + + info ptx + + should give you access to the complete manual. + + + +ptx 5.3.0 November 2004 PTX(1) diff --git a/coreutils-5.3.0-bin/man/cat1/pwd.1.txt b/coreutils-5.3.0-bin/man/cat1/pwd.1.txt new file mode 100644 index 0000000..0458a8a --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/pwd.1.txt @@ -0,0 +1,50 @@ +PWD(1) User Commands PWD(1) + + + + + +NAME + pwd - print name of current/working directory + +SYNOPSIS + pwd [OPTION] + +DESCRIPTION + NOTE: your shell may have its own version of pwd which + will supersede the version described here. Please refer + to your shell's documentation for details about the + options it supports. + + Print the full filename of the current working direc- + tory. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for pwd is maintained as a Tex- + info manual. If the info and pwd programs are properly + installed at your site, the command + + info pwd + + should give you access to the complete manual. + + + +pwd 5.3.0 November 2004 PWD(1) diff --git a/coreutils-5.3.0-bin/man/cat1/readlink.1.txt b/coreutils-5.3.0-bin/man/cat1/readlink.1.txt new file mode 100644 index 0000000..830accf --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/readlink.1.txt @@ -0,0 +1,70 @@ +READLINK(1) User Commands READLINK(1) + + + + + +NAME + readlink - display value of a symbolic link + +SYNOPSIS + readlink [OPTION]... FILE + +DESCRIPTION + Display value of a symbolic link on standard output. + + -f, --canonicalize + canonicalize by following every symlink in every + component of the given path recursively; all but + the last path component must exist + + -e, --canonicalize-existing + canonicalize by following every symlink in every + component of the given path recursively, all path + components must exist + + -m, --canonicalize-missing + canonicalize by following every symlink in every + component of the given path recursively, without + requirements on components existence + + -n, --no-newline + do not output the trailing newline + + -q, --quiet, + + -s, --silent + suppress most error messages + + -v, --verbose + report error messages + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Dmitry V. Levin. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for readlink is maintained as a + Texinfo manual. If the info and readlink programs are + properly installed at your site, the command + + info readlink + + should give you access to the complete manual. + + + +readlink 5.3.0 November 2004 READLINK(1) diff --git a/coreutils-5.3.0-bin/man/cat1/rm.1.txt b/coreutils-5.3.0-bin/man/cat1/rm.1.txt new file mode 100644 index 0000000..8bc315f --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/rm.1.txt @@ -0,0 +1,93 @@ +RM(1) User Commands RM(1) + + + + + +NAME + rm - remove files or directories + +SYNOPSIS + rm [OPTION]... FILE... + +DESCRIPTION + This manual page documents the GNU version of rm. rm + removes each specified file. By default, it does not + remove directories. + + If a file is unwritable, the standard input is a tty, + and the -f or --force option is not given, rm prompts + the user for whether to remove the file. If the + response is not affirmative, the file is skipped. + +OPTIONS + Remove (unlink) the FILE(s). + + -d, --directory + unlink FILE, even if it is a non-empty directory + (super-user only; this works only if your system + + supports `unlink' for nonempty directories) + + -f, --force + ignore nonexistent files, never prompt + + -i, --interactive + prompt before any removal + + --no-preserve-root do not treat `/' specially (the + default) + + --preserve-root + fail to operate recursively on `/' + + -r, -R, --recursive + remove the contents of directories recursively + + -v, --verbose + explain what is being done + + --help display this help and exit + + --version + output version information and exit + + To remove a file whose name starts with a `-', for exam- + ple `-foo', use one of these commands: + + rm -- -foo + + rm ./-foo + + Note that if you use rm to remove a file, it is usually + possible to recover the contents of that file. If you + want more assurance that the contents are truly unrecov- + erable, consider using shred. + +AUTHOR + Written by Paul Rubin, David MacKenzie, Richard Stall- + man, and Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + chattr(1), shred(1) + + The full documentation for rm is maintained as a Texinfo + manual. If the info and rm programs are properly + installed at your site, the command + + info rm + + should give you access to the complete manual. + + + +rm 5.3.0 November 2004 RM(1) diff --git a/coreutils-5.3.0-bin/man/cat1/rmdir.1.txt b/coreutils-5.3.0-bin/man/cat1/rmdir.1.txt new file mode 100644 index 0000000..87821e6 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/rmdir.1.txt @@ -0,0 +1,57 @@ +RMDIR(1) User Commands RMDIR(1) + + + + + +NAME + rmdir - remove empty directories + +SYNOPSIS + rmdir [OPTION]... DIRECTORY... + +DESCRIPTION + Remove the DIRECTORY(ies), if they are empty. + + --ignore-fail-on-non-empty + + ignore each failure that is solely because a + directory is non-empty + + -p, --parents + remove DIRECTORY, then try to remove each direc- + tory component of that path name. E.g., `rmdir + -p a/b/c' is similar to `rmdir a/b/c a/b a'. + + -v, --verbose + output a diagnostic for every directory processed + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for rmdir is maintained as a Tex- + info manual. If the info and rmdir programs are prop- + erly installed at your site, the command + + info rmdir + + should give you access to the complete manual. + + + +rmdir 5.3.0 November 2004 RMDIR(1) diff --git a/coreutils-5.3.0-bin/man/cat1/sed.1.txt b/coreutils-5.3.0-bin/man/cat1/sed.1.txt new file mode 100644 index 0000000..f1153f1 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/sed.1.txt @@ -0,0 +1,321 @@ +SED(1) User Commands SED(1) + + + +NAME + sed - stream editor for filtering and transforming text + +SYNOPSIS + sed.exe [OPTION]... {script-only-if-no-other-script} + [input-file]... + +DESCRIPTION + Sed is a stream editor. A stream editor is used to per- + form basic text transformations on an input stream (a + file or input from a pipeline). While in some ways sim- + ilar to an editor which permits scripted edits (such as + ed), sed works by making only one pass over the + input(s), and is consequently more efficient. But it is + sed's ability to filter text in a pipeline which partic- + ularly distinguishes it from other types of editors. + + -n, --quiet, --silent + + suppress automatic printing of pattern space + + -e script, --expression=script + + add the script to the commands to be executed + + -f script-file, --file=script-file + + add the contents of script-file to the commands + to be executed + + -i[SUFFIX], --in-place[=SUFFIX] + + edit files in place (makes backup if extension + supplied) + + -b, --binary + + open files in binary mode (CR+LFs are not pro- + cessed specially) + + -c, --copy + + use copy instead of rename when shuffling files + in -i mode (avoids change of input file owner- + ship) + + -l N, --line-length=N + + specify the desired line-wrap length for the `l' + command + + --posix + + disable all GNU extensions. + + -r, --regexp-extended + + use extended regular expressions in the script. + + -s, --separate + + consider files as separate rather than as a sin- + gle continuous long stream. + + -u, --unbuffered + + load minimal amounts of data from the input files + and flush the output buffers more often + + --help + display this help and exit + + --version + output version information and exit + + If no -e, --expression, -f, or --file option is given, + then the first non-option argument is taken as the sed + script to interpret. All remaining arguments are names + of input files; if no input files are specified, then + the standard input is read. + + GNU sed home page: <http://www.gnu.org/software/sed/>. + General help using GNU software: + <http://www.gnu.org/gethelp/>. E-mail bug reports to: + <bug-gnu-utils@gnu.org>. Be sure to include the word + ``sed'' somewhere in the ``Subject:'' field. + +COMMAND SYNOPSIS + This is just a brief synopsis of sed commands to serve + as a reminder to those who already know sed; other docu- + mentation (such as the texinfo document) must be con- + sulted for fuller descriptions. + + Zero-address ``commands'' + : label + Label for b and t commands. + + #comment + The comment extends until the next newline (or + the end of a -e script fragment). + + } The closing bracket of a { } block. + + Zero- or One- address commands + = Print the current line number. + + a \ + + text Append text, which has each embedded newline pre- + ceded by a backslash. + + i \ + + text Insert text, which has each embedded newline pre- + ceded by a backslash. + + q [exit-code] + Immediately quit the sed script without process- + ing any more input, except that if auto-print is + not disabled the current pattern space will be + printed. The exit code argument is a GNU exten- + sion. + + Q [exit-code] + Immediately quit the sed script without process- + ing any more input. This is a GNU extension. + + r filename + Append text read from filename. + + R filename + Append a line read from filename. Each invoca- + tion of the command reads a line from the file. + This is a GNU extension. + + Commands which accept address ranges + { Begin a block of commands (end with a }). + + b label + Branch to label; if label is omitted, branch to + end of script. + + t label + If a s/// has done a successful substitution + since the last input line was read and since the + last t or T command, then branch to label; if + label is omitted, branch to end of script. + + T label + If no s/// has done a successful substitution + since the last input line was read and since the + last t or T command, then branch to label; if + label is omitted, branch to end of script. This + is a GNU extension. + + c \ + + text Replace the selected lines with text, which has + each embedded newline preceded by a backslash. + + d Delete pattern space. Start next cycle. + + D Delete up to the first embedded newline in the + pattern space. Start next cycle, but skip read- + ing from the input if there is still data in the + pattern space. + + h H Copy/append pattern space to hold space. + + g G Copy/append hold space to pattern space. + + x Exchange the contents of the hold and pattern + spaces. + + l List out the current line in a ``visually unam- + biguous'' form. + + l width + List out the current line in a ``visually unam- + biguous'' form, breaking it at width characters. + This is a GNU extension. + + n N Read/append the next line of input into the pat- + tern space. + + p Print the current pattern space. + + P Print up to the first embedded newline of the + current pattern space. + + s/regexp/replacement/ + Attempt to match regexp against the pattern + space. If successful, replace that portion + matched with replacement. The replacement may + contain the special character & to refer to that + portion of the pattern space which matched, and + the special escapes \1 through \9 to refer to the + corresponding matching sub-expressions in the + regexp. + + w filename + Write the current pattern space to filename. + + W filename + Write the first line of the current pattern space + to filename. This is a GNU extension. + + y/source/dest/ + Transliterate the characters in the pattern space + which appear in source to the corresponding char- + acter in dest. + +Addresses + Sed commands can be given with no addresses, in which + case the command will be executed for all input lines; + with one address, in which case the command will only be + executed for input lines which match that address; or + with two addresses, in which case the command will be + executed for all input lines which match the inclusive + range of lines starting from the first address and con- + tinuing to the second address. Three things to note + about address ranges: the syntax is addr1,addr2 (i.e., + the addresses are separated by a comma); the line which + addr1 matched will always be accepted, even if addr2 + selects an earlier line; and if addr2 is a regexp, it + will not be tested against the line that addr1 matched. + + After the address (or address-range), and before the + command, a ! may be inserted, which specifies that the + command shall only be executed if the address (or + address-range) does not match. + + The following address types are supported: + + number Match only the specified line number. + + first~step + Match every step'th line starting with line + first. For example, ``sed -n 1~2p'' will print + all the odd-numbered lines in the input stream, + and the address 2~5 will match every fifth line, + starting with the second. first can be zero; in + this case, sed operates as if it were equal to + step. (This is an extension.) + + $ Match the last line. + + /regexp/ + Match lines matching the regular expression reg- + exp. + + \cregexpc + Match lines matching the regular expression reg- + exp. The c may be any character. + + GNU sed also supports some special 2-address forms: + + 0,addr2 + Start out in "matched first address" state, until + addr2 is found. This is similar to 1,addr2, + except that if addr2 matches the very first line + of input the 0,addr2 form will be at the end of + its range, whereas the 1,addr2 form will still be + at the beginning of its range. This works only + when addr2 is a regular expression. + + addr1,+N + Will match addr1 and the N lines following addr1. + + addr1,~N + Will match addr1 and the lines following addr1 + until the next line whose input line number is a + multiple of N. + +REGULAR EXPRESSIONS + POSIX.2 BREs should be supported, but they aren't com- + pletely because of performance problems. The \n + sequence in a regular expression matches the newline + character, and similarly for \a, \t, and other + sequences. + +BUGS + E-mail bug reports to bonzini@gnu.org. Be sure to + include the word ``sed'' somewhere in the ``Subject:'' + field. Also, please include the output of ``sed --ver- + sion'' in the body of your report if at all possible. + +COPYRIGHT + Copyright © 2009 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE, to the extent + permitted by law. + + GNU sed home page: <http://www.gnu.org/software/sed/>. + General help using GNU software: + <http://www.gnu.org/gethelp/>. E-mail bug reports to: + <bug-gnu-utils@gnu.org>. Be sure to include the word + ``sed'' somewhere in the ``Subject:'' field. + +SEE ALSO + awk(1), ed(1), grep(1), tr(1), perlre(1), sed.info, any + of various books on sed, the sed FAQ + (http://sed.sf.net/grabbag/tutorials/sedfaq.txt), + http://sed.sf.net/grabbag/. + + The full documentation for sed is maintained as a Tex- + info manual. If the info and sed programs are properly + installed at your site, the command + + info sed + + should give you access to the complete manual. + + + +sed version 4.2.1 June 2009 SED(1) diff --git a/coreutils-5.3.0-bin/man/cat1/seq.1.txt b/coreutils-5.3.0-bin/man/cat1/seq.1.txt new file mode 100644 index 0000000..cb0419e --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/seq.1.txt @@ -0,0 +1,66 @@ +SEQ(1) User Commands SEQ(1) + + + + + +NAME + seq - print a sequence of numbers + +SYNOPSIS + seq [OPTION]... LAST + seq [OPTION]... FIRST LAST + seq [OPTION]... FIRST INCREMENT LAST + +DESCRIPTION + Print numbers from FIRST to LAST, in steps of INCREMENT. + + -f, --format=FORMAT + use printf style floating-point FORMAT (default: + %g) + + -s, --separator=STRING + use STRING to separate numbers (default: \n) + + -w, --equal-width + equalize width by padding with leading zeroes + + --help display this help and exit + + --version + output version information and exit + + If FIRST or INCREMENT is omitted, it defaults to 1. + That is, an omitted INCREMENT defaults to 1 even when + LAST is smaller than FIRST. FIRST, INCREMENT, and LAST + are interpreted as floating point values. INCREMENT is + usually positive if FIRST is smaller than LAST, and + INCREMENT is usually negative if FIRST is greater than + LAST. When given, the FORMAT argument must contain + exactly one of the printf-style, floating point output + formats %e, %f, %g + +AUTHOR + Written by Ulrich Drepper. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for seq is maintained as a Tex- + info manual. If the info and seq programs are properly + installed at your site, the command + + info seq + + should give you access to the complete manual. + + + +seq 5.3.0 December 2004 SEQ(1) diff --git a/coreutils-5.3.0-bin/man/cat1/sha1sum.1.txt b/coreutils-5.3.0-bin/man/cat1/sha1sum.1.txt new file mode 100644 index 0000000..a249897 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/sha1sum.1.txt @@ -0,0 +1,70 @@ +SHA1SUM(1) User Commands SHA1SUM(1) + + + + + +NAME + sha1sum - compute and check SHA1 message digest + +SYNOPSIS + sha1sum [OPTION] [FILE]... + sha1sum [OPTION] --check [FILE] + +DESCRIPTION + Print or check SHA1 (160-bit) checksums. With no FILE, + or when FILE is -, read standard input. + + -b, --binary + read files in binary mode (default on DOS/Win- + dows) + + -c, --check + check SHA1 sums against given list + + -t, --text + read files in text mode (default) + + The following two options are useful only when verifying + checksums: + --status + don't output anything, status code shows success + + -w, --warn + warn about improperly formated checksum lines + + --help display this help and exit + + --version + output version information and exit + + The sums are computed as described in FIPS-180-1. When + checking, the input should be a former output of this + program. The default mode is to print a line with + checksum, a character indicating type (`*' for binary, ` + ' for text), and name for each FILE. + +AUTHOR + Written by Ulrich Drepper and Scott Miller. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for sha1sum is maintained as a + Texinfo manual. If the info and sha1sum programs are + properly installed at your site, the command + + info sha1sum + + should give you access to the complete manual. + + + +sha1sum 5.3.0 November 2004 SHA1SUM(1) diff --git a/coreutils-5.3.0-bin/man/cat1/shred.1.txt b/coreutils-5.3.0-bin/man/cat1/shred.1.txt new file mode 100644 index 0000000..3748041 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/shred.1.txt @@ -0,0 +1,116 @@ +SHRED(1) User Commands SHRED(1) + + + + + +NAME + shred - overwrite a file to hide its contents, and + optionally delete it + +SYNOPSIS + shred [OPTIONS] FILE [...] + +DESCRIPTION + Overwrite the specified FILE(s) repeatedly, in order to + make it harder for even very expensive hardware probing + to recover the data. + + Mandatory arguments to long options are mandatory for + short options too. + + -f, --force + change permissions to allow writing if necessary + + -n, --iterations=N + Overwrite N times instead of the default (25) + + -s, --size=N + shred this many bytes (suffixes like K, M, G + accepted) + + -u, --remove + truncate and remove file after overwriting + + -v, --verbose + show progress + + -x, --exact + do not round file sizes up to the next full + block; + + this is the default for non-regular files + + -z, --zero + add a final overwrite with zeros to hide shred- + ding + + --help display this help and exit + + --version + output version information and exit + + If FILE is -, shred standard output. + + Delete FILE(s) if --remove (-u) is specified. The + default is not to remove the files because it is common + to operate on device files like /dev/hda, and those + files usually should not be removed. When operating on + regular files, most people use the --remove option. + + CAUTION: Note that shred relies on a very important + assumption: that the file system overwrites data in + place. This is the traditional way to do things, but + many modern file system designs do not satisfy this + assumption. The following are examples of file systems + on which shred is not effective: + + * log-structured or journaled file systems, such as + those supplied with + + AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, + etc.) + + * file systems that write redundant data and carry on + even if some writes + + fail, such as RAID-based file systems + + * file systems that make snapshots, such as Network + Appliance's NFS server + + * file systems that cache in temporary locations, such + as NFS + + version 3 clients + + * compressed file systems + + In addition, file system backups and remote mirrors may + contain copies of the file that cannot be removed, and + that will allow a shredded file to be recovered later. + +AUTHOR + Written by Colin Plumb. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2005 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for shred is maintained as a Tex- + info manual. If the info and shred programs are prop- + erly installed at your site, the command + + info shred + + should give you access to the complete manual. + + + +shred 5.3.0 January 2005 SHRED(1) diff --git a/coreutils-5.3.0-bin/man/cat1/sleep.1.txt b/coreutils-5.3.0-bin/man/cat1/sleep.1.txt new file mode 100644 index 0000000..6ed8ec7 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/sleep.1.txt @@ -0,0 +1,49 @@ +SLEEP(1) User Commands SLEEP(1) + + + + + +NAME + sleep - delay for a specified amount of time + +SYNOPSIS + sleep NUMBER[SUFFIX]... + sleep OPTION + +DESCRIPTION + Pause for NUMBER seconds. SUFFIX may be `s' for seconds + (the default), `m' for minutes, `h' for hours or `d' for + days. Unlike most implementations that require NUMBER + be an integer, here NUMBER may be an arbitrary floating + point number. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Jim Meyering and Paul Eggert. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for sleep is maintained as a Tex- + info manual. If the info and sleep programs are prop- + erly installed at your site, the command + + info sleep + + should give you access to the complete manual. + + + +sleep 5.3.0 November 2004 SLEEP(1) diff --git a/coreutils-5.3.0-bin/man/cat1/sort.1.txt b/coreutils-5.3.0-bin/man/cat1/sort.1.txt new file mode 100644 index 0000000..87be6a1 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/sort.1.txt @@ -0,0 +1,124 @@ +SORT(1) User Commands SORT(1) + + + + + +NAME + sort - sort lines of text files + +SYNOPSIS + sort [OPTION]... [FILE]... + +DESCRIPTION + Write sorted concatenation of all FILE(s) to standard + output. + + Ordering options: + + Mandatory arguments to long options are mandatory for + short options too. + + -b, --ignore-leading-blanks ignore leading blanks + + -d, --dictionary-order + consider only blanks and alphanumeric characters + + -f, --ignore-case + fold lower case to upper case characters + + -g, --general-numeric-sort + compare according to general numerical value + + -i, --ignore-nonprinting + consider only printable characters + + -M, --month-sort + compare (unknown) < `JAN' < ... < `DEC' + + -n, --numeric-sort + compare according to string numerical value + + -r, --reverse + reverse the result of comparisons + + Other options: + + -c, --check + check whether input is sorted; do not sort + + -k, --key=POS1[,POS2] + start a key at POS1, end it at POS 2 (origin 1) + + -m, --merge + merge already sorted files; do not sort + + -o, --output=FILE + write result to FILE instead of standard output + + -s, --stable + stabilize sort by disabling last-resort compari- + son + + -S, --buffer-size=SIZE + use SIZE for main memory buffer + + -t, --field-separator=SEP use SEP instead of non-blank + to blank transition + + -T, --temporary-directory=DIR + use DIR for temporaries, not $TMPDIR or /tmp; + multiple options specify multiple directories + + -u, --unique + with -c, check for strict ordering; without -c, + output only the first of an equal run + + -z, --zero-terminated + end lines with 0 byte, not newline + + --help display this help and exit + + --version + output version information and exit + + POS is F[.C][OPTS], where F is the field number and C + the character position in the field. OPTS is one or + more single-letter ordering options, which override + global ordering options for that key. If no key is + given, use the entire line as the key. + + SIZE may be followed by the following multiplicative + suffixes: % 1% of memory, b 1, K 1024 (default), and so + on for M, G, T, P, E, Z, Y. + + With no FILE, or when FILE is -, read standard input. + + *** WARNING *** The locale specified by the environment + affects sort order. Set LC_ALL=C to get the traditional + sort order that uses native byte values. + +AUTHOR + Written by Mike Haertel and Paul Eggert. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for sort is maintained as a Tex- + info manual. If the info and sort programs are properly + installed at your site, the command + + info sort + + should give you access to the complete manual. + + + +sort 5.3.0 December 2004 SORT(1) diff --git a/coreutils-5.3.0-bin/man/cat1/split.1.txt b/coreutils-5.3.0-bin/man/cat1/split.1.txt new file mode 100644 index 0000000..732a758 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/split.1.txt @@ -0,0 +1,71 @@ +SPLIT(1) User Commands SPLIT(1) + + + + + +NAME + split - split a file into pieces + +SYNOPSIS + split [OPTION] [INPUT [PREFIX]] + +DESCRIPTION + Output fixed-size pieces of INPUT to PREFIXaa, PREFIXab, + ...; default PREFIX is `x'. With no INPUT, or when + INPUT is -, read standard input. + + Mandatory arguments to long options are mandatory for + short options too. + + -a, --suffix-length=N + use suffixes of length N (default 2) + + -b, --bytes=SIZE + put SIZE bytes per output file + + -C, --line-bytes=SIZE + put at most SIZE bytes of lines per output file + + -d, --numeric-suffixes + use numeric suffixes instead of alphabetic + + -l, --lines=NUMBER + put NUMBER lines per output file + + --verbose + print a diagnostic to standard error just before + each output file is opened + + --help display this help and exit + + --version + output version information and exit + + SIZE may have a multiplier suffix: b for 512, k for 1K, + m for 1 Meg. + +AUTHOR + Written by Torbjorn Granlund and Richard M. Stallman. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for split is maintained as a Tex- + info manual. If the info and split programs are prop- + erly installed at your site, the command + + info split + + should give you access to the complete manual. + + + +split 5.3.0 December 2004 SPLIT(1) diff --git a/coreutils-5.3.0-bin/man/cat1/stat.1.txt b/coreutils-5.3.0-bin/man/cat1/stat.1.txt new file mode 100644 index 0000000..ddb9d58 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/stat.1.txt @@ -0,0 +1,136 @@ +STAT(1) User Commands STAT(1) + + + + + +NAME + stat - display file or file system status + +SYNOPSIS + stat [OPTION] FILE... + +DESCRIPTION + Display file or file system status. + + -f, --file-system + display file system status instead of file status + + -c --format=FORMAT + use the specified FORMAT instead of the default + + -L, --dereference + follow links + + -t, --terse + print the information in terse form + + --help display this help and exit + + --version + output version information and exit + + The valid format sequences for files (without + --file-system): + + %A Access rights in human readable form + + %a Access rights in octal + + %B The size in bytes of each block reported by `%b' + + %b Number of blocks allocated (see %B) + + %D Device number in hex + + %d Device number in decimal + + %F File type + + %f Raw mode in hex + + %G Group name of owner + + %g Group ID of owner + + %h Number of hard links + + %i Inode number + + %N Quoted File name with dereference if symbolic + link + + %n File name + + %o IO block size + + %s Total size, in bytes + + %T Minor device type in hex + + %t Major device type in hex + + %U User name of owner + + %u User ID of owner + + %X Time of last access as seconds since Epoch + + %x Time of last access + + %Y Time of last modification as seconds since Epoch + + %y Time of last modification + + %Z Time of last change as seconds since Epoch + + %z Time of last change + + Valid format sequences for file systems: + + %a Free blocks available to non-superuser + + %b Total data blocks in file system + + %c Total file nodes in file system + + %d Free file nodes in file system + + %f Free blocks in file system + + %i File System id in hex + + %l Maximum length of filenames + + %n File name + + %s Optimal transfer block size + + %T Type in human readable form + + %t Type in hex + +AUTHOR + Written by Michael Meskes. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for stat is maintained as a Tex- + info manual. If the info and stat programs are properly + installed at your site, the command + + info stat + + should give you access to the complete manual. + + + +stat 5.3.0 November 2004 STAT(1) diff --git a/coreutils-5.3.0-bin/man/cat1/stty.1.txt b/coreutils-5.3.0-bin/man/cat1/stty.1.txt new file mode 100644 index 0000000..6d1cebf --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/stty.1.txt @@ -0,0 +1,403 @@ +STTY(1) User Commands STTY(1) + + + + + +NAME + stty - change and print terminal line settings + +SYNOPSIS + stty [-F DEVICE] [--file=DEVICE] [SETTING]... + stty [-F DEVICE] [--file=DEVICE] [-a|--all] + stty [-F DEVICE] [--file=DEVICE] [-g|--save] + +DESCRIPTION + Print or change terminal characteristics. + + -a, --all + print all current settings in human-readable form + + -g, --save + print all current settings in a stty-readable + form + + -F, --file=DEVICE + open and use the specified DEVICE instead of + stdin + + --help display this help and exit + + --version + output version information and exit + + Optional - before SETTING indicates negation. An * + marks non-POSIX settings. The underlying system defines + which settings are available. + + Special characters: + * dsusp CHAR + CHAR will send a terminal stop signal once input + flushed + + eof CHAR + CHAR will send an end of file (terminate the + input) + + eol CHAR + CHAR will end the line + + * eol2 CHAR + alternate CHAR for ending the line + + erase CHAR + CHAR will erase the last character typed + + intr CHAR + CHAR will send an interrupt signal + + kill CHAR + CHAR will erase the current line + + * lnext CHAR + CHAR will enter the next character quoted + + quit CHAR + CHAR will send a quit signal + + * rprnt CHAR + CHAR will redraw the current line + + start CHAR + CHAR will restart the output after stopping it + + stop CHAR + CHAR will stop the output + + susp CHAR + CHAR will send a terminal stop signal + + * swtch CHAR + CHAR will switch to a different shell layer + + * werase CHAR + CHAR will erase the last word typed + + Special settings: + N set the input and output speeds to N bauds + + * cols N + tell the kernel that the terminal has N columns + + * columns N + same as cols N + + ispeed N + set the input speed to N + + * line N + use line discipline N + + min N with -icanon, set N characters minimum for a com- + pleted read + + ospeed N + set the output speed to N + + * rows N + tell the kernel that the terminal has N rows + + * size print the number of rows and columns according to + the kernel + + speed print the terminal speed + + time N with -icanon, set read timeout of N tenths of a + second + + Control settings: + [-]clocal + disable modem control signals + + [-]cread + allow input to be received + + * [-]crtscts + enable RTS/CTS handshaking + + csN set character size to N bits, N in [5..8] + + [-]cstopb + use two stop bits per character (one with `-') + + [-]hup send a hangup signal when the last process closes + the tty + + [-]hupcl + same as [-]hup + + [-]parenb + generate parity bit in output and expect parity + bit in input + + [-]parodd + set odd parity (even with `-') + + Input settings: + [-]brkint + breaks cause an interrupt signal + + [-]icrnl + translate carriage return to newline + + [-]ignbrk + ignore break characters + + [-]igncr + ignore carriage return + + [-]ignpar + ignore characters with parity errors + + * [-]imaxbel + beep and do not flush a full input buffer on a + character + + [-]inlcr + translate newline to carriage return + + [-]inpck + enable input parity checking + + [-]istrip + clear high (8th) bit of input characters + + * [-]iutf8 + assume input characters are UTF-8 encoded + + * [-]iuclc + translate uppercase characters to lowercase + + * [-]ixany + let any character restart output, not only start + character + + [-]ixoff + enable sending of start/stop characters + + [-]ixon + enable XON/XOFF flow control + + [-]parmrk + mark parity errors (with a 255-0-character + sequence) + + [-]tandem + same as [-]ixoff + + Output settings: + * bsN backspace delay style, N in [0..1] + + * crN carriage return delay style, N in [0..3] + + * ffN form feed delay style, N in [0..1] + + * nlN newline delay style, N in [0..1] + + * [-]ocrnl + translate carriage return to newline + + * [-]ofdel + use delete characters for fill instead of null + characters + + * [-]ofill + use fill (padding) characters instead of timing + for delays + + * [-]olcuc + translate lowercase characters to uppercase + + * [-]onlcr + translate newline to carriage return-newline + + * [-]onlret + newline performs a carriage return + + * [-]onocr + do not print carriage returns in the first column + + [-]opost + postprocess output + + * tabN horizontal tab delay style, N in [0..3] + + * tabs same as tab0 + + * -tabs + same as tab3 + + * vtN vertical tab delay style, N in [0..1] + + Local settings: + [-]crterase + echo erase characters as + backspace-space-backspace + + * crtkill + kill all line by obeying the echoprt and echoe + settings + + * -crtkill + kill all line by obeying the echoctl and echok + settings + + * [-]ctlecho + echo control characters in hat notation (`^c') + + [-]echo + echo input characters + + * [-]echoctl + same as [-]ctlecho + + [-]echoe + same as [-]crterase + + [-]echok + echo a newline after a kill character + + * [-]echoke + same as [-]crtkill + + [-]echonl + echo newline even if not echoing other characters + + * [-]echoprt + echo erased characters backward, between `\' and + '/' + + [-]icanon + enable erase, kill, werase, and rprnt special + characters + + [-]iexten + enable non-POSIX special characters + + [-]isig + enable interrupt, quit, and suspend special char- + acters + + [-]noflsh + disable flushing after interrupt and quit special + characters + + * [-]prterase + same as [-]echoprt + + * [-]tostop + stop background jobs that try to write to the + terminal + + * [-]xcase + with icanon, escape with `\' for uppercase char- + acters + + Combination settings: + * [-]LCASE + same as [-]lcase + + cbreak same as -icanon + + -cbreak + same as icanon + + cooked same as brkint ignpar istrip icrnl ixon opost + isig icanon, eof and eol characters to their + default values + + -cooked + same as raw + + crt same as echoe echoctl echoke + + dec same as echoe echoctl echoke -ixany intr ^c erase + 0177 kill ^u + + * [-]decctlq + same as [-]ixany + + ek erase and kill characters to their default values + + evenp same as parenb -parodd cs7 + + -evenp same as -parenb cs8 + + * [-]lcase + same as xcase iuclc olcuc + + litout same as -parenb -istrip -opost cs8 + + -litout + same as parenb istrip opost cs7 + + nl same as -icrnl -onlcr + + -nl same as icrnl -inlcr -igncr onlcr -ocrnl -onlret + + oddp same as parenb parodd cs7 + + -oddp same as -parenb cs8 + + [-]parity + same as [-]evenp + + pass8 same as -parenb -istrip cs8 + + -pass8 same as parenb istrip cs7 + + raw same as -ignbrk -brkint -ignpar -parmrk -inpck + -istrip -inlcr -igncr -icrnl -ixon -ixoff + -iuclc -ixany -imaxbel -opost -isig -icanon + -xcase min 1 time 0 + + -raw same as cooked + + sane same as cread -ignbrk brkint -inlcr -igncr icrnl + -iutf8 -ixoff -iuclc -ixany imaxbel opost -olcuc + -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 + tab0 bs0 vt0 ff0 isig icanon iexten echo echoe + echok -echonl -noflsh -xcase -tostop -echoprt + echoctl echoke, all special characters to their + default values. + + Handle the tty line connected to standard input. With- + out arguments, prints baud rate, line discipline, and + deviations from stty sane. In settings, CHAR is taken + literally, or coded as in ^c, 0x37, 0177 or 127; special + values ^- or undef used to disable special characters. + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for stty is maintained as a Tex- + info manual. If the info and stty programs are properly + installed at your site, the command + + info stty + + should give you access to the complete manual. + + + +stty 5.3.0 November 2004 STTY(1) diff --git a/coreutils-5.3.0-bin/man/cat1/su.1.txt b/coreutils-5.3.0-bin/man/cat1/su.1.txt new file mode 100644 index 0000000..641c0ff --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/su.1.txt @@ -0,0 +1,64 @@ +SU(1) User Commands SU(1) + + + + + +NAME + su - run a shell with substitute user and group IDs + +SYNOPSIS + su [OPTION]... [-] [USER [ARG]...] + +DESCRIPTION + Change the effective user id and group id to that of + USER. + + -, -l, --login + make the shell a login shell + + -c, --commmand=COMMAND + pass a single COMMAND to the shell with -c + + -f, --fast + pass -f to the shell (for csh or tcsh) + + -m, --preserve-environment + do not reset environment variables + + -p same as -m + + -s, --shell=SHELL + run SHELL if /etc/shells allows it + + --help display this help and exit + + --version + output version information and exit + + A mere - implies -l. If USER not given, assume root. + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for su is maintained as a Texinfo + manual. If the info and su programs are properly + installed at your site, the command + + info su + + should give you access to the complete manual. + + + +su 5.3.0 November 2004 SU(1) diff --git a/coreutils-5.3.0-bin/man/cat1/sum.1.txt b/coreutils-5.3.0-bin/man/cat1/sum.1.txt new file mode 100644 index 0000000..b646973 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/sum.1.txt @@ -0,0 +1,51 @@ +SUM(1) User Commands SUM(1) + + + + + +NAME + sum - checksum and count the blocks in a file + +SYNOPSIS + sum [OPTION]... [FILE]... + +DESCRIPTION + Print checksum and block counts for each FILE. + + -r defeat -s, use BSD sum algorithm, use 1K blocks + + -s, --sysv + use System V sum algorithm, use 512 bytes blocks + + --help display this help and exit + + --version + output version information and exit + + With no FILE, or when FILE is -, read standard input. + +AUTHOR + Written by Kayvan Aghaiepour and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for sum is maintained as a Tex- + info manual. If the info and sum programs are properly + installed at your site, the command + + info sum + + should give you access to the complete manual. + + + +sum 5.3.0 November 2004 SUM(1) diff --git a/coreutils-5.3.0-bin/man/cat1/sync.1.txt b/coreutils-5.3.0-bin/man/cat1/sync.1.txt new file mode 100644 index 0000000..c0e5b8a --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/sync.1.txt @@ -0,0 +1,44 @@ +SYNC(1) User Commands SYNC(1) + + + + + +NAME + sync - flush file system buffers + +SYNOPSIS + sync [OPTION] + +DESCRIPTION + Force changed blocks to disk, update the super block. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for sync is maintained as a Tex- + info manual. If the info and sync programs are properly + installed at your site, the command + + info sync + + should give you access to the complete manual. + + + +sync (coreutils) 5.3.0 November 2004 SYNC(1) diff --git a/coreutils-5.3.0-bin/man/cat1/tac.1.txt b/coreutils-5.3.0-bin/man/cat1/tac.1.txt new file mode 100644 index 0000000..10828c5 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/tac.1.txt @@ -0,0 +1,57 @@ +TAC(1) User Commands TAC(1) + + + + + +NAME + tac - concatenate and print files in reverse + +SYNOPSIS + tac [OPTION]... [FILE]... + +DESCRIPTION + Write each FILE to standard output, last line first. + With no FILE, or when FILE is -, read standard input. + + Mandatory arguments to long options are mandatory for + short options too. + + -b, --before + attach the separator before instead of after + + -r, --regex + interpret the separator as a regular expression + + -s, --separator=STRING + use STRING as the separator instead of newline + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Jay Lepreau and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for tac is maintained as a Tex- + info manual. If the info and tac programs are properly + installed at your site, the command + + info tac + + should give you access to the complete manual. + + + +tac 5.3.0 December 2004 TAC(1) diff --git a/coreutils-5.3.0-bin/man/cat1/tail.1.txt b/coreutils-5.3.0-bin/man/cat1/tail.1.txt new file mode 100644 index 0000000..cc9401f --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/tail.1.txt @@ -0,0 +1,104 @@ +TAIL(1) User Commands TAIL(1) + + + + + +NAME + tail - output the last part of files + +SYNOPSIS + tail [OPTION]... [FILE]... + +DESCRIPTION + Print the last 10 lines of each FILE to standard output. + With more than one FILE, precede each with a header giv- + ing the file name. With no FILE, or when FILE is -, + read standard input. + + Mandatory arguments to long options are mandatory for + short options too. + + --retry + keep trying to open a file even if it is inacces- + sible when tail starts or if it becomes inacces- + sible later; useful when following by name, i.e., + with --follow=name + + -c, --bytes=N + output the last N bytes + + -f, --follow[={name|descriptor}] + output appended data as the file grows; -f, + --follow, and --follow=descriptor are equivalent + + -F same as --follow=name --retry + + -n, --lines=N + output the last N lines, instead of the last 10 + + --max-unchanged-stats=N + with --follow=name, reopen a FILE which has not + changed size after N (default 5) iterations to + see if it has been unlinked or renamed (this is + the usual case of rotated log files) + + --pid=PID + with -f, terminate after process ID, PID dies + + -q, --quiet, --silent + never output headers giving file names + + -s, --sleep-interval=S + with -f, sleep for approximately S seconds + (default 1.0) between iterations. + + -v, --verbose + always output headers giving file names + + --help display this help and exit + + --version + output version information and exit + + If the first character of N (the number of bytes or + lines) is a `+', print beginning with the Nth item from + the start of each file, otherwise, print the last N + items in the file. N may have a multiplier suffix: b + 512, k 1024, m 1024*1024. + + With --follow (-f), tail defaults to following the file + descriptor, which means that even if a tail'ed file is + renamed, tail will continue to track its end. This + default behavior is not desirable when you really want + to track the actual name of the file, not the file + descriptor (e.g., log rotation). Use --follow=name in + that case. That causes tail to track the named file by + reopening it periodically to see if it has been removed + and recreated by some other program. + +AUTHOR + Written by Paul Rubin, David MacKenzie, Ian Lance Tay- + lor, and Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for tail is maintained as a Tex- + info manual. If the info and tail programs are properly + installed at your site, the command + + info tail + + should give you access to the complete manual. + + + +tail 5.3.0 December 2004 TAIL(1) diff --git a/coreutils-5.3.0-bin/man/cat1/tee.1.txt b/coreutils-5.3.0-bin/man/cat1/tee.1.txt new file mode 100644 index 0000000..631c857 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/tee.1.txt @@ -0,0 +1,55 @@ +TEE(1) User Commands TEE(1) + + + + + +NAME + tee - read from standard input and write to standard + output and files + +SYNOPSIS + tee [OPTION]... [FILE]... + +DESCRIPTION + Copy standard input to each FILE, and also to standard + output. + + -a, --append + append to the given FILEs, do not overwrite + + -i, --ignore-interrupts + ignore interrupt signals + + --help display this help and exit + + --version + output version information and exit + + If a FILE is -, copy again to standard output. + +AUTHOR + Written by Mike Parker, Richard M. Stallman, and David + MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for tee is maintained as a Tex- + info manual. If the info and tee programs are properly + installed at your site, the command + + info tee + + should give you access to the complete manual. + + + +tee 5.3.0 November 2004 TEE(1) diff --git a/coreutils-5.3.0-bin/man/cat1/test.1.txt b/coreutils-5.3.0-bin/man/cat1/test.1.txt new file mode 100644 index 0000000..84d18d5 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/test.1.txt @@ -0,0 +1,171 @@ +TEST(1) User Commands TEST(1) + + + + + +NAME + test - check file types and compare values + +SYNOPSIS + test EXPRESSION + test + + [ EXPRESSION ] + [ ] + [ OPTION + +DESCRIPTION + Exit with the status determined by EXPRESSION. + + --help display this help and exit + + --version + output version information and exit + + An omitted EXPRESSION defaults to false. Otherwise, + EXPRESSION is true or false and sets exit status. It is + one of: + + ( EXPRESSION ) + EXPRESSION is true + + ! EXPRESSION + EXPRESSION is false + + EXPRESSION1 -a EXPRESSION2 + both EXPRESSION1 and EXPRESSION2 are true + + EXPRESSION1 -o EXPRESSION2 + either EXPRESSION1 or EXPRESSION2 is true + + -n STRING + the length of STRING is nonzero + + STRING equivalent to -n STRING + + -z STRING + the length of STRING is zero + + STRING1 = STRING2 + the strings are equal + + STRING1 != STRING2 + the strings are not equal + + INTEGER1 -eq INTEGER2 + INTEGER1 is equal to INTEGER2 + + INTEGER1 -ge INTEGER2 + INTEGER1 is greater than or equal to INTEGER2 + + INTEGER1 -gt INTEGER2 + INTEGER1 is greater than INTEGER2 + + INTEGER1 -le INTEGER2 + INTEGER1 is less than or equal to INTEGER2 + + INTEGER1 -lt INTEGER2 + INTEGER1 is less than INTEGER2 + + INTEGER1 -ne INTEGER2 + INTEGER1 is not equal to INTEGER2 + + FILE1 -ef FILE2 + FILE1 and FILE2 have the same device and inode + numbers + + FILE1 -nt FILE2 + FILE1 is newer (modification date) than FILE2 + + FILE1 -ot FILE2 + FILE1 is older than FILE2 + + -b FILE + FILE exists and is block special + + -c FILE + FILE exists and is character special + + -d FILE + FILE exists and is a directory + + -e FILE + FILE exists + + -f FILE + FILE exists and is a regular file + + -g FILE + FILE exists and is set-group-ID + + -G FILE + FILE exists and is owned by the effective group + ID + + -h FILE + FILE exists and is a symbolic link (same as -L) + + -k FILE + FILE exists and has its sticky bit set + + -L FILE + FILE exists and is a symbolic link (same as -h) + + -O FILE + FILE exists and is owned by the effective user ID + + -p FILE + FILE exists and is a named pipe + + -r FILE + FILE exists and read permission is granted + + -s FILE + FILE exists and has a size greater than zero + + -S FILE + FILE exists and is a socket + + -t FD file descriptor FD is opened on a terminal + + -u FILE + FILE exists and its set-user-ID bit is set + + -w FILE + FILE exists and write permission is granted + + -x FILE + FILE exists and execute (or search) permission is + granted + + Except for -h and -L, all FILE-related tests dereference + symbolic links. Beware that parentheses need to be + escaped (e.g., by backslashes) for shells. INTEGER may + also be -l STRING, which evaluates to the length of + STRING. + +AUTHOR + Written by Kevin Braunsdorf and Matthew Bradburn. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for test is maintained as a Tex- + info manual. If the info and test programs are properly + installed at your site, the command + + info test + + should give you access to the complete manual. + + + +test 5.3.0 November 2004 TEST(1) diff --git a/coreutils-5.3.0-bin/man/cat1/touch.1.txt b/coreutils-5.3.0-bin/man/cat1/touch.1.txt new file mode 100644 index 0000000..4b7513e --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/touch.1.txt @@ -0,0 +1,75 @@ +TOUCH(1) User Commands TOUCH(1) + + + + + +NAME + touch - change file timestamps + +SYNOPSIS + touch [OPTION]... FILE... + +DESCRIPTION + Update the access and modification times of each FILE to + the current time. + + Mandatory arguments to long options are mandatory for + short options too. + + -a change only the access time + + -c, --no-create + do not create any files + + -d, --date=STRING + parse STRING and use it instead of current time + + -f (ignored) + + -m change only the modification time + + -r, --reference=FILE + use this file's times instead of current time + + -t STAMP + use [[CC]YY]MMDDhhmm[.ss] instead of current time + + --time=WORD + change the specified time: WORD is access, atime, + or use: equivalent to -a WORD is modify or mtime: + equivalent to -m + + --help display this help and exit + + --version + output version information and exit + + Note that the -d and -t options accept different + time-date formats. + +AUTHOR + Written by Paul Rubin, Arnold Robbins, Jim Kingdon, + David MacKenzie, and Randy Smith. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for touch is maintained as a Tex- + info manual. If the info and touch programs are prop- + erly installed at your site, the command + + info touch + + should give you access to the complete manual. + + + +touch 5.3.0 November 2004 TOUCH(1) diff --git a/coreutils-5.3.0-bin/man/cat1/tr.1.txt b/coreutils-5.3.0-bin/man/cat1/tr.1.txt new file mode 100644 index 0000000..57bc3e4 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/tr.1.txt @@ -0,0 +1,142 @@ +TR(1) User Commands TR(1) + + + + + +NAME + tr - translate or delete characters + +SYNOPSIS + tr [OPTION]... SET1 [SET2] + +DESCRIPTION + Translate, squeeze, and/or delete characters from stan- + dard input, writing to standard output. + + -c, -C, --complement + first complement SET1 + + -d, --delete + delete characters in SET1, do not translate + + -s, --squeeze-repeats + replace each input sequence of a repeated charac- + ter that is listed in SET1 with a single occur- + rence of that character + + -t, --truncate-set1 + first truncate SET1 to length of SET2 + + --help display this help and exit + + --version + output version information and exit + + SETs are specified as strings of characters. Most rep- + resent themselves. Interpreted sequences are: + + \NNN character with octal value NNN (1 to 3 octal dig- + its) + + \\ backslash + + \a audible BEL + + \b backspace + + \f form feed + + \n new line + + \r return + + \t horizontal tab + + \v vertical tab + + CHAR1-CHAR2 + all characters from CHAR1 to CHAR2 in ascending + order + + [CHAR*] + in SET2, copies of CHAR until length of SET1 + + [CHAR*REPEAT] + REPEAT copies of CHAR, REPEAT octal if starting + with 0 + + [:alnum:] + all letters and digits + + [:alpha:] + all letters + + [:blank:] + all horizontal whitespace + + [:cntrl:] + all control characters + + [:digit:] + all digits + + [:graph:] + all printable characters, not including space + + [:lower:] + all lower case letters + + [:print:] + all printable characters, including space + + [:punct:] + all punctuation characters + + [:space:] + all horizontal or vertical whitespace + + [:upper:] + all upper case letters + + [:xdigit:] + all hexadecimal digits + + [=CHAR=] + all characters which are equivalent to CHAR + + Translation occurs if -d is not given and both SET1 and + SET2 appear. -t may be used only when translating. + SET2 is extended to length of SET1 by repeating its last + character as necessary. Excess characters of SET2 are + ignored. Only [:lower:] and [:upper:] are guaranteed to + expand in ascending order; used in SET2 while translat- + ing, they may only be used in pairs to specify case con- + version. -s uses SET1 if not translating nor deleting; + else squeezing uses SET2 and occurs after translation or + deletion. + +AUTHOR + Written by Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for tr is maintained as a Texinfo + manual. If the info and tr programs are properly + installed at your site, the command + + info tr + + should give you access to the complete manual. + + + +tr 5.3.0 November 2004 TR(1) diff --git a/coreutils-5.3.0-bin/man/cat1/true.1.txt b/coreutils-5.3.0-bin/man/cat1/true.1.txt new file mode 100644 index 0000000..a8931d9 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/true.1.txt @@ -0,0 +1,47 @@ +TRUE(1) User Commands TRUE(1) + + + + + +NAME + true - do nothing, successfully + +SYNOPSIS + true [ignored command line arguments] + true OPTION + +DESCRIPTION + Exit with a status code indicating success. + + These option names may not be abbreviated. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Jim Meyering. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for true is maintained as a Tex- + info manual. If the info and true programs are properly + installed at your site, the command + + info true + + should give you access to the complete manual. + + + +true 5.3.0 November 2004 TRUE(1) diff --git a/coreutils-5.3.0-bin/man/cat1/tsort.1.txt b/coreutils-5.3.0-bin/man/cat1/tsort.1.txt new file mode 100644 index 0000000..724d404 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/tsort.1.txt @@ -0,0 +1,46 @@ +TSORT(1) User Commands TSORT(1) + + + + + +NAME + tsort - perform topological sort + +SYNOPSIS + tsort [OPTION] [FILE] + +DESCRIPTION + Write totally ordered list consistent with the partial + ordering in FILE. With no FILE, or when FILE is -, read + standard input. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Mark Kettenis. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for tsort is maintained as a Tex- + info manual. If the info and tsort programs are prop- + erly installed at your site, the command + + info tsort + + should give you access to the complete manual. + + + +tsort (coreutils) 5.3.0 November 2004 TSORT(1) diff --git a/coreutils-5.3.0-bin/man/cat1/tty.1.txt b/coreutils-5.3.0-bin/man/cat1/tty.1.txt new file mode 100644 index 0000000..cb23ff3 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/tty.1.txt @@ -0,0 +1,49 @@ +TTY(1) User Commands TTY(1) + + + + + +NAME + tty - print the file name of the terminal connected to + standard input + +SYNOPSIS + tty [OPTION]... + +DESCRIPTION + Print the file name of the terminal connected to stan- + dard input. + + -s, --silent, --quiet + print nothing, only return an exit status + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for tty is maintained as a Tex- + info manual. If the info and tty programs are properly + installed at your site, the command + + info tty + + should give you access to the complete manual. + + + +tty 5.3.0 November 2004 TTY(1) diff --git a/coreutils-5.3.0-bin/man/cat1/uname.1.txt b/coreutils-5.3.0-bin/man/cat1/uname.1.txt new file mode 100644 index 0000000..43c2a1f --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/uname.1.txt @@ -0,0 +1,72 @@ +UNAME(1) User Commands UNAME(1) + + + + + +NAME + uname - print system information + +SYNOPSIS + uname [OPTION]... + +DESCRIPTION + Print certain system information. With no OPTION, same + as -s. + + -a, --all + print all information, in the following order: + + -s, --kernel-name + print the kernel name + + -n, --nodename + print the network node hostname + + -r, --kernel-release + print the kernel release + + -v, --kernel-version + print the kernel version + + -m, --machine + print the machine hardware name + + -p, --processor + print the processor type + + -i, --hardware-platform + print the hardware platform + + -o, --operating-system + print the operating system + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for uname is maintained as a Tex- + info manual. If the info and uname programs are prop- + erly installed at your site, the command + + info uname + + should give you access to the complete manual. + + + +uname 5.3.0 November 2004 UNAME(1) diff --git a/coreutils-5.3.0-bin/man/cat1/unexpand.1.txt b/coreutils-5.3.0-bin/man/cat1/unexpand.1.txt new file mode 100644 index 0000000..9d2c73b --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/unexpand.1.txt @@ -0,0 +1,66 @@ +UNEXPAND(1) User Commands UNEXPAND(1) + + + + + +NAME + unexpand - convert spaces to tabs + +SYNOPSIS + unexpand [OPTION]... [FILE]... + +DESCRIPTION + Convert blanks in each FILE to tabs, writing to standard + output. With no FILE, or when FILE is -, read standard + input. + + Mandatory arguments to long options are mandatory for + short options too. + + -a, --all + convert all blanks, instead of just initial + blanks + + --first-only convert only leading sequences of blanks + (overrides -a) + + -t, --tabs=N + have tabs N characters apart instead of 8 + (enables -a) + + -t, --tabs=LIST + use comma separated LIST of tab positions + (enables -a) + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + expand(1) + + The full documentation for unexpand is maintained as a + Texinfo manual. If the info and unexpand programs are + properly installed at your site, the command + + info unexpand + + should give you access to the complete manual. + + + +unexpand 5.3.0 November 2004 UNEXPAND(1) diff --git a/coreutils-5.3.0-bin/man/cat1/uniq.1.txt b/coreutils-5.3.0-bin/man/cat1/uniq.1.txt new file mode 100644 index 0000000..c4988db --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/uniq.1.txt @@ -0,0 +1,78 @@ +UNIQ(1) User Commands UNIQ(1) + + + + + +NAME + uniq - report or omit repeated lines + +SYNOPSIS + uniq [OPTION]... [INPUT [OUTPUT]] + +DESCRIPTION + Discard all but one of successive identical lines from + INPUT (or standard input), writing to OUTPUT (or stan- + dard output). + + Mandatory arguments to long options are mandatory for + short options too. + + -c, --count + prefix lines by the number of occurrences + + -d, --repeated + only print duplicate lines + + -D, --all-repeated[=delimit-method] print all duplicate + lines + delimit-method={none(default),prepend,separate} + Delimiting is done with blank lines. + + -f, --skip-fields=N + avoid comparing the first N fields + + -i, --ignore-case + ignore differences in case when comparing + + -s, --skip-chars=N + avoid comparing the first N characters + + -u, --unique + only print unique lines + + -w, --check-chars=N + compare no more than N characters in lines + + --help display this help and exit + + --version + output version information and exit + + A field is a run of whitespace, then non-whitespace + characters. Fields are skipped before chars. + +AUTHOR + Written by Richard Stallman and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for uniq is maintained as a Tex- + info manual. If the info and uniq programs are properly + installed at your site, the command + + info uniq + + should give you access to the complete manual. + + + +uniq 5.3.0 December 2004 UNIQ(1) diff --git a/coreutils-5.3.0-bin/man/cat1/unlink.1.txt b/coreutils-5.3.0-bin/man/cat1/unlink.1.txt new file mode 100644 index 0000000..3267e2b --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/unlink.1.txt @@ -0,0 +1,46 @@ +UNLINK(1) User Commands UNLINK(1) + + + + + +NAME + unlink - call the unlink function to remove the speci- + fied file + +SYNOPSIS + unlink FILE + unlink OPTION + +DESCRIPTION + Call the unlink function to remove the specified FILE. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Michael Stone. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for unlink is maintained as a + Texinfo manual. If the info and unlink programs are + properly installed at your site, the command + + info unlink + + should give you access to the complete manual. + + + +unlink 5.3.0 November 2004 UNLINK(1) diff --git a/coreutils-5.3.0-bin/man/cat1/uptime.1.txt b/coreutils-5.3.0-bin/man/cat1/uptime.1.txt new file mode 100644 index 0000000..16ddbbf --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/uptime.1.txt @@ -0,0 +1,49 @@ +UPTIME(1) User Commands UPTIME(1) + + + + + +NAME + uptime - tell how long the system has been running + +SYNOPSIS + uptime [OPTION]... [ FILE ] + +DESCRIPTION + Print the current time, the length of time the system + has been up, the number of users on the system, and the + average number of jobs in the run queue over the last 1, + 5 and 15 minutes. If FILE is not specified, use + /var/run/utmp. /var/log/wtmp as FILE is common. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Joseph Arceneaux, David MacKenzie, and Kaveh + Ghazi. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for uptime is maintained as a + Texinfo manual. If the info and uptime programs are + properly installed at your site, the command + + info uptime + + should give you access to the complete manual. + + + +uptime 5.3.0 November 2004 UPTIME(1) diff --git a/coreutils-5.3.0-bin/man/cat1/users.1.txt b/coreutils-5.3.0-bin/man/cat1/users.1.txt new file mode 100644 index 0000000..9146363 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/users.1.txt @@ -0,0 +1,47 @@ +USERS(1) User Commands USERS(1) + + + + + +NAME + users - print the user names of users currently logged + in to the current host + +SYNOPSIS + users [OPTION]... [ FILE ] + +DESCRIPTION + Output who is currently logged in according to FILE. If + FILE is not specified, use /var/run/utmp. /var/log/wtmp + as FILE is common. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Joseph Arceneaux and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for users is maintained as a Tex- + info manual. If the info and users programs are prop- + erly installed at your site, the command + + info users + + should give you access to the complete manual. + + + +users 5.3.0 November 2004 USERS(1) diff --git a/coreutils-5.3.0-bin/man/cat1/vdir.1.txt b/coreutils-5.3.0-bin/man/cat1/vdir.1.txt new file mode 100644 index 0000000..aaae259 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/vdir.1.txt @@ -0,0 +1,233 @@ +VDIR(1) User Commands VDIR(1) + + + + + +NAME + vdir - list directory contents + +SYNOPSIS + vdir [OPTION]... [FILE]... + +DESCRIPTION + List information about the FILEs (the current directory + by default). Sort entries alphabetically if none of + -cftuSUX nor --sort. + + Mandatory arguments to long options are mandatory for + short options too. + + -a, --all + do not ignore entries starting with . + + -A, --almost-all + do not list implied . and .. + + --author + with -l, print the author of each file + + -b, --escape + print octal escapes for nongraphic characters + + --block-size=SIZE + use SIZE-byte blocks + + -B, --ignore-backups + do not list implied entries ending with ~ + + -c with -lt: sort by, and show, ctime (time of last + modification of file status information) with -l: + show ctime and sort by name otherwise: sort by + ctime + + -C list entries by columns + + --color[=WHEN] + control whether color is used to distinguish file + types. WHEN may be `never', `always', or `auto' + + -d, --directory + list directory entries instead of contents, and + do not dereference symbolic links + + -D, --dired + generate output designed for Emacs' dired mode + + -f do not sort, enable -aU, disable -lst + + -F, --classify + append indicator (one of */=@|) to entries + + --format=WORD + across -x, commas -m, horizontal -x, long -l, + single-column -1, verbose -l, vertical -C + + --full-time + like -l --time-style=full-iso + + -g like -l, but do not list owner + + -G, --no-group + like -l, but do not list group + + -h, --human-readable + with -l, print sizes in human readable format + (e.g., 1K 234M 2G) + + --si likewise, but use powers of 1000 not 1024 + + -H, --dereference-command-line + follow symbolic links listed on the command line + + --dereference-command-line-symlink-to-dir + follow each command line symbolic link that + points to a directory + + --hide=PATTERN + do not list implied entries matching shell PAT- + TERN (overridden by -a or -A) + + --indicator-style=WORD append indicator with style WORD + to entry names: + none (default), classify (-F), file-type (-p) + + -i, --inode + with -l, print the index number of each file + + -I, --ignore=PATTERN + do not list implied entries matching shell PAT- + TERN + + -k like --block-size=1K + + -l use a long listing format + + -L, --dereference + when showing file information for a symbolic + link, show information for the file the link ref- + erences rather than for the link itself + + -m fill width with a comma separated list of entries + + -n, --numeric-uid-gid + like -l, but list numeric UIDs and GIDs + + -N, --literal + print raw entry names (don't treat e.g. control + characters specially) + + -o like -l, but do not list group information + + -p, --file-type + append indicator (one of /=@|) to entries + + -q, --hide-control-chars + print ? instead of non graphic characters + + --show-control-chars + show non graphic characters as-is (default unless + program is `ls' and output is a terminal) + + -Q, --quote-name + enclose entry names in double quotes + + --quoting-style=WORD + use quoting style WORD for entry names: literal, + locale, shell, shell-always, c, escape + + -r, --reverse + reverse order while sorting + + -R, --recursive + list subdirectories recursively + + -s, --size + with -l, print size of each file, in blocks + + -S sort by file size + + --sort=WORD + extension -X, none -U, size -S, time -t, version + -v, status -c, time -t, atime -u, access -u, use + -u + + --time=WORD + with -l, show time as WORD instead of modifica- + tion time: atime, access, use, ctime or status; + use specified time as sort key if --sort=time + + --time-style=STYLE + with -l, show times using style STYLE: full-iso, + long-iso, iso, locale, +FORMAT. FORMAT is inter- + preted like `date'; if FORMAT is FORMAT1<new- + line>FORMAT2, FORMAT1 applies to non-recent files + and FORMAT2 to recent files; if STYLE is prefixed + with `posix-', STYLE takes effect only outside + the POSIX locale + + -t sort by modification time + + -T, --tabsize=COLS + assume tab stops at each COLS instead of 8 + + -u with -lt: sort by, and show, access time with -l: + show access time and sort by name otherwise: sort + by access time + + -U do not sort; list entries in directory order + + -v sort by version + + -w, --width=COLS + assume screen width instead of current value + + -x list entries by lines instead of by columns + + -X sort alphabetically by entry extension + + -1 list one file per line + + --help display this help and exit + + --version + output version information and exit + + SIZE may be (or may be an integer optionally followed + by) one of following: kB 1000, K 1024, MB 1000*1000, M + 1024*1024, and so on for G, T, P, E, Z, Y. + + By default, color is not used to distinguish types of + files. That is equivalent to using --color=none. Using + the --color option without the optional WHEN argument is + equivalent to using --color=always. With --color=auto, + color codes are output only if standard output is con- + nected to a terminal (tty). + + Exit status is 0 if OK, 1 if minor problems, 2 if seri- + ous trouble. + +AUTHOR + Written by Richard Stallman and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for vdir is maintained as a Tex- + info manual. If the info and vdir programs are properly + installed at your site, the command + + info vdir + + should give you access to the complete manual. + + + +vdir 5.3.0 December 2004 VDIR(1) diff --git a/coreutils-5.3.0-bin/man/cat1/wc.1.txt b/coreutils-5.3.0-bin/man/cat1/wc.1.txt new file mode 100644 index 0000000..2038c23 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/wc.1.txt @@ -0,0 +1,62 @@ +WC(1) User Commands WC(1) + + + + + +NAME + wc - print the number of newlines, words, and bytes in + files + +SYNOPSIS + wc [OPTION]... [FILE]... + +DESCRIPTION + Print newline, word, and byte counts for each FILE, and + a total line if more than one FILE is specified. With + no FILE, or when FILE is -, read standard input. + + -c, --bytes + print the byte counts + + -m, --chars + print the character counts + + -l, --lines + print the newline counts + + -L, --max-line-length + print the length of the longest line + + -w, --words + print the word counts + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Paul Rubin and David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for wc is maintained as a Texinfo + manual. If the info and wc programs are properly + installed at your site, the command + + info wc + + should give you access to the complete manual. + + + +wc 5.3.0 November 2004 WC(1) diff --git a/coreutils-5.3.0-bin/man/cat1/who.1.txt b/coreutils-5.3.0-bin/man/cat1/who.1.txt new file mode 100644 index 0000000..1520566 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/who.1.txt @@ -0,0 +1,98 @@ +WHO(1) User Commands WHO(1) + + + + + +NAME + who - show who is logged on + +SYNOPSIS + who [OPTION]... [ FILE | ARG1 ARG2 ] + +DESCRIPTION + -a, --all + same as -b -d --login -p -r -t -T -u + + -b, --boot + time of last system boot + + -d, --dead + print dead processes + + -H, --heading + print line of column headings + + -i, --idle + add idle time as HOURS:MINUTES, . or old (depre- + cated, use -u) + + -l, --login + print system login processes + + --lookup + attempt to canonicalize hostnames via DNS + + -m only hostname and user associated with stdin + + -p, --process + print active processes spawned by init + + -q, --count + all login names and number of users logged on + + -r, --runlevel + print current runlevel + + -s, --short + print only name, line, and time (default) + + -t, --time + print last system clock change + + -T, -w, --mesg + add user's message status as +, - or ? + + -u, --users + list users logged in + + --message + same as -T + + --writable + same as -T + + --help display this help and exit + + --version + output version information and exit + + If FILE is not specified, use /var/run/utmp. + /var/log/wtmp as FILE is common. If ARG1 ARG2 given, -m + presumed: `am i' or `mom likes' are usual. + +AUTHOR + Written by Joseph Arceneaux, David MacKenzie, and + Michael Stone. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for who is maintained as a Tex- + info manual. If the info and who programs are properly + installed at your site, the command + + info who + + should give you access to the complete manual. + + + +who 5.3.0 November 2004 WHO(1) diff --git a/coreutils-5.3.0-bin/man/cat1/whoami.1.txt b/coreutils-5.3.0-bin/man/cat1/whoami.1.txt new file mode 100644 index 0000000..042e606 --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/whoami.1.txt @@ -0,0 +1,45 @@ +WHOAMI(1) User Commands WHOAMI(1) + + + + + +NAME + whoami - print effective userid + +SYNOPSIS + whoami [OPTION]... + +DESCRIPTION + Print the user name associated with the current effec- + tive user id. Same as id -un. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by Richard Mlynarik. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for whoami is maintained as a + Texinfo manual. If the info and whoami programs are + properly installed at your site, the command + + info whoami + + should give you access to the complete manual. + + + +whoami 5.3.0 November 2004 WHOAMI(1) diff --git a/coreutils-5.3.0-bin/man/cat1/yes.1.txt b/coreutils-5.3.0-bin/man/cat1/yes.1.txt new file mode 100644 index 0000000..14757bf --- /dev/null +++ b/coreutils-5.3.0-bin/man/cat1/yes.1.txt @@ -0,0 +1,46 @@ +YES(1) User Commands YES(1) + + + + + +NAME + yes - output a string repeatedly until killed + +SYNOPSIS + yes [STRING]... + yes OPTION + +DESCRIPTION + Repeatedly output a line with all specified STRING(s), + or `y'. + + --help display this help and exit + + --version + output version information and exit + +AUTHOR + Written by David MacKenzie. + +REPORTING BUGS + Report bugs to <bug-coreutils@gnu.org>. + +COPYRIGHT + Copyright (C) 2004 Free Software Foundation, Inc. + This is free software; see the source for copying condi- + tions. There is NO warranty; not even for MERCHANTABIL- + ITY or FITNESS FOR A PARTICULAR PURPOSE. + +SEE ALSO + The full documentation for yes is maintained as a Tex- + info manual. If the info and yes programs are properly + installed at your site, the command + + info yes + + should give you access to the complete manual. + + + +yes 5.3.0 December 2004 YES(1) |