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.
Distribution: Solaris 9 & 10, Mac OS X, Ubuntu Server
Just a further comment on rsh vs. ssh -- even if I were not changing OS's, I would change from rsh to ssh. rsh is not secure for many reasons. It basically means that if anyone gets into one of your machines, they've got them all.
I use Amanda for backup. One option with it is to use ssh authentication and connections between backup server and clients. You can set up public key authentication, and you can restrict the keys. So, for example, the backup user on the server has a public key which is distributed to the clients. The client's backup user implements those keys with restrictions that allow them to be used only with one particular command (for backing up) and blocking portforwarding, x forwarding, etc. When I set something up like that, I typically reference http://sial.org/howto/openssh/publickey-auth/. The man page for sshd(8), `man -s 8 sshd`, also has details under Authorized_keys File Format. You end up with the ease of use of rsh, automatic login without passwords for automatic processes like backup, but with secure restrictions so that if someone were to break into one machine they wouldn't have access or free reign on any other machine.