Date: Fri, 4 May 2007 16:51:05 +1000 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Scott Long <scottl@samsco.org> Cc: stable@freebsd.org, "Sean C. Farley" <sean-freebsd@farley.org>, Ulrich Spoerlein <uspoerlein@gmail.com> Subject: Re: acd and iostat [was Re: FreeBSD vs Region Code DVDs] Message-ID: <Pine.BSF.3.96.1070504164043.16876D-100000@gaia.nimnet.asn.au> In-Reply-To: <463AD28B.9070709@samsco.org>
index | next in thread | previous in thread | raw e-mail
On Fri, 4 May 2007, Scott Long wrote:
> Ian Smith wrote:
> > On Thu, 3 May 2007, Scott Long wrote:
> >
> > > Ulrich Spoerlein wrote:
> > [..]
> > > > PS: why is iostat(1) not working for acd(4) devices?
> > >
> > > Because acd doesn't make use of the standard kernel facilities that make
> > > iostat work. It's a deliberate choice by the driver author.
> >
> > Same for systat -vm of course. I guess this was a regression, as acdX
> > used to show up fine in 4.X in {sys,io}stat, whether or not also showing
> > cdX (with atapicam). I often used to watch it while testing burned CDs.
> >
> > Was that because of an API change to said kernel facilities, perhaps?
> >
> > Cheers, Ian
> >
>
> No, the devstat kernel API hasn't changed in since it was introduced
> nearly 10 years ago.
Thanks. The only other reason I can see for removing acdX from these
stats would be to save on some admittedly precious screen real estate.
Cheers, Ian
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.1070504164043.16876D-100000>