From owner-freebsd-questions@FreeBSD.ORG Thu Jun 30 05:14:16 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 B477C106566C; Thu, 30 Jun 2011 05:14:16 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 9249D8FC12; Thu, 30 Jun 2011 05:14:16 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p5U5ECpV076173 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 Jun 2011 22:14:12 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p5U5ECYw076172; Wed, 29 Jun 2011 22:14:12 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA25339; Wed, 29 Jun 11 22:10:30 PDT Date: Wed, 29 Jun 2011 22:10:32 -0700 From: perryh@pluto.rain.com To: korvus@comcast.net Message-Id: <4e0c0548.eW27hshSLoLhhTu1%perryh@pluto.rain.com> References: <4E0B540B.3090400@comcast.net> In-Reply-To: <4E0B540B.3090400@comcast.net> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 05:14:16 -0000 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.