Re: What /proc should contain [was: /proc/driver/microcode]

From: Patrick Spinler (spinler.patrick@mayo.edu)
Date: Mon Feb 28 2000 - 17:48:10 EST

Next message: Jeff Garzik: "Re: gettimeofday non-monotonic on SMP 2.3.47"
Previous message: Jacob Alifrangis: "RE: Load linux...from linux?"
Next in thread: Ron Flory: "poor system response after "nice'ing" a compute-bound process to 19"
Reply: Ron Flory: "poor system response after "nice'ing" a compute-bound process to 19"
Reply: Mark H. Wood: "Re: What /proc should contain [was: /proc/driver/microcode]"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Preface this with the obligatory "I am not a kernel hacker. If this
message is stupid, just ignore me."

Regarding parsing /proc files, has anyone thought of a file format which
contains a parsing specification ? For example a scanf format string.

Eg:

$ cat /proc/somefile
%d %d %f %s
12 45 8.4 Some String

Scanf may not be the best way to do this, but you get the idea.

-- Pat

-- This message does not represent the policies or positions of the Mayo Foundation or its subsidaries. Patrick Spinler email: Spinler.Patrick@Mayo.EDU Mayo Foundation phone: 507/284-9485

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/

Next message: Jeff Garzik: "Re: gettimeofday non-monotonic on SMP 2.3.47"
Previous message: Jacob Alifrangis: "RE: Load linux...from linux?"
Next in thread: Ron Flory: "poor system response after "nice'ing" a compute-bound process to 19"
Reply: Ron Flory: "poor system response after "nice'ing" a compute-bound process to 19"
Reply: Mark H. Wood: "Re: What /proc should contain [was: /proc/driver/microcode]"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Feb 29 2000 - 21:00:21 EST