Date: Mon, 10 Jan 2000 00:22:57 +0800 From: Peter Wemm <peter@netplex.com.au> To: obrien@NUXI.com Cc: "Jordan K. Hubbard" <jkh@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/conf GENERIC LINT Message-ID: <20000109162257.7BA5A1CCE@overcee.netplex.com.au> In-Reply-To: Message from "David O'Brien" <obrien@NUXI.com> of "Sun, 09 Jan 2000 08:08:52 PST." <20000109080852.Q54775@relay.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"David O'Brien" wrote: > On Sun, Jan 09, 2000 at 10:44:03PM +0800, Peter Wemm wrote: > > > A) Let the 'sym' take precedence over 'ncr' (default) > > > > Yes! > > I'm personally against this, as I feel it is the wrong thing to do in > -STABLE. Changing a kernel driver out from under deployed stable systems > is something we state we don't do. Don't forget it also causes people > with wired down drive numbering to have to change things if they don't be > extra carful when merging GENERIC changes into their kernel config files. GENERIC doesn't *have* wired down devices.. Making GENERIC support ncr and sym means that new installs support both, but existing systems keep on going the same way they always have. If they boot off a GENERIC kernel, the device wiring (which doesn't exist) and numbering is exactly the same. I can't imagine anyone going to the trouble of adding wiring to a custom kernel without removing drivers they don't use. If they blindly add in new drivers without looking (which would be quite an achievement without a truely non-interactive 3-way merge) then they deserve what they get. Also, using sym instead of ncr stops the dreaded 'ncr + fxp panic' in 3.x for most folks suffering from it. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000109162257.7BA5A1CCE>