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.
I'm a brand new linux mint user and was a windows user before. Used several versions of windows and got used to their terminology.
Switched to linux cause with windows the newer it got the more it ate up my memory and was always getting bogged down.
I'm having trouble understanding what the simple things mean. I read the explanation of what mount/umount means here. It was great and now I know what it means. When I get a list together I'll ask questions.
It is great there is a place you can ask questions and get answers.
I made a little Linux dictionary for myself, which I would be happy to share, but I can't upload it here because the attachments manager doesn't allow tarballs I'm pretty sure it used to do so.
Linux Mint has a hidden gem - the GNOME help viewer, Yelp. It is poorly documented, and almost everything I learned about it was by accident. One of those accidents was it can be launched from a terminal and used to view man-pages - I find it is much easier to read and navigate a man-page with Yelp than from the terminal output.
It is poorly documented, and almost everything I learned about it was by accident.
Maybe not just the documentation. On my system it takes quite a while to complete "exit" - I started to look at a strace but figured walking the dog would make more sense ...
As sort of an afterthought, here are the two basic bits of Linux terminology that tantalized me the most when I started with Linux.
In Linux, you do not delete (del) a file, you remove (rm) it. There is a del command, but rm is preferred.
You do not rename (ren) a file, you move (mv) it from one name to another. Of course, you can also move it from one directory to another without renaming it. If you are moving it to another directory, be sure to include the trailing slash (/) at the end of the path, or you will be attempting to rename it to the directory's name.
Code:
mv [somefile] [/path/to/directory/] <---moves file
mv [somefile] [/path/to/directory <---tries to rename it "directory" located in [/path/to/]
Learn how to use the man (manual) pages. They are generally not very useful for learning and can't be thought of as tutorials in any sense, but they are excellent references. See man man for more.
As sort of an afterthought, here are the two basic bits of Linux terminology that tantalized me the most when I started with Linux.
In Linux, you do not delete (del) a file, you remove (rm) it. There is a del command, but rm is preferred.
That's surely just a difference in the name.
Quote:
You do not rename (ren) a file, you move (mv) it from one name to another. Of course, you can also move it from one directory to another without renaming it.
That's a real difference. Using mv for both operations is an insight into what actually happens when you "move" a file. The file doesn't move (unless the new parent directory is on another drive), but its name and location (inode) is moved into another directory. Directories aren't really folders, they're indexes and Linux shows you that.
Quote:
If you are moving it to another directory, be sure to include the trailing slash (/) at the end of the path, or you will be attempting to rename it to the directory's name.
I never use a trailing slash. mv works perfectly well without it. It's smart enough to recognise if the destination is a directory, and it will then move the source file into it.
Using mv for both operations is an insight into what actually happens when you "move" a file. The file doesn't move (unless the new parent directory is on another drive), but its name and location (inode) is moved into another directory. Directories aren't really folders, they're indexes and Linux shows you that.
The inode doesn't move, either. All that happens is that a link to the existing inode is added in the new directory, and the link in the old directory is removed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.