Here is a brief outline of how to get DVD playing/burning working on
Solaris 10 for KDE:

1. create one or more symlinks under /dev, one for each of your CD/DVD
drives,  with the following naming convention:

/dev/rsr0
/dev/rsr1
...
etc

these symlinks should point to the 'c' slice of your CD/DVD drive(s).
on some systems these symlinks already exist. for example:

lrwxrwxrwx  1 root root 13 2005-10-08 19:15 /dev/rsr0 -> rdsk/c0t0d0s2
lrwxrwxrwx  1 root root 13 2005-09-02 14:20 /dev/rsr1 -> rdsk/c1t0d0s2

this is necessary for K3B. there is no way of guessing which devices are
CD/DVD removable media devices, and which are hard disks. i do not like
the idea of scanning everything under /dev/rdsk/c?t?d?s? and determining
by brute force which device is a CD/DVD and which is a hard disk. this way,
we avoid unnecessary polling of hard drives.

2. create a symlink pointing to the 'c' slice of your CD reader/burner
device, and name it /dev/cdrom. for example, on my system:

lrwxrwxrwx  1 root root 18 2005-11-18 22:47 /dev/cdrom -> /dev/rdsk/c1t0d0s2

3. create a symlink pointing to the 'c' slice of your DVD reader/burner
device, and name it /dev/dvd. for example, on my system:

lrwxrwxrwx  1 root root 18 2005-11-18 22:48 /dev/dvd -> /dev/rdsk/c0t0d0s2

this is necessary for Xine/Kaffeine.

if you only have one device which is both a CD and DVD, just create the
two symlinks pointing to the same device.

4. modify the following two files:

/etc/security/prof_attr
/etc/securiy/policy.conf

according to the unified diff's included below:

--- prof_attr.sun.orig	2005-03-15 02:57:35.241914000 -0500
+++ prof_attr	2005-11-13 18:30:02.614752000 -0500
@@ -11,7 +11,7 @@
 Application Server Management:::Administrator of Application Server:
 Audit Control:::Configure BSM auditing:auths=solaris.audit.config,solaris.jobs.admin,solaris.admin.logsvc.purge,solaris.admin.logsvc.read;help=RtAuditCtrl.html
 Audit Review:::Review BSM auditing logs:auths=solaris.audit.read;help=RtAuditReview.html
-Basic Solaris User:::Automatically assigned rights:auths=solaris.profmgr.read,solaris.jobs.users,solaris.mail.mailq,solaris.admin.usermgr.read,solaris.admin.logsvc.read,solaris.admin.fsmgr.read,solaris.admin.serialmgr.read,solaris.admin.diskmgr.read,solaris.admin.procmgr.user,solaris.compsys.read,solaris.admin.printer.read,solaris.admin.prodreg.read,solaris.admin.dcmgr.read,solaris.snmp.read,solaris.project.read,solaris.admin.patchmgr.read,,solaris.network.hosts.read,solaris.admin.volmgr.read;profiles=All;help=RtDefault.html
+Basic Solaris User:::Automatically assigned rights:auths=solaris.profmgr.read,solaris.jobs.users,solaris.mail.mailq,solaris.admin.usermgr.read,solaris.admin.logsvc.read,solaris.admin.fsmgr.read,solaris.admin.serialmgr.read,solaris.admin.diskmgr.read,solaris.admin.procmgr.user,solaris.compsys.read,solaris.admin.printer.read,solaris.admin.prodreg.read,solaris.admin.dcmgr.read,solaris.snmp.read,solaris.project.read,solaris.admin.patchmgr.read,,solaris.network.hosts.read,solaris.admin.volmgr.read,solaris.device.*,solaris.admin.serialmgr.*;profiles=All;help=RtDefault.html
 Contract Observer:::Reliably observe any/all contract events:help=RtContractObserver.html
 Cron Management:::Manage at and cron jobs:auths=solaris.jobs.*,solaris.smf.manage.cron;help=RtCronMngmnt.html
 Crypto Management:::Cryptographic Framework Administration:help=RtCryptoMngmnt.html


--- policy.conf.sun.orig	2005-03-15 02:45:59.528395000 -0500
+++ policy.conf	2005-11-14 22:40:24.108312000 -0500
@@ -8,7 +8,8 @@
 #
 #ident	"@(#)policy.conf	1.11	04/09/27 SMI"
 #
-AUTHS_GRANTED=solaris.device.cdrw
+AUTHS_GRANTED=solaris.device.;solaris.device.allocate;solaris.device.cdrw;solaris.device.config;solaris.device.grant;solaris.admin.privilege.
+# AUTHS_GRANTED=solaris.device.cdrw
 PROFS_GRANTED=Basic Solaris User
 
 # crypt(3c) Algorithms Configuration
@@ -49,8 +50,8 @@
 # as any set-uid root program may suddenly fail because it lacks certain
 # privilege(s).
 #
-#PRIV_DEFAULT=basic
-#PRIV_LIMIT=all
+PRIV_DEFAULT=basic,sys_devices,proc_owner
+PRIV_LIMIT=all
 #
 # LOCK_AFTER_RETRIES specifies the default account locking policy for local
 # user accounts (passwd(4)/shadow(4)).  The default may be overridden by


this grants sys_devices and proc_owner privileges. this is needed by
libsmedia. without these privileges DVD playing/burning may not work at all.

5. stop vold:

/etc/init.d/volmgt stop

and then kill volcheck, if it happens to be running:

%> pkill -9 volcheck

vold takes an exclusive lock on the devices it manages. because of this,
no other program can access these devices. 

7. make sure you have enabled DMA on your CD/DVD device (X86).

6. that's it. let me know if you run into problems.