Bug 714531 - rc.sysinit calls start_udev which is not a part of udev
Summary: rc.sysinit calls start_udev which is not a part of udev
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-19 23:54 UTC by Sergey
Modified: 2014-03-17 03:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-21 19:22:37 UTC
Type: ---


Attachments (Terms of Use)

Description Sergey 2011-06-19 23:54:05 UTC
Description of problem:
When booting the system using rc.sysinit (i.e. with upstart) udev does not start, because rc.sysinit contains a call to start_udev which is not a part of udev any more.

Suggested solition:
Replace call to `start_udev` with call to `udev -d` and related udevadm calls in rc.sysinit.
Alternatively put start_udev script into initscripts-legacy. Or, maybe, bring it back to the udev package?

Version-Release number of selected component (if applicable):
udev-171-1.fc16.i686
initscripts-legacy-9.30-1.fc16.i686

How reproducible:
Always

Steps to Reproduce:
0. Get rawhide updated
1. yum install upstart
2. boot with init=/sbin/upstart

Actual results:
a bunch of errors and udev not starting

Expected results:
everything boots and works as usual.

Comment 2 Sergey 2011-06-20 22:38:03 UTC
Works for me. Thanks.

The difference compared to the start_udev version is only in a missing line:
Starting udev: [ OK ]


Just an idea: what about splitting those three commands into two parts: "Staring udev" and "Waiting for devices to settle"? First part is started where it is, and second (udevadm settle) is called later, near "init_crypto" or even "Mounting local filesystems", allowing udev to do its job while sysinit sets the hostname, etc.

Should I fill a feature request about it? Is there some initscripts-related mailing list for such questions/ideas?

Comment 3 Bill Nottingham 2011-06-21 19:21:56 UTC
That would be effectively changing the operating paradigm of the script. Given that's it's only maintained for critical fixes like this (and likely won't be maintained long term, as upstart falls out of use), I'm not really interested in changes of that sort.

I'll add a brief message for udev start that matches what was there before.


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