In a message dated: Tue, 09 May 2000 22:57:54 EDT
Benjamin Scott said:
>If we, as a group, have our own server, we are free to do what we want with
>it. If someone has a neat idea and the willingness to work on it, we can let
>them at it, and not have to worry about the politics of Someone Else's Stuff.
>
> Again, I don't want to sound like I don't appreciate the offer of the
>hardware -- I just think giving GNHLUG a server of its own would be the best
>thing to do, and I'm willing to foot the bill for the hardware.
>
> What do you think, Paul? What do others think?
export HAT=GNHLUG
Well, keep in mind, Derek, Kenny, and I are the sysadmins here. We are the
ones doing the configuring, and setting up the hardware. Additionally, we'll
be the ones to provide the adminstrator accounts to people external to MCL.
As long as 1 of us is here (and we're not going anywhere until *AFTER* the
IPO :), I don't think we have to worry about the politics of
"Someone Else's Stuff". We're planning on buying a pretty hefty Cobalt RAQ
3i for this purpose (though it will be used for some other stuff in addition
to GNHLUG).
I have no problems with GNHLUG obtaining/providing a system for this, and we
will gladly place it in the rack with our other servers.
If GNHLUG is going to provide a system, I would highly recommend looking at
the Cobalt RAQ 3i systems. They are a pretty decent machine, with a very
small form factor (1ux19"x12"). These machines retail for $2500+ (we get them
a little cheaper, but not much).
export HAT=MCL_sysadmin
Also keep in mind, you will never be "free" from the politics of that
"someone else" once the server is on someone else's network.
We are willing to donate not only the machine, but the space, electricity,
cooling, bandwidth (currently 2 T1s, but we're upgrading to a T3), and
possibly disaster recovery efforts (i.e. backups). Not to mention
general system adminstration time/services. This server will be up 24x7.
But with all that we offer, also comes certain compromises. There will be
very stringent security practices enforced on this box (as there are on
*all* of our systems outside our firewall).
My first responsibility is to MCL. I will in no way compromise the security
here.
export HAT=GNHLUG
That being said, I'm also not going to be so militant that GNHLUG can't do
what we need to do on this system in order to support our site.
Security will most likely consist of:
- turning off all "r" services (actually commenting out
everything in /etc/inetd.conf)
- allowing only ssh connections into the box for shell access
- restricting those with shell access to a limited group
of people (chosen by the members of the GNHLUG steering committee)
Of course, these security requirements will exist regardless of whether MCL
provides the box or not. If it's connected to our network, we have to enforce
good security practices. But there is nothing preventing GNHLUG from doing
what we want on the system, as long as it doesn't conflict with good security
practices. As I said before, this system can be used for anything LUG
related, including, but not limited to those things you listed:
- A central location for mailing lists
- Searchable mailing list archives
- A GNHLUG Internet Relay Chat server
- FTP space for whatever projects GNHLUG is working on
- CVS server for GNHLUG projects
- Interactive web applications for LUG organization -- things like
calendars, contact lists, and so on
- A place to demo things Linux can do (LDAP, for example)
--
Seeya,
Paul
----
"I always explain our company via interpretive dance.
I meet lots of interesting people that way."
Niall Kavanagh, 10 April, 2000
If you're not having fun, you're not doing it right!
