This patch cleans up ramfs(4) and /sys/src/cmd/ramfs.c, to be in
sync.

Notes:
Thu Sep 22 08:44:03 EDT 2005 rsc
    Nice work.  Thanks.


Reference: /n/sources/patch/applied/ramfs-man-sync
Date: Thu Sep 22 11:16:22 CES 2005
Reviewed-by: rsc

--- /sys/src/cmd/ramfs.c	Thu Sep 22 11:15:46 2005
+++ /sys/src/cmd/ramfs.c	Thu Sep 22 11:15:41 2005
@@ -887,6 +887,6 @@
 void
 usage(void)
 {
-	fprint(2, "usage: %s [-is] [-m mountpoint]\n", argv0);
+	fprint(2, "usage: %s [-Dips] [-m mountpoint] [-S srvname]\n", argv0);
 	exits("usage");
 }
--- /sys/man/4/ramfs	Thu Sep 22 11:16:04 2005
+++ /sys/man/4/ramfs	Thu Sep 22 11:16:00 2005
@@ -4,18 +4,16 @@
 .SH SYNOPSIS
 .B ramfs
 [
-.B -i
-]
-[
-.B -s
-]
-[
-.B -p
+.B -Dips
 ]
 [
 .B -m
 .I mountpoint
 ]
+[
+.B -S
+.I srvname
+]
 .SH DESCRIPTION
 .I Ramfs
 starts a process that mounts itself (see
@@ -32,6 +30,10 @@
 Initially the file tree is empty.
 .PP
 The
+.B -D
+option enables a trace of general debugging messages.
+.PP
+The
 .B -i
 flag tells
 .I ramfs
@@ -43,27 +45,32 @@
 and 1 will be the network channel from
 .I ramfs
 to the client machine.
+.PP
+The
+.B -p
+flag causes
+.I ramfs
+to make its memory `private'
+(see
+.IR proc (3))
+so that its files are not accessible through the debugging interface.
+.PP
 The
 .B -s
 flag causes
 .I ramfs
 to post its channel on
 .B /srv/ramfs
+or
+.I srvname,
+when
+.B -S is specified,
 rather than mounting it on
 .IR mountpoint ,
 enabling multiple clients to access its files.
 However, it does not authenticate its clients and its
 implementation of groups is simplistic, so
 it should not be used for precious data.
-.PP
-The
-.B -p
-flag causes
-.I ramfs
-to make its memory `private'
-(see
-.IR proc (3))
-so that its files are not accessible through the debugging interface.
 .PP
 This program is useful mainly as an example of how
 to write a user-level file server.