Date: Sun, 21 Nov 1999 15:20:02 -0800 (PST) From: "Kenneth D. Merry" <ken@kdm.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/15025: chio appears to ignore ACCESS field Message-ID: <199911212320.PAA31022@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/15025; it has been noted by GNATS. From: "Kenneth D. Merry" <ken@kdm.org> To: mjacob@feral.com Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/15025: chio appears to ignore ACCESS field Date: Sun, 21 Nov 1999 16:17:49 -0700 (MST) Matthew Jacob wrote... > FreeBSD frobzit.feral.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Nov 21 11:06:48 PST 1999 mjacob@quarm.feral.com:/freebsd/FreeBSD-current/sys/compile/FROBZIT i386 > > >Description: > > Did a chio status on an Exabyte 210: > > frobzit.feral.com > chio status > picker 0: > slot 0: <ACCESS> > slot 1: <ACCESS,EXCEPT,FULL> > slot 2: <ACCESS,EXCEPT,FULL> > slot 3: <ACCESS,EXCEPT,FULL> > slot 4: <ACCESS,EXCEPT,FULL> > slot 5: <ACCESS,EXCEPT,FULL> > slot 6: <ACCESS> > slot 7: <ACCESS> > slot 8: <ACCESS> > slot 9: <ACCESS> > slot 10: <ACCESS> > drive 0: > drive 1: <EXCEPT,FULL> > > immediately followed by a move: > > frobzit.feral.com > chio move drive 1 slot 0 > > I believe chio *should* have said: "You can't do this because the source > element is not accessible". So what *did* happen? You only say what you think should have happened. I think it's probably better to do state checking in the driver than in chio, since the driver has a more persistent view of things. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911212320.PAA31022>