]> Dogcows Code - chaz/tar/blob - NEWS
Add xz support.
[chaz/tar] / NEWS
1 GNU tar NEWS - User visible changes. 2009-03-04
2 Please send GNU tar bug reports to <bug-tar@gnu.org>
3
4 \f
5 version 1.21.90 (CVS)
6
7 * Support for xz compression
8
9 Tar uses xz for compression if at least one of the following
10 conditions is met:
11
12 1. The option --xz or -J (see below) is used.
13 2. The xz binary is set as compressor using --use-compress-program option.
14 3. The file name of the archive being created ends in `.xz' and
15 auto-compress option (-a) is used.
16
17 Xz is used for decompression if at least one of the following
18 conditions is met:
19
20 1. The option --xz or -J is used.
21 2. The xz binary is set as compressor using --use-compress-program option.
22 3. The file is recognized as xz compressed stream data.
23
24 * Short option -J
25
26 The decision to assign -J option was taken just before the XZ format
27 has been officially declared stable. Now, that stable xz tools are
28 available, the -J option is re-assigned as a short equivalent of --xz.
29
30 * New option -I
31
32 The -I option is assigned as a short equivalent for
33 --use-compress-program.
34
35 \f
36 version 1.21 - Sergey Poznyakoff, 2008-12-27
37
38 * New short option -J
39
40 A shortcut for --lzma.
41
42 * New option --lzop
43
44 * New option --no-auto-compress
45
46 Cancels the effect of previous --auto-compress (-a) option.
47
48 * New option --no-null
49
50 Cancels the effect of previous --null option.
51
52 * Compressed format recognition
53
54 If tar is unable to determine archive compression format, it falls
55 back to using archive suffix to determine it.
56
57 * VCS support.
58
59 Using --exclude-vcs handles also files used internally by Bazaar,
60 Mercurial and Darcs.
61
62 * Transformation scope flags
63
64 Name transformation expressions understand additional flags that
65 control type of archive members affected by them. The flags are:
66
67 - r
68 Apply transformation to regular archive members.
69
70 - s
71 Apply transformation to symbolic link targets.
72
73 - h
74 Apply transformation to hard link targets.
75
76 Corresponding upper-case letters negate the meaning, so that
77 `H' means ``do not apply transformation to hard link targets.''
78
79 The scope flags are listed in the third part of an `s' expression,
80 e.g.:
81
82 tar --transform 's|^|/usr/local/|S'
83
84 Default is `rsh', which means that transformations are applied to
85 both regular archive members and to the targets of symbolic and hard
86 links. If several transform expressions are used, the default flags
87 can be changed using `flags=' statement before the expressions, e.g.:
88
89 tar --transform 'flags=S;s|^|/usr/local/|S'
90
91 * Bugfixes
92
93 ** The --null option disabled handling of tar options in list files. This
94 is fixed.
95 ** Fixed record size autodetection. If detected record size differs from
96 the expected value (either default, or set on the command line), tar
97 always prints a warning if verbosity level is set to 1 or greater,
98 i.e. if either -t or -v option is given.
99
100 \f
101
102 version 1.20 - Sergey Poznyakoff, 2008-04-14
103
104 * New option --auto-compress (-a)
105
106 With --create, selects compression algorithm basing on the suffix
107 of the archive file name.
108
109 * New option --lzma
110
111 Selects LZMA compression algorithm
112
113 * New option --hard-dereference
114
115 During archive creation, dereferences hard links and stores the files
116 they refer to, instead of creating usual hard link members (type '1').
117
118 * New option --checkpoint-action
119
120 This action allows to specify an action to be executed upon hitting a
121 checkpoint. Recognized actions are: dot, echo (the default),
122 echo=string, ttyout=string, exec=cmdline, and sleep=value. Any number
123 of `--checkpoint-action' options can be specified, the actions will be
124 executed in order of their appearance in the command line. See
125 chapter 3.8 "Checkpoints" for a complete description.
126
127 * New options --no-check-device, --check-device.
128
129 The `--no-check-device' option disables comparing device numbers during
130 preparatory stage of an incremental dump. This allows to avoid
131 creating full dumps if the device numbers change (e.g. when using an
132 LVM snapshot).
133
134 The `--check-device' option enables comparing device numbers. This is
135 the default. This option is provided to undo the effect of the previous
136 `--no-check-device' option, e.g. if it was set in TAR_OPTIONS
137 environment variable.
138
139 * The --transform option.
140
141 Any number of `--transform' options can be given in the command line.
142 The specified transformations will be applied in turn.
143
144 The argument to `--transform' option can be a list of replace
145 expressions, separated by a semicolon (as in `sed').
146
147 Filename transformations are applied to symbolic link targets
148 during both creation and extraction. Tar 1.19 used them only
149 during extraction.
150
151 For a detailed description, see chapter 6.7 "Modifying File and Member
152 Names".
153
154 * Info (end-of-volume) scripts
155
156 The value of the blocking factor is made available to info and
157 checkpoint scripts via environment variable TAR_BLOCKING_FACTOR.
158
159 * Incremental archives
160
161 Improved (sped up) extracting from incremental archives.
162
163 * Bugfixes.
164 ** Fix bug introduced in version 1.19: tar refused to update non-existing
165 archives.
166
167 \f
168 version 1.19 - Sergey Poznyakoff, 2007-10-10
169
170 * New option --exclude-vcs
171
172 Excludes directories and files, created by several widely used version
173 control systems, e.g. "CVS/", ".svn/", etc.
174
175 * --exclude-tag and --exclude-cache options
176
177 The following options now work with incremental archives as well:
178
179 --exclude-caches
180 --exclude-caches-all
181 --exclude-tag
182 --exclude-tag-all
183 --exclude-tag-under
184
185 * Fix handling of renamed files in listed incremental archives.
186
187 Previous versions always stored absolute file names in rename
188 records, even if -P was not used. This is fixed: rename records
189 contain file names processed in accordance with the command line
190 settings.
191
192 * Fix --version output.
193
194 * Recognition of broken archives.
195
196 When supplied an archive smaller than 512 bytes in reading mode (-x,
197 -t), the previous version of tar silently ignored it, exiting with
198 code 0. It is fixed. Tar now issues the following diagnostic message:
199 'This does not look like a tar archive', and exits with code 2.
200
201 * Fix double-dot recognition in archive member names in case of duplicate '/.'.
202
203 * Fix file padding in case of truncation of the input file to zero size.
204
205 \f
206 version 1.18 - Sergey Poznyakoff, 2007-06-29
207
208 * Licensed under the GPLv3
209
210 * Fixed several bugs in the testsuite
211
212 \f
213 version 1.17 - Sergey Poznyakoff, 2007-06-08
214
215 * Fix archivation of sparse files in posix mode. Previous versions padded
216 sparse members with spurious zero blocks.
217
218 * Fix operation of --verify --listed-incremental. Version 1.16.1 produced
219 a full dump when both options were given.
220
221 * Fix --occurrence. In previous versions it continued scanning the archive
222 even though all requested members has already been extracted.
223
224 * Scope of --transform and --strip-components options.
225
226 In addition to affecting regular archive members, the --transform
227 option affects hard and soft link targets and the --strip-components
228 option affects hard link targets as well.
229
230 * End-of-volume script can send the new volume name to tar by writing
231 it to the file descriptor stored in the environment variable `TAR_FD'.
232
233 \f
234 version 1.16.1 - Sergey Poznyakoff, 2006-12-09
235
236 * New option --exclude-tag allows to specify "exclusion tag files", i.e.
237 files whose presence in a directory means that the directory should not
238 be archived.
239
240 * The --exclude-cache option excludes directories that contain the
241 CACHEDIR.TAG file from being archived. Previous versions excluded
242 directory contents only, while the directories themselves were
243 still added to the archive.
244
245 * Support for reading ustar type 'N' header logical records has been removed.
246 This GNU extension was generated only by very old versions of GNU 'tar'.
247 Unfortunately its implementation had security holes; see
248 <http://archives.neohapsis.com/archives/fulldisclosure/2006-11/0344.html>.
249 We don't expect that any tar archives in practical use have type 'N'
250 records, but if you have one and you trust its contents, you can
251 decode it with GNU tar 1.16 or earlier.
252
253 * Race conditions have been fixed that in some cases briefly allowed
254 files extracted by 'tar -x --same-owner' (or plain 'tar -x', when
255 running as root) to be accessed by users that they shouldn't have been.
256
257 \f
258 version 1.16 - Sergey Poznyakoff, 2006-10-21
259
260 * After creating an archive, tar exits with code 1 if some files were
261 changed while being read. Previous versions exited with code 2 (fatal
262 error), and only if some files were truncated while being archived.
263
264 * New option --mtime allows to set modification times for all archive
265 members during creation.
266
267 * Bug fixes
268 ** Avoid running off file descriptors when using multiple -C options.
269 ** tar --index-file=FILE --file=- sent the archive to FILE, and
270 the listing to stderr.
271
272 \f
273 version 1.15.91 - Sergey Poznyakoff, 2006-06-16
274
275 * Incompatible changes
276
277 ** Globbing
278
279 Previous versions of GNU tar assumed shell-style globbing when
280 extracting from or listing an archive. For example:
281
282 tar xf foo.tar '*.c'
283
284 would extract all files whose names end in '.c'. This behavior
285 was not documented and was incompatible with traditional tar
286 implementations. Therefore, starting from this version, GNU tar
287 no longer uses globbing by default. For example, the above invocation
288 is now interpreted as a request to extract from the archive the file
289 named '*.c'.
290
291 To treat member names as globbing patterns, use --wildcards option.
292 If you wish tar to mimic the behavior of versions up to 1.15.90,
293 add --wildcards to the value of the environment variable TAR_OPTIONS.
294
295 The exact way in which tar interprets member names is controlled by the
296 following command line options:
297
298 --wildcards use wildcards
299 --anchored patterns match file name start
300 --ignore-case ignore case
301 --wildcards-match-slash wildcards match `/'
302
303 Each of these options has a '--no-' counterpart that disables its
304 effect (e.g. --no-wildcards).
305
306 These options affect both the interpretation of member names from
307 command line and that of the exclusion patterns (given with --exclude
308 and --exclude-from options). The defaults are:
309
310 1. For member names: --no-wildcards --anchored
311 2. For exclusion patterns: --wildcards --no-anchored --wildcards-match-slash
312
313 The options can appear multiple times in the command line, thereby
314 changing the way command line arguments are interpreted. For example,
315 to use case-insensitive matching in exclude patterns and to revert to
316 case-sensitive matching for the rest of command line, one could write:
317
318 tar xf foo.tar --ignore-case --exclude-from=FILE --no-ignore-case file.name
319
320 ** Short option -l is now an alias of --check-links option, which complies
321 with UNIX98. This ends the transition period started with version 1.14.
322
323 * New features
324
325 ** New option --transform allows to transform file names before storing them
326 in the archive or member names before extracting. The option takes a
327 sed replace expression as its argument. For example,
328
329 tar cf foo.tar --transform 's,^,prefix/,'
330
331 will add 'prefix/' to all file names stored in foo.tar.
332
333 ** --strip-components option works when deleting and comparing. In previous
334 versions it worked only with --extract.
335
336 ** New option --show-transformed-names enables display of transformed file
337 or archive. It generalizes --show-stored-names option, introduced in
338 1.15.90. In particular, when creating an archive in verbose mode, it lists
339 member names as stored in the archive, i.e., with any eventual prefixes
340 removed and file name transformations applied. The option is useful,
341 for example, while comparing `tar cv' and `tar tv' outputs.
342
343 ** New incremental snapshot file format keeps information about file names
344 as well as that about directories.
345
346 ** The --checkpoint option takes an optional argument specifying the number
347 of records between the two successive checkpoints. Optional dot
348 starting the argument intructs tar to print dots instead of textual
349 checkpoints.
350
351 ** The --totals option can be used with any tar operation (previous versions
352 understood it only with --create). If an argument to this option is
353 given, it specifies the signal upon delivery of which the statistics
354 is to be printed. Both forms of this option (with and without
355 argument) can be given to in a single invocation of tar.
356
357 * Bug fixes
358 ** Detect attempts to update compressed archives.
359
360 \f
361 version 1.15.90 - Sergey Poznyakoff, 2006-02-19
362
363 * New features
364
365 ** Any number of -T (--files-from) options may be used in the command line.
366 The file specified with -T may include any valid `tar' options,
367 including another -T option.
368 Compatibility note: older versions of tar would only recognize -C
369 as an option name within the file list file. Now any file whose name
370 starts with - is handled as an option. To insert file names starting with
371 dash, use the --add-file option.
372
373 ** List files containing null-separated file names are detected and processed
374 automatically. It is no longer necessary to give the --null option.
375
376 ** New option --no-unquote disables the unquoting of input file names.
377 This is useful for processing output from `find dir -print0'.
378 An orthogonal option --unquote is provided as well.
379
380 ** New option --test-label tests the archive volume label.
381 If an argument is specified, the label is compared against its value.
382 Tar exits with code 0 if the two strings match, and with code 2 if
383 they do not.
384
385 If no argument is given, the --verbose option is implied. In this case,
386 tar prints the label name if present and exits with code 0.
387
388 ** New option --show-stored-names. When creating an archive in verbose mode,
389 it lists member names as stored in the archive, i.e., with any eventual
390 prefixes removed. The option is useful, for example, while comparing
391 `tar cv' and `tar tv' outputs.
392
393 ** New option --to-command pipes the contents of archive members to the
394 specified command.
395
396 ** New option --atime-preserve=system, which uses the O_NOATIME feature
397 of recent Linux kernels to avoid some problems when preserving file
398 access times.
399
400 ** New option --delay-directory-restore delays restoring modification times
401 and permissions of extracted directories until the end of extraction.
402 This is necessary for restoring from archives with unusual member
403 ordering (in particular, those created with --no-recursion option).
404 This option is implied when restoring from incremental archives.
405
406 ** New option --restrict prohibits use of some potentially harmful tar
407 options. Currently it disables '!' escape in multi-volume name menu.
408
409 ** New options --quoting-style and --quote-chars control the way tar
410 quotes member names on output. The --quoting-style takes an argument
411 specifying the quoting style to use (literal, shell, shell-always,
412 c, escape, locale, clocale). The argument to --quote-chars is a string
413 specifying characters to quote, even if the selected quoting style
414 would not quote them otherwise. The option --no-quote-chars is
415 provided to disable quoting certain characters.
416
417 ** The end-of-volume script (introduced with --info-script option) can
418 get current archive name from the environment variable TAR_ARCHIVE and
419 the volume number from the variable TAR_VOLUME. It can alter the
420 archive name by writing new name to the file descriptor 3.
421
422 ** Better support for full-resolution time stamps. Tar cannot restore
423 time stamps to full nanosecond resolution, though, until the kernel
424 guys get their act together and give us a system call to set file time
425 stamps to nanosecond resolution.
426
427 ** The -v option now prints time stamps only to 1-minute resolution,
428 not full resolution, to avoid using up too many output columns.
429 Nanosecond resolution is now supported, but that would be too much.
430
431 * Bug fixes
432
433 ** Allow non-option arguments to be interspersed with options.
434 ** When extracting or listing archives in old GNU format, tar
435 used to read an extra block of data after a long name header
436 if length of the member name was divisible by block size (512).
437 Consequently, the file pointer was set off and the next member
438 was not processed correctly.
439 ** Previous version created invalid archives when files shrink
440 during reading.
441 ** Compare mode (tar d) hung when trying to compare file contents.
442 ** Previous versions in certain cases failed to restore directory
443 modification times.
444 ** When creating an archive, do not attempt to store files whose
445 meta-data cannot be stored in the header due to format limitations
446 (for ustar and v7 formats).
447 ** The --version option now also outputs information about copyright,
448 license, and credits. This reverts to the behavior of tar 1.14 and
449 earlier, and conforms to the GNU coding standards. The --license (-L)
450 option introduced in tar 1.15 has been removed, since it's no longer
451 needed.
452
453 \f
454 version 1.15.1 - Sergey Poznyakoff, 2004-12-21
455
456 This version fixes a bug introduced in 1.15 which caused
457 tar to refuse to extract files from standard input.
458
459 \f
460 version 1.15 - Sergey Poznyakoff, 2004-12-20
461
462 * Compressed archives are recognised automatically, it is no longer
463 necessary to specify -Z, -z, or -j options to read them. Thus, you can
464 now run `tar tf archive.tar.gz'.
465
466 * When restoring incremental dumps, --one-file-system option
467 prevents directory hierarchies residing on different devices
468 from being purged.
469
470 With the previous versions of tar it was dangerous to create
471 incremental dumps with --one-file-system option, since they
472 would recursively remove mount points when restoring from the
473 back up. This change fixes the bug.
474
475 * Renamed --strip-path to --strip-components for consistency with
476 the GNU convention.
477
478 * Skipping archive members is sped up if the archive media supports
479 seeks.
480
481 * Restore script starts restoring only if it is given --all (-a) option,
482 or some patterns. This is to prevent accidental restores.
483
484 * `tar --verify' prints a warning if during archive creation some of
485 the file names had their prefixes stripped off.
486
487 * New option --exclude-caches instructs tar to exclude cache directories
488 automatically on archive creation. Cache directories are those
489 containing a standardized tag file, as specified at:
490
491 http://www.brynosaurus.com/cachedir/spec.html
492
493 * New configure option --with-rmt allows to specify full path name to
494 the `rmt' utility. This supersedes DEFAULT_RMT_COMMAND variable
495 introduced in version 1.14
496
497 * New configure variable DEFAULT_RMT_DIR allows to specify the directory
498 where to install `rmt' utility. This is necessary since modifying
499 --libexecdir as was suggested for version 1.14 produced a side effect: it
500 also modified installation prefix for backup scripts (if
501 --enable-backup-scripts was given).
502
503 * Bug fixes:
504 ** Fixed flow in recognizing files to be included in incremental dumps.
505 ** Correctly recognize sparse archive members when used with -T option.
506 ** GNU multivolume headers cannot store filenames longer than 100 characters.
507 Do not allow multivolume archives to begin with such filenames.
508 ** If a member with link count > 2 was stored in the archive twice,
509 previous versions of tar were not able to extract it, since they
510 were trying to link the file to itself, which always failed and
511 lead to removing the already extracted copy. Preserve the first
512 extracted copy in such cases.
513 ** Restore script was passing improper argument to tar --listed option (which
514 didn't affect the functionality, but was logically incorrect).
515 ** Fixed verification of created archives.
516 ** Fixed unquoting of file names containing backslash escapes (previous
517 versions failed to recognize \a and \v).
518 ** When attempting to delete a non-existing member from the archive, previous
519 versions of tar used to overwrite last archive block with zeroes.
520
521 \f
522 version 1.14 - Sergey Poznyakoff, 2004-05-11
523
524 * Added support for POSIX.1-2001 and ustar archive formats.
525 * New option --format allows to select the output archive format
526 * The default output format can be selected at configuration time
527 by presetting the environment variable DEFAULT_ARCHIVE_FORMAT.
528 Allowed values are GNU, V7, OLDGNU and POSIX.
529 * New option --strip-path allows to cut off a given number of
530 path elements from the name of the file being extracted.
531
532 * New options --index-file, --no-overwrite-dir. The --overwrite-dir
533 option is now the default; use --no-overwrite-dir if you prefer
534 the previous default behavior.
535
536 * The semantics of -o option is changed. When extracting, it
537 does the same as --no-same-owner GNU tar option. This is compatible
538 with UNIX98 tar. Otherwise, its effect is the same as that of
539 --old-archive option. This latter is deprecated and will be removed
540 in future.
541
542 * New option --check-links prints a message if not all links are dumped
543 for a file being archived. This corresponds to the UNIX98 -l option.
544 The current semantics of the -l option is retained for compatibility
545 with previous releases, however such usage is strongly deprecated as
546 the option will change to its UNIX98 semantics in the future releases.
547
548 * New option --occurrence[=N] can be used in conjunction with one of
549 the subcommands --delete, --diff, --extract or --list when a list of
550 files is given either on the command line or via -T option. This
551 option instructs tar to process only the Nth occurrence of each named
552 file. N defaults to 1, so `tar -x -f archive --occurrence filename'
553 extracts the first occurrence of `filename' from `archive'
554 and terminates without scanning to the end of the archive.
555
556 * New option --pax-option allows to control the handling of POSIX
557 keywords in `pax' extended headers. It is equivalent to `pax'
558 -o option.
559
560 * --incremental and --listed-incremental options work correctly on
561 individual files, as well as on directories.
562
563 * New scripts: backup (replaces old level-0 and level-1) and restore.
564 The scripts are compiled and installed if --enable-backup-scripts
565 option is given to configure.
566
567 * By default tar searches "rmt" utility in "$prefix/libexec/rmt",
568 which is consistent with the location where the version of "rmt"
569 included in the package is installed. Previous versions of tar
570 used "/etc/rmt". To install "rmt" to its traditional location,
571 run configure with option --libexecdir=/etc. Otherwise, if you
572 already have rmt installed and wish to use it, instead of the
573 shipped in version, set the variable DEFAULT_RMT_COMMAND to
574 the full path name of the utility, e.g., ./configure
575 DEFAULT_RMT_COMMAND=/etc/rmt.
576
577 Notice also that the full path name of the "rmt" utility to
578 use can be set at runtime, by giving option --rmt-command to
579 tar.
580
581 * Removed obsolete command line options:
582 ** --absolute-paths superseded by --absolute-names
583 ** --block-compress is not needed any longer
584 ** --block-size superseded by --blocking-factor
585 ** --modification-time superseded by --touch
586 ** --read-full-blocks superseded by --read-full-records
587 ** --record-number superseded by --block-number
588 ** --version-control superseded by --backup
589
590 * New message translations fi (Finnish), gl (Galician), hr (Croatian),
591 hu (Hungarian), ms (Malaysian), nb (Norwegian), ro (Romanian), sk
592 (Slovak), zh_CN (Chinese simplified), zh_TW (Chinese traditional).
593 The code 'no' for Norwegian (Bokmål) has been withdrawn; use 'nb' instead.
594
595 * Bug fixes.
596
597 \f
598 version 1.13.25 - Paul Eggert, 2001-09-26
599
600 * Bug fixes.
601
602 \f
603 version 1.13.24 - Paul Eggert, 2001-09-22
604
605 * New option --overwrite-dir.
606 * Fixes for buffer overrun, porting, and copyright notice problems.
607 * The message translations for Korean are available again.
608
609 \f
610 version 1.13.23 - Paul Eggert, 2001-09-13
611
612 * Bug, porting, and copyright notice fixes.
613
614 \f
615 version 1.13.22 - Paul Eggert, 2001-08-29
616
617 * Bug fixes.
618
619 \f
620 version 1.13.21 - Paul Eggert, 2001-08-28
621
622 * Porting and copyright notice fixes.
623
624 \f
625 version 1.13.20 - Paul Eggert, 2001-08-27
626
627 * Some bugs were fixed:
628 - security problems
629 - hard links to symbolic links
630
631 * New option --recursion (the default) that is the inverse of --no-recursion.
632
633 * New options --anchored, --ignore-case, --wildcards,
634 --wildcards-match-slash, and their negations (e.g., --no-anchored).
635 Along with --recursion and --no-recursion, these options control how
636 exclude patterns are interpreted.
637
638 * The default interpretation of exclude patterns is now --no-anchored
639 --no-ignore-case --recursion --wildcards --wildcards-match-slash.
640 This is a quiet change to the semantics of --exclude. The previous
641 semantics were a failed attempt at backward compatibility but it
642 became clear that the semantics were puzzling and did not satisfy
643 everybody. Rather than continue to try to revive that dead horse we
644 thought it better to substitute cleaner semantics, with options so
645 that you can change the behavior more to your liking.
646
647 * New message translations for Indonesian and Turkish.
648 The translation for Korean has been withdrawn due to encoding errors.
649 It will be reissued once those are fixed.
650
651 \f
652 version 1.13.19 - Paul Eggert, 2001-01-13
653
654 * The -I option has been withdrawn, as it was buggy and confusing.
655 Eventually it is planned to be reintroduced, with the same meaning as -T.
656
657 * With an option like -N DATE, if DATE starts with "/" or ".", it is taken
658 to be a file name; the last-modified time of that file is used as the date.
659
660 \f
661 version 1.13.18 - Paul Eggert, 2000-10-29
662
663 * Some security problems have been fixed. `tar -x' now modifies only
664 files under the working directory, unless you also specify an unsafe
665 option like --absolute-names or --overwrite.
666
667 * The short name of the --bzip option has been changed to -j,
668 and -I is now an alias for -T, for compatibility with Solaris tar.
669
670 * The manual is now distributed under the GNU Free Documentation License.
671
672 * The new environment variable TAR_OPTIONS holds default command-line options.
673
674 * The --no-recursion option now affects extraction too.
675
676 * The wording in some diagnostics has been changed slightly.
677
678 * Snapshot files now record whether each file was accessed via NFS.
679 The new file format is upward- and downward-compatible with the old.
680
681 * New language supported: da.
682
683 * Compilation by traditional (K&R) C compilers is no longer supported.
684 If you still use such a compiler, please use GCC instead.
685
686 * This version of tar works best with GNU gzip test version 1.3 or later.
687 Please see <ftp://alpha.gnu.org/gnu/gzip/>.
688
689 * `tar --delete -f -' now works again.
690
691 \f
692 version 1.13.17 - Paul Eggert, 2000-01-07.
693
694 * `tar --delete -f -' is no longer allowed; it was too buggy.
695 * Diagnostic messages have been made more regular and consistent.
696
697 \f
698 version 1.13.16 - Paul Eggert, 1999-12-13.
699
700 * By default, tar now refuses to overwrite an existing file when
701 extracting files from an archive; instead, it removes the file
702 before extracting it. If the existing file is a symbolic link, the
703 link is removed and not the pointed-to file. There is one
704 exception: existing nonempty directories are not removed, nor are
705 their ownerships or permissions extracted. This fixes some
706 longstanding security problems.
707
708 The new --overwrite option enables the old default behavior.
709
710 For regular files, tar implements this change by using the O_EXCL
711 option of `open' to ensure that it creates the file; if this fails, it
712 removes the file and tries again. This is similar to the behavior of
713 the --unlink-first option, but it is faster in the common case of
714 extracting a new directory.
715
716 * By default, tar now ignores file names containing a component of `..'
717 when extracting, and warns about such file names when creating an archive.
718 To enable the old behavior, use the -P or --absolute-names option.
719
720 * Tar now handles file names with multibyte encodings (e.g., UTF-8, Shift-JIS)
721 correctly. It relies on the mbrtowc function to handle multibyte characters.
722
723 * The file generated by -g or --listed-incremental now uses a format
724 that is independent of locale, so that users need not worry about
725 locale when restoring a backup. This is needed for proper support
726 of multibyte characters. Old-format files can still be read, and
727 older versions of GNU tar can read new-format files, unless member
728 names have multibyte chars.
729
730 * Many diagnostics have been changed slightly, so that file names are
731 now output unambiguously. File names in diagnostics now are either
732 `quoted like this' (in the default C locale) or are followed by
733 colon, newline, or space, depending on context. Unprintable
734 characters are escaped with a C-like backslash conventions.
735 Terminating characters (e.g., close-quote, colon, newline)
736 are also escaped as needed.
737
738 * tar now ignores socket files when creating an archive.
739 Previously tar archived sockets as fifos, which caused problems.
740
741 \f
742 version 1.13.15 - Paul Eggert, 1999-12-03.
743
744 * If a file's ctime changes when being archived, report an error.
745 Previously tar looked at mtime, which missed some errors.
746
747 \f
748 version 1.13.14 - Paul Eggert, 1999-11-07.
749
750 * New translations ja, pt_BR.
751 * New options --help and --version for rmt.
752 * Ignore Solaris door files when creating an archive.
753
754 \f
755 version 1.13.13 - Paul Eggert, 1999-10-11.
756
757 * Invalid headers in tar files now elicit errors, not just warnings.
758 * `tar --version' output conforms to the latest GNU coding standards.
759 * If you specify an invalid date, `tar' now substitutes (time_t) -1.
760 * `configure --with-dmalloc' is no longer available.
761
762 \f
763 version 1.13.12 - Paul Eggert, 1999-09-24.
764
765 * `tar' now supports hard links to symbolic links.
766
767 * New options --no-same-owner, --no-same-permissions.
768
769 * --total now also outputs a human-readable size, and a throughput value.
770
771 * `tar' now uses two's-complement base-256 when outputting header
772 values that are out of the range of the standard unsigned base-8
773 format. This affects archive members with negative or huge time
774 stamps or uids, and archive members 8 GB or larger. The new tar
775 archives cannot be read by traditional tar, or by older versions of
776 GNU tar. Use the --old-archive option to revert to the old
777 behavior, which uses unportable representations for negative values,
778 and which rejects large files.
779
780 * On 32-bit hosts, `tar' now assumes that an incoming time stamp T in
781 the range 2**31 <= T < 2**32 represents the negative time (T -
782 2**32). This behavior is nonstandard and is not portable to 64-bit
783 time_t hosts, so `tar' issues a warning.
784
785 * `tar' no longer gives up extracting immediately upon discovering
786 that an archive contains garbage at the end. It attempts to extract
787 as many files as possible from the good data before the garbage.
788
789 * A read error now causes a nonzero exit status, not just a warning.
790
791 * Some diagnostics have been reworded for consistency.
792
793 \f
794 version 1.13.11 - Paul Eggert, 1999-08-23.
795
796 * The short name of the --bzip option has been changed to -I,
797 for compatibility with paxutils.
798
799 * -T /dev/null now matches nothing; previously, it matched anything
800 if no explicit operands were given.
801
802 * The `--' option now works the same as with other GNU utilities;
803 it causes later operands to be interpreted as file names, not options,
804 even if they begin with `-'.
805
806 * For the --newer and --after-date options, the table of time zone
807 abbreviations like `EST' has been updated to match current practice.
808 Also, local time abbreviations are now recognized, even if they are
809 not in tar's hardwired table. Remember, though, that you should use
810 numeric UTC offsets like `-0500' instead of abbreviations like
811 `EST', as abbreviations are not standardized and are ambiguous.
812
813 \f
814 version 1.13.10 - Paul Eggert, 1999-08-20.
815
816 * `tar' now uses signed base-64 when outputting header values that are
817 out of the range of the standard unsigned base-8 format. [This
818 change was superseded in 1.13.12, described above.]
819
820 \f
821 version 1.13.9 - Paul Eggert, 1999-08-18.
822
823 * `tar' now writes two zero blocks at end-of-archive instead of just one.
824 POSIX.1 requires this, and some other `tar' implementations check for it.
825
826 * `tar' no longer silently accepts a block containing nonzero checksum bytes
827 as a zero block.
828
829 * `tar' now reads buggy tar files that have a null byte at the start of a
830 numeric header field.
831
832 \f
833 version 1.13.8 - Paul Eggert, 1999-08-16.
834
835 * For compatibility with traditional `tar', intermediate directories
836 created automatically by root are no longer given the uid and gid of
837 the original file or directory.
838
839 \f
840 version 1.13.7 - Paul Eggert, 1999-08-14.
841
842 * --listed-incremental and --newer are now incompatible options.
843
844 * When creating an archive, leading `./' is no longer stripped,
845 to match traditional tar's behavior (and simplify the documentation).
846
847 * --diff without --absolute-names no longer falls back on absolute names.
848
849 \f
850 version 1.13.6 - Paul Eggert, 1999-08-11.
851
852 * An --exclude pattern containing / now excludes a file only if it matches an
853 initial prefix of the file name; a pattern without / continues to
854 exclude a file if it matches any file name component.
855
856 * The protocol for talking to rmt has been extended slightly.
857 Open flags are now communicated in symbolic format as well as numeric.
858 The symbolic format (e.g., "O_WRONLY|O_CREAT|O_TRUNC") is for portability
859 when rmt is operating on a different operating system from tar.
860 The numeric format is retained, and rmt uses it if symbolic format is absent,
861 for backward compatibility with older versions of tar and rmt.
862
863 * When writing GNU tar format headers, tar now uses signed base-64
864 for values that cannot be represented in unsigned octal.
865 This supports larger files (2**66 - 1 bytes instead of 2**33 - 1 bytes),
866 larger uids, negative time stamps, etc.
867
868 * When extracting files with unknown ownership, tar now looks up the
869 uid and gid "nobody" on hosts whose headers do not define UID_NOBODY
870 and GID_NOBODY, and falls back on uid/gid -2 if there is no "nobody".
871
872 * tar -t --numeric-owner now prints numeric uids and gids, not symbolic.
873
874 * New option -y or --bzip2 for bzip2 compression, by popular request.
875
876 \f
877 version 1.13.5 - Paul Eggert, 1999-07-20.
878
879 * Do the delayed updates of file metadata even after a fatal error.
880
881 \f
882 version 1.13.4 - Paul Eggert, 1999-07-20.
883
884 * Do not chmod unless we are root or the -p option was given;
885 this matches historical practice.
886
887 \f
888 version 1.13.3 - Paul Eggert, 1999-07-16.
889
890 * A path name is excluded if any of its file name components matches an
891 excluded pattern, even if the path name was specified on the command line.
892 Also see 1.13.6 for later changes in this area.
893
894 \f
895 version 1.13.2 - Paul Eggert, 1999-07-14.
896
897 * Bug reporting address changed to <bug-tar@gnu.org>.
898
899 \f
900 version 1.13.1 - Paul Eggert, 1999-07-12.
901
902 * Bug fixes only.
903 \f
904 version 1.13 - Paul Eggert, 1999-07-08.
905
906 * Support for large files, e.g., files larger than 2 GB on many 32-bit hosts.
907 Also, support for larger uids, device ids, etc.
908 * Many bug fixes and porting fixes.
909 * This release is only for fixes. A more ambitious test release,
910 with new features, is available as part of the paxutils. Please see:
911 ftp://alpha.gnu.org/gnu/paxutils/
912 The fixes in this release are intended to be merged with paxutils
913 at some point, but they haven't been merged yet.
914 * An interim GNU tar alpha had new --bzip2 and --ending-file options,
915 but they have been removed to maintain compatibility with paxutils.
916 Please try --use=bzip2 instead of --bzip2.
917 \f
918 Version 1.12 - François Pinard, 1997-04.
919
920 Sensitive matters
921 * Use shell globbing patterns for --label, instead of regular expressions.
922 * Do not quote anymore internally over the quoting done by the shell.
923
924 Output for humans
925 * Offer internationalization capabilities of most recent GNU gettext.
926 * Messages available in many more languages, thanks to all translators!
927 * Usage of ISO 8601 dates in listings, instead of local American dates.
928 * More normalization and cleanup in error messages.
929
930 Creation
931 * For helping using tar with find, offer a --no-recursion option.
932 * Implement --numeric-owner for ignoring symbolic names at create time.
933 * New --owner, --group --mode options, still preliminary.
934 * Recognize creating an archive on /dev/null, so Amanda works faster.
935 * Object to the creation of an empty archive (like in `tar cf FILE').
936 * Barely start implementing --posix and POSIXLY_CORRECT.
937
938 Extraction
939 * Make a better job at restoring file and directory attributes.
940 * Automatically attempt deleting existing files when in the way.
941 * Option --unlink-first (-U) removes most files prior to extraction.
942 * Option --recursive-unlink removes non-empty directories when in the way.
943 * Option --numeric-owner ignores owner/group names, it uses UID/GID instead.
944 * Use global umask when creating missing intermediate directories.
945 * When symlinks are not available, extract symbolic links as hard links.
946 * Diagnose extraction of contiguous files as regular files.
947 * New --backup, --suffix and --version-control options.
948
949 Various changes
950 * Better support of huge archives with --tape-length and --totals.
951 * Rename option --read-full-blocks (-B) to --read-full-records (-B).
952 * Rename option --block-size (-b) to --blocking-factor (-b).
953 * Rename option --record-number (-R) to --block-number (-R).
954 * With --block-number (-R), report null blocks and end of file.
955 * Implement --record-size for introducing a size in bytes.
956 * Delete --block-compress option and rather decide it automatically.
957 * Rename option --modification-time to --touch.
958
959 Many bugs are squashed, while others still run free.
960 \f
961 Version 1.11.8 - François Pinard, 1995-06.
962
963 * Messages available in French, German, Portuguese and Swedish.
964 * The distribution provides a rudimentary Texinfo manual.
965 * The device defaults to stdin/stdout, unless overridden by the installer.
966 * Option --sparse (-S) should work on more systems.
967 * Option --rsh-command may select an alternative remote shell program.
968
969 Most changes are internal, and should yield better portability.
970 \f
971 Version 1.11.2 - Michael Bushnell, 1993-03.
972
973 * Changes in backup scripts: cleaned up considerably; notices error
974 conditions better over rsh; DUMP_REMIND_SCRIPT is now an option in
975 backup-specs; new file dump-remind is an example of a
976 DUMP_REMIND_SCRIPT.
977
978 * Superfluous "Reading dirname" was a bug; fixed.
979
980 * Incompatibility problems with a bug on Solaris are fixed.
981
982 * New option --gzip (aliases are --ungzip and -z); calls gzip instead
983 of compress. Also, --use-compress-program lets you specify any
984 compress program. --compress-block is renamed --block-compress and
985 now requires one of the three compression options to be specified.
986
987 * Several error messages are cleaned up.
988
989 * Directory owners are now set properly when running as root.
990
991 * Provide DUMP_REMIND_SCRIPT in backup-specs as a possible option
992 for --info-script.
993
994 * Behave better with broken rmt servers.
995
996 * Dump scripts no longer use --atime-preserve; this causes a nasty probem.
997
998 * Several Makefile cleanups.
999 \f
1000 Version 1.11.1 - Michael Bushnell, 1992-09.
1001
1002 * Many bug fixes.
1003 \f
1004 Version 1.11 - Michael Bushnell, 1992-09.
1005 Version 1.10.16 - 1992-07.
1006 Version 1.10.15 - 1992-06.
1007 Version 1.10.14 - 1992-05.
1008 Version 1.10.13 - 1992-01.
1009
1010 * Many bug fixes.
1011
1012 * Now uses GNU standard configure, generated by Autoconf.
1013
1014 * Long options now use `--'; use of `+' is deprecated and support
1015 for it will eventually be removed.
1016
1017 * New option --null causes filenames read by -T to be
1018 null-terminated, and causes -C to be ignored.
1019
1020 * New option --remove-files deletes files (but not directories)
1021 after they are added to the archive.
1022
1023 * New option --ignore-failed-read prevents read-errors from affecting
1024 the exit status.
1025
1026 * New option --checkpoint prints occasional messages as the tape
1027 is being read or written.
1028
1029 * New option --show-omitted-dirs prints the names of directories
1030 omitted from the archive.
1031
1032 * Some tape drives which use a non-standard method of indicating
1033 end-of-tape now work correctly with multi-tape archives.
1034
1035 * --volno-file: Read the volume number used in prompting the user
1036 (but not in recording volume ID's on the archive) from a file.
1037
1038 * When using --multi-volume, you can now give multiple -f arguments;
1039 the various tape drives will get used in sequence and then wrap
1040 around to the beginning.
1041
1042 * Remote archive names no longer have to be in /dev: any file with a
1043 `:' is interpreted as remote. If new option --force-local is given,
1044 then even archive files with a `:' are considered local.
1045
1046 * New option --atime-preserve restores (if possible) atimes to
1047 their original values after dumping the file.
1048
1049 * No longer does tar confusingly dump "." when you don't tell it
1050 what to dump.
1051
1052 * When extracting directories, tar now correctly restores their
1053 modification and access times.
1054
1055 * Longnames support is redone differently--long name info directly
1056 precedes the long-named file or link in the archive, so you no
1057 longer have to wait for the extract to hit the end of the tape for
1058 long names to work.
1059 \f
1060 Version 1.10 - Michael Bushnell, 1991-07.
1061
1062 * Filename to -G is optional. -C works right. Names +newer and
1063 +newer-mtime work right.
1064
1065 * -g is now +incremental, -G is now +listed-incremental.
1066
1067 * Sparse files now work correctly.
1068
1069 * +volume is now called +label.
1070
1071 * +exclude now takes a filename argument, and +exclude-from does
1072 what +exclude used to do.
1073
1074 * Exit status is now correct.
1075
1076 * +totals keeps track of total I/O and prints it when tar exits.
1077
1078 * When using +label with +extract, the label is now a regexp.
1079
1080 * New option +tape-length (-L) does multi-volume handling like BSD
1081 dump: you tell tar how big the tape is and it will prompt at that
1082 point instead of waiting for a write error.
1083
1084 * New backup scripts level-0 and level-1 which might be useful
1085 to people. They use a file "backup-specs" for information, and
1086 shouldn't need local modification. These are what we use to do
1087 all our backups at the FSF.
1088 \f
1089 Version 1.09 - Jay Fenlason, 1990-10.
1090 Version 1.08 - Jay Fenlason, 1990-01.
1091 Versions 1.07 back to 1.00 by Jay Fenlason.
1092
1093 * See ChangeLog for more details.
1094
1095 \f
1096
1097 Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2003,
1098 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
1099
1100 This file is part of GNU tar.
1101
1102 GNU tar is free software; you can redistribute it and/or modify
1103 it under the terms of the GNU General Public License as published by
1104 the Free Software Foundation; either version 3, or (at your option)
1105 any later version.
1106
1107 GNU tar is distributed in the hope that it will be useful,
1108 but WITHOUT ANY WARRANTY; without even the implied warranty of
1109 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
1110 GNU General Public License for more details.
1111
1112 You should have received a copy of the GNU General Public License
1113 along with tar; see the file COPYING. If not, write to
1114 the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
1115 Boston, MA 02110-1301, USA.
1116 \f
1117 Local variables:
1118 mode: outline
1119 paragraph-separate: "[ \f]*$"
1120 eval: (add-hook 'write-file-hooks 'time-stamp)
1121 time-stamp-start: "changes. "
1122 time-stamp-format: "%:y-%02m-%02d"
1123 time-stamp-end: "\n"
1124 end:
This page took 0.079175 seconds and 5 git commands to generate.