Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!ogicse!schaefer
From: schaefer@ogicse.ogc.edu (Barton E. Schaefer)
Newsgroups: comp.mail.mush
Subject: Re: mush and mmdf help wanted
Message-ID: <10727@ogicse.ogc.edu>
Date: 21 Jul 90 06:29:24 GMT
References: <1990Jul18.143855.11452@murdoch.acc.Virginia.EDU> <1990Jul19.065835.11243@robobar.co.uk> <1990Jul19.155151.29977@murdoch.acc.Virginia.EDU> <1990Jul20.090225.5008@robobar.co.uk>
Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR
Lines: 24

In article <1990Jul20.090225.5008@robobar.co.uk> ronald@robobar.co.uk (Ronald S H Khoo) writes:
} [ Bart, a short description of ._.mail format is below.  Don't hit 'n' yet! ]

I deliberately get all this stuff both via news and via the mush-users list
so I won't accidentally lose anything important.

} the structure of the ._.mail file is found in msg.h.  It consists of 1
} struct status followed by n struct message records.

Seems doubtful that mush would be able to deal with this properly without
considerably more information on how each of the fields is generated,
especially the "magic number" in struct status.  Mush also would have to
support those data structures exactly in order to write out the correct
binary form.  If it had been an ascii format, or even a binary that
wasn't a dump of an array of structures, it might have been possible.

} Bart, I'll look harder at it if you think it's worth it,
} and if you think that this will fit into mush at all.

I think the best idea is just to have mush remove the "._.mail" fail on
update when MMDF is defined.  Is the index file name always the folder
name with "._." prepended?
-- 
Bart Schaefer						schaefer@cse.ogi.edu