From owner-freebsd-current Sun Dec 15 14: 4:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAB0A37B401 for ; Sun, 15 Dec 2002 14:04:20 -0800 (PST) Received: from smtpauth2-ext.prodigy.net (smtpauth2-ext.prodigy.net [207.115.63.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21CA143ED4 for ; Sun, 15 Dec 2002 14:04:20 -0800 (PST) (envelope-from jimit@myrealbox.com) Received: from hawk (crtntx1-ar1-4-60-243-201.crtntx1.dsl-verizon.net [4.60.243.201]) (authenticated) by smtpauth2-ext.prodigy.net (8.11.0/8.11.0) with ESMTP id gBFM43p199972 for ; Sun, 15 Dec 2002 17:04:09 -0500 From: "Jimi Thompson" To: Subject: RE: FBSD 5.0RC1 install oddity Date: Sun, 15 Dec 2002 16:04:42 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 9:23 PM +0100 2002/12/15, Claudio Nieder wrote: > Problem: After that question the install programm immediatly tries to > contact the DHCP server, which cannot work, as informations like the WEP > key to use etc. were asked for/supplied so that the wireless card could > be properly set up to communicate. I ran into this same problem when I was trying to install FreeBSD-4.6.2-RELEASE. I think that the solution is actually to flip to a different page in the sysinstall program and provide the additional options that you need. Unfortunately, although I think I stumbled into this solution, I couldn't tell you how to replicate it. -- Brad Knowles, I have noticed several oddities surrounding the dhclient, as well. It seems that my network card is not initalizing early enough in the boot process for me to acquire a dhcp lease. Since I'm not getting a lease this was causing cascade problems with Apache, SSH, etc. However, I have found that setting the crontab to run @reboot and fire off dhclient seems to work for at least acquiring the IP address. This has the effect of firing off dhclient much later on in the boot process (after cron loads). Perhaps this will help you as well. I add as a note that this does not appear to be a complete solution since I am still fighting the cascade issues, most notably with SSH. Thanks, Ms. Jimi Thompson Those who are too smart to engage in politics are punished by being governed by those who are dumber. - Plato To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message