Free faq software for linux

DBI::FAQ is a Perl module for the Frequently Asked Questions of the Perl5 Database Interface.

What is DBI, DBperl, Oraperl and *perl?

To quote Tim Bunce, the architect and author of DBI:

``DBI is a database access Application Programming Interface (API)
for the Perl Language. The DBI API Specification defines a set
of functions, variables and conventions that provide a consistent
database interface independant of the actual database being used.

In simple language, the DBI interface allows users to access multiple database types transparently. So, if you connecting to an Oracle, Informix, mSQL, Sybase or whatever database, you dont need to know the underlying mechanics of the 3GL layer. The API defined by DBI will work on all these database types.

A similar benefit is gained by the ability to connect to two different databases of different vendor within the one perl script, ie, I want to read data from an Oracle database and insert it back into an Informix database all within one program. The DBI layer allows you to do this simply and powerfully.

DBperl is the old name for the interface specification. Its usually now used to denote perl4 modules on database interfacing, such as, oraperl, isqlperl, ingperl and so on. These interfaces didnt have a standard API and are generally not supported.

Heres a list of DBperl modules, their corresponding DBI counterparts and support information. Please note, the authors listed here generally do not maintain the DBI module for the same database. These email addresses are unverified and should only be used for queries concerning the perl4 modules listed below. DBI driver queries should be directed to the dbi-users mailing list.

However, some DBI modules have DBperl emulation layers, so, DBD::Oracle comes with an Oraperl emulation layer, which allows you to run legacy oraperl scripts without modification. The emulation layer translates the oraperl API calls into DBI calls and executes them through the DBI switch.

Heres a table of emulation layer information:

Module Emulation Layer Status
------ --------------- ------
DBD::Oracle Oraperl Complete
DBD::Informix Isqlperl Under development
DBD::Ingres Ingperl Complete?
DBD::Sybase Sybperl Working? ( Needs verification )
DBD::mSQL Msqlperl Experimentally released with
DBD::mSQL-0.61

The Msqlperl emulation is a special case. Msqlperl is a perl5 driver for mSQL databases, but does not conform to the DBI Specification. Its use is being deprecated in favour of DBD::mSQL. Msqlperl may be downloaded from CPAN via:

http://www.perl.com/cgi-bin/cpan_mod?module=Msqlperl

PDL::FAQ is a Perl module for frequently asked questions about PDL.

This is a considerably reworked version of the PDL FAQ. As such many errors might have crept in and many updates might not have made it in. You are explicitly encouraged to let us know about questions which you think should be answered in this document but currently arent.

Similarly, if you think parts of this document are unclear, please tell the FAQ maintainer about it. Where a specific answer is taken in full from someones posting the authorship should be indicated, let the FAQ maintainer know if it isnt. For more general information explicit acknowledgement is not made in the text, but rather there is an incomplete list of contributors at the end of this docuement. Please contact the FAQ maintainer if you feel hard done by.

XBase::FAQ is a Perl module with frequently asked questions about the XBase.pm/DBD::XBase modules.

This is a list of questions people asked since the module has been announced in fall 1997, and my answers to them.

The Faq-O-Matic is a CGI-based system that automates the process of maintaining a FAQ list. It allows visitors to your FAQ to take part in keeping it up-to-date. A permission system also makes it useful as a help-desk application, bug-tracking database, or documentation system. Jon wrote an article about the FAQ-O-Matic that appeared in the USENIX ;login: newsletter: http://www.usenix.org/publications/login/1998-6/faq.html.

This documentation itself is, naturally, maintained with Faq-O-Matic. Hence the weird title. If you see anything that can use updating, please do fix it! If you just want to play around, check out the (Xref) Playground.

A mailing list is very good because it gets together people who have questions with people who have answers.

A mailing list archive is even better, because it lets thoughtful people with Frequently Asked Questions search for an immediate answer, and avoid bothering the people who have answers. Unfortunately, the answers in a mailing list archive become stale over time, are disorganized, and are hard to sift from the conversational noise of the mailing list.

A Frequently Asked Questions list (FAQ) is even better, because the people with questions can be a little lazier and still find their answer right away. Unfortunately, maintaining a FAQ list requires effort; if the people with the answers become lazy, the FAQ list becomes stale.

I wrote the FAQ-O-Matic when I found myself frequently answering a certain question on a mailing list. The FAQ for the list had become stale (its creators interest had succumbed to laziness), and I knew I was far too lazy to take over maintaining my own FAQ.

So, in a triumph of laziness, I wrote the FAQ-O-Matic. The idea is this:

- People with answers can submit them to the FAQ, but
nobody is responsible for knowing all the answers.

- People with corrections can make them to answers, but
nobody is responsible for coordinating corrections.

This worked pretty well, but the first FAQ-O-Matic tended to become disorganized, since no-one was responsible for its structure. So I added commands to move answers and categories around, plus a Moderator feature that lets one person keep track of changes to the FAQ by e-mail:

