On Wed, Aug 10, 2011 at 04:13:16PM -0400, Rich Freeman wrote: > > It was historically in /etc because it got used to mount /var. > > As an example, if you grab some RHEL systems on the default install, > > every entry in the fstab is UUID=... rather than fixed devices. Not > > having the cache the mounts will still work, but will be very slow as > > all devices will be rescanned. > I would think that something like this would change so infrequently as > to not matter much. If you're going to actually install new block > devices relevant to the boot process, I have to think that somewhere > along the lines you'll probably need to mount /etc read-write. It can change more often than you realize in some more enterprisy situations. The one that I've seen the most was a fibrechannel SAN, where the disk order varied with the response time of the devices (first-come first-serve in allocation of device nodes). Alternatively booting with USB/Firewire storage devices attached, if those storage modules are loaded before whatever other controller, it will vary depending what you have attached.
> mdadm.conf is in a similar boat. So is fstab for that matter (my > fstab probably changes more often than the list of permanent block > devices does). mdadm.conf is less of a concern as it's written by the user, not the system, and it contains just UUIDs and scans devices directly to assemble. -- Robin Hugh Johnson Gentoo Linux: Developer, Trustee & Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
