[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-developers] Just RaQ2 hardware...



Hi,

> I'm seriously considering "forgetting" about the RaQ2's gui web-based user
> interface and going strictly with telnet support.
> If I abandon it, I won't have to worry about messing it up.

	Yup. Thjere's soo much to 'break' in the GUI. The other problem is,
when you go back to do something else with the GUI, you don't know what
stuff that you've done is gonna break.

> Has anyone done this?  What do you think of it?  Any caveats?

	One of the first things I did when I got a RaQ was abandon the Cobalt
GUI and start developing my own for use by me and my co-workers (who
aren't too savvy with the operation of apache). This means that I can do
things without fear of breaking other things. Also, when the news broke
about the hole(s?) in the Cobalt UI, Iwas able to completely disable the
thing without any problems.

	The only probs that I've noticed are that the monitoring tools use the
data from the GUI to work. You will notice this as soon as you change
quotas for instance.

Dave

--
David Sexton

Network Technician
Sapphire Technologies Ltd.
Tel: +44 (0) 1642 702100
Fax: +44 (0) 1642 702119


-----------------------------------------------
Any opinions expressed in this message are those of the individual and not necessarily the company.  This message and any files transmitted with it are confidential and solely for the use of the intended recipient.  If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this message in error and that any use is strictly prohibited.

Sapphire Technologies Ltd
http://www.sapphire.net