1 GNU coreutils NEWS -*- outline -*-
3 * Major changes in release 5.90 (2005-09-29) [unstable]
5 ** Bring back support for `head -NUM', `tail -NUM', etc. even when
6 conforming to POSIX 1003.1-2001. The following changes apply only
7 when conforming to POSIX 1003.1-2001; there is no effect when
8 conforming to older POSIX versions.
10 The following usages now behave just as when conforming to older POSIX:
13 expand -TAB1[,TAB2,...]
19 join -o FIELD_NAME1 FIELD_NAME2...
24 tail -[NUM][bcl][f] [FILE]
26 The following usages no longer work, due to the above changes:
28 date -I TIMESPEC (use `date -ITIMESPEC' instead)
29 od -w WIDTH (use `od -wWIDTH' instead)
30 pr -S STRING (use `pr -SSTRING' instead)
32 A few usages still have behavior that depends on which POSIX standard is
33 being conformed to, and portable applications should beware these
34 problematic usages. These include:
36 Problematic Standard-conforming replacement, depending on
37 usage whether you prefer the behavior of:
38 POSIX 1003.2-1992 POSIX 1003.1-2001
39 sort +4 sort -k 5 sort ./+4
40 tail +4 tail -n +4 tail ./+4
41 tail - main.c tail main.c tail -- - main.c
42 tail -c 4 tail -c 10 ./4 tail -c4
43 touch 12312359 f touch -t 12312359 f touch ./12312359 f
44 uniq +4 uniq -s 4 uniq ./+4
46 These changes are in response to decisions taken in the January 2005
47 Austin Group standardization meeting. For more details, please see
48 "Utility Syntax Guidelines" in the Minutes of the January 2005
49 Meeting <http://www.opengroup.org/austin/docs/austin_239.html>.
51 ** Binary input and output are now implemented more consistently.
52 These changes affect only platforms like MS-DOS that distinguish
53 between binary and text files.
55 The following programs now always use text input/output:
59 The following programs now always use binary input/output to copy data:
63 The following programs now always use binary input/output to copy
64 data, except for stdin and stdout when it is a terminal.
67 (cat behaves similarly, unless one of the options -bensAE is used.)
69 cat's --binary or -B option has been removed. It existed only on
70 MS-DOS-like platforms, and didn't work as documented there.
72 md5sum and sha1sum now obey the -b or --binary option, even if
73 standard input is a terminal, and they no longer report files to be
74 binary if they actually read them in text mode.
76 ** Changes for better conformance to POSIX
78 cp, ln, mv, rm changes:
80 Leading white space is now significant in responses to yes-or-no questions.
81 For example, if "rm" asks "remove regular file `foo'?" and you respond
82 with " y" (i.e., space before "y"), it counts as "no".
86 On a QUIT or PIPE signal, dd now exits without printing statistics.
88 On hosts lacking the INFO signal, dd no longer treats the USR1
89 signal as if it were INFO when POSIXLY_CORRECT is set.
91 If the file F is non-seekable and contains fewer than N blocks,
92 then before copying "dd seek=N of=F" now extends F with zeroed
93 blocks until F contains N blocks.
97 When POSIXLY_CORRECT is set, "fold file -3" is now equivalent to
98 "fold file ./-3", not the obviously-erroneous "fold file ./-w3".
102 -p now marks only directories; it is equivalent to the new option
103 --indicator-style=slash. Use --file-type or
104 --indicator-style=file-type to get -p's old behavior.
108 Documentation and diagnostics now refer to "nicenesses" (commonly
109 in the range -20...19) rather than "nice values" (commonly 0...39).
113 nohup now ignores the umask when creating nohup.out.
115 nohup now closes stderr if it is a terminal and stdout is closed.
117 nohup now exits with status 127 (not 1) when given an invalid option.
121 It now rejects the empty name in the normal case. That is,
122 "pathchk -p ''" now fails, and "pathchk ''" fails unless the
123 current host (contra POSIX) allows empty file names.
125 The new -P option checks whether a file name component has leading "-",
126 as suggested in interpretation "Austin-039:XCU:pathchk:pathchk -p"
127 <http://www.opengroup.org/austin/interps/doc.tpl?gdid=6232>.
128 It also rejects the empty name even if the current host accepts it; see
129 <http://www.opengroup.org/austin/interps/doc.tpl?gdid=6233>.
131 The --portability option is now equivalent to -p -P.
135 chmod, mkdir, mkfifo, and mknod formerly mishandled rarely-used symbolic
136 permissions like =xX and =u, and did not properly diagnose some invalid
137 strings like g+gr, ug,+x, and +1. These bugs have been fixed.
139 csplit could produce corrupt output, given input lines longer than 8KB
141 dd now computes statistics using a realtime clock (if available)
142 rather than the time-of-day clock, to avoid glitches if the
143 time-of-day is changed while dd is running. Also, it avoids
144 using unsafe code in signal handlers; this fixes some core dumps.
146 expr and test now correctly compare integers of unlimited magnitude.
148 expr now detects integer overflow when converting strings to integers,
149 rather than silently wrapping around.
151 ls now refuses to generate time stamps containing more than 1000 bytes, to
152 foil potential denial-of-service attacks on hosts with very large stacks.
154 "mkdir -m =+x dir" no longer ignores the umask when evaluating "+x",
155 and similarly for mkfifo and mknod.
157 "mkdir -p /tmp/a/b dir" no longer attempts to create the `.'-relative
158 directory, dir (in /tmp/a), when, after creating /tmp/a/b, it is unable
159 to return to its initial working directory. Similarly for "install -D
162 "pr -D FORMAT" now accepts the same formats that "date +FORMAT" does.
164 stat now exits nonzero if a file operand does not exist
166 ** Improved robustness
168 Date no longer needs to allocate virtual memory to do its job,
169 so it can no longer fail due to an out-of-memory condition,
170 no matter how large the result.
172 ** Improved portability
174 hostid now prints exactly 8 hexadecimal digits, possibly with leading zeros,
175 and without any spurious leading "fff..." on 64-bit hosts.
177 nice now works on Darwin 7.7.0 in spite of its invalid definition of NZERO.
179 `rm -r' can remove all entries in a directory even when it is on a
180 file system for which readdir is buggy and that was not checked by
181 coreutils' old configure-time run-test.
183 sleep no longer fails when resumed after being suspended on linux-2.6.8.1,
184 in spite of that kernel's buggy nanosleep implementation.
188 chmod -w now complains if its behavior differs from what chmod a-w
189 would do, and similarly for chmod -r, chmod -x, etc.
191 cp and mv: the --reply=X option is deprecated
193 date accepts the new option --rfc-3339=TIMESPEC. The old --iso-8602 (-I)
194 option is deprecated; it still works, but new applications should avoid it.
195 date, du, ls, and pr's time formats now support new %:z, %::z, %:::z
196 specifiers for numeric time zone offsets like -07:00, -07:00:00, and -07.
198 dd has new iflag= and oflag= flags "binary" and "text", which have an
199 effect only on nonstandard platforms that distinguish text from binary I/O.
201 du accepts new options: --time[=TYPE] and --time-style=STYLE
203 join now supports a NUL field separator, e.g., "join -t '\0'".
204 join now detects and reports incompatible options, e.g., "join -t x -t y",
206 ls no longer outputs an extra space between the mode and the link count
207 when none of the listed files has an ACL.
209 md5sum --check now accepts multiple input files, and similarly for sha1sum.
211 If stdin is a terminal, nohup now redirects it from /dev/null to
212 prevent the command from tying up an OpenSSH session after you logout.
214 "rm -FOO" now suggests "rm ./-FOO" if the file "-FOO" exists and
215 "-FOO" is not a valid option.
217 stat -f -c %S outputs the fundamental block size (used for block counts).
218 stat -f's default output format has been changed to output this size as well.
219 stat -f recognizes file systems of type XFS and JFS
221 "touch -" now touches standard output, not a file named "-".
223 uname -a no longer generates the -p and -i outputs if they are unknown.
225 * Major changes in release 5.3.0 (2005-01-08) [unstable]
229 Several fixes to chgrp and chown for compatibility with POSIX and BSD:
231 Do not affect symbolic links by default.
232 Now, operate on whatever a symbolic link points to, instead.
233 To get the old behavior, use --no-dereference (-h).
235 --dereference now works, even when the specified owner
236 and/or group match those of an affected symlink.
238 Check for incompatible options. When -R and --dereference are
239 both used, then either -H or -L must also be used. When -R and -h
240 are both used, then -P must be in effect.
242 -H, -L, and -P have no effect unless -R is also specified.
243 If -P and -R are both specified, -h is assumed.
245 Do not optimize away the chown() system call when the file's owner
246 and group already have the desired value. This optimization was
247 incorrect, as it failed to update the last-changed time and reset
248 special permission bits, as POSIX requires.
250 "chown : file", "chown '' file", and "chgrp '' file" now succeed
251 without changing the uid or gid, instead of reporting an error.
253 Do not report an error if the owner or group of a
254 recursively-encountered symbolic link cannot be updated because
255 the file system does not support it.
257 chmod now accepts multiple mode-like options, e.g., "chmod -r -w f".
259 chown is no longer subject to a race condition vulnerability, when
260 used with --from=O:G and without the (-h) --no-dereference option.
262 cut's --output-delimiter=D option works with abutting byte ranges.
264 dircolors's documentation now recommends that shell scripts eval
265 "`dircolors`" rather than `dircolors`, to avoid shell expansion pitfalls.
267 du no longer segfaults when a subdirectory of an operand
268 directory is removed while du is traversing that subdirectory.
269 Since the bug was in the underlying fts.c module, it also affected
270 chown, chmod, and chgrp.
272 du's --exclude-from=FILE and --exclude=P options now compare patterns
273 against the entire name of each file, rather than against just the
276 echo now conforms to POSIX better. It supports the \0ooo syntax for
277 octal escapes, and \c now terminates printing immediately. If
278 POSIXLY_CORRECT is set and the first argument is not "-n", echo now
279 outputs all option-like arguments instead of treating them as options.
281 expand and unexpand now conform to POSIX better. They check for
282 blanks (which can include characters other than space and tab in
283 non-POSIX locales) instead of spaces and tabs. Unexpand now
284 preserves some blanks instead of converting them to tabs or spaces.
286 "ln x d/" now reports an error if d/x is a directory and x a file,
287 instead of incorrectly creating a link to d/x/x.
289 ls no longer segfaults on systems for which SIZE_MAX != (size_t) -1.
291 md5sum and sha1sum now report an error when given so many input
292 lines that their line counter overflows, instead of silently
293 reporting incorrect results.
297 If it fails to lower the niceness due to lack of permissions,
298 it goes ahead and runs the command anyway, as POSIX requires.
300 It no longer incorrectly reports an error if the current niceness
303 It no longer assumes that nicenesses range from -20 through 19.
305 It now consistently adjusts out-of-range nicenesses to the
306 closest values in range; formerly it sometimes reported an error.
308 pathchk no longer accepts trailing options, e.g., "pathchk -p foo -b"
309 now treats -b as a file name to check, not as an invalid option.
311 `pr --columns=N' was not equivalent to `pr -N' when also using
314 pr now supports page numbers up to 2**64 on most hosts, and it
315 detects page number overflow instead of silently wrapping around.
316 pr now accepts file names that begin with "+" so long as the rest of
317 the file name does not look like a page range.
319 printf has several changes:
321 It now uses 'intmax_t' (not 'long int') to format integers, so it
322 can now format 64-bit integers on most modern hosts.
324 On modern hosts it now supports the C99-inspired %a, %A, %F conversion
325 specs, the "'" and "0" flags, and the ll, j, t, and z length modifiers
326 (this is compatible with recent Bash versions).
328 The printf command now rejects invalid conversion specifications
329 like %#d, instead of relying on undefined behavior in the underlying
332 ptx now diagnoses invalid values for its --width=N (-w)
333 and --gap-size=N (-g) options.
335 mv (when moving between partitions) no longer fails when
336 operating on too many command-line-specified nonempty directories.
338 rm (without -f) no longer hangs when attempting to remove a symlink
339 to a file on an off-line NFS-mounted partition.
341 rm no longer gets a failed assertion under some unusual conditions.
343 rm no longer requires read access to the current directory.
345 "rm -r" would mistakenly fail to remove files under a directory
346 for some types of errors (e.g., read-only file system, I/O error)
347 when first encountering the directory.
351 "sort -o -" now writes to a file named "-" instead of to standard
352 output; POSIX requires this.
354 An unlikely race condition has been fixed where "sort" could have
355 mistakenly removed a temporary file belonging to some other process.
357 "sort" no longer has O(N**2) behavior when it creates many temporary files.
359 tac can now handle regular, nonseekable files like Linux's
360 /proc/modules. Before, it would produce no output for such a file.
362 tac would exit immediately upon I/O or temp-file creation failure.
363 Now it continues on, processing any remaining command line arguments.
365 "tail -f" no longer mishandles pipes and fifos. With no operands,
366 tail now ignores -f if standard input is a pipe, as POSIX requires.
367 When conforming to POSIX 1003.2-1992, tail now supports the SUSv2 b
368 modifier (e.g., "tail -10b file") and it handles some obscure cases
369 more correctly, e.g., "tail +cl" now reads the file "+cl" rather
370 than reporting an error, "tail -c file" no longer reports an error,
371 and "tail - file" no longer reads standard input.
373 tee now exits when it gets a SIGPIPE signal, as POSIX requires.
374 To get tee's old behavior, use the shell command "(trap '' PIPE; tee)".
375 Also, "tee -" now writes to standard output instead of to a file named "-".
377 "touch -- MMDDhhmm[yy] file" is now equivalent to
378 "touch MMDDhhmm[yy] file" even when conforming to pre-2001 POSIX.
380 tr no longer mishandles a second operand with leading "-".
382 who now prints user names in full instead of truncating them after 8 bytes.
384 The following commands now reject unknown options instead of
385 accepting them as operands, so that users are properly warned that
386 options may be added later. Formerly they accepted unknown options
387 as operands; e.g., "basename -a a" acted like "basename -- -a a".
389 basename dirname factor hostname link nohup sync unlink yes
393 For efficiency, `sort -m' no longer copies input to a temporary file
394 merely because the input happens to come from a pipe. As a result,
395 some relatively-contrived examples like `cat F | sort -m -o F - G'
396 are no longer safe, as `sort' might start writing F before `cat' is
397 done reading it. This problem cannot occur unless `-m' is used.
399 When outside the default POSIX locale, the 'who' and 'pinky'
400 commands now output time stamps like "2004-06-21 13:09" instead of
401 the traditional "Jun 21 13:09".
403 pwd now works even when run from a working directory whose name
404 is longer than PATH_MAX.
406 cp, install, ln, and mv have a new --no-target-directory (-T) option,
407 and -t is now a short name for their --target-directory option.
409 cp -pu and mv -u (when copying) now don't bother to update the
410 destination if the resulting time stamp would be no newer than the
411 preexisting time stamp. This saves work in the common case when
412 copying or moving multiple times to the same destination in a file
413 system with a coarse time stamp resolution.
415 cut accepts a new option, --complement, to complement the set of
416 selected bytes, characters, or fields.
418 dd now also prints the number of bytes transferred, the time, and the
419 transfer rate. The new "status=noxfer" operand suppresses this change.
421 dd has new conversions for the conv= option:
423 nocreat do not create the output file
424 excl fail if the output file already exists
425 fdatasync physically write output file data before finishing
426 fsync likewise, but also write metadata
428 dd has new iflag= and oflag= options with the following flags:
430 append append mode (makes sense for output file only)
431 direct use direct I/O for data
432 dsync use synchronized I/O for data
433 sync likewise, but also for metadata
434 nonblock use non-blocking I/O
435 nofollow do not follow symlinks
436 noctty do not assign controlling terminal from file
438 stty now provides support (iutf8) for setting UTF-8 input mode.
440 With stat, a specified format is no longer automatically newline terminated.
441 If you want a newline at the end of your output, append `\n' to the format
444 'df', 'du', and 'ls' now take the default block size from the
445 BLOCKSIZE environment variable if the BLOCK_SIZE, DF_BLOCK_SIZE,
446 DU_BLOCK_SIZE, and LS_BLOCK_SIZE environment variables are not set.
447 Unlike the other variables, though, BLOCKSIZE does not affect
448 values like 'ls -l' sizes that are normally displayed as bytes.
449 This new behavior is for compatibility with BSD.
451 du accepts a new option --files0-from=FILE, where FILE contains a
452 list of NUL-terminated file names.
454 Date syntax as used by date -d, date -f, and touch -d has been
457 Dates like `January 32' with out-of-range components are now rejected.
459 Dates can have fractional time stamps like 2004-02-27 14:19:13.489392193.
461 Dates can be entered via integer counts of seconds since 1970 when
462 prefixed by `@'. For example, `@321' represents 1970-01-01 00:05:21 UTC.
464 Time zone corrections can now separate hours and minutes with a colon,
465 and can follow standard abbreviations like "UTC". For example,
466 "UTC +0530" and "+05:30" are supported, and are both equivalent to "+0530".
468 Date values can now have leading TZ="..." assignments that override
469 the environment only while that date is being processed. For example,
470 the following shell command converts from Paris to New York time:
472 TZ="America/New_York" date --date='TZ="Europe/Paris" 2004-10-31 06:30'
474 `date' has a new option --iso-8601=ns that outputs
475 nanosecond-resolution time stamps.
477 echo -e '\xHH' now outputs a byte whose hexadecimal value is HH,
478 for compatibility with bash.
480 ls now exits with status 1 on minor problems, 2 if serious trouble.
482 ls has a new --hide=PATTERN option that behaves like
483 --ignore=PATTERN, except that it is overridden by -a or -A.
484 This can be useful for aliases, e.g., if lh is an alias for
485 "ls --hide='*~'", then "lh -A" lists the file "README~".
487 In the following cases POSIX allows the default GNU behavior,
488 so when POSIXLY_CORRECT is set:
490 false, printf, true, unlink, and yes all support --help and --option.
492 pr no longer depends on LC_TIME for the date format in non-POSIX locales.
493 printf supports \u, \U, \x.
494 tail supports two or more files when using the obsolete option syntax.
496 The usual `--' operand is now supported by chroot, hostid, hostname,
499 `od' now conforms to POSIX better, and is more compatible with BSD:
501 The older syntax "od [-abcdfilosx]... [FILE] [[+]OFFSET[.][b]]" now works
502 even without --traditional. This is a change in behavior if there
503 are one or two operands and the last one begins with +, or if
504 there are two operands and the latter one begins with a digit.
505 For example, "od foo 10" and "od +10" now treat the last operand as
506 an offset, not as a file name.
508 -h is no longer documented, and may be withdrawn in future versions.
509 Use -x or -t x2 instead.
511 -i is now equivalent to -t dI (not -t d2), and
512 -l is now equivalent to -t dL (not -t d4).
514 -s is now equivalent to -t d2. The old "-s[NUM]" or "-s NUM"
515 option has been renamed to "-S NUM".
517 The default output format is now -t oS, not -t o2, i.e., short int
518 rather than two-byte int. This makes a difference only on hosts like
519 Cray systems where the C short int type requires more than two bytes.
521 The stat option --filesystem has been renamed to --file-system, for
522 consistency with POSIX "file system" and with cp and du --one-file-system.
526 md5sum and sha1sum's undocumented --string option has been removed.
528 tail's undocumented --max-consecutive-size-changes option has been removed.
530 * Major changes in release 5.2.1 (2004-03-12) [stable]
534 mv could mistakenly fail to preserve hard links when moving two
535 or more arguments between partitions.
537 `cp --sparse=always F /dev/hdx' no longer tries to use lseek to create
538 holes in the destination.
540 nohup now sets the close-on-exec flag for its copy of the stderr file
541 descriptor. This avoids some nohup-induced hangs. For example, before
542 this change, if you ran `ssh localhost', then `nohup sleep 600 </dev/null &',
543 and then exited that remote shell, the ssh session would hang until the
544 10-minute sleep terminated. With the fixed nohup, the ssh session
545 terminates immediately.
547 `expr' now conforms to POSIX better:
549 Integers like -0 and 00 are now treated as zero.
551 The `|' operator now returns 0, not its first argument, if both
552 arguments are null or zero. E.g., `expr "" \| ""' now returns 0,
553 not the empty string.
555 The `|' and `&' operators now use short-circuit evaluation, e.g.,
556 `expr 1 \| 1 / 0' no longer reports a division by zero.
560 `chown user.group file' now has its traditional meaning even when
561 conforming to POSIX 1003.1-2001, so long as no user has a name
562 containing `.' that happens to equal `user.group'.
565 * Major changes in release 5.2.0 (2004-02-19) [stable]
572 * Major changes in release 5.1.3 (2004-02-08): candidate to become stable 5.2.0
576 `cp -d' now works as required even on systems like OSF V5.1 that
577 declare stat and lstat as `static inline' functions.
579 time stamps output by stat now include actual fractional seconds,
580 when available -- or .0000000 for files without that information.
582 seq no longer infloops when printing 2^31 or more numbers.
583 For reference, seq `echo 2^31|bc` > /dev/null takes about one hour
584 on a 1.6 GHz Athlon 2000 XP. Now it can output 2^53-1 numbers before
587 * Major changes in release 5.1.2 (2004-01-25):
591 rmdir -p exits with status 1 on error; formerly it sometimes exited
592 with status 0 when given more than one argument.
594 nohup now always exits with status 127 when it finds an error,
595 as POSIX requires; formerly it sometimes exited with status 1.
597 Several programs (including cut, date, dd, env, hostname, nl, pr,
598 stty, and tr) now always exit with status 1 when they find an error;
599 formerly they sometimes exited with status 2.
601 factor no longer reports a usage error if stdin has the wrong format.
603 paste no longer infloops on ppc systems (bug introduced in 5.1.1)
606 * Major changes in release 5.1.1 (2004-01-17):
608 ** Configuration option
610 You can select the default level of POSIX conformance at configure-time,
611 e.g., by ./configure DEFAULT_POSIX2_VERSION=199209
615 fold -s works once again on systems with differing sizes for int
616 and size_t (bug introduced in 5.1.0)
620 touch -r now specifies the origin for any relative times in the -d
621 operand, if both options are given. For example, "touch -r FOO -d
622 '-5 seconds' BAR" sets BAR's modification time to be five seconds
625 join: The obsolete options "-j1 FIELD", "-j2 FIELD", and
626 "-o LIST1 LIST2..." are no longer supported on POSIX 1003.1-2001 systems.
627 Portable scripts should use "-1 FIELD", "-2 FIELD", and
628 "-o LIST1,LIST2..." respectively. If join was compiled on a
629 POSIX 1003.1-2001 system, you may enable the old behavior
630 by setting _POSIX2_VERSION=199209 in your environment.
631 [This change was reverted in coreutils 5.3.1.]
634 * Major changes in release 5.1.0 (2003-12-21):
638 chgrp, chmod, and chown can now process (with -R) hierarchies of virtually
639 unlimited depth. Before, they would fail to operate on any file they
640 encountered with a relative name of length PATH_MAX (often 4096) or longer.
642 chgrp, chmod, chown, and rm accept the new options:
643 --preserve-root, --no-preserve-root (default)
645 chgrp and chown now accept POSIX-mandated -L, -H, and -P options
647 du can now process hierarchies of virtually unlimited depth.
648 Before, du was limited by the user's stack size and it would get a
649 stack overflow error (often a segmentation fault) when applied to
650 a hierarchy of depth around 30,000 or larger.
652 du works even when run from an inaccessible directory
654 du -D now dereferences all symlinks specified on the command line,
655 not just the ones that reference directories
657 du now accepts -P (--no-dereference), for compatibility with du
658 of NetBSD and for consistency with e.g., chown and chgrp
660 du's -H option will soon have the meaning required by POSIX
661 (--dereference-args, aka -D) rather then the current meaning of --si.
662 Now, using -H elicits a warning to that effect.
664 When given -l and similar options, ls now adjusts the output column
665 widths to fit the data, so that output lines are shorter and have
666 columns that line up better. This may adversely affect shell
667 scripts that expect fixed-width columns, but such shell scripts were
668 not portable anyway, even with old GNU ls where the columns became
669 ragged when a datum was too wide.
671 du accepts a new option, -0/--null, to make it produce NUL-terminated
676 printf, seq, tail, and sleep now parse floating-point operands
677 and options in the C locale. POSIX requires this for printf.
679 od -c -w9999999 no longer segfaults
681 csplit no longer reads from freed memory (dumping core on some systems)
683 csplit would mistakenly exhaust virtual memory in some cases
685 ls --width=N (for very large N) is no longer subject to an address
686 arithmetic bug that could result in bounds violations.
688 ls --width=N (with -x or -C) no longer allocates more space
689 (potentially much more) than necessary for a given directory.
691 dd `unblock' and `sync' may now be combined (e.g., dd conv=unblock,sync)
693 * Major changes in release 5.0.91 (2003-09-08):
697 date accepts a new option --rfc-2822, an alias for --rfc-822.
699 split accepts a new option -d or --numeric-suffixes.
701 cp, install, mv, and touch now preserve microsecond resolution on
702 file timestamps, on platforms that have the 'utimes' system call.
703 Unfortunately there is no system call yet to preserve file
704 timestamps to their full nanosecond resolution; microsecond
705 resolution is the best we can do right now.
707 sort now supports the zero byte (NUL) as a field separator; use -t '\0'.
708 The -t '' option, which formerly had no effect, is now an error.
710 sort option order no longer matters for the options -S, -d, -i, -o, and -t.
711 Stronger options override weaker, and incompatible options are diagnosed.
713 `sha1sum --check' now accepts the BSD format for SHA1 message digests
714 in addition to the BSD format for MD5 ones.
716 who -l now means `who --login', not `who --lookup', per POSIX.
717 who's -l option has been eliciting an unconditional warning about
718 this impending change since sh-utils-2.0.12 (April 2002).
722 Mistakenly renaming a file onto itself, e.g., via `mv B b' when `B' is
723 the same directory entry as `b' no longer destroys the directory entry
724 referenced by both `b' and `B'. Note that this would happen only on
725 file systems like VFAT where two different names may refer to the same
726 directory entry, usually due to lower->upper case mapping of file names.
727 Now, the above can happen only on file systems that perform name mapping and
728 that support hard links (stat.st_nlink > 1). This mitigates the problem
729 in two ways: few file systems appear to be affected (hpfs and ntfs are),
730 when the bug is triggered, mv no longer removes the last hard link to a file.
731 *** ATTENTION ***: if you know how to distinguish the following two cases
732 without writing to the file system in question, please let me know:
733 1) B and b refer to the same directory entry on a file system like NTFS
734 (B may well have a link count larger than 1)
735 2) B and b are hard links to the same file
737 stat no longer overruns a buffer for format strings ending in `%'
739 fold -s -wN would infloop for N < 8 with TABs in the input.
740 E.g., this would not terminate: printf 'a\t' | fold -w2 -s
742 `split -a0', although of questionable utility, is accepted once again.
744 `df DIR' used to hang under some conditions on OSF/1 5.1. Now it doesn't.
746 seq's --width (-w) option now works properly even when the endpoint
747 requiring the larger width is negative and smaller than the other endpoint.
749 seq's default step is 1, even if LAST < FIRST.
751 paste no longer mistakenly outputs 0xFF bytes for a nonempty input file
752 without a trailing newline.
754 `tail -n0 -f FILE' and `tail -c0 -f FILE' no longer perform what amounted
755 to a busy wait, rather than sleeping between iterations.
757 tail's long-undocumented --allow-missing option now elicits a warning
760 * Major changes in release 5.0.90 (2003-07-29):
764 sort is now up to 30% more CPU-efficient in some cases
766 `test' is now more compatible with Bash and POSIX:
768 `test -t', `test --help', and `test --version' now silently exit
769 with status 0. To test whether standard output is a terminal, use
770 `test -t 1'. To get help and version info for `test', use
771 `[ --help' and `[ --version'.
773 `test' now exits with status 2 (not 1) if there is an error.
775 wc count field widths now are heuristically adjusted depending on the input
776 size, if known. If only one count is printed, it is guaranteed to
777 be printed without leading spaces.
779 Previously, wc did not align the count fields if POSIXLY_CORRECT was set,
780 but POSIX did not actually require this undesirable behavior, so it
785 kill no longer tries to operate on argv[0] (introduced in 5.0.1)
786 Why wasn't this noticed? Although many tests use kill, none of
787 them made an effort to avoid using the shell's built-in kill.
789 `[' invoked with no arguments no longer evokes a segfault
791 rm without --recursive (aka -r or -R) no longer prompts regarding
792 unwritable directories, as required by POSIX.
794 uniq -c now uses a SPACE, not a TAB between the count and the
795 corresponding line, as required by POSIX.
797 expr now exits with status 2 if the expression is syntactically valid,
798 and with status 3 if an error occurred. POSIX requires this.
800 expr now reports trouble if string comparison fails due to a collation error.
802 split now generates suffixes properly on EBCDIC hosts.
804 split -a0 now works, as POSIX requires.
806 `sort --version' and `sort --help' fail, as they should
807 when their output is redirected to /dev/full.
809 `su --version > /dev/full' now fails, as it should.
811 ** Fewer arbitrary limitations
813 cut requires 97% less memory when very large field numbers or
814 byte offsets are specified.
817 * Major changes in release 5.0.1 (2003-07-15):
820 - new program: `[' (much like `test')
823 - head now accepts --lines=-N (--bytes=-N) to print all but the
824 N lines (bytes) at the end of the file
825 - md5sum --check now accepts the output of the BSD md5sum program, e.g.,
826 MD5 (f) = d41d8cd98f00b204e9800998ecf8427e
827 - date -d DATE can now parse a DATE string like May-23-2003
828 - chown: `.' is no longer recognized as a separator in the OWNER:GROUP
829 specifier on POSIX 1003.1-2001 systems. If chown *was not* compiled
830 on such a system, then it still accepts `.', by default. If chown
831 was compiled on a POSIX 1003.1-2001 system, then you may enable the
832 old behavior by setting _POSIX2_VERSION=199209 in your environment.
833 - chown no longer tries to preserve set-user-ID and set-group-ID bits;
834 on some systems, the chown syscall resets those bits, and previous
835 versions of the chown command would call chmod to restore the original,
836 pre-chown(2) settings, but that behavior is problematic.
837 1) There was a window whereby a malicious user, M, could subvert a
838 chown command run by some other user and operating on files in a
839 directory where M has write access.
840 2) Before (and even now, on systems with chown(2) that doesn't reset
841 those bits), an unwary admin. could use chown unwittingly to create e.g.,
842 a set-user-ID root copy of /bin/sh.
845 - chown --dereference no longer leaks a file descriptor per symlink processed
846 - `du /' once again prints the `/' on the last line
847 - split's --verbose option works once again [broken in 4.5.10 and 5.0]
848 - tail -f is no longer subject to a race condition that could make it
849 delay displaying the last part of a file that had stopped growing. That
850 bug could also make tail -f give an unwarranted `file truncated' warning.
851 - du no longer runs out of file descriptors unnecessarily
852 - df and `readlink --canonicalize' no longer corrupt the heap on
853 non-glibc, non-solaris systems
854 - `env -u UNSET_VARIABLE' no longer dumps core on non-glibc systems
855 - readlink's --canonicalize option now works on systems like Solaris that
856 lack the canonicalize_file_name function but do have resolvepath.
857 - mv now removes `a' in this example on all systems: touch a; ln a b; mv a b
858 This behavior is contrary to POSIX (which requires that the mv command do
859 nothing and exit successfully), but I suspect POSIX will change.
860 - date's %r format directive now honors locale settings
861 - date's `-' (no-pad) format flag now affects the space-padded-by-default
862 conversion specifiers, %e, %k, %l
863 - fmt now diagnoses invalid obsolescent width specifications like `-72x'
864 - fmt now exits nonzero when unable to open an input file
865 - tsort now fails when given an odd number of input tokens,
866 as required by POSIX. Before, it would act as if the final token
867 appeared one additional time.
869 ** Fewer arbitrary limitations
870 - tail's byte and line counts are no longer limited to OFF_T_MAX.
871 Now the limit is UINTMAX_MAX (usually 2^64).
872 - split can now handle --bytes=N and --lines=N with N=2^31 or more.
875 - `kill -t' now prints signal descriptions (rather than `?') on systems
876 like Tru64 with __sys_siglist but no strsignal function.
877 - stat.c now compiles on Ultrix systems
878 - sleep now works on AIX systems that lack support for clock_gettime
879 - rm now works around Darwin6.5's broken readdir function
880 Before `rm -rf DIR' would fail to remove all files in DIR
881 if there were more than 338.
883 * Major changes in release 5.0 (2003-04-02):
884 - false --help now exits nonzero
887 * printf no longer treats \x specially when POSIXLY_CORRECT is set
888 * printf avoids buffer overrun with format ending in a backslash and
889 * printf avoids buffer overrun with incomplete conversion specifier
890 * printf accepts multiple flags in a single conversion specifier
893 * seq no longer requires that a field width be specified
894 * seq no longer fails when given a field width of `0'
895 * seq now accepts ` ' and `'' as valid format flag characters
896 * df now shows a HOSTNAME: prefix for each remote-mounted file system on AIX 5.1
897 * portability tweaks for HP-UX, AIX 5.1, DJGPP
900 * printf no longer segfaults for a negative field width or precision
901 * shred now always enables --exact for non-regular files
902 * du no longer lists hard-linked files more than once
903 * du no longer dumps core on some systems due to `infinite' recursion
904 via nftw's use of the buggy replacement function in getcwd.c
905 * portability patches for a few vendor compilers and 64-bit systems
906 * du -S *really* now works like it did before the change in 4.5.5
909 * du no longer truncates file sizes or sums to fit in 32-bit size_t
910 * work around Linux kernel bug in getcwd (fixed in 2.4.21-pre4), so that pwd
911 now fails if the name of the working directory is so long that getcwd
912 truncates it. Before it would print the truncated name and exit successfully.
913 * `df /some/mount-point' no longer hangs on a GNU libc system when another
914 hard-mounted NFS file system (preceding /some/mount-point in /proc/mounts)
916 * rm -rf now gives an accurate diagnostic when failing to remove a file
917 under certain unusual conditions
918 * mv and `cp --preserve=links' now preserve multiple hard links even under
919 certain unusual conditions where they used to fail
922 * du -S once again works like it did before the change in 4.5.5
923 * stat accepts a new file format, %B, for the size of each block reported by %b
924 * du accepts new option: --apparent-size
925 * du --bytes (-b) works the same way it did in fileutils-3.16 and before
926 * du reports proper sizes for directories (not zero) (broken in 4.5.6 or 4.5.7)
927 * df now always displays under `Filesystem', the device file name
928 corresponding to the listed mount point. Before, for a block- or character-
929 special file command line argument, df would display that argument. E.g.,
930 `df /dev/hda' would list `/dev/hda' as the `Filesystem', rather than say
931 /dev/hda3 (the device on which `/' is mounted), as it does now.
932 * test now works properly when invoked from a set user ID or set group ID
933 context and when testing access to files subject to alternate protection
934 mechanisms. For example, without this change, a set-UID program that invoked
935 `test -w F' (to see if F is writable) could mistakenly report that it *was*
936 writable, even though F was on a read-only file system, or F had an ACL
937 prohibiting write access, or F was marked as immutable.
940 * du would fail with more than one DIR argument when any but the last did not
941 contain a slash (due to a bug in ftw.c)
944 * du no longer segfaults on Solaris systems (fixed heap-corrupting bug in ftw.c)
945 * du --exclude=FILE works once again (this was broken by the rewrite for 4.5.5)
946 * du no longer gets a failed assertion for certain hierarchy lay-outs
947 involving hard-linked directories
948 * `who -r' no longer segfaults when using non-C-locale messages
949 * df now displays a mount point (usually `/') for non-mounted
950 character-special and block files
953 * ls --dired produces correct byte offset for file names containing
954 nonprintable characters in a multibyte locale
955 * du has been rewritten to use a variant of GNU libc's ftw.c
956 * du now counts the space associated with a directory's directory entry,
957 even if it cannot list or chdir into that subdirectory.
958 * du -S now includes the st_size of each entry corresponding to a subdirectory
959 * rm on FreeBSD can once again remove directories from NFS-mounted file systems
960 * ls has a new option --dereference-command-line-symlink-to-dir, which
961 corresponds to the new default behavior when none of -d, -l -F, -H, -L
963 * ls dangling-symlink now prints `dangling-symlink'.
964 Before, it would fail with `no such file or directory'.
965 * ls -s symlink-to-non-dir and ls -i symlink-to-non-dir now print
966 attributes of `symlink', rather than attributes of their referents.
967 * Fix a bug introduced in 4.5.4 that made it so that ls --color would no
968 longer highlight the names of files with the execute bit set when not
969 specified on the command line.
970 * shred's --zero (-z) option no longer gobbles up any following argument.
971 Before, `shred --zero file' would produce `shred: missing file argument',
972 and worse, `shred --zero f1 f2 ...' would appear to work, but would leave
973 the first file untouched.
974 * readlink: new program
975 * cut: new feature: when used to select ranges of byte offsets (as opposed
976 to ranges of fields) and when --output-delimiter=STRING is specified,
977 output STRING between ranges of selected bytes.
978 * rm -r can no longer be tricked into mistakenly reporting a cycle.
979 * when rm detects a directory cycle, it no longer aborts the entire command,
980 but rather merely stops processing the affected command line argument.
983 * cp no longer fails to parse options like this: --preserve=mode,ownership
984 * `ls --color -F symlink-to-dir' works properly
985 * ls is much more efficient on directories with valid dirent.d_type.
986 * stty supports all baud rates defined in linux-2.4.19.
987 * `du symlink-to-dir/' would improperly remove the trailing slash
988 * `du ""' would evoke a bounds violation.
989 * In the unlikely event that running `du /' resulted in `stat ("/", ...)'
990 failing, du would give a diagnostic about `' (empty string) rather than `/'.
991 * printf: a hexadecimal escape sequence has at most two hex. digits, not three.
992 * The following features have been added to the --block-size option
993 and similar environment variables of df, du, and ls.
994 - A leading "'" generates numbers with thousands separators.
996 $ ls -l --block-size="'1" file
997 -rw-rw-r-- 1 eggert src 47,483,707 Sep 24 23:40 file
998 - A size suffix without a leading integer generates a suffix in the output.
1000 $ ls -l --block-size="K"
1001 -rw-rw-r-- 1 eggert src 46371K Sep 24 23:40 file
1002 * ls's --block-size option now affects file sizes in all cases, not
1003 just for --block-size=human-readable and --block-size=si. Fractional
1004 sizes are now always rounded up, for consistency with df and du.
1005 * df now displays the block size using powers of 1000 if the requested
1006 block size seems to be a multiple of a power of 1000.
1007 * nl no longer gets a segfault when run like this `yes|nl -s%n'
1010 * du --dereference-args (-D) no longer fails in certain cases
1011 * `ln --target-dir=DIR' no longer fails when given a single argument
1014 * `rm -i dir' (without --recursive (-r)) no longer recurses into dir
1015 * `tail -c N FILE' now works with files of size >= 4GB
1016 * `mkdir -p' can now create very deep (e.g. 40,000-component) directories
1017 * rmdir -p dir-with-trailing-slash/ no longer fails
1018 * printf now honors the `--' command line delimiter
1019 * od's 8-byte formats x8, o8, and u8 now work
1020 * tail now accepts fractional seconds for its --sleep-interval=S (-s) option
1023 * du and ls now report sizes of symbolic links (before they'd always report 0)
1024 * uniq now obeys the LC_COLLATE locale, as per POSIX 1003.1-2001 TC1.
1026 ========================================================================
1027 Here are the NEWS entries made from fileutils-4.1 until the
1028 point at which the packages merged to form the coreutils:
1031 * `rm symlink-to-unwritable' doesn't prompt [introduced in 4.1.10]
1033 * rm once again gives a reasonable diagnostic when failing to remove a file
1034 owned by someone else in a sticky directory [introduced in 4.1.9]
1035 * df now rounds all quantities up, as per POSIX.
1036 * New ls time style: long-iso, which generates YYYY-MM-DD HH:MM.
1037 * Any time style can be preceded by "posix-"; this causes "ls" to
1038 use traditional timestamp format when in the POSIX locale.
1039 * The default time style is now posix-long-iso instead of posix-iso.
1040 Set TIME_STYLE="posix-iso" to revert to the behavior of 4.1.1 thru 4.1.9.
1041 * `rm dangling-symlink' doesn't prompt [introduced in 4.1.9]
1042 * stat: remove support for --secure/-s option and related %S and %C format specs
1043 * stat: rename --link/-l to --dereference/-L.
1044 The old options will continue to work for a while.
1046 * rm can now remove very deep hierarchies, in spite of any limit on stack size
1047 * new programs: link, unlink, and stat
1048 * New ls option: --author (for the Hurd).
1049 * `touch -c no-such-file' no longer fails, per POSIX
1051 * mv no longer mistakenly creates links to preexisting destination files
1054 * rm: close a hole that would allow a running rm process to be subverted
1056 * New cp option: --copy-contents.
1057 * cp -r is now equivalent to cp -R. Use cp -R -L --copy-contents to get the
1058 traditional (and rarely desirable) cp -r behavior.
1059 * ls now accepts --time-style=+FORMAT, where +FORMAT works like date's format
1060 * The obsolete usage `touch [-acm] MMDDhhmm[YY] FILE...' is no longer
1061 supported on systems conforming to POSIX 1003.1-2001. Use touch -t instead.
1062 * cp and inter-partition mv no longer give a misleading diagnostic in some
1065 * cp -r no longer preserves symlinks
1066 * The block size notation is now compatible with SI and with IEC 60027-2.
1067 For example, --block-size=1MB now means --block-size=1000000,
1068 whereas --block-size=1MiB now means --block-size=1048576.
1069 A missing `B' (e.g. `1M') has the same meaning as before.
1070 A trailing `B' now means decimal, not binary; this is a silent change.
1071 The nonstandard `D' suffix (e.g. `1MD') is now obsolescent.
1072 * -H or --si now outputs the trailing 'B', for consistency with the above.
1073 * Programs now output trailing 'K' (not 'k') to mean 1024, as per IEC 60027-2.
1074 * New df, du short option -B is short for --block-size.
1075 * You can omit an integer `1' before a block size suffix,
1076 e.g. `df -BG' is equivalent to `df -B 1G' and to `df --block-size=1G'.
1077 * The following options are now obsolescent, as their names are
1078 incompatible with IEC 60027-2:
1079 df, du: -m or --megabytes (use -BM or --block-size=1M)
1080 df, du, ls: --kilobytes (use --block-size=1K)
1082 * df --local no longer lists smbfs file systems whose name starts with //
1083 * dd now detects the Linux/tape/lseek bug at run time and warns about it.
1085 * ls -R once again outputs a blank line between per-directory groups of files.
1086 This was broken by the cycle-detection change in 4.1.1.
1087 * dd once again uses `lseek' on character devices like /dev/mem and /dev/kmem.
1088 On systems with the linux kernel (at least up to 2.4.16), dd must still
1089 resort to emulating `skip=N' behavior using reads on tape devices, because
1090 lseek has no effect, yet appears to succeed. This may be a kernel bug.
1092 * cp no longer fails when two or more source files are the same;
1093 now it just gives a warning and doesn't copy the file the second time.
1094 E.g., cp a a d/ produces this:
1095 cp: warning: source file `a' specified more than once
1096 * chmod would set the wrong bit when given symbolic mode strings like
1097 these: g=o, o=g, o=u. E.g., `chmod a=,o=w,ug=o f' would give a mode
1098 of --w-r---w- rather than --w--w--w-.
1100 * mv (likewise for cp), now fails rather than silently clobbering one of
1101 the source files in the following example:
1102 rm -rf a b c; mkdir a b c; touch a/f b/f; mv a/f b/f c
1103 * ls -R detects directory cycles, per POSIX. It warns and doesn't infloop.
1104 * cp's -P option now means the same as --no-dereference, per POSIX.
1105 Use --parents to get the old meaning.
1106 * When copying with the -H and -L options, cp can preserve logical
1107 links between source files with --preserve=links
1108 * cp accepts new options:
1109 --preserve[={mode,ownership,timestamps,links,all}]
1110 --no-preserve={mode,ownership,timestamps,links,all}
1111 * cp's -p and --preserve options remain unchanged and are equivalent
1112 to `--preserve=mode,ownership,timestamps'
1113 * mv and cp accept a new option: --reply={yes,no,query}; provides a consistent
1114 mechanism to control whether one is prompted about certain existing
1115 destination files. Note that cp's and mv's -f options don't have the
1116 same meaning: cp's -f option no longer merely turns off `-i'.
1117 * remove portability limitations (e.g., PATH_MAX on the Hurd, fixes for
1119 * mv now prompts before overwriting an existing, unwritable destination file
1120 when stdin is a tty, unless --force (-f) is specified, as per POSIX.
1121 * mv: fix the bug whereby `mv -uf source dest' would delete source,
1122 even though it's older than dest.
1123 * chown's --from=CURRENT_OWNER:CURRENT_GROUP option now works
1124 * cp now ensures that the set-user-ID and set-group-ID bits are cleared for
1125 the destination file when when copying and not preserving permissions.
1126 * `ln -f --backup k k' gives a clearer diagnostic
1127 * ls no longer truncates user names or group names that are longer
1129 * ls's new --dereference-command-line option causes it to dereference
1130 symbolic links on the command-line only. It is the default unless
1131 one of the -d, -F, or -l options are given.
1132 * ls -H now means the same as ls --dereference-command-line, as per POSIX.
1133 * ls -g now acts like ls -l, except it does not display owner, as per POSIX.
1134 * ls -n now implies -l, as per POSIX.
1135 * ls can now display dates and times in one of four time styles:
1137 - The `full-iso' time style gives full ISO-style time stamps like
1138 `2001-05-14 23:45:56.477817180 -0700'.
1139 - The 'iso' time style gives ISO-style time stamps like '2001-05-14 '
1141 - The 'locale' time style gives locale-dependent time stamps like
1142 'touko 14 2001' and 'touko 14 23:45' (in a Finnish locale).
1143 - The 'posix-iso' time style gives traditional POSIX-locale
1144 time stamps like 'May 14 2001' and 'May 14 23:45' unless the user
1145 specifies a non-POSIX locale, in which case it uses ISO-style dates.
1146 This is the default.
1148 You can specify a time style with an option like --time-style='iso'
1149 or with an environment variable like TIME_STYLE='iso'. GNU Emacs 21
1150 and later can parse ISO dates, but older Emacs versions cannot, so
1151 if you are using an older version of Emacs outside the default POSIX
1152 locale, you may need to set TIME_STYLE="locale".
1154 * --full-time is now an alias for "-l --time-style=full-iso".
1157 ========================================================================
1158 Here are the NEWS entries made from sh-utils-2.0 until the
1159 point at which the packages merged to form the coreutils:
1162 * date no longer accepts e.g., September 31 in the MMDDhhmm syntax
1163 * fix a bug in this package's .m4 files and in configure.ac
1165 * nohup's behavior is changed as follows, to conform to POSIX 1003.1-2001:
1166 - nohup no longer adjusts scheduling priority; use "nice" for that.
1167 - nohup now redirects stderr to stdout, if stderr is not a terminal.
1168 - nohup exit status is now 126 if command was found but not invoked,
1169 127 if nohup failed or if command was not found.
1171 * uname and uptime work better on *BSD systems
1172 * pathchk now exits nonzero for a path with a directory component
1173 that specifies a non-directory
1176 * who accepts new options: --all (-a), --boot (-b), --dead (-d), --login,
1177 --process (-p), --runlevel (-r), --short (-s), --time (-t), --users (-u).
1178 The -u option now produces POSIX-specified results and is the same as
1179 the long option `--users'. --idle is no longer the same as -u.
1180 * The following changes apply on systems conforming to POSIX 1003.1-2001:
1181 - `date -I' is no longer supported. Instead, use `date --iso-8601'.
1182 - `nice -NUM' is no longer supported. Instead, use `nice -n NUM'.
1183 [This change was reverted in coreutils 5.3.1.]
1184 * New 'uname' options -i or --hardware-platform, and -o or --operating-system.
1185 'uname -a' now outputs -i and -o information at the end.
1186 New uname option --kernel-version is an alias for -v.
1187 Uname option --release has been renamed to --kernel-release,
1188 and --sysname has been renamed to --kernel-name;
1189 the old options will work for a while, but are no longer documented.
1190 * 'expr' now uses the LC_COLLATE locale for string comparison, as per POSIX.
1191 * 'expr' now requires '+' rather than 'quote' to quote tokens;
1192 this removes an incompatibility with POSIX.
1193 * date -d 'last friday' would print a date/time that was one hour off
1194 (e.g., 23:00 on *thursday* rather than 00:00 of the preceding friday)
1195 when run such that the current time and the target date/time fall on
1196 opposite sides of a daylight savings time transition.
1197 This problem arose only with relative date strings like `last monday'.
1198 It was not a problem with strings that include absolute dates.
1199 * factor is twice as fast, for large numbers
1201 * setting the date now works properly, even when using -u
1202 * `date -f - < /dev/null' no longer dumps core
1203 * some DOS/Windows portability changes
1205 * `date -d DATE' now parses certain relative DATEs correctly
1207 * fixed a bug introduced in 2.0h that made many programs fail with a
1208 `write error' when invoked with the --version option
1210 * all programs fail when printing --help or --version output to a full device
1211 * printf exits nonzero upon write failure
1212 * yes now detects and terminates upon write failure
1213 * date --rfc-822 now always emits day and month names from the `C' locale
1214 * portability tweaks for Solaris8, Ultrix, and DOS
1216 * date now handles two-digit years with leading zeros correctly.
1217 * printf interprets unicode, \uNNNN \UNNNNNNNN, on systems with the
1218 required support; from Bruno Haible.
1219 * stty's rprnt attribute now works on HPUX 10.20
1220 * seq's --equal-width option works more portably
1222 * fix build problems with ut_name vs. ut_user
1224 * stty: fix long-standing bug that caused test failures on at least HPUX
1225 systems when COLUMNS was set to zero
1226 * still more portability fixes
1227 * unified lib/: now that directory and most of the configuration framework
1228 is common between fileutils, textutils, and sh-utils
1230 * fix portability problem with sleep vs lib/strtod.c's requirement for -lm
1232 * fix portability problems with nanosleep.c and with the new code in sleep.c
1234 * Regenerate lib/Makefile.in so that nanosleep.c is distributed.
1236 * sleep accepts floating point arguments on command line
1237 * sleep's clock continues counting down when sleep is suspended
1238 * when a suspended sleep process is resumed, it continues sleeping if
1239 there is any time remaining
1240 * who once again prints whatever host information it has, even without --lookup
1242 ========================================================================
1243 For older NEWS entries for the fileutils, textutils, and sh-utils
1244 packages, see ./old/*/NEWS.
1246 This package began as the union of the following:
1247 textutils-2.1, fileutils-4.1.11, sh-utils-2.0.15.