From owner-freebsd-current Tue Aug 25 10:25:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29321 for freebsd-current-outgoing; Tue, 25 Aug 1998 10:25:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29309 for ; Tue, 25 Aug 1998 10:24:58 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA22385 for ; Tue, 25 Aug 1998 19:28:44 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 25 Aug 1998 19:28:44 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: Panic with DEVFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It was pointed to me that it's very easy to panic -current system running DEVFS on /dev, with / on MFS. The problem manifested itself with picobsd floppy. The following scenario causes panic with "mfs_strategy: bad dev": 1. boot with -c 2. disable at least one device 3. log in 4. cd /dev 5. ls -l What's funny is that when I do 'ls' (without -l) in step 5., everything is ok. My guess is that DEVFS doesn't like these devices which are present in kernel, but are disabled... Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message