--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 08, 2004 at 12:31:03AM +0200, Emmanuel Dreyfus wrote:
> Ted Lemon <mellon@fugue.com> wrote:
>=20
> > There's actually no need to patch the server like that.   You can just
> > define those options in the dhcpd.conf file.   Since the options are in
> > violation of the DHCP standard, it would actually be inappropriate to
> > patch the server like that.   But it's easy to make it work in the=20
> > config file:
> >=20
> > option mac-nc-client-unknown code 220 =3D string;
> > option mac-nc-client-id code 221 =3D string;
> > option mac-version code 230 =3D string;
> > option mac-user-name code 232 =3D string;
> > option mac-password code 233 =3D string;
> > option mac-nb-image code 234 =3D string;
> > option mac-apps-image code 235 =3D string;
> > option mac-machine-name code 237 =3D string;
> > option mac-client-nb-image code 238 =3D string;
>=20
> But all of that is used to netboot MacOS X, right? Why would I need that
> for NetBSD?

Sorry for the delay. Because the firmware uses it to load the OS,=20
regardless of it being MacOS X or NetBSD.

Take care,

Bill

--pWyiEgJYm5f9v55/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAz8IGWz+3JHUci9cRAjEhAJwPtI4u2F9wl6TBo+jovdIOdhF05ACfdw13
AJOAcf4d0UOrlXnLq8XpapE=
=6QuI
-----END PGP SIGNATURE-----

--pWyiEgJYm5f9v55/--