[29] in linux-scsi channel archive
Re: Probing luns > 0 (fwd)
daemon@ATHENA.MIT.EDU (Andrew Walker)
Wed Jan 25 11:21:14 1995
From: andy@eng.kvaerner.no (Andrew Walker)
To: chip@cybernetics.net (Chip Salzenberg)
Date: Wed, 25 Jan 1995 16:06:27 +0100 (MET)
Cc: andy@eng.kvaerner.no, eowmob@exp-math.uni-essen.de,
linux-scsi@vger.rutgers.edu
In-Reply-To: <9501251427.AA22297@cybernetics.net> from "Chip Salzenberg" at Jan 25, 95 09:27:22 am
Chip Salzenburg wrote:
>
> According to Andrew Walker:
> > Anybody see a way around this without building a list of devices
> > to be probed for multiple LUNs?
>
> Sure:
>
> scsi_multi_luns=PIONEER,KLUDGE-CO
>
> Devices that respond with either of the given strings in their
> manufacturer's description qualify for multi-lun probes.
Yeah, this may be the way we have to go. I thought for a minute that
it might be tricky for an average user to find the appropriate strings
if everything hangs on boot, but that won't happen 'cos we're now going
to the *safe* option where we don't probe multiple LUNs unless told to.
Well, time to go home here in Norway. When us europeans come in tomorrow
America will have had its say. If we're gonna go with Chip's suggestion
then I suggest that the SCSI and/or Hardware HOWTOs should contain a list
of known devices that need this, with the appropriate strings.
BTW: is there a practical limit on the size/number of command line args.
-Andy
--
Andy Walker Kvaerner Engineering a.s.
Andrew.Walker@eng.kvaerner.no P.O. Box 222, N-1324 Lysaker, Norway
......if the answer isn't violence, neither is it silence......
