I'm no expert, but as I understand it, halevt simply monitors the system changes that hal reports and executes commands if it encounters something that matches a rule in it's config file.
I'd be surprised if hal didn't report some change in status when a disc becomes readable, but whether you can do what you want without ejecting the disc, I don't know. It could be that the system itself can't detect the change unless the disc is reloaded. Most burning programs seem to automatically eject discs at the end of a burn, and there's probably a reason for that. I can also imagine that other functions like udev device creation may depend on a physical reload too.
So all you have to do is determine whether and when hal reports the change in status, and write a corresponding halevt rule for it. You could probably start by watching lshal in monitor mode (lshal -m).
|