linux-kernel - Re: [PATCH] add netdev led trigger

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: <20101117200614.GK15096@localhost>
Date:	Wed, 17 Nov 2010 15:06:14 -0500
From:	Eric Cooper <ecc@....edu>
To:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] add netdev led trigger

On Wed, Nov 17, 2010 at 08:58:43PM +0100, Pavel Machek wrote:
> I was hoping you'd comment on the ABI itself, too. It uses 
> 
> echo "foo bar baz" > file
> 
> to enable/disable specific events to be "displayed". More traditional
> interface would be 
> 
> echo disable > file_foo

The main arguments for using the single "mode" file are:
1. that's how it was implemented for OpenWrt, and there's a fair
   amount of userland (web admin tools, etc.) that groks it
2. it's only specifying a set of three possible values -- separate
   files seem like overkill

-- 
Eric Cooper             e c c @ c m u . e d u
--
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/