Various spelling/formatting changes.

Submitted by: Philippe Charnier <charnier@xp11.frmug.org>

Clarify the example a bit.

PR: 6801
Reviewed by: David Kelly <dkelly@hiwaay.net>

Correct use of .Nm. Add rcsid.

.Sh AUTHOR -> .Sh AUTHORS
Use .An/.Aq

Revert $FreeBSD$ to $Id$

Make the long-awaited change from $Id$ to $FreeBSD$

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

Make the long-awaited change from $Id$ to $FreeBSD$

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.

show more ...

Fix possible FS corruption caused by extra parameter to pax.
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 "potent

Fix possible FS corruption caused by extra parameter to pax.
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

show more ...

Added $Id$

BSD 4.4 Lite bin Sources

Markup fixes.

Fix the wording about the blocksize (-b) parameter. The existing
wording makes it look like pax archives > 32256 bytes are not
POSIX-compliant! Correct this to state that pax archives with
block size

Fix the wording about the blocksize (-b) parameter. The existing
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>

show more ...

Add the new standard EXIT STATUS section where appropriate.
Sort standard sections in the (documented) preferred order.

/*- or .\"- or #- to begin license clauses.

Document missing multibyte character handling in utilities specified
by POSIX.

Deal with double whitespace.

Mechanically kill hard sentence breaks.

Remove clause 3 from the UCB licenses.

OK'ed by: imp, core

Make the "tarcp" example more direct.

/dev/sa0 is the default tape device, not /dev/rst0.

s/filesystem/file system/ as discussed on -developers

Consistancy check s/file system/filesystem/

Reviewed by: brian

Use `The .Nm utility'

mdoc(7) police: s/BSD/.Bx/ where appropriate.

mdoc(7) police: join split punctuation to macro calls.

Remove whitespace at EOL.