From owner-freebsd-questions@FreeBSD.ORG Sun Dec 4 22:39:57 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47A4216A41F for ; Sun, 4 Dec 2005 22:39:57 +0000 (GMT) (envelope-from msoulier@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43DD143D6E for ; Sun, 4 Dec 2005 22:39:46 +0000 (GMT) (envelope-from msoulier@gmail.com) Received: by nproxy.gmail.com with SMTP id b2so439190nfe for ; Sun, 04 Dec 2005 14:39:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Sz2LmE3ja+pwoE4CfrDr8EzWS6k+Ll+L4fKpypmVWwnds2mz6UKKP6wckJwrR1QOfbpsnVY+DvPcRJX1vBEOHL2m2Wwn4IhewfZnzkk0P+apVQXYQU7oSYb3vM7SFeBfk/cUXgbujjlLTh5S7RS8uv1E5/6hYrnkwxqKxNvELkI= Received: by 10.48.12.20 with SMTP id 20mr1606361nfl; Sun, 04 Dec 2005 14:32:42 -0800 (PST) Received: by 10.48.225.9 with HTTP; Sun, 4 Dec 2005 14:32:42 -0800 (PST) Message-ID: Date: Sun, 4 Dec 2005 17:32:42 -0500 From: "Michael P. Soulier" Sender: msoulier@gmail.com To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: kernel panic because I pulled a floppy? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 22:39:57 -0000 Hey all, I'm reading "BSD Hacks" by Dru Lavigne, published by O'Reilly. In the section on managing floppies, it mentions that if you pull a floppy without umounting it first, the next time to try to access the filesystem, you'll get a kernel panic. Is this true? If so, it would be the very first Unix that I've seen crash from this kind of user-mistake. Thanks, Mike -- Michael P. Soulier