public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Check dependencies for modules "dm-snapshot" and "sd_mod" in kernel 2.6.23.1
Date: Sun, 28 Oct 2007 19:51:37 +0100	[thread overview]
Message-ID: <4724DA39.4020601@web.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0710281815020.30465@fbirervta.pbzchgretzou.qr>

> If you really have to roll your own kernel (often this is not the case-YMMV),
> I suggest you enable dm-snapshot and sd_mod.

I intentionally omitted the configuration option "DM_SNAPSHOT" because it is marked as
"EXPERIMENTAL".
Snapshot target:
"Allow volume managers to take writable snapshots of a device."

I intentionally checked the option "BLK_DEV_SD". I do not want to build it as a module.
SCSI disk support:
"If you want to use SCSI hard disks, Fibre Channel disks,
Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
USB storage or the SCSI or parallel port version of
the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
the Disk-HOWTO and the Multi-Disk-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
CD-ROMs.

To compile this driver as a module, choose M here and read
<file:Documentation/scsi/scsi.txt>.
The module will be called sd_mod.

Do not compile this driver as a module if your root file system
(the one containing the directory /) is located on a SCSI disk.
In this case, do not compile the driver for your SCSI host adapter
(below) as a module either."


Do I expect more from the dependency management than it is provided at the moment?

Regards,
Markus


      reply	other threads:[~2007-10-28 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-28 15:52 Check dependencies for modules "dm-snapshot" and "sd_mod" in kernel 2.6.23.1 Markus Elfring
2007-10-28 16:02 ` Jan Engelhardt
2007-10-28 17:05   ` Markus Elfring
2007-10-28 17:15     ` Jan Engelhardt
2007-10-28 18:51       ` Markus Elfring [this message]

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=4724DA39.4020601@web.de \
    --to=markus.elfring@web.de \
    --cc=linux-kernel@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