From owner-freebsd-current@FreeBSD.ORG Mon Oct 27 15:09:08 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 501DD16A4B3; Mon, 27 Oct 2003 15:09:08 -0800 (PST) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E79343FE3; Mon, 27 Oct 2003 15:09:07 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.homeunix.net (66-91-236-204.san.rr.com [66.91.236.204]) by smtp-relay.omnis.com (Postfix) with ESMTP id 5649A5B625; Mon, 27 Oct 2003 15:04:25 -0800 (PST) From: Wes Peters Organization: Softweyr To: Lukas Ertl , wes@freebsd.org Date: Mon, 27 Oct 2003 15:09:04 -0800 User-Agent: KMail/1.5.4 References: <200310271326.23562.wes@softweyr.com> <20031027223620.S604@korben.in.tern> In-Reply-To: <20031027223620.S604@korben.in.tern> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310271509.04732.wes@softweyr.com> cc: current@freebsd.org Subject: Re: newfs by fstab directory name? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2003 23:09:08 -0000 On Monday 27 October 2003 01:37 pm, Lukas Ertl wrote: > On Mon, 27 Oct 2003, Wes Peters wrote: > > At work we do a lot of dynamic filesystem creation, so we added the > > ability to specify the 'special file' argument to newfs via the fstab > > mount point directory. Please see the attached patch. If nobody > > objects, I'll commit this in a couple of days. > > Wouldn't this be a good candidate to be added directly to libufs? libufs already does this sort of translation, but newfs explicitly breaks it because it needs to have the actual name of the device for some other manipulations. The alternative would be to have ufs_disk_fillout_blank et all modify their second argument, which doesn't seem like a great alternative. -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com