Date: Thu, 10 Jul 2003 22:31:11 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: FreeBSD-rc@yahoogroups.com Subject: Re: support for mounting md(4) based filesystem at boot [PATCHES] Message-ID: <4173.1057869071@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 10 Jul 2003 17:22:57 -0300." <3F0DCB21.1060704@tcoip.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <3F0DCB21.1060704@tcoip.com.br>, "Daniel C. Sobral" writes: >Andrew Kenneth Milton wrote: >> +-------[ Poul-Henning Kamp ]---------------------- >> | >> | I think we need somebody to reconsider how we configure our filesystems >> | in the future, in order to avoid a confusion of config files whose >> | interrelationship users will have no chance of figuring out. >> | >> | We have CCD, GBDE, MD and in the future likely other technologies for >> | configuring the underlying devices, we have FSCK, UFS and NFS and >> | other filesystems to mount. >> | >> | Somebody must be able to come up with some creative stuff here... ? >> >> We want .... >> >> A REGISTRY! >> >> Ni! Ni! Ni! Ni! Ni! Ni! > >Bah. Add a prerequisites field to fstab with all the filesystems that >must be mounted before that one can be mounted. That's not enough. I have filesystems I don't want fscked/mounted until after sshd will accept my login for instance (I hate waiting for a fsck of /home/ncvs...) (Yes yes yes, bgfsck improves things a bit). Please don't hack /etc/fstab yet another time, please try to do it in a future-proof way (which doesn't suck) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4173.1057869071>