[lkml]   [2002]   [Feb]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: RFC: /proc key naming consistency
    On February 13, 2002 09:07 pm, H. Peter Anvin wrote:
    > Followup to: <>
    > By author: Mark Swanson <>
    > In newsgroup:
    > >
    > > Notice the space between "cpu" and "MHz", or "cpu" and "family" yet there
    > > is no space between "fdiv" and "bug" (_).
    > >
    > > The reason I think NOT using a space is a good idea because it makes life
    > > easier for developers parsing /proc entries. Specifically, Java
    > > developers could use /proc/cpuinfo as a property file, but the space in
    > > the 'key' breaks java.util.Properties.load().
    > >
    > When I and Dan Quinlan submitted the cleanup for this we used _
    > everywhere. Unfortunately some other people not just added keys with
    > spaces, but gracefully "corrected" our "mistakes"...

    What do you think about the idea earlier in this thread of going with
    shell-parsable key value pairs? I find that idea really attractive, but
    there's the issue of breaking utilities (kde control panel?) that already
    parse the existing format.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:24    [W:0.021 / U:16.680 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site