From owner-freebsd-fs@FreeBSD.ORG Sat Jul 3 19:49:39 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97CA616A4CE; Sat, 3 Jul 2004 19:49:39 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 121FC43D48; Sat, 3 Jul 2004 19:49:39 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i63Js1VV083254; Sat, 3 Jul 2004 13:54:01 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40E70D90.4090304@freebsd.org> Date: Sat, 03 Jul 2004 13:48:32 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alfred Perlstein References: <20040702184020.GC95729@elvis.mu.org> In-Reply-To: <20040702184020.GC95729@elvis.mu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: fs@freebsd.org Subject: Re: tweaking mounted filesystems by fsid X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2004 19:49:39 -0000 Alfred Perlstein wrote: > Hi. > > The last year or so I spent bringing file system improvements into > OS X. > > The mechanism I used to tweak filesystems was sysctl. > > I created a node that would route a request to a filesystem based > on a fsid. This would allow tweaking of filesystems without entering > the namespace. > > I realize we have the nmount syscall. I have several questions > about it. > > 1) can I muck with it so that it functions like unmount(2) by > taking the "FSID:val0:val1" parameter in order to properly > route requests? > > 2) what if i want to pass binary data? I can do that right? > I assume by just passing the binary gook via the value of the > key value pair. > > Any comments? > > On of the issues I have is that I need the call to be callable > from both inside and outside of the kernel, I'm guessing this can > be taken care of by the internal options... > > Ideas people? > > Use nmount or sysctl? > Can't comment on your main questions, but there has been talk about removing nmount since the work was never finished and the benefits never realized. If you'd like to breath some life into it, feel free. Scott