Re: Driver module access to filesystem

Oliver Xymoron (
Thu, 3 Apr 1997 13:09:48 -0600 (CST)

On Thu, 3 Apr 1997, Theodore Y. Ts'o wrote:

> Date: Thu, 03 Apr 1997 04:52:21 -0600
> From: Rick Richardson <>
> The ioctl is the traditional way of doing this. The daemon does have
> to be running all the time in many cases such as the Digi C/X
> products where the concentrators are remote and could be power cycled
> by accident. The driver has to be prepared to give the box a
> firmware download at any time.
> Err... yeah, I guess that's a good reason to have a driver do it. I
> still think in general it's a bad idea, but yes, there are times when it
> is the best way to go about things.

Another possibility is to use a facility like kerneld to call a userspace
program when a certain hook is hit. You can have a single well defined
facility to trigger and not need to build any paths into the driver.

 "Love the dolphins," she advised him. "Write by W.A.S.T.E.."