src/sys/boot/common/dev_net.c, branch release/6.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2005-11-03T00:35:26+00:00

'RELENG_6_0_0_RELEASE'.

This commit was manufactured to restore the state of the 6.0-RELEASE image.

Change the following environment variables to kernel options:

2004-07-08T22:35:36+00:00

    bootp -> BOOTP
    bootp.nfsroot -> BOOTP_NFSROOT
    bootp.nfsv3 -> BOOTP_NFSV3
    bootp.compat -> BOOTP_COMPAT
    bootp.wired_to -> BOOTP_WIRED_TO

- i.e. back out the previous commit.  It's already possible to
pxeboot(8) with a GENERIC kernel.

Pointed out by: dwmalone

Change the following kernel options to environment variables:

2004-07-08T13:40:33+00:00

    BOOTP -> bootp
    BOOTP_NFSROOT -> bootp.nfsroot
    BOOTP_NFSV3 -> bootp.nfsv3
    BOOTP_COMPAT -> bootp.compat
    BOOTP_WIRED_TO -> bootp.wired_to

This lets you PXE boot with a GENERIC kernel by putting this sort of thing
in loader.conf:

    bootp="YES"
    bootp.nfsroot="YES"
    bootp.nfsv3="YES"
    bootp.wired_to="bge1"

or even setting the variables manually from the OK prompt.

Override the root server address if an IP address is specified in

2003-11-03T19:45:05+00:00

the root path. This is reported to make non-PXE netbooting, such as
is used on sparc64 systems, work correctly when the TFTP server is
not the same as the root server.

PR:		kern/57328
Submitted by:	Per Kristian Hove

Use __FBSDID().

2003-08-25T23:30:41+00:00

Also some minor style cleanups.

Stash various networking paramters in the environment for the kernel

2002-07-31T20:17:06+00:00

to pick up, ala pxe.

Give the network device a print method.

2000-11-10T06:37:43+00:00

Reviewed by:	obrien

Add support to send the string 'PXEClient' as the Vendor class

2000-08-11T08:36:17+00:00

identifier to the DHCP server.  Now you can check for this string
in your dhcp configuration to decide whether you will hand out a
lease to the client or not.

Fix the more obvious warnings to deal with my earlier warning cleanups.

2000-08-03T09:49:44+00:00

Only probe network settings on the first open of the network device.

2000-05-13T15:40:46+00:00

The alpha firmware takes a seriously long time to open the network device
the first time.