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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
hi, i got stuck on these questions -_-, seems to be dumb, but no, i dont know how:
A pipe is a Unix mechanism for directing (piping) the output of one program or command to become the input of another program or command. For example, consider the two commands who and less. less outputs the contents of its input (for example, a file) onto the screen in such a way that is pauses after each screenful. who lists information about every user session currently on the system. If there are more sessions than lines on the screen, the top lines will scroll off before we get a chance to see them. If we make the output of who go through a pipe to become the input of less, then less will pause after a screenful, displaying the top lines originally output by who.
A pipe is indicated by the character "|"; the command described above would look like this: who | less. Pipes let you chain commands on a single line; each command takes as its input the output of the previous command.
1. Assume you have a program called Large.class which prints many lines of output to the screen,. Give a one-line command (try man java) that will run Large and display the output, sorted alphabetically.
2. One of the pieces of information printed by who, described above, is the id of the terminal used in a given session. Give a one-line command to list only the session associated with a terminal named "tty22". Try looking at grep.
Make sampledir your current working directory. You want to know which files in the current directory contain the word "Canada".
1. What command do you use to display only the filenames of the files in the current directory that contain "Canada"?
2. What if you didn't care about the case of the letters (e.g., could be "Canada", or "CANADA" or "cAnaDa")?
Suppose myfile contains 100 lines. How do you display, with a one-line command, just lines 50 through 70 (inclusive) of myfile?
Originally posted by kyborg beautiful, i love u man.... i dont even know when i will use those commands
I don't know what you plan on doing with Linux, but if you plan on doing anything besides surfing the web, playing games, music, or videos, then I would learn them. Just take your time and look at some good docs.