[Gloucs] Linux information

[Sean Keane]

Some time around Monday 31 Mar 2003 15:47, Paul Spencer slipped on a keyboard 
and came up with:

> Hello,
>
> Could you inform me of the benifits/disadvatages of using Linux
> client/Linux server over windows.

No, not easily.  It depends a lot on what server applications (and indeed what
client software) you want.  It also depends a lot on what you're using it/them
for.  It pains me to say it, but a linux solution is not always the answer.

> Which Linux software would be best to use on a client/server i.e. 
> redhat/mandrak etc.

OK, firstly Redhat, Mandrake et al are what we call distributions, not just
software packages.  They come with a kernel (sometimes several), which is 
your basic OS, and heaps of both client and server software depending on
which.

So first, a question, and appologies if it's condescending...

Do you know the difference between a client and a server?

> Also what Linux software would be required for a client/server system 
> package i.e. email, word etc.

Um... OK, word processors are generally workstation apps, not server, although
that's possible too.  Perhaps, I'm thinking, you consider a server to be 
like the Windows Terminal Server edition? Hrm...  It could be done... both
ways...

> Is it possible to connect a windows client to a Linux server and how would 
> this be achieved.

Yes, and depends what you want to do with it.

> How would you implement a system with a Linux server which
> includes the firewall software and email software and a windows server used
> for applications.

Most linux distributions have a packet filter (ipchains/iptables) built in.
It's a basic firewall on a sockets level.  i.e. it doesn't take note of the
application, just what it's doing and how.

> Would the client retrieve emails trough the Linux server or would they 
> retrieve the emails through the windows server.

However you prefer.  Again, most linux distributions have at least one mail
server built in, usually several.  Email can be stored, used locally, 
forwarded to your windows box, whatever.

> Also is it possible to protect a windows server from security risks like 
> email and firewall with a Linux server. Also how would this be implemented.

Yes, but it's way to complicated for an email.
However, if you had f'rinstance, a spare box (eg. old P166) doing nothing, it
could be installed with linux, without the pretty GUIs and so forth, but with
iptables and routing enabled.  I would also suggest this be your "gateway" box 
- which would be the dial-up machine if you were on a modem.  The combination 
of firewall rules and routing rules could be set (actually easier to do than 
to describe) so that nothing from the outside ever finds your windows box.  
Of course, this won't protect it from vulnerabilities started inside... eg, a 
programme carrying a trojan that tunnels out rather than in...

Anyway, this is getting long and I haven't had my coffee yet so...

1. Linux and Windows will co-habit on a network happily enough in any 
combination of clients and servers.
2. There is linux software available (usually supplied in the box) equivalent 
to most of the office applications you use.  I suggest looking at 
www.openoffice.org for one example that will run on both linux and windows.
3. Linux is very well adapted to server operations, and as you've probably 
read, is getting popular on the desktop too.  You would probably not need a 
windows box with it, but note I said probably.  You'd need to relearn a lot 
of stuff - simple stuff maybe, but...
4. As with all firewall applications, it's only as secure as the rule set.
5. As with Windows, Linux is only secure if you keep it up to date... at least 
the applications you use.

Basically, I'd suggest you come along to one of our meetings (Cross Keys, 
Barnwood Rd, Gloucester, 4th Tuesday of t'month) and speak to people.  We 
don't bite... well, not all of us anyway.

-- 
Sean Keane @ Work
Powered by SuSE Linux
  8:46am  up 111 days, 19:10,  1 user,  load average: 0.04, 0.03, 0.00