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 08:05:36 -0800 [thread overview]
Message-ID: <20010108160536.E0910E0B7@wraith> (raw)
In-Reply-To: Message from Daniel Mitzlaff <hackbyte@gmx.de> of "Wed, 03 Jan 2001 13:13:14 GMT." <20010103.13131495@dmitzlaff2.botschendv.de>
A short parable seems to be in order here.
There once was a large penguin rookery located on an island that was
designated as K-2.2.18. The penguin population that lived there was large
and plentiful due to the fact that it provided suitable protection and
sustenance. Due to this the population had grown large and was starting
to look for new territory to occupy. Lo and behold they discovered
a substantially larger island known as K-2.4.0 which had a wealth of
untapped resources that would allow the colony to expand in the future.
Unfortunately, the distance between K-2.2.18 and K-2.4.0 was large and
full of many unknown dangers (not the least of which were large killer
whales looking for tasty penguins to snack on).
Despite this, many of the penguin population decided that the risk and
effort necessary to reach K-2.4.0 was acceptable because of the
opportunities it provided. This divided the penguins into a number of
groups:
o Group #1 was composed of some of the elder penguins, who had made
successful ocean crossings in the past. They traveled together in a flock
so
as to mitigate their danger. They arrived successfully with only minor
injuries.
o Group #2 was formed from mature and adolescent penguins. When they
ventured forth they either swam in groups for protection or as individuals
who counted on their own strengths (speed and cunning) to insure a
successful journey. Despite this they still encountered dangerous schools
of jellyfish that inflicted damage upon some of them. These penguins
required some time to recuperate after completing their journey
Group #3 was made up of fledging penguins, who having seen others make the
journey, decided they could do so as well. They launched from shore with
a plan that consisted of nothing more than a dream of Island K-2.4.0 for
they were unexperienced in such endeavors. Many of them became lost
during the journey or were eaten by killer whales hunting for the
inexperienced. Of the remaining penguins, the majority turned back to
K-2.2.18. A few of the original group did make it K-2.4.0 and spent much
time recuperating from the exhausting swim and the mental trauma from having
seen their friends eaten.
Group #4 was all the other penguins left on K-2.2.18. These penguins waited
a number of months till the ocean calmed down and the killer whales migrated
to warmer waters. A this point the majority of them departed from K-2.2.18
for K-2.4.0 with friendly schools of dolphins to guide them (designated
Pod-RedHat, Pod-SuSe, Pod-Sistina, etc...). They arrived without incident
on K-2.4.0. Those left on K-2.2.18 maintained the rookery and lived happy
ever after.
The moral of the story -- If you are a Group #3 penguin don't expect
much sympathy from your wiser or more cautious
brethren when you get eaten.
---
Michael Declerck, declerck@sistina.com +1.510.823.7991
next prev parent reply other threads:[~2001-01-08 16:05 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 [this message]
2001-01-08 17:43 ` Daniel Mitzlaff
2001-01-08 19:24 ` Michael J. Declerck
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=20010108160536.E0910E0B7@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.