dp(1M) dp(1M)NAME dp - perform disk partitioning SYNOPSIS dp [-q] [-u] file DESCRIPTION dp is used to perform disk partitioning and ``Block Zero Block'' manipulation on file. In most cases, though not re- quired, file is a special file. dp accepts commands from standard input and performs the specified operations. dp could be considered a special purpose editor. All input between the character # and a newline (inclusive), defines a comment and is ignored. This allows for commands to be easily kept in a disk file and piped to dp whenever a disk needs to be reinitialized. Commands do not have to be separated by newlines (that is, more than one command can be entered at an input prompt). White space is normally stripped, but may be escaped by a backslash (\). This is useful when including white space in string input. A lead- ing zero (0) in numeric input indicates octal conversion and a leading 0x or 0X indicates hexadecimal conversion; other- wise, decimal conversion is used. dp has some safeguards built in to help avoid destruction or deletion of data. On occasions when dp detects such a re- quest, it will prompt you for confirmation before the action is performed. By specifying some commands in uppercase, the safeguards can be circumvented. Commands that fall into this category are so noted by the word (force) in their description. dp has the following operation ``modes.'' command DPME-field BZB-field timestamp-field ABM-field A field mode is entered when a request is made to add or modify one of the fields. Each field mode accepts its own commands. A menu containing the list of commands valid for the current mode can be printed using the ? command. A mode is exited using the q command. dp will accept commands to manipulate and change partitions, to display and save changes, to manipulate the fields of a DPME (Disk Partition Map Entry) structure, to manipulate the fields of a BZB (Block Zero Block) structure, to manipulate the timestamp fields of a BZB structure, and to manipulate April, 1990 1
dp(1M) dp(1M)the fields of an ABM (Alternate Block Map) structure. For more information about these structures see altblk(4), bzb(4), and dpme(4). In command mode, dp accepts the following commands. a add partition A add partition (force) c change partition d delete partition f change name of output file i initialize disk I initialize disk (force) p print a partition P print allocated partitions q quit dp Q quit dp (force) s print partition map status U uninitialize the map v print dp version information w write changes ? print current menu # start of comment In DPME-field mode, dp accepts the following commands. a change ABM (bzb_abm) b change/initialize BZB n name (dpme_dpident.dpiname) t type (dpme_dpident.dpitype) [ physical start (dpme_pblock_start) ] physical length (dpme_pblocks) ( logical start (dpme_lblock_start) ) logical length (dpme_lblocks) > writable (dpme_writable) < readable (dpme_readable) p print current DPME q quit DPME changes ? print current menu # start of comment In BZB-field mode, dp accepts the following commands. c no inode level badblk handling (bzb_crit) i bad block inode number (bzb_inode) m timestamps (bzb_tmade, bzb_tmount, bzb_tumount) n cluster number (bzb_cluster) p print current bzb q quit bzb changes r root FS (bzb_root) t FS type (bzb_type) T FS type (force) (bzb_type) 2 April, 1990
dp(1M) dp(1M)u usr FS (bzb_usr) U uninitialize bzb ? print current menu # start of comment In timestamp-field mode, dp accepts the following commands. p print timestamps c change creation time (bzb_tmade) m change mount time (bzb_tmount) u change umount time (bzb_tumount) q quit timestamp changes ? print current menu # start of comment In ABM-field mode, dp accepts the following commands. b size of map in blocks (abm_size) c consistency check e number of used entries (discouraged) (abm_ents) I initialize altblk map per abm contents i default initialization of abm/altblk map o physical block of start of altblk map (abm_start) p print current abm q quit abm changes s size of map in bytes (discouraged) (abm_size) ? print current menu # start of comment Similar to most ordinary editors, dp will encourage you to save any changes that might have been made before quitting. LIMITS dp will not allow the creation of a disk partition map con- taining more than 1024 entries. FLAG OPTIONS The following flag options are interpreted by dp: -q When this option is specified, dp will not prompt for input. -u This option will cause output to be unbuffered. EXAMPLES The following is an example of running dp noninteractively. It should be noted that if one was doing disk partitioning on many disks, it might prove useful to have a dpscript. cat << EOF | dp -q /dev/rdsk/c0d0s31 #!dp # @(#)dpscript 2.1 April, 1990 3
dp(1M) dp(1M)# I64 # Initialize the map with 64 entries # add some partitions # # FS type key: 1=UNIX 2=Autorec. 3=Swap # [ ] Name Type ( ) EC FS RFS UFS a1 128 4096 Autorecovery\ 1 y 0 4096 0 2 a2 4224 111184 A/UX\ Root y 0 111184 0 1 y y a3 115408 32768 Swap y 0 32768 0 3 a4 152272 4096 Autorecovery\ 2 y 0 4096 0 2 wq # Write changes and quit EOF To print a description of the currently defined partitions, do the following. echo P | dp -q /dev/rdsk/c0d0s31 FILES /bin/dp SEE ALSO pname(1M), altblk(4), bzb(4), dpme(4), ptab(4), au- torecovery(8). DIAGNOSTICS dp produces various messages if the specified file does not exist. WARNINGS At various times while fields are being modified, dp may produce warning messages if it is determined that the modif- ication made is of a questionable nature. Even though dp doesn't produce a warning, never assume that a modification of questionable nature hasn't been made. In the event that a modification of questionable nature is made while running as noninteractive (for example, redirecting standard input from a disk file), dp exits. 4 April, 1990