From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: generating a Linux WWN? Date: Wed, 03 Oct 2007 01:25:29 -0400 Message-ID: <470327C9.9060103@garzik.org> References: <682234.70713.qm@web31815.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:44217 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751316AbXJCFZd (ORCPT ); Wed, 3 Oct 2007 01:25:33 -0400 In-Reply-To: <682234.70713.qm@web31815.mail.mud.yahoo.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: ltuikov@yahoo.com Cc: Michael Reed , James.Smart@Emulex.Com, linux-scsi Luben Tuikov wrote: > --- Jeff Garzik wrote: >> Luben Tuikov wrote: >>> --- Jeff Garzik 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. Jeff