From owner-freebsd-questions@FreeBSD.ORG Thu Jun 30 13:02:33 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 134ED106564A for ; Thu, 30 Jun 2011 13:02:33 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [76.96.59.228]) by mx1.freebsd.org (Postfix) with ESMTP id C99678FC0A for ; Thu, 30 Jun 2011 13:02:32 +0000 (UTC) Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta15.westchester.pa.mail.comcast.net with comcast id 2CfP1h0080vyq2s5FCpHdp; Thu, 30 Jun 2011 12:49:17 +0000 Received: from [10.0.0.79] ([71.199.122.142]) by omta05.westchester.pa.mail.comcast.net with comcast id 2Cp61h01j34Sj4f3RCpDlX; Thu, 30 Jun 2011 12:49:14 +0000 Message-ID: <4E0C70C7.2000102@comcast.net> Date: Thu, 30 Jun 2011 08:49:11 -0400 From: Steve Polyack User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: perryh@pluto.rain.com References: <4E0B540B.3090400@comcast.net> <4e0c0548.eW27hshSLoLhhTu1%perryh@pluto.rain.com> In-Reply-To: <4e0c0548.eW27hshSLoLhhTu1%perryh@pluto.rain.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Question about NIC link state initialization X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 13:02:33 -0000 On 6/30/2011 1:10 AM, perryh@pluto.rain.com wrote: > Steve Polyack wrote: > >> ... An occaisional fat-finger in /etc/fstab may cause one to >> end up in single-user mode ... some of these systems have a LOM >> (lights-out management) controller which shares the system's >> on-board NICs ... when the system drops out of init(8) and into >> single-user mode, the links on the interfaces never come up, >> and therefore the LOM becomes inaccessible. >> >> ... all one has to do is run ifconfig to cause the NIC's links to >> come up ... why do we have to run ifconfig(8) to bring the links >> up on the attached interfaces? > When trying to troubleshoot a problem that was known or suspected to > involve the network or its hardware, one might not _want_ the NICs > alive. > >> Short of patching init(8) (or perhaps the NIC drivers?), I don't >> see another way for me to ensure the links come up even when the >> system drops into single-user mode on boot. > Something in /root/.profile, perhaps? That should get run when the > single-user shell starts up, if it's started as a "login" shell. > This won't work. When the system kicks you into single-user mode, you are prompted to enter the name of a shell or press enter for /bin/sh. If no one is there to press enter, or enter the path to an alternate shell, then a shell never starts.