From owner-freebsd-sysinstall@FreeBSD.ORG Tue May 25 17:14:39 2010 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB8851065670 for ; Tue, 25 May 2010 17:14:39 +0000 (UTC) (envelope-from dteske@vicor.com) Received: from postoffice.vicor.com (postoffice.vicor.com [69.26.56.53]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF988FC14 for ; Tue, 25 May 2010 17:14:39 +0000 (UTC) Received: from [192.82.228.151] (port=47597 helo=windhcp51.vicor.com) by postoffice.vicor.com with esmtpsa (SSLv3:RC4-MD5:128) (Exim 4.71) (envelope-from ) id 1OGxhz-0005i7-Jg; Tue, 25 May 2010 10:14:29 -0700 From: Devin Teske To: freebsd-sysinstall@freebsd.org Content-Type: text/plain Organization: Vicor, Inc Date: Tue, 25 May 2010 10:14:27 -0700 Message-Id: <1274807667.6175.101.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-41.el4) Content-Transfer-Encoding: 7bit X-Scan-Signature: ac92434a94776a934d5a961bb6a95535 X-Scan-Host: postoffice.vicor.com X-Mailman-Approved-At: Tue, 25 May 2010 17:49:38 +0000 Cc: Subject: NIC Selection Menu X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2010 17:14:39 -0000 I just got a call from the field which inspired me with an enhancement idea for sysinstall... Problem: Currently as-it-stands, when performing a network-based install with sysinstall, sysinstall gives you no indication as to which network interface is "active" (versus "no carrier" for 'status')... often leading to the scenario where the field engineer has to try one, and then the other. Solution: Sysinstall could "bold" the NIC entry in the selection menu if (and only-if) [a] it is able to properly probe the status of said NIC and [b] said status indicates that a cable is plugged into the interface. The particular problem that this poor field engineer ran into was that he tried to configure one interface, surreptitiously failed, then tried to configure the next (without reboot) and then dead-locked himself because the system was ultimately confused with both NICs using the same IP address (diagnosed by walking said field engineer through a series of commands on the emergency Holo shell -- over on Alt+F4). Currently, I am instructing our field engineers to -- when presented with the NIC selection menu -- do the following (because our install disc supports this, as it has been highly customized): 1. Press Alt+F4 2. Type "rescue" and hit enter NOTE: A special feature of our install disc... the mfsroot has a shell script named /stand/rescue which bootstraps (using ldconfig, et. al.) a fully-functional bash shell with 217 ancillary binaries, such as ifconfig, awk, grep, ls, and many MANY more 3. Type "ifconfig" and hit enter 4. Find which adapter has "status: active" opposed to "status: no carrier" 5. Press Alt+F1 to go back to the install menu which is prompting for NIC selection 6. Select the proper NIC to use 7. Continue with the rest of the setup instructions Now... if the NIC selection menu simply showed the status (if/when available), then the above would be null-and-void... the field engineer would know immediately which NIC to select from the menu. ASIDE: Maybe making-bold is not the best solution. Perhaps -- if room can be made -- we should simply add a "status" column. Or... perhaps we do both (make bold the active interfaces AND add a column with the status). I like the latter, as it means I should theoretically get less calls from L-Users (I kid). ^_^ -- Cheers, Devin Teske -> CONTACT INFORMATION <- Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.teske@fisglobal.com -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> END TRANSMISSION <-