[net.micro.apple] ProLine

mdavis@pro-sol.UUCP (10/08/86)

GVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGV
From: Morgan Davis <crash!pnet01!pro-sol!mdavis@nosc.arpa>
To: pnet01!crash!ihnp4!convex!mcomp!p40001@nosc.arpa
Subject: Re: ProLine
Cc: info-apple@amsaa.arpa
Return-Path: <info-apple-request@BRL.ARPA>
Redistributed: XeroxInfo-Apple^.pa
Received: from BRL-SMOKE.ARPA by Xerox.COM ; 05 OCT 86 01:24:34 PDT
Received: from amsaa.arpa by SMOKE.BRL.ARPA id ab06574; 5 Oct 86 3:39 EDT
Received: from nosc.arpa by AMSAA.ARPA id a027772; 5 Oct 86 3:29 EDT
Received: by bass.ARPA (5.31/4.7)	id AA27736; Sun, 5 Oct 86 00:31:53 PDT
Message-Id: <8610050731.AA27736@bass.ARPA>
Original-Date: Sat, 4 Oct 86 16:59:14 PDT
GVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGV

> Morgan,
> 
> I just received the LLS flyer which was enclosed with the OpenApple
> newsletter.
> Can you give me some more info on the ProLine package? How does it
> interface to UUCP? Could I just find any uucp site to connect to?
> It sounds like something I'd be interested in, but I'd like to know
> a bit more about it before investing nearly $200.
> Thanks!
> Wolf
> -----------------------------------------------------
> Wolf N. Paul
> UUCP:  ihnp4!convex!mcomp!doulos!wnp
>   or   ihnp4!convex!mcomp!p40001

First and foremost, ProLine is probably the most complete and powerful
messaging systems ever written for the Apple computer.  The entire program was
written with UNIX in mind.  I wanted a system that at least looked and acted a
lot like UNIX.  So I built a shell, and from that a mailer, and from that a
conference system (not that much unlike readnews).  I was fortunate enough to
have a unix account on one of Bill Blue's unix boxes, and so I got all of my
experience there.  By keeping the direction of ProLine toward that which unix
provides, it made it a lot easier to implement unix-ish stuff, including node
networking between ProLine sites, as well as into other gateways (such as the
one that this message is going through).

ProLine in itself is unable to speak with uucp, but through a gateway program,
it can.  One such gateway is P-Net (crash!pnet01).  It is a conferencing
system written by Bill Blue in C under Symmetrix BSD 4.2.  He and I created a
simple interface between our systems in order to pass mail back and forth.
But if it wasn't for P-Net, there's no way that ProLine would be able to find
paths into uucp/arpa-land.  However, I do not consider uucp access as the one
and only reason for buying ProLine...there's a heck of a lot more to this
system than it's simple interface into gateways.

So, with that explained, on to the features.

ProLine was written using ModemWorks and Applesoft BASIC, and runs under
ProDOS on at least 10mb of hard disk.  It can support up to 256 individual
accounts, and each user has his own workspace and mailbox.  A workspace is
nothing more than a subdirectory (/a/usr/mdavis, for example).  The user is
free to do anything in his area that he wants:  create, edit, store, and
delete files, create subdirectories, etc.  Also, a special security feature
allows users to pass files back and forth between user areas, for example:

        $ cp foobar ../jdoe

This copies "foobar" in your area to jdoe's area.  Also, xmodem protocol is
supported for transferring binary and text data files.

Each user has a mailbox, designed after the uucp mailbox structure.  Because
of this, a mailbox's size is only limited by the amount of disk space.  A
mailbox can hold as many messages as well fit (with a logical limit upheld by
ProDOS of 16 megabytes).  The mail program, at present, will only handle 128
messages at a time, though I am planning on expanding this.  The mailer
supports automatic return-path generation (which was employed when I commented
to your letter), variables, and interactiveness with your filespace, carbon
and blind copy feature, multiple To-field recipients, etc.  Just like mail.
In addition, the ReMAILer will support alias distribution lists.  With this,
there are a few folks on my ProLine node who will be reading this message
since it will come back through the networks to my info-apple alias list.
The user interface of ProLine's mailer is an enhancement of the UCSD MSG
System.

ProLine has a non-threaded conferencing system, which can contain up to 51
major groups, each containing any number of subtopics.  With a 5mb data space,
about 7,000 individual messages can be maintained.  The conferencing system is
self-maintaining, as it will flush old messages when new ones are added.  A
user can join as many group topics as he wishes, providing he has requisite
access to some of the closed-to-general-public areas.  Each major group has a
conference moderator who is responsible for taking care of his subtopics.
Message entry modes in the conference area (as well as in the mailer) are disk
based, meaning messages can be very large in size -- limited only by disk
space.  The editor is limited to 400 lines of text, however.  Word-wrap text
entry is supported.

ProLine has a Data Library, consisting of many "bookshelves."  Each shelf can
hold any number of "titles" (files, programs, etc).  Users can browse through
the library and select books to check out (download) or can donate their own
if they wish.  Each user can download 6 files per day maximum, in order to
keep system usage at a reasonable level.  Each "title" includes a coresponding
card in the card catalog; a descriptive 6-line text field which gives the
program's name, author, file type, size, and date donated.  Each entry also is
kept up to date as to how many times is has been checked out (letting you know
which are popular and which aren't).  The library is assigned a librarian to
maintain it (which can be the system manager [or sysop] or any one else).
Xmodem protocol is supported in the Data Library.

ProLine's password file (/a/etc/passwd) is structured like unix, where each
entry contains:

   login:encrypted_password:UID:GID:real name:home_area:program_to_run

This allows the SA to create password entries which can run any file in
the system, not just the SHell.

Every account on ProLine has billing and accounting information maintained at
all times.  Each user is tracked by the minute, and the accounting information
can report: number of times logged, total number of minutes used since account
was established, total number of minutes used in the previous month, total
minutes used in the current month, rate per minute, account balance, total
amount due, as well as billing address and phone number.  Likewise, the system
will keep a running history of itself with the same information (it's fun to
see that in 12 months, the system has been in use by callers for 600,000
minutes!).  Any user can check his account statistics at any time.

While idle (waiting for a call), ProLine keeps track of timed tasks
(/a/etc/crontab), to see if it is time to poll other sites, run system
maintenance programs such as archiving the log files, removing inactive
accounts, etc.  This makes the system practically self-maintaining.
The system manager of ProLine can make changes to the crontab task file and
set up tasks to run at any given time points, from minute-to-minute, to days
and months in advance.

ProLine's shell supports variables, character escaping, multiple commands per
line, executable script files, conditional logic, many built-in management
commands (cp, mv, pwd, cd, to name a few) and will run any programs in /a/bin,
such as grep, stty, ls, rmuser, rmdir, etc, etc etc etc...  it's pretty damned
unix-like.  Each user can tailor his own custom "profile" script.

All told, ProLine's help facilities total near 100K of helpful text files.  So
if all of this sounded like it goes beyond the scope of your normal BBS
junkie, there is quite a bit of tutorial information online.  More than a few
folks have used ProLine to learn how to use *real* UNIX systems, without even
knowing they were, in a sense, studying!

This very compact and condensed description of ProLine is far from detailed.
I have only touched on some of the points of the program.  It has been under
development for over a year, and is still being worked on.  It should be ready
for release to serious sites by January, 1987 (I've written most of the code,
now all I have to do is document UNIX, essentially.  Sigh...).  I will post
an official announcement to the net when it's ready.

ProLine will run on any Apple computer (which can run ProDOS, that is).  I
recommend the Apple IIe, though my site has been running off of an old
Apple II+ for over a year.  A ProDOS-compatible clock card, 10mb hard disk
(like the Sider and equiv.), one floppy drive or UniDisk 3.5 (for backups and
installation), and a modem are the other requirements.  Because of ModemWorks,
any truly Hayes-compatible external modem or Apple-Cat II internal modem will
work just fine.  Baud rates up to 2400 bps are supported.

My site runs all day long, and currently has a 300/1200 bps modem attached.
Feel free to call and check it out personally if you wish.  Login as guest.
The number is 619/281-7222 (San Diego, California, USA).  I think you will
find it very difficult to believe that it all runs under BASIC, because
it is quite fast and responsive.

--Morgan W. Davis

UUCP: [ akgua, hplabs!hp-sdd, sdcsvax, noscvax ] !crash!pnet01!pro-sol!mdavis
ARPA: crash!pnet01!pro-sol!mdavis@nosc

mdavis@pro-sol.UUCP (10/14/86)

Return-Path: <info-apple-request@BRL.ARPA>
Redistributed: XeroxInfo-Apple^.x
Received: from BRL-SMOKE.ARPA by Xerox.COM ; 08 OCT 86 15:21:50 PDT
Received: from amsaa.arpa by SMOKE.BRL.ARPA id a024363; 8 Oct 86 16:56 EDT
Received: from xerox.arpa by AMSAA.ARPA id a019895; 8 Oct 86 16:46 EDT
Received: from Riesling.ms by ArpaGateway.ms ; 08 OCT 86 12:56:43 PDT
Original-Date: 8 Oct 86 12:55:41 PDT (Wednesday)
Message-ID: <861008-125643-6311@Xerox>

GVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGV
From: Morgan Davis <crash!pnet01!pro-sol!mdavis@nosc.arpa>
To: pnet01!crash!ihnp4!convex!mcomp!p40001@nosc.arpa
Subject: Re: ProLine
Cc: info-apple@amsaa.arpa
Return-Path: <info-apple-request@BRL.ARPA>
Redistributed: XeroxInfo-Apple^.pa
Received: from BRL-SMOKE.ARPA by Xerox.COM ; 05 OCT 86 01:24:34 PDT
Received: from amsaa.arpa by SMOKE.BRL.ARPA id ab06574; 5 Oct 86 3:39 EDT
Received: from nosc.arpa by AMSAA.ARPA id a027772; 5 Oct 86 3:29 EDT
Received: by bass.ARPA (5.31/4.7)	id AA27736; Sun, 5 Oct 86 00:31:53 PDT
Message-Id: <8610050731.AA27736@bass.ARPA>
Original-Date: Sat, 4 Oct 86 16:59:14 PDT
GVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGV

> Morgan,
> 
> I just received the LLS flyer which was enclosed with the OpenApple
> newsletter.
> Can you give me some more info on the ProLine package? How does it
> interface to UUCP? Could I just find any uucp site to connect to?
> It sounds like something I'd be interested in, but I'd like to know
> a bit more about it before investing nearly $200.
> Thanks!
> Wolf
> -----------------------------------------------------
> Wolf N. Paul
> UUCP:  ihnp4!convex!mcomp!doulos!wnp
>   or   ihnp4!convex!mcomp!p40001

First and foremost, ProLine is probably the most complete and powerful
messaging systems ever written for the Apple computer.  The entire program was
written with UNIX in mind.  I wanted a system that at least looked and acted a
lot like UNIX.  So I built a shell, and from that a mailer, and from that a
conference system (not that much unlike readnews).  I was fortunate enough to
have a unix account on one of Bill Blue's unix boxes, and so I got all of my
experience there.  By keeping the direction of ProLine toward that which unix
provides, it made it a lot easier to implement unix-ish stuff, including node
networking between ProLine sites, as well as into other gateways (such as the
one that this message is going through).

ProLine in itself is unable to speak with uucp, but through a gateway program,
it can.  One such gateway is P-Net (crash!pnet01).  It is a conferencing
system written by Bill Blue in C under Symmetrix BSD 4.2.  He and I created a
simple interface between our systems in order to pass mail back and forth.
But if it wasn't for P-Net, there's no way that ProLine would be able to find
paths into uucp/arpa-land.  However, I do not consider uucp access as the one
and only reason for buying ProLine...there's a heck of a lot more to this
system than it's simple interface into gateways.

So, with that explained, on to the features.

ProLine was written using ModemWorks and Applesoft BASIC, and runs under
ProDOS on at least 10mb of hard disk.  It can support up to 256 individual
accounts, and each user has his own workspace and mailbox.  A workspace is
nothing more than a subdirectory (/a/usr/mdavis, for example).  The user is
free to do anything in his area that he wants:  create, edit, store, and
delete files, create subdirectories, etc.  Also, a special security feature
allows users to pass files back and forth between user areas, for example:

        $ cp foobar ../jdoe

This copies "foobar" in your area to jdoe's area.  Also, xmodem protocol is
supported for transferring binary and text data files.

Each user has a mailbox, designed after the uucp mailbox structure.  Because
of this, a mailbox's size is only limited by the amount of disk space.  A
mailbox can hold as many messages as well fit (with a logical limit upheld by
ProDOS of 16 megabytes).  The mail program, at present, will only handle 128
messages at a time, though I am planning on expanding this.  The mailer
supports automatic return-path generation (which was employed when I commented
to your letter), variables, and interactiveness with your filespace, carbon
and blind copy feature, multiple To-field recipients, etc.  Just like mail.
In addition, the ReMAILer will support alias distribution lists.  With this,
there are a few folks on my ProLine node who will be reading this message
since it will come back through the networks to my info-apple alias list.
The user interface of ProLine's mailer is an enhancement of the UCSD MSG
System.

ProLine has a non-threaded conferencing system, which can contain up to 51
major groups, each containing any number of subtopics.  With a 5mb data space,
about 7,000 individual messages can be maintained.  The conferencing system is
self-maintaining, as it will flush old messages when new ones are added.  A
user can join as many group topics as he wishes, providing he has requisite
access to some of the closed-to-general-public areas.  Each major group has a
conference moderator who is responsible for taking care of his subtopics.
Message entry modes in the conference area (as well as in the mailer) are disk
based, meaning messages can be very large in size -- limited only by disk
space.  The editor is limited to 400 lines of text, however.  Word-wrap text
entry is supported.

ProLine has a Data Library, consisting of many "bookshelves."  Each shelf can
hold any number of "titles" (files, programs, etc).  Users can browse through
the library and select books to check out (download) or can donate their own
if they wish.  Each user can download 6 files per day maximum, in order to
keep system usage at a reasonable level.  Each "title" includes a coresponding
card in the card catalog; a descriptive 6-line text field which gives the
program's name, author, file type, size, and date donated.  Each entry also is
kept up to date as to how many times is has been checked out (letting you know
which are popular and which aren't).  The library is assigned a librarian to
maintain it (which can be the system manager [or sysop] or any one else).
Xmodem protocol is supported in the Data Library.

ProLine's password file (/a/etc/passwd) is structured like unix, where each
entry contains:

   login:encrypted_password:UID:GID:real name:home_area:program_to_run

This allows the SA to create password entries which can run any file in
the system, not just the SHell.

Every account on ProLine has billing and accounting information maintained at
all times.  Each user is tracked by the minute, and the accounting information
can report: number of times logged, total number of minutes used since account
was established, total number of minutes used in the previous month, total
minutes used in the current month, rate per minute, account balance, total
amount due, as well as billing address and phone number.  Likewise, the system
will keep a running history of itself with the same information (it's fun to
see that in 12 months, the system has been in use by callers for 600,000
minutes!).  Any user can check his account statistics at any time.

While idle (waiting for a call), ProLine keeps track of timed tasks
(/a/etc/crontab), to see if it is time to poll other sites, run system
maintenance programs such as archiving the log files, removing inactive
accounts, etc.  This makes the system practically self-maintaining.
The system manager of ProLine can make changes to the crontab task file and
set up tasks to run at any given time points, from minute-to-minute, to days
and months in advance.

ProLine's shell supports variables, character escaping, multiple commands per
line, executable script files, conditional logic, many built-in management
commands (cp, mv, pwd, cd, to name a few) and will run any programs in /a/bin,
such as grep, stty, ls, rmuser, rmdir, etc, etc etc etc...  it's pretty damned
unix-like.  Each user can tailor his own custom "profile" script.

All told, ProLine's help facilities total near 100K of helpful text files.  So
if all of this sounded like it goes beyond the scope of your normal BBS
junkie, there is quite a bit of tutorial information online.  More than a few
folks have used ProLine to learn how to use *real* UNIX systems, without even
knowing they were, in a sense, studying!

This very compact and condensed description of ProLine is far from detailed.
I have only touched on some of the points of the program.  It has been under
development for over a year, and is still being worked on.  It should be ready
for release to serious sites by January, 1987 (I've written most of the code,
now all I have to do is document UNIX, essentially.  Sigh...).  I will post
an official announcement to the net when it's ready.

ProLine will run on any Apple computer (which can run ProDOS, that is).  I
recommend the Apple IIe, though my site has been running off of an old
Apple II+ for over a year.  A ProDOS-compatible clock card, 10mb hard disk
(like the Sider and equiv.), one floppy drive or UniDisk 3.5 (for backups and
installation), and a modem are the other requirements.  Because of ModemWorks,
any truly Hayes-compatible external modem or Apple-Cat II internal modem will
work just fine.  Baud rates up to 2400 bps are supported.

My site runs all day long, and currently has a 300/1200 bps modem attached.
Feel free to call and check it out personally if you wish.  Login as guest.
The number is 619/281-7222 (San Diego, California, USA).  I think you will
find it very difficult to believe that it all runs under BASIC, because
it is quite fast and responsive.

--Morgan W. Davis

UUCP: [ akgua, hplabs!hp-sdd, sdcsvax, noscvax ] !crash!pnet01!pro-sol!mdavis
ARPA: crash!pnet01!pro-sol!mdavis@nosc

mdavis@pro-sol.UUCP (10/15/86)

Return-Path: <info-apple-request@BRL.ARPA>
Redistributed: XeroxInfo-Apple^.x
Received: from BRL-SMOKE.ARPA by Xerox.COM ; 14 OCT 86 13:40:44 PDT
Received: from amsaa.arpa by SMOKE.BRL.ARPA id a007444; 14 Oct 86 14:44 EDT
Received: from xerox.arpa by AMSAA.ARPA id a013866; 14 Oct 86 14:38 EDT
Received: from Riesling.ms by ArpaGateway.ms ; 14 OCT 86 11:05:39 PDT
Original-Date: 14 Oct 86 11:03:51 PDT (Tuesday)
Message-ID: <861014-110539-2458@Xerox>

Return-Path: <info-apple-request@BRL.ARPA>
Redistributed: XeroxInfo-Apple^.x
Received: from BRL-SMOKE.ARPA by Xerox.COM ; 08 OCT 86 15:21:50 PDT
Received: from amsaa.arpa by SMOKE.BRL.ARPA id a024363; 8 Oct 86 16:56 EDT
Received: from xerox.arpa by AMSAA.ARPA id a019895; 8 Oct 86 16:46 EDT
Received: from Riesling.ms by ArpaGateway.ms ; 08 OCT 86 12:56:43 PDT
Original-Date: 8 Oct 86 12:55:41 PDT (Wednesday)
Message-ID: <861008-125643-6311@Xerox>

GVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGV
From: Morgan Davis <crash!pnet01!pro-sol!mdavis@nosc.arpa>
To: pnet01!crash!ihnp4!convex!mcomp!p40001@nosc.arpa
Subject: Re: ProLine
Cc: info-apple@amsaa.arpa
Return-Path: <info-apple-request@BRL.ARPA>
Redistributed: XeroxInfo-Apple^.pa
Received: from BRL-SMOKE.ARPA by Xerox.COM ; 05 OCT 86 01:24:34 PDT
Received: from amsaa.arpa by SMOKE.BRL.ARPA id ab06574; 5 Oct 86 3:39 EDT
Received: from nosc.arpa by AMSAA.ARPA id a027772; 5 Oct 86 3:29 EDT
Received: by bass.ARPA (5.31/4.7)	id AA27736; Sun, 5 Oct 86 00:31:53 PDT
Message-Id: <8610050731.AA27736@bass.ARPA>
Original-Date: Sat, 4 Oct 86 16:59:14 PDT
GVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGVGV

> Morgan,
> 
> I just received the LLS flyer which was enclosed with the OpenApple
> newsletter.
> Can you give me some more info on the ProLine package? How does it
> interface to UUCP? Could I just find any uucp site to connect to?
> It sounds like something I'd be interested in, but I'd like to know
> a bit more about it before investing nearly $200.
> Thanks!
> Wolf
> -----------------------------------------------------
> Wolf N. Paul
> UUCP:  ihnp4!convex!mcomp!doulos!wnp
>   or   ihnp4!convex!mcomp!p40001

First and foremost, ProLine is probably the most complete and powerful
messaging systems ever written for the Apple computer.  The entire program was
written with UNIX in mind.  I wanted a system that at least looked and acted a
lot like UNIX.  So I built a shell, and from that a mailer, and from that a
conference system (not that much unlike readnews).  I was fortunate enough to
have a unix account on one of Bill Blue's unix boxes, and so I got all of my
experience there.  By keeping the direction of ProLine toward that which unix
provides, it made it a lot easier to implement unix-ish stuff, including node
networking between ProLine sites, as well as into other gateways (such as the
one that this message is going through).

ProLine in itself is unable to speak with uucp, but through a gateway program,
it can.  One such gateway is P-Net (crash!pnet01).  It is a conferencing
system written by Bill Blue in C under Symmetrix BSD 4.2.  He and I created a
simple interface between our systems in order to pass mail back and forth.
But if it wasn't for P-Net, there's no way that ProLine would be able to find
paths into uucp/arpa-land.  However, I do not consider uucp access as the one
and only reason for buying ProLine...there's a heck of a lot more to this
system than it's simple interface into gateways.

So, with that explained, on to the features.

ProLine was written using ModemWorks and Applesoft BASIC, and runs under
ProDOS on at least 10mb of hard disk.  It can support up to 256 individual
accounts, and each user has his own workspace and mailbox.  A workspace is
nothing more than a subdirectory (/a/usr/mdavis, for example).  The user is
free to do anything in his area that he wants:  create, edit, store, and
delete files, create subdirectories, etc.  Also, a special security feature
allows users to pass files back and forth between user areas, for example:

        $ cp foobar ../jdoe

This copies "foobar" in your area to jdoe's area.  Also, xmodem protocol is
supported for transferring binary and text data files.

Each user has a mailbox, designed after the uucp mailbox structure.  Because
of this, a mailbox's size is only limited by the amount of disk space.  A
mailbox can hold as many messages as well fit (with a logical limit upheld by
ProDOS of 16 megabytes).  The mail program, at present, will only handle 128
messages at a time, though I am planning on expanding this.  The mailer
supports automatic return-path generation (which was employed when I commented
to your letter), variables, and interactiveness with your filespace, carbon
and blind copy feature, multiple To-field recipients, etc.  Just like mail.
In addition, the ReMAILer will support alias distribution lists.  With this,
there are a few folks on my ProLine node who will be reading this message
since it will come back through the networks to my info-apple alias list.
The user interface of ProLine's mailer is an enhancement of the UCSD MSG
System.

ProLine has a non-threaded conferencing system, which can contain up to 51
major groups, each containing any number of subtopics.  With a 5mb data space,
about 7,000 individual messages can be maintained.  The conferencing system is
self-maintaining, as it will flush old messages when new ones are added.  A
user can join as many group topics as he wishes, providing he has requisite
access to some of the closed-to-general-public areas.  Each major group has a
conference moderator who is responsible for taking care of his subtopics.
Message entry modes in the conference area (as well as in the mailer) are disk
based, meaning messages can be very large in size -- limited only by disk
space.  The editor is limited to 400 lines of text, however.  Word-wrap text
entry is supported.

ProLine has a Data Library, consisting of many "bookshelves."  Each shelf can
hold any number of "titles" (files, programs, etc).  Users can browse through
the library and select books to check out (download) or can donate their own
if they wish.  Each user can download 6 files per day maximum, in order to
keep system usage at a reasonable level.  Each "title" includes a coresponding
card in the card catalog; a descriptive 6-line text field which gives the
program's name, author, file type, size, and date donated.  Each entry also is
kept up to date as to how many times is has been checked out (letting you know
which are popular and which aren't).  The library is assigned a librarian to
maintain it (which can be the system manager [or sysop] or any one else).
Xmodem protocol is supported in the Data Library.

ProLine's password file (/a/etc/passwd) is structured like unix, where each
entry contains:

   login:encrypted_password:UID:GID:real name:home_area:program_to_run

This allows the SA to create password entries which can run any file in
the system, not just the SHell.

Every account on ProLine has billing and accounting information maintained at
all times.  Each user is tracked by the minute, and the accounting information
can report: number of times logged, total number of minutes used since account
was established, total number of minutes used in the previous month, total
minutes used in the current month, rate per minute, account balance, total
amount due, as well as billing address and phone number.  Likewise, the system
will keep a running history of itself with the same information (it's fun to
see that in 12 months, the system has been in use by callers for 600,000
minutes!).  Any user can check his account statistics at any time.

While idle (waiting for a call), ProLine keeps track of timed tasks
(/a/etc/crontab), to see if it is time to poll other sites, run system
maintenance programs such as archiving the log files, removing inactive
accounts, etc.  This makes the system practically self-maintaining.
The system manager of ProLine can make changes to the crontab task file and
set up tasks to run at any given time points, from minute-to-minute, to days
and months in advance.

ProLine's shell supports variables, character escaping, multiple commands per
line, executable script files, conditional logic, many built-in management
commands (cp, mv, pwd, cd, to name a few) and will run any programs in /a/bin,
such as grep, stty, ls, rmuser, rmdir, etc, etc etc etc...  it's pretty damned
unix-like.  Each user can tailor his own custom "profile" script.

All told, ProLine's help facilities total near 100K of helpful text files.  So
if all of this sounded like it goes beyond the scope of your normal BBS
junkie, there is quite a bit of tutorial information online.  More than a few
folks have used ProLine to learn how to use *real* UNIX systems, without even
knowing they were, in a sense, studying!

This very compact and condensed description of ProLine is far from detailed.
I have only touched on some of the points of the program.  It has been under
development for over a year, and is still being worked on.  It should be ready
for release to serious sites by January, 1987 (I've written most of the code,
now all I have to do is document UNIX, essentially.  Sigh...).  I will post
an official announcement to the net when it's ready.

ProLine will run on any Apple computer (which can run ProDOS, that is).  I
recommend the Apple IIe, though my site has been running off of an old
Apple II+ for over a year.  A ProDOS-compatible clock card, 10mb hard disk
(like the Sider and equiv.), one floppy drive or UniDisk 3.5 (for backups and
installation), and a modem are the other requirements.  Because of ModemWorks,
any truly Hayes-compatible external modem or Apple-Cat II internal modem will
work just fine.  Baud rates up to 2400 bps are supported.

My site runs all day long, and currently has a 300/1200 bps modem attached.
Feel free to call and check it out personally if you wish.  Login as guest.
The number is 619/281-7222 (San Diego, California, USA).  I think you will
find it very difficult to believe that it all runs under BASIC, because
it is quite fast and responsive.

--Morgan W. Davis

UUCP: [ akgua, hplabs!hp-sdd, sdcsvax, noscvax ] !crash!pnet01!pro-sol!mdavis
ARPA: crash!pnet01!pro-sol!mdavis@nosc