From owner-cvs-all@FreeBSD.ORG Tue Mar 16 03:24:05 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4BF016A4CE for ; Tue, 16 Mar 2004 03:24:05 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 9E2AC43D53 for ; Tue, 16 Mar 2004 03:24:05 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 57621 invoked by uid 1002); 16 Mar 2004 11:24:03 -0000 Received: from unknown (HELO ?10.4.1.17?) (64.58.1.252) by smtp.mho.net with SMTP; 16 Mar 2004 11:24:03 -0000 Date: Tue, 16 Mar 2004 04:27:45 -0700 (MST) From: Scott Long X-X-Sender: scottl@pooker.samsco.home To: Maxime Henrion In-Reply-To: <20040316101114.GN35475@elvis.mu.org> Message-ID: <20040316041008.R8512@pooker.samsco.home> References: <200403160945.i2G9jcgO074159@repoman.freebsd.org> <20040316101114.GN35475@elvis.mu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: Tim Robbins Subject: Re: cvs commit: src/lib/libc/sys Makefile.inc mount.2 X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2004 11:24:06 -0000 On Tue, 16 Mar 2004, Maxime Henrion wrote: > Tim Robbins wrote: > > On Tue, Mar 16, 2004 at 01:45:38AM -0800, Tim J. Robbins wrote: > > > > > tjr 2004/03/16 01:45:38 PST > > > > > > FreeBSD src repository > > > > > > Modified files: > > > lib/libc/sys Makefile.inc mount.2 > > > Log: > > > Add fairly minimal documentation for the nmount() syscall. > > > > BTW, I am not at all happy with the fact that we have two syscalls > > to mount filesystems. One of them needs to go before 5-stable, > > and personally, I don't see the point of keeping nmount(). > > I entirely agree, and I actually feel quite guilty for that. I couldn't > find time to finish nmount and I'm the only one to blame here. I'm not > even particularly happy with how nmount(2) looks right now. I wanted to > remove nmount from the CVS repository, and suggested that to Poul, since > I wrote this code under his guidance some time ago now. He didn't want > me to remove the code so I just left it as is. > This is unfortunate since a lot of work was put into nmount. I thought that it was supposed to be the Way Of THe Future and provide things that the old mount(2) call couldn't do. However, Tim is right in that if it's developement is dead then it needs to be removed before 5.3. Please let me know what your intention is on this, and what it will affect. Primarily, will this affect the iconv stuff that was recently added to many of the filesystems? Also, will there be any plans to re-visit the limitations of mount(2) in 6.x? Scott