Subject: Re: mail(1) feature set...
To: None <firstname.lastname@example.org, netbsd-users@NetBSD.ORG,>
From: Brian Buhrow <email@example.com>
Date: 05/12/1997 10:02:53
I've been using Mush, version 7.2.3 and 7.2.5 under NetBSD since
NetBSD 0.9, but I have recompiled binaries for 1.0, 1.1 and now 1.2. All
binaries work fine with a few small changes. It works flawlessly and never
crashes at all. Even the handling of the curses stuff is fine.
You'll notice that this mail was sent using Mush and from my NetBSD
workstation to boot.
Anyone interested in the changes I made to get things working can send
On May 10, 9:44pm, James R Grinter wrote:
} Subject: Re: mail(1) feature set...
} In article <c=US%a=_%p=Schwab%l=N1001SMX-970502175537Zfirstname.lastname@example.org> James.Graham@Schwab.COM (Graham, James) writes:
} > > I'm thinking of adding '|' to the mailer...
} > Forget it. Go get mush version 7.2.5, unless you need MIME
} > compliance, and even then I wonder...
} (whereupon you can use 'pipe').
} However, has anyone both successfully built mush under NetBSD *and*
} then got it working reliably? (quite a bit of work, bearing in mind the
} curses and old-bsd behaviour reliance)
} Ever since NetBSD 1.1, my various binaries (including one that was
} built under NetBSD 0.9, thus statically linked) have had a habit of
} crashing out whilst sending emails and in an editor (the mush process
} gets to a state where it will crash as soon as you exit vi). It also
} sometimes exits after receiving an EOF from 'nowhere'.
} Now, it could be a mush bug, but it seems odd that I've only
} encountered this under NetBSD. (I've set reply-to and added
} netbsd-users, as it's not a specific to current thing)
>-- End of excerpt from James R Grinter