| 4.t (1856) | 4.t (215334) |
|---|---|
| 1.\" Copyright (c) 1980, 1986, 1988 The Regents of the University of California. 2.\" All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)4.t 8.1 (Berkeley) 7/29/93 | 1.\" Copyright (c) 1980, 1986, 1988 The Regents of the University of California. 2.\" All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)4.t 8.1 (Berkeley) 7/29/93 |
| 33.\" $FreeBSD: head/share/doc/smm/01.setup/4.t 215334 2010-11-15 05:25:51Z dougb $ |
|
| 33.\" 34.ds LH "Installing/Operating \*(4B 35.ds CF \*(Dy 36.ds RH "System setup 37.Sh 1 "System setup" 38.PP 39This section describes procedures used to set up a \*(4B UNIX system. 40These procedures are used when a system is first installed --- 106 unchanged lines hidden (view full) --- 147files in the filesystem, made by the 148.Xr mknod (8) 149program and normally kept in the 150.Pn /dev 151directory. 152For all the devices supported by the distribution system, the 153files in 154.Pn /dev | 34.\" 35.ds LH "Installing/Operating \*(4B 36.ds CF \*(Dy 37.ds RH "System setup 38.Sh 1 "System setup" 39.PP 40This section describes procedures used to set up a \*(4B UNIX system. 41These procedures are used when a system is first installed --- 106 unchanged lines hidden (view full) --- 148files in the filesystem, made by the 149.Xr mknod (8) 150program and normally kept in the 151.Pn /dev 152directory. 153For all the devices supported by the distribution system, the 154files in 155.Pn /dev |
| 155are created by the 156.Pn /dev/MAKEDEV 157shell script. | 156are created by devfs. |
| 158.PP 159Determine the set of devices that you have and create a new 160.Pn /dev | 157.PP 158Determine the set of devices that you have and create a new 159.Pn /dev |
| 161directory by running the MAKEDEV script. 162First create a new directory 163.Pn /newdev , 164copy MAKEDEV into it, edit the file MAKEDEV.local 165to provide an entry for local needs, 166and run it to generate a 167.Pn /newdev directory. 168For instance, 169.DS 170\fB#\fP \fIcd /\fP 171\fB#\fP \fImkdir newdev\fP 172\fB#\fP \fIcp dev/MAKEDEV newdev/MAKEDEV\fP 173\fB#\fP \fIcd newdev\fP 174\fB#\fP \fIMAKEDEV \*(Dk0 pt0 std LOCAL\fP 175.DE 176Note the ``std'' argument causes standard devices such as 177.Pn /dev/console , 178the machine console, to be created. 179.PP 180You can then do 181.DS 182\fB#\fP \fIcd /\fP 183\fB#\fP \fImv dev olddev ; mv newdev dev\fP 184\fB#\fP \fIsync\fP 185.DE 186to install the new device directory. | 160directory by mounting devfs. |
| 187.Sh 3 "Building new system images" 188.PP 189The kernel configuration of each UNIX system is described by 190a single configuration file, stored in the 191.Pn /sys/<architecture>/conf 192directory. 193To learn about the format of this file and the procedure used 194to build system images, --- 32 unchanged lines hidden (view full) --- 227access from directly-connected terminals other than the console, 228the file 229.Pn /etc/ttys 230(see 231.Xr ttys (5)) 232must be edited. 233.PP 234To add a new terminal device, be sure the device is configured into the system | 161.Sh 3 "Building new system images" 162.PP 163The kernel configuration of each UNIX system is described by 164a single configuration file, stored in the 165.Pn /sys/<architecture>/conf 166directory. 167To learn about the format of this file and the procedure used 168to build system images, --- 32 unchanged lines hidden (view full) --- 201access from directly-connected terminals other than the console, 202the file 203.Pn /etc/ttys 204(see 205.Xr ttys (5)) 206must be edited. 207.PP 208To add a new terminal device, be sure the device is configured into the system |
| 235and that the special files for the device have been made by 236.Pn /dev/MAKEDEV . | 209and that the special files for the device exist in 210.Pn /dev . |
| 237Then, enable the appropriate lines of 238.Pn /etc/ttys 239by setting the ``status'' 240field to \fBon\fP (or add new lines). 241Note that lines in 242.Pn /etc/ttys 243are one-for-one with entries in the file of current users 244(see --- 85 unchanged lines hidden (view full) --- 330printed on the console, though other actions may occur depending 331on the configuration information found in 332.Pn /etc/syslog.conf . 333.PP 334Finally note that you should change the names of any dialup 335terminals to ttyd? 336where ? is in [0-9a-zA-Z], as some programs use this property of the 337names to determine if a terminal is a dialup. | 211Then, enable the appropriate lines of 212.Pn /etc/ttys 213by setting the ``status'' 214field to \fBon\fP (or add new lines). 215Note that lines in 216.Pn /etc/ttys 217are one-for-one with entries in the file of current users 218(see --- 85 unchanged lines hidden (view full) --- 304printed on the console, though other actions may occur depending 305on the configuration information found in 306.Pn /etc/syslog.conf . 307.PP 308Finally note that you should change the names of any dialup 309terminals to ttyd? 310where ? is in [0-9a-zA-Z], as some programs use this property of the 311names to determine if a terminal is a dialup. |
| 338Shell commands to do this should be put in the 339.Pn /dev/MAKEDEV.local 340script. | |
| 341.PP 342While it is possible to use truly arbitrary strings for terminal names, 343the accounting and noticeably the 344.Xr ps (1) 345command make good use of the convention that tty names 346(by default, and also after dialups are named as suggested above) 347are distinct in the last 2 characters. 348Change this and you may be sorry later, as the heuristic --- 365 unchanged lines hidden --- | 312.PP 313While it is possible to use truly arbitrary strings for terminal names, 314the accounting and noticeably the 315.Xr ps (1) 316command make good use of the convention that tty names 317(by default, and also after dialups are named as suggested above) 318are distinct in the last 2 characters. 319Change this and you may be sorry later, as the heuristic --- 365 unchanged lines hidden --- |