[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170508190900.GF17700@fury>
Date: Mon, 8 May 2017 12:09:00 -0700
From: Darren Hart <dvhart@...radead.org>
To: Mario.Limonciello@...l.com
Cc: a.bokovoy@...il.com, andy.shevchenko@...il.com, luto@...nel.org,
pali.rohar@...il.com, rjw@...ysocki.net, len.brown@...el.com,
corentin.chary@...il.com, andriy.shevchenko@...ux.intel.com,
linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: RFC: WMI Enhancements
On Mon, May 08, 2017 at 06:26:53PM +0000, Mario.Limonciello@...l.com wrote:
> (Responding as plain text, your email probably got punted from the ML from being HTML)
>
> >
> > ...
> >
> > I'm not sure what you are asking about. Samba does not deal with WMI at all. The state of affairs is
> > explained at https://powershell.org/2015/04/24/management-information-the-omicimwmimidmtf-dictionary/
> > -- old WMI (DCOM/RPC-based) is deprecated, new WMI based on WS-MAN is supported and OMI is the
> > implementation. We used to have a very limited attemt at writing DCOM stack and nobody worked on
> > it for years so it got removed.
>
> Thanks! That was a very interesting read.
>
> > Microsoft has already published a MOF parser as part of OMI work: https://github.com/Microsoft/omi/
> > under MIT license.
>
> Unfortunately that's expecting text MOF, not this intermediary compiled format.
>
I presume which of these to use is the decision of the vendor? Is there a
transition going on from BMOF to Text MOF? Or will both be part of products for
the near term?
I'm trying to understand if BMOF is a legacy thing now, or if it will continue
to be used in new designs.
--
Darren Hart
VMware Open Source Technology Center
Powered by blists - more mailing lists