Date: Tue, 13 Apr 1999 04:50:19 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: chris@calldei.com, Mattias Pantzare <pantzer@ludd.luth.se>, Amancio Hasty <hasty@rah.star-gate.com>, Dmitry Valdov <dv@dv.ru>, Brian Feldman <green@unixhelp.org>, freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) Message-ID: <199904131150.EAA14736@apollo.backplane.com> References: <199904102051.WAA07790@zed.ludd.luth.se> <199904102057.NAA01570@apollo.backplane.com> <19990413004728.C1968@holly.dyndns.org> <37131436.644E6E48@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:What you really mean is that "FreeBSD is not a solution for public
:shell systems", correct? Public shell systems is not a bad idea,
:it's a business opportunity and a public service. If the OS is not
:up to the task, don't blame the task.
:
:--
:Daniel C. Sobral (8-DCS)
I would note that BEST.COM has been running, effectively, public shell
systems for 5 years. The last couple of years have been using FreeBSD.
It works just dandy. We put 2000 users on each box.
Just because people aren't willing to spend thousands of hours making
the kernel handle every conceivable user abuse doesn't make the machine
a bad solution for a particular problem. With that sort of attitude,
no operating system ever made could live up to your standards. FreeBSD
does the things most easily handled in a kernel. You, the sysop, are
supposed to do the things that are most easily handled by a sysop. That
is inclusive of writing monitoring and kill scripts.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904131150.EAA14736>