Next Previous Contents

## 1. Introduction

## 1.1 Is Linux Right for You?

Let's start politically correct. Throughout this document I say ``Linux'', but I mean ``GNU/Linux''. Please go to http://www.gnu.org/gnu/linux-and-gnu.html to see why.

You want to switch from the DOS/Windows world to Linux? Good idea: Linux is technically superior to DOS, Windows 9x and even Windows NT. But beware: it might not be useful for you. These are the main differences between DOS/Windows and Linux:

- Windows runs Microsoft Office and lots of games; is perceived to be easy to install and configure; is notoriously unstable; performs poorly; crashes are frequent.
- Linux runs StarOffice, scores of technical software and fewer games; can be tricky to install and configure; is rock solid; performs impeccably; crashes are extremely rare.

It's up to you to decide what you need. Furthermore, Linux gives you power, but it takes some time to learn how to harness it. Thus, if mostly need commercial sw, or if you don't feel like learning new commands and concepts, you had better look elsewhere. Be aware that many newcomers give up because of initial difficulties.

Work is underway to make Linux simpler to use, but don't expect to be proficient with it unless you read a lot of documentation and use it at least for a few months. Linux won't give you instant results. In spite of these warnings, I'm 100% confident that if you are the right user type you'll find in Linux your computer Nirvana. By the way, Linux + DOS/Win can coexist happily on the same machine.

Prerequisites for this howto: I'll assume that

- you know the basic DOS commands and concepts;
- Linux, possibly with X Window System (X11 for short), is properly installed on your PC;
- your shell (the equivalent of `COMMAND.COM`) is `bash`.

Unless specified, all information in this work is aimed at bad ol' DOS. There is information about Windows here and there, but bear in mind that Windows and Linux are totally different, unlike DOS that is sort of a UNIX poor relation.

Please also note that this work is neither a complete primer nor a configuration guide!

The latest version of this document is available in several formats on http://www.linuxdoc.org.

## 1.2 It Is. Tell Me More

You installed Linux and the programs you needed on the PC. You gave yourself an account (if not, type `adduser yourname` now!) and Linux is running. You've just entered your name and password, and now you are looking at the screen thinking: ``Well, now what?''

Now, don't despair. You're almost ready to do the same things you used to do with DOS/Win, and many more. If you were running DOS/Win instead of Linux, you would be doing some of the following tasks:

- running programs and creating, copying, viewing, deleting, printing, renaming files;
- CD'ing, MD'ing, RD'ing, and DIR'ring your directories;
- formatting floppies and copying files from/to them;
- tailoring the system;
- surfing the Internet;
- writing .BAT files and programs in your favourite language;
- the remaining 1%.

You'll be glad to know that these tasks can be accomplished under Linux in a fashion similar to DOS. Under DOS, the average user uses very few of the 100+ commands available: the same, up to a point, applies to Linux.

### Introductory Concepts

The best way to learn something new is to get your feet wet. You are strongly encouraged to experiment and play with Linux: unless you login as ``root'', you can't damage the system that way. A few points:

- first of all, how to quit Linux safely. If you see a text mode screen, press <CTRL-ALT-DEL>, wait for the system to reboot, then switch off the PC. If you are working under X Window System, press <CTRL-ALT-BACKSPACE> first, then <CTRL-ALT-DEL>. Never switch off or reset the PC directly: this could damage the file system;
- unlike DOS or Windows, Linux has built-in security mechanisms. Files and directories have permissions associated to them; as a result, some cannot be accessed by the normal user; (see Section Permissions and Ownership). DOS and Windows, on the contrary, will let you wipe out the entire contents of your hard disk;
- there's a special user called ``root'': the system administrator, with full power of life and death on the machine. If you work on your own PC, you'll be root as well. Working as root is dangerous: any mistake can seriously damage or destroy the system just like with DOS/Windows. Don't work as root unless absolutely necessary;
- much of the complexity of Linux comes from its extreme configurability: virtually every feature and every application can be tailored through one or more configuration files. Complexity is the price to pay for power;
- redirection and piping are a side DOS feature, a very inportant one and much more powerful under Linux. Simple commands can be strung together to accomplish complex tasks. I strongly suggest that you learn how to use them.

### Getting Help

There are many ways to get help with Linux. The most important are:

- reading the documentation---I mean it. Although the HOWTO you are reading may serve as an introduction to Linux, there are several books that you really should read: at least, Matt Welsh's ``Linux Installation and Getting Started'' ( http://www.linuxdoc.org/LDP/gs/gs.html) and the Linux FAQ ( http://www.linuxdoc.org/FAQ/Linux-FAQ/index.html). Feel a guilty conscience until you have read at least one of them;
- the documentation of the packages installed on the machine is often found in subdirectories under /usr/doc/;
- to get some help about the ``internal commands'' of the shell, type `help` or, better, `man bash` or `info bash`;
- to get help about a command, type `man command` that invokes the manual (``man'') page of `command`. Alternatively, type `info command` that invokes, if available, the info page pertinent of `command`; info is a hypertext-based documentation system, perhaps not intuitive to use at first. Finally, you may try `apropos command` or `whatis command`. With all of these commands, press `q' to exit.
- finally, on the Internet: the right place for getting help is Usenet, like news:comp.os.linux.setup. Please don't email me for help, because I'm quite overloaded.

## 1.3 Conventions

Throughout this work, examples will often follow the following format: `<...>` is a required argument, while `[...]` an optional one. Example:

> `

>     $ tar -tf <file.tar> [> redir_file]

> `

`file.tar` must be indicated, but redirection to `redir_file` is optional.

``RMP'' means ``please Read the Man Pages for further information''. I can't stress enough how important reading the documentation is.

When the prompt of a command example is `#`, the command can only be performed by root.

Next Previous Contents