Bug 132358
| Summary: | hald doesn't produce /media/cdrom link | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Steve Grubb <linux_4ever> | ||||||
| Component: | hal | Assignee: | David Zeuthen <davidz> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | rawhide | CC: | mclasen | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2004-09-12 16:22:26 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Steve Grubb
2004-09-11 15:10:29 UTC
Created attachment 103722 [details]
Output from verbose run
Created attachment 103723 [details]
Output from lshal
Hi, it seems hal properly detects your cdrom drive but fstab-sync refuses to add an entry to the fstab since a) there is already an entry for /dev/cdrom; and b) /dev/cdrom is a symlink pointing to /dev/hdc. In fact, since /dev/cdrom and /dev/hdc are the same, fstab-sync actually changes the block.device property on the hal device object representing your optical drive such that e.g. gnome-volume-manager can simply do a 'mount /dev/cdrom' and everything works. I suppose this entry was left by the installer or kudzu from back when updfstab was part of kudzu. So, this is in fact a feature (and a nice one I might add: you don't want two entries in the fstab for the same device), not a bug. Would you agree? (I will close with NOTABUG if you concur) OK, I was under the impression that /dev/cdrom is deprecated and /media/cdrom is the new location. Does this mean that all cdrom software needs to be patched to try /dev/cdrom and /media/cdrom? You can close this PR if this is the case. Well, using and relying on /dev/cdrom is kind of broken since there may be more than one optical drive in the system. Also, relying on a specific mount point is also broken for the same reason. As far as I understand FHS2.3 all filesystems for removable media is to be mounted in /media (and hotpluggable drives without removable media since I consider such to be considered removable media as well). My opinion: software in general and desktop software in particular should rather be asking the hal daemon or looking at sysfs to find the optical drive or other devices with the desired capabilities - thus it needs to be patched anyway. And for good UI the software should rather expose TORISAN DVD-ROM DRD-U624 [X] LITEON DVDRW SOHW-812S [ ] or maybe even better Internal DVD-ROM drive [X] External CD-RW/DVD-RW drive [ ] rather than asking for the device file [/dev/cdrom ] which may be /dev/sr0 or /dev/cdrom1 for an external USB2 drive. All in all, neither special device files nor mount points should appear in any user interface. But all this is still a bit in the future. However, to preserve backwards compatibility udev now creates /dev/cdrom, /dev/cdrom1, ... compat symlinks. Also then pam_console gets it right and the right permissions are applied such that the user can eject optical discs. |