From owner-freebsd-current Mon Aug 28 1:22:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 8248637B422 for ; Mon, 28 Aug 2000 01:22:35 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7S8MWN04757; Mon, 28 Aug 2000 10:22:32 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: alpha devfs feedback In-Reply-To: Your message of "Mon, 28 Aug 2000 00:55:18 PDT." Date: Mon, 28 Aug 2000 10:22:32 +0200 Message-ID: <4755.967450952@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: >> >> What names do you usually access your disks by ? Just da0a etc ? > >da0{a,b,c,d} and so on.. >> >> You should be able to find those as well with the clone stuff... > >Nope. Weren't there. > >I booted up once. I had 3 disks- none with a FreeBSD label. The >contents of /dev for da disks was /dev/da{0,1,2}[c]. > >So, I did the '-Brw da0 auto' and disklabel -e trick to add >a da0a to da0. disklabel happily saw da0a after this. Nothing >in /dev. Okay- so this kind of rescan doesn't work yet. > >So, I reboot. The contents of dev still are /dev/da{0,1,2}[c]. I mostly >was raising this to see if someone else has tried alpha in this regard. >If not- I can help debug this and fix it, but next week. Hmm, can you send me a ls -l /dev from a !devfs alpha so I can see what it looks like ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message