You are not logged in.
Pages: 1
Ran pacman -Syu on 2011-10-25 and noted the following message (copied from pacman.log):
[2011-10-25 22:13] ATTENTION UDEV:
[2011-10-25 22:13] ----------
[2011-10-25 22:13] We now use upstream rules for assigning devices to the 'disk', 'optical',
[2011-10-25 22:13] 'scanner' and 'video' groups. Beware of any changes.
[2011-10-25 22:13] --
[2011-10-25 22:13] We no longer create symlinks from /dev/<dev> to /dev/<dev>0.
[2011-10-25 22:13] --
[2011-10-25 22:13] For security reasons, we no longer add devices to the 'storage' group. Use
[2011-10-25 22:13] udisks and friends, or add custom rules to /etc/udev.d/rules/, if you want
[2011-10-25 22:13] this functionality back.
[2011-10-25 22:13] --
[2011-10-25 22:13] We no longer create the static nodes on install needed for an initrd-less and
[2011-10-25 22:13] devtmpfs-less boot, this only affects fresh installs.
[2011-10-25 22:13] ---------------
When I launch xfburn I receive a warning dialog that states:
No burners are currently available
Possibly the disc(s) are in use, and cannot get accessed.
Please unmount and restart the application.
If no disc is in the drive, check that you have read and write access to the drive with the current user.
My user "grim" is a member of the optical group and xfburn worked just fine before the update. So I'm fairly certain it has something to do with the upgrade to udev.
Any suggestions how to remedy the problem?
Offline
Have you tried https://bbs.archlinux.org/viewtopic.php … 0#p1007850 ?
Offline
Thank you for your help karol, I added myself to the "disk" group as stipulated in that conversation and now xfburn properly locates my drive. I do have one concern though, Misfit138 states (on the thread you linked) that doing so is a possible security faux pas. He suggests creating symlinks as per the Beginners' Guide but that did nothing. I would infer that the optimal solution would be to create the udev rule file that makes drives members of the "optical" group again as before (so as to avoid the security pitfalls)? Further, what sort of security vulnerabilities does this create exactly?
Offline
Pages: 1