Article View: bit.listserv.l-vmctr
Article #704VMBACKUP update
From: Richard W Wiggins
Date: Wed, 18 Mar 1992 21:57
Date: Wed, 18 Mar 1992 21:57
13 lines
1194 bytes
1194 bytes
We recently received a "Product Update Information" envelope. Postmark was March 3, date on the letter was January 22. It describes some zaps addressing some potentially serious bugs. I'm trying to find out if our posting was an anomaly or if others also saw the delay. No one wants to read about serious bugs, and it's good to see them flagging the envelopes as we've nagged them to do, but the delay in mailing tends to undermine mailing it at all. (A couple of these look pretty nasty; if you're like me and you let vendor mail pile up, check this one out.) /Rich Wiggins, Michigan State U
Technical Details
Message-ID:
<L-VMCTR%92031817092792@VM1.CC.UAKRON.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!auvm!MSU.BITNET!RWWMAINTShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe320,498674c05c851320,start X-Google-Attributes: gidfe320,public X-Google-ArrivalTime: 1992-03-18 14:15:40 PST Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU Path: arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!auvm!MSU.BITNET!RWWMAINT Message-ID: <L-VMCTR%92031817092792@VM1.CC.UAKRON.EDU> Newsgroups: bit.listserv.l-vmctr Date: Wed, 18 Mar 1992 16:57:27 EST Sender: VMCENTER Components Discussion List <L-VMCTR@AKRONVM.BITNET> From: Richard W Wiggins <RWWMAINT@MSU.BITNET> Subject: VMBACKUP update