[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] excessive recursion
- Subject: Re: [cobalt-users] excessive recursion
- From: baltimoremd@xxxxxxxxxxxxxxx
- Date: Mon Feb 5 06:28:01 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Sun, 4 Feb 2001, H.P. Stroebel wrote:
>
> BTW : did I mention that the GUI introduced syntax errors in
> /etc/named.conf ?
I have spent the last few months getting used to the "Cobalt Way",
reading the Knowledge Base and the archives...and reached the conclusion
that either I am not a good reader, or that there seems to be no
central list of
A. Known Bugs in the "Cobalt Way"
B. Known "Cobalt Way versus the rest of the world" list of
implimentations
C. Known fixes for either of the above
If there is such a thing, I'd love to know about it.
If there is not such a thing, it might be of benefit to create one...that
would cut down the number of duplicate and/or inaccurate posts on an
issue, the numerous "look in the KB and/or look in the archive" that have
no reference to specific entries for a specific issue.
Some time ago I offered to setup an online database of such things...but
the majority of the comments were in the vein of "I don't like your
program, design, breath, etc."
It strikes me that Cobalt should be supplying the information about known
bugs and strange implimentations, and as reasonably efficient managers we
should be able to document what they don't.
If I was a "guru" I'd just write it all and post it...but, being a newbee,
I don't know enough to be more than dangerous.
However, if folks who do know are willing to share, I'd be happy to
compile something...and instead of vague references we all could look
at a specific location/page/document to answer what seem to be ever
repeating questions.
Who knows, maybe even Cobalt might take the position that the list of bugs
and "features" were valuable contributions from their paying beta
testers(those of use that have purchased the units) and consider either
making changes or supplying information that would allow work-arounds.
Thom
././././././././././././././././././././././././././././././././././././././
baltimoremd@xxxxxxxxxxxxxxx Thom LaCosta K3HRN Webmaster
http://www.baltimoremd.com/ Baltimore's Home Page
http://www.baltimorehon.com/ Home of the Baltimore Lexicon
http://www.zerobeat.net Home of The QRP Web Ring
and Drake Mail List Pages