|
DataMuseum.dkPresents historical artifacts from the history of: ICL Comet 32 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about ICL Comet 32 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 5423 (0x152f)
Types: TextFile
Notes: UNIX file
Names: »mkfs.8«
└─⟦26887b7e0⟧ Bits:30009717 Comet 32 harddisk image
└─⟦28c352965⟧ »/a« UNIX Filesystem
└─⟦this⟧ »usr/man/cat8/mkfs.8«
1
MKFS(8) UNIX Programmer's Manual MKFS(8)
NAME
mkfs - construct a file system
SYNOPSIS
/etc/mkfs special size [ m n ]
/etc/mkfs special proto
DESCRIPTION
_▶08◀M_▶08◀k_▶08◀f_▶08◀s constructs a file system by writing on the special
file _▶08◀s_▶08◀p_▶08◀e_▶08◀c_▶08◀i_▶08◀a_▶08◀l. In the first form of the command a numeric
size is given and _▶08◀m_▶08◀k_▶08◀f_▶08◀s builds a file system with a single
empty directory on it. The number of i-nodes is calcu-
lated as a function of the filesystem size. (No boot pro-
gram is initialized in this form of _▶08◀m_▶08◀k_▶08◀f_▶08◀s.)
N.B.: All filesystems should have a _▶08◀l_▶08◀o_▶08◀s_▶08◀t+_▶08◀f_▶08◀o_▶08◀u_▶08◀n_▶08◀d directory
for _▶08◀f_▶08◀s_▶08◀c_▶08◀k(8); this should be created for each file system
by running _▶08◀m_▶08◀k_▶08◀l_▶08◀o_▶08◀s_▶08◀t+_▶08◀f_▶08◀o_▶08◀u_▶08◀n_▶08◀d(8) in the root directory of a
newly created file system, after the file system is first
mounted.
In bootstrapping, the second form of _▶08◀m_▶08◀k_▶08◀f_▶08◀s is sometimes
used. In this form, the file system is constructed
according to the directions found in the prototype file
_▶08◀p_▶08◀r_▶08◀o_▶08◀t_▶08◀o. The prototype file contains tokens separated by
spaces or new lines. The first token is the name of a
file to be copied onto sector zero as the bootstrap pro-
gram. The second token is a number specifying the size of
the created file system. Typically it will be the number
of blocks on the device, perhaps diminished by space for
swapping. The next token is the number of i-nodes in the
i-list. The next set of tokens comprise the specification
for the root file. File specifications consist of tokens
giving the mode, the user-id, the group id, and the ini-
tial contents of the file. The syntax of the contents
field depends on the mode.
The mode token for a file is a 6 character string. The
first character specifies the type of the file. (The
characters -bcd specify regular, block special, character
special and directory files respectively.) The second
character of the type is either u or - to specify set-
user-id mode or not. The third is g or - for the set-
group-id mode. The rest of the mode is a three digit
octal number giving the owner, group, and other read,
write, execute permissions, see _▶08◀c_▶08◀h_▶08◀m_▶08◀o_▶08◀d(1).
Two decimal number tokens come after the mode; they
specify the user and group ID's of the owner of the file.
If the file is a regular file, the next token is a path-
name whence the contents and size are copied.
If the file is a block or character special file, two
decimal number tokens follow which give the major and
minor device numbers.
If the file is a directory, _▶08◀m_▶08◀k_▶08◀f_▶08◀s makes the entries . and
1
MKFS(8) UNIX Programmer's Manual MKFS(8)
.. and then reads a list of names and (recursively) file
specifications for the entries in the directory. The scan
is terminated with the token $.
A sample prototype specification follows:
/usr/mdec/uboot
4872 55
d--777 3 1
usr d--777 3 1
sh ---755 3 1 /bin/sh
ken d--755 6 1
$
b0 b--644 3 1 0 0
c0 c--644 3 1 0 0
$
$
The arguments m and n specify the interleave factor. M
should always be 3 and you should use the following table
to choose n. as follows.
RM03 80
RM05 304
RM80 217
RP06 209
RP07 800
SI/CDC 9766 304
RK07 33
EMULEX/AMPEX 300M 304
EMULEX/FUJITSU 160M 160
SEE ALSO
filsys(5), dir(5), fsck(8), mklost+found(8)
BUGS
There should be some way to specify links.
There should be some way to specify bad blocks.
Should make _▶08◀l_▶08◀o_▶08◀s_▶08◀t+_▶08◀f_▶08◀o_▶08◀u_▶08◀n_▶08◀d automatically.
2