Date: Mon, 2 Aug 2004 11:36:11 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/modules Makefile Message-ID: <20040802183611.GA1700@dragon.nuxi.com> In-Reply-To: <200408021422.19592.jhb@FreeBSD.org> References: <200408021814.i72IE6QJ030695@repoman.freebsd.org> <200408021422.19592.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 02, 2004 at 02:22:19PM -0400, John Baldwin wrote: > On Monday 02 August 2004 02:14 pm, David E. O'Brien wrote: > > obrien 2004-08-02 18:14:06 UTC > > > > FreeBSD src repository > > > > Modified files: > > sys/modules Makefile > > Log: > > Don't build and install a mem.ko module. > > Currently one cannot load the mem.ko module without panicing if mem is > > compiled into the kernel and one cannot build a kernel w/o "device mem" > > right now either. Thus it is too dangerous to install mem.ko right now > > because if one puts 'mem_load="YES"' in /etc/loader.conf they cannot > > boot an "old" kernel (at the time that a kernel doesn't have to be built > > with "device mem). > > > > Revision Changes Path > > 1.388 +0 -1 src/sys/modules/Makefile > > You need to file a bug report, not start a commit war. Revert this > commit and give Mark a chance of trying to fix this. Why is this a commit war? I'm trying to prevent panics for something that is a WIP and isn't ready for prime time. I'll back it out, but I'm now asking for a back out of the entire mem as a module commit -- it is only 1/2 baked and CVS doesn't need to be a sandbox for incomplete WIP's that panic can easly the system. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040802183611.GA1700>