[comp.sys.ibm.pc] MS-DOS Standards, Mail, Communications

jon@chiron.UUCP (Jon L. Griffeth) (04/26/88)

Questions:

1.  Is there a current or developing standard for a directory hierarchy?
    While a standardized directory hierarchy might not be appropriate for
    a floppy based system, hard disks have become fairly prevalent.  Such
    a system might also help other standards (based on the file system)
    to emerge.

2.  Is there a current or developing standard for maintaining electronic mail
    on the IBM-PC?  I do not imply a standard for the communication of mail
    messages, only the means by which they are stored and maintained.  This
    would allow messages from multiple sources to be routed into a common
    sub-system, thereby providing a common user interface.

3.  Is there a current or developing standard for managing communication
    resources?  Both Microsoft Windows and OS/2 have some form of multi-
    tasking.  It becomes apparent that some system is needed to prevent
    two processes from accessing the same port.  Also, some system of
    maintaining dialup information (similar to that provided by the 'UUCP'
    facilities of UNIX) would also be nice.

4.  Is there a decent scheme for the automated transfer of files between
    systems with remote command execution?  I realize that there are many
    commercial communication products available.  However, none of them
    seem to provide the level automation, flexibility, and reliability
    frequently desired.  I have heard about 'UUPC', but believe that this
    is tied too strongly to the UNIX system.


Proposals:

1.  Start with a directory hierarchy similar to UNIX's and modify it as
    appropriate.  Suggestions from the net would primarily be responsible
    for shaping this.

2.  Mail messages could be maintained in a special sub-directory with one
    message per file.  File names might be of the form:

        <sequence number>.MAI

    where <sequence number> is an 8 digit number.  The next available
    sequence number would be stored within a file named SEQFILE and be
    updated as appropriate.  All messages would be in pure text form,
    although some structure could be imposed upon them.

    A small set of utility programs would then be charged with maintenance
    of the directory.  One such program would be responsible for adding
    messages to the directory.  Another would provide the user interface.

    Note: This is similar to the UNIX approach of handling mail.

3.  Once again, a special sub-directory could be created with files that
    maintain specific information.  Lock files would be created within
    this directory to manage communication ports.

    Again, this could be similar the UNIX's UUCP approach.

4.  Perhaps a better extension to the Kermit file transfer protocol could
    be devised.


I believe it appropriate that some standards be developed in these areas.
Any constructive input would be greatly appreciated, especially from people
at Microsoft.

Thanks,
Jon

rochester!cci632!chiron!jon

bear@houtz.UUCP (J.ALLEN) (04/27/88)

In article <112@chiron.UUCP>, jon@chiron.UUCP (Jon L. Griffeth) writes
about wanting various features on clone.pc, the common thread in the
original article is "like UNIX":
> 
>     ... Both Microsoft Windows and OS/2 have some form of multi-
>     tasking...(similar to that provided by the 'UUCP' of UNIX)
>     would also be nice...Start with a directory hierarchy similar
>     to UNIX's...Note: This is similar to the UNIX approach of
>     handling mail. ... Again, this could be similar the UNIX's
>     UUCP approach. ...

RUN UNIX on that clone!

Jim Allen