From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 00:59:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 563B537B401 for ; Tue, 8 Jul 2003 00:59:17 -0700 (PDT) Received: from phys9911.phys.tue.nl (PHYS9911.phys.tue.nl [131.155.108.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 402B143FCB for ; Tue, 8 Jul 2003 00:59:16 -0700 (PDT) (envelope-from karelj@phys9911.phys.tue.nl) Received: from phys9911.phys.tue.nl (localhost [127.0.0.1]) by phys9911.phys.tue.nl (8.12.9/8.12.9) with ESMTP id h687xJJR058526; Tue, 8 Jul 2003 09:59:19 +0200 (CEST) (envelope-from karelj@phys9911.phys.tue.nl) Received: (from karelj@localhost) by phys9911.phys.tue.nl (8.12.9/8.12.9/Submit) id h687xIvJ058525; Tue, 8 Jul 2003 09:59:18 +0200 (CEST) Date: Tue, 8 Jul 2003 09:59:18 +0200 From: "Karel J. Bosschaart" To: walt Message-ID: <20030708075918.GB58019@phys9911.phys.tue.nl> References: <3F09AAAF.8000508@myrealbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F09AAAF.8000508@myrealbox.com> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: how to create device nodes when devfs doesn't do it? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2003 07:59:17 -0000 On Mon, Jul 07, 2003 at 10:15:27AM -0700, walt wrote: > Karel J. Bosschaart wrote: > >Hi, > > > >After googling and searching in the mailing list archive I still can't > >figure out how to make device nodes in -current when devfs doesn't do this > >automatically. I have an external USB-drive (external 3.5" case with > >leftover > >1.6 GB HD) from which I want to mount /dev/da0s4h. It works fine in > >-stable, after MAKEDEV'ing the node, but on -current I only get da0s4. > > > Have you tried mounting da0s4h? It may show up in /dev after mounting it. > That's how I started, but I'm getting phys9911# mount /dev/da0s4h /mnt/test/ mount: /dev/da0s4h: No such file or directory > >disklabel: partition c doesn't start at 0! > >disklabel: partition c doesn't cover the whole unit! > >disklabel: An incorrect partition c may cause problems for standard system > >utilities > > My experience is that these warnings can be ignored as long as the drive > will mount. That's my experience as well. The partition mounts fine in -stable. Karel.