p The options are as follows: l -tag -width flag t Fl n Do not actually write anything on the disk. t Fl v Be verbose, printing out the block numbers that .Ar bootxx will use to load .Ar ufsboot . .El
p The arguments are: l -tag -width ufsboot t Ar ufsboot the name of the second-stage boot program in the file system where the first-stage boot program is to be installed. t Ar bootxx the name of the prototype file for the first stage boot program. t Ar rawdev the name of the raw device in which the first-stage boot program is to be installed. This should correspond to the block device on which the file system containing .Ar ufsboot is mounted. .El .Sh SEE ALSO .Xr disklabel 8 , .Xr init 8 .Sh BUGS .Nm requires simultaneous access to the mounted file system and the raw device, but that is not allowed with the kernel .Dv securelevel variable set to a value greater than zero (the default), so .Nm only works in single-user mode (or insecure mode - see .Xr init 8 ) .