- A person can keep a subset of the FAQ organized, but he
or she doesnt have to know all the answers or organize
the whole FAQ.

So a FAQ-O-Matic is something that lets the members of a community share the tasks of entering, correcting, and organizing frequently-asked questions and answers. Many folks have found other uses for FAQ-O-Matic, treating it as a general collaborative editing tool.

phpMyFAQ is a multilingual, completely database-driven FAQ system. phpMyFAQ support various database systems and it also offers a content management system with a WYSIWYG editor, an image manager, flexible multi-user support, a news system, user tracking, language modules, templates, extensive XML support, PDF support, DocBook XML support, a backup system, and an easy to use installation script.
Main features:
- Varius supported database systems:
- You can use MySQL, PostgreSQL, Sybase, MS SQL Server, IBM DB2, MaxDB or SQLite.
- LDAP integration:
- Add your companys LDAP based user management into phpMyFAQ
- Content Management System:
- You can administrate your users, news, themes, categories and records in the password protected admin area.
- User Administration:
- Selected users can edit and administrate records.
- Record Administration:
- Your users can write new records, the administrator has te unlock the record. The admin can also edit the record, move into a another category oder delete the record.
- WYSIWYG editor:
- Write your articles like you do in OpenOffice.org or Word.
- Image Manager:
- The Image Manager provides an web interface to browse for image files (JPEG, PNG, GIF, and others) on the web server.
- News Administration:
- Write news that appear on the FAQ mainpage.
- User-Tracking:
- Analyze the way of your users through your FAQ.
- User-Voting:
- With the voting of the users you can analyze the quality of your records.
- Top 10:
- Youll get a Top 10 with ten of the most popular records.
- Language files:
- phpMyFAQ supports more than 25 languages including Arabic, Chinese and Vietnamese.
- Multilanguage support:
- Write records in different languages.
- Search engine optimization:
- Support for Apache mod_rewrite and IIS ISAPI_rewrite
- Firefox search plugin support:
- Search through your FAQ using Firefox search
- Sitemap:
- Lists all FAQ articles in a alphabetical order
- Template system:
- Custimize your FAQ to your webdesign.
- Simple installation and configuration:
- Install and set up your FAQ only with your browser!
- 5 different views for records:
- XHTML, printer optimized XHTML, PDF, DocBook XML and plain XML
- XML-RPC interface:
- Support for searching over the internet.
- Backup:
- export and import from SQL tables
- Community module:
- Users can write questions to the system, so that other user can answer these questions.
- Send2Friend:
- User can send records up to five friends with email.
- PHP 5.x ready
- phpMyFAQ 1.5.x works with PHP 5.x

iFAQMaker provides a PHP class for easy maintenance of FAQs.
iFAQMaker is a PHP class for easy maintenance of FAQs, but it can be used for other things (like program documentation) as well. It is easy to use and works out of the box.
Main features:
- Inserting/Deleting/Moving single topics (within the same FAQ file) without the hazzle of reorganizing indices, numberings and links
- Use of templates to display the FAQ corresponding to the web site design
- Use of user-definable makros for frequently used formatings etc.
iFAQMaker needs no database or the like - it simply works with files. In general, we can distinguish between the program code, configuration, and content files. One central index.php file is the only one to be called within the browser.
It takes the topic to display as only argument, which is at the same time the basename of the content file to parse (without the extension): so
http://www.myserver.tld/faq/index.php?topic=faqmaker
parses the faqmaker.txt content file and displays it according to your setup.

Device::USB::FAQ Perl module contains Frequently Asked Questions for Device::USB.

This is an attempt to answer some of the frequently asked questions about the Device::USB module.

Which platforms does Device::USB support?

Device:USB supports any platform that libusb supports. This list currently includes Linux, FreeBSD, NetBSD, OpenBSD, Darwin, and MacOS X.

There is a port of the libusb library to the Windows environment called LibUsb-Win32. Because I dont have a development environment for testing this library, Device::USB does not yet support this library.

Do I have to use Device::USB as root?

By default, access to the USB devices on a Unix-based system appear to be limited to the root account. This usually causes access to most of the libusb features to fail with a permission error.

Using the Device::USB module as root avoids this feature, but is not very satisfying from a security standpoint. (See the next question for more options.)

How do I enable use of Device::USB as a non-root user?

Some of the attributes of USB devices are available to non-root users, but accessing many of the more interesting features require special privileges. According to the libusb source, the open() function requires either device nodes to be present or the usbfs file system to be mounted in specific locations. Those places in order are:

1)
/dev/bus/usb - pre-2.6.11: via devfs / post-2.6.11: via udev
2)
/proc/bus/usb - usbfs

Look in both locations on your system for which of these two methods your libusb will use.

No matter which method your system uses, you will probably want to create a separate group to control access. Run this command to add a system group:

addgroup --system usb

or

groupadd --system usb

You can then add users to that group to allow access to your usb devices.