I also am looking for something to collect documentation tidbits into a DB that 
all can contribute to. We do have a need to search and organise though. We are 
a very small group (6 ppl) and are only doing the occaisional DB updates and 
compilations. I was considering just writing my own software with PHP/MySQL but 
found MySQL to be a memory hog so am unsure how that will affect us. We are 
also somewhat constrained with z/Linux under a z/VM guest.

Is wiki not the way for me to go?

thank you, gurus


----- Original Message ----
From: Alan Cox <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, May 16, 2007 1:57:59 PM
Subject: Re: Wiki


> I am considering using Wiki to organize and make available some of the IT 
> documentation that is
> spread all over my shop. After looking I fount that there are several Wiki 
> engines available. Which
> one is the best?  Is that like asking which editor is the best?

Wiki does not "organise". One of the reasons I despise Wiki for a lot of
things is that it has no categorisation generally speaking. Some like
Mediawiki at least have good search but its not substitute for structure
- either enforced by a good editor or content managers that deal with
what/where something belongs.

> MediaWiki will run on Debian-390. Is anyone running a Wiki on a mainframe? Is 
> that a good place to
> run one?

Its capable of being quite a CPU hog under heavy use. I guess it depends
on the userbase. You could always put the db on the mainframe and the
engine on a PC I guess

Alan

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to