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