From owner-freebsd-current Thu Oct 16 11:23:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA15433 for current-outgoing; Thu, 16 Oct 1997 11:23:08 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA15418 for ; Thu, 16 Oct 1997 11:22:58 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id UAA23465; Thu, 16 Oct 1997 20:22:08 +0200 (CEST) To: Karl Denninger cc: current@FreeBSD.ORG Subject: Re: Can I have the pointy cap please? (or did someone really break something?) In-reply-to: Your message of "Thu, 16 Oct 1997 12:56:57 CDT." <19971016125657.25670@Mars.Mcs.Net> Date: Thu, 16 Oct 1997 20:22:07 +0200 Message-ID: <23462.877026127@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <19971016125657.25670@Mars.Mcs.Net>, Karl Denninger writes: >Do you (or anyone else) know if this megacommit will screw me using >nfs_bio.c 1.41 (instead of 1.44)? I have to do this to avoid panics >due to problems with the small-write consolidation that were introduced >in 1.42. Since there are major changes in the I/O subsystem, I thought >I'd ask before finding out the hard way. I have no idea really. All these changes are supposed to be functional NO-OPs, its merely reordering the way the bits cling together (I hope!) not what they do, so I guess the likely answer to your question is that if nfs_bio.c compiles, then you're probably safe. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."