Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!ucbvax!TRANSARC.COM!Craig_Everhart From: Craig_Everhart@TRANSARC.COM Newsgroups: comp.soft-sys.andrew Subject: Re: AMDS compatible "inc" for MH Message-ID: <4b39v8X0BwwO8jLFYL@transarc.com> Date: 5 Oct 90 14:55:04 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 23 I would be happy to collaborate on such a program (``inc'' lookalike for AMDS). I would also be happy to collaborate on a more general-purpose program that takes mail from ~/Mailbox/* and puts it into /usr/spool/mail/ (/usr/mail/). If any vanilla-Unix-mail wizards want to help, that's great. The kind of help I would need is to know the detailed semantics for what ``inc'' should produce, or for that matter for how a program like /bin/mail goes about appending stuff to /usr/spool/mail/userid. Of course, my concern is that there's lots of customization that people have applied to The shell-script approach to amds-inc might be straightforward, but unless you're careful it might screw up. If the underlying moves are done with ``mv'' to locations in the same AFS volume, then you're probably safe from outages; the Mailbox file won't get lost, but will either be moved or stay where it was. If you're concerned with MH locking, you'd probably have to write a program. A shell script would probably work OK in a single-user context, where you're either running native MH inc or your new amds-inc. Takers? Helpers? Craig