[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-developers] What makes a RAQ a RAQ?
- Subject: [cobalt-developers] What makes a RAQ a RAQ?
- From: "Hosting Sales" <hosting@xxxxxxxxxxx>
- Date: Fri Sep 14 14:50:33 2001
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
If you have worked extensively with "traditional" Linux-based servers
and compare the internals of same with the RAQ (my issue is the RAQ3
specifically), what you see is not pretty. The RAQ has a GUI that,
while helpful to those unfamiliar with Linux, Apache, Sendmail, etc.
administration, precludes (and, in fact erases) file edits that are
consistent with and an integral part of the aforementioned packages
provided by the developers to implement some worthwhile features. More
distressing, you see in the RAQ a collection of woefully outdated
software, some two years old yet under active development and
improvement by the open source community. Sun makes packages available
only after it can tweak them to not interfere with the GUI. Fair
enough. But what about those who want to run a "real" Linux that is
free of the GUI and its restrictions? Ignoring the issue of "breaking"
the warranty, what are the items that have to be addressed? In other
words, what (from a hardware/OS internal viewpoint) makes a RAQ a RAQ?