Re: /proc/misc has bad mode

Matthias Urlichs (smurf@smurf.noris.de)
Sat, 20 Apr 1996 00:53:20 +0200 (MET DST)


Hi,

Molnar Ingo wrote:
>
>[ readonly root filesystem ]
>whee, almost. what about /etc/ld.so.cache?

What about it? After installing a library (or when booting), I remount =
root
read-write, run ldconfig, then mount it readonly again. I (have to) do =
the
same when I want to update config files in /etc.

In situations where this isn't appropriate, /etc/ld.so.cache can easily=
be
symlinked off to /var/whatever, and /sbin/ldconfig can be patched to up=
date
there.

Of course, I could have done the same with /etc/mtab, and used mount -n=
and
umount -n a whole lot, at boot and shutdown time. But the other advanta=
ge
of /proc/mounts (the first is, of course, that it can't get out of sync=
) is
that now three different mount commands won't block each other. This is
important when booting -- I usually do a parellel fsck+mount, and when =
two
of these are done at the same time, previously at least one mount comma=
nd
would simply fail. Or they all would hang because another mount command
would be busy mounting all these slow NFS servers, and yet a third moun=
t
command would scan the CD-ROM changer and mount all the CDs. (If you th=
ink
I'm crazy, you're probably not entirely wrong. ;-)

Well, no longer. Now all this is able to run in parallel, and I can
finally say "mount -atiso9660 &" in my /etc/rc.local, and have that
ampersand character actually _mean_ something.

A big Thank You to whoever put in the option handling for /proc/mounts.

--=20
May's Law:
The quality of correlation is inverely proportional to the densit=
y
of control. (The fewer the data points, the smoother the curves.)
--=20
Matthias Urlichs \ XLink-POP N=FCrnberg | EMail: urlichs@smurf.=
noris.de
Schleiermacherstra=DFe 12 \ Unix+Linux+Mac | Phone: ...please use =
email.
90491 N=FCrnberg (Germany) \ Consulting+Networking+Programming+etc'i=
ng 42
PGP: 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 DE=20
Click <A HREF=3D"http://smurf.noris.de/~smurf/finger">here</A>.