From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9852b5a4b869d8dfc64fc1e5f98440d0@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 31 Mar 2006 07:27:08 -0600
To: 9fans@cse.psu.edu
Subject: Re: [9fans] new compilers
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 2a33b7e8-ead1-11e9-9d60-3106f5b1d025

ioctl is so 2002.  netlink sockets are all the rage now.

- erik

On Thu Mar 30 13:59:35 CST 2006, leimy2k@gmail.com wrote:
> On 3/30/06, Rob Pike <robpike@gmail.com> wrote:
> > Also, ioctl masks the direction of data motion, while read and
> > write make it was explicit as can be.
> >
> > -rob
> >
>
> It really does seem that ioctl is just a "kitchen sink" for operations
> on resources in a filesystem that people didn't think could be
> addressed as files at the time.
>
> The xattr stuff seems neat on the surface because you effectively get
> a hierarchical namespace directly attached to your device file.  Of
> course, there's really nothing stopping us from doing that with
> directories the Plan 9 way I suppose.
>
> In fact, I often wondered why the eia* stuff kind of differed in
> structure from the sd* stuff.
>
> Any good reason not to do
> eia0/ctl
> eia0/data
> eia0/status
>
> Dave