looking for error codes

[Andriy Gapon]

on 01/04/2011 18:04 Andrew Duane said the following:
> AFAIK, FreeBSD does not really detect read-only media. This was something I had to add as a small project here at work, and was considering cleaning up to try to get into CURRENT. If there's a real need for it, I could speed that up.
> 

Yes, that's exactly the problem that I am looking at.
So if you have anything to share it will be greatly appreciated at least by me.
But I think many more people could benefit from it (e.g. those having SD/SDHC/etc
cards).
Thanks!

> ________________________________________
> From: owner-freebsd-hackers at freebsd.org [owner-freebsd-hackers at freebsd.org] On Behalf Of Warner Losh [imp at bsdimp.com]
> Sent: Friday, April 01, 2011 10:51 AM
> To: Andriy Gapon
> Cc: FreeBSD Hackers; FreeBSD Arch
> Subject: Re: looking for error codes
> 
> On Apr 1, 2011, at 8:29 AM, Andriy Gapon wrote:
> 
>>
>> I am looking for error codes that would unambiguously signal that a disk drive has
>> readonly or write-protected media and that disk drive has no media at the moment.
>> I foresee these error codes being used mostly between disk peripheral drivers and
>> filesystem drivers.
>>
>> I will appreciate your suggestions.
>>
>> P.S.
>> I see that Linux uses EROFS and ENOMEDIUM for these purposes.
>> I am not sure about EROFS in this role.
>> And we don't have ENOMEDIUM (nor EMEDIUMTYPE).
> 
> Maybe we could add ENOMEDIA for that (spelled however Linux spells it) after EDAVE.

-- 
Andriy Gapon