Networking Linux

[kingswood]

OK.

So we have about 30 machines (with pretty low spec- around 300-600MHz processors and 128MB RAM) that I think could be used for Fedora Linux/RedHat stations. I would like to test several out first with a Linux server. What's the best way of doing this so that the setup is secure?

I have looked at the LTSP (looks neat) and also Linux for Schools. I'm familiar with SAMBA and NIS/NFS. But which would be best to use- a SAMBA server (using SMB) or a real Linux networking solution like NIS/NFS--or something else?

Purpose of stations? Probably internet access and break-time work like typing assignments etc. Nothing too heavy.

Any advice out there?

Thanks,

Paul

[ChrisH]

Maybe you could turn the machines into thin clients instead if they are going to be limited in what they do. You could use a Linux distro on the clients and us Terminal services on a server with beefed up ram.

[Ric_]

I use Thinstation (http://thinstation.org) on most of by boxes cos they are rubbish (your low-spec machines make mine pale into insignificance!)

If you go for about 30 clients you could use a P4 with a couble of gig of RAM as your server and use Terminal Services in Windows 2003. You would of course need server CALS (approx. £5ea) and TS CALs (approx. £12ea).

[Geoff]

I'd go with Ric's advice if there's a requirement to use windows apps.

If not you can use a Linux terminal server. The Linux Terminal Server project is perfectly sufficent for this.

As for the nuts and bolts. NIS/NFS is sufficent for a small deployment. For a larger project you should replace NIS with LDAP. There's no need for Samba unless you want people on the thin clients to have access to their files on the windows server(s). If you do want that, its best done on the terminal server rather than the thin client.

[kingswood]

Hi people.

Great advice- lots to consider. Thanks!

I'm leaning towards a Linux only LTSP solution at the moment. Although I also like the idea of LDAP. I thought about SAMBA but didn't see a real need to use unless (as you say) we need to access user-related files on the server. I'd rather not do this, but it's something I could hold in reserve I suppose.

Oh well- off to the grind-stone.

Thanks again,

Paul

[Geoff]

Well I suppose it depends how far you want to go with it. Its probably best to start small and simple. There's nothing to stop you revisiting it at a later date and extending the functionality to include Samba/LDAP/etc.