Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z - Internet FAQ Archives

alt.bbs.unixbbs Frequently Asked Questions
Section - drealm

( Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Sex offenders ]

Top Document: alt.bbs.unixbbs Frequently Asked Questions
Previous Document: Commune/IX
Next Document: EBBS Eagle's Nest BBS
See reader questions & answers on this topic! - Help others by sharing your knowledge

DRealm                  GNU License              source included

     contact:   Peter Jones

     demo:      drealm BBS
                +44 (0)181 568 2204     v.34
                           568 4318     HST/v.32
                           568 4305     v.32
                           232 8592     v.22bis

This is the blurb that came with version 2.1 (released 5/96).

drealmBBS is a multi-user BBS system.

drealmBBS runs a separate process for each node, and finds out about
other nodes by interrogating certain files on disk and via IPC.  It
needs about 1Mb virtual memory per user.

ALL data is produced and stored as plain ASCII so it can be accessed by
any other application.

It is highly configurable.  All menu options can have access controlled
by user level, userflags, areaflags, and min/max times of day.  Menus may be
presented in plain text or graphics standards such as ANSI.

You may offer your callers any of eight external file transfer
protocols, any three editors and any three display programs.  We have
included our own line editor (isle) and our own display program (pager)
which are both absolutely free of shell escapes and command access.
There is support for output in up to 10 human languages or styles.

Each BBS user has his/her own account in the passwd file, but may of
course run drealmBBS as his shell for security.  Security is also aided
by reverting user to login permissions when using external file transfer
protocols, editors or file viewers - and other external programs

Facilities include:

Private inter-user mail, with interface to external mail.  A quota of
external mail can be set per person, and mail can be made available only
to users over a certain level or with a certain flag set.

Message areas (forums):  Public messages are posted without naming a
recipient and can be read by anyone who may access a particular area.
Areas can be open or private, read only or read/write or moderated.
Each area may have an individual areamask, which represents the flag
settings of the users who may access it. An area may also be restricted
to people of over a certain security level.  In the case of a "private"
area access is restricted to only people who are specifically named
within that area.  Messages are linked as threads, and may be read
threadwise, numerically, or by "reference" (ie always reading down
through replies first).  Messages may be unlinked, relinked in a
different way, and copied to other message areas.  Whole threads or
branches may be copied to other areas, retaining their relationships.

Voting:  Votes are attached to public messages.

File up/downloads:  Functions to descend through directories and
re-ascend. File descriptions held.  Files may be posted between
individual users.  No internal protocol provided, you can use any which
are available on your system.  Rename, delete, edit, view files.
Searches recursively from any named parent directory on filenames or
file descriptions.

Chat:  Realtime chat on a message by message basis via pipes and
sockets.  Users can chat and listen whilst doing other things.  Users
can select chat reception on or off.  Menus may disable or enable chat
at any point.  Broadcast chat to anyone listening, or a private message
to named person.

Timing:  Session timers can be set on, off, or paused.  Also total time
per day can be limited.

User defaults:  An extensive range of user default choices including
inactivity timeout, hotkey mode, chat message colours.  Also interface
with terminfo to allow user to choose his best terminal type for use
with external programs.

Run Unix commands or "doors" either with BBS permissions or with login
permissions, as required for access and security.

All above are under total control of configuration files and the
semi-programmable menus.  Each line of each menu can be made available
only at certain times, or only to people with a certain flag set or
security level.

The nodes themselves may be configured to only accept callers fulfilling
certain criteria.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:


Top Document: alt.bbs.unixbbs Frequently Asked Questions
Previous Document: Commune/IX
Next Document: EBBS Eagle's Nest BBS

Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer: (UnixBBS FAQ Maintainer)

Last Update March 27 2014 @ 02:12 PM