From owner-freebsd-hackers Fri Jul 30 13: 6: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BAB4514EDB for ; Fri, 30 Jul 1999 13:05:59 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA08587; Fri, 30 Jul 1999 13:05:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "David E. Cross" Cc: hackers@FreeBSD.ORG Subject: Re: So, back on the topic of enabling bpf in GENERIC... In-reply-to: Your message of "Fri, 30 Jul 1999 16:00:16 EDT." <199907302000.QAA30574@cs.rpi.edu> Date: Fri, 30 Jul 1999 13:05:20 -0700 Message-ID: <8583.933365120@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It will let us use a dhcp client in the install programs, this is of > tremendous use to many people as DHCP starts to become much more > popular. I cannot net install a machine at home since that is on a > DHCP cable modem service. Well, just to clarify this, if you're installing a 4.0 snapshot then you can indeed now do so; it will just be a bit savage in that the installation-time lease will be snapshotted into your /etc/rc.conf in order that the box can reboot for the first time with network connectivity. After that, it's a very good idea to build a new kernel with bpf support enabled and change the ifconfig_foo line in your /etc/rc.conf to say "DHCP" instead of the static lease information it will have in it. Then you're set from then on out. My only desire is that this process be made entirely automatic by enabling you to skip that kernel rebuild part. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message