On Thu, Jan 03, 2002 at 02:26:27AM +0100, Jeroen Dekkers wrote:
> Hmm strange as remote debugging works fine.

It's not strange ata ll, as with remote debugging the kernel opens the
device and never closes it, while in our case you open the device,
read/write, and then close it.

> Can you tell me more about
> it and especially how to reproduce this?

Try "devprobe com0" twice, that might be enough already.  Or use minicom,
leave it, use it again.  It will not start up because the device is gone.

Thanks,
Marcus


-- 
`Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED]
Marcus Brinkmann              GNU    http://www.gnu.org    [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.marcus-brinkmann.de

_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd

Reply via email to