From owner-freebsd-stable Thu Jan 13 15:55:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 34F8C14DE2 for ; Thu, 13 Jan 2000 15:55:45 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <20000113235331.OQQN28811.mail.rdc3.on.home.com@tristan.net>; Thu, 13 Jan 2000 15:53:31 -0800 Content-Length: 1084 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 13 Jan 2000 18:52:18 -0500 (EST) From: Colin To: Agent Drek Subject: Re: access floppy rw to lock system Cc: freebsd-stable@FreeBSD.ORG, "Chad R. Larson" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Jan-2000 Agent Drek wrote: > On Wed, 12 Jan 2000, Chad R. Larson wrote: > >|As I recall, Agent Drek wrote: >|> >|> I have a repeatable problem on my FreeBSD-3.4Stable workstation. If >|> the floppy disk is physically tabbed as read-only and I mount it rw I >|> can then 'lock' the system up by using vim (to read a text-file on the >|> disk ... less had the same problem). Is this expected behaviour? I >|> did this from the console and could still between the virtual >|> consoles. The only way to get going again was to reboot. After that >|> happened twice I tabbed the disk writable and things were fine. >| >|I'd start by asking, "Why would you do that?" There are, oddly enough, occasionally reaons for things like floppies. That one could slip, unnoticed, into the drive write-protected...see where this is going? This is where I get concerned. Failure writing to a floppy shouldn't hang the system. That it does would imply a problem with the driver at the very least. Or am I failing to trip on the blatantly obvious here? cheers, Colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message