NAME

bifmkfs − construct a Bell file system

SYNOPSIS

bifmkfs special blocks[:inodes] [gap blocks]
bifmkfs special proto [gap blocks]

HP-UX COMPATIBILITY

Level: HP-UX/NUCLEUS

Origin: HP

DESCRIPTION

Bifmkfs constructs a Bell file system by writing on the special file according to the directions found in the remainder of the command line.  If the second argument is given as a string of digits, bifmkfs builds a file system with a single empty directory on it. The size of the file system is the value of blocks interpreted as a decimal number.  The boot program is left uninitialized. If the optional number of inodes is not given, the default is the number of blocks divided by 4. 

If the second argument is a file name that can be opened, bifmkfs assumes it to be a prototype file proto, and will take its directions from that file. The prototype file contains tokens separated by spaces or new-lines. The first token is the name of a file to be copied onto block zero as the bootstrap program. 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 i-list size in blocks 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 initial 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 bifchmod(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, bifmkfs 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:

/stand/diskboot
4872 110
d−−777 3 1
usrd−−777 3 1
sh−−−755 3 1 /bin/sh
kend−−755 6 1
$
b0b−−644 3 1 0 0
c0c−−644 3 1 0 0
$
$

In both command syntaxes, the rotational gap and the number of blocks can be specified.  For RP04 type drives, these numbers should be 7 and 418. 

EXAMPLES

To put a Bell file system on a double density micro floppy with 770 1K blocks of capacity:

bifmkfs /dev/rfd9122.0 770

where /dev/rfd9122.0 is the device special file for the micro floppy. 

SEE ALSO

bif(5). 

BUGS

If a prototype is used, it is not possible to initialize a file with second- or third-level indirects. 

Hewlett-Packard  —  last mod. May 11, 2021