Re: Urgent, Please respond - Re: max_scsi_luns and 2.4.19-pre10.

[Austin Gonyou]

On Tue, 2002-06-25 at 22:47, jw schultz wrote:
...
> I don't have -aa but that is -1.  I would suggest a bit of
> greping.
> 
> I seriously doubt changing it to 16 would cause data
> corruption.  It will either work or not.  If it doesn't you
> will crash on boot/init.
> 

yeah...I hear that. I tried some grepping, but didn't come up with much
since #define MAX_SCSI_LUNS 0xFFFFFFFF; replaced 8, and then it's seems
nothing like the mainline code, so it's much different. 

If Andrea is listening, can you tell us if that's correct or not? Also,
it seems that passing max_scsi_luns=128 or even 10 or something at boot
time does not get parsed by scsi_mod, if CONFIG_SCSI=y. 

Can someone shed some light on that?

> 
> -- 
> ________________________________________________________________
> 	J.W. Schultz            Pegasystems Technologies
> 	email address:		[e-mail]
> 
> 		Remember Cernan and Schmitt
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-- 
Austin Gonyou <[e-mail]>