From owner-freebsd-hackers Mon Oct 20 12:48:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA15180 for hackers-outgoing; Mon, 20 Oct 1997 12:48:28 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA15173 for ; Mon, 20 Oct 1997 12:48:25 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id NAA15483; Mon, 20 Oct 1997 13:48:13 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA00007; Mon, 20 Oct 1997 13:48:13 -0600 (MDT) Date: Mon, 20 Oct 1997 13:48:13 -0600 (MDT) Message-Id: <199710201948.NAA00007@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Nate Williams , joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: Urge to apply the vn device hack even to 2.2.5 In-Reply-To: <13791.877372893@time.cdrom.com> References: <199710201615.KAA29216@rocky.mt.sri.com> <13791.877372893@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > My advice is to 'just do it'. I suspect Jordan must have the patch on > > his build box in order for him to roll the release, and since there are > > few hours left to do it in, it should be done ASAP. > > I don't, that's the weird thing. I'm running a standard 2.2-stable > kernel here. Maybe it only hits in situations where you have a > certain amount of RAM? Hmm, I don't know. It's been seen by lots of folks though. > In any case, the tag is going down in just over 6 hours, so a decision > will need to be made quickly. :) I decided to take the heat for it. I haven't been in a good flame wars in awhile. It won't break the compile in any case, and I know enough people who build 'private' releases that breaking it seems silly. Nate ps. It *shouldn't* break your build, but if it does yell at me and yank it out.