Subject: install/9656: sysinst should support dhcp
To: None <gnats-bugs@gnats.netbsd.org>
From: John Hawkinson <jhawk@mit.edu>
List: netbsd-bugs
Date: 03/21/2000 18:27:04
>Number:         9656
>Category:       install
>Synopsis:       sysinst should support dhcp
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    install-manager (NetBSD system installation bug manager)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 21 18:27:00 2000
>Last-Modified:
>Originator:     John Hawkinson
>Organization:
	MIT
>Release:        NetBSD 1.4.2
>Environment:
	
System: NetBSD zorkmid.mit.edu 1.4.2 NetBSD 1.4.2 (GENERIC) #3: Wed Mar 15 23:41:54 PST 2000 toddpw@vader.toddpw.net:/usr/src/sys/arch/i386/compile/GENERIC i386


>Description:
	Having euphorically learned of the release of NetBSD 1.4.2
and therefore a chance to test out the upgrade process on my laptop,
I decided to try upgrading NetBSD from work. It so happened that said
laptop was plugged in on a DHCP-only network, with no static IP address.

	If DHCP really is the wave of the future and the best thing
since sliced bread and the way that people are expected to get their
IP addresses in the stateless autoconfiguring universe, then the
install utility had better support it.

	sysinst should allow you to get your network address (and other
ancillary info: mask, nameservers, etc.) via dhcp.

	I understand that space in the boot image is tight. I don't
know what to say. For upgrades, you could piggyback off the old
os's dhcp implementation, but I'm sure that is way too unclean and
disgusting.
>How-To-Repeat:
	
>Fix:
	
>Audit-Trail:
>Unformatted: