Re: [cobalt-users] Location of Apache Daemon

["Jim Jeup" <raq3@xxxxxxxxxxxxxx>]

> How is it making this harder for you?  By using the
> RedHat file system layouts?  I wouldn't call this
> making things harder for the average user.
>

<rant>
If you alter those layouts, you break what the Raq was purchased for... GUI
interface.

If you alter the Apache files, you break what the Raq was purchased for ...
GUI interface.

One cannot use a RedHat book to learn the Cobalt system.

One cannot use a Apache book to learn the Cobalt system.

One cannot get a Cobalt book, because they don't have one.

I know the answer to this... just buy a Restore disk, and a
spare-in-the-air... but, don't try to restore files to the Raq, because
there is a bug... you can backup the system, but not restore.

Most likely, before the system is changed over, the hard drive will be full,
because the log files can't be deleted easily. But, this is not a problem...
because there are NO man files about Cobalt's proprietary system.

But, this is no problem... before you can find the information about the
system (Raq3 is definitely not in the knowledge base), one of Cobalt's
recommended packages will render your system unusable.

But, this is no problem... they have an experimental patch for the problem
that, when installed, voids any warranty on the system (because it is
experimental and not supported) {by the way, this particular statement is
unsupported and can be considered a rant :)}

But, this is no problem... one can get support in their first 30 days of
ownership (the following is a true story). You can submit a request for
assistance using Cobalt's web interface (you know... the one that states
someone will contact you back within the next day.... yeah right!) And not
have it answered for 45 days. After following the instructions (you know
diagnostic dump and all that...)You can call on the phone... and leave
several messages that were NEVER returned. Then, about a month-and-a-half
later, receive a call asking if we ever "got it worked out".

But, this is no problem... the unit was purchased with the idea that it
would make the company money. It was not purchased as a neat toy that will
need to be broken down folder-by-folder to see why the GUI interface is
broken each time something is done through telnet (i.e. does not appear in
the GUI interface). Teaching new employees how to work with the system
should not be like pulling teeth. Straight Linux with Apache isn't (with a
few Perl scripts and some cron jobs)

We're not asking for the world, just a book, or anything else that has
pertinent information about the system.

I do use Linux, I do use Apache. These are simple and easy to understand.
What Cobalt has done to the system could be documented, and hacked with
little problem. If they had any truly pertinent information. Heck, I'd even
pay for the darned thing.

But, it all goes to the fact that the unit is not quite what it should be.
Or, maybe it is. But, we can't tell, because there is no pertinent
information to go by.

Imagine giving support (NOT AT $200) for the first unit. Gee, after that,
the next 50/100 wouldn't even need support. It would have been done on the
first unit.

Most of the clients that we have had to walk through hosting by the hand,
have turned out to bring allot of referrals, and fewer questions.

</rant>

There, I said it and feel better for it.


Jim