Date: Sun, 18 Jan 2009 17:51:34 +0100 From: Luigi Rizzo <rizzo@iet.unipi.it> To: Andrew Lankford <lankfordandrew@charter.net> Cc: peterjeremy@optushome.com.au, stable@freebsd.org, xxjack12xx@gmail.com Subject: Re: System borked: loader stack overflow. Message-ID: <20090118165134.GB21705@onelab2.iet.unipi.it> In-Reply-To: <20090118164724.GA21705@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 18, 2009 at 05:47:24PM +0100, Luigi Rizzo wrote: > On Sun, Jan 18, 2009 at 10:38:51AM -0500, Andrew Lankford wrote: > > > > I can't say what version of the loader it is that I'm using, but > > (following Peter's advice, thanks), I've tried loader.old (about a week > > old) and the latest loader (built yesterday), and both start. Where > > each loader has a problem appears to be reading (include-ing?) > > /boot/default/loader.conf . The spinner spins for a longer time than > > ok so the problem could be is a recursive assignment of loader_conf_files > in your previous installation (either as a result of the default > installation, or because of manual modifications). > Could you please send me a copy of your /boot/loader.conf and > /boot/defaults/loader.conf so i can check ? also /boot/loader.conf.local please... thanks luigi > A recent commit fixed the handling of loader_conf_files, > which previously was broken (in some cases assignments were ignored). > A side effect of the fix is that now certain errors in the config > files are now detected as such. > > cheers > luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090118165134.GB21705>