From owner-freebsd-hackers Thu Feb 8 21:58:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id C7E8637B491 for ; Thu, 8 Feb 2001 21:58:16 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f195wEW01613; Thu, 8 Feb 2001 22:58:14 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102090558.f195wEW01613@harmony.village.org> To: supenguin@bigfoot.com Subject: Re: mount checking for read-only media Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 09 Feb 2001 00:03:06 EST." <3A837A0A.DAB3520A@columbus.rr.com> References: <3A837A0A.DAB3520A@columbus.rr.com> Date: Thu, 08 Feb 2001 22:58:14 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A837A0A.DAB3520A@columbus.rr.com> Kenny Drobnack writes: : Is some system call to check the hardware to see if its physically : writable? I figure there is. I want to start hacking at the kernel a : bit, and it seems like something simple (comparitively) would be a good : place to start. Up there on my wish list is getting a journaling : filesystem ported to FreeBSD. This is a driver bug. The da driver, which deals with disks, doesn't check to see if the media is writable or not before allowing r/w mounts. You could short circuit the panic by fixing this. Fixing the panic might be harder... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message