[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ioctl's handling with a trivfs translator

From: Marcus Brinkmann
Subject: Re: ioctl's handling with a trivfs translator
Date: Thu, 14 Mar 2002 17:47:39 +0100
User-agent: Mutt/1.3.27i

On Thu, Mar 14, 2002 at 05:41:04PM +0100, Ludovic Court├Ęs wrote:
> > One of the reason to not have a ioctl call is that not all traditional UNIX
> > ioctls can be dealt with by simple rpcs, it needs support in the user task. 
> > Another is cleanliness:  ioctl is a horrible hack to avoid designing proper
> > interfaces, or maybe to save syscall numbers.  In the Hurd, we have a proper
> > IPC system, so we don't really need ioctls.  But we need them anyway for
> > compatibility, so we have them, but then a ioctl id corresponds to an RPC,
> > or to a special case in the C library.
> So, if I understand well, libstore is the user interface that makes it 
> possible
> for a user program to communicate with a storeio server, right?

No, libstore is the library that provides a store abstraction to, for
example, servers.  storeio is one server using libstore.  But I am not sure
what this has to do with ioctl's :)  A store is basically one or multiple
runs of blocks.  The blocks can be collected from different sub-stores, like
devices, and manipulated upfront, like gunzip'ed.

Play with the storeinfo program a bit to get the feel of its power.

> I've been looking for the source code of the mouse and kbd translators in the
> hurd source tree but I haven't been able to find it. Any pointers? Is it 
> related
> to streamio?

mouse and kbd are only in the Debian package.  We want them to be part of a
more general scheme, the channel abstraction, which is to character devices
what a store is to block devices (see the analogy?).  Nobody has written
libchannel yet, though.


`Rhubarb is no Egyptian god.' Debian
Marcus Brinkmann              GNU

reply via email to

[Prev in Thread] Current Thread [Next in Thread]