summaryrefslogtreecommitdiffstats
path: root/bin/pax/pax.1
Commit message (Collapse)AuthorAgeFilesLines
* dump(1) -> dump(8).trasz2016-02-291-1/+1
| | | | | MFC after: 1 month Sponsored by: The FreeBSD Foundation
* Implement pax -O option to permit limiting a PAX archive to a single volume.eadler2015-03-181-5/+13
| | | | | | | | | -O Force the archive to be one volume. If a volume ends prematurely, pax will not prompt for a new volume. PR: 198481 Submitted by: Sevan Janiyan Reviewed by: allanjude (doc)
* Document the lack of chflags support in pax(1)crees2013-12-211-1/+19
| | | | | | PR: docs/135516 Submitted by: arundel (based on) Approved by: gjb (mentor)
* Touch the man page date after updating the ustar limitations.brian2010-08-291-1/+1
| | | | MFC after: 3 weeks
* Correct an out-by-one error when earlying out ustar filenames thatbrian2010-08-291-1/+3
| | | | | | | | | | | | | are too long. Filenames escaping this test are caught later on, so the bug doesn't cause any breakage. Document the correct ustar limitations in pax. As I have no access to the IEEE 1003.2 spec, I can only assume that the limitations imposed are in fact correct. Add regression tests for the filename limitations imposed by pax. MFC after: 3 weeks
* Markup fixes.ru2006-09-171-1/+2
|
* Fix the wording about the blocksize (-b) parameter. The existingcokane2006-05-101-2/+3
| | | | | | | | | wording makes it look like pax archives > 32256 bytes are not POSIX-compliant! Correct this to state that pax archives with block sizes > 32256 are not POSIX compliant...and settle our fears. PR: docs/97059 Reviewed by: Giorgos Keramidas <keramida>
* Add the new standard EXIT STATUS section where appropriate.ru2005-01-161-49/+49
| | | | Sort standard sections in the (documented) preferred order.
* /*- or .\"- or #- to begin license clauses.imp2005-01-101-0/+1
|
* Document missing multibyte character handling in utilities specifiedtjr2004-07-031-1/+5
| | | | by POSIX.
* Deal with double whitespace.ru2004-07-031-2/+2
|
* Mechanically kill hard sentence breaks.ru2004-07-021-2/+2
|
* Remove clause 3 from the UCB licenses.markm2004-04-061-4/+0
| | | | OK'ed by: imp, core
* Make the "tarcp" example more direct.obrien2003-01-101-5/+5
|
* /dev/sa0 is the default tape device, not /dev/rst0.tjr2002-10-061-2/+2
|
* s/filesystem/file system/ as discussed on -developerstrhodes2002-08-211-6/+6
|
* Consistancy check s/file system/filesystem/trhodes2002-05-161-6/+6
| | | | Reviewed by: brian
* Use `The .Nm utility'charnier2002-04-211-23/+24
|
* mdoc(7) police: s/BSD/.Bx/ where appropriate.ru2001-08-141-1/+4
|
* mdoc(7) police: join split punctuation to macro calls.ru2001-08-101-7/+6
|
* Remove whitespace at EOL.dd2001-07-151-39/+39
|
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-101-1/+6
|
* mdoc(7) police: remove extraneous .Pp before and/or after .Sh.dd2001-07-091-2/+0
|
* mdoc(7) police: sort xrefs.ru2001-05-081-2/+2
|
* Sync up with OpenBSD. Too many changes to note, but the major featureskris2001-05-081-1/+7
| | | | | | | | | | | | | | are: * Implement cpio compatibility mode when pax is invoked as cpio * Extend tar compatibility mode to cover many of the GNU tar single-letter options (bzip2 mode, aka -y/-j is not present in OpenBSD). When invoked as tar, pax is now full-featured enough for use by the ports collection to extract distfiles and create packages. * Many bug fixes to the operation of pax and the tar compatibility modes * Code fixes for things like correct string buffer termination. I tried to preserve existing FreeBSD fixes to this utility; please let me know if I have inadvertently spammed something.
* Add -z flag to pax to allow gzipping of archive output. Add -z and -Z (gzipkris2001-05-051-3/+10
| | | | | | | | | | | | | | and compress) to pax when used in tar mode (invoked as 'tar') for compatibility with GNU tar. bzip2 functionality for further GNU tar compatibility will be added at a later date. Note in the manpage that -z is non-standard. Obtained from: OpenBSD Reviewed by: -hackers MFC after: 2 weeks
* mdoc(7) police: use the default ``file ...'' feature of the .Ar macro.ru2001-02-131-2/+2
|
* mdoc(7) police: split punctuation characters + misc fixes.ru2001-02-011-5/+5
|
* Prepare for mdoc(7)NG.ru2000-12-181-24/+24
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-5/+5
|
* Remove more single-space hard sentence breaks.sheldonh2000-03-021-1/+2
|
* Remove single-space hard sentence breaks. These degrade the qualitysheldonh2000-03-011-1/+2
| | | | | of the typeset output, tend to make diffs harder to read and provide bad examples for new-comers to mdoc.
* $Id$ -> $FreeBSD$peter1999-08-271-1/+1
|
* Various spelling/formatting changes.kris1999-05-081-2/+2
| | | | Submitted by: Philippe Charnier <charnier@xp11.frmug.org>
* Clarify the example a bit.steve1998-05-311-6/+6
| | | | | PR: 6801 Reviewed by: David Kelly <dkelly@hiwaay.net>
* Correct use of .Nm. Add rcsid.charnier1998-05-151-32/+32
|
* .Sh AUTHOR -> .Sh AUTHORScharnier1998-03-191-3/+4
| | | | Use .An/.Aq
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* Fix possible FS corruption caused by extra parameter to pax.nate1995-08-161-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | oo Turns out, it's pretty important if you use PAX for backup. In the man page for PAX, there is an error (OK, we could call it a "potentially catastrophic incompleteness"). It reads: > The command: > > pax -r -v -f filename > > gives the verbose table of contents for an archive stored in filename. Yup, it does do that. With a side effect: it also _replaces_ all the files that come in from the archive. As is my custom, I did my backup-validation real soon after the backup was written. Precisely because I've seen the same sort of thing happen on other systems. So all that file-restoring didn't do a lot of damage. Probably helped my fragmentation somewhat (aha, an online defragger?) It did confuse one hapless user, who lost an email message he _knew_ he hadn't deleted. Apparently the system restored the file as of just before that critical message came in. The correct entry should read: > The command: > > pax -v -f filename > > gives the verbose table of contents for an archive stored in filename. Submitted by: John Beckett <jbeckett@southern.edu> via the BSDI mailing list
* Added $Id$dg1994-09-241-0/+1
|
* BSD 4.4 Lite bin Sourcesrgrimes1994-05-261-0/+1169
OpenPOWER on IntegriCloud