From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 2/2] checkquorum.wdmd: add integration script with wdmd
Date: Wed, 10 Oct 2012 13:14:40 +0200 [thread overview]
Message-ID: <507558A0.6060302@redhat.com> (raw)
In-Reply-To: <50755652.5080906@itechnical.de>
On 10/10/2012 1:04 PM, Heiko Nardmann wrote:
> Am 10.10.2012 10:11, schrieb Fabio M. Di Nitto:
>> [snip]
>> that doesn?t scale well for debian derivates that don?t ship
>> debian_version :) (see ubuntu & co..)
>>
>> You can?t even use something like "which dpkg" since the tool is
>> available on rpm based distributions... or viceversa.. there is rpm for
>> Debian & derivates.
>>
>> hardcoding all distributions is not optimal either, as they might change
>> policy by version....
>>
>> Fabio
>>
>
> What about 'lsb_release'? Is that executable available on all platforms?
Not installed by default, it?s generally shipped with $distro-lsb
metapackage that pulls in half gazillions dependencies.
I doubt it would solve anything since you still need to parse the
output. It?s really no different than hardcoding /etc/$distro_release,
actually with a few GB of extra packages ;)
Fabio
next prev parent reply other threads:[~2012-10-10 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 9:36 [Cluster-devel] [PATCH 1/2] cman init: make sure we start after fence_sanlockd and warn users Fabio M. Di Nitto
2012-10-09 9:36 ` [Cluster-devel] [PATCH 2/2] checkquorum.wdmd: add integration script with wdmd Fabio M. Di Nitto
2012-10-10 4:26 ` Dietmar Maurer
2012-10-10 6:59 ` Fabio M. Di Nitto
2012-10-10 8:06 ` Dietmar Maurer
2012-10-10 8:11 ` Fabio M. Di Nitto
2012-10-10 8:15 ` Dietmar Maurer
2012-10-10 11:04 ` Heiko Nardmann
2012-10-10 11:14 ` Fabio M. Di Nitto [this message]
2012-10-10 4:33 ` Dietmar Maurer
2012-10-10 7:06 ` Fabio M. Di Nitto
2012-10-10 8:10 ` Dietmar Maurer
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=507558A0.6060302@redhat.com \
--to=fdinitto@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 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).