MAKEDEV.LOCAL(8) | System Manager's Manual | MAKEDEV.LOCAL(8)

# NAME

`MAKEDEV.local` —
create site-specific device special files

# SYNOPSIS

`MAKEDEV.local` | [`-fMsu`] [`-m` mknod] [`-p` pax] [`-t` mtree] {all | site-specific-argument} [...]

# DESCRIPTION

`MAKEDEV.local` is used to create site-specific device special files. Each argument may be the word all or a site-specific argument. By default, there are no valid site-specific arguments, and the all argument has no effect; This may be changed by editing the script.

The script is in /dev/MAKEDEV.local. Devices are created in the current working directory; in normal use, `MAKEDEV.local` should be invoked with /dev as the current working directory.

Supported options for `MAKEDEV.local` are the same as for MAKEDEV(8).

# FILES

/dev
  special device files directory
/dev/MAKEDEV
  script that invokes `MAKEDEV.local` with the all argument.
/dev/MAKEDEV.local
  script described in this man page

# SEE ALSO

config(1), intro(4), MAKEDEV(8), mknod(8)

# HISTORY

The `MAKEDEV.local` command appeared in 4.2BSD. Handling of the same command line options as MAKEDEV(8), and the use of MAKEDEV(8) as a function library, was added in NetBSD 5.0.

# NOTES

The relationship between `MAKEDEV.local` and MAKEDEV(8) is complex:

- If MAKEDEV(8) is invoked with the all or local argument, then it will invoke `MAKEDEV.local` as a child process, with options similar to those that were originally passed to MAKEDEV(8), and with the all argument.
- `MAKEDEV.local` uses shell functions defined in MAKEDEV(8). This is done by loading MAKEDEV(8) using the shell “.” command, with the `MAKEDEV_AS_LIBRARY` variable set (to inform MAKEDEV(8) that it should behave as a function library, not as an independent program).

August 6, 2011 | NetBSD 9.2