Subject: EBUSY error on psuedo-device open
To: None <firstname.lastname@example.org>
From: Emmanuel Dreyfus <email@example.com>
Date: 10/27/2001 15:41:39
I've been stuck for a while with clockctl developement because of a
EBUSY error that occurs when I attempt to open the pseudodriver for
writing. There is no problem with opening for reading, but opening for
writing lead to EBUSY. The open method of the driver is never called.
Were there some change somewhere that could explain this? It started two
weeks ago when I catched up current to finish clockctl developement.