From owner-freebsd-current Sat May 16 18:05:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05618 for freebsd-current-outgoing; Sat, 16 May 1998 18:05:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05609; Sat, 16 May 1998 18:05:53 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id BAA15285; Sun, 17 May 1998 01:04:37 GMT Date: Sun, 17 May 1998 10:04:37 +0900 (JST) From: Michael Hancock To: Peter Wemm cc: Bruce Evans , dyson@FreeBSD.ORG, current@FreeBSD.ORG, kkennawa@physics.adelaide.edu.au Subject: Re: libc corruption In-Reply-To: <199805161139.TAA02040@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 16 May 1998, Peter Wemm wrote: > Generating vnode_if.[ch] is another annoyance that I'd like to see > eradicated. You don't want to do that. Think of it as a custom IDL used to keep the VOP interface defined universally for all file systems, including and potentially for file systems in different address spaces. If someone implements a stacked crypto layer, we probably wouldn't want to put various encryption algorithms in the kernel. In Japan, people might want a Kanji character set translation layer and wouldn't want to put huge tables in the kernel either. It would be very very difficult to extend and maintain compatibility without a mechanism like we have now. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message