From: Steve Lord <lord@sgi.com>
Date: Fri, 3 Oct 2003 20:04:27 +0000 (+0000)
Subject: nuke prototype section for now
X-Git-Tag: v2.6.0~7
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=00920558f643942838d79a925a9627c33d4d26e3;p=thirdparty%2Fxfsprogs-dev.git

nuke prototype section for now
remove text
---

diff --git a/man/man8/mkfs.xfs.8 b/man/man8/mkfs.xfs.8
index a129c2fe7..70b26b6e0 100644
--- a/man/man8/mkfs.xfs.8
+++ b/man/man8/mkfs.xfs.8
@@ -426,144 +426,6 @@ in which case the default value is the filesystem block size.
 For version 1 directories the block size is the same as the 
 filesystem block size.
 .TP
-\f3\-p\f1 \f2protofile\f1
-If the optional
-.B \-p
-.I protofile
-argument is given,
-.I mkfs.xfs
-uses
-.I protofile
-as a prototype file
-and takes its directions from that file.
-The blocks and inodes
-specifiers in the
-.I protofile
-are provided for backwards compatibility, but are otherwise unused.
-The prototype file
-contains tokens separated by spaces or
-newlines.
-A sample prototype specification follows (line numbers have been added to
-aid in the explanation):
-.nf
-.sp .8v
-.in +5
-\f71       /stand/\f1\f2diskboot\f1\f7
-2       4872 110
-3       d--777 3 1
-4       usr     d--777 3 1
-5       sh      ---755 3 1 /bin/sh
-6       ken     d--755 6 1
-7               $
-8       b0      b--644 3 1 0 0
-9       c0      c--644 3 1 0 0
-10      fifo    p--644 3 1
-11      slink   l--644 3 1 /a/symbolic/link
-12      :  This is a comment line
-13      $
-14      $\f1
-.in -5
-.fi
-.IP
-Line 1 is a dummy string.
-(It was formerly the bootfilename.)
-It is present for backward
-compatibility; boot blocks are not used on SGI systems.
-.IP
-Note that some string of characters must be present as the first line of
-the proto file to cause it to be parsed correctly; the value
-of this string is immaterial since it is ignored.
-.IP
-Line 2 contains two numeric values (formerly the numbers of blocks and inodes).
-These are also merely for backward compatibility: two numeric values must
-appear at this point for the proto file to be correctly parsed,
-but their values are immaterial since they are ignored.
-.IP
-Lines 3-11 tell
-.I mkfs.xfs
-about files and directories to
-be included in this filesystem.
-Line 3 specifies the root directory.
-Lines 4-6 and 8-10 specifies other directories and files.
-Note the special symbolic link syntax on line 11.
-.IP
-The
-.B $
-on line 7 tells
-.I mkfs.xfs
-to end the branch of the filesystem it is on, and continue
-from the next higher directory.
-It must be the last character
-on a line.
-The colon
-on line 12 introduces a comment; all characters up until the
-following newline are ignored.
-Note that this means you cannot
-have a file in a prototype file whose name contains a colon.
-The
-.B $
-on lines 13 and 14 end the process, since no additional
-specifications follow.
-.IP
-File specifications give the mode,
-the user ID,
-the group ID,
-and the initial contents of the file.
-Valid syntax for the contents field
-depends on the first character of the mode.
-.IP
-The mode for a file is specified by a 6-character string.
-The first character
-specifies the type of the file.
-The character range is
-.B \-bcdpl
-to specify regular, block special,
-character special, directory files, named pipes (fifos), and symbolic
-links, respectively.
-The second character of the mode
-is either
-.B u
-or
-.B \-
-to specify setuserID mode or not.
-The third is
-.B g
-or
-.B \-
-for the setgroupID mode.
-The rest of the mode
-is a three digit octal number giving the
-owner, group, and other read, write, execute
-permissions (see
-.IR chmod (1)).
-.IP
-Two decimal number
-tokens come after the mode; they specify the
-user and group IDs of the owner of the file.
-.IP
-If the file is a regular file,
-the next token of the specification can be a pathname
-from which the contents and size are copied.
-If the file is a block or character special file,
-two decimal numbers
-follow that give the major and minor device numbers.
-If the file is a symbolic link, the next token of the specification
-is used as the contents of the link.
-If the file is a directory,
-.I mkfs.xfs
-makes the entries
-.BR . ""
-and
-.B  ..
-and then
-reads a list of names and
-(recursively)
-file specifications for the entries
-in the directory.
-As noted above, the scan is terminated with the
-token
-.BR $ .
-.TP
 .B \-q
 Quiet option.
 .IP