Bug 2531 - rpm doesn't check if partitions are mounted read/write
rpm doesn't check if partitions are mounted read/write
Status: CLOSED DUPLICATE of bug 4098
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Turner
Depends On:
  Show dependency treegraph
Reported: 1999-05-04 01:08 EDT by Marc MERLIN
Modified: 2015-01-07 18:37 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-09-14 14:09:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marc MERLIN 1999-05-04 01:08:48 EDT
On my systems /usr and /usr/local are always mounted
read/only, like they were meant to be.
The problem is that when I try to install an rpm, it may
do an incomplete install, but especially if I remove an
existing rpm, it will be removed from the database without
its files being removed from /usr.

So far, I've worked around this problem by moving
/var/lib/rpm to /usr/lib/rhs/rpm, which prevents rpm from
getting a lock on the dabase if /usr is mounted read only,
but it'd be much better if RPM checked if it has write
permissions before doing anything, and abort right away,
instead of doing half the job and bailing out later
Comment 1 Jeff Johnson 1999-05-04 13:32:59 EDT
Rpm was not designed to manage packages on file systems, some
of which are mounted read-only. Maybe some day ...
Comment 2 Jeff Johnson 1999-08-19 11:17:59 EDT
*** Bug 4098 has been marked as a duplicate of this bug. ***

rpm fails to realize it cannot write  when /usr is mounted
RO and an rpm -e or rpm -U
is done.

Result: partly updated  /deleted rpms that are marked as
updated/deleted in the rpm database.

rpm needs to check if it can write on a filesystem

------- Additional Comments From jturner@redhat.com  07/19/99 09:42 -------
This issue has been assigned to a developer for further action.
Comment 3 Jeff Johnson 2001-01-08 11:17:42 EST

*** This bug has been marked as a duplicate of 4098 ***

Note You need to log in before you can comment on or make changes to this bug.