Bug 150766 - MAKEDEV doesn't like CVS directory in /etc/makedev.d
MAKEDEV doesn't like CVS directory in /etc/makedev.d
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: MAKEDEV (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2005-03-10 07:51 EST by Peter Bieringer
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: 4.19-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-17 16:01:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Bieringer 2005-03-10 07:51:12 EST
Description of problem:
We're using a system CVS to track configuration changes properly.

udev isn't smart enough during running through its configuration
directory and an error message now.

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

How reproducible:

Steps to Reproduce:
1. create directory in /etc/makedev.d
2. reboot

Actual Results:  Starting udev:  error: /etc/makedev.d/CVS is not a
regular file

Expected Results:  No such error message

Additional info:

It looks like udev only expect files in /etc/makedev.d, so why not
filtering the directory open for files only or skip file if it is a
Comment 2 Harald Hoyer 2005-03-11 06:53:03 EST
this is makedev
Comment 3 Nalin Dahyabhai 2005-03-17 15:47:37 EST
If you invoke MAKEDEV with the "-i" flag, it will issue a warning instead of an
error if it runs into a problem reading its configuration.
Comment 4 Peter Bieringer 2005-03-18 08:22:35 EST
How to tell using "-i" udev? ;-)

BTW: can I test the rawhide package on RHEL4?
Comment 5 Harald Hoyer 2005-03-18 10:03:29 EST
Peter, edit /sbin/start_udev and change the MAKEDEV call.

yes, you can _test_ the rawhide package on RHEL4
Comment 6 Peter Bieringer 2005-04-14 04:43:41 EDT
Can confirm that it works now using following version:


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