From owner-freebsd-arch Tue Jul 25 14:43:19 2000 Delivered-To: freebsd-arch@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DECBA37BA8D for ; Tue, 25 Jul 2000 14:43:11 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA31261; Tue, 25 Jul 2000 14:42:56 -0700 Date: Tue, 25 Jul 2000 14:42:16 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jack Rusher Cc: Poul-Henning Kamp , freebsd-arch@FreeBSD.ORG Subject: Re: How much do we need the all-singing, all-dancing devfs? In-Reply-To: <397E0855.CEC23FF@integratus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > # disklabel /dev/HW:BLABLA__2983942394 > /dev/null > > # ls /dev/HW* > > /dev/HW:BLABLA__2983942394 > > What is the suggested interface for listing the available (but not > currently in use) devices? In the normal /dev way of looking at things, > you can get a listing of device names from the directory namespace. > Where does that info live in this scheme? ad hoc, even as it is now- 'camcontrol devlist' and parsing dmesg output. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message