I think for detailed information about hardware would be in /proc directory.<br>for example commands like "less /proc/meminfo" and "less /proc/cpuinfo" would give detailed information about particular hardware.<br>
<br>Arshdeep<br><br><br><br><div class="gmail_quote">On Mon, Nov 7, 2011 at 12:00 PM, <span dir="ltr"><<a href="mailto:kent-request@mailman.lug.org.uk">kent-request@mailman.lug.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Send Kent mailing list submissions to<br>
<a href="mailto:kent@mailman.lug.org.uk">kent@mailman.lug.org.uk</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mailman.lug.org.uk/mailman/listinfo/kent" target="_blank">https://mailman.lug.org.uk/mailman/listinfo/kent</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:kent-request@mailman.lug.org.uk">kent-request@mailman.lug.org.uk</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:kent-owner@mailman.lug.org.uk">kent-owner@mailman.lug.org.uk</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Kent digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: CLI for resources? (James Morris)<br>
2. Re: CLI for resources? (Michael E. Rentell)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 6 Nov 2011 20:18:01 +0000<br>
From: James Morris <<a href="mailto:jwm.art.net@gmail.com">jwm.art.net@gmail.com</a>><br>
Subject: Re: [Klug-general] CLI for resources?<br>
To: Kent Linux User Group - General Topics <<a href="mailto:kent@mailman.lug.org.uk">kent@mailman.lug.org.uk</a>><br>
Message-ID:<br>
<CAPLoHyohnCf81Z-9=<a href="mailto:6iLNKOCZFAPrbeDXRREOthuixohBu6wWw@mail.gmail.com">6iLNKOCZFAPrbeDXRREOthuixohBu6wWw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On 3 November 2011 09:47, Michael E. Rentell<br>
<<a href="mailto:michael.rentell@ntlworld.com">michael.rentell@ntlworld.com</a>> wrote:<br>
> A friend in USA whom I've convinced to switch to Linux wants to know the<br>
> size of his RAM and his processor clock-speed. From this he will determine<br>
> which version to install.<br>
> He asks if there is are CLIs to report on RAM size and clockspeed. Such<br>
> questions are beyond me, can anyone help?<br>
<br>
<br>
Sorry a bit late to reply, but another useful command line is "uname<br>
--all", or "uname --processor" for part of solution as requested.<br>
<br>
James.<br>
<br>
<br>
<br>
<br>
> MikeR<br>
><br>
> _______________________________________________<br>
> Kent mailing list<br>
> <a href="mailto:Kent@mailman.lug.org.uk">Kent@mailman.lug.org.uk</a><br>
> <a href="https://mailman.lug.org.uk/mailman/listinfo/kent" target="_blank">https://mailman.lug.org.uk/mailman/listinfo/kent</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 07 Nov 2011 10:00:14 +0000<br>
From: "Michael E. Rentell" <<a href="mailto:michael.rentell@ntlworld.com">michael.rentell@ntlworld.com</a>><br>
Subject: Re: [Klug-general] CLI for resources?<br>
To: Kent Linux User Group - General Topics <<a href="mailto:kent@mailman.lug.org.uk">kent@mailman.lug.org.uk</a>><br>
Message-ID: <<a href="mailto:4EB7AC2E.8040404@ntlworld.com">4EB7AC2E.8040404@ntlworld.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
thanks for that James, I'll let him know those wheezes too.<br>
<br>
MikeR<br>
<br>
<br>
On 06/11/11 20:18, James Morris wrote:<br>
> On 3 November 2011 09:47, Michael E. Rentell<br>
> <<a href="mailto:michael.rentell@ntlworld.com">michael.rentell@ntlworld.com</a>> wrote:<br>
>> A friend in USA whom I've convinced to switch to Linux wants to know the<br>
>> size of his RAM and his processor clock-speed. From this he will determine<br>
>> which version to install.<br>
>> He asks if there is are CLIs to report on RAM size and clockspeed. Such<br>
>> questions are beyond me, can anyone help?<br>
><br>
><br>
> Sorry a bit late to reply, but another useful command line is "uname<br>
> --all", or "uname --processor" for part of solution as requested.<br>
><br>
> James.<br>
><br>
><br>
><br>
><br>
>> MikeR<br>
>><br>
>> _______________________________________________<br>
>> Kent mailing list<br>
>> <a href="mailto:Kent@mailman.lug.org.uk">Kent@mailman.lug.org.uk</a><br>
>> <a href="https://mailman.lug.org.uk/mailman/listinfo/kent" target="_blank">https://mailman.lug.org.uk/mailman/listinfo/kent</a><br>
>><br>
><br>
> _______________________________________________<br>
> Kent mailing list<br>
> <a href="mailto:Kent@mailman.lug.org.uk">Kent@mailman.lug.org.uk</a><br>
> <a href="https://mailman.lug.org.uk/mailman/listinfo/kent" target="_blank">https://mailman.lug.org.uk/mailman/listinfo/kent</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Kent mailing list<br>
<a href="mailto:Kent@mailman.lug.org.uk">Kent@mailman.lug.org.uk</a><br>
<a href="https://mailman.lug.org.uk/mailman/listinfo/kent" target="_blank">https://mailman.lug.org.uk/mailman/listinfo/kent</a><br>
<br>
End of Kent Digest, Vol 349, Issue 1<br>
************************************<br>
</blockquote></div><br>