Artem Kachitchkine <Artem.Kachitchkin at Sun.COM> wrote: > > BTW: cdrecord (when going to write to a CD / DVD / BD) loads the medium, > > then locks the eject button and will not unlock the eject button before > > the write process to the medium has been completed. Is there a potential > > problem that could remove the lock from the eject button that has been > > established by cdrecord and thus make cdrecord less reliable than before? > > The effect would be the same as issuing eject(1) command during cdrecord. > > The latest version of HAL provides interface locking: > > http://people.freedesktop.org/~david/hal-spec/hal-spec.html#locking > > Applications like cdrecord can grab the lock for the duration of the > critical operation, which would prevent any DBus method from being > called on the locked interface, including Eject() method. HAL in > Solaris, however, needs to be upgraded to the latest version to get this > functionality.
Do you know when this will happen? Do you know whether this will allow to force to unmount a filesystem in order to allow cdrecord to add another session to the medium? J?rg -- EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin js at cs.tu-berlin.de (uni) joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily