From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: Hal Rosenstock <hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"linux-rdma
(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Yan Burman <yanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: config file lost
Date: Tue, 18 Jun 2013 12:03:37 +0300 [thread overview]
Message-ID: <51C02269.5050105@mellanox.com> (raw)
In-Reply-To: <51BF591B.4090002-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On 17/06/2013 21:44, Hal Rosenstock wrote:
> I'm not 100% sure about the origin of those RPMs but I think the 3.3.15
> one is RedHat packaged and the 3.3.16 appears to be PLD packaged and the
> processes are a little different. I suspect the 3.3.16 one is packaged
> with the spec file in the tree whereas RedHat uses their own spec file.
>
> FWIW it's simple to generate an up to date config file:
>
> opensm -c opensm.conf
Hal,
YES for your observations, that 3.3.15 was RHEL packages and the 3.3.16
was built from the upstream spec. I know that
I can generate the config file using the method you suggested, however,
does the upstream service scripts uses the location to which this is
generated, so things are plug-and-play, or I need to hack that somehow?
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-06-18 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 13:02 config file lost Or Gerlitz
[not found] ` <51BDB769.70107-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-06-17 18:44 ` Hal Rosenstock
[not found] ` <51BF591B.4090002-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-06-18 9:03 ` Or Gerlitz [this message]
[not found] ` <51C02269.5050105-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-06-18 11:19 ` Hal Rosenstock
[not found] ` <51C0424F.60307-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-06-18 11:57 ` Or Gerlitz
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=51C02269.5050105@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
/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.