From: Lars Marowsky-Bree <lmb@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: tools target for SLES9 SP2 and RHEL4 U2
Date: Fri, 10 Jun 2005 12:47:11 +0200 [thread overview]
Message-ID: <20050610104711.GC20162@marowsky-bree.de> (raw)
In-Reply-To: <20050610061033.GA9474@us.ibm.com>
On 2005-06-09T23:10:33, Mike Anderson <andmike@us.ibm.com> wrote:
> > > Should we stabilize a 0.4.5 out of the git head
> > Yes - both distributions are basing their next package on your
> > current git head.
> What about multipathd's use of uevents for dm updates and the distro
> kernels currently not supporting this capability. Will a person just have
> to restart multipathd if one changes the dm config and a newer kernel is
> not being used?
We'll need a workaround for that, or back it out for our distribution
and go back to the signal version...
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
next prev parent reply other threads:[~2005-06-10 10:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 18:16 tools target for SLES9 SP2 and RHEL4 U2 christophe varoqui
2005-06-09 19:13 ` Alasdair G Kergon
2005-06-09 19:15 ` Alasdair G Kergon
2005-06-09 19:34 ` christophe varoqui
2005-06-12 12:21 ` StorageWorks failover model (was: tools target for SLES9 SP2 and RHEL4 U2) Axel Thimm
2005-06-12 12:31 ` christophe varoqui
2005-06-12 14:33 ` Axel Thimm
2005-06-12 16:37 ` christophe varoqui
2005-06-10 6:10 ` tools target for SLES9 SP2 and RHEL4 U2 Mike Anderson
2005-06-10 6:44 ` Christophe Varoqui
2005-06-10 10:47 ` Lars Marowsky-Bree [this message]
2005-06-14 10:34 ` Lars Marowsky-Bree
2005-06-14 11:44 ` Christophe Varoqui
2005-06-14 12:00 ` Lars Marowsky-Bree
2005-06-14 12:48 ` Christophe Varoqui
2005-06-14 13:57 ` Lars Marowsky-Bree
2005-06-14 14:08 ` Christophe Varoqui
2005-06-14 14:13 ` Lars Marowsky-Bree
2005-06-14 13:22 ` Alasdair G Kergon
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=20050610104711.GC20162@marowsky-bree.de \
--to=lmb@suse.de \
--cc=dm-devel@redhat.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.