🚀 go-pugleaf

HAPPY DAYS ARE HERE AGAIN!

Thanks for all the help with configuring Mush to work with
SCO UNIX 3.2v2.0 and ODT 1.1.

Two basic solutions were proposed; one was to modify the
permissions of various mmdf files and directories, the other
was to hack mush so that it would interface with execmail
instead of mmdf.

Somehow or other, the idea of moving up the mail hierarchy
and interacting with execmail didn't appeal to me, so I
decided to have a go at hacking mmdf permissions.

As advised, I ran /usr/mmdf/bin/checkup, which checks all
the permissions of the various pieces of mmdf.  Checkup
found that most of the directories in the /usr/spool/mmdf
hierarchy were mode 700, and suggested that they should be
mode 707.  In particular, I think that /usr/spool/mmdf/tmp
being mode 700 was what was causing the "can not write"
errors.

After changing the /usr/spool/mmdf sub-directories to mode
707, mush began working correctly.  Note that not all of
these directories should be changed (in particular,
/usr/spool/mmdf and /usr/spool/mmdf/lock should be left
700), only the ones which checkup suggests.

Other than that, changing EACCESS to EACCES in lock.c, and
including <sys.select.h> in curs_io.c were the only changes
I had to make.  Congratulations, guys.


--
Rick Farris  RF Engineering POB M Del Mar, CA 92014  voice (619) 259-6793
rfarris@rfengr.com     ...!ucsd!serene!rfarris      serenity bbs 259-7757