From owner-freebsd-arch Fri Jan 18 17:17:21 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 5111537B400 for ; Fri, 18 Jan 2002 17:17:18 -0800 (PST) Received: (from ak03@localhost) by h132-197-179-27.gte.com (8.11.6/8.11.4) id g0J1H4x98655; Fri, 18 Jan 2002 20:17:04 -0500 (EST) (envelope-from ak03) Date: Fri, 18 Jan 2002 20:17:04 -0500 From: "Alexander N. Kabaev" To: Poul-Henning Kamp Cc: Maxime Henrion , freebsd-arch@FreeBSD.ORG Subject: Re: Proposal for a new mount API Message-ID: <20020119011702.GB98105@kanpc.gte.com> References: <20020118164457.B52542@sneakerz.org> <18157.1011394111@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18157.1011394111@critter.freebsd.dk> User-Agent: Mutt/1.3.25i 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 > Does that address your concerns ? Yes. I think this API can be made even more powerful when paired with helper generic parameter processing library which is able to convert data from string to the binary format or handle weird parameters names such as 'suid'/'nosuid' which actually refer to single actual parameter. -- Alexander Kabaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message