From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932595AbWG1IWS (ORCPT ); Fri, 28 Jul 2006 04:22:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932596AbWG1IWS (ORCPT ); Fri, 28 Jul 2006 04:22:18 -0400 Received: from smtp-vbr1.xs4all.nl ([194.109.24.21]:63759 "EHLO smtp-vbr1.xs4all.nl") by vger.kernel.org with ESMTP id S932595AbWG1IWR (ORCPT ); Fri, 28 Jul 2006 04:22:17 -0400 To: "Brown, Len" Cc: "Shem Multinymous" , "Pavel Machek" , "Matthew Garrett" , , "kernel list" , , Subject: Re: Generic battery interface References: From: Johan Vromans Date: Fri, 28 Jul 2006 10:22:03 +0200 In-Reply-To: (Len Brown's message of "Fri, 28 Jul 2006 00:05:35 -0400") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org "Brown, Len" writes: > good for shell scripts, not clear it is better for C programs > that have to open a bunch of files by name. Moreover, it means that the factual data is only made available as a nice textual string, that then has to be parsed by shell scripts and other programs to get the factual data again. So I feel much for /dev/xxx approach, together with the already mentioned small utilities like 'batstat' for shell scripts. -- Johan