Re: ? four port NIC - Unknown if this is configured?

On Mon, 27 Aug 2007, in the Usenet newsgroup comp.os.linux.hardware, in article
<1188202883.234807.97770@xxxxxxxxxxxxxxxxxxxxxxxxxxx>, robertharvey@xxxxxxxxxxx
wrote:

NOTE: Posting from groups.google.com (or some web-forums) dramatically
reduces the chance of your post being seen. Find a real news server.

If this is truly going to be a server and you expect it to have a decent
lifespan (i.e. more than 6 months to a year) then don't use Fedora Core
anything,

If it's truly going to be a server, it doesn't want a "popular" distro
with lots of cycle-wasting eye-candy. The more sh!t you have running on
a server, the more things you have to secure because there are more things
to exploit. X does not belong on a server. Period.

I think this is fantastically important, and not widely enough covered
by the gutter press of the FOSS movement, who are much more interested
in sweetshopping than in proper advice. Just why would anyone want
their windows to wobble?

Why would they have windows installed in the first place? Not enough
skills to configure a system without it? There may be a hint buried in
there.

I know a couple of people who have recently installed BSD based
servers, and it seems to be a perfectly sensible thing to do. Even
ubuntu has a "long term support" version 6.06.

Use the operating system or distribution you are most comfortable with,
and know how to set up properly. The *BSDs, or even the "branded" UNIX
are no more secure than windoze95 if the idiot setting the system up
doesn't know what they are doing. The "popular" distributions, whether
Fedora, Mandriva, SUSE, *buntu, _or_what-ever_ may actually be slightly
worse in this regard as they tend to have the "let me help you" tools
that do _something_ but the user is never entirely sure what, unless
that user spends the time learning what is needed - in which case the
tools become less useful than setting things up by hand.

Most really important hardware support stuff gets backported sensibly.

For server applications, I'm not sure this is as critical than for the
desktop user. Spiffy new video card with a Gig of video RAM? Of what
use is that? Multi-port Gigabit NIC? How big is the pipe you're trying
to keep full? Fancy power saving (sleep mode) motherboard? Better be
very quick to wake up, as the client to your server is impatient.

Old guy
.

Relevant Pages

  • Re: 400 remote sites connected via DSL
    ... distribution point server share. ... If the SMS server is getting hit by all the clients at once, ... 2000 roaming clients downloading from remote distribution points. ...
    (microsoft.public.sms.swdist)
  • Re: server xloads on my desktop
    ... server xloads on my desktop ... GSSAPIAuthentication yes ... for the addressee and may contain confidential, ... unauthorized review, distribution or other use ...
    (AIX-L)
  • Re: schannel.dll, secur32.dll, and DSCLIENT.EXE redistribution
    ... > include it in the distribution package. ... > when not present in a client attempting to access server. ... >> distributing these DLLs to them, ...
    (microsoft.public.platformsdk.security)
  • Re: restrict design access
    ... on the server & multiple copies of the FE distributed to the various user's ... Your best bet here is to use the server path in the MDB with the linked ... References play no part in splitting a database... ... ready for the next distribution. ...
    (microsoft.public.access.modulesdaovba)
  • Re: SCCM Distribution Point Server share
    ... Actually there is one site server with all roles, but we want to place the distribution share Role on a seperate server. ... You said, that this szenario is not supported, so what kind of architecture works with storage who is not managed by Windows-OS like NetApp? ... Actually we don't want to use block based protocols like iSCSI which should work of course, but we need to access the packages and other files from different clients. ...
    (microsoft.public.sms.setup)