From: Matthew Wilcox <matthew@wil.cx>
To: Douglas Gilbert <dougg@torque.net>
Cc: Bodo Eggert <7eggert@gmx.de>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Bad escriptions in Kconfig
Date: Mon, 31 Dec 2007 08:47:31 -0700 [thread overview]
Message-ID: <20071231154731.GY11638@parisc-linux.org> (raw)
In-Reply-To: <477907DB.8030406@torque.net>
On Mon, Dec 31, 2007 at 10:16:43AM -0500, Douglas Gilbert wrote:
> Bodo Eggert wrote:
> > ---
> > SCSI target support (SCSI_TGT) [N/m/y/?] (NEW) ?
> >
> > If you want to use SCSI target mode drivers enable this option.
> > If you choose M, the module will be called scsi_tgt.
> > ---
> >
> > What TF is a SCSI target mode, what is a target mode driver?
>
> Heard of google :-)
>
> For explanations of SCSI (and other storage) terminology
> reference could be made to SAM-3 or SAM-4 drafts (because
> the real standards cost money) at www.t10.org .
>
> Perhaps many other subsections in the kernel could have
> similar references.
I think that's an appalling idea. Someone's trying to configure their
kernel, not research hundreds of new ideas on the internet. Here's a
better description:
help
The SCSI target code allows your computer to appear as a SCSI
device. This is useful in a SAN or NAS environment where you
want other computers to be able to treat this computer as a disc.
To compile this driver as a module, choose M here: the module
will be called scsi_tgt.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2007-12-31 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 12:26 Bad escriptions in Kconfig Bodo Eggert
2007-12-31 15:16 ` Douglas Gilbert
2007-12-31 15:47 ` Matthew Wilcox [this message]
2007-12-31 16:34 ` Douglas Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071231154731.GY11638@parisc-linux.org \
--to=matthew@wil.cx \
--cc=7eggert@gmx.de \
--cc=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).