From owner-freebsd-arch  Fri Jan 18 14:51:38 2002
Delivered-To: freebsd-arch@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by hub.freebsd.org (Postfix) with ESMTP id C0C5537B43F
	for <freebsd-arch@FreeBSD.ORG>; Fri, 18 Jan 2002 14:51:07 -0800 (PST)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g0IMmVA18159;
	Fri, 18 Jan 2002 23:48:31 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Maxime Henrion <mux@sneakerz.org>
Cc: freebsd-arch@FreeBSD.ORG, Alexander Kabaev <ak03@gte.com>
Subject: Re: Proposal for a new mount API 
In-Reply-To: Your message of "Fri, 18 Jan 2002 16:44:57 CST."
             <20020118164457.B52542@sneakerz.org> 
Date: Fri, 18 Jan 2002 23:48:31 +0100
Message-ID: <18157.1011394111@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG


Let me try to clarify how the new mount api is much stronger and
completely abolishes the 32 bit thing.

If I issue the command:
	mount -t devfs -o thisopt -o thatopt=3 -o yetanopt=DTRT /home/dev

A uiovec will be passed into the kernel which looks like this:

	uiovec[0] = "thisopt"
	uiovec[1] = ""
	uiovec[2] = "thatopt"
	uiovec[3] = "3"
	uiovec[4] = "yetanopt"
	uiovec[5] = "DTRT"
	uiovec[6] = "vfstype"
	uiovec[7] = "devfs"
	uiovec[8] = "mountpoint"
	uiovec[9] = "/home/dev"

As you can see this is extensible in all directions: As long as
I stay with ascii options, I don't have to write a "mount_devfs"
program, and I can introduce new options and filesystems without
rewriting the current mount program.

Now, it may be that a particular filesystem needs to pass binary
data, a UNIcode table has been mentioned as an example, in that
case you can do that, but then you need to write a mount_foofs
program to do that.

Does that address your concerns ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message