From owner-freebsd-stable Wed May 16 0: 6: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 83DE737B423; Wed, 16 May 2001 00:06:05 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 81B0D10F40F; Wed, 16 May 2001 02:06:12 -0500 (CDT) Message-ID: <06c701c0ddd6$ad852d60$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Geoff Buckingham" , "Mike Smith" Cc: "Jonathan Lemon" , , References: <200105151924.f4FJO3A05849@prism.flugsvamp.com> <200105152002.f4FK2J100674@mass.dis.org> <20010516073318.A93130@chuggalug.clues.com> Subject: Re: Recent fxp Driver Changes Date: Wed, 16 May 2001 02:06:06 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It was posted on -stable before it was done, which people are supposed to track if they are using -stable. Maybe it should also be in updating if its not already. > It would be helpfull for the various upgrade paths to warn of changes that > can mean an upgraded remote machine suddenly has no network connection. > > The worst case being the change name of NIC devices as that invalidates the > rc.conf entries. > > -- > GeoffB > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message