From: Alasdair G Kergon <agk@uk.sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] determing lvm support
Date: Mon Dec 22 18:08:01 2003 [thread overview]
Message-ID: <20031223000655.N21022@uk.sistina.com> (raw)
In-Reply-To: <1072109013.1353.11.camel@rich>; from rich@storix.com on Mon, Dec 22, 2003 at 08:03:34AM -0800
On Mon, Dec 22, 2003 at 08:03:34AM -0800, Rich Turner wrote:
> > > look for "device-mapper" in /proc/devices or
> > It's better to check for that in /proc/misc, which will tell you whether
> > or not device-mapper support is present in the running kernel.
> why is it better to check in /proc/misc? when device-mapper support is
> loaded, it shows up in both /proc/misc as well as /proc/devices.
You can only guarantee its appearance in /proc/devices while you
have a device active.
Alasdair
--
agk@uk.sistina.com
next prev parent reply other threads:[~2003-12-22 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 18:49 [linux-lvm] determing lvm support Rich Turner
2003-12-20 6:31 ` Alasdair G Kergon
2003-12-20 7:37 ` Luca Berra
2003-12-20 17:32 ` Alasdair G Kergon
2003-12-21 2:09 ` Luca Berra
2003-12-21 10:02 ` Alasdair G Kergon
2003-12-22 10:05 ` Rich Turner
2003-12-22 18:08 ` Alasdair G Kergon [this message]
2003-12-20 12:55 ` Micah Anderson
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=20031223000655.N21022@uk.sistina.com \
--to=agk@uk.sistina.com \
--cc=linux-lvm@sistina.com \
/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