Date: Mon, 9 Apr 2001 16:22:48 -0400 (EDT) From: Mikhail Teterin <mi@misha.privatelabs.com> To: FreeBSD-gnats-submit@freebsd.org Cc: julian@freebsd.org, jkh@freebsd.org Subject: kern/26466: devfs panics Message-ID: <200104092022.f39KMmv16963@misha.privatelabs.com>
next in thread | raw e-mail | index | archive | help
>Number: 26466 >Category: kern >Synopsis: devfs panics >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 09 13:30:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: >Release: FreeBSD 4.2-RC i386 >Organization: Virtual Estates, Inc. >Environment: A dual PIII-1GHz with 1Gb of RAM. >Description: The usual /dev/ad8e and the devfs /devs/rad8e are supposed to be the same. Major number is 116, minor -- 68. The drive is "dangerously allocated". The /dev/ad8e can be used properly and houses my /home partition. However, attempts to use /devs/rad8e, even for something as minor as ``tunefs -n enable /devs/rad8e'' causes an instant panic. May be, someone will address the naming problem in devfs too :) Ultimately, I'd like to be able to mount devfs as /dev, so I can mount the / as read-only. >How-To-Repeat: See description. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104092022.f39KMmv16963>