Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 5 Nov 2001 18:41:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 5 Nov 2001 18:41:23 -0500 Received: from leibniz.math.psu.edu ([146.186.130.2]:29867 "EHLO math.psu.edu") by vger.kernel.org with ESMTP id ; Mon, 5 Nov 2001 18:41:08 -0500 Date: Mon, 5 Nov 2001 18:41:07 -0500 (EST) From: Alexander Viro To: Tim Jansen cc: andersen@codepoet.org, Ben Greear , linux-kernel@vger.kernel.org Subject: Re: PROPOSAL: dot-proc interface [was: /proc stuff] In-Reply-To: <160tEV-20u3KSC@fmrl04.sul.t-online.com> Message-ID: 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 On Tue, 6 Nov 2001, Tim Jansen wrote: > But how can the user know this without looking into the kernel? Compare it to > /proc/mounts. Proc mounts escapes spaces and other special characters in > strings with an octal encoding (so spaces are replaced by '\040'). Ah, yes - the horrible /proc/mounts. Check that code in 2.4.13-ac8, will you? Yes, current procfs sucks. We got a decent infrastructure that allows to write that code easily. Again, see -ac8 and watch fs/namespace.c code dealing with /proc/mounts. No need to play silly buggers with "one value per file" (and invite the Elder Ones with applications trying to use getdents()). Sigh... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/