Date: Sun, 18 Jan 2009 21:08:56 +0100 From: Luigi Rizzo <rizzo@iet.unipi.it> To: Andrew Lankford <lankfordandrew@charter.net> Cc: stable@freebsd.org Subject: Re: System borked: loader stack overflow. Message-ID: <20090118200856.GA28366@onelab2.iet.unipi.it> In-Reply-To: <497380BB.1050409@charter.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Setting loader_conf_files="x y z" is basically equivalent to writing "call a; call b; call c;" in a programming language, with the only difference that the action is done at the end of the current file. > Indeed, it would be nice if um someone (anyone, mind you) with commit > priviledges might put some descriptive comments around the > "default-only" settings in /boot/default/loader.conf...:) it is not "default only", either - it is just one of the many files loaded by /boot/loader, you just need to avoid infinite loops. I can write some extra notes in the manpage, and perhaps suggest a rename of the /boot/defaults/ file so one does not end up with two copies by mistake. cheers luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090118200856.GA28366>