Date: Thu, 30 Jun 2011 08:49:11 -0400 From: Steve Polyack <korvus@comcast.net> To: perryh@pluto.rain.com Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Question about NIC link state initialization Message-ID: <4E0C70C7.2000102@comcast.net> In-Reply-To: <4e0c0548.eW27hshSLoLhhTu1%perryh@pluto.rain.com> References: <4E0B540B.3090400@comcast.net> <4e0c0548.eW27hshSLoLhhTu1%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/30/2011 1:10 AM, perryh@pluto.rain.com wrote: > Steve Polyack<korvus@comcast.net> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E0C70C7.2000102>