[2315] in SIPB_Linux_Development
Returned mail: Cannot send message for 3 days
daemon@ATHENA.MIT.EDU (Mail Delivery Subsystem)
Wed Nov 18 12:56:47 1998
Date: Wed, 18 Nov 98 12:55:49 EST
From: MAILER-DAEMON@MIT.EDU (Mail Delivery Subsystem)
To: <amu@MIT.EDU>
To: rshah@PO7.LOCAL
To: yonah@PO7.LOCAL
To: linux-dev-mtg@charon.MIT.EDU
To: djib@PO8.LOCAL
To: nygren@PO7.LOCAL
To: jmmikkel@PO9.LOCAL
To: ghudson@PO10.LOCAL
To: pmccormi@LIPCHITZ.MIT.EDU
To: dalmeida@PO7.LOCAL
To: proven@PO7.LOCAL
To: warlord@PO7.LOCAL
To: svalente@PO10.LOCAL
To: yandros@PO9.LOCAL
To: tytso@PO9.LOCAL
To: basch@lehman.com
To: eichin@PO9.LOCAL
To: dkk@PO9.LOCAL
To: efoo@PO10.LOCAL
To: fastcart@PO8.LOCAL
To: nocturne@cygnus.com
To: holt@graphics.lcs.mit.edu
To: amu@PO8.LOCAL
To: sit@PO10.LOCAL
To: fubob@PO10.LOCAL
To: jered@PO9.LOCAL
To: mwhitson@PO10.LOCAL
To: klmitch@PO9.LOCAL
To: kcr@PO7.LOCAL
To: wdc@PO9.LOCAL
----- Transcript of session follows -----
421 let.mit.edu.tcp... Deferred: Connection refused by let.mit.edu
451 tke@let.mit.edu... Cannot send message for 3 days
----- Unsent message follows -----
Received: from TUX.MIT.EDU by MIT.EDU with SMTP
id AA18830; Sun, 15 Nov 98 12:25:33 EST
Received: (from amu@localhost)
by tux.mit.edu (8.8.7/8.8.7) id MAA05763;
Sun, 15 Nov 1998 12:25:26 -0500
Sender: amu@MIT.EDU
To: linux-announce@MIT.EDU
Subject: more 4.2 updates, including one for libc5
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: amu@MIT.EDU (Aaron M. Ucko)
Date: 15 Nov 1998 12:25:25 -0500
Message-Id: <udld86ozx4q.fsf@tux.mit.edu>
Lines: 12
X-Mailer: Gnus v5.6.43/Emacs 20.3
Red Hat has recently issued more updates to 4.2 to plug various
security holes, including one in libc (the C library, which pretty
much everything uses). If you're running Red Hat-Athena 4.2, we
recommend that you install these updates by attaching the linux locker
and running /mit/linux/redhat/redhat-4.2/i386/updates/update.pl as
root. I have had reports that the update script may clobber certain
configuration files when updating the packages that own them, so if
you've modified any system files, you may want to save the modified
copies somewhere just in case.
--
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)