From owner-freebsd-arch Fri Jan 18 8:41:35 2002 Delivered-To: freebsd-arch@freebsd.org Received: from h132-197-179-27.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by hub.freebsd.org (Postfix) with ESMTP id F20BA37B400 for ; Fri, 18 Jan 2002 08:41:32 -0800 (PST) Received: from kanpc.gte.com (localhost [127.0.0.1]) by h132-197-179-27.gte.com (8.11.6/8.11.4) with SMTP id g0IGfOZ94590; Fri, 18 Jan 2002 11:41:24 -0500 (EST) (envelope-from ak03@gte.com) Date: Fri, 18 Jan 2002 11:41:24 -0500 From: Alexander Kabaev To: Poul-Henning Kamp Cc: mux@sneakerz.org, freebsd-arch@FreeBSD.ORG Subject: Re: Proposal for a new mount API Message-Id: <20020118114124.61c39faf.ak03@gte.com> In-Reply-To: <12159.1011371137@critter.freebsd.dk> References: <20020118112224.236b4754.ak03@gte.com> <12159.1011371137@critter.freebsd.dk> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.7.0claws8 (GTK+ 1.2.10; i386--freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I belive what you see is the backwards compatibility stuff. How is that? The vfs_nmount sycall accepts flags as its first parameter and then proceeds testing it for flags various MNT_??? bits almost exactly as the existing mount sysccall is doing today. What is the point in backwards compatibility for these functions anyway? The new mount was supposed to become a new syscall, if I am not mistaken. -- Alexander Kabaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message