Re: looking for error codes

2011-04-05 Thread Andriy Gapon
on 01/04/2011 17:29 Andriy Gapon said the following: > > 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 periphe

Re: looking for error codes

2011-04-03 Thread Warner Losh
On Apr 3, 2011, at 12:06 PM, Pawel Jakub Dawidek wrote: > On Fri, Apr 01, 2011 at 06:18:54PM +0300, Andriy Gapon wrote: >> 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 a

Re: looking for error codes

2011-04-03 Thread Pawel Jakub Dawidek
On Fri, Apr 01, 2011 at 06:18:54PM +0300, Andriy Gapon wrote: > 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 in

RE: looking for error codes

2011-04-02 Thread Andrew Duane
er-freebsd-hack...@freebsd.org] On Behalf Of Warner Losh [i...@bsdimp.com] Sent: Saturday, April 02, 2011 11:54 AM To: per...@pluto.rain.com Cc: freebsd-hackers@freebsd.org; m.e.sanlit...@gmail.com; a...@freebsd.org; freebsd-a...@freebsd.org Subject: Re: looking for error codes On Apr 2, 2011,

Re: looking for error codes

2011-04-02 Thread Warner Losh
On Apr 2, 2011, at 1:50 AM, per...@pluto.rain.com wrote: > >> With respect to my knowledge , no one of the operating systems >> has a facility to separate read-only and modifiable parts ... > > SunOS 4 had a partial solution to this, by rearranging the FS layout > so that /usr could be mounted r

Re: looking for error codes

2011-04-02 Thread Paul Schenkeveld
On Sat, Apr 02, 2011 at 12:50:29AM -0700, per...@pluto.rain.com wrote: > Mehmet Erol Sanliturk wrote: > > > For a long time I am thinking to obtain a physically ( not only > > software ) based [read-only] FreeBSD edition by re-arranging some > > parts of it , but I do not know how to do it ... >

Re: looking for error codes

2011-04-02 Thread perryh
Mehmet Erol Sanliturk wrote: > For a long time I am thinking to obtain a physically ( not only > software ) based [read-only] FreeBSD edition by re-arranging some > parts of it , but I do not know how to do it ... > After some years , MFM hard disks abandoned in favor of IDE > ( Integrated Drive

Re: looking for error codes

2011-04-01 Thread Mehmet Erol Sanliturk
1 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

RE: looking for error codes

2011-04-01 Thread Andrew Duane
y Gapon [a...@freebsd.org] Sent: Friday, April 01, 2011 11:18 AM To: Andrew Duane Cc: Warner Losh; FreeBSD Hackers; FreeBSD Arch Subject: Re: looking for error codes on 01/04/2011 18:04 Andrew Duane said the following: > AFAIK, FreeBSD does not really detect read-only media. This was something I

Re: looking for error codes

2011-04-01 Thread Andriy Gapon
__ > From: owner-freebsd-hack...@freebsd.org [owner-freebsd-hack...@freebsd.org] > On Behalf Of Warner Losh [i...@bsdimp.com] > Sent: Friday, April 01, 2011 10:51 AM > To: Andriy Gapon > Cc: FreeBSD Hackers; FreeBSD Arch > Subject: Re: looking for error codes >

RE: looking for error codes

2011-04-01 Thread Andrew Duane
on 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 t

Re: looking for error codes

2011-04-01 Thread Warner Losh
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