Messages in this thread | | | Date | Tue, 2 Jun 1998 10:40:15 -0400 (EDT) | From | Jon Lewis <> | Subject | Re: [IDEA] Developers: your opinion badly needed ! (Was: [PATCH] /proc/config.gz) |
| |
On Tue, 2 Jun 1998, Marty Leisner wrote:
> Having a /proc/config is a good idea. > > Having to match static files with a running kernel is a bad > idea...no matter how careful you are, you may make mistakes (assuming > you can find the file). > > The solution for /boot/*-${VERSION} is not sufficient when > multiple kernels exists for the same version...
Why not? You can't come up with descriptive uniqe names?
/kernels/System.map-2.0.33-1-stackln /kernels/System.map-2.0.33-stackF /kernels/System.map-2.0.33-stackln /kernels/config-2.0.33-1-stackln /kernels/config-2.0.33-stackF /kernels/config-2.0.33-stackln /kernels/vmlinuz-2.0.33-1-stackln /kernels/vmlinuz-2.0.33-stackF /kernels/vmlinuz-2.0.33-stackln
The only problem I'll have is remembering exactly how these differ a year from now...but /proc/config isn't going to help with that. Wasn't there a /proc/patches patch that lists all the patches used if they register with it? That might be far more useful.
> When you need this information, you want ACCURATE infomation, not a guess > (multiple files are a guess).
But this really isn't a kernel issue...it's an administration issue. If /proc/config goes in, at least make it optional.
------------------------------------------------------------------ Jon Lewis <jlewis@fdt.net> | Spammers will be winnuked or Network Administrator | drawn and quartered...whichever Florida Digital Turnpike | is more convenient. ______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key____
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |