Date: Thu, 15 Oct 1998 09:55:57 -0600 (MDT) From: "Kenneth D. Merry" <ken@plutotech.com> To: nick.hibma@jrc.it Cc: ckempf@enigami.com, joe@pavilion.net, freebsd-scsi@FreeBSD.ORG Subject: Re: Official way to detect CAM? Message-ID: <199810151555.JAA17897@panzer.plutotech.com> In-Reply-To: <Pine.GSO.3.95q.981015154754.5955Z-100000@elect8> from Nick Hibma at "Oct 15, 98 03:48:58 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Nick Hibma wrote...
>
> Or execute
>
> camcontrol periphlist
>
> and look for '^ch[0-9]:'
>
> Makes it possible to at the same time present a menu if multiple
> changers are present.
Well, that probably won't do what you want. The 'periphlist' function just
prints out the list of peripherals attached to the given device. e.g.:
{roadwarrior:/usr/home/ken:1:0} camcontrol periphlist -n da -u 1
pass1: generation: 4 index: 1 status: MORE
da1: generation: 4 index: 2 status: LAST
{roadwarrior:/usr/home/ken:2:0} camcontrol periphlist
pass0: generation: 4 index: 1 status: MORE
da0: generation: 4 index: 2 status: LAST
You'll probably want to use 'camcontrol devlist' piped through a script to
find all of the changers. (i.e. something like Dan Nelson's script)
Sometime or another it might be nice to add command line pattern matching
code to camcontrol.
Ken
--
Kenneth Merry
ken@plutotech.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810151555.JAA17897>