https://gunkies.org/index.php?action=history&feed=atom&title=32v_1m_mkfs 2026-05-06T02:20:06Z Revision history for this page on the wiki MediaWiki 1.30.1 https://gunkies.org/w/index.php?title=32v_1m_mkfs&diff=6993&oldid=prev 2009-10-26T14:54:54Z

<p>New page: MKFS(1M) UNIX Programmer&#039;s Manual MKFS(1M) == NAME == mkfs - construct a file system == SYNOPSIS == /etc/mkfs special proto == DESCRIPTION == _M_...</p> <p><b>New page</b></p><div>MKFS(1M) UNIX Programmer's Manual MKFS(1M)<br /> <br /> <br /> <br /> == NAME ==<br /> mkfs - construct a file system<br /> <br /> == SYNOPSIS ==<br /> /etc/mkfs special proto<br /> <br /> == DESCRIPTION ==<br /> _M_k_f_s constructs a file system by writing on the special file<br /> _s_p_e_c_i_a_l according to the directions found in the prototype<br /> file _p_r_o_t_o. The prototype file contains tokens separated by<br /> spaces or new lines. The first token is the name of a file<br /> to be copied onto block zero as the bootstrap program, see<br /> _b_p_r_o_c(8). The second token is a number specifying the size<br /> of the created file system. Typically it will be the number<br /> of blocks on the device, perhaps diminished by space for<br /> swapping. The next token is the number of i-nodes in the<br /> i-list. The next set of tokens comprise the specification<br /> for the root file. File specifications consist of tokens<br /> giving the mode, the user-id, the group id, and the initial<br /> contents of the file. The syntax of the contents field<br /> depends on the mode.<br /> <br /> The mode token for a file is a 6 character string. The<br /> first character specifies the type of the file. (The char-<br /> acters -bcd specify regular, block special, character spe-<br /> cial and directory files respectively.) The second character<br /> of the type is either u or - to specify set-user-id mode or<br /> not. The third is g or - for the set-group-id mode. The<br /> rest of the mode is a three digit octal number giving the<br /> owner, group, and other read, write, execute permissions,<br /> see _c_h_m_o_d(1).<br /> <br /> Two decimal number tokens come after the mode; they specify<br /> the user and group ID's of the owner of the file.<br /> <br /> If the file is a regular file, the next token is a pathname<br /> whence the contents and size are copied.<br /> <br /> If the file is a block or character special file, two<br /> decimal number tokens follow which give the major and minor<br /> device numbers.<br /> <br /> If the file is a directory, _m_k_f_s makes the entries . and ..<br /> and then reads a list of names and (recursively) file<br /> specifications for the entries in the directory. The scan<br /> is terminated with the token $.<br /> <br /> If the prototype file cannot be opened and its name consists<br /> of a string of digits, _m_k_f_s builds a file system with a sin-<br /> gle empty directory on it. The size of the file system is<br /> the value of _p_r_o_t_o interpreted as a decimal number. The<br /> number of i-nodes is calculated as a function of the<br /> filsystem size. The boot program is left uninitialized.<br /> <br /> A sample prototype specification follows:<br /> <br /> /usr/mdec/uboot<br /> 4872 55<br /> d--777 3 1<br /> usr d--777 3 1<br /> sh ---755 3 1 /bin/sh<br /> ken d--755 6 1<br /> $<br /> b0 b--644 3 1 0 0<br /> c0 c--644 3 1 0 0<br /> $<br /> $<br /> <br /> == SEE ALSO ==<br /> [[32v 5m filsys|filsys(5)]], [[32v 5m dir|dir(5)]], [[32v 8m bproc|bproc(8)]]<br /> <br /> == BUGS ==<br /> There should be some way to specify links. There should be<br /> some way to specify bad blocks.<br /> <br /> [[Category:32v man section 1]]</div>

Neozeed