Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
I'll take a beating on this, but you simply cannot, in any cost effective manner, replace all Win2k3 Srv's functionality with Samba. You will lose out on Group Policy (though old, best forgotten, NT4 style group policy will work -- to the extent that ever worked), any WSUS installation and some smaller things. Those first two are killers as they alone ease admin burden a ton.
Even a basic migration from WinSrv to Samba with LDAP backend is a real chore.
Samba is VERY good as a member server of an AD domain and will happily play along with MS's implementations of Kerberos and LDAP as well as Distributed File System...very nice.
So, if it's a "must do" project, I'd look first at how you're going to handle Group Policy and patching. Samba hits the high points on most of the rest. Also, investigate the use of Posix ACLs on the partitions/filesystems where Samba shares are mounted. ACLs and certain Samba settings put the frosting on the cake when trying to create a client experience very nearly indistinguishable from Windows Server/LanMan.
If this is just a home system, or a small office network (say <50 users) then you might have a look at SME server.
SME is an idiot proof (as near as that can be) Linux install based (on CentOS 4.4) that can be a DC, file server, web server, mail server, fax server, print server and many more. It has a very active support community and is free.
Do a Google search for SMEserver
That page has links to the Downloads, Documentation, user forums, the Contribs (what they call addons - as in Contributions) and Howtos.
I have been using it for 3 years, updating automatically as updates become available, both at home and at the small not-for-profit offices I support. It just works!