--- Jeff Garzik <jeff@xxxxxxxxxx> wrote: > Luben Tuikov wrote: > > --- Jeff Garzik <jeff@xxxxxxxxxx> wrote: > >> Luben Tuikov wrote: > >>> --- Jeff Garzik <jeff@xxxxxxxxxx> wrote: > >>>> Luben Tuikov wrote: > >>>>> This still does not justify "let's generate it in the kernel". > >>>> Once an admin specifies to use an alternate WWN provision, the method > >>>> used to obtain that WWN is an implementation detail and irrelevant. > >>> But you're arguing that the kernel should generate it to "help out" > >>> SAS drivers with HW that has had it's MS/NVRAM erased or corrupted. > >>> > >>> The kernel has no business generating SAS WWN. > >> Perhaps you missed the English text "once an admin specifies" in the > >> quoted email. > > > > Was your "once an admin specifies" reply to my email > > supposed to be "Oh, I see, generating a SAS WWN in the kernel > > is not that good an idea after all. I'll implement it > > as a kernel/module option." ? > > The admin will have the option to auto-generate a WWN, should they so > desire. What does that mean? "auto-generate"? By whom? What if they don't "auto-generate" (whatever that means)? - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
