Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ mkfs(8) — GENIX 4.1A

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

filsys(5)

dir(5)

fsck(8)

mklost+found(8)



      MKFS(8)                 GENIX Programmer's Manual                 MKFS(8)



      NAME
           mkfs - construct a file system

      SYNOPSIS
           /etc/mkfs special size [ m n ]
           /etc/mkfs special proto

      DESCRIPTION
           Mkfs constructs a file system by writing on the  special  file  spe-
           cial.  In  the first form of the command a numeric size is given and
           mkfs builds a file system with a single empty directory on it.   The
           number  of  i-nodes  is  calculated  as a function of the filesystem
           size.  (No boot program is initialized in this form of mkfs.)

           N.B.:  All  filesystems  should  have  a  lost+found  directory  for
           fsck(8);  this  should  be  created  for each file system by running
           mklost+found(8) in the root directory of a newly created  file  sys-
           tem, after the file system is first mounted.

           In bootstrapping, the second form of mkfs  is  sometimes  used.   In
           this  form,  the  file system is constructed according to the direc-
           tions found in the prototype file proto. 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 specifi-
           cations consist of tokens giving the mode, the  user-id,  the  group
           id,  and  the  initial contents of the file.  The syntax of the con-
           tents field depends on the mode.

           The mode token for a file is a 6 character string.  The first  char-
           acter  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 chmod(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  pathname  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.





      Printed 11/16/83                                                        1





      MKFS(8)                 GENIX Programmer's Manual                 MKFS(8)



           If the file is a directory, mkfs makes the entries  .   and  ..  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 lost+found automatically.














      Printed 11/16/83                                                        2



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026