[lkml]   [1999]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: /proc/cpuinfo verbiage differ unnecessarily between ports...
    In article <>,
    Steve Dodd <> wrote:
    >On Tue, Aug 31, 1999 at 05:17:23PM -0700, david parsons wrote:
    >> Why not? I'd say that the contents of /proc/cpuinfo would be very
    >> interesting to tools, because it's what the operating system thinks
    >> it's running on.
    >Would it not be more sensible to introduce a syscall or some such thing to
    >do it?

    No. If this information is presented in a syscall, you end up
    restricting access to that set of programs that know about the
    syscall. If it's presented in text, just about anything, up to and
    including that shell that you managed to get started before
    that fork bomb ate the system, can display the contents of the

    david parsons \bi/ Syscalls? Eeeeuuuuuwwww!

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

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