From: Rich Turner <rich@storix.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] determing lvm support
Date: Fri Dec 19 18:49:01 2003 [thread overview]
Message-ID: <1071881237.1464.14.camel@rich> (raw)
is there any fool proof way of knowing whether or not a system has lvm
support?
right now i determine it this way:
lvm1:
look for "vgcreate" command and
look for "lvm" in /proc/devices or
look for "lvm-mod" in /lib/modules/[release]/kernel/drivers/md/*
lvm2:
look for "vgcreate" command and
look for "device-mapper" in /proc/devices or
look for "dm-mod" in /lib/modules/[release]/kernel/drivers/md/*
i think i am fairly certain with lvm1, but with lvm2 i am not sure if i
have device mapper support and a lvm command that is enough.
any ideas?
rich turner
next reply other threads:[~2003-12-19 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 18:49 Rich Turner [this message]
2003-12-20 6:31 ` [linux-lvm] determing lvm support 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
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=1071881237.1464.14.camel@rich \
--to=rich@storix.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