From owner-cvs-src@FreeBSD.ORG Tue Apr 6 11:39:10 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6797116A4D0; Tue, 6 Apr 2004 11:39:10 -0700 (PDT) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E1B943D45; Tue, 6 Apr 2004 11:39:08 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from salty.rapid.stbernard.com (unknown [198.147.128.71]) by smtp-relay.omnis.com (Postfix) with ESMTP id C6C46101C3D; Tue, 6 Apr 2004 11:37:16 -0700 (PDT) From: Wes Peters Organization: Softweyr.com To: Wes Peters , src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Date: Tue, 6 Apr 2004 11:37:48 -0700 User-Agent: KMail/1.5.4 References: <200404061826.i36IQh5P025090@repoman.freebsd.org> In-Reply-To: <200404061826.i36IQh5P025090@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200404061137.48974.wes@softweyr.com> cc: brooks@freebsd.org Subject: Re: cvs commit: src/etc/rc.d ramdisk ramdisk-own X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Apr 2004 18:39:10 -0000 On Tuesday 06 April 2004 11:26 am, Wes Peters wrote: > wes 2004/04/06 11:26:43 PDT > > FreeBSD src repository > > Modified files: > etc/rc.d ramdisk > Added files: > etc/rc.d ramdisk-own > Log: > Split ramdisk processing in two so it can actually work. Ownerships > and permissions specified per rc.conf(5) now apply both to the md > device and to the mountpoint directory, after the mount has completed. > This has to be done in two steps, because chown is not available > until after /usr has been mounted, but the mdconfig and newfs steps > have to complete before fstab processing. Now that Brooks has split out dynamic creation of /var and /tmp for diskless systems, I wonder if we could profitably coalesce these? Maybe not; the ramdisk silliness is mostly just to help people who want to use md's for small pools of high-speed cache, and is quite manual and simple about configuration, where Brooks' var and tmp processing is quite automatic. Still, it bears some thinking. -- "Where am I, and what am I doing in this handbasket?" Wes Peters wes@softweyr.com