Bug 134271

Summary: udev complains if no files are in /etc/udev/devices
Product: [Fedora] Fedora Reporter: Bernard Johnson <bjohnson>
Component: udevAssignee: Harald Hoyer <harald>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: udev-032-6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-10-01 08:13:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 130887    

Description Bernard Johnson 2004-09-30 19:13:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040808 Firefox/0.9.3

Description of problem:
If there are no files in /etc/udev/devices, start_udev complains on
bootup:




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

How reproducible:
Always

Steps to Reproduce:
1. boot system with no files in /etc/udev/devices
2.
3.
    

Actual Results:                  Welcome to Fedora Core
                Press 'I' to enter interactive startup.
Making extra nodes:  cp: cannot stat `/etc/udev/devices/*': No such
file or directory
[FAILED]

Expected Results:  no complaint message

Additional info:

Comment 1 TGS 2004-10-01 07:49:15 UTC
Same error here.

Comment 2 TGS 2004-10-01 07:53:29 UTC
I should add that the system hangs at this point.

Just updated my system to the latest development as of 3 AM EST, and 
cannot
boot. 

Error follows:

Press 'I' to enter interactive startup.

Making extra nodes: cp: cannot stat '/etc/udev/devices/*': No such 
file or
directory
                                                     [FAILED]
Starting udev:                                       [  OK  ]
Initializing hardware... storage network audio done [  OK  ]
Configuring kernel parameters:

then nothing, since it is frozen.


Comment 3 Harald Hoyer 2004-10-01 08:22:19 UTC
seems like /etc/sysctl.conf is b0rken or /proc is not mounted...
the "cp" error does not harm... really...

Comment 4 TGS 2004-10-01 12:20:02 UTC
Update: if I remove the rhgb option from the grub kernel options, I 
can boot.