This seems to overlap the recent discussion on hardware and trac ticket #8048.
I am about 90% done with a python script to do this on Linux, and I need to chop it apart and "functionalize" it, so to speak. Basically, the /proc info is standardized, while /etc is different between distros. I try to pull in /etc/issue, but don't try to rely on it. You should be able to call this from sage, whatever it ends up being called. But, assuming an installation fails, it would be optimal to call this as a simple python script or ... something. I'm not sure the best way to organize that part, but I have been writing this so that it functions inside and outside of sage. Here's what it returns right now for a couple of machines: sagenb.org from inside sage notebook: -- OS and system information -- Machine Name: boxen Issue: Ubuntu 8.04.4 LTS Architecture: 64bit, ELF uname -a: Linux, boxen, 2.6.24-24-server, #1 SMP Fri Sep 18 16:47:05 UTC 2009, x86_64, Python Version: Python 2.6.4 GCC Version: gcc (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4) -- CPU information -- Processor: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz Processor Count: 4 Cores Per CPU: 6 Total Number of Threads: 24 -- memory information -- Total Memory: 132301916 kB Free Memory: 578520 kB Total Swap: 71681988 kB Free Swap: 69053096 kB -- sage specific information -- sage: exp(1.0) 2.71828182845905 euclid.colorado.edu from python -- OS and system information -- Machine Name: euclid.colorado.edu Issue: Red Hat Enterprise Linux Client release 5.5 Architecture: 32bit, ELF uname -a: Linux, euclid.colorado.edu, 2.6.18-164.15.1.el5PAE, #1 SMP Mon Mar 1 11:14:09 EST 2010, i686, i686 Python Version: Python 2.4.3 GCC Version: gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48) -- CPU information -- Processor: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz Processor Count: 2 Cores Per CPU: 4 Total Number of Threads: 8 -- memory information -- Total Memory: 24942604 kB Free Memory: 22163964 kB Total Swap: 27262296 kB Free Swap: 27262068 kB On Wed, Jun 30, 2010 at 4:05 AM, David Kirkby <david.kir...@onetel.net>wrote: > On 30 June 2010 08:35, Robert Bradshaw <rober...@math.washington.edu> > wrote: > > > The install log should contain the system information. > > > > - Robert > > In practice, a lot of people are going to cut and past the error > message from the screen to sage-support. So I believe having at least > a minimum of information (Operating system version and CPU at the very > least) would be useful to always print. > > > dave > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com<sage-devel%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
