Re: [patch-2.3.47] /proc/driver/microcode -> /dev/cpu/microcode

2000-02-25 Thread Alan Cox
> Currently all options suck equally. I'm not advocating /proc for the data > (that'd be silly) but I am against a wholesale change from one dump to > another in the name of being "pretty" wit a more significant fix. It should be a misc device too obviously. Your 68K of devfs does actually get

Re: [patch-2.3.47] /proc/driver/microcode -> /dev/cpu/microcode

2000-02-24 Thread Jes Sorensen
> "Eric" == Eric W Biederman writes: Eric> Jes Sorensen <[EMAIL PROTECTED]> writes: >> I second that - I always had the impression that if devfs ever >> went into the official kernel it was going to be as an option, >> leaving system functional without enabling it. Eric> I never saw an arg

Re: [patch-2.3.47] /proc/driver/microcode -> /dev/cpu/microcode

2000-02-24 Thread George
On Thu, 24 Feb 2000, Tigran Aivazian wrote: >On Wed, 23 Feb 2000, George wrote: >> The alternative to devfs is what we already have, a working (maybe not >> perfect, but working) /dev. And if you already have /dev (and use it), >> what's the point of wasting memory on devfs which would duplicate