NEWS 44 KB

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