Date: Mon, 14 Jan 2008 22:40:46 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Alfred Perlstein <alfred@freebsd.org> Cc: gnn@freebsd.org, Andriy Gapon <avg@icyb.net.ua>, freebsd-arch@freebsd.org Subject: Re: cdcontrol purpose Message-ID: <478BD6DE.1070407@FreeBSD.org> In-Reply-To: <20080114213347.GU99258@elvis.mu.org> References: <478B3EE0.8040908@icyb.net.ua> <7iir1wtp91.wl%gnn@neville-neil.com> <20080114160617.GN99258@elvis.mu.org> <478B953F.1070209@icyb.net.ua> <20080114170624.GR99258@elvis.mu.org> <478B9A2C.4080206@icyb.net.ua> <20080114213347.GU99258@elvis.mu.org>
index | next in thread | previous in thread | raw e-mail
Alfred Perlstein wrote: > * Andriy Gapon <avg@icyb.net.ua> [080114 09:18] wrote: >> on 14/01/2008 19:06 Alfred Perlstein said the following: >>> * Andriy Gapon <avg@icyb.net.ua> [080114 08:57] wrote: >>>> So I hope my question would be clearer now: should cdcontrol be allowed >>>> to override "prevent" issued by mount/open(2) and eject a disk in use ? >>>> Or should it simply fail in the same way that the physical button is >>>> disabled? >>> It should not. >> Sorry, I am not completely sure which question you answered with that, >> damn alternative questions :-) >> > > Regarding: > >>>> should cdcontrol be allowed >>>> to override "prevent" issued by mount/open(2) and eject a disk in use ? > > It should not do this. It should NOT eject a disk in use. > > Furthermore: > >>> If in that situation the tool does not emit a diagnostic that's >>> useful then it could be augmented to do so. > > > When I tried this last it indeed did not eject a mounted CDROM. I wonder if Andriy's hardware is not responding to the "lock media" command or something. Can anyone else confirm this behaviour? Krishelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?478BD6DE.1070407>