[KrudUsers] Distributions and support
efm at tummy.com
efm at tummy.com
Tue Nov 4 11:34:17 MST 2003
As several people have mentioned already, tummy.com provides support for a
wide range of Linux distributions, not just KRUD.
There are several different levels of support required to keep a Linux box
running effectively:
Operating system updates - from updating packages to get new features,
to installing new distribution versions.
Security updates - these are applied as they become available, and are
usually distribution specific.
Initial installation support - this includes getting the base OS on the
system, doing a burn-in of the hardware, and making sure that the system
is up-to-date so that it can be safely put on the network. Having a
fully patched distribution available for doing installations is the
original reason we started doing KRUD, and it's the biggest reason why
we ship it only on CD.
Application installation support - installing, configuring and
documenting a specific application, such as a mail server, a database or
other specific application. This involves installing required software,
making sure the software is configured for your specific needs, and
testing it. Sometimes we write custom RPMs for doing this, such as
QmailInstall, or the Python RPMs.
Ongoing support - this includes monitoring, log reviews, security
audits, and training.
Only the initial installation and updates (both OS and security) are
distribution specific. Often times the application choice, such as Oracle
database, restricts which distributions can be installed.
As of today, we're doing 6 versions of KRUD and KRUDserver:
KRUD 9
KRUD 8.0
KRUD 7.3
KRUDserver 9
KRUDserver 8.0
KRUDserver 7.3
We're planning on offering these distributions:
A KRUD version based on Fedora
Security updates for 7.3 in 2004
Security updates for 8.0 in 2004
In order for us to do versions of RH Enterprise AS, WS and ES, we'd need to
remove all RH logos, license a JVM, and recompile everything from source.
We could do that. The question is, will it help anyone? It sounds like many
of the people who are looking for us to do this are unhappy with the
per-machine license. The big question for me is, is that per-machine
license a restriction place by the JVM license? If it is, there's no way
that tummy.com would be able to do anything different, or anything cheaper.
And, as several people have mentioned, the 3rd party commercial
applications may not be supported on a recomplied version of RH.
We do KRUD because it fills a real need for us: to have a regularly updated
version of Linux for doing fresh installs and for maintaining the servers
we manage.
We share KRUD with others because we think it fills a real need for them as
well: to have a convenient method of doing fresh installs and updating
existing servers.
Other than saying "We support Enterprise AS, WS and ES", what would doing a
version of KRUD based on those three versions of RH get people?
It might be possible to do a site license rather than a per-machine
license
CDs are more convenient for doing installs and for setting up update
repositories
tummy support is more responsive than RH
There may be trouble with 3rd party commercial software vendor support
And if we didn't do a version of KRUD based on AS, ES and WS what would we
be doing:
Providing responsive, qualified support for all versions of KRUD,
KRUDserver, RH Enterprise AS, WS and ES, and Debian
Shipping KRUD (9, 8.0, 7.3), KRUDFedora (which will eventually become
KRUD), KRUDserver
Creating both free and commercial RPM packages
I apologize for being cautious about this choice. I just want to make sure
that if we plan on doing a KRUD version of AS, WS and ES, we're filling a real
need. And that the need we're filling is one that adds real value to our
customers and the community.
--
Regards, tummy.com, ltd
Evelyn Mitchell Linux Consulting since 1995
efm at tummy.com Senior System and Network Administrators
http://www.tummy.com/
More information about the KrudUsers
mailing list