From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3e1162e60603301158w49b3620el9464387b4aa32287@mail.gmail.com>
Date: Thu, 30 Mar 2006 11:58:18 -0800
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] new compilers
In-Reply-To: <7359f0490603301129x786756e8n20b6b17d8a4cb9fb@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <3e1162e60603301115n238a39abka1e01d3dd2fd6de0@mail.gmail.com>
	<34f4aaa16338144f1f76f071652aac8d@terzarima.net>
	<7359f0490603301129x786756e8n20b6b17d8a4cb9fb@mail.gmail.com>
Topicbox-Message-UUID: 281740a6-ead1-11e9-9d60-3106f5b1d025

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