From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 21:14:12 2009 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22624106566B; Sun, 18 Jan 2009 21:14:12 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id D5AC08FC16; Sun, 18 Jan 2009 21:14:11 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 15B4273098; Sun, 18 Jan 2009 22:19:29 +0100 (CET) Date: Sun, 18 Jan 2009 22:19:29 +0100 From: Luigi Rizzo To: Andrew Thompson Message-ID: <20090118211929.GA29063@onelab2.iet.unipi.it> References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> <20090118164724.GA21705@onelab2.iet.unipi.it> <20090118185605.GA28874@citylink.fud.org.nz> <497380BB.1050409@charter.net> <20090118200856.GA28366@onelab2.iet.unipi.it> <20090118201809.GA44812@citylink.fud.org.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090118201809.GA44812@citylink.fud.org.nz> User-Agent: Mutt/1.4.2.3i Cc: Andrew Lankford , stable@freebsd.org Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2009 21:14:12 -0000 On Sun, Jan 18, 2009 at 12:18:09PM -0800, Andrew Thompson wrote: > On Sun, Jan 18, 2009 at 09:08:56PM +0100, Luigi Rizzo wrote: > > On Sun, Jan 18, 2009 at 02:19:23PM -0500, Andrew Lankford wrote: > > > Andrew Thompson wrote: > > ... > > > >Having the following in /boot/loader.conf triggers it for me, > > > > > > > > loader_conf_files="/boot/device.hints /boot/loader.conf" > > > > > > > >You may say thats its an invalid config line but the loader shouldnt > > > >blow up from it. Can this be fixed up somehow? > > > > no, this cannot be "fixed" because it is the user misprogramming > > the system, such as providing the wrong path to the kernel > > or writing a loop in /etc/rc.conf or a billion other ways. > > Yes, but you can copy /etc/defaults/rc.conf to /etc/rc.conf and things > still work. just because it contains only variable assignments, whereas the "assignments" in loader.conf have other side effects. However, I agree that a split of the content of loader.conf might make reduce the chance of mistakes. I'll look into this. > Ok, then loader_conf_files needs to be marked as special and not to be > overridden from /boot/defaults/loader.conf like all the other options. Unless i misunderstand what you say, this is already documented in loader.conf(5) cheers luigi