X-Git-Url: https://git.dogcows.com/gitweb?a=blobdiff_plain;f=NEWS;h=36926e87af7950fef3475ede16c21a522da6cc05;hb=b68057816b2f880a8bd2e9747a9b75d60f7e1a4f;hp=4fcc0b5d35b5441677e8180b9de2de338f8b0ae4;hpb=f8baeb3fa0552692a4cea06ec5622103b4dddf2e;p=chaz%2Ftar diff --git a/NEWS b/NEWS index 4fcc0b5..36926e8 100644 --- a/NEWS +++ b/NEWS @@ -1,38 +1,355 @@ GNU tar NEWS - User visible changes. -Copyright © 1994, 1995-1998, 1999 Free Software Foundation, Inc. - -version 1.12.64012 - Paul Eggert, 1999-06-16. - -This is an unofficial port of GNU `tar' 1.12 to large file -environments like AIX 4.2, HP-UX 10.20, IRIX 6.2, and Solaris 2.6 that -(among other things) rely on integer system types longer than `long'. -Please send bug reports specific to this unofficial version of GNU `tar' -to . - -This is not intended to be a forked release for GNU tar; it's -just an interim experimental release, mostly intended for -large file hosts. The patches of this -release have all been (or will be) submitted via the usual channels and -they should no longer be needed once the next official release -of GNU tar is out. + +* New options --index-file, --no-overwrite-dir. The --overwrite-dir + option is now the default; use --no-overwrite-dir if you prefer + the previous default behavior. + +* New message translations en_GB (British English), fi (Finnish), gl + (Galician), hr (Croatian), hu (Hungarian), ms (Malaysian), nb + (Norwegian), ro (Romanian), sk (Slovak), zh_CN (Chinese simplified), + zh_TW (Chinese traditional). The code 'no' for Norwegian has been + withdrawn; use 'nb' instead. + +version 1.13.26 + +* Bug fixes. + +* The semantics of -o option is changed. When extracting, it +does the same as --no-same-owner GNU tar option. This is compatible +with UNIX98 tar. Otherwise, its effect is the same as that of +--old-archive option. This latter is deprecated and will be removed +in future. + +* New option --check-links prints a message if not all links are dumped +for a file being archived. This corresponds to the UNIX98 -l option. +The current semantics of the -l option is retained for compatibility +with previous releases, however such usage is strongly deprecated as +the option will change to its UNIX98 semantics in the future releases. + +version 1.13.25 - Paul Eggert, 2001-09-26 + +* Bug fixes. + +version 1.13.24 - Paul Eggert, 2001-09-22 + +* New option --overwrite-dir. +* Fixes for buffer overrun, porting, and copyright notice problems. +* The message translations for Korean are available again. + +version 1.13.23 - Paul Eggert, 2001-09-13 + +* Bug, porting, and copyright notice fixes. + +version 1.13.22 - Paul Eggert, 2001-08-29 + +* Bug fixes. + +version 1.13.21 - Paul Eggert, 2001-08-28 + +* Porting and copyright notice fixes. + +version 1.13.20 - Paul Eggert, 2001-08-27 + +* Some bugs were fixed: + - security problems + - hard links to symbolic links + +* New option --recursion (the default) that is the inverse of --no-recursion. + +* New options --anchored, --ignore-case, --wildcards, + --wildcards-match-slash, and their negations (e.g., --no-anchored). + Along with --recursion and --no-recursion, these options control how + exclude patterns are interpreted. + +* The default interpretation of exclude patterns is now --no-anchored + --no-ignore-case --recursion --wildcards --wildcards-match-slash. + This is a quiet change to the semantics of --exclude. The previous + semantics were a failed attempt at backward compatibility but it + became clear that the semantics were puzzling and did not satisfy + everybody. Rather than continue to try to revive that dead horse we + thought it better to substitute cleaner semantics, with options so + that you can change the behavior more to your liking. + +* New message translations for Indonesian and Turkish. + The translation for Korean has been withdrawn due to encoding errors. + It will be reissued once those are fixed. + +version 1.13.19 - Paul Eggert, 2001-01-13 + +* The -I option has been withdrawn, as it was buggy and confusing. + Eventually it is planned to be reintroduced, with the same meaning as -T. + +* With an option like -N DATE, if DATE starts with "/" or ".", it is taken + to be a file name; the last-modified time of that file is used as the date. + +version 1.13.18 - Paul Eggert, 2000-10-29 + +* Some security problems have been fixed. `tar -x' now modifies only + files under the working directory, unless you also specify an unsafe + option like --absolute-names or --overwrite. + +* The short name of the --bzip option has been changed to -j, + and -I is now an alias for -T, for compatibility with Solaris tar. + +* The manual is now distributed under the GNU Free Documentation License. + +* The new environment variable TAR_OPTIONS holds default command-line options. + +* The --no-recursion option now affects extraction too. + +* The wording in some diagnostics has been changed slightly. + +* Snapshot files now record whether each file was accessed via NFS. + The new file format is upward- and downward-compatible with the old. + +* New language supported: da. + +* Compilation by traditional (K&R) C compilers is no longer supported. + If you still use such a compiler, please use GCC instead. + +* This version of tar works best with GNU gzip test version 1.3 or later. + Please see . + +* `tar --delete -f -' now works again. + +version 1.13.17 - Paul Eggert, 2000-01-07. + +* `tar --delete -f -' is no longer allowed; it was too buggy. +* Diagnostic messages have been made more regular and consistent. + +version 1.13.16 - Paul Eggert, 1999-12-13. + +* By default, tar now refuses to overwrite an existing file when + extracting files from an archive; instead, it removes the file + before extracting it. If the existing file is a symbolic link, the + link is removed and not the pointed-to file. There is one + exception: existing nonempty directories are not removed, nor are + their ownerships or permissions extracted. This fixes some + longstanding security problems. + + The new --overwrite option enables the old default behavior. + + For regular files, tar implements this change by using the O_EXCL + option of `open' to ensure that it creates the file; if this fails, it + removes the file and tries again. This is similar to the behavior of + the --unlink-first option, but it is faster in the common case of + extracting a new directory. + +* By default, tar now ignores file names containing a component of `..' + when extracting, and warns about such file names when creating an archive. + To enable the old behavior, use the -P or --absolute-names option. + +* Tar now handles file names with multibyte encodings (e.g. UTF-8, Shift-JIS) + correctly. It relies on the mbrtowc function to handle multibytes. + +* The file generated by -g or --listed-incremental now uses a format + that is independent of locale, so that users need not worry about + locale when restoring a backup. This is needed for proper support + of multibyte characters. Old-format files can still be read, and + older versions of GNU tar can read new-format files, unless member + names have multibyte chars. + +* Many diagnostics have been changed slightly, so that file names are + now output unambiguously. File names in diagnostics now are either + `quoted like this' (in the default C locale) or are followed by + colon, newline, or space, depending on context. Unprintable + characters are escaped with a C-like backslash conventions. + Terminating characters (e.g. close-quote, colon, newline) + are also escaped as needed. + +* tar now ignores socket files when creating an archive. + Previously tar archived sockets as fifos, which caused problems. + +version 1.13.15 - Paul Eggert, 1999-12-03. + +* If a file's ctime changes when being archived, report an error. + Previously tar looked at mtime, which missed some errors. + +version 1.13.14 - Paul Eggert, 1999-11-07. + +* New translations ja, pt_BR. +* New options --help and --version for rmt. +* Ignore Solaris door files when creating an archive. + +version 1.13.13 - Paul Eggert, 1999-10-11. + +* Invalid headers in tar files now elicit errors, not just warnings. +* `tar --version' output conforms to the latest GNU coding standards. +* If you specify an invalid date, `tar' now substitutes (time_t) -1. +* `configure --with-dmalloc' is no longer available. + +version 1.13.12 - Paul Eggert, 1999-09-24. + +* `tar' now supports hard links to symbolic links. + +* New options --no-same-owner, --no-same-permissions. + +* --total now also outputs a human-readable size, and a throughput value. + +* `tar' now uses two's-complement base-256 when outputting header + values that are out of the range of the standard unsigned base-8 + format. This affects archive members with negative or huge time + stamps or uids, and archive members 8 GB or larger. The new tar + archives cannot be read by traditional tar, or by older versions of + GNU tar. Use the --old-archive option to revert to the old + behavior, which uses unportable representations for negative values, + and which rejects large files. + +* On 32-bit hosts, `tar' now assumes that an incoming time stamp T in + the range 2**31 <= T < 2**32 represents the negative time (T - + 2**32). This behavior is nonstandard and is not portable to 64-bit + time_t hosts, so `tar' issues a warning. + +* `tar' no longer gives up extracting immediately upon discovering + that an archive contains garbage at the end. It attempts to extract + as many files as possible from the good data before the garbage. + +* A read error now causes a nonzero exit status, not just a warning. + +* Some diagnostics have been reworded for consistency. + + +version 1.13.11 - Paul Eggert, 1999-08-23. + +* The short name of the --bzip option has been changed to -I, + for compatibility with paxutils. + +* -T /dev/null now matches nothing; previously, it matched anything + if no explicit operands were given. + +* The `--' option now works the same as with other GNU utilities; + it causes later operands to be interpreted as file names, not options, + even if they begin with `-'. + +* For the --newer and --after-date options, the table of time zone + abbreviations like `EST' has been updated to match current practice. + Also, local time abbreviations are now recognized, even if they are + not in tar's hardwired table. Remember, though, that you should use + numeric UTC offsets like `-0500' instead of abbreviations like + `EST', as abbreviations are not standardized and are ambiguous. + + +version 1.13.10 - Paul Eggert, 1999-08-20. + +* `tar' now uses signed base-64 when outputting header values that are + out of the range of the standard unsigned base-8 format. [This + change was superseded in 1.13.12, described above.] + + +version 1.13.9 - Paul Eggert, 1999-08-18. + +* `tar' now writes two zero blocks at end-of-archive instead of just one. + POSIX.1 requires this, and some other `tar' implementations check for it. + +* `tar' no longer silently accepts a block containing nonzero checksum bytes + as a zero block. + +* `tar' now reads buggy tar files that have a null byte at the start of a + numeric header field. + + +version 1.13.8 - Paul Eggert, 1999-08-16. + +* For compatibility with traditional `tar', intermediate directories + created automatically by root are no longer given the uid and gid of + the original file or directory. + + +version 1.13.7 - Paul Eggert, 1999-08-14. + +* --listed-incremental and --newer are now incompatible options. + +* When creating an archive, leading `./' is no longer stripped, + to match traditional tar's behavior (and simplify the documentation). + +* --diff without --absolute-names no longer falls back on absolute names. + + +version 1.13.6 - Paul Eggert, 1999-08-11. + +* An --exclude pattern containing / now excludes a file only if it matches an + initial prefix of the file name; a pattern without / continues to + exclude a file if it matches any file name component. + +* The protocol for talking to rmt has been extended slightly. + Open flags are now communicated in symbolic format as well as numeric. + The symbolic format (e.g. "O_WRONLY|O_CREAT|O_TRUNC") is for portability + when rmt is operating on a different operating system from tar. + The numeric format is retained, and rmt uses it if symbolic format is absent, + for backward compatibility with older versions of tar and rmt. + +* When writing GNU tar format headers, tar now uses signed base-64 + for values that cannot be represented in unsigned octal. + This supports larger files (2**66 - 1 bytes instead of 2**33 - 1 bytes), + larger uids, negative time stamps, etc. + +* When extracting files with unknown ownership, tar now looks up the + uid and gid "nobody" on hosts whose headers do not define UID_NOBODY + and GID_NOBODY, and falls back on uid/gid -2 if there is no "nobody". + +* tar -t --numeric-owner now prints numeric uids and gids, not symbolic. + +* New option -y or --bzip2 for bzip2 compression, by popular request. + + +version 1.13.5 - Paul Eggert, 1999-07-20. + +* Do the delayed updates of file metadata even after a fatal error. + + +version 1.13.4 - Paul Eggert, 1999-07-20. + +* Do not chmod unless we are root or the -p option was given; + this matches historical practice. + + +version 1.13.3 - Paul Eggert, 1999-07-16. + +* A path name is excluded if any of its file name components matches an + excluded pattern, even if the path name was specified on the command line. + Also see 1.13.6 for later changes in this area. + + +version 1.13.2 - Paul Eggert, 1999-07-14. + +* Bug reporting address changed to . + + +version 1.13.1 - Paul Eggert, 1999-07-12. + +* Bug fixes only. + +version 1.13 - Paul Eggert, 1999-07-08. + +* Support for large files, e.g. files larger than 2 GB on many 32-bit hosts. + Also, support for larger uids, device ids, etc. +* Many bug fixes and porting fixes. +* This release is only for fixes. A more ambitious test release, + with new features, is available as part of the paxutils. Please see: + ftp://alpha.gnu.org/gnu/paxutils/ + The fixes in this release are intended to be merged with paxutils + at some point, but they haven't been merged yet. +* An interim GNU tar alpha had new --bzip2 and --ending-file options, + but they have been removed to maintain compatibility with paxutils. + Please try --use=bzip2 instead of --bzip2. -Version 1.12 - François Pinard, 1997-04. +Version 1.12 - François Pinard, 1997-04. Sensitive matters * Use shell globbing patterns for --label, instead of regular expressions. * Do not quote anymore internally over the quoting done by the shell. Output for humans -* Offer internationalisation capabilities of most recent GNU gettext. +* Offer internationalization capabilities of most recent GNU gettext. * Messages available in many more languages, thanks to all translators! * Usage of ISO 8601 dates in listings, instead of local American dates. -* More normalisation and cleanup in error messages. +* More normalization and cleanup in error messages. Creation * For helping using tar with find, offer a --no-recursion option. * Implement --numeric-owner for ignoring symbolic names at create time. * New --owner, --group --mode options, still preliminary. -* Recognise creating an archive on /dev/null, so Amanda works faster. +* Recognize creating an archive on /dev/null, so Amanda works faster. * Object to the creation of an empty archive (like in `tar cf FILE'). * Barely start implementing --posix and POSIXLY_CORRECT. @@ -59,7 +376,7 @@ Various changes Many bugs are squashed, while others still run free. -Version 1.11.8 - François Pinard, 1995-06. +Version 1.11.8 - François Pinard, 1995-06. * Messages available in French, German, Portuguese and Swedish. * The distribution provides a rudimentary Texinfo manual. @@ -192,3 +509,25 @@ Version 1.08 - Jay Fenlason, 1990-01. Versions 1.07 back to 1.00 by Jay Fenlason. * See ChangeLog for more details. + + + +Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2003 +Free Software Foundation, Inc. + +This file is part of GNU tar. + +GNU tar is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 2, or (at your option) +any later version. + +GNU tar is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with tar; see the file COPYING. If not, write to +the Free Software Foundation, Inc., 59 Temple Place - Suite 330, +Boston, MA 02111-1307, USA.