[lkml]   [1998]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.1.120 - too many errors on the network interfaces
    In message <>, 
    x Buell writes:
    | On Sun, 20 Sep 1998, Brandon S. Allbery KF8NH wrote:
    | > Dunno about ioctl (I've seen lots of schemes proposed and used, and
    | > all of them fall short), but it does seem silly that proc doesn't
    | > include version numbers. Would it really be that painful to have the
    | I have had some problems parsing /proc/cpuinfos on different
    | architectures. I hope you have seen my message about it earlier today.

    I did, in fact it was another reason that I posted the above. Consistent
    interfaces as suggested are well, fine, and good, but (XthreadX with UDI)
    you can't always maintain interface consistency when that interface is
    broken, as with the dev->flush() changes. And /proc/cpuinfo strikes me as
    an interface which may well have problems being simultaneously consistent
    and complete while addressing multiple CPU architecture families (heck, it's
    been a problem just between Intel, AMD, and Cyrix; should we be surprised at
    problems between x86 and PPC, Alpha, SPARC, ...?).

    brandon s. allbery [os/2][linux][solaris][japh]
    system administrator [WAY too many hats]
    electrical and computer engineering KF8NH
    carnegie mellon university

    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:44    [W:0.020 / U:54.756 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site