Date: Sun, 9 Jan 2000 09:08:48 -0800 From: "David O'Brien" <obrien@NUXI.com> To: Peter Wemm <peter@netplex.com.au> 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: <20000109090848.U54775@relay.nuxi.com> In-Reply-To: <20000109162257.7BA5A1CCE@overcee.netplex.com.au> References: <obrien@NUXI.com> <20000109162257.7BA5A1CCE@overcee.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 10, 2000 at 12:22:57AM +0800, Peter Wemm wrote: > > GENERIC doesn't *have* wired down devices.. Yes I know. > If they boot off a GENERIC kernel, the device wiring (which doesn't > exist) and numbering is exactly the same. I guess I'm the only one that starts out with a GENERIC file and commenting out rather than deleting stuff I don't want. And I guess I'm the only one that keeps my kernel file synced with GENERIC (again with things I don't want commented out). > I can't imagine anyone going to the trouble of adding wiring to a custom > kernel without removing drivers they don't use. Well I guess you're talking about me. I merge in changes from GENERIC to my kernel config file, commenting them out in the process. When I switched from `ncr' to `sym' on my NFS server I forgot to change all the wiring down. You can guess my CCD with /usr/src on it wasn't too happy when the drive IDs changed. While what I did was stupid, we are talking -STABLE here. I thought we wanted to keep minimal the number of possible disruptions and messups that could occur. > Also, using sym instead of ncr stops the dreaded 'ncr + fxp panic' in 3.x for > most folks suffering from it. Does it?? Paul Sabb while at Hotmail said it didn't. -- -- David (obrien@NUXI.com) 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?20000109090848.U54775>