Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 230

Summary: makewhatis expects /usr to be rw
Product: [Retired] Red Hat Linux Reporter: Marc MERLIN <marc_soft>
Component: manAssignee: David Lawrence <dkl>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1998-12-04 22:10:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marc MERLIN 1998-11-30 10:00:14 UTC
Resending old report to bugzilla.

This "bug" doesn't show on a stock installation.

The problem is that makewhatis is non FHS compliant (since
one is supposed to be able to mount /usr as read

If you replace the makewhatis cron job with the following
script, it should catch the most common setups (it won't
work though if for instance /usr/local/man is a mount point)

# By

if [ ! -z "`cat /proc/mounts  | grep '/usr ' | grep ro`" ];

        mount -o remount,rw
if [ ! -z "`cat /proc/mounts  | grep '/usr/local ' | grep
ro`" ]; then

        mount -o remount,rw


if [ $USR = "yes" ];
        mount -o remount,ro
if [ $USRLOCAL = "yes" ];
        mount -o remount,ro

Comment 1 David Lawrence 1998-12-04 22:10:59 UTC
This would be nice ideally but it unfortunately cannot happen
realistically. A multiuser machine requires /usr to be accessible most
of the time. When root wants to upgrade something, they would need to
unmount the partition and then remount rw in order to upgrade and then
back again. This would cause interruption. Most of the /usr tree is
already non writable by users other than root regardless.

Comment 2 Marc MERLIN 1998-12-04 22:20:59 UTC
You don't need to umount /usr to remount as read write, there is no
interruption involved.

I use:
magic:~$ more /var/local/scr/rw

echo Remounting /usr read-write
if [ ! -z "`cat /proc/mounts  | grep '/usr '`" ]; then
        mount -o remount,rw /usr
if [ ! -z "`cat /proc/mounts  | grep '/usr/local '`" ]; then
        mount -o remount,rw /usr/local

/usr has been read only on my systems for over two years with no
problems whatsoever (except the occasional script that I need to fix).
The main reason for having /usr ro is to prevent long fscks and
possible filesystem corruption when a crash/power outage does occur.

Note that it is still fine with me if you discard this though :-)