Re: rfc: fcntl() error reporting

To: "Bill Stouder-Studenmund" <wrstuden%netbsd.org@localhost>
Subject: Re: rfc: fcntl() error reporting
From: "Andy Shevchenko" <andy.shevchenko%gmail.com@localhost>
Date: Mon, 25 Aug 2008 16:30:32 +0300

On Fri, Aug 22, 2008 at 9:38 PM, Bill Stouder-Studenmund
<wrstuden%netbsd.org@localhost> wrote:
> You'll have more luck getting the results you want testing operation codes
> 2147483647 and below.
Yep, the FS related stuff is bypass if the most significant bit is set.

Thanks all for discussion. Indeed, the fcntl() standard description
allows to manipulate with command argument, but doesn't describe
anything about custom error signaling.

-- 
With Best Regards,
Andy Shevchenko

References:
- rfc: fcntl() error reporting
  - From: Andy Shevchenko
- Re: rfc: fcntl() error reporting
  - From: David Holland
- Re: rfc: fcntl() error reporting
  - From: Andy Shevchenko
- Re: rfc: fcntl() error reporting
  - From: Bill Stouder-Studenmund

Prev by Date: Re: sysmon_envsys(9)
Next by Date: Device driver writing ideas for a beginner
Previous by Thread: Re: rfc: fcntl() error reporting
Next by Thread: bwi(4): Broadcom AirForce BCM43xx IEEE 802.11b/g wifi driver
Indexes:

Home | Main Index | Thread Index | Old Index