Messages in this thread | | | Date | Tue, 14 Mar 2000 17:43:35 -0500 | From | Tim Coleman <> | Subject | Re: ver_linux script |
| |
On Tue, Mar 14, 2000 at 08:27:43PM +0000, Riley Williams wrote: > Hi Tim. > > >>> Alan,Tim: Enclosed is a version that fixes both this alias > >>> problem and other prospective ones without destroying the > >>> users' environment or spawning a subshell. Can it be used? > > >> [mega snippage] > > > Um, I'm just curious, what happened to the patch that > > started this whole snowball? i.e. the proc/version vs. > > uname change. > > I've no idea. I'm not even sure of the reasoning behind the > proposal to make that change...
Perhaps I was a little bit unclear. My question was more like: "When you wrote up that patch, why did you choose not to include the /proc/version part?" You included it in a patch that you previously wrote.
The reason behind that change was some discussion dating back a bit where someone thought it would be useful to see the compiler that was used to build the kernel with, because of all the problems with people having strange results with different compilers.
/proc/version lists the compiler that was used. uname -a does not.
Yes, ver_linux does print out your compiler, but that is not necessarily the one that was used to build the kernel.
Is this a worthwhile goal? Am I being clear?
Tim
-- ------------------------------------------------------------------------ Tim Coleman <tim@beastor.mine.nu> Software Developer/Systems Administrator/RDBMS Specialist/Linux Advocate University of Waterloo Honours Co-op Combinatorics & Optimization "Go to Heaven for the climate, Hell for the company." -- Mark Twain [unhandled content-type:application/pgp-signature] | |