From owner-freebsd-hackers Mon Jul 31 12:56:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.dynamine.net (phoenix.dynamine.net [64.14.25.210]) by hub.freebsd.org (Postfix) with ESMTP id 1920537BBFB for ; Mon, 31 Jul 2000 12:56:43 -0700 (PDT) (envelope-from michael@dynamine.net) Received: from lucretia (host1.auctionwatch.com [64.14.25.32]) by phoenix.dynamine.net (Postfix) with SMTP id 1A7CC183939 for ; Mon, 31 Jul 2000 12:56:39 -0700 (PDT) Message-ID: <003101bffb29$480b6340$1500800a@corp.auctionwatch.com> From: "Michael S. Fischer" To: Subject: DHCP in scripted sysinstall? Date: Mon, 31 Jul 2000 12:55:30 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know that currently one can request a DHCP lease when configuring the network interfaces in sysinstall, but that functionality does not seem to exist during a scripted install. Reading sysinstall.8 (which, incidentally, does not appear to be installed in the correct place during a make world), it appears that the installation target's hostname, IP address and other networking information must be manually supplied by the installation script before making a mediaSetFTP or mediaSetNFS call. Is it possible we'll see a future version of sysinstall any time soon that will allow scripted installation targets to get their network profile from DHCP? I'm running 4.x-STABLE. Thanks for your help, -- Michael S. Fischer AKA Otterley _O_ Lead Hacketeer, Dynamine Consulting, Silicon Valley, CA | Phone: +1 650 533 4684 | AIM: IsThisOtterley | ICQ: 4218323 | "From the bricks of shame is built the hope"--Alan Wilder net.goth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message