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

From: Jamie Lokier (lk@tantalophile.demon.co.uk)
Date: Thu Feb 24 2000 - 18:23:41 EST

Next message: Joseph Cheek: "RE: 2.3.47 build barfing on mtrr.c"
Previous message: Peter Chubb: "Re: permissions not honoured by /bin/pwd aka getcwd"
In reply to: Ricky Beam: "Re: What /proc should contain [was: /proc/driver/microcode]"
Next in thread: almesber@lrc.di.epfl.ch: "Re: What /proc should contain [was: /proc/driver/microcode]"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ricky Beam wrote:
> Well, not _exact_ ... ls -l /proc/<pid>/fd resolving to devices and filenames
> is _very_ handy.

I use that too. Very handy indeed.

-- Jamie

-
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: Joseph Cheek: "RE: 2.3.47 build barfing on mtrr.c"
Previous message: Peter Chubb: "Re: permissions not honoured by /bin/pwd aka getcwd"
In reply to: Ricky Beam: "Re: What /proc should contain [was: /proc/driver/microcode]"
Next in thread: almesber@lrc.di.epfl.ch: "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:10 EST