Jeffrey Walton wrote:This problem comes up several times a year on the mailing list. Can you find a place to memorialize it, like <https://wiki.debian.org/>?
Instead of manual "ln", looking into /lib/udev/rules.d/60-cdrom_id.rules, I expect something like (untested, I do not have an optical drive)
SUBSYSTEM=="block", KERNEL=="sr[0-9]*", ENV{DEVTYPE}=="disk", ACTION!="remove", SYMLINK+="scd%n"
in /etc/udev/rules.d/ Perhaps it needs some fix prior to be added to<https://wiki.debian.org/BurnCd>. I see that a link to this thread has been added to <https://wiki.debian.org/cdrecord>
On 19/11/2025 15:14, Thomas Schmitt wrote:
There seems to be no public code repository either.
I think <https://salsa.debian.org/debian/cdrkit>is public enough. There is no separate upstream repository. Last commits to this one are almost exclusively related to Debian packaging staff.
Thomas, of course, I do not expect merge requests from you. You info related to scdX vs. srX device naming and to locking issues with sgX may be extremely valuable though to those whose who have optical drives and some time to prepare a fix.
That is why I earlier asked if xorriso may be a replacement.Rather cdrskin, which can do audio, CD-TEXT, and CDRWIN CUE files. xorriso restricts itself to single-track data sessions. The CD use cases knwon to me which demand wodim or cdrecord are:
Thanks for clarification.