Hello I'm a newbie at the Linux world. I'm a certified Microsoft Trainer and want to add more Linux knowledge to my networking lessons. At this moment I'm writing a new part for my networking curriculum. In this part I want to describe something about what solutions to use in Linux networking.

I'm working on central and distributed authorization and file sharing.

My questions is, what solutions should I describe, which method is most common at companies using Linu.

Thus far I came up with the following conclusions:

File sharing:
NFS for linux <-> linux communication
Samba for linux <-> Windows communication
Samba for linux <-> linux communication

Is it wise to explain NFS or is Samba more common.

Authorization:
/etc/passwords local authorization for small environment
NIS distribution of /etc/password for larfer environment, is an old technique, but still often used
LDAP through PAM, connection to Novell's eDirectory of Microsoft's AD

Is it wise to explain NIS or is it to old.

Regards

Erik Verberne

I've never gotten a client that was 100% linux/unix, so I'd say focus on Samba. It can integrate into 2000/2003 networks for File/Print servers inside Active Directory, Terminal Services, Web & FTP. Although it can do more, those are the implementations in the Real World that I've run up against. Another huge benefit for small offices and "Mom & Pop" type shops in using Samba as a PDC emulator. This saves them a bunch while still securing and centralizing their network. I'd say Samba is more common, but both have strengths.
NFS is a great tool if you can understand its benefits. I've seen it go to waste because of a lack of vision though (as with some of the peoples visions about linux).

I've never had to play with NIS/NIS+. Perhaps its is old and out-dated. LDAP, PAM, & Kerberos can seemlessly integrate a linux box into an existing Directory structure.

I'd recommend the "Official Samba3" book. It was an easy read and had great examples. It did lack a little of the technical explainations, but samba.org is good for that.

---
<EDIT>
Also check Samba-TNG. Though I've never implemented it, I like to keep up on what new tricks they are working on.
</EDIT>

Just as an added extra to the fairly comprehensive response from musicman_ace, LDAP is becoming more commonly used with OpenLDAP or similar, rather than purely used to tie into existing directory structures. We're currently doing a lot of work with OpenLDAP as the backend to Samba servers, so that even Windows clients login in via Samba, pulling data from the OpenLDAP database, and with Linux machines doing this via nss_ldap and changes to PAM.

As for NIS, it is largely outdated as you mentioned, due to extra functions available in more feautre-rich directory structures, but it's probably worth at least going over what it is, as your students may well encounter environments setup running NIS, even if you wouldn't neccessarily implement it from scratch. Depending on how much control you need, NIS may well be adequate enough in some situations even now.

Hi! I'm an administrator in a university campus. I have 2 questions:
1) How do you think, is it right decision to use authorisation through LDAP and to have NIS responsible for managing fstab, services, etc?
2) It is posibble to have 1 fstab file in lan?

Thanks

Welcome to linux/*nix.
But Cetification of MS doesnt matter much in this part of world. Being more technically correct is the utmost requirement as per my view.

Regards
..amit..