Lines Matching full:be
13 .\" may be used to endorse or promote products derived from this software
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
35 can be found in Appendix A and may be of use if you should have
44 system image to be generated, and
81 An option may be given a value by following its name with ``\fB=\fP'',
104 The values must be enclosed in double quotes if they include numerals
113 An optional integer or floating point number may be included
121 This system is to be known as
136 Multiple bootable images may be specified in a single configuration
139 system specific devices may be different. A system image is specified
152 calls may also be specified, though in practice this is almost
169 allows specifications to be continued across multiple lines
173 area(s), the ``dumps'' clause can be used to force system dumps
174 to be taken on a particular device, and the ``args'' clause
175 can be used to specify that argument list processing for
177 should be done on a particular device.
179 The device names supplied in the clauses may be fully specified
186 For example, the swap area need not be specified at all if
206 number is incorrect for your configuration, it can be replaced
212 where the device name would normally be found. For example,
219 at boot time. If a non-standard size is to be used for one
221 this can also be specified. To do this, the
229 would force swapping to be done in partition ``b'' of ``hp0'' and
230 the swap partition size would be set to 1200 sectors. A swap area
235 should be specified; any extra clauses will cause an error.
239 Each device attached to a machine must be specified
244 specified in the configuration need not actually be present on
245 the machine where the generated system is to be run. Only the
246 hardware actually found at boot time will be used by the system.
249 parallels the interconnection hierarchy of the machine to be
252 which \fInexi\fP they might be connected.*
260 and controllers must be indicated as possibly being connected
266 configurations. For example, a disk may be indicated as present
271 if a disk must be moved around for some reason, the system will
298 unit number to be assigned the device (the
300 unit number may be different than the
318 specifications would be used:
326 To tie a controller to a specific nexus, ``x'' would be supplied
327 as the number of that nexus; otherwise ``x'' may be specified as
335 may be connected to another controller (e.g. a disk controller attached
361 Any piece of hardware which may be connected to a specific
362 controller may also be wildcarded across multiple controllers.
369 \fIDrive\fP numbers may be wildcarded
371 For controllers, the control status register must be
373 the names of the routines to which they should be bound.
374 Thus the example lines given above might be completed as:
393 one last parameter may be specified to a
406 in section 4 should be consulted to determine how each driver
419 must be used. A specification for a pseudo device takes the form
435 More information on configuring each of these can also be found