Bug 560756

Summary: initscripts use of SYSFS in 88-clock.rules makes udev unhappy
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: iarlyy, johannbg, jonathan, notting, plautrba, rvokal
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 560801 (view as bug list) Environment:
Last Closed: 2010-02-01 21:27:33 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: 560801    

Description Michal Jaegermann 2010-02-01 19:13:10 UTC
Description of problem:

With the current udev-151-2.fc13 the following warnings show up while booting:

udevd[533]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /lib/udev/rules.d/88-clock.rules:1

udevd[533]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /lib/udev/rules.d/88-clock.rules:2

No idea what this "a future udev version" will be.

Version-Release number of selected component (if applicable):
initscripts-9.04-1.fc13

How reproducible:
on every boot

Comment 1 iarly selbir 2010-02-01 20:33:53 UTC
I don't follow udev's development, but its like a message when you run udevcontrol, indicating that will be removed soon

Bill may be more familiarized with.

Thanks for your report.

--
Fedora Bugzappers Team Member

Comment 3 Bill Nottingham 2010-02-01 21:27:33 UTC
Will be in a future rawhide build.

Comment 4 Bill Nottingham 2010-02-15 15:37:04 UTC
*** Bug 565506 has been marked as a duplicate of this bug. ***