Bug 158579 - Multiple entries for /dev/shm in /etc/fstab
Summary: Multiple entries for /dev/shm in /etc/fstab
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: MAKEDEV   
(Show other bugs)
Version: 3.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Brock Organ
Whiteboard: RHEL3U7NAK
Depends On:
Blocks: 190430 205158
TreeView+ depends on / blocked
Reported: 2005-05-23 19:18 UTC by David Milburn
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-10 14:42:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description David Milburn 2005-05-23 19:18:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
When /etc/fstab has an entry for /dev/shm mount point
that mounts a ramfs instead of a tmpfs, an upgrade from
dev-3.3.12-1 to dev- will generate another
/etc/fstab entry for /dev/shm with a filesystem type
of tmpfs. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Change /dev/shm entry in /etc/fstab to mount ramfs instead of tmpfs.
2. Upgrade to dev-
3. Cat /etc/fstab

Actual Results:  Two entries for /dev/shm

none /dev/shm tmpfs defaults 0 0
none /dev/shm ramfs defaults 0 0

Expected Results:  One entry for /dev/shm

none /dev/shm ramfs defaults 0 0

Additional info:

Comment 1 Nalin Dahyabhai 2005-07-21 22:00:04 UTC
The kernel's tmpfs.txt file doesn't mention that ramfs can be used here
(personally, I don't know why you'd want to), but it's still a bug in the %post
script.  Fixing in

Comment 12 Chris Lumens 2007-07-10 14:42:58 UTC
Closing as WONTFIX based on comment #11.

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