Kostik Belousov wrote:
On Fri, Dec 19, 2008 at 12:52:12PM -0800, Maxim Sobolev wrote:
Should not it be better to implement this on the kernel side when the
device is closed abruptly?
The state that is kept is not accumulated on any particular filedescriptor,
it is associated with the physical s
On Fri, Dec 19, 2008 at 12:52:12PM -0800, Maxim Sobolev wrote:
> Should not it be better to implement this on the kernel side when the
> device is closed abruptly?
The state that is kept is not accumulated on any particular filedescriptor,
it is associated with the physical state of the device.
T
On Fri, Dec 19, 2008 at 12:52:12PM -0800, Maxim Sobolev wrote:
> Should not it be better to implement this on the kernel side when the
> device is closed abruptly?
Maybe. I've hit this issue before and there was a patch to fix it and
I wanted to see it fixed. If you have a patch to fix it as yo
Should not it be better to implement this on the kernel side when the
device is closed abruptly?
David E. O'Brien wrote:
Author: obrien
Date: Fri Dec 19 20:20:14 2008
New Revision: 186337
URL: http://svn.freebsd.org/changeset/base/186337
Log:
burncd(8) doesn't handle signals and interrupting
