aoe-mkshelf(8) [debian man page]

aoe-mkshelf(8)						      System Manager's Manual						    aoe-mkshelf(8)

NAME

       aoe-mkshelf - create special device files for one shelf address

SYNOPSIS

       aoe-mkshelf {device-dir} {shelf-address}
       env n_partitions=1 aoe-mkshelf {device-dir} {shelf-address}

DESCRIPTION

       The  aoe-mkshelf  command  is not needed on systems that have udev installed and is incompatible with aoe drivers that have the aoe_dyndevs
       module parameter set to 1.

       Systems lacking udev and having an aoe driver that uses static minor device numbers can use aoe-mkshelf to create the block  special  files
       necessary to access the AoE devices with the given shelf address.

       All  aoe  drivers  prior  to  aoe6-50 use static minor device numbers.  Versions 50 and up use dynamic minor device numbers when the module
       parameter aoe_dyndevs=1 is set.

       If you are using static minor device numbers and your aoe driver supports only one partition per device (whole-disk partitions),  then  the
       device files must match, and you should use the n_partitions environment variable described below.

   Arguments
       device-dir
	      This should be the name of the directory where the block device files will be created.

       shelf-address
	      This  is	the  AoE  major address, or shelf address, for which to create device nodes.  For example, specifying a shelf address of 1
	      means that the e1.* device nodes will be created in device-dir.

ENVIRONMENT VARIABLES

       If the n_partitions variable is set in the environment, it will override the default number of partitions per aoe disk, namely 16.

EXAMPLE

       In this example, the root user on a host named nai creates special files for using the aoe disks in shelf 7.  Then he  remembers  that  the
       driver doesn't have partition support, so the command is called again with n_partitions set to 1.

	      nai:~# aoe-mkshelf /dev/etherd 7
	      nai:~# ls /dev/etherd/e7.* | wc -l
	      160
	      nai:~# rm /dev/etherd/e7.*
	      nai:~# n_partitions=1 aoe-mkshelf /dev/etherd 7
	      nai:~# ls /dev/etherd/e7.* | wc -l
	      10
	      nai:~#

SEE ALSO

       aoe-discover(8), aoe-interfaces(8), aoe-mkdevs(8), aoe-stat(8), aoetools(8), udev(7).

AUTHOR

       Ed L. Cashin (ecashin@coraid.com)

																    aoe-mkshelf(8)

MKNOD(8)						    BSD System Manager's Manual 						  MKNOD(8)

NAME

     mknod -- build special file

SYNOPSIS

     mknod name
     mknod name [b | c] major minor [owner:group]

DESCRIPTION

     The mknod utility is deprecated on modern FreeBSD systems.

     The mknod utility creates device special files.  To make nodes manually, the arguments are:

     name    Device name, for example /dev/da0 for a SCSI disk or /dev/pts/0 for pseudo-terminals.

     b | c   Type of device.  If the device is a block type device such as a tape or disk drive which needs both cooked and raw special files, the
	     type is b.  All other devices are character type devices, such as terminal and pseudo devices, and are type c.

     major   The major device number is an integer number which tells the kernel which device driver entry point to use.

     minor   The minor device number tells the kernel which subunit the node corresponds to on the device; for example, a subunit may be a file
	     system partition or a tty line.

     owner:group
	     The owner group operand pair is optional, however, if one is specified, they both must be specified.  The owner may be either a
	     numeric user ID or a user name.  If a user name is also a numeric user ID, the operand is used as a user name.  The group may be
	     either a numeric group ID or a group name.  Similar to the user name, if a group name is also a numeric group ID, the operand is used
	     as a group name.

     Major and minor device numbers can be given in any format acceptable to strtoul(3), so that a leading '0x' indicates a hexadecimal number,
     and a leading '0' will cause the number to be interpreted as octal.

     The mknod utility can be used to recreate deleted device nodes under a devfs(5) mount point by invoking it with only a filename as an argu-
     ment.  Example:

	   mknod /dev/cd0

     where /dev/cd0 is the name of the deleted device node.

COMPATIBILITY

     The chown(8)-like functionality is specific to FreeBSD.

     As of FreeBSD 4.0, block devices were deprecated in favour of character devices.  As of FreeBSD 5.0, device nodes are managed by the device
     file system devfs(5), making the mknod utility superfluous.  As of FreeBSD 6.0 device nodes may be created in regular file systems but such
     nodes cannot be used to access devices.

SEE ALSO

     mkfifo(1), mknod(2), devfs(5), chown(8)

HISTORY

     A mknod utility appeared in Version 6 AT&T UNIX.

BSD
								 January 31, 2010							       BSD