Is the O_EXCL patch going to be applied so this bug gets fixed?
Joerg Schilling wrote:
[EMAIL PROTECTED] wrote:
This is a followup for bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug2678
I am not that confident hald is a perfect software. Though upstream take
all notes into account. I wondered if your information on how this is
done on solaris could help improve the problem in the above bug.
What is hald?
http://www.freedesktop.org/Software/hal
A volmgt SW that periodically (e.g. every 3 seconds) polls the drive with
a
Test Unit Ready and does not try to mount a device that does not have a
readable medium inserted (e.g. Solaris) does not disturb the writing
process.
That hack of checking periodically is avoided in hald.
In the reported problem there was a medium in the drive .
Did you meant that if there was a cdrom in the drive it may
fails on solaris too ? Or readable medium is only for already
burnt cdrom ?
Could it retrieve more than if the unit is ready (i guess this
is when the drive is ready to read the cdrom), for example the
drive cache size, without breaking the burn process.
As cdrecord waits 10 seconds before starting to write, there is absolutely
no problem on Solaris.
So the hack of waiting 10 seconds is for that!
Debian maintainer: we need to remove that 10 seconds wait.
The Solaris vold will check the CD after at most 3 seconds and after
it found that it is empty, it leaves it alone for cdrecord.
What a shit of hack solaris has!!!
That's why in a real OS the O_EXCL is needed!
From that I have been reported, the volume management on Linux is not
friendly to other applications :-(, it should be fixed.
OK, propose a valid fix, but a real fix, not the Solaris hack.
Joerg please give solutions instead of whining about solaris. If you
need to sell all your SUN stock just do it! ;-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
