All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael J. Declerck" <declerck@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Another strange setup by a newbie, but strange oops  resulted while trying vgextend/vgmerge!
Date: Mon, 08 Jan 2001 11:24:41 -0800	[thread overview]
Message-ID: <20010108192441.AB70FE0B7@wraith> (raw)
In-Reply-To: Message from Daniel Mitzlaff <hackbyte@gmx.de>  of "Mon, 08 Jan 2001 17:43:54 GMT." <20010108.17435488@dmitzlaff2.botschendv.de>

hackbyte@gmx.de said:
> *smile* .... ok ... But, what about Penguins which have its own
> disability's and can't do such a long jorney to reach K-2.4.0 islands?
> Are they all so outdated, that peoples from K-2.4.0 doesn't have to
> look for them or in any other way care about them?

> You don't remember your own basics?;)

I believe that what I said is that those penguins should wait for 
guidance and help from the dolphin pods when the waters were safe.
I didn't say anything about leaving them behind if they wanted to
make the journey then.

As stated in an earlier post Sistina never said the "crossing conditions
with regards to LVM and K-2.4.0 were safe".  These are still uncharted
waters that we are working quickly to make safe.

---
Michael Declerck, declerck@sistina.com   +1.510.823.7991

  reply	other threads:[~2001-01-08 19:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <hackbyte@gmx.de>
2001-01-03 13:13 ` [linux-lvm] Another strange setup by a newbie, but strange oops resulted while trying vgextend/vgmerge! Daniel Mitzlaff
2001-01-03 13:55   ` Joe Thornber
2001-01-03 18:24   ` lewis
2001-01-08 16:05   ` Michael J. Declerck
2001-01-08 17:43     ` Daniel Mitzlaff
2001-01-08 19:24       ` Michael J. Declerck [this message]
2001-01-08 21:21         ` Daniel Mitzlaff
2001-01-03 17:44 Daniel Mitzlaff

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=20010108192441.AB70FE0B7@wraith \
    --to=declerck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.