netdev - Re: PATCH: Network Device Naming mechanism and policy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 13 Oct 2009 19:56:09 +0100
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Dan Williams <dcbw@...hat.com>
Cc:	"Karl O. Pinc" <kop@...e.com>, Greg KH <greg@...ah.com>,
	Narendra K <Narendra_K@...l.com>, notting@...hat.com,
	matt_domsch@...l.com, netdev@...r.kernel.org,
	shemminger@...tta.com, linux-hotplug@...r.kernel.org,
	jordan_hargrave@...l.com, charles_rose@...l.com
Subject: Re: PATCH: Network Device Naming mechanism and policy

On Tue, 2009-10-13 at 11:17 -0700, Dan Williams wrote:
> On Mon, 2009-10-12 at 14:41 -0500, Karl O. Pinc wrote:
> > On 10/12/2009 02:09:00 PM, Greg KH wrote:
> > 
> > > "LOM"?
> > 
> > "LAN On Motherboard" of all things.  
> > 
> > (I had to look this
> > one up.  The expansion better suited
> > to today's economy is "Low On Manna".)
> 
> Or the previous usage from Sun, Apple, and others: "Lights Out
> Management".  Not sure why they needed to clash with a name already used
> in server-space, but perhaps I'm just out-of-date and there's a fancier
> name for LOM these days, and LOM got repurposed.

It's widely used with both meanings - what's more, LOM is an expected
feature of LOMs. :-)

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html