xref: /netbsd-src/usr.sbin/rpc.bootparamd/rpc.bootparamd.8 (revision ce0bb6e8d2e560ecacbe865a848624f94498063b)
1.\" $Id: rpc.bootparamd.8,v 1.5 1995/04/12 00:53:13 jtc Exp $
2.\" @(#)bootparamd.8
3.Dd Jan 8, 1994
4.Dt BOOTPARAMD 8
5.Os NetBSD
6.Sh NAME
7.Nm bootparamd ,
8.Nm rpc.bootparamd
9.Nd boot parameter server
10.Sh SYNOPSIS
11.Nm /usr/sbin/rpc.bootparamd
12.Op Fl d
13.Op Fl s
14.Op Fl r router
15.Op Fl f file
16.Sh DESCRIPTION
17.Nm \&Bootparamd
18is a server process that provides information to diskless clients
19necessary for booting. It consults the file
20.Dq Pa /etc/bootparams .
21It should normally be started from
22.Dq Pa /etc/rc .
23.Pp
24This version will allow the use of aliases on the hostname in the
25.Dq Pa /etc/bootparams
26file. The hostname returned in response to the booting client's whoami request
27will be the name that appears in the config file, not the canonical name.
28In this way you can keep the answer short enough
29so that machines that cannot handle long hostnames won't fail during boot.
30.Pp
31While parsing, if a line containing just ``+'' is found, and
32the YP subsystem is active, the YP map
33.Pa bootparams
34will be searched immediately.
35.Sh OPTIONS
36.Bl -tag -width indent
37.It Fl d
38Display the debugging information. The daemon does not fork in this
39case.
40.It Fl s
41Log the debugging information with syslog.
42.It Fl r
43Set the default router (a hostname or IP-address).
44This defaults to the machine running the server.
45.It Fl f
46Specify the file to use as boot parameter file instead of
47.Dq Pa /etc/bootparams .
48.El
49.Pp
50.Sh FILES
51.Bl -tag -width /etc/bootparams -compact
52.It Pa /etc/bootparams
53default configuration file
54.El
55.Sh "SEE ALSO"
56.Xr bootparams 5
57.Sh BUGS
58You may find the syslog loggings too verbose.
59.Pp
60It's not clear if the non-cannonical hack mentioned above is a good idea.
61.Sh AUTHOR
62Originally written by Klas Heggemann <klas@nada.kth.se>
63