Bug 649753 - /dev gets mounted two times during start up
Summary: /dev gets mounted two times during start up
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: udev
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: udev-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-04 13:50 UTC by Artem S. Tashkinov
Modified: 2012-05-10 19:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-10 19:08:45 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Artem S. Tashkinov 2010-11-04 13:50:03 UTC 
Description of problem: /dev gets mounted two times during start up

Version-Release number of selected component (if applicable): initscripts-9.20.1-1.fc14

How reproducible: Always

Steps to Reproduce:
1. Boot F14
2. grep udev /proc/mounts
3.
  
Actual results: 

udev /dev devtmpfs rw,...
udev /dev devtmpfs rw,...

Expected results:

udev /dev devtmpfs rw,...

Additional info:
Comment 1 Bill Nottingham 2010-11-04 18:07:23 UTC 
initscripts doesn't specifically mount /dev. Moving to udev, may be dracut.
Comment 2 Artem S. Tashkinov 2010-11-04 22:02:37 UTC 
Sorry I actually meant 'boot sequence', thus dracut, so you are right - this bug has nothing to do with initscripts.

BTW, why users aren't allowed to change a component?
Comment 3 Fedora Admin XMLRPC Client 2011-10-20 16:10:14 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 4 Fedora Admin XMLRPC Client 2011-10-20 16:12:04 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 5 Fedora Admin XMLRPC Client 2011-10-20 16:14:52 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 6 Artem S. Tashkinov 2012-05-10 19:08:45 UTC 
SysVinit got killed. Thus this bug bears no relevance any longer.
Note You need to log in before you can comment on or make changes to this bug.