From: "Eve Atley" <eatley@wowcorp.com>
To: linux-admin@vger.kernel.org
Subject: Red Hat Enterprise Linux WS or ES for server?
Date: Wed, 22 Dec 2004 15:50:00 -0500 [thread overview]
Message-ID: <000001c4e867$ce7b9e60$1f0aa8c0@lanadmin> (raw)
We are a small company (less then 20 people) that is currently running
Redhat Linux 9 as a fileserver. We have a firewall router set up currently
that is wreaking havoc, and we had previously had used the Linux box as a
firewall and router hooked up to our shared T1 line. We're looking to return
to that system again. With cost as a factor, can we get away with Redhat
Linux WS for this purpose?
Additionally, we had abandoned the Linux system as a firewall/router for 2
reasons: to be less machine dependent, and because our ethernet cards kept
insisting on switching upon reboots (thereby causing all sorts of problems).
If we upgrade to ANY version of Redhat Enterprise, would this solve our
issues at all, or are we totally barking up the wrong tree? The system
should probably be upgraded anyway as the GUI is as slow as molasses.
Thanks so much,
Eve
next reply other threads:[~2004-12-22 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 20:50 Eve Atley [this message]
2004-12-22 20:48 ` Red Hat Enterprise Linux WS or ES for server? Hal Wigoda
2004-12-22 21:07 ` Jens Knoell
2004-12-22 21:24 ` Scott Taylor
2004-12-23 1:19 ` chuck gelm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001c4e867$ce7b9e60$1f0aa8c0@lanadmin' \
--to=eatley@wowcorp.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).