From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET
Description of problem:
Symbolic links were not created for hotplug events
Note:I am not entitled to raise defects for "Red Hat Enterprise Linux
Beta", hence opening this bug under product "Red Hat Enterprise Linux
Version-Release number of selected component (if applicable):
kernel-2.6.7-1.451.2.3, rpm-4.3.2-0.4, RHEL4 Alpha4
Steps to Reproduce:
1.No symolic link exits for hotplugs
What sort of symbolic links are you looking for?
What architecture (you mentioned 'alpha', that doesn't seem right. :) )
Usually for hotplugging support a symbolic link is being created
which exactly refers to the specific device number of a (e.g.) DASD.
It means that like in UDEV or DEVFS I have the opportunity to refer
to a DASD for instance as /udev/dasd/0.0.<devno>/part1. This entry
infact would be a symbolic link to the original DASD name which might
be for instance /dev/dasdX1.
My apologies the defect I raised is for Red Hat Enterprise Linux Beta
Since I do not have the access rights yet, for Red Hat Enterprise
Linux Beta , I have raised under Red Hat Enterprise Linux.
----- Additional Comments From firstname.lastname@example.org 2004-09-30 11:32 EDT -------
ping ? any update here for next beta?
----- Additional Comments From email@example.com 2004-11-16 04:20 EDT -------
Hello ! Any info yet on this defect please let us know in case if you require
any more information.
----- Additional Comments From firstname.lastname@example.org 2004-11-19 04:55 EDT -------
I have made the following observations.
When I added two more entries for DASD in the file /etc/udev/rules.d/50-
The sym links are getting created in the directory /dev/dasd.
However I feel for zSeries these entries should present by default.Please let
me know your concern on this.
are these the only rules you need for udev??
----- Additional Comments From email@example.com 2004-11-23 04:09 EDT -------
Yes these are the only two entries , which I added to create symbolic links
for dasd. It works .
----- Additional Comments From firstname.lastname@example.org 2004-12-28 03:57 EDT -------
Tested on pre RC2 release and is not reproducable. This can be closed.
----- Additional Comments From email@example.com 2005-01-10 19:21 EST -------
Closing problem. Thanks.