From 93aa30a8df668b3ad5806c417acb65d2a4663178 Mon Sep 17 00:00:00 2001 From: rsc Date: Fri, 14 Jan 2005 03:27:51 +0000 Subject: some changes --- man/man1/0intro.1 | 43 ++++++++++++++++++++++++------------------- man/man1/9.1 | 51 +++++++++++++++++++++++++++++++++++++++++++++++---- man/man1/INDEX | 1 + man/man1/mk.1 | 20 +++----------------- 4 files changed, 75 insertions(+), 40 deletions(-) (limited to 'man/man1') diff --git a/man/man1/0intro.1 b/man/man1/0intro.1 index 610e7911..6e86bb44 100644 --- a/man/man1/0intro.1 +++ b/man/man1/0intro.1 @@ -30,7 +30,7 @@ they expect the environment variable to contain the name of the root of the tree. See -.IR install (8) +.IR install (1) for details about installation. .PP Many of the familiar Unix commands, @@ -127,6 +127,15 @@ The .IR 9p (1) client can be used in shell scripts or by hand to carry out simple interactions with servers. +.SS External databases +Some programs rely on large databases that would be +cumbersome to include in every release. +Scripts are provided that download these databases separately. +These databases can be downloaded separately. +See +.B $PLAN9/dict/README +and +.BR $PLAN9/sky/README . .SS Programming The shell scripts .I 9c @@ -187,15 +196,6 @@ can be relied upon to produce reasonable stack traces cannot) and dump data structures, but that it is the extent to which they have been developed and exercised. -.SS External databases -Some programs rely on large databases that would be -cumbersome to include in every release. -Scripts are provided that download these databases separately. -These databases can be downloaded separately. -See -.B $PLAN9/dict/README -and -.BR $PLAN9/sky/README . .SS Porting programs The vast majority of the familiar Plan 9 programs have been ported, including the Unicode-aware @@ -244,8 +244,8 @@ and the implementation of .IR getcallerpc (3), but these are usually simple and are not on the critical path for getting the system up and running. -.SS SEE ALSO -The system's documentation is these manual pages. +.SH SEE ALSO +The rest of this manual describes Plan 9 from User Space. Many of the man pages have been brought from Plan 9, but they have been updated, and others have been written from scratch. .PP @@ -276,19 +276,24 @@ directly, as in The manual sections follow the Unix numbering conventions, not the Plan 9 ones. .PP -Section (1) describes general publicly accessible commands. +.HR ../man1 "Section (1) +describes general publicly accessible commands. .PP -Section (3) describes C library functions. +.HR ../man3 "Section (3) +describes C library functions. .PP -Section (4) describes user-level file servers. +.HR ../man4 "Section (4) +describes user-level file servers. .PP -Section (7) describes file formats and protocols. +.HR ../man7 "Section (7) +describes file formats and protocols. (On Unix, section (5) is technically for file formats but seems now to be used for describing specific files.) +.\" .PP +.\" Section (8) describes commands used for system administration. .PP -Section (8) describes commands used for system administration. -.PP -Section (9p) describes the Plan 9 file protocol 9P. +.HR ../man9 "Section (9p) +describes the Plan 9 file protocol 9P. .SH DIAGNOSTICS In Plan 9, a program's exit status is an arbitrary text string, while on Unix it is an integer. diff --git a/man/man1/9.1 b/man/man1/9.1 index d590f3b3..24ce0226 100644 --- a/man/man1/9.1 +++ b/man/man1/9.1 @@ -2,17 +2,60 @@ .SH NAME 9 \- run Plan 9 commands .SH SYNOPSIS -.B . -.B 9 -.PP .B 9 .I cmd [ .I args \&... ] +.PP +.B . +.B 9 .SH DESCRIPTION -XXX +Because Plan 9 supplies commands with the same name as but different +behavior than many basic Unix system commands +(e.g., +.BR grep , +.BR sed , +.BR mkdir , +.BR rm ), +it is not recommended to run with the Plan 9 bin directory +ahead of the system directories. +.PP +.I 9 +is a shell script that sets up a Plan 9 environment and runs +.I cmd . +It sets +.B $PLAN9 +and adds +.B $PLAN9/bin +to the beginning of +.B $PATH +before running +.IR cmd . +.PP +If run with no arguments, +.B 9 +does not do anything. This is so that it can be invoked from +.IR sh -style +shells using +.B . +.B 9 +in order to make the current shell start running in the Plan 9 environment. +.SH EXAMPLES +Search for greek in the password file: +.IP +.EX +$ 9 grep '[α-ζ]' /etc/passwd +.EE +.PP +Start an +.IR rc (1) +with the Plan 9 commands in the path before the system commands. +.IP +.EX +9 rc +.EE .SH SOURCE .B \*9/bin/9 .SH SEE ALSO diff --git a/man/man1/INDEX b/man/man1/INDEX index fcd708c7..629dc654 100644 --- a/man/man1/INDEX +++ b/man/man1/INDEX @@ -169,6 +169,7 @@ tr tr.1 tr2post tr2post.1 nroff troff.1 troff troff.1 +troff2html troff2html.1 tweak tweak.1 uniq uniq.1 units units.1 diff --git a/man/man1/mk.1 b/man/man1/mk.1 index caa2d176..6ef12499 100644 --- a/man/man1/mk.1 +++ b/man/man1/mk.1 @@ -1,6 +1,6 @@ .TH MK 1 .SH NAME -mk, membername \- maintain (make) related files +mk \- maintain (make) related files .SH SYNOPSIS .B mk [ @@ -13,10 +13,6 @@ mk, membername \- maintain (make) related files [ .I target ... ] -.PP -.B membername -.IR lib ( object ) -\&... .SH DESCRIPTION .I Mk uses the dependency rules specified in @@ -529,18 +525,6 @@ Currently, the only aggregates supported are (see .IR 9c (1)) archives. -.PP -.I Membername -echoes just the member names of a list of aggregate names. -It is useful in recipes like: -.IP -.EX -OFILES=a.o b.o -libc.a(%):N: % -libc.a: ${OFILES:%=libc.a(%)} - 9ar rvc libc.a `membername $newprereq` -.EE -which re-archives only the new object files. .SS Attributes The colon separating the target from the prerequisites may be @@ -669,6 +653,8 @@ rule: x.tab.h:Pcmp -s: y.tab.h cp y.tab.h x.tab.h .EE +.SH SOURCE +.B /usr/local/plan9/src/cmd/mk .SH SEE ALSO .IR sh (1), .IR regexp (7) -- cgit v1.2.3