From owner-freebsd-hackers  Mon May 12 20:35:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id UAA25775
          for hackers-outgoing; Mon, 12 May 1997 20:35:29 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25769
          for <hackers@freebsd.org>; Mon, 12 May 1997 20:35:25 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id VAA19271; Mon, 12 May 1997 21:35:20 -0600 (MDT)
Date: Mon, 12 May 1997 21:35:20 -0600 (MDT)
Message-Id: <199705130335.VAA19271@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Brian N. Handy" <handy@sag.space.lockheed.com>
Cc: hackers@freebsd.org
Subject: Re: newfs hangs my system?
In-Reply-To: <Pine.OSF.3.96.970512173551.12407A-100000@sag.space.lockheed.com>
References: <Pine.OSF.3.96.970512164812.12315A-100000@sag.space.lockheed.com>
	<Pine.OSF.3.96.970512173551.12407A-100000@sag.space.lockheed.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> And I've figured out my problem.  I was doing
> 
> 	newfs [options] /dev/ccd0c
> 
> And I shoulda been doing
> 
> 	newfs [options] /dev/rccd0c
> 
> Why was I doing this?  This problem wasn't unique to my CCD, I was able to
> crash my machine without this.  No, the problem is in the man page for
> newfs.  I quoth from the examples:
> 
> EXAMPLES
>            mount_mfs -s=20480 -o nosuid,nodev /dev/sd0b /tmp
> 
> 
> --> shouldn't this be /dev/rsd0b?

Not for the mount command.  You 'mount' block devices, but you create
(newfs) using the character device.

Basically, it's just unix magic. :) :) :)


Nate