Date: Tue, 6 Apr 2004 11:37:48 -0700 From: Wes Peters <wes@softweyr.com> To: Wes Peters <wes@FreeBSD.org>, src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Cc: brooks@freebsd.org Subject: Re: cvs commit: src/etc/rc.d ramdisk ramdisk-own Message-ID: <200404061137.48974.wes@softweyr.com> In-Reply-To: <200404061826.i36IQh5P025090@repoman.freebsd.org> References: <200404061826.i36IQh5P025090@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404061137.48974.wes>