From owner-freebsd-current Mon Feb 12 13:30:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (mail.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id B9BBD37B491; Mon, 12 Feb 2001 13:30:29 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f1CLUBO30791; Mon, 12 Feb 2001 14:30:14 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200102122130.f1CLUBO30791@aslan.scsiguy.com> To: Tony Finch Cc: non@ever.sanda.gr.jp, current@FreeBSD.ORG, trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT In-Reply-To: Your message of "Mon, 12 Feb 2001 21:25:43 GMT." <20010212212543.H35416@hand.dotat.at> Date: Mon, 12 Feb 2001 14:30:10 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >"Justin T. Gibbs" wrote: >> >>It is not necessarily sufficient since the media may be changed after >>open on certain types of devices that don't have a media lock. > >But don't you risk a panic if you do that? By pulling the media out and flipping off the hardware write protect? Even pulling out the media for a valid filesystem shouldn't panic. All I/O to that volume should fail and your system may become next to useless, but the system shouldn't panic. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message