Date: Thu, 14 Oct 2004 22:40:58 -0400 From: Bill Vermillion <bv@wjv.com> To: freebsd-current@freebsd.org Subject: Re: atapiacam(4) at KLD? Message-ID: <20041015024058.GA79925@wjv.com> In-Reply-To: <20041014120059.9871316A4D7@hub.freebsd.org> References: <20041014120059.9871316A4D7@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
While humming that old rock song Yackety Yacc - Dont Awk Back freebsd-current-request@freebsd.org sang or SED something like this: > > Message: 2 > Date: Thu, 14 Oct 2004 13:45:25 +0200Westeurop?ische Normalzeit) > From: Lukas Ertl <le@FreeBSD.org> > Subject: Re: atapicam(4) as KLD? > To: freebsd-current@FreeBSD.org > Message-ID: <Pine.WNT.4.61.0410141343500.2552@korben> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > On Thu, 14 Oct 2004, Michael Nottebrock wrote: > > Easy workaround: Put atapicam into GENERIC. I'm waiting for > > that to happen ever since atapicam entered the tree. > How hard would it be to offer multiple different GENERIC kernels > at the install stage, and the user can decide which one to > install? One with atapicam, one without... (this is not limited > to atapicam, of course). My own personal opinion is that would be very ugly. It brings back memories of the time I was doing beta testing on the Caldera Linux single boot kernel. Prior to that time you figured out what hardware you had, and then chose from a dozen or more kernel choices. I'd think that making comments on such things like this in the RELEASE NOTES would be the appropriate place. Of course the problem is getting people to read RELEASE NOTES just as it seems a bit hard for some to read UPDATING. Bill -- Bill Vermillion - bv @ wjv . com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041015024058.GA79925>