mounting /usr read-only -- didn't this *used* to work?
Robert P. J. Day
rpjday at crashcourse.ca
Sun Oct 21 12:59:59 UTC 2007
On Sun, 21 Oct 2007, Jacques B. wrote:
> On 10/21/07, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
... blah blah about remounting /usr read-only ...
> Something I must try. Never tried the remount option. Did you try
> an lsof to see if there are any open files from /usr for some reason
> as well as check the output of your ps for same?
there's no question that running "lsof" on the /usr filesystem is
going to give *tons* of output, since there's all sorts of things
open, like shared libraries and so on. but, again, those should be
open for read only, so that shouldn't *technically* stop me from
remounting that way.
the question is -- is there something open in such a way as to prevent
that remounting; that is, is there anything running behind the scenes
that is *writing* to /usr without my explicit intervention? if there
is, that would seem to be a violation of the FHS, which dictates that
/usr be explicitly static and only change based on operator
intervention.
so what might be running that is quietly updating something in /usr to
prevent that remount? or is there another reason for this happening?
rday
p.s. as i mentioned, the read-only remount works fine on separate
filesystems i have (/opt, /usr/local) that aren't doing anything at
the moment.
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
More information about the fedora-list
mailing list