From owner-freebsd-stable Wed Jan 12 22: 4:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.monsterbymistake.com (monsterbymistake.com [205.207.163.17]) by hub.freebsd.org (Postfix) with ESMTP id C92E115090 for ; Wed, 12 Jan 2000 22:04:15 -0800 (PST) (envelope-from drek@MonsterByMistake.Com) Received: from bunny.monsterbymistake.com([205.207.163.17]) (2466 bytes) by mail.monsterbymistake.com via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Thu, 13 Jan 2000 01:04:47 -0500 (EST) (Smail-3.2.0.107 1999-Sep-8 #1 built 1999-Sep-11) Date: Thu, 13 Jan 2000 01:04:47 -0500 (EST) From: Agent Drek To: "Chad R. Larson" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: access floppy rw to lock system In-Reply-To: <200001130214.TAA03924@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, Chad R. Larson wrote: |Date: Wed, 12 Jan 2000 19:14:56 -0700 (MST) |From: Chad R. Larson |To: Agent Drek |Cc: freebsd-stable@FreeBSD.ORG |Subject: Re: access floppy rw to lock system | |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?" | |If you make the media read-only at the hardware level, by all means |mount it read-only. | I'm not used to ever using a floppy disk, no need until I got ether- net card and needed info from damn diskette. |If you're just asking why this interesting phenomenon occurs, that's |a different question. I'm not sure if it's an MS-DOS filesystem, |but a UFS mount will want to modify the superblock with the mount |time and mount point. and should hang the ENTIRE system if it can't!?! I'm asking because I used the default way of thinking ... mount /floppy I usually use vim to read big files ... I'm happy to know that this is a way to instantly hang a freebsd server. This felt wrong to me so I thought I would try and get a second opinion. What if the disk was just corrupt .. could the same behaviour happen? was msdosfs (m$-driver disk). One person mailed me off list to say that they too had done this once as well. thanks, =derek Monster By Mistake Inc > 'digital plumber' http://www.interlog.com/~drek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message