netdev - Re: [PATCH 05/15] dec netdev: relocate DIGITAL based drivers to legacy

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20101028.225326.183057622.davem@davemloft.net>
Date:	Thu, 28 Oct 2010 22:53:26 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	macro@...ux-mips.org
Cc:	paul.gortmaker@...driver.com, netdev@...r.kernel.org
Subject: Re: [PATCH 05/15] dec netdev: relocate DIGITAL based drivers to
 legacy

From: "Maciej W. Rozycki" <macro@...ux-mips.org>
Date: Fri, 29 Oct 2010 06:46:13 +0100 (BST)

>  This would be no different to what we do wrt network protocols under 
> net/, so drivers would go to ethernet/, fasteth/, gbeth/, 10gbeth/, fddi/, 
> tokenring/, atm/, appletalk/, etc. (names up to debate if need be) as 
> applicable.  This would scale well, avoid the need for arbitrary decisions 
> (is this piece legacy yet or not?) and automatically classify drivers as 
> more or less obsolescent too, as obviously none of the stuff under 
> ethernet/, fddi/ or tokenring/ can be reasonably recent unlike 10gbeth/.

Why are you so hung up about something being called legacy?

I would be proud to be labelled "legacy", as that means I've served a
purpose for a long time and some folks even want or need me to stick
around for a bit longer.

Legacy hardware is just old and the drivers for them are in a purely
"sustaining" state, that is all.

And using link layer technology to classify is really stupid since
many devices match multiple of the categories you've suggested.

I think the existing proposal is just fine.
--
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