Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My wife and I recently got an iMac PowerPC running Linux Debian from a friend of hers at work. I have no experience with Linux and very little with Macs. I'd like to know how to find out how much memory (hard drive and RAM) I have on it. I know it's been upgraded, but I don't know how much. My wifes friend doesn't remember exactly because she's upgraded a couple of them since this one. Any help would be appreciated.
Click here to see the post LQ members have rated as the most helpful post in this thread.
You can use the free command to find out how much RAM your system has, along with how much is used, and how much is free. Read the man page for exact details and arguments using "man free."
An example would be as follows:
Code:
free -m
That will give the output in megabytes. For gigabytes, use -g instead.
There is also LSPCI which will tell you your drivers, and LS which will locate file directories ... Just search google for 'LS command linux' and it should pop up some tutorials. Hope this was useful.
EDIT: Also take a look at this link, It was my Wallpaper for the longest time and proved to be very helpful: COMMANDS LIST IMAGE
Debian also has a "System Information" graphical tool. If you are using the default Gnome desktop, it is likely under System-->Administration on the menu.
You can use the free command to find out how much RAM your system has, along with how much is used, and how much is free.
AFAIK free excludes certain reserved memory (e.g. for the kernel, etc.), so it doesn't give a 100% accurate picture of how much physical memory is actually installed in the machine. As an example, my laptop has 4 GiB of RAM, but free doesn't detect all of it:
True... But most likely, in most cases, you want to know what memory is available of use to the user only, not all of it, unless you are a programmer, messing with the kernel, etc.
You want to learn and use the LS command in the terminal. It will tell you all your directories and hardware.
So open your terminal and type in LSHW, it will look like this:
Code:
name@computer:$ lshw
What you get in return will look like this ):
.....
.....
.....
There is also LSPCI which will tell you your drivers, and LS which will locate file directories ... Just search google for 'LS command linux' and it should pop up some tutorials. Hope this was useful.
EDIT: Also take a look at this link, It was my Wallpaper for the longest time and proved to be very helpful: COMMANDS LIST IMAGE
Please keep in mind that Linux is case-sensitive. Giving a newbie commands in capital letters may be very confusing, since they just won't work typed in capital letters. If you want to emphasize words/commands in a post you can easily use the bold or italic option, or just use code-tags.
Also keep in mind that lshw, lspci and lsusb are (except for the name) not related to ls, they are separate commands that come in separate packages. In my Slackware standard installation lsusb comes with usbutils, lspci comes with pciutils and lshw isn't even installed. In Debian it was the same, lshw had to be installed, it was not part of the standard install.
Please keep in mind that Linux is case-sensitive. Giving a newbie commands in capital letters may be very confusing, since they just won't work typed in capital letters.
I agree, they mean different things t othe computer depending on case. I don't capitalize them even if they're the first word in a sentence.
This reminds me of another thing that often bothers me, that's well explained here:
Quote:
Originally Posted by http://www.catb.org/jargon/html/writing-style.html
Hackers tend to use quotes as balanced delimiters like parentheses, much to the dismay of American editors. Thus, if “Jim is going” is a phrase, and so are “Bill runs” and “Spock groks”, then hackers generally prefer to write: “Jim is going”, “Bill runs”, and “Spock groks”. This is incorrect according to standard American usage (which would put the continuation commas and the final period inside the string quotes); however, it is counter-intuitive to hackers to mutilate literal strings with characters that don't belong in them. Given the sorts of examples that can come up in discussions of programming, American-style quoting can even be grossly misleading. When communicating command lines or small pieces of code, extra characters can be a real pain in the neck.
Consider, for example, a sentence in a vi tutorial that looks like this:
Then delete a line from the file by typing “dd”.
Standard usage would make this
Then delete a line from the file by typing “dd.”
but that would be very bad — because the reader would be prone to type the string d-d-dot, and it happens that in vi(1), dot repeats the last command accepted. The net result would be to delete two lines!
I agree, they mean different things t othe computer depending on case. I don't capitalize them even if they're the first word in a sentence.
This reminds me of another thing that often bothers me, that's well explained here:
While this is true grammatically, you also have to remember that these rules were written before the advent of computers and programming, for the most part, and that conventions are broken when directed to a particular trade, which programming definitely is.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
