1GNU coreutils NEWS -*- outline -*- 2 3* Noteworthy changes in release 8.4 (2010-01-13) [stable] 4 5** Bug fixes 6 7 nproc --all is now guaranteed to be as large as the count 8 of available processors, which may not have been the case 9 on GNU/Linux systems with neither /proc nor /sys available. 10 [bug introduced in coreutils-8.1] 11 12** Build-related 13 14 Work around a build failure when using buggy <sys/capability.h>. 15 Alternatively, configure with --disable-libcap. 16 17 Compilation would fail on systems using glibc-2.7..2.9 due to changes in 18 gnulib's wchar.h that tickled a bug in at least those versions of glibc's 19 own <wchar.h> header. Now, gnulib works around the bug in those older 20 glibc <wchar.h> headers. 21 22 Building would fail with a link error (cp/copy.o) when XATTR headers 23 were installed without the corresponding library. Now, configure 24 detects that and disables xattr support, as one would expect. 25 26 27* Noteworthy changes in release 8.3 (2010-01-07) [stable] 28 29** Bug fixes 30 31 cp -p, install -p, mv, and touch -c could trigger a spurious error 32 message when using new glibc coupled with an old kernel. 33 [bug introduced in coreutils-6.12]. 34 35 ls -l --color no longer prints "argetm" in front of dangling 36 symlinks when the 'LINK target' directive was given to dircolors. 37 [bug introduced in fileutils-4.0] 38 39 pr's page header was improperly formatted for long file names. 40 [bug introduced in coreutils-7.2] 41 42 rm -r --one-file-system works once again. 43 The rewrite to make rm use fts introduced a regression whereby 44 a commmand of the above form would fail for all subdirectories. 45 [bug introduced in coreutils-8.0] 46 47 stat -f recognizes more file system types: k-afs, fuseblk, gfs/gfs2, ocfs2, 48 and rpc_pipefs. Also Minix V3 is displayed correctly as minix3, not minux3. 49 [bug introduced in coreutils-8.1] 50 51 tail -f (inotify-enabled) once again works with remote files. 52 The use of inotify with remote files meant that any changes to those 53 files that was not done from the local system would go unnoticed. 54 [bug introduced in coreutils-7.5] 55 56 tail -F (inotify-enabled) would abort when a tailed file is repeatedly 57 renamed-aside and then recreated. 58 [bug introduced in coreutils-7.5] 59 60 tail -F (inotify-enabled) could fail to follow renamed files. 61 E.g., given a "tail -F a b" process, running "mv a b" would 62 make tail stop tracking additions to "b". 63 [bug introduced in coreutils-7.5] 64 65 touch -a and touch -m could trigger bugs in some file systems, such 66 as xfs or ntfs-3g, and fail to update timestamps. 67 [bug introduced in coreutils-8.1] 68 69 wc now prints counts atomically so that concurrent 70 processes will not intersperse their output. 71 [the issue dates back to the initial implementation] 72 73 74* Noteworthy changes in release 8.2 (2009-12-11) [stable] 75 76** Bug fixes 77 78 id's use of mgetgroups no longer writes beyond the end of a malloc'd buffer 79 [bug introduced in coreutils-8.1] 80 81 id no longer crashes on systems without supplementary group support. 82 [bug introduced in coreutils-8.1] 83 84 rm once again handles zero-length arguments properly. 85 The rewrite to make rm use fts introduced a regression whereby 86 a command like "rm a '' b" would fail to remove "a" and "b", due to 87 the presence of the empty string argument. 88 [bug introduced in coreutils-8.0] 89 90 sort is now immune to the signal handling of its parent. 91 Specifically sort now doesn't exit with an error message 92 if it uses helper processes for compression and its parent 93 ignores CHLD signals. [bug introduced in coreutils-6.9] 94 95 tail without -f no longer access uninitialized memory 96 [bug introduced in coreutils-7.6] 97 98 timeout is now immune to the signal handling of its parent. 99 Specifically timeout now doesn't exit with an error message 100 if its parent ignores CHLD signals. [bug introduced in coreutils-7.6] 101 102 a user running "make distcheck" in the coreutils source directory, 103 with TMPDIR unset or set to the name of a world-writable directory, 104 and with a malicious user on the same system 105 was vulnerable to arbitrary code execution 106 [bug introduced in coreutils-5.0] 107 108 109* Noteworthy changes in release 8.1 (2009-11-18) [stable] 110 111** Bug fixes 112 113 chcon no longer exits immediately just because SELinux is disabled. 114 Even then, chcon may still be useful. 115 [bug introduced in coreutils-8.0] 116 117 chcon, chgrp, chmod, chown and du now diagnose an ostensible directory cycle 118 and arrange to exit nonzero. Before, they would silently ignore the 119 offending directory and all "contents." 120 121 env -u A=B now fails, rather than silently adding A to the 122 environment. Likewise, printenv A=B silently ignores the invalid 123 name. [the bugs date back to the initial implementation] 124 125 ls --color now handles files with capabilities correctly. Previously 126 files with capabilities were often not colored, and also sometimes, files 127 without capabilites were colored in error. [bug introduced in coreutils-7.0] 128 129 md5sum now prints checksums atomically so that concurrent 130 processes will not intersperse their output. 131 This also affected sum, sha1sum, sha224sum, sha384sum and sha512sum. 132 [the bug dates back to the initial implementation] 133 134 mktemp no longer leaves a temporary file behind if it was unable to 135 output the name of the file to stdout. 136 [the bug dates back to the initial implementation] 137 138 nice -n -1 PROGRAM now runs PROGRAM even when its internal setpriority 139 call fails with errno == EACCES. 140 [the bug dates back to the initial implementation] 141 142 nice, nohup, and su now refuse to execute the subsidiary program if 143 they detect write failure in printing an otherwise non-fatal warning 144 message to stderr. 145 146 stat -f recognizes more file system types: afs, cifs, anon-inode FS, 147 btrfs, cgroupfs, cramfs-wend, debugfs, futexfs, hfs, inotifyfs, minux3, 148 nilfs, securityfs, selinux, xenfs 149 150 tail -f (inotify-enabled) now avoids a race condition. 151 Before, any data appended in the tiny interval between the initial 152 read-to-EOF and the inotify watch initialization would be ignored 153 initially (until more data was appended), or forever, if the file 154 were first renamed or unlinked or never modified. 155 [The race was introduced in coreutils-7.5] 156 157 tail -F (inotify-enabled) now consistently tails a file that has been 158 replaced via renaming. That operation provokes either of two sequences 159 of inotify events. The less common sequence is now handled as well. 160 [The bug came with the implementation change in coreutils-7.5] 161 162 timeout now doesn't exit unless the command it is monitoring does, 163 for any specified signal. [bug introduced in coreutils-7.0]. 164 165** Changes in behavior 166 167 chroot, env, nice, and su fail with status 125, rather than 1, on 168 internal error such as failure to parse command line arguments; this 169 is for consistency with stdbuf and timeout, and avoids ambiguity 170 with the invoked command failing with status 1. Likewise, nohup 171 fails with status 125 instead of 127. 172 173 du (due to a change in gnulib's fts) can now traverse NFSv4 automounted 174 directories in which the stat'd device number of the mount point differs 175 during a traversal. Before, it would fail, because such a mismatch would 176 usually represent a serious error or a subversion attempt. 177 178 echo and printf now interpret \e as the Escape character (0x1B). 179 180 rm -f /read-only-fs/nonexistent now succeeds and prints no diagnostic 181 on systems with an unlinkat syscall that sets errno to EROFS in that case. 182 Before, it would fail with a "Read-only file system" diagnostic. 183 Also, "rm /read-only-fs/nonexistent" now reports "file not found" rather 184 than the less precise "Read-only file system" error. 185 186** New programs 187 188 nproc: Print the number of processing units available to a process. 189 190** New features 191 192 env and printenv now accept the option --null (-0), as a means to 193 avoid ambiguity with newlines embedded in the environment. 194 195 md5sum --check now also accepts openssl-style checksums. 196 So do sha1sum, sha224sum, sha384sum and sha512sum. 197 198 mktemp now accepts the option --suffix to provide a known suffix 199 after the substitution in the template. Additionally, uses such as 200 "mktemp fileXXXXXX.txt" are able to infer an appropriate --suffix. 201 202 touch now accepts the option --no-dereference (-h), as a means to 203 change symlink timestamps on platforms with enough support. 204 205 206* Noteworthy changes in release 8.0 (2009-10-06) [beta] 207 208** Bug fixes 209 210 cp --preserve=xattr and --archive now preserve extended attributes even 211 when the source file doesn't have write access. 212 [bug introduced in coreutils-7.1] 213 214 touch -t [[CC]YY]MMDDhhmm[.ss] now accepts a timestamp string ending in .60, 215 to accommodate leap seconds. 216 [the bug dates back to the initial implementation] 217 218 ls --color now reverts to the color of a base file type consistently 219 when the color of a more specific type is disabled. 220 [bug introduced in coreutils-5.90] 221 222 ls -LR exits with status 2, not 0, when it encounters a cycle 223 224 ls -is is now consistent with ls -lis in ignoring values returned 225 from a failed stat/lstat. For example ls -Lis now prints "?", not "0", 226 for the inode number and allocated size of a dereferenced dangling symlink. 227 228 tail --follow --pid now avoids a race condition where data written 229 just before the process dies might not have been output by tail. 230 Also, tail no longer delays at all when the specified pid is not live. 231 [The race was introduced in coreutils-7.5, 232 and the unnecessary delay was present since textutils-1.22o] 233 234** Portability 235 236 On Solaris 9, many commands would mistakenly treat file/ the same as 237 file. Now, even on such a system, path resolution obeys the POSIX 238 rules that a trailing slash ensures that the preceeding name is a 239 directory or a symlink to a directory. 240 241** Changes in behavior 242 243 id no longer prints SELinux " context=..." when the POSIXLY_CORRECT 244 environment variable is set. 245 246 readlink -f now ignores a trailing slash when deciding if the 247 last component (possibly via a dangling symlink) can be created, 248 since mkdir will succeed in that case. 249 250** New features 251 252 ln now accepts the options --logical (-L) and --physical (-P), 253 added by POSIX 2008. The default behavior is -P on systems like 254 GNU/Linux where link(2) creates hard links to symlinks, and -L on 255 BSD systems where link(2) follows symlinks. 256 257 stat: without -f, a command-line argument of "-" now means standard input. 258 With --file-system (-f), an argument of "-" is now rejected. 259 If you really must operate on a file named "-", specify it as 260 "./-" or use "--" to separate options from arguments. 261 262** Improvements 263 264 rm: rewrite to use gnulib's fts 265 This makes rm -rf significantly faster (400-500%) in some pathological 266 cases, and slightly slower (20%) in at least one pathological case. 267 268 rm -r deletes deep hierarchies more efficiently. Before, execution time 269 was quadratic in the depth of the hierarchy, now it is merely linear. 270 However, this improvement is not as pronounced as might be expected for 271 very deep trees, because prior to this change, for any relative name 272 length longer than 8KiB, rm -r would sacrifice official conformance to 273 avoid the disproportionate quadratic performance penalty. Leading to 274 another improvement: 275 276 rm -r is now slightly more standards-conformant when operating on 277 write-protected files with relative names longer than 8KiB. 278 279 280* Noteworthy changes in release 7.6 (2009-09-11) [stable] 281 282** Bug fixes 283 284 cp, mv now ignore failure to preserve a symlink time stamp, when it is 285 due to their running on a kernel older than what was implied by headers 286 and libraries tested at configure time. 287 [bug introduced in coreutils-7.5] 288 289 cp --reflink --preserve now preserves attributes when cloning a file. 290 [bug introduced in coreutils-7.5] 291 292 cp --preserve=xattr no longer leaks resources on each preservation failure. 293 [bug introduced in coreutils-7.1] 294 295 dd now exits with non-zero status when it encounters a write error while 296 printing a summary to stderr. 297 [bug introduced in coreutils-6.11] 298 299 dd cbs=N conv=unblock would fail to print a final newline when the size 300 of the input was not a multiple of N bytes. 301 [the non-conforming behavior dates back to the initial implementation] 302 303 df no longer requires that each command-line argument be readable 304 [bug introduced in coreutils-7.3] 305 306 ls -i now prints consistent inode numbers also for mount points. 307 This makes ls -i DIR less efficient on systems with dysfunctional readdir, 308 because ls must stat every file in order to obtain a guaranteed-valid 309 inode number. [bug introduced in coreutils-6.0] 310 311 tail -f (inotify-enabled) now flushes any initial output before blocking. 312 Before, this would print nothing and wait: stdbuf -o 4K tail -f /etc/passwd 313 Note that this bug affects tail -f only when its standard output is buffered, 314 which is relatively unusual. 315 [bug introduced in coreutils-7.5] 316 317 tail -f once again works with standard input. inotify-enabled tail -f 318 would fail when operating on a nameless stdin. I.e., tail -f < /etc/passwd 319 would say "tail: cannot watch `-': No such file or directory", yet the 320 relatively baroque tail -f /dev/stdin < /etc/passwd would work. Now, the 321 offending usage causes tail to revert to its conventional sleep-based 322 (i.e., not inotify-based) implementation. 323 [bug introduced in coreutils-7.5] 324 325** Portability 326 327 ln, link: link f z/ would mistakenly succeed on Solaris 10, given an 328 existing file, f, and nothing named "z". ln -T f z/ has the same problem. 329 Each would mistakenly create "z" as a link to "f". Now, even on such a 330 system, each command reports the error, e.g., 331 link: cannot create link `z/' to `f': Not a directory 332 333** New features 334 335 cp --reflink accepts a new "auto" parameter which falls back to 336 a standard copy if creating a copy-on-write clone is not possible. 337 338** Changes in behavior 339 340 tail -f now ignores "-" when stdin is a pipe or FIFO. 341 tail-with-no-args now ignores -f unconditionally when stdin is a pipe or FIFO. 342 Before, it would ignore -f only when no file argument was specified, 343 and then only when POSIXLY_CORRECT was set. Now, :|tail -f - terminates 344 immediately. Before, it would block indefinitely. 345 346 347* Noteworthy changes in release 7.5 (2009-08-20) [stable] 348 349** Bug fixes 350 351 dd's oflag=direct option now works even when the size of the input 352 is not a multiple of e.g., 512 bytes. 353 354 dd now handles signals consistently even when they're received 355 before data copying has started. 356 357 install runs faster again with SELinux enabled 358 [introduced in coreutils-7.0] 359 360 ls -1U (with two or more arguments, at least one a nonempty directory) 361 would print entry names *before* the name of the containing directory. 362 Also fixed incorrect output of ls -1RU and ls -1sU. 363 [introduced in coreutils-7.0] 364 365 sort now correctly ignores fields whose ending position is specified 366 before the start position. Previously in numeric mode the remaining 367 part of the line after the start position was used as the sort key. 368 [This bug appears to have been present in "the beginning".] 369 370 truncate -s failed to skip all whitespace in the option argument in 371 some locales. 372 373** New programs 374 375 stdbuf: A new program to run a command with modified stdio buffering 376 for its standard streams. 377 378** Changes in behavior 379 380 ls --color: files with multiple hard links are no longer colored differently 381 by default. That can be enabled by changing the LS_COLORS environment 382 variable. You can control that using the MULTIHARDLINK dircolors input 383 variable which corresponds to the 'mh' LS_COLORS item. Note these variables 384 were renamed from 'HARDLINK' and 'hl' which were available since 385 coreutils-7.1 when this feature was introduced. 386 387** Deprecated options 388 389 nl --page-increment: deprecated in favor of --line-increment, the new option 390 maintains the previous semantics and the same short option, -i. 391 392** New features 393 394 chroot now accepts the options --userspec and --groups. 395 396 cp accepts a new option, --reflink: create a lightweight copy 397 using copy-on-write (COW). This is currently only supported within 398 a btrfs file system. 399 400 cp now preserves time stamps on symbolic links, when possible 401 402 sort accepts a new option, --human-numeric-sort (-h): sort numbers 403 while honoring human readable suffixes like KiB and MB etc. 404 405 tail --follow now uses inotify when possible, to be more responsive 406 to file changes and more efficient when monitoring many files. 407 408 409* Noteworthy changes in release 7.4 (2009-05-07) [stable] 410 411** Bug fixes 412 413 date -d 'next mon', when run on a Monday, now prints the date 414 7 days in the future rather than the current day. Same for any other 415 day-of-the-week name, when run on that same day of the week. 416 [This bug appears to have been present in "the beginning". ] 417 418 date -d tuesday, when run on a Tuesday -- using date built from the 7.3 419 release tarball, not from git -- would print the date 7 days in the future. 420 Now, it works properly and prints the current date. That was due to 421 human error (including not-committed changes in a release tarball) 422 and the fact that there is no check to detect when the gnulib/ git 423 submodule is dirty. 424 425** Build-related 426 427 make check: two tests have been corrected 428 429** Portability 430 431 There have been some ACL-related portability fixes for *BSD, 432 inherited from gnulib. 433 434 435* Noteworthy changes in release 7.3 (2009-05-01) [stable] 436 437** Bug fixes 438 439 cp now diagnoses failure to preserve selinux/xattr attributes when 440 --preserve=context,xattr is specified in combination with -a. 441 Also, cp no longer suppresses attribute-preservation diagnostics 442 when preserving SELinux context was explicitly requested. 443 444 ls now aligns output correctly in the presence of abbreviated month 445 names from the locale database that have differing widths. 446 447 ls -v and sort -V now order names like "#.b#" properly 448 449 mv: do not print diagnostics when failing to preserve xattr's on file 450 systems without xattr support. 451 452 sort -m no longer segfaults when its output file is also an input file. 453 E.g., with this, touch 1; sort -m -o 1 1, sort would segfault. 454 [introduced in coreutils-7.2] 455 456** Changes in behavior 457 458 shred, sort, shuf: now use an internal pseudorandom generator by default. 459 This is mainly noticable in shred where the 3 random passes it does by 460 default should proceed at the speed of the disk. Previously /dev/urandom 461 was used if available, which is relatively slow on GNU/Linux systems. 462 463** Improved robustness 464 465 cp would exit successfully after copying less than the full contents 466 of a file larger than ~4000 bytes from a linux-/proc file system to a 467 destination file system with a fundamental block size of 4KiB or greater. 468 Reading into a 4KiB-or-larger buffer, cp's "read" syscall would return 469 a value smaller than 4096, and cp would interpret that as EOF (POSIX 470 allows this). This optimization, now removed, saved 50% of cp's read 471 syscalls when copying small files. Affected linux kernels: at least 472 2.6.9 through 2.6.29. 473 [the optimization was introduced in coreutils-6.0] 474 475** Portability 476 477 df now pre-mounts automountable directories even with automounters for 478 which stat-like syscalls no longer provoke mounting. Now, df uses open. 479 480 `id -G $USER` now works correctly even on Darwin and NetBSD. Previously it 481 would either truncate the group list to 10, or go into an infinite loop, 482 due to their non-standard getgrouplist implementations. 483 [truncation introduced in coreutils-6.11] 484 [infinite loop introduced in coreutils-7.1] 485 486 487* Noteworthy changes in release 7.2 (2009-03-31) [stable] 488 489** New features 490 491 pwd now accepts the options --logical (-L) and --physical (-P). For 492 compatibility with existing scripts, -P is the default behavior 493 unless POSIXLY_CORRECT is requested. 494 495** Bug fixes 496 497 cat once again immediately outputs data it has processed. 498 Previously it would have been buffered and only output if enough 499 data was read, or on process exit. 500 [bug introduced in coreutils-6.0] 501 502 comm's new --check-order option would fail to detect disorder on any pair 503 of lines where one was a prefix of the other. For example, this would 504 fail to report the disorder: printf 'Xb\nX\n'>k; comm --check-order k k 505 [bug introduced in coreutils-7.0] 506 507 cp once again diagnoses the invalid "cp -rl dir dir" right away, 508 rather than after creating a very deep dir/dir/dir/... hierarchy. 509 The bug strikes only with both --recursive (-r, -R) and --link (-l). 510 [bug introduced in coreutils-7.1] 511 512 ls --sort=version (-v) sorted names beginning with "." inconsistently. 513 Now, names that start with "." are always listed before those that don't. 514 515 pr: fix the bug whereby --indent=N (-o) did not indent header lines 516 [bug introduced in coreutils-6.9.90] 517 518 sort now handles specified key ends correctly. 519 Previously -k1,1b would have caused leading space from field 2 to be 520 included in the sort while -k2,3.0 would have not included field 3. 521 522** Changes in behavior 523 524 cat,cp,install,mv,split: these programs now read and write a minimum 525 of 32KiB at a time. This was seen to double throughput when reading 526 cached files on GNU/Linux-based systems. 527 528 cp -a now tries to preserve extended attributes (xattr), but does not 529 diagnose xattr-preservation failure. However, cp --preserve=all still does. 530 531 ls --color: hard link highlighting can be now disabled by changing the 532 LS_COLORS environment variable. To disable it you can add something like 533 this to your profile: eval `dircolors | sed s/hl=[^:]*:/hl=:/` 534 535 536* Noteworthy changes in release 7.1 (2009-02-21) [stable] 537 538** New features 539 540 Add extended attribute support available on certain filesystems like ext2 541 and XFS. 542 cp: Tries to copy xattrs when --preserve=xattr or --preserve=all specified 543 mv: Always tries to copy xattrs 544 install: Never copies xattrs 545 546 cp and mv accept a new option, --no-clobber (-n): silently refrain 547 from overwriting any existing destination file 548 549 dd accepts iflag=cio and oflag=cio to open the file in CIO (concurrent I/O) 550 mode where this feature is available. 551 552 install accepts a new option, --compare (-C): compare each pair of source 553 and destination files, and if the destination has identical content and 554 any specified owner, group, permissions, and possibly SELinux context, then 555 do not modify the destination at all. 556 557 ls --color now highlights hard linked files, too 558 559 stat -f recognizes the Lustre file system type 560 561** Bug fixes 562 563 chgrp, chmod, chown --silent (--quiet, -f) no longer print some diagnostics 564 [bug introduced in coreutils-5.1] 565 566 cp uses much less memory in some situations 567 568 cp -a now correctly tries to preserve SELinux context (announced in 6.9.90), 569 doesn't inform about failure, unlike with --preserve=all 570 571 du --files0-from=FILE no longer reads all of FILE into RAM before 572 processing the first file name 573 574 seq 9223372036854775807 9223372036854775808 now prints only two numbers 575 on systems with extended long double support and good library support. 576 Even with this patch, on some systems, it still produces invalid output, 577 from 3 to at least 1026 lines long. [bug introduced in coreutils-6.11] 578 579 seq -w now accounts for a decimal point added to the last number 580 to correctly print all numbers to the same width. 581 582 wc --files0-from=FILE no longer reads all of FILE into RAM, before 583 processing the first file name, unless the list of names is known 584 to be small enough. 585 586** Changes in behavior 587 588 cp and mv: the --reply={yes,no,query} option has been removed. 589 Using it has elicited a warning for the last three years. 590 591 dd: user specified offsets that are too big are handled better. 592 Previously, erroneous parameters to skip and seek could result 593 in redundant reading of the file with no warnings or errors. 594 595 du: -H (initially equivalent to --si) is now equivalent to 596 --dereference-args, and thus works as POSIX requires 597 598 shred: now does 3 overwrite passes by default rather than 25. 599 600 ls -l now marks SELinux-only files with the less obtrusive '.', 601 rather than '+'. A file with any other combination of MAC and ACL 602 is still marked with a '+'. 603 604 605* Noteworthy changes in release 7.0 (2008-10-05) [beta] 606 607** New programs 608 609 timeout: Run a command with bounded time. 610 truncate: Set the size of a file to a specified size. 611 612** New features 613 614 chgrp, chmod, chown, chcon, du, rm: now all display linear performance, 615 even when operating on million-entry directories on ext3 and ext4 file 616 systems. Before, they would exhibit O(N^2) performance, due to linear 617 per-entry seek time cost when operating on entries in readdir order. 618 Rm was improved directly, while the others inherit the improvement 619 from the newer version of fts in gnulib. 620 621 comm now verifies that the inputs are in sorted order. This check can 622 be turned off with the --nocheck-order option. 623 624 comm accepts new option, --output-delimiter=STR, that allows specification 625 of an output delimiter other than the default single TAB. 626 627 cp and mv: the deprecated --reply=X option is now also undocumented. 628 629 dd accepts iflag=fullblock to make it accumulate full input blocks. 630 With this new option, after a short read, dd repeatedly calls read, 631 until it fills the incomplete block, reaches EOF, or encounters an error. 632 633 df accepts a new option --total, which produces a grand total of all 634 arguments after all arguments have been processed. 635 636 If the GNU MP library is available at configure time, factor and 637 expr support arbitrarily large numbers. Pollard's rho algorithm is 638 used to factor large numbers. 639 640 install accepts a new option --strip-program to specify the program used to 641 strip binaries. 642 643 ls now colorizes files with capabilities if libcap is available 644 645 ls -v now uses filevercmp function as sort predicate (instead of strverscmp) 646 647 md5sum now accepts the new option, --quiet, to suppress the printing of 648 'OK' messages. sha1sum, sha224sum, sha384sum, and sha512sum accept it, too. 649 650 sort accepts a new option, --files0-from=F, that specifies a file 651 containing a null-separated list of files to sort. This list is used 652 instead of filenames passed on the command-line to avoid problems with 653 maximum command-line (argv) length. 654 655 sort accepts a new option --batch-size=NMERGE, where NMERGE 656 represents the maximum number of inputs that will be merged at once. 657 When processing more than NMERGE inputs, sort uses temporary files. 658 659 sort accepts a new option --version-sort (-V, --sort=version), 660 specifying that ordering is to be based on filevercmp. 661 662** Bug fixes 663 664 chcon --verbose now prints a newline after each message 665 666 od no longer suffers from platform bugs in printf(3). This is 667 probably most noticeable when using 'od -tfL' to print long doubles. 668 669 seq -0.1 0.1 2 now prints 2,0 when locale's decimal point is ",". 670 Before, it would mistakenly omit the final number in that example. 671 672 shuf honors the --zero-terminated (-z) option, even with --input-range=LO-HI 673 674 shuf --head-count is now correctly documented. The documentation 675 previously claimed it was called --head-lines. 676 677** Improvements 678 679 Improved support for access control lists (ACLs): On MacOS X, Solaris 7..10, 680 HP-UX 11, Tru64, AIX, IRIX 6.5, and Cygwin, "ls -l" now displays the presence 681 of an ACL on a file via a '+' sign after the mode, and "cp -p" copies ACLs. 682 683 join has significantly better performance due to better memory management 684 685 ls now uses constant memory when not sorting and using one_per_line format, 686 no matter how many files are in a given directory 687 688 od now aligns fields across lines when printing multiple -t 689 specifiers, and no longer prints fields that resulted entirely from 690 padding the input out to the least common multiple width. 691 692** Changes in behavior 693 694 stat's --context (-Z) option has always been a no-op. 695 Now it evokes a warning that it is obsolete and will be removed. 696 697 698* Noteworthy changes in release 6.12 (2008-05-31) [stable] 699 700** Bug fixes 701 702 chcon, runcon: --help output now includes the bug-reporting address 703 704 cp -p copies permissions more portably. For example, on MacOS X 10.5, 705 "cp -p some-fifo some-file" no longer fails while trying to copy the 706 permissions from the some-fifo argument. 707 708 id with no options now prints the SELinux context only when invoked 709 with no USERNAME argument. 710 711 id and groups once again print the AFS-specific nameless group-ID (PAG). 712 Printing of such large-numbered, kernel-only (not in /etc/group) group-IDs 713 was suppressed in 6.11 due to ignorance that they are useful. 714 715 uniq: avoid subtle field-skipping malfunction due to isblank misuse. 716 In some locales on some systems, isblank(240) (aka  ) is nonzero. 717 On such systems, uniq --skip-fields=N would fail to skip the proper 718 number of fields for some inputs. 719 720 tac: avoid segfault with --regex (-r) and multiple files, e.g., 721 "echo > x; tac -r x x". [bug present at least in textutils-1.8b, from 1992] 722 723** Changes in behavior 724 725 install once again sets SELinux context, when possible 726 [it was deliberately disabled in 6.9.90] 727 728 729* Noteworthy changes in release 6.11 (2008-04-19) [stable] 730 731** Bug fixes 732 733 configure --enable-no-install-program=groups now works. 734 735 "cp -fR fifo E" now succeeds with an existing E. Before this fix, using 736 -fR to copy a fifo or "special" file onto an existing file would fail 737 with EEXIST. Now, it once again unlinks the destination before trying 738 to create the destination file. [bug introduced in coreutils-5.90] 739 740 dd once again works with unnecessary options like if=/dev/stdin and 741 of=/dev/stdout. [bug introduced in fileutils-4.0h] 742 743 id now uses getgrouplist, when possible. This results in 744 much better performance when there are many users and/or groups. 745 746 ls no longer segfaults on files in /proc when linked with an older version 747 of libselinux. E.g., ls -l /proc/sys would dereference a NULL pointer. 748 749 md5sum would segfault for invalid BSD-style input, e.g., 750 echo 'MD5 (' | md5sum -c - Now, md5sum ignores that line. 751 sha1sum, sha224sum, sha384sum, and sha512sum are affected, too. 752 [bug introduced in coreutils-5.1.0] 753 754 md5sum -c would accept a NUL-containing checksum string like "abcd\0..." 755 and would unnecessarily read and compute the checksum of the named file, 756 and then compare that checksum to the invalid one: guaranteed to fail. 757 Now, it recognizes that the line is not valid and skips it. 758 sha1sum, sha224sum, sha384sum, and sha512sum are affected, too. 759 [bug present in the original version, in coreutils-4.5.1, 1995] 760 761 "mkdir -Z x dir" no longer segfaults when diagnosing invalid context "x" 762 mkfifo and mknod would fail similarly. Now they're fixed. 763 764 mv would mistakenly unlink a destination file before calling rename, 765 when the destination had two or more hard links. It no longer does that. 766 [bug introduced in coreutils-5.3.0] 767 768 "paste -d'\' file" no longer overruns memory (heap since coreutils-5.1.2, 769 stack before then) [bug present in the original version, in 1992] 770 771 "pr -e" with a mix of backspaces and TABs no longer corrupts the heap 772 [bug present in the original version, in 1992] 773 774 "ptx -F'\' long-file-name" would overrun a malloc'd buffer and corrupt 775 the heap. That was triggered by a lone backslash (or odd number of them) 776 at the end of the option argument to --flag-truncation=STRING (-F), 777 --word-regexp=REGEXP (-W), or --sentence-regexp=REGEXP (-S). 778 779 "rm -r DIR" would mistakenly declare to be "write protected" -- and 780 prompt about -- full DIR-relative names longer than MIN (PATH_MAX, 8192). 781 782 "rmdir --ignore-fail-on-non-empty" detects and ignores the failure 783 in more cases when a directory is empty. 784 785 "seq -f % 1" would issue the erroneous diagnostic "seq: memory exhausted" 786 rather than reporting the invalid string format. 787 [bug introduced in coreutils-6.0] 788 789** New features 790 791 join now verifies that the inputs are in sorted order. This check can 792 be turned off with the --nocheck-order option. 793 794 sort accepts the new option --sort=WORD, where WORD can be one of 795 general-numeric, month, numeric or random. These are equivalent to the 796 options --general-numeric-sort/-g, --month-sort/-M, --numeric-sort/-n 797 and --random-sort/-R, resp. 798 799** Improvements 800 801 id and groups work around an AFS-related bug whereby those programs 802 would print an invalid group number, when given no user-name argument. 803 804 ls --color no longer outputs unnecessary escape sequences 805 806 seq gives better diagnostics for invalid formats. 807 808** Portability 809 810 rm now works properly even on systems like BeOS and Haiku, 811 which have negative errno values. 812 813** Consistency 814 815 install, mkdir, rmdir and split now write --verbose output to stdout, 816 not to stderr. 817 818 819* Noteworthy changes in release 6.10 (2008-01-22) [stable] 820 821** Bug fixes 822 823 Fix a non-portable use of sed in configure.ac. 824 [bug introduced in coreutils-6.9.92] 825 826 827* Noteworthy changes in release 6.9.92 (2008-01-12) [beta] 828 829** Bug fixes 830 831 cp --parents no longer uses uninitialized memory when restoring the 832 permissions of a just-created destination directory. 833 [bug introduced in coreutils-6.9.90] 834 835 tr's case conversion would fail in a locale with differing numbers 836 of lower case and upper case characters. E.g., this would fail: 837 env LC_CTYPE=en_US.ISO-8859-1 tr '[:upper:]' '[:lower:]' 838 [bug introduced in coreutils-6.9.90] 839 840** Improvements 841 842 "touch -d now writable-but-owned-by-someone-else" now succeeds 843 whenever that same command would succeed without "-d now". 844 Before, it would work fine with no -d option, yet it would 845 fail with the ostensibly-equivalent "-d now". 846 847 848* Noteworthy changes in release 6.9.91 (2007-12-15) [beta] 849 850** Bug fixes 851 852 "ls -l" would not output "+" on SELinux hosts unless -Z was also given. 853 854 "rm" would fail to unlink a non-directory when run in an environment 855 in which the user running rm is capable of unlinking a directory. 856 [bug introduced in coreutils-6.9] 857 858 859* Noteworthy changes in release 6.9.90 (2007-12-01) [beta] 860 861** New programs 862 863 arch: equivalent to uname -m, not installed by default 864 But don't install this program on Solaris systems. 865 866 chcon: change the SELinux security context of a file 867 868 mktemp: create a temporary file or directory (or names) 869 870 runcon: run a program in a different SELinux security context 871 872** Programs no longer installed by default 873 874 hostname, su 875 876** Changes in behavior 877 878 cp, by default, refuses to copy through a dangling destination symlink 879 Set POSIXLY_CORRECT if you require the old, risk-prone behavior. 880 881 pr -F no longer suppresses the footer or the first two blank lines in 882 the header. This is for compatibility with BSD and POSIX. 883 884 tr now warns about an unescaped backslash at end of string. 885 The tr from coreutils-5.2.1 and earlier would fail for such usage, 886 and Solaris' tr ignores that final byte. 887 888** New features 889 890 Add SELinux support, based on the patch from Fedora: 891 * cp accepts new --preserve=context option. 892 * "cp -a" works with SELinux: 893 Now, cp -a attempts to preserve context, but failure to do so does 894 not change cp's exit status. However "cp --preserve=context" is 895 similar, but failure *does* cause cp to exit with nonzero status. 896 * install accepts new "-Z, --context=C" option. 897 * id accepts new "-Z" option. 898 * stat honors the new %C format directive: SELinux security context string 899 * ls accepts a slightly modified -Z option. 900 * ls: contrary to Fedora version, does not accept --lcontext and --scontext 901 902 The following commands and options now support the standard size 903 suffixes kB, M, MB, G, GB, and so on for T, P, Y, Z, and Y: 904 head -c, head -n, od -j, od -N, od -S, split -b, split -C, 905 tail -c, tail -n. 906 907 cp -p tries to preserve the GID of a file even if preserving the UID 908 is not possible. 909 910 uniq accepts a new option: --zero-terminated (-z). As with the sort 911 option of the same name, this makes uniq consume and produce 912 NUL-terminated lines rather than newline-terminated lines. 913 914 wc no longer warns about character decoding errors in multibyte locales. 915 This means for example that "wc /bin/sh" now produces normal output 916 (though the word count will have no real meaning) rather than many 917 error messages. 918 919** New build options 920 921 By default, "make install" no longer attempts to install (or even build) su. 922 To change that, use ./configure --enable-install-program=su. 923 If you also want to install the new "arch" program, do this: 924 ./configure --enable-install-program=arch,su. 925 926 You can inhibit the compilation and installation of selected programs 927 at configure time. For example, to avoid installing "hostname" and 928 "uptime", use ./configure --enable-no-install-program=hostname,uptime 929 Note: currently, "make check" passes, even when arch and su are not 930 built (that's the new default). However, if you inhibit the building 931 and installation of other programs, don't be surprised if some parts 932 of "make check" fail. 933 934** Remove deprecated options 935 936 df no longer accepts the --kilobytes option. 937 du no longer accepts the --kilobytes or --megabytes options. 938 ls no longer accepts the --kilobytes option. 939 ptx longer accepts the --copyright option. 940 who no longer accepts -i or --idle. 941 942** Improved robustness 943 944 ln -f can no longer silently clobber a just-created hard link. 945 In some cases, ln could be seen as being responsible for data loss. 946 For example, given directories a, b, c, and files a/f and b/f, we 947 should be able to do this safely: ln -f a/f b/f c && rm -f a/f b/f 948 However, before this change, ln would succeed, and thus cause the 949 loss of the contents of a/f. 950 951 stty no longer silently accepts certain invalid hex values 952 in its 35-colon command-line argument 953 954** Bug fixes 955 956 chmod no longer ignores a dangling symlink. Now, chmod fails 957 with a diagnostic saying that it cannot operate on such a file. 958 [bug introduced in coreutils-5.1.0] 959 960 cp attempts to read a regular file, even if stat says it is empty. 961 Before, "cp /proc/cpuinfo c" would create an empty file when the kernel 962 reports stat.st_size == 0, while "cat /proc/cpuinfo > c" would "work", 963 and create a nonempty one. [bug introduced in coreutils-6.0] 964 965 cp --parents no longer mishandles symlinks to directories in file 966 name components in the source, e.g., "cp --parents symlink/a/b d" 967 no longer fails. Also, 'cp' no longer considers a destination 968 symlink to be the same as the referenced file when copying links 969 or making backups. For example, if SYM is a symlink to FILE, 970 "cp -l FILE SYM" now reports an error instead of silently doing 971 nothing. The behavior of 'cp' is now better documented when the 972 destination is a symlink. 973 974 "cp -i --update older newer" no longer prompts; same for mv 975 976 "cp -i" now detects read errors on standard input, and no longer consumes 977 too much seekable input; same for ln, install, mv, and rm. 978 979 cut now diagnoses a range starting with zero (e.g., -f 0-2) as invalid; 980 before, it would treat it as if it started with 1 (-f 1-2). 981 982 "cut -f 2-0" now fails; before, it was equivalent to "cut -f 2-" 983 984 cut now diagnoses the '-' in "cut -f -" as an invalid range, rather 985 than interpreting it as the unlimited range, "1-". 986 987 date -d now accepts strings of the form e.g., 'YYYYMMDD +N days', 988 in addition to the usual 'YYYYMMDD N days'. 989 990 du -s now includes the size of any stat'able-but-inaccessible directory 991 in the total size. 992 993 du (without -s) prints whatever it knows of the size of an inaccessible 994 directory. Before, du would print nothing for such a directory. 995 996 ls -x DIR would sometimes output the wrong string in place of the 997 first entry. [introduced in coreutils-6.8] 998 999 ls --color would mistakenly color a dangling symlink as if it were 1000 a regular symlink. This would happen only when the dangling symlink 1001 was not a command-line argument and in a directory with d_type support. 1002 [introduced in coreutils-6.0] 1003 1004 ls --color, (with a custom LS_COLORS envvar value including the 1005 ln=target attribute) would mistakenly output the string "target" 1006 before the name of each symlink. [introduced in coreutils-6.0] 1007 1008 od's --skip (-j) option now works even when the kernel says that a 1009 nonempty regular file has stat.st_size = 0. This happens at least 1010 with files in /proc and linux-2.6.22. 1011 1012 "od -j L FILE" had a bug: when the number of bytes to skip, L, is exactly 1013 the same as the length of FILE, od would skip *no* bytes. When the number 1014 of bytes to skip is exactly the sum of the lengths of the first N files, 1015 od would skip only the first N-1 files. [introduced in textutils-2.0.9] 1016 1017 ./printf %.10000000f 1 could get an internal ENOMEM error and generate 1018 no output, yet erroneously exit with status 0. Now it diagnoses the error 1019 and exits with nonzero status. [present in initial implementation] 1020 1021 seq no longer mishandles obvious cases like "seq 0 0.000001 0.000003", 1022 so workarounds like "seq 0 0.000001 0.0000031" are no longer needed. 1023 1024 seq would mistakenly reject some valid format strings containing %%, 1025 and would mistakenly accept some invalid ones. e.g., %g%% and %%g, resp. 1026 1027 "seq .1 .1" would mistakenly generate no output on some systems 1028 1029 Obsolete sort usage with an invalid ordering-option character, e.g., 1030 "env _POSIX2_VERSION=199209 sort +1x" no longer makes sort free an 1031 invalid pointer [introduced in coreutils-6.5] 1032 1033 sorting very long lines (relative to the amount of available memory) 1034 no longer provokes unaligned memory access 1035 1036 split --line-bytes=N (-C N) no longer creates an empty file 1037 [this bug is present at least as far back as textutils-1.22 (Jan, 1997)] 1038 1039 tr -c no longer aborts when translating with Set2 larger than the 1040 complement of Set1. [present in the original version, in 1992] 1041 1042 tr no longer rejects an unmatched [:lower:] or [:upper:] in SET1. 1043 [present in the original version] 1044 1045 1046* Noteworthy changes in release 6.9 (2007-03-22) [stable] 1047 1048** Bug fixes 1049 1050 cp -x (--one-file-system) would fail to set mount point permissions 1051 1052 The default block size and output format for df -P are now unaffected by 1053 the DF_BLOCK_SIZE, BLOCK_SIZE, and BLOCKSIZE environment variables. It 1054 is still affected by POSIXLY_CORRECT, though. 1055 1056 Using pr -m -s (i.e. merging files, with TAB as the output separator) 1057 no longer inserts extraneous spaces between output columns. 1058 1059* Noteworthy changes in release 6.8 (2007-02-24) [not-unstable] 1060 1061** Bug fixes 1062 1063 chgrp, chmod, and chown now honor the --preserve-root option. 1064 Before, they would warn, yet continuing traversing and operating on /. 1065 1066 chmod no longer fails in an environment (e.g., a chroot) with openat 1067 support but with insufficient /proc support. 1068 1069 "cp --parents F/G D" no longer creates a directory D/F when F is not 1070 a directory (and F/G is therefore invalid). 1071 1072 "cp --preserve=mode" would create directories that briefly had 1073 too-generous permissions in some cases. For example, when copying a 1074 directory with permissions 777 the destination directory might 1075 temporarily be setgid on some file systems, which would allow other 1076 users to create subfiles with the same group as the directory. Fix 1077 similar problems with 'install' and 'mv'. 1078 1079 cut no longer dumps core for usage like "cut -f2- f1 f2" with two or 1080 more file arguments. This was due to a double-free bug, introduced 1081 in coreutils-5.3.0. 1082 1083 dd bs= operands now silently override any later ibs= and obs= 1084 operands, as POSIX and tradition require. 1085 1086 "ls -FRL" always follows symbolic links on Linux. Introduced in 1087 coreutils-6.0. 1088 1089 A cross-partition "mv /etc/passwd ~" (by non-root) now prints 1090 a reasonable diagnostic. Before, it would print this: 1091 "mv: cannot remove `/etc/passwd': Not a directory". 1092 1093 pwd and "readlink -e ." no longer fail unnecessarily when a parent 1094 directory is unreadable. 1095 1096 rm (without -f) could prompt when it shouldn't, or fail to prompt 1097 when it should, when operating on a full name longer than 511 bytes 1098 and getting an ENOMEM error while trying to form the long name. 1099 1100 rm could mistakenly traverse into the wrong directory under unusual 1101 conditions: when a full name longer than 511 bytes specifies a search-only 1102 directory, and when forming that name fails with ENOMEM, rm would attempt 1103 to open a truncated-to-511-byte name with the first five bytes replaced 1104 with "[...]". If such a directory were to actually exist, rm would attempt 1105 to remove it. 1106 1107 "rm -rf /etc/passwd" (run by non-root) now prints a diagnostic. 1108 Before it would print nothing. 1109 1110 "rm --interactive=never F" no longer prompts for an unwritable F 1111 1112 "rm -rf D" would emit an misleading diagnostic when failing to 1113 remove a symbolic link within the unwritable directory, D. 1114 Introduced in coreutils-6.0. Similarly, when a cross-partition 1115 "mv" fails because the source directory is unwritable, it now gives 1116 a reasonable diagnostic. Before, this would print 1117 $ mkdir /tmp/x; touch /tmp/x/y; chmod -w /tmp/x; 1118 $ test $(stat -c %d /tmp/x) -ne $(stat -c %d .) && mv /tmp/x/y . 1119 mv: cannot remove `/tmp/x/y': Not a directory 1120 Now it prints this: 1121 mv: cannot remove `/tmp/x/y': Permission denied. 1122 1123** New features 1124 1125 sort's new --compress-program=PROG option specifies a compression 1126 program to use when writing and reading temporary files. 1127 This can help save both time and disk space when sorting large inputs. 1128 1129 sort accepts the new option -C, which acts like -c except no diagnostic 1130 is printed. Its --check option now accepts an optional argument, and 1131 --check=quiet and --check=silent are now aliases for -C, while 1132 --check=diagnose-first is an alias for -c or plain --check. 1133 1134 1135* Noteworthy changes in release 6.7 (2006-12-08) [stable] 1136 1137** Bug fixes 1138 1139 When cp -p copied a file with special mode bits set, the same bits 1140 were set on the copy even when ownership could not be preserved. 1141 This could result in files that were setuid to the wrong user. 1142 To fix this, special mode bits are now set in the copy only if its 1143 ownership is successfully preserved. Similar problems were fixed 1144 with mv when copying across file system boundaries. This problem 1145 affects all versions of coreutils through 6.6. 1146 1147 cp --preserve=ownership would create output files that temporarily 1148 had too-generous permissions in some cases. For example, when 1149 copying a file with group A and mode 644 into a group-B sticky 1150 directory, the output file was briefly readable by group B. 1151 Fix similar problems with cp options like -p that imply 1152 --preserve=ownership, with install -d when combined with either -o 1153 or -g, and with mv when copying across file system boundaries. 1154 This bug affects all versions of coreutils through 6.6. 1155 1156 du --one-file-system (-x) would skip subdirectories of any directory 1157 listed as second or subsequent command line argument. This bug affects 1158 coreutils-6.4, 6.5 and 6.6. 1159 1160 1161* Noteworthy changes in release 6.6 (2006-11-22) [stable] 1162 1163** Bug fixes 1164 1165 ls would segfault (dereference a NULL pointer) for a file with a 1166 nameless group or owner. This bug was introduced in coreutils-6.5. 1167 1168 A bug in the latest official m4/gettext.m4 (from gettext-0.15) 1169 made configure fail to detect gettext support, due to the unusual 1170 way in which coreutils uses AM_GNU_GETTEXT. 1171 1172** Improved robustness 1173 1174 Now, du (and the other fts clients: chmod, chgrp, chown) honor a 1175 trailing slash in the name of a symlink-to-directory even on 1176 Solaris 9, by working around its buggy fstatat implementation. 1177 1178 1179* Major changes in release 6.5 (2006-11-19) [stable] 1180 1181** Bug fixes 1182 1183 du (and the other fts clients: chmod, chgrp, chown) would exit early 1184 when encountering an inaccessible directory on a system with native 1185 openat support (i.e., linux-2.6.16 or newer along with glibc-2.4 1186 or newer). This bug was introduced with the switch to gnulib's 1187 openat-based variant of fts, for coreutils-6.0. 1188 1189 "ln --backup f f" now produces a sensible diagnostic 1190 1191** New features 1192 1193 rm accepts a new option: --one-file-system 1194 1195 1196* Major changes in release 6.4 (2006-10-22) [stable] 1197 1198** Bug fixes 1199 1200 chgrp and chown would malfunction when invoked with both -R and -H and 1201 with one or more of the following: --preserve-root, --verbose, --changes, 1202 --from=o:g (chown only). This bug was introduced with the switch to 1203 gnulib's openat-based variant of fts, for coreutils-6.0. 1204 1205 cp --backup dir1 dir2, would rename an existing dir2/dir1 to dir2/dir1~. 1206 This bug was introduced in coreutils-6.0. 1207 1208 With --force (-f), rm no longer fails for ENOTDIR. 1209 For example, "rm -f existing-non-directory/anything" now exits 1210 successfully, ignoring the error about a nonexistent file. 1211 1212 1213* Major changes in release 6.3 (2006-09-30) [stable] 1214 1215** Improved robustness 1216 1217 pinky no longer segfaults on Darwin 7.9.0 (MacOS X 10.3.9) due to a 1218 buggy native getaddrinfo function. 1219 1220 rm works around a bug in Darwin 7.9.0 (MacOS X 10.3.9) that would 1221 sometimes keep it from removing all entries in a directory on an HFS+ 1222 or NFS-mounted partition. 1223 1224 sort would fail to handle very large input (around 40GB) on systems with a 1225 mkstemp function that returns a file descriptor limited to 32-bit offsets. 1226 1227** Bug fixes 1228 1229 chmod would fail unnecessarily in an unusual case: when an initially- 1230 inaccessible argument is rendered accessible by chmod's action on a 1231 preceding command line argument. This bug also affects chgrp, but 1232 it is harder to demonstrate. It does not affect chown. The bug was 1233 introduced with the switch from explicit recursion to the use of fts 1234 in coreutils-5.1.0 (2003-10-15). 1235 1236 cp -i and mv -i occasionally neglected to prompt when the copy or move 1237 action was bound to fail. This bug dates back to before fileutils-4.0. 1238 1239 With --verbose (-v), cp and mv would sometimes generate no output, 1240 or neglect to report file removal. 1241 1242 For the "groups" command: 1243 1244 "groups" no longer prefixes the output with "user :" unless more 1245 than one user is specified; this is for compatibility with BSD. 1246 1247 "groups user" now exits nonzero when it gets a write error. 1248 1249 "groups" now processes options like --help more compatibly. 1250 1251 shuf would infloop, given 8KB or more of piped input 1252 1253** Portability 1254 1255 Versions of chmod, chown, chgrp, du, and rm (tools that use openat etc.) 1256 compiled for Solaris 8 now also work when run on Solaris 10. 1257 1258 1259* Major changes in release 6.2 (2006-09-18) [stable candidate] 1260 1261** Changes in behavior 1262 1263 mkdir -p and install -d (or -D) now use a method that forks a child 1264 process if the working directory is unreadable and a later argument 1265 uses a relative file name. This avoids some race conditions, but it 1266 means you may need to kill two processes to stop these programs. 1267 1268 rm now rejects attempts to remove the root directory, e.g., `rm -fr /' 1269 now fails without removing anything. Likewise for any file name with 1270 a final `./' or `../' component. 1271 1272 tail now ignores the -f option if POSIXLY_CORRECT is set, no file 1273 operand is given, and standard input is any FIFO; formerly it did 1274 this only for pipes. 1275 1276** Infrastructure changes 1277 1278 Coreutils now uses gnulib via the gnulib-tool script. 1279 If you check the source out from CVS, then follow the instructions 1280 in README-cvs. Although this represents a large change to the 1281 infrastructure, it should cause no change in how the tools work. 1282 1283** Bug fixes 1284 1285 cp --backup no longer fails when the last component of a source file 1286 name is "." or "..". 1287 1288 "ls --color" would highlight other-writable and sticky directories 1289 no differently than regular directories on a file system with 1290 dirent.d_type support. 1291 1292 "mv -T --verbose --backup=t A B" now prints the " (backup: B.~1~)" 1293 suffix when A and B are directories as well as when they are not. 1294 1295 mv and "cp -r" no longer fail when invoked with two arguments 1296 where the first one names a directory and the second name ends in 1297 a slash and doesn't exist. E.g., "mv dir B/", for nonexistent B, 1298 now succeeds, once more. This bug was introduced in coreutils-5.3.0. 1299 1300 1301* Major changes in release 6.1 (2006-08-19) [unstable] 1302 1303** Changes in behavior 1304 1305 df now considers BSD "kernfs" file systems to be dummies 1306 1307** New features 1308 1309 printf now supports the 'I' flag on hosts whose underlying printf 1310 implementations support 'I', e.g., "printf %Id 2". 1311 1312** Bug fixes 1313 1314 cp --sparse preserves sparseness at the end of a file, even when 1315 the file's apparent size is not a multiple of its block size. 1316 [introduced with the original design, in fileutils-4.0r, 2000-04-29] 1317 1318 df (with a command line argument) once again prints its header 1319 [introduced in coreutils-6.0] 1320 1321 ls -CF would misalign columns in some cases involving non-stat'able files 1322 [introduced in coreutils-6.0] 1323 1324* Major changes in release 6.0 (2006-08-15) [unstable] 1325 1326** Improved robustness 1327 1328 df: if the file system claims to have more available than total blocks, 1329 report the number of used blocks as being "total - available" 1330 (a negative number) rather than as garbage. 1331 1332 dircolors: a new autoconf run-test for AIX's buggy strndup function 1333 prevents malfunction on that system; may also affect cut, expand, 1334 and unexpand. 1335 1336 fts no longer changes the current working directory, so its clients 1337 (chmod, chown, chgrp, du) no longer malfunction under extreme conditions. 1338 1339 pwd and other programs using lib/getcwd.c work even on file systems 1340 where dirent.d_ino values are inconsistent with those from stat.st_ino. 1341 1342 rm's core is now reentrant: rm --recursive (-r) now processes 1343 hierarchies without changing the working directory at all. 1344 1345** Changes in behavior 1346 1347 basename and dirname now treat // as different from / on platforms 1348 where the two are distinct. 1349 1350 chmod, install, and mkdir now preserve a directory's set-user-ID and 1351 set-group-ID bits unless you explicitly request otherwise. E.g., 1352 `chmod 755 DIR' and `chmod u=rwx,go=rx DIR' now preserve DIR's 1353 set-user-ID and set-group-ID bits instead of clearing them, and 1354 similarly for `mkdir -m 755 DIR' and `mkdir -m u=rwx,go=rx DIR'. To 1355 clear the bits, mention them explicitly in a symbolic mode, e.g., 1356 `mkdir -m u=rwx,go=rx,-s DIR'. To set them, mention them explicitly 1357 in either a symbolic or a numeric mode, e.g., `mkdir -m 2755 DIR', 1358 `mkdir -m u=rwx,go=rx,g+s' DIR. This change is for convenience on 1359 systems where these bits inherit from parents. Unfortunately other 1360 operating systems are not consistent here, and portable scripts 1361 cannot assume the bits are set, cleared, or preserved, even when the 1362 bits are explicitly mentioned. For example, OpenBSD 3.9 `mkdir -m 1363 777 D' preserves D's setgid bit but `chmod 777 D' clears it. 1364 Conversely, Solaris 10 `mkdir -m 777 D', `mkdir -m g-s D', and 1365 `chmod 0777 D' all preserve D's setgid bit, and you must use 1366 something like `chmod g-s D' to clear it. 1367 1368 `cp --link --no-dereference' now works also on systems where the 1369 link system call cannot create a hard link to a symbolic link. 1370 This change has no effect on systems with a Linux-based kernel. 1371 1372 csplit and nl now use POSIX syntax for regular expressions, not 1373 Emacs syntax. As a result, character classes like [[:print:]] and 1374 interval expressions like A\{1,9\} now have their usual meaning, 1375 . no longer matches the null character, and \ must precede the + and 1376 ? operators. 1377 1378 date: a command like date -d '2006-04-23 21 days ago' would print 1379 the wrong date in some time zones. (see the test for an example) 1380 1381 df changes: 1382 1383 df now considers "none" and "proc" file systems to be dummies and 1384 therefore does not normally display them. Also, inaccessible file 1385 systems (which can be caused by shadowed mount points or by 1386 chrooted bind mounts) are now dummies, too. 1387 1388 df now fails if it generates no output, so you can inspect the 1389 exit status of a command like "df -t ext3 -t reiserfs DIR" to test 1390 whether DIR is on a file system of type "ext3" or "reiserfs". 1391 1392 expr no longer complains about leading ^ in a regular expression 1393 (the anchor is ignored), or about regular expressions like A** (the 1394 second "*" is ignored). expr now exits with status 2 (not 3) for 1395 errors it detects in the expression's values; exit status 3 is now 1396 used only for internal errors (such as integer overflow, which expr 1397 now checks for). 1398 1399 install and mkdir now implement the X permission symbol correctly, 1400 e.g., `mkdir -m a+X dir'; previously the X was ignored. 1401 1402 install now creates parent directories with mode u=rwx,go=rx (755) 1403 instead of using the mode specified by the -m option; and it does 1404 not change the owner or group of parent directories. This is for 1405 compatibility with BSD and closes some race conditions. 1406 1407 ln now uses different (and we hope clearer) diagnostics when it fails. 1408 ln -v now acts more like FreeBSD, so it generates output only when 1409 successful and the output is easier to parse. 1410 1411 ls now defaults to --time-style='locale', not --time-style='posix-long-iso'. 1412 However, the 'locale' time style now behaves like 'posix-long-iso' 1413 if your locale settings appear to be messed up. This change 1414 attempts to have the default be the best of both worlds. 1415 1416 mkfifo and mknod no longer set special mode bits (setuid, setgid, 1417 and sticky) with the -m option. 1418 1419 nohup's usual diagnostic now more precisely specifies the I/O 1420 redirections, e.g., "ignoring input and appending output to 1421 nohup.out". Also, nohup now redirects stderr to nohup.out (or 1422 $HOME/nohup.out) if stdout is closed and stderr is a tty; this is in 1423 response to Open Group XCU ERN 71. 1424 1425 rm --interactive now takes an optional argument, although the 1426 default of using no argument still acts like -i. 1427 1428 rm no longer fails to remove an empty, unreadable directory 1429 1430 seq changes: 1431 1432 seq defaults to a minimal fixed point format that does not lose 1433 information if seq's operands are all fixed point decimal numbers. 1434 You no longer need the `-f%.f' in `seq -f%.f 1048575 1024 1050623', 1435 for example, since the default format now has the same effect. 1436 1437 seq now lets you use %a, %A, %E, %F, and %G formats. 1438 1439 seq now uses long double internally rather than double. 1440 1441 sort now reports incompatible options (e.g., -i and -n) rather than 1442 silently ignoring one of them. 1443 1444 stat's --format=FMT option now works the way it did before 5.3.0: 1445 FMT is automatically newline terminated. The first stable release 1446 containing this change was 5.92. 1447 1448 stat accepts the new option --printf=FMT, where FMT is *not* 1449 automatically newline terminated. 1450 1451 stat: backslash escapes are interpreted in a format string specified 1452 via --printf=FMT, but not one specified via --format=FMT. That includes 1453 octal (\ooo, at most three octal digits), hexadecimal (\xhh, one or 1454 two hex digits), and the standard sequences (\a, \b, \f, \n, \r, \t, 1455 \v, \", \\). 1456 1457 With no operand, 'tail -f' now silently ignores the '-f' only if 1458 standard input is a FIFO or pipe and POSIXLY_CORRECT is set. 1459 Formerly, it ignored the '-f' when standard input was a FIFO, pipe, 1460 or socket. 1461 1462** Scheduled for removal 1463 1464 ptx's --copyright (-C) option is scheduled for removal in 2007, and 1465 now evokes a warning. Use --version instead. 1466 1467 rm's --directory (-d) option is scheduled for removal in 2006. This 1468 option has been silently ignored since coreutils 5.0. On systems 1469 that support unlinking of directories, you can use the "unlink" 1470 command to unlink a directory. 1471 1472 Similarly, we are considering the removal of ln's --directory (-d, 1473 -F) option in 2006. Please write to <bug-coreutils@gnu.org> if this 1474 would cause a problem for you. On systems that support hard links 1475 to directories, you can use the "link" command to create one. 1476 1477** New programs 1478 1479 base64: base64 encoding and decoding (RFC 3548) functionality. 1480 sha224sum: print or check a SHA224 (224-bit) checksum 1481 sha256sum: print or check a SHA256 (256-bit) checksum 1482 sha384sum: print or check a SHA384 (384-bit) checksum 1483 sha512sum: print or check a SHA512 (512-bit) checksum 1484 shuf: Shuffle lines of text. 1485 1486** New features 1487 1488 chgrp now supports --preserve-root, --no-preserve-root (default), 1489 as it was documented to do, and just as chmod, chown, and rm do. 1490 1491 New dd iflag= and oflag= flags: 1492 1493 'directory' causes dd to fail unless the file is a directory, on 1494 hosts that support this (e.g., Linux kernels, version 2.1.126 and 1495 later). This has limited utility but is present for completeness. 1496 1497 'noatime' causes dd to read a file without updating its access 1498 time, on hosts that support this (e.g., Linux kernels, version 1499 2.6.8 and later). 1500 1501 'nolinks' causes dd to fail if the file has multiple hard links, 1502 on hosts that support this (e.g., Solaris 10 and later). 1503 1504 ls accepts the new option --group-directories-first, to make it 1505 list directories before files. 1506 1507 rm now accepts the -I (--interactive=once) option. This new option 1508 prompts once if rm is invoked recursively or if more than three 1509 files are being deleted, which is less intrusive than -i prompting 1510 for every file, but provides almost the same level of protection 1511 against mistakes. 1512 1513 shred and sort now accept the --random-source option. 1514 1515 sort now accepts the --random-sort (-R) option and `R' ordering option. 1516 1517 sort now supports obsolete usages like "sort +1 -2" unless 1518 POSIXLY_CORRECT is set. However, when conforming to POSIX 1519 1003.1-2001 "sort +1" still sorts the file named "+1". 1520 1521 wc accepts a new option --files0-from=FILE, where FILE contains a 1522 list of NUL-terminated file names. 1523 1524** Bug fixes 1525 1526 cat with any of the options, -A -v -e -E -T, when applied to a 1527 file in /proc or /sys (linux-specific), would truncate its output, 1528 usually printing nothing. 1529 1530 cp -p would fail in a /proc-less chroot, on some systems 1531 1532 When `cp -RL' encounters the same directory more than once in the 1533 hierarchy beneath a single command-line argument, it no longer confuses 1534 them with hard-linked directories. 1535 1536 fts-using tools (chmod, chown, chgrp, du) no longer fail due to 1537 a double-free bug -- it could be triggered by making a directory 1538 inaccessible while e.g., du is traversing the hierarchy under it. 1539 1540 fts-using tools (chmod, chown, chgrp, du) no longer misinterpret 1541 a very long symlink chain as a dangling symlink. Before, such a 1542 misinterpretation would cause these tools not to diagnose an ELOOP error. 1543 1544 ls --indicator-style=file-type would sometimes stat a symlink 1545 unnecessarily. 1546 1547 ls --file-type worked like --indicator-style=slash (-p), 1548 rather than like --indicator-style=file-type. 1549 1550 mv: moving a symlink into the place of an existing non-directory is 1551 now done atomically; before, mv would first unlink the destination. 1552 1553 mv -T DIR EMPTY_DIR no longer fails unconditionally. Also, mv can 1554 now remove an empty destination directory: mkdir -p a b/a; mv a b 1555 1556 rm (on systems with openat) can no longer exit before processing 1557 all command-line arguments. 1558 1559 rm is no longer susceptible to a few low-probability memory leaks. 1560 1561 rm -r no longer fails to remove an inaccessible and empty directory 1562 1563 rm -r's cycle detection code can no longer be tricked into reporting 1564 a false positive (introduced in fileutils-4.1.9). 1565 1566 shred --remove FILE no longer segfaults on Gentoo systems 1567 1568 sort would fail for large inputs (~50MB) on systems with a buggy 1569 mkstemp function. sort and tac now use the replacement mkstemp 1570 function, and hence are no longer subject to limitations (of 26 or 32, 1571 on the maximum number of files from a given template) on HP-UX 10.20, 1572 SunOS 4.1.4, Solaris 2.5.1 and OSF1/Tru64 V4.0F&V5.1. 1573 1574 tail -f once again works on a file with the append-only 1575 attribute (affects at least Linux ext2, ext3, xfs file systems) 1576 1577* Major changes in release 5.97 (2006-06-24) [stable] 1578* Major changes in release 5.96 (2006-05-22) [stable] 1579* Major changes in release 5.95 (2006-05-12) [stable] 1580* Major changes in release 5.94 (2006-02-13) [stable] 1581 1582[see the b5_9x branch for details] 1583 1584* Major changes in release 5.93 (2005-11-06) [stable] 1585 1586** Bug fixes 1587 1588 dircolors no longer segfaults upon an attempt to use the new 1589 STICKY_OTHER_WRITABLE (OWT) attribute. 1590 1591 du no longer overflows a counter when processing a file larger than 1592 2^31-1 on some 32-bit systems (at least some AIX 5.1 configurations). 1593 1594 md5sum once again defaults to using the ` ' non-binary marker 1595 (rather than the `*' binary marker) by default on Unix-like systems. 1596 1597 mkdir -p and install -d no longer exit nonzero when asked to create 1598 a directory like `nonexistent/.' 1599 1600 rm emits a better diagnostic when (without -r) it fails to remove 1601 a directory on e.g., Solaris 9/10 systems. 1602 1603 tac now works when stdin is a tty, even on non-Linux systems. 1604 1605 "tail -c 2 FILE" and "touch 0101000000" now operate as POSIX 1606 1003.1-2001 requires, even when coreutils is conforming to older 1607 POSIX standards, as the newly-required behavior is upward-compatible 1608 with the old. 1609 1610 The documentation no longer mentions rm's --directory (-d) option. 1611 1612** Build-related bug fixes 1613 1614 installing .mo files would fail 1615 1616 1617* Major changes in release 5.92 (2005-10-22) [stable] 1618 1619** Bug fixes 1620 1621 chmod now diagnoses an invalid mode string starting with an octal digit 1622 1623 dircolors now properly quotes single-quote characters 1624 1625 1626* Major changes in release 5.91 (2005-10-17) [stable candidate] 1627 1628** Bug fixes 1629 1630 "mkdir -p /a/b/c" no longer fails merely because a leading prefix 1631 directory (e.g., /a or /a/b) exists on a read-only file system. 1632 1633** Removed options 1634 1635 tail's --allow-missing option has been removed. Use --retry instead. 1636 1637 stat's --link and -l options have been removed. 1638 Use --dereference (-L) instead. 1639 1640** Deprecated options 1641 1642 Using ls, du, or df with the --kilobytes option now evokes a warning 1643 that the long-named option is deprecated. Use `-k' instead. 1644 1645 du's long-named --megabytes option now evokes a warning. 1646 Use -m instead. 1647 1648 1649* Major changes in release 5.90 (2005-09-29) [unstable] 1650 1651** Bring back support for `head -NUM', `tail -NUM', etc. even when 1652 conforming to POSIX 1003.1-2001. The following changes apply only 1653 when conforming to POSIX 1003.1-2001; there is no effect when 1654 conforming to older POSIX versions. 1655 1656 The following usages now behave just as when conforming to older POSIX: 1657 1658 date -I 1659 expand -TAB1[,TAB2,...] 1660 fold -WIDTH 1661 head -NUM 1662 join -j FIELD 1663 join -j1 FIELD 1664 join -j2 FIELD 1665 join -o FIELD_NAME1 FIELD_NAME2... 1666 nice -NUM 1667 od -w 1668 pr -S 1669 split -NUM 1670 tail -[NUM][bcl][f] [FILE] 1671 1672 The following usages no longer work, due to the above changes: 1673 1674 date -I TIMESPEC (use `date -ITIMESPEC' instead) 1675 od -w WIDTH (use `od -wWIDTH' instead) 1676 pr -S STRING (use `pr -SSTRING' instead) 1677 1678 A few usages still have behavior that depends on which POSIX standard is 1679 being conformed to, and portable applications should beware these 1680 problematic usages. These include: 1681 1682 Problematic Standard-conforming replacement, depending on 1683 usage whether you prefer the behavior of: 1684 POSIX 1003.2-1992 POSIX 1003.1-2001 1685 sort +4 sort -k 5 sort ./+4 1686 tail +4 tail -n +4 tail ./+4 1687 tail - f tail f [see (*) below] 1688 tail -c 4 tail -c 10 ./4 tail -c4 1689 touch 12312359 f touch -t 12312359 f touch ./12312359 f 1690 uniq +4 uniq -s 4 uniq ./+4 1691 1692 (*) "tail - f" does not conform to POSIX 1003.1-2001; to read 1693 standard input and then "f", use the command "tail -- - f". 1694 1695 These changes are in response to decisions taken in the January 2005 1696 Austin Group standardization meeting. For more details, please see 1697 "Utility Syntax Guidelines" in the Minutes of the January 2005 1698 Meeting <http://www.opengroup.org/austin/docs/austin_239.html>. 1699 1700** Binary input and output are now implemented more consistently. 1701 These changes affect only platforms like MS-DOS that distinguish 1702 between binary and text files. 1703 1704 The following programs now always use text input/output: 1705 1706 expand unexpand 1707 1708 The following programs now always use binary input/output to copy data: 1709 1710 cp install mv shred 1711 1712 The following programs now always use binary input/output to copy 1713 data, except for stdin and stdout when it is a terminal. 1714 1715 head tac tail tee tr 1716 (cat behaves similarly, unless one of the options -bensAE is used.) 1717 1718 cat's --binary or -B option has been removed. It existed only on 1719 MS-DOS-like platforms, and didn't work as documented there. 1720 1721 md5sum and sha1sum now obey the -b or --binary option, even if 1722 standard input is a terminal, and they no longer report files to be 1723 binary if they actually read them in text mode. 1724 1725** Changes for better conformance to POSIX 1726 1727 cp, ln, mv, rm changes: 1728 1729 Leading white space is now significant in responses to yes-or-no questions. 1730 For example, if "rm" asks "remove regular file `foo'?" and you respond 1731 with " y" (i.e., space before "y"), it counts as "no". 1732 1733 dd changes: 1734 1735 On a QUIT or PIPE signal, dd now exits without printing statistics. 1736 1737 On hosts lacking the INFO signal, dd no longer treats the USR1 1738 signal as if it were INFO when POSIXLY_CORRECT is set. 1739 1740 If the file F is non-seekable and contains fewer than N blocks, 1741 then before copying "dd seek=N of=F" now extends F with zeroed 1742 blocks until F contains N blocks. 1743 1744 fold changes: 1745 1746 When POSIXLY_CORRECT is set, "fold file -3" is now equivalent to 1747 "fold file ./-3", not the obviously-erroneous "fold file ./-w3". 1748 1749 ls changes: 1750 1751 -p now marks only directories; it is equivalent to the new option 1752 --indicator-style=slash. Use --file-type or 1753 --indicator-style=file-type to get -p's old behavior. 1754 1755 nice changes: 1756 1757 Documentation and diagnostics now refer to "nicenesses" (commonly 1758 in the range -20...19) rather than "nice values" (commonly 0...39). 1759 1760 nohup changes: 1761 1762 nohup now ignores the umask when creating nohup.out. 1763 1764 nohup now closes stderr if it is a terminal and stdout is closed. 1765 1766 nohup now exits with status 127 (not 1) when given an invalid option. 1767 1768 pathchk changes: 1769 1770 It now rejects the empty name in the normal case. That is, 1771 "pathchk -p ''" now fails, and "pathchk ''" fails unless the 1772 current host (contra POSIX) allows empty file names. 1773 1774 The new -P option checks whether a file name component has leading "-", 1775 as suggested in interpretation "Austin-039:XCU:pathchk:pathchk -p" 1776 <http://www.opengroup.org/austin/interps/doc.tpl?gdid=6232>. 1777 It also rejects the empty name even if the current host accepts it; see 1778 <http://www.opengroup.org/austin/interps/doc.tpl?gdid=6233>. 1779 1780 The --portability option is now equivalent to -p -P. 1781 1782** Bug fixes 1783 1784 chmod, mkdir, mkfifo, and mknod formerly mishandled rarely-used symbolic 1785 permissions like =xX and =u, and did not properly diagnose some invalid 1786 strings like g+gr, ug,+x, and +1. These bugs have been fixed. 1787 1788 csplit could produce corrupt output, given input lines longer than 8KB 1789 1790 dd now computes statistics using a realtime clock (if available) 1791 rather than the time-of-day clock, to avoid glitches if the 1792 time-of-day is changed while dd is running. Also, it avoids 1793 using unsafe code in signal handlers; this fixes some core dumps. 1794 1795 expr and test now correctly compare integers of unlimited magnitude. 1796 1797 expr now detects integer overflow when converting strings to integers, 1798 rather than silently wrapping around. 1799 1800 ls now refuses to generate time stamps containing more than 1000 bytes, to 1801 foil potential denial-of-service attacks on hosts with very large stacks. 1802 1803 "mkdir -m =+x dir" no longer ignores the umask when evaluating "+x", 1804 and similarly for mkfifo and mknod. 1805 1806 "mkdir -p /tmp/a/b dir" no longer attempts to create the `.'-relative 1807 directory, dir (in /tmp/a), when, after creating /tmp/a/b, it is unable 1808 to return to its initial working directory. Similarly for "install -D 1809 file /tmp/a/b/file". 1810 1811 "pr -D FORMAT" now accepts the same formats that "date +FORMAT" does. 1812 1813 stat now exits nonzero if a file operand does not exist 1814 1815** Improved robustness 1816 1817 Date no longer needs to allocate virtual memory to do its job, 1818 so it can no longer fail due to an out-of-memory condition, 1819 no matter how large the result. 1820 1821** Improved portability 1822 1823 hostid now prints exactly 8 hexadecimal digits, possibly with leading zeros, 1824 and without any spurious leading "fff..." on 64-bit hosts. 1825 1826 nice now works on Darwin 7.7.0 in spite of its invalid definition of NZERO. 1827 1828 `rm -r' can remove all entries in a directory even when it is on a 1829 file system for which readdir is buggy and that was not checked by 1830 coreutils' old configure-time run-test. 1831 1832 sleep no longer fails when resumed after being suspended on linux-2.6.8.1, 1833 in spite of that kernel's buggy nanosleep implementation. 1834 1835** New features 1836 1837 chmod -w now complains if its behavior differs from what chmod a-w 1838 would do, and similarly for chmod -r, chmod -x, etc. 1839 1840 cp and mv: the --reply=X option is deprecated 1841 1842 date accepts the new option --rfc-3339=TIMESPEC. The old --iso-8601 (-I) 1843 option is deprecated; it still works, but new applications should avoid it. 1844 date, du, ls, and pr's time formats now support new %:z, %::z, %:::z 1845 specifiers for numeric time zone offsets like -07:00, -07:00:00, and -07. 1846 1847 dd has new iflag= and oflag= flags "binary" and "text", which have an 1848 effect only on nonstandard platforms that distinguish text from binary I/O. 1849 1850 dircolors now supports SETUID, SETGID, STICKY_OTHER_WRITABLE, 1851 OTHER_WRITABLE, and STICKY, with ls providing default colors for these 1852 categories if not specified by dircolors. 1853 1854 du accepts new options: --time[=TYPE] and --time-style=STYLE 1855 1856 join now supports a NUL field separator, e.g., "join -t '\0'". 1857 join now detects and reports incompatible options, e.g., "join -t x -t y", 1858 1859 ls no longer outputs an extra space between the mode and the link count 1860 when none of the listed files has an ACL. 1861 1862 md5sum --check now accepts multiple input files, and similarly for sha1sum. 1863 1864 If stdin is a terminal, nohup now redirects it from /dev/null to 1865 prevent the command from tying up an OpenSSH session after you logout. 1866 1867 "rm -FOO" now suggests "rm ./-FOO" if the file "-FOO" exists and 1868 "-FOO" is not a valid option. 1869 1870 stat -f -c %S outputs the fundamental block size (used for block counts). 1871 stat -f's default output format has been changed to output this size as well. 1872 stat -f recognizes file systems of type XFS and JFS 1873 1874 "touch -" now touches standard output, not a file named "-". 1875 1876 uname -a no longer generates the -p and -i outputs if they are unknown. 1877 1878* Major changes in release 5.3.0 (2005-01-08) [unstable] 1879 1880** Bug fixes 1881 1882 Several fixes to chgrp and chown for compatibility with POSIX and BSD: 1883 1884 Do not affect symbolic links by default. 1885 Now, operate on whatever a symbolic link points to, instead. 1886 To get the old behavior, use --no-dereference (-h). 1887 1888 --dereference now works, even when the specified owner 1889 and/or group match those of an affected symlink. 1890 1891 Check for incompatible options. When -R and --dereference are 1892 both used, then either -H or -L must also be used. When -R and -h 1893 are both used, then -P must be in effect. 1894 1895 -H, -L, and -P have no effect unless -R is also specified. 1896 If -P and -R are both specified, -h is assumed. 1897 1898 Do not optimize away the chown() system call when the file's owner 1899 and group already have the desired value. This optimization was 1900 incorrect, as it failed to update the last-changed time and reset 1901 special permission bits, as POSIX requires. 1902 1903 "chown : file", "chown '' file", and "chgrp '' file" now succeed 1904 without changing the uid or gid, instead of reporting an error. 1905 1906 Do not report an error if the owner or group of a 1907 recursively-encountered symbolic link cannot be updated because 1908 the file system does not support it. 1909 1910 chmod now accepts multiple mode-like options, e.g., "chmod -r -w f". 1911 1912 chown is no longer subject to a race condition vulnerability, when 1913 used with --from=O:G and without the (-h) --no-dereference option. 1914 1915 cut's --output-delimiter=D option works with abutting byte ranges. 1916 1917 dircolors's documentation now recommends that shell scripts eval 1918 "`dircolors`" rather than `dircolors`, to avoid shell expansion pitfalls. 1919 1920 du no longer segfaults when a subdirectory of an operand 1921 directory is removed while du is traversing that subdirectory. 1922 Since the bug was in the underlying fts.c module, it also affected 1923 chown, chmod, and chgrp. 1924 1925 du's --exclude-from=FILE and --exclude=P options now compare patterns 1926 against the entire name of each file, rather than against just the 1927 final component. 1928 1929 echo now conforms to POSIX better. It supports the \0ooo syntax for 1930 octal escapes, and \c now terminates printing immediately. If 1931 POSIXLY_CORRECT is set and the first argument is not "-n", echo now 1932 outputs all option-like arguments instead of treating them as options. 1933 1934 expand and unexpand now conform to POSIX better. They check for 1935 blanks (which can include characters other than space and tab in 1936 non-POSIX locales) instead of spaces and tabs. Unexpand now 1937 preserves some blanks instead of converting them to tabs or spaces. 1938 1939 "ln x d/" now reports an error if d/x is a directory and x a file, 1940 instead of incorrectly creating a link to d/x/x. 1941 1942 ls no longer segfaults on systems for which SIZE_MAX != (size_t) -1. 1943 1944 md5sum and sha1sum now report an error when given so many input 1945 lines that their line counter overflows, instead of silently 1946 reporting incorrect results. 1947 1948 Fixes for "nice": 1949 1950 If it fails to lower the niceness due to lack of permissions, 1951 it goes ahead and runs the command anyway, as POSIX requires. 1952 1953 It no longer incorrectly reports an error if the current niceness 1954 happens to be -1. 1955 1956 It no longer assumes that nicenesses range from -20 through 19. 1957 1958 It now consistently adjusts out-of-range nicenesses to the 1959 closest values in range; formerly it sometimes reported an error. 1960 1961 pathchk no longer accepts trailing options, e.g., "pathchk -p foo -b" 1962 now treats -b as a file name to check, not as an invalid option. 1963 1964 `pr --columns=N' was not equivalent to `pr -N' when also using 1965 either -s or -w. 1966 1967 pr now supports page numbers up to 2**64 on most hosts, and it 1968 detects page number overflow instead of silently wrapping around. 1969 pr now accepts file names that begin with "+" so long as the rest of 1970 the file name does not look like a page range. 1971 1972 printf has several changes: 1973 1974 It now uses 'intmax_t' (not 'long int') to format integers, so it 1975 can now format 64-bit integers on most modern hosts. 1976 1977 On modern hosts it now supports the C99-inspired %a, %A, %F conversion 1978 specs, the "'" and "0" flags, and the ll, j, t, and z length modifiers 1979 (this is compatible with recent Bash versions). 1980 1981 The printf command now rejects invalid conversion specifications 1982 like %#d, instead of relying on undefined behavior in the underlying 1983 printf function. 1984 1985 ptx now diagnoses invalid values for its --width=N (-w) 1986 and --gap-size=N (-g) options. 1987 1988 mv (when moving between partitions) no longer fails when 1989 operating on too many command-line-specified nonempty directories. 1990 1991 "readlink -f" is more compatible with prior implementations 1992 1993 rm (without -f) no longer hangs when attempting to remove a symlink 1994 to a file on an off-line NFS-mounted partition. 1995 1996 rm no longer gets a failed assertion under some unusual conditions. 1997 1998 rm no longer requires read access to the current directory. 1999 2000 "rm -r" would mistakenly fail to remove files under a directory 2001 for some types of errors (e.g., read-only file system, I/O error) 2002 when first encountering the directory. 2003 2004 "sort" fixes: 2005 2006 "sort -o -" now writes to a file named "-" instead of to standard 2007 output; POSIX requires this. 2008 2009 An unlikely race condition has been fixed where "sort" could have 2010 mistakenly removed a temporary file belonging to some other process. 2011 2012 "sort" no longer has O(N**2) behavior when it creates many temporary files. 2013 2014 tac can now handle regular, nonseekable files like Linux's 2015 /proc/modules. Before, it would produce no output for such a file. 2016 2017 tac would exit immediately upon I/O or temp-file creation failure. 2018 Now it continues on, processing any remaining command line arguments. 2019 2020 "tail -f" no longer mishandles pipes and fifos. With no operands, 2021 tail now ignores -f if standard input is a pipe, as POSIX requires. 2022 When conforming to POSIX 1003.2-1992, tail now supports the SUSv2 b 2023 modifier (e.g., "tail -10b file") and it handles some obscure cases 2024 more correctly, e.g., "tail +cl" now reads the file "+cl" rather 2025 than reporting an error, "tail -c file" no longer reports an error, 2026 and "tail - file" no longer reads standard input. 2027 2028 tee now exits when it gets a SIGPIPE signal, as POSIX requires. 2029 To get tee's old behavior, use the shell command "(trap '' PIPE; tee)". 2030 Also, "tee -" now writes to standard output instead of to a file named "-". 2031 2032 "touch -- MMDDhhmm[yy] file" is now equivalent to 2033 "touch MMDDhhmm[yy] file" even when conforming to pre-2001 POSIX. 2034 2035 tr no longer mishandles a second operand with leading "-". 2036 2037 who now prints user names in full instead of truncating them after 8 bytes. 2038 2039 The following commands now reject unknown options instead of 2040 accepting them as operands, so that users are properly warned that 2041 options may be added later. Formerly they accepted unknown options 2042 as operands; e.g., "basename -a a" acted like "basename -- -a a". 2043 2044 basename dirname factor hostname link nohup sync unlink yes 2045 2046** New features 2047 2048 For efficiency, `sort -m' no longer copies input to a temporary file 2049 merely because the input happens to come from a pipe. As a result, 2050 some relatively-contrived examples like `cat F | sort -m -o F - G' 2051 are no longer safe, as `sort' might start writing F before `cat' is 2052 done reading it. This problem cannot occur unless `-m' is used. 2053 2054 When outside the default POSIX locale, the 'who' and 'pinky' 2055 commands now output time stamps like "2004-06-21 13:09" instead of 2056 the traditional "Jun 21 13:09". 2057 2058 pwd now works even when run from a working directory whose name 2059 is longer than PATH_MAX. 2060 2061 cp, install, ln, and mv have a new --no-target-directory (-T) option, 2062 and -t is now a short name for their --target-directory option. 2063 2064 cp -pu and mv -u (when copying) now don't bother to update the 2065 destination if the resulting time stamp would be no newer than the 2066 preexisting time stamp. This saves work in the common case when 2067 copying or moving multiple times to the same destination in a file 2068 system with a coarse time stamp resolution. 2069 2070 cut accepts a new option, --complement, to complement the set of 2071 selected bytes, characters, or fields. 2072 2073 dd now also prints the number of bytes transferred, the time, and the 2074 transfer rate. The new "status=noxfer" operand suppresses this change. 2075 2076 dd has new conversions for the conv= option: 2077 2078 nocreat do not create the output file 2079 excl fail if the output file already exists 2080 fdatasync physically write output file data before finishing 2081 fsync likewise, but also write metadata 2082 2083 dd has new iflag= and oflag= options with the following flags: 2084 2085 append append mode (makes sense for output file only) 2086 direct use direct I/O for data 2087 dsync use synchronized I/O for data 2088 sync likewise, but also for metadata 2089 nonblock use non-blocking I/O 2090 nofollow do not follow symlinks 2091 noctty do not assign controlling terminal from file 2092 2093 stty now provides support (iutf8) for setting UTF-8 input mode. 2094 2095 With stat, a specified format is no longer automatically newline terminated. 2096 If you want a newline at the end of your output, append `\n' to the format 2097 string. 2098 2099 'df', 'du', and 'ls' now take the default block size from the 2100 BLOCKSIZE environment variable if the BLOCK_SIZE, DF_BLOCK_SIZE, 2101 DU_BLOCK_SIZE, and LS_BLOCK_SIZE environment variables are not set. 2102 Unlike the other variables, though, BLOCKSIZE does not affect 2103 values like 'ls -l' sizes that are normally displayed as bytes. 2104 This new behavior is for compatibility with BSD. 2105 2106 du accepts a new option --files0-from=FILE, where FILE contains a 2107 list of NUL-terminated file names. 2108 2109 Date syntax as used by date -d, date -f, and touch -d has been 2110 changed as follows: 2111 2112 Dates like `January 32' with out-of-range components are now rejected. 2113 2114 Dates can have fractional time stamps like 2004-02-27 14:19:13.489392193. 2115 2116 Dates can be entered via integer counts of seconds since 1970 when 2117 prefixed by `@'. For example, `@321' represents 1970-01-01 00:05:21 UTC. 2118 2119 Time zone corrections can now separate hours and minutes with a colon, 2120 and can follow standard abbreviations like "UTC". For example, 2121 "UTC +0530" and "+05:30" are supported, and are both equivalent to "+0530". 2122 2123 Date values can now have leading TZ="..." assignments that override 2124 the environment only while that date is being processed. For example, 2125 the following shell command converts from Paris to New York time: 2126 2127 TZ="America/New_York" date --date='TZ="Europe/Paris" 2004-10-31 06:30' 2128 2129 `date' has a new option --iso-8601=ns that outputs 2130 nanosecond-resolution time stamps. 2131 2132 echo -e '\xHH' now outputs a byte whose hexadecimal value is HH, 2133 for compatibility with bash. 2134 2135 ls now exits with status 1 on minor problems, 2 if serious trouble. 2136 2137 ls has a new --hide=PATTERN option that behaves like 2138 --ignore=PATTERN, except that it is overridden by -a or -A. 2139 This can be useful for aliases, e.g., if lh is an alias for 2140 "ls --hide='*~'", then "lh -A" lists the file "README~". 2141 2142 In the following cases POSIX allows the default GNU behavior, 2143 so when POSIXLY_CORRECT is set: 2144 2145 false, printf, true, unlink, and yes all support --help and --option. 2146 ls supports TABSIZE. 2147 pr no longer depends on LC_TIME for the date format in non-POSIX locales. 2148 printf supports \u, \U, \x. 2149 tail supports two or more files when using the obsolete option syntax. 2150 2151 The usual `--' operand is now supported by chroot, hostid, hostname, 2152 pwd, sync, and yes. 2153 2154 `od' now conforms to POSIX better, and is more compatible with BSD: 2155 2156 The older syntax "od [-abcdfilosx]... [FILE] [[+]OFFSET[.][b]]" now works 2157 even without --traditional. This is a change in behavior if there 2158 are one or two operands and the last one begins with +, or if 2159 there are two operands and the latter one begins with a digit. 2160 For example, "od foo 10" and "od +10" now treat the last operand as 2161 an offset, not as a file name. 2162 2163 -h is no longer documented, and may be withdrawn in future versions. 2164 Use -x or -t x2 instead. 2165 2166 -i is now equivalent to -t dI (not -t d2), and 2167 -l is now equivalent to -t dL (not -t d4). 2168 2169 -s is now equivalent to -t d2. The old "-s[NUM]" or "-s NUM" 2170 option has been renamed to "-S NUM". 2171 2172 The default output format is now -t oS, not -t o2, i.e., short int 2173 rather than two-byte int. This makes a difference only on hosts like 2174 Cray systems where the C short int type requires more than two bytes. 2175 2176 readlink accepts new options: --canonicalize-existing (-e) 2177 and --canonicalize-missing (-m). 2178 2179 The stat option --filesystem has been renamed to --file-system, for 2180 consistency with POSIX "file system" and with cp and du --one-file-system. 2181 2182** Removed features 2183 2184 md5sum and sha1sum's undocumented --string option has been removed. 2185 2186 tail's undocumented --max-consecutive-size-changes option has been removed. 2187 2188* Major changes in release 5.2.1 (2004-03-12) [stable] 2189 2190** Bug fixes 2191 2192 mv could mistakenly fail to preserve hard links when moving two 2193 or more arguments between partitions. 2194 2195 `cp --sparse=always F /dev/hdx' no longer tries to use lseek to create 2196 holes in the destination. 2197 2198 nohup now sets the close-on-exec flag for its copy of the stderr file 2199 descriptor. This avoids some nohup-induced hangs. For example, before 2200 this change, if you ran `ssh localhost', then `nohup sleep 600 </dev/null &', 2201 and then exited that remote shell, the ssh session would hang until the 2202 10-minute sleep terminated. With the fixed nohup, the ssh session 2203 terminates immediately. 2204 2205 `expr' now conforms to POSIX better: 2206 2207 Integers like -0 and 00 are now treated as zero. 2208 2209 The `|' operator now returns 0, not its first argument, if both 2210 arguments are null or zero. E.g., `expr "" \| ""' now returns 0, 2211 not the empty string. 2212 2213 The `|' and `&' operators now use short-circuit evaluation, e.g., 2214 `expr 1 \| 1 / 0' no longer reports a division by zero. 2215 2216** New features 2217 2218 `chown user.group file' now has its traditional meaning even when 2219 conforming to POSIX 1003.1-2001, so long as no user has a name 2220 containing `.' that happens to equal `user.group'. 2221 2222 2223* Major changes in release 5.2.0 (2004-02-19) [stable] 2224 2225** Bug fixes 2226 2227 none 2228 2229 2230* Major changes in release 5.1.3 (2004-02-08): candidate to become stable 5.2.0 2231 2232** Bug fixes 2233 2234 `cp -d' now works as required even on systems like OSF V5.1 that 2235 declare stat and lstat as `static inline' functions. 2236 2237 time stamps output by stat now include actual fractional seconds, 2238 when available -- or .0000000 for files without that information. 2239 2240 seq no longer infloops when printing 2^31 or more numbers. 2241 For reference, seq `echo 2^31|bc` > /dev/null takes about one hour 2242 on a 1.6 GHz Athlon 2000 XP. Now it can output 2^53-1 numbers before 2243 misbehaving. 2244 2245* Major changes in release 5.1.2 (2004-01-25): 2246 2247** Bug fixes 2248 2249 rmdir -p exits with status 1 on error; formerly it sometimes exited 2250 with status 0 when given more than one argument. 2251 2252 nohup now always exits with status 127 when it finds an error, 2253 as POSIX requires; formerly it sometimes exited with status 1. 2254 2255 Several programs (including cut, date, dd, env, hostname, nl, pr, 2256 stty, and tr) now always exit with status 1 when they find an error; 2257 formerly they sometimes exited with status 2. 2258 2259 factor no longer reports a usage error if stdin has the wrong format. 2260 2261 paste no longer infloops on ppc systems (bug introduced in 5.1.1) 2262 2263 2264* Major changes in release 5.1.1 (2004-01-17): 2265 2266** Configuration option 2267 2268 You can select the default level of POSIX conformance at configure-time, 2269 e.g., by ./configure DEFAULT_POSIX2_VERSION=199209 2270 2271** Bug fixes 2272 2273 fold -s works once again on systems with differing sizes for int 2274 and size_t (bug introduced in 5.1.0) 2275 2276** New features 2277 2278 touch -r now specifies the origin for any relative times in the -d 2279 operand, if both options are given. For example, "touch -r FOO -d 2280 '-5 seconds' BAR" sets BAR's modification time to be five seconds 2281 before FOO's. 2282 2283 join: The obsolete options "-j1 FIELD", "-j2 FIELD", and 2284 "-o LIST1 LIST2..." are no longer supported on POSIX 1003.1-2001 systems. 2285 Portable scripts should use "-1 FIELD", "-2 FIELD", and 2286 "-o LIST1,LIST2..." respectively. If join was compiled on a 2287 POSIX 1003.1-2001 system, you may enable the old behavior 2288 by setting _POSIX2_VERSION=199209 in your environment. 2289 [This change was reverted in coreutils 5.3.1.] 2290 2291 2292* Major changes in release 5.1.0 (2003-12-21): 2293 2294** New features 2295 2296 chgrp, chmod, and chown can now process (with -R) hierarchies of virtually 2297 unlimited depth. Before, they would fail to operate on any file they 2298 encountered with a relative name of length PATH_MAX (often 4096) or longer. 2299 2300 chgrp, chmod, chown, and rm accept the new options: 2301 --preserve-root, --no-preserve-root (default) 2302 2303 chgrp and chown now accept POSIX-mandated -L, -H, and -P options 2304 2305 du can now process hierarchies of virtually unlimited depth. 2306 Before, du was limited by the user's stack size and it would get a 2307 stack overflow error (often a segmentation fault) when applied to 2308 a hierarchy of depth around 30,000 or larger. 2309 2310 du works even when run from an inaccessible directory 2311 2312 du -D now dereferences all symlinks specified on the command line, 2313 not just the ones that reference directories 2314 2315 du now accepts -P (--no-dereference), for compatibility with du 2316 of NetBSD and for consistency with e.g., chown and chgrp 2317 2318 du's -H option will soon have the meaning required by POSIX 2319 (--dereference-args, aka -D) rather then the current meaning of --si. 2320 Now, using -H elicits a warning to that effect. 2321 2322 When given -l and similar options, ls now adjusts the output column 2323 widths to fit the data, so that output lines are shorter and have 2324 columns that line up better. This may adversely affect shell 2325 scripts that expect fixed-width columns, but such shell scripts were 2326 not portable anyway, even with old GNU ls where the columns became 2327 ragged when a datum was too wide. 2328 2329 du accepts a new option, -0/--null, to make it produce NUL-terminated 2330 output lines 2331 2332** Bug fixes 2333 2334 printf, seq, tail, and sleep now parse floating-point operands 2335 and options in the C locale. POSIX requires this for printf. 2336 2337 od -c -w9999999 no longer segfaults 2338 2339 csplit no longer reads from freed memory (dumping core on some systems) 2340 2341 csplit would mistakenly exhaust virtual memory in some cases 2342 2343 ls --width=N (for very large N) is no longer subject to an address 2344 arithmetic bug that could result in bounds violations. 2345 2346 ls --width=N (with -x or -C) no longer allocates more space 2347 (potentially much more) than necessary for a given directory. 2348 2349 dd `unblock' and `sync' may now be combined (e.g., dd conv=unblock,sync) 2350 2351* Major changes in release 5.0.91 (2003-09-08): 2352 2353** New features 2354 2355 date accepts a new option --rfc-2822, an alias for --rfc-822. 2356 2357 split accepts a new option -d or --numeric-suffixes. 2358 2359 cp, install, mv, and touch now preserve microsecond resolution on 2360 file timestamps, on platforms that have the 'utimes' system call. 2361 Unfortunately there is no system call yet to preserve file 2362 timestamps to their full nanosecond resolution; microsecond 2363 resolution is the best we can do right now. 2364 2365 sort now supports the zero byte (NUL) as a field separator; use -t '\0'. 2366 The -t '' option, which formerly had no effect, is now an error. 2367 2368 sort option order no longer matters for the options -S, -d, -i, -o, and -t. 2369 Stronger options override weaker, and incompatible options are diagnosed. 2370 2371 `sha1sum --check' now accepts the BSD format for SHA1 message digests 2372 in addition to the BSD format for MD5 ones. 2373 2374 who -l now means `who --login', not `who --lookup', per POSIX. 2375 who's -l option has been eliciting an unconditional warning about 2376 this impending change since sh-utils-2.0.12 (April 2002). 2377 2378** Bug fixes 2379 2380 Mistakenly renaming a file onto itself, e.g., via `mv B b' when `B' is 2381 the same directory entry as `b' no longer destroys the directory entry 2382 referenced by both `b' and `B'. Note that this would happen only on 2383 file systems like VFAT where two different names may refer to the same 2384 directory entry, usually due to lower->upper case mapping of file names. 2385 Now, the above can happen only on file systems that perform name mapping and 2386 that support hard links (stat.st_nlink > 1). This mitigates the problem 2387 in two ways: few file systems appear to be affected (hpfs and ntfs are), 2388 when the bug is triggered, mv no longer removes the last hard link to a file. 2389 *** ATTENTION ***: if you know how to distinguish the following two cases 2390 without writing to the file system in question, please let me know: 2391 1) B and b refer to the same directory entry on a file system like NTFS 2392 (B may well have a link count larger than 1) 2393 2) B and b are hard links to the same file 2394 2395 stat no longer overruns a buffer for format strings ending in `%' 2396 2397 fold -s -wN would infloop for N < 8 with TABs in the input. 2398 E.g., this would not terminate: printf 'a\t' | fold -w2 -s 2399 2400 `split -a0', although of questionable utility, is accepted once again. 2401 2402 `df DIR' used to hang under some conditions on OSF/1 5.1. Now it doesn't. 2403 2404 seq's --width (-w) option now works properly even when the endpoint 2405 requiring the larger width is negative and smaller than the other endpoint. 2406 2407 seq's default step is 1, even if LAST < FIRST. 2408 2409 paste no longer mistakenly outputs 0xFF bytes for a nonempty input file 2410 without a trailing newline. 2411 2412 `tail -n0 -f FILE' and `tail -c0 -f FILE' no longer perform what amounted 2413 to a busy wait, rather than sleeping between iterations. 2414 2415 tail's long-undocumented --allow-missing option now elicits a warning 2416 2417 2418* Major changes in release 5.0.90 (2003-07-29): 2419 2420** New features 2421 2422 sort is now up to 30% more CPU-efficient in some cases 2423 2424 `test' is now more compatible with Bash and POSIX: 2425 2426 `test -t', `test --help', and `test --version' now silently exit 2427 with status 0. To test whether standard output is a terminal, use 2428 `test -t 1'. To get help and version info for `test', use 2429 `[ --help' and `[ --version'. 2430 2431 `test' now exits with status 2 (not 1) if there is an error. 2432 2433 wc count field widths now are heuristically adjusted depending on the input 2434 size, if known. If only one count is printed, it is guaranteed to 2435 be printed without leading spaces. 2436 2437 Previously, wc did not align the count fields if POSIXLY_CORRECT was set, 2438 but POSIX did not actually require this undesirable behavior, so it 2439 has been removed. 2440 2441** Bug fixes 2442 2443 kill no longer tries to operate on argv[0] (introduced in 5.0.1) 2444 Why wasn't this noticed? Although many tests use kill, none of 2445 them made an effort to avoid using the shell's built-in kill. 2446 2447 `[' invoked with no arguments no longer evokes a segfault 2448 2449 rm without --recursive (aka -r or -R) no longer prompts regarding 2450 unwritable directories, as required by POSIX. 2451 2452 uniq -c now uses a SPACE, not a TAB between the count and the 2453 corresponding line, as required by POSIX. 2454 2455 expr now exits with status 2 if the expression is syntactically valid, 2456 and with status 3 if an error occurred. POSIX requires this. 2457 2458 expr now reports trouble if string comparison fails due to a collation error. 2459 2460 split now generates suffixes properly on EBCDIC hosts. 2461 2462 split -a0 now works, as POSIX requires. 2463 2464 `sort --version' and `sort --help' fail, as they should 2465 when their output is redirected to /dev/full. 2466 2467 `su --version > /dev/full' now fails, as it should. 2468 2469** Fewer arbitrary limitations 2470 2471 cut requires 97% less memory when very large field numbers or 2472 byte offsets are specified. 2473 2474 2475* Major changes in release 5.0.1 (2003-07-15): 2476 2477** New programs 2478- new program: `[' (much like `test') 2479 2480** New features 2481- head now accepts --lines=-N (--bytes=-N) to print all but the 2482 N lines (bytes) at the end of the file 2483- md5sum --check now accepts the output of the BSD md5sum program, e.g., 2484 MD5 (f) = d41d8cd98f00b204e9800998ecf8427e 2485- date -d DATE can now parse a DATE string like May-23-2003 2486- chown: `.' is no longer recognized as a separator in the OWNER:GROUP 2487 specifier on POSIX 1003.1-2001 systems. If chown *was not* compiled 2488 on such a system, then it still accepts `.', by default. If chown 2489 was compiled on a POSIX 1003.1-2001 system, then you may enable the 2490 old behavior by setting _POSIX2_VERSION=199209 in your environment. 2491- chown no longer tries to preserve set-user-ID and set-group-ID bits; 2492 on some systems, the chown syscall resets those bits, and previous 2493 versions of the chown command would call chmod to restore the original, 2494 pre-chown(2) settings, but that behavior is problematic. 2495 1) There was a window whereby a malicious user, M, could subvert a 2496 chown command run by some other user and operating on files in a 2497 directory where M has write access. 2498 2) Before (and even now, on systems with chown(2) that doesn't reset 2499 those bits), an unwary admin. could use chown unwittingly to create e.g., 2500 a set-user-ID root copy of /bin/sh. 2501 2502** Bug fixes 2503- chown --dereference no longer leaks a file descriptor per symlink processed 2504- `du /' once again prints the `/' on the last line 2505- split's --verbose option works once again [broken in 4.5.10 and 5.0] 2506- tail -f is no longer subject to a race condition that could make it 2507 delay displaying the last part of a file that had stopped growing. That 2508 bug could also make tail -f give an unwarranted `file truncated' warning. 2509- du no longer runs out of file descriptors unnecessarily 2510- df and `readlink --canonicalize' no longer corrupt the heap on 2511 non-glibc, non-solaris systems 2512- `env -u UNSET_VARIABLE' no longer dumps core on non-glibc systems 2513- readlink's --canonicalize option now works on systems like Solaris that 2514 lack the canonicalize_file_name function but do have resolvepath. 2515- mv now removes `a' in this example on all systems: touch a; ln a b; mv a b 2516 This behavior is contrary to POSIX (which requires that the mv command do 2517 nothing and exit successfully), but I suspect POSIX will change. 2518- date's %r format directive now honors locale settings 2519- date's `-' (no-pad) format flag now affects the space-padded-by-default 2520 conversion specifiers, %e, %k, %l 2521- fmt now diagnoses invalid obsolescent width specifications like `-72x' 2522- fmt now exits nonzero when unable to open an input file 2523- tsort now fails when given an odd number of input tokens, 2524 as required by POSIX. Before, it would act as if the final token 2525 appeared one additional time. 2526 2527** Fewer arbitrary limitations 2528- tail's byte and line counts are no longer limited to OFF_T_MAX. 2529 Now the limit is UINTMAX_MAX (usually 2^64). 2530- split can now handle --bytes=N and --lines=N with N=2^31 or more. 2531 2532** Portability 2533- `kill -t' now prints signal descriptions (rather than `?') on systems 2534 like Tru64 with __sys_siglist but no strsignal function. 2535- stat.c now compiles on Ultrix systems 2536- sleep now works on AIX systems that lack support for clock_gettime 2537- rm now works around Darwin6.5's broken readdir function 2538 Before `rm -rf DIR' would fail to remove all files in DIR 2539 if there were more than 338. 2540 2541* Major changes in release 5.0 (2003-04-02): 2542- false --help now exits nonzero 2543 2544[4.5.12] 2545* printf no longer treats \x specially when POSIXLY_CORRECT is set 2546* printf avoids buffer overrun with format ending in a backslash and 2547* printf avoids buffer overrun with incomplete conversion specifier 2548* printf accepts multiple flags in a single conversion specifier 2549 2550[4.5.11] 2551* seq no longer requires that a field width be specified 2552* seq no longer fails when given a field width of `0' 2553* seq now accepts ` ' and `'' as valid format flag characters 2554* df now shows a HOSTNAME: prefix for each remote-mounted file system on AIX 5.1 2555* portability tweaks for HP-UX, AIX 5.1, DJGPP 2556 2557[4.5.10] 2558* printf no longer segfaults for a negative field width or precision 2559* shred now always enables --exact for non-regular files 2560* du no longer lists hard-linked files more than once 2561* du no longer dumps core on some systems due to `infinite' recursion 2562 via nftw's use of the buggy replacement function in getcwd.c 2563* portability patches for a few vendor compilers and 64-bit systems 2564* du -S *really* now works like it did before the change in 4.5.5 2565 2566[4.5.9] 2567* du no longer truncates file sizes or sums to fit in 32-bit size_t 2568* work around Linux kernel bug in getcwd (fixed in 2.4.21-pre4), so that pwd 2569 now fails if the name of the working directory is so long that getcwd 2570 truncates it. Before it would print the truncated name and exit successfully. 2571* `df /some/mount-point' no longer hangs on a GNU libc system when another 2572 hard-mounted NFS file system (preceding /some/mount-point in /proc/mounts) 2573 is inaccessible. 2574* rm -rf now gives an accurate diagnostic when failing to remove a file 2575 under certain unusual conditions 2576* mv and `cp --preserve=links' now preserve multiple hard links even under 2577 certain unusual conditions where they used to fail 2578 2579[4.5.8] 2580* du -S once again works like it did before the change in 4.5.5 2581* stat accepts a new file format, %B, for the size of each block reported by %b 2582* du accepts new option: --apparent-size 2583* du --bytes (-b) works the same way it did in fileutils-3.16 and before 2584* du reports proper sizes for directories (not zero) (broken in 4.5.6 or 4.5.7) 2585* df now always displays under `Filesystem', the device file name 2586 corresponding to the listed mount point. Before, for a block- or character- 2587 special file command line argument, df would display that argument. E.g., 2588 `df /dev/hda' would list `/dev/hda' as the `Filesystem', rather than say 2589 /dev/hda3 (the device on which `/' is mounted), as it does now. 2590* test now works properly when invoked from a set user ID or set group ID 2591 context and when testing access to files subject to alternate protection 2592 mechanisms. For example, without this change, a set-UID program that invoked 2593 `test -w F' (to see if F is writable) could mistakenly report that it *was* 2594 writable, even though F was on a read-only file system, or F had an ACL 2595 prohibiting write access, or F was marked as immutable. 2596 2597[4.5.7] 2598* du would fail with more than one DIR argument when any but the last did not 2599 contain a slash (due to a bug in ftw.c) 2600 2601[4.5.6] 2602* du no longer segfaults on Solaris systems (fixed heap-corrupting bug in ftw.c) 2603* du --exclude=FILE works once again (this was broken by the rewrite for 4.5.5) 2604* du no longer gets a failed assertion for certain hierarchy lay-outs 2605 involving hard-linked directories 2606* `who -r' no longer segfaults when using non-C-locale messages 2607* df now displays a mount point (usually `/') for non-mounted 2608 character-special and block files 2609 2610[4.5.5] 2611* ls --dired produces correct byte offset for file names containing 2612 nonprintable characters in a multibyte locale 2613* du has been rewritten to use a variant of GNU libc's ftw.c 2614* du now counts the space associated with a directory's directory entry, 2615 even if it cannot list or chdir into that subdirectory. 2616* du -S now includes the st_size of each entry corresponding to a subdirectory 2617* rm on FreeBSD can once again remove directories from NFS-mounted file systems 2618* ls has a new option --dereference-command-line-symlink-to-dir, which 2619 corresponds to the new default behavior when none of -d, -l -F, -H, -L 2620 has been specified. 2621* ls dangling-symlink now prints `dangling-symlink'. 2622 Before, it would fail with `no such file or directory'. 2623* ls -s symlink-to-non-dir and ls -i symlink-to-non-dir now print 2624 attributes of `symlink', rather than attributes of their referents. 2625* Fix a bug introduced in 4.5.4 that made it so that ls --color would no 2626 longer highlight the names of files with the execute bit set when not 2627 specified on the command line. 2628* shred's --zero (-z) option no longer gobbles up any following argument. 2629 Before, `shred --zero file' would produce `shred: missing file argument', 2630 and worse, `shred --zero f1 f2 ...' would appear to work, but would leave 2631 the first file untouched. 2632* readlink: new program 2633* cut: new feature: when used to select ranges of byte offsets (as opposed 2634 to ranges of fields) and when --output-delimiter=STRING is specified, 2635 output STRING between ranges of selected bytes. 2636* rm -r can no longer be tricked into mistakenly reporting a cycle. 2637* when rm detects a directory cycle, it no longer aborts the entire command, 2638 but rather merely stops processing the affected command line argument. 2639 2640[4.5.4] 2641* cp no longer fails to parse options like this: --preserve=mode,ownership 2642* `ls --color -F symlink-to-dir' works properly 2643* ls is much more efficient on directories with valid dirent.d_type. 2644* stty supports all baud rates defined in linux-2.4.19. 2645* `du symlink-to-dir/' would improperly remove the trailing slash 2646* `du ""' would evoke a bounds violation. 2647* In the unlikely event that running `du /' resulted in `stat ("/", ...)' 2648 failing, du would give a diagnostic about `' (empty string) rather than `/'. 2649* printf: a hexadecimal escape sequence has at most two hex. digits, not three. 2650* The following features have been added to the --block-size option 2651 and similar environment variables of df, du, and ls. 2652 - A leading "'" generates numbers with thousands separators. 2653 For example: 2654 $ ls -l --block-size="'1" file 2655 -rw-rw-r-- 1 eggert src 47,483,707 Sep 24 23:40 file 2656 - A size suffix without a leading integer generates a suffix in the output. 2657 For example: 2658 $ ls -l --block-size="K" 2659 -rw-rw-r-- 1 eggert src 46371K Sep 24 23:40 file 2660* ls's --block-size option now affects file sizes in all cases, not 2661 just for --block-size=human-readable and --block-size=si. Fractional 2662 sizes are now always rounded up, for consistency with df and du. 2663* df now displays the block size using powers of 1000 if the requested 2664 block size seems to be a multiple of a power of 1000. 2665* nl no longer gets a segfault when run like this `yes|nl -s%n' 2666 2667[4.5.3] 2668* du --dereference-args (-D) no longer fails in certain cases 2669* `ln --target-dir=DIR' no longer fails when given a single argument 2670 2671[4.5.2] 2672* `rm -i dir' (without --recursive (-r)) no longer recurses into dir 2673* `tail -c N FILE' now works with files of size >= 4GB 2674* `mkdir -p' can now create very deep (e.g. 40,000-component) directories 2675* rmdir -p dir-with-trailing-slash/ no longer fails 2676* printf now honors the `--' command line delimiter 2677* od's 8-byte formats x8, o8, and u8 now work 2678* tail now accepts fractional seconds for its --sleep-interval=S (-s) option 2679 2680[4.5.1] 2681* du and ls now report sizes of symbolic links (before they'd always report 0) 2682* uniq now obeys the LC_COLLATE locale, as per POSIX 1003.1-2001 TC1. 2683 2684======================================================================== 2685Here are the NEWS entries made from fileutils-4.1 until the 2686point at which the packages merged to form the coreutils: 2687 2688[4.1.11] 2689* `rm symlink-to-unwritable' doesn't prompt [introduced in 4.1.10] 2690[4.1.10] 2691* rm once again gives a reasonable diagnostic when failing to remove a file 2692 owned by someone else in a sticky directory [introduced in 4.1.9] 2693* df now rounds all quantities up, as per POSIX. 2694* New ls time style: long-iso, which generates YYYY-MM-DD HH:MM. 2695* Any time style can be preceded by "posix-"; this causes "ls" to 2696 use traditional timestamp format when in the POSIX locale. 2697* The default time style is now posix-long-iso instead of posix-iso. 2698 Set TIME_STYLE="posix-iso" to revert to the behavior of 4.1.1 thru 4.1.9. 2699* `rm dangling-symlink' doesn't prompt [introduced in 4.1.9] 2700* stat: remove support for --secure/-s option and related %S and %C format specs 2701* stat: rename --link/-l to --dereference/-L. 2702 The old options will continue to work for a while. 2703[4.1.9] 2704* rm can now remove very deep hierarchies, in spite of any limit on stack size 2705* new programs: link, unlink, and stat 2706* New ls option: --author (for the Hurd). 2707* `touch -c no-such-file' no longer fails, per POSIX 2708[4.1.8] 2709* mv no longer mistakenly creates links to preexisting destination files 2710 that aren't moved 2711[4.1.7] 2712* rm: close a hole that would allow a running rm process to be subverted 2713[4.1.6] 2714* New cp option: --copy-contents. 2715* cp -r is now equivalent to cp -R. Use cp -R -L --copy-contents to get the 2716 traditional (and rarely desirable) cp -r behavior. 2717* ls now accepts --time-style=+FORMAT, where +FORMAT works like date's format 2718* The obsolete usage `touch [-acm] MMDDhhmm[YY] FILE...' is no longer 2719 supported on systems conforming to POSIX 1003.1-2001. Use touch -t instead. 2720* cp and inter-partition mv no longer give a misleading diagnostic in some 2721 unusual cases 2722[4.1.5] 2723* cp -r no longer preserves symlinks 2724* The block size notation is now compatible with SI and with IEC 60027-2. 2725 For example, --block-size=1MB now means --block-size=1000000, 2726 whereas --block-size=1MiB now means --block-size=1048576. 2727 A missing `B' (e.g. `1M') has the same meaning as before. 2728 A trailing `B' now means decimal, not binary; this is a silent change. 2729 The nonstandard `D' suffix (e.g. `1MD') is now obsolescent. 2730* -H or --si now outputs the trailing 'B', for consistency with the above. 2731* Programs now output trailing 'K' (not 'k') to mean 1024, as per IEC 60027-2. 2732* New df, du short option -B is short for --block-size. 2733* You can omit an integer `1' before a block size suffix, 2734 e.g. `df -BG' is equivalent to `df -B 1G' and to `df --block-size=1G'. 2735* The following options are now obsolescent, as their names are 2736 incompatible with IEC 60027-2: 2737 df, du: -m or --megabytes (use -BM or --block-size=1M) 2738 df, du, ls: --kilobytes (use --block-size=1K) 2739[4.1.4] 2740* df --local no longer lists smbfs file systems whose name starts with // 2741* dd now detects the Linux/tape/lseek bug at run time and warns about it. 2742[4.1.3] 2743* ls -R once again outputs a blank line between per-directory groups of files. 2744 This was broken by the cycle-detection change in 4.1.1. 2745* dd once again uses `lseek' on character devices like /dev/mem and /dev/kmem. 2746 On systems with the linux kernel (at least up to 2.4.16), dd must still 2747 resort to emulating `skip=N' behavior using reads on tape devices, because 2748 lseek has no effect, yet appears to succeed. This may be a kernel bug. 2749[4.1.2] 2750* cp no longer fails when two or more source files are the same; 2751 now it just gives a warning and doesn't copy the file the second time. 2752 E.g., cp a a d/ produces this: 2753 cp: warning: source file `a' specified more than once 2754* chmod would set the wrong bit when given symbolic mode strings like 2755 these: g=o, o=g, o=u. E.g., `chmod a=,o=w,ug=o f' would give a mode 2756 of --w-r---w- rather than --w--w--w-. 2757[4.1.1] 2758* mv (likewise for cp), now fails rather than silently clobbering one of 2759 the source files in the following example: 2760 rm -rf a b c; mkdir a b c; touch a/f b/f; mv a/f b/f c 2761* ls -R detects directory cycles, per POSIX. It warns and doesn't infloop. 2762* cp's -P option now means the same as --no-dereference, per POSIX. 2763 Use --parents to get the old meaning. 2764* When copying with the -H and -L options, cp can preserve logical 2765 links between source files with --preserve=links 2766* cp accepts new options: 2767 --preserve[={mode,ownership,timestamps,links,all}] 2768 --no-preserve={mode,ownership,timestamps,links,all} 2769* cp's -p and --preserve options remain unchanged and are equivalent 2770 to `--preserve=mode,ownership,timestamps' 2771* mv and cp accept a new option: --reply={yes,no,query}; provides a consistent 2772 mechanism to control whether one is prompted about certain existing 2773 destination files. Note that cp's and mv's -f options don't have the 2774 same meaning: cp's -f option no longer merely turns off `-i'. 2775* remove portability limitations (e.g., PATH_MAX on the Hurd, fixes for 2776 64-bit systems) 2777* mv now prompts before overwriting an existing, unwritable destination file 2778 when stdin is a tty, unless --force (-f) is specified, as per POSIX. 2779* mv: fix the bug whereby `mv -uf source dest' would delete source, 2780 even though it's older than dest. 2781* chown's --from=CURRENT_OWNER:CURRENT_GROUP option now works 2782* cp now ensures that the set-user-ID and set-group-ID bits are cleared for 2783 the destination file when when copying and not preserving permissions. 2784* `ln -f --backup k k' gives a clearer diagnostic 2785* ls no longer truncates user names or group names that are longer 2786 than 8 characters. 2787* ls's new --dereference-command-line option causes it to dereference 2788 symbolic links on the command-line only. It is the default unless 2789 one of the -d, -F, or -l options are given. 2790* ls -H now means the same as ls --dereference-command-line, as per POSIX. 2791* ls -g now acts like ls -l, except it does not display owner, as per POSIX. 2792* ls -n now implies -l, as per POSIX. 2793* ls can now display dates and times in one of four time styles: 2794 2795 - The `full-iso' time style gives full ISO-style time stamps like 2796 `2001-05-14 23:45:56.477817180 -0700'. 2797 - The 'iso' time style gives ISO-style time stamps like '2001-05-14 ' 2798 and '05-14 23:45'. 2799 - The 'locale' time style gives locale-dependent time stamps like 2800 'touko 14 2001' and 'touko 14 23:45' (in a Finnish locale). 2801 - The 'posix-iso' time style gives traditional POSIX-locale 2802 time stamps like 'May 14 2001' and 'May 14 23:45' unless the user 2803 specifies a non-POSIX locale, in which case it uses ISO-style dates. 2804 This is the default. 2805 2806 You can specify a time style with an option like --time-style='iso' 2807 or with an environment variable like TIME_STYLE='iso'. GNU Emacs 21 2808 and later can parse ISO dates, but older Emacs versions cannot, so 2809 if you are using an older version of Emacs outside the default POSIX 2810 locale, you may need to set TIME_STYLE="locale". 2811 2812* --full-time is now an alias for "-l --time-style=full-iso". 2813 2814 2815======================================================================== 2816Here are the NEWS entries made from sh-utils-2.0 until the 2817point at which the packages merged to form the coreutils: 2818 2819 [2.0.15] 2820* date no longer accepts e.g., September 31 in the MMDDhhmm syntax 2821* fix a bug in this package's .m4 files and in configure.ac 2822 [2.0.14] 2823* nohup's behavior is changed as follows, to conform to POSIX 1003.1-2001: 2824 - nohup no longer adjusts scheduling priority; use "nice" for that. 2825 - nohup now redirects stderr to stdout, if stderr is not a terminal. 2826 - nohup exit status is now 126 if command was found but not invoked, 2827 127 if nohup failed or if command was not found. 2828 [2.0.13] 2829* uname and uptime work better on *BSD systems 2830* pathchk now exits nonzero for a path with a directory component 2831 that specifies a non-directory 2832 [2.0.12] 2833* kill: new program 2834* who accepts new options: --all (-a), --boot (-b), --dead (-d), --login, 2835 --process (-p), --runlevel (-r), --short (-s), --time (-t), --users (-u). 2836 The -u option now produces POSIX-specified results and is the same as 2837 the long option `--users'. --idle is no longer the same as -u. 2838* The following changes apply on systems conforming to POSIX 1003.1-2001: 2839 - `date -I' is no longer supported. Instead, use `date --iso-8601'. 2840 - `nice -NUM' is no longer supported. Instead, use `nice -n NUM'. 2841 [This change was reverted in coreutils 5.3.1.] 2842* New 'uname' options -i or --hardware-platform, and -o or --operating-system. 2843 'uname -a' now outputs -i and -o information at the end. 2844 New uname option --kernel-version is an alias for -v. 2845 Uname option --release has been renamed to --kernel-release, 2846 and --sysname has been renamed to --kernel-name; 2847 the old options will work for a while, but are no longer documented. 2848* 'expr' now uses the LC_COLLATE locale for string comparison, as per POSIX. 2849* 'expr' now requires '+' rather than 'quote' to quote tokens; 2850 this removes an incompatibility with POSIX. 2851* date -d 'last friday' would print a date/time that was one hour off 2852 (e.g., 23:00 on *thursday* rather than 00:00 of the preceding friday) 2853 when run such that the current time and the target date/time fall on 2854 opposite sides of a daylight savings time transition. 2855 This problem arose only with relative date strings like `last monday'. 2856 It was not a problem with strings that include absolute dates. 2857* factor is twice as fast, for large numbers 2858 [2.0.11] 2859* setting the date now works properly, even when using -u 2860* `date -f - < /dev/null' no longer dumps core 2861* some DOS/Windows portability changes 2862 [2.0j] 2863* `date -d DATE' now parses certain relative DATEs correctly 2864 [2.0i] 2865* fixed a bug introduced in 2.0h that made many programs fail with a 2866 `write error' when invoked with the --version option 2867 [2.0h] 2868* all programs fail when printing --help or --version output to a full device 2869* printf exits nonzero upon write failure 2870* yes now detects and terminates upon write failure 2871* date --rfc-822 now always emits day and month names from the `C' locale 2872* portability tweaks for Solaris8, Ultrix, and DOS 2873 [2.0g] 2874* date now handles two-digit years with leading zeros correctly. 2875* printf interprets unicode, \uNNNN \UNNNNNNNN, on systems with the 2876 required support; from Bruno Haible. 2877* stty's rprnt attribute now works on HPUX 10.20 2878* seq's --equal-width option works more portably 2879 [2.0f] 2880* fix build problems with ut_name vs. ut_user 2881 [2.0e] 2882* stty: fix long-standing bug that caused test failures on at least HPUX 2883 systems when COLUMNS was set to zero 2884* still more portability fixes 2885* unified lib/: now that directory and most of the configuration framework 2886 is common between fileutils, textutils, and sh-utils 2887 [2.0d] 2888* fix portability problem with sleep vs lib/strtod.c's requirement for -lm 2889 [2.0c] 2890* fix portability problems with nanosleep.c and with the new code in sleep.c 2891 [2.0b] 2892* Regenerate lib/Makefile.in so that nanosleep.c is distributed. 2893 [2.0a] 2894* sleep accepts floating point arguments on command line 2895* sleep's clock continues counting down when sleep is suspended 2896* when a suspended sleep process is resumed, it continues sleeping if 2897 there is any time remaining 2898* who once again prints whatever host information it has, even without --lookup 2899 2900======================================================================== 2901For older NEWS entries for the fileutils, textutils, and sh-utils 2902packages, see ./old/*/NEWS. 2903 2904 This package began as the union of the following: 2905 textutils-2.1, fileutils-4.1.11, sh-utils-2.0.15. 2906 2907======================================================================== 2908 2909Copyright (C) 2001-2010 Free Software Foundation, Inc. 2910 2911Permission is granted to copy, distribute and/or modify this document 2912under the terms of the GNU Free Documentation License, Version 1.3 or 2913any later version published by the Free Software Foundation; with no 2914Invariant Sections, with no Front-Cover Texts, and with no Back-Cover 2915Texts. A copy of the license is included in the ``GNU Free 2916Documentation License'' file as part of this distribution. 2917