https://bugzilla.novell.com/show_bug.cgi?id=788886 https://bugzilla.novell.com/show_bug.cgi?id=788886#c7 --- Comment #7 from aleksei P. <opera1818@yandex.ru> 2012-11-19 21:56:17 UTC ---
How did you get it installed? Have you tried mounting the images?
http://cdemu.sourceforge.net/about/vhba/
As such, depending on the configuration (i.e. if CDEmu daemon is to be run in session, non-root mode), it might be a good idea to include an udev rule to set up appripriate permissions. E.g.:
KERNEL=="vhba_ctl", NAME="%k", MODE="0660", OWNER="root", GROUP="cdrom" For example in arch: https://www.archlinux.org/packages/community/i686/vhba-module/
View the file list for vhba-module: ... usr/lib/udev/rules.d/60-vhba.rules
+ https://www.archlinux.org/packages/community/i686/cdemu-daemon/
.... usr/lib/systemd/system/cdemu-daemon.service ...
cdemu-daemon is supposed to be run as user.
# modprobe -r vhba # cd /etc/udev/rules.d/ # mv 60-vhba.rules 60-vhba.rules.backup # modprobe vhba ~> /usr/bin/cdemud Starting daemon in local mode with following parameters: - num devices: 1 - ctl device: /dev/vhba_ctl - audio driver: null - bus type: session cdemu0: Device: failed to open control device /dev/vhba_ctl! cdemud: Daemon: failed to initialize device 0! Daemon initialization failed: Device initialization failed. # modprobe -r vhba # mv 60-vhba.rules.backup 60-vhba.rules # modprobe vhba ~> /usr/bin/cdemud Starting daemon in local mode with following parameters: - num devices: 1 - ctl device: /dev/vhba_ctl - audio driver: null - bus type: session In other console: ~> cdemu status Devices' status: DEV LOADED FILENAME 0 0 N/A
There is no udev rule file by default because that is a site-specific security decision. Some users may want 0666, others may want {0660 with a cdemu group}.
Therefore it is necessary to find a compromise. I think a normal user should not: /sbin/yast2 sysconfig set MODULES_LOADED_ON_BOOT="vhba" touch /etc/udev/rules.d/60-vhba.rules -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.