Date: Thu, 26 Jan 2006 06:49:08 -0500 From: Tom Rhodes <trhodes@FreeBSD.org> To: Ceri Davies <ceri@submonkey.net> Cc: murray@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org, doc-committers@FreeBSD.org Subject: Re: cvs commit: www/en/releases/6.1R todo.sgml Message-ID: <20060126064908.4bc6215d.trhodes@FreeBSD.org> In-Reply-To: <20060126101706.GJ36965@submonkey.net> References: <200601260957.k0Q9vCUn054132@repoman.freebsd.org> <20060126101706.GJ36965@submonkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Jan 2006 10:17:06 +0000 Ceri Davies <ceri@submonkey.net> wrote: > On Thu, Jan 26, 2006 at 09:57:12AM +0000, Murray Stokely wrote: > > murray 2006-01-26 09:57:12 UTC > > > > FreeBSD doc repository > > > > Modified files: > > en/releases/6.1R todo.sgml > > Log: > > Add kbdmux and sysinstall smp kernel install items from the ideas page > > to the 6.1 Desired Features list. > > I think it's a little late to mess with sysinstall to that extent > for 6.1. Sounds like the kind of thing that could sit in -CURRENT for > months, but hardly anyone would actually be using it. It seems that the > main problem with sysinstall is that hardly any of our developers use > it. > > On to the question: how often does an SMP kernel fail to boot where a > UP one might work? I remember that this used to be a problem, but if > it's still "too often", can we have just the bits that probe for an > mptable (or however we determine that there is more that one processor) > in the UP kernel without suffering that instability? > > What I'm basically asking is how much of the SMP code is really required > just to detect MP hardware? *I* have not had many problems. Ok, I've had none. -- Tom Rhodes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060126064908.4bc6215d.trhodes>