All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Subject: Re: [Notice] multipath-tools changes upstream
Date: Fri, 18 Apr 2008 16:45:59 +0200	[thread overview]
Message-ID: <4808B427.1000209@suse.de> (raw)
In-Reply-To: <1208278929.11770.62.camel@plop>

Hi Christophe,

Christophe Varoqui wrote:
> Hi,
> 
> please take notice I updated the upstream git tree for the
> multipath-tools project. This tree includes lots of code shuffling :
> 
> 1) prioritizers as dlopen'ed shared libs (/lib/libmultipath/libprio*.so)
> 2) checkers as dlopen'ed shared libs (/lib/libmultipath/libcheck*.so)
Maybe /lib/multipath is more appropriate; eventually something more might
be stored in there.

> 
> Consequences :
> The multipath tool is about to get shot for good
About time :-)
But: how do I get the topology output?
I hope not via the 'multipathd -k' option?
Maybe we should just have it symlinked to multipathd
and print out the appropriate output ...

> The klibc build is gone
Even better.

Oh, and I do have some fixes queued which I need to polish up
and post here. Just as a reminder if you thought of doing
a release or somesuch ...

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

  parent reply	other threads:[~2008-04-18 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 17:02 [Notice] multipath-tools changes upstream Christophe Varoqui
2008-04-17 18:25 ` Benjamin Marzinski
2008-04-17 20:48   ` Mike Anderson
2008-04-18 14:45 ` Hannes Reinecke [this message]
2008-05-14 15:21 ` Kiyoshi Ueda
  -- strict thread matches above, loose matches on Subject: below --
2008-05-14 20:21 Christophe Varoqui

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=4808B427.1000209@suse.de \
    --to=hare@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=k-ueda@ct.jp.nec.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.