On 1 July 2010 00:07, Jason B. Hill <ja...@jasonbhill.com> wrote:
>
> 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

This looks useful. I do however think this should be done from a shell
script, rather than a python script, as otherwise it limits the
usefulness until such point as python is built. There are plenty of
things that can wrong in building python. I'm not saying it's not
useful to have a python package that can do these sort of things, but
for build issues, making it as simple as possible seems sensible to
me.

Things like exp(1.0) are only going to be computable once Sage is
running, but some of this sort of thing needs to be available with the
bare minimum of Sage working.

Dave

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
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Reply via email to