| 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
| ||
|
Message-ID: <20080220163042.GC5539@lazybastard.org> Date: Wed, 20 Feb 2008 17:30:42 +0100 From: Jörn Engel <joern@...fs.org> To: Stephane Chazelas <stephane.chazelas@...rson.com> Cc: Arnd Bergmann <arnd@...db.de>, Jörn Engel <joern@...fs.org>, linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org Subject: Re: [PATCH 2.6.24] block2mtd: removing a device and typo fixes On Wed, 20 February 2008 14:43:39 +0000, Stephane Chazelas wrote: > > note that for "loop", you have /dev/loop0, /dev/loop1... which > makes it a pain to handle > > For block2mtd, you don't need several device files in /dev, you > only need one to pass ioctls down to create mtd devices. > > That may end up creating new /dev devices via mtdblock or > mtdblock_ro for instance. > > So I'm not sure reusing the "loop" ioctls is a good idea. /me notes that you dislike both existing interfaces and would prefer a third. How likely is it that you will still like the new interface two years down the road? How likely is it that everyone else will agree with you? In the end, a painful interface is still less painful than a choice of several incompatible ones. I used to think different and have burned my fingers often enough to learn the lesson. :) Jörn -- Mac is for working, Linux is for Networking, Windows is for Solitaire! -- stolen from dc -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists