#8048: command to gather build report on a platform/hardware combination
---------------------------+------------------------------------------------
Reporter: mvngu | Owner: tbd
Type: enhancement | Status: new
Priority: major | Milestone: sage-4.5
Component: misc | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Comment(by jasonbhill):
Notes on hrdwr-info.sh as of July 15:
* only writes to the screen, not to a file yet
* is bash instead of python
* only checks Linux right now. (The other OSs are easier, IMO, but I
mainly have access to Linux and some Solaris machines. I'll do Solaris
next.)
There are several things to consider: * Pruning info from /etc is not
safe. It is not standardized, subject to user modifications, subject to
lack of updates between distros (Ubuntu -> Mint etc). But, when the info
exists it can be useful. It can also be badly formatted... with \r and \n
explicit in the file. I used some 'sed' commands to get around this a bit.
* Pruning from /proc is fine, since the data is standardized and updated
by the OS. The only problem I have had in testing here is with virtual
machines where the CPU is a virtual processor. But, the output in that
case makes the situation obvious.
* Getting your hands on the 32/64-bit declaration is tricky, since you'd
like to use uname to do it. We can do that, but this ONLY returns
information about the OS and not the hardware capabilities. I suppose that
is fine, since we're testing installs and we only really care what
bitlength the OS is capable of. But, many of the servers I've tested on
are running 32-bit Linux distros on 64-bit capable hardware... and so I
listed the OS and hardware bitlengths separately. I'm just curious if this
will ever cause issues.
Questions I have: * Can you test it, break it?
* What looks useful? What doesn't? What looks left out? Why?
* How would something like this be used? I'm under the impression that
this can get written to a log and the user can paste that log... where?
I'll post a link with sample output since it isn't formatting nicely in
this forum wysiwyg editor.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8048#comment:5>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
