On Fri, Jun 25, 2010 at 10:59 AM, Jason Hill <jasonbrandonh...@gmail.com> wrote:
>
> You can chop it up a bit for readability too. This is tested on Debian and
> Red Hat.
>
> $ uname -a
> $ cat /etc/issue
> $ cat /proc/cpuinfo | grep -m 1 "model name"
> $ cat /proc/cpuinfo | grep -c "processor" # number of cores
> or $ cat /proc/cpuinfo | grep -m 1 "cores" # number of cores per processor
> $ cat /proc/meminfo | grep "MemTotal"
> $ cat /proc/meminfo | grep "SwapTotal"
>
> Jason
>
> On Fri, Jun 25, 2010 at 7:48 AM, Minh Nguyen <nguyenmi...@gmail.com> wrote:
>>
>> Hi David,
>>
>> On Fri, Jun 25, 2010 at 11:40 PM, David Kirkby <david.kir...@onetel.net>
>> wrote:
>>
>> <SNIP>
>>
>> > Of course, that could change over time. If you want to know your way
>> > around a Solaris system a bit more, here are some semi-useful commands
>>
>> Thank you for giving such a useful list of commands for getting
>> information about a Solaris system. Let me repay in kind for a Linux
>> system:
>>
>> $ uname -a
>> $ cat /etc/issue
>> $ cat /proc/cpuinfo
>> $ cat /proc/meminfo
>>
>> And for a Mac OS X system:
>>
>> $ uname -a
>> $ /usr/sbin/system_profiler
Anyone interested in turning this thread into a script that spits out
the version of sage, together with all the above system
hardware/software information? Then we can ask users to send the
output of the command:
sage -system_info
(or some other appropriate name). This command should be available
both from within sage as well as from the command line.
Franco
--
--
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
