linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgscan won't recognize my VG
Date: Tue, 20 Mar 2001 13:31:11 -0600	[thread overview]
Message-ID: <20010320133111.C14965@sistina.com> (raw)
In-Reply-To: <20010320202353.A1300@dardhal.mired.net>; from jdomingo@internautas.org on Tue, Mar 20, 2001 at 08:23:53PM +0000

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

On Tue, Mar 20, 2001 at 08:23:53PM +0000, Jos? Luis Domingo L?pez wrote:
> On Tuesday, 20 March 2001, at 19:52:37 +0100,
> David Vidal Rodriguez wrote:
> 
> > OK, I have compiled the beta6 tools.
> > 
> > 1) How do I know if the clean linus-2.4.0 kernel has a beta2 lvm module?
> > 
> Do a "dmesg" once the LVM code is in memory. LVM version should be there.

Or 'head -1 /proc/lvm/global' - I always forget that's there.

-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-379-3951
1313 5th St SE, Suite 111              Fax:    612-379-3952
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
Carpe Aptenodytes! (Seize the Penguins!)
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2001-03-20 19:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-19 20:13 [linux-lvm] vgscan won't recognize my VG David Vidal Rodriguez
2001-03-19 20:37 ` Andreas Dilger
2001-03-20 18:52   ` David Vidal Rodriguez
2001-03-20 19:17     ` AJ Lewis
2001-03-20 19:25     ` Andreas Dilger
2001-03-20 19:35       ` David Vidal Rodriguez
2001-03-20 20:00       ` David Vidal Rodriguez
2001-03-20 20:21         ` Andreas Dilger
2001-03-20 20:36           ` David Vidal Rodriguez
2001-03-21  0:29             ` Kirth
2001-03-21 18:30               ` David Vidal Rodriguez
2001-03-21 19:17                 ` Andreas Dilger
2001-03-23 14:55                   ` David Vidal Rodriguez
2001-03-23 22:36                     ` Andreas Dilger
2001-03-20 20:57           ` [linux-lvm] LVM and fault tolerance Anders Widman
2001-03-21 17:33             ` Lars Kellogg-Stedman
2001-03-22 23:59               ` Anders Widman
     [not found]                 ` <0103262137020G.01456@lyta>
2001-03-27 21:48                   ` Anders Widman
2001-03-27 21:56                     ` Ragnar Kjørstad
2001-03-27 22:29                       ` Anders Widman
2001-03-27 22:45                         ` Ragnar Kjørstad
2001-03-28  6:43                         ` Russell Coker
2001-03-31 17:17                           ` Anders Widman
2001-03-20 20:23     ` [linux-lvm] vgscan won't recognize my VG José Luis Domingo López
2001-03-20 19:31       ` AJ Lewis [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=20010320133111.C14965@sistina.com \
    --to=lewis@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;
as well as URLs for NNTP newsgroup(s).