Description of problem: /dev/raw/raw0 is char device major 162, minor 0, i.e. /dev/rawctl. If a user attempts to bind this device udev will notice the new device & set up a node for it. It also deletes /dev/rawctl at this point. This is confusing for users. An error message indicating that raw0 should not be bound is preferable. Version-Release number of selected component (if applicable): util-linux-2.12a-16.EL4.20 How reproducible: 100% Steps to Reproduce: 1. raw /dev/raw/raw0 /dev/<something> 2. ls -l /dev/rawctl Actual results: ls: /dev/rawctl: No such file or directory Expected results: /dev/rawctl still exists or the user gets a warning/error Additional info:
Created attachment 149121 [details] trivial patch to give an error when binding raw0
Yeah, this is already known issue (that has been fixed in RHEL5).
And this is a RHEL4 bug - changing flags
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Seems like bug 218315 has addressed this at the kernel level (2.6.9-55.2).
Well, the bug has been fixed in kernel and also in raw(8).
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0785.html