From owner-freebsd-announce Thu Feb 27 04:17:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA21686 for freebsd-announce-outgoing; Thu, 27 Feb 1997 04:17:48 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA21667; Thu, 27 Feb 1997 04:17:38 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id EAA12160; Thu, 27 Feb 1997 04:17:28 -0800 (PST) To: announce@freebsd.org cc: hubs@freebsd.org Subject: 2.1.7 Boot floppies updated on ftp.freebsd.org Date: Thu, 27 Feb 1997 04:17:28 -0800 Message-ID: <12156.857045848@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-announce@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here are the new MD5 checksums if you want to make sure you've got the latest and greatest: MD5 (boot.flp) = 978decacb9508ddea5908f7b2f781923 MD5 (boot4.flp) = 52bbedd7a3ccbeb09c9b3516024ba7e8 MD5 (fixit.flp) = b8be0b59dae73b16d0586bfda98b4310 Mirrors, *please* check your floppies directories and make sure you've got these bits! If you're not sure, simply remove 2.1.7-RELEASE/floppies/*.flp and let your mirror pick up new copies on its next pass. This fixes a bug where people with FTP timeouts on lossy connections would sometimes see a signal-11. It didn't occur in any of my testing because my connection isn't lossy enough, unfortunately. :-) This is the only bug fixed by this update, and if you've already successfully installed 2.1.7 or are not planning on installing 2.1.7 over FTP then you do not need to worry about any of this and can hit `d' now. Those tracking the 2.1-stable source branch (see http://www.freebsd.org/handbook/stable.html) will also receive the source changes for fixing this bug and can always rebuild just sysinstall by going to /usr/src/release/sysinstall and doing a make, then copying the new executable into /stand. My apologies for any inconvenience caused by this problem. Jordan From owner-freebsd-announce Sat Mar 1 19:56:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA19062 for freebsd-announce-outgoing; Sat, 1 Mar 1997 19:56:27 -0800 (PST) Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA19058 for freebsd-announce; Sat, 1 Mar 1997 19:56:25 -0800 (PST) Date: Sat, 1 Mar 1997 19:56:25 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199703020356.TAA19058@freefall.freebsd.org> To: freebsd-announce Subject: CMU Monarch Project implementation of IETF Mobile IP Sender: owner-freebsd-announce@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The Monarch Project at Carnegie Mellon University is proud to announce the availability of Release 1.0.2 of our implementation of IETF Mobile IP for IPv4. This release now directly supports both NetBSD (version 1.1) and FreeBSD (version 2.2_GAMMA). Our implementation, since Release 1.0.0, fully conforms to the IETF standard Mobile IP protocol, as specified in RFC 2002, and includes both "IP-in-IP" and "minimal" encapsulation support (RFC 2003 and RFC 2004). The only real change in Release 1.0.2 over our recent Release 1.0.1 version is the addition of support for FreeBSD 2.2_GAMMA; this FreeBSD support is based on changes submitted by Assar Westerlund of the Swedish Institute of Computer Science. This release of the CMU Monarch Project's implementation of IETF Mobile IPv4 is available from our web page at http://www.monarch.cs.cmu.edu/ and by ftp as a gzip'ed tar file from ftp://ftp.monarch.cs.cmu.edu/pub/monarch/mobileip/mip-1.0.2.tar.gz The CMU Monarch Project researches issues in mobile and wireless networking. Named after the migratory monarch butterfly (or the acronym "MObile Networking ARCHitecture"), the goal of the CMU Monarch Project is to enable mobile hosts to communicate with each other and with stationary or wired hosts, transparently and adaptively making the most efficient use of the best network connectivity available to the mobile host at any time. Our research includes work in areas from protocol design and implementation to performance measurement and usage-based evaluation. For more information on the CMU Monarch Project, visit our web page at http://www.monarch.cs.cmu.edu/.