From owner-freebsd-stable Mon Jul 17 16:45:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id EFF4837B7A5; Mon, 17 Jul 2000 16:45:29 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id TAA93137; Mon, 17 Jul 2000 19:45:49 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Mon, 17 Jul 2000 19:45:49 -0400 (EDT) From: Adam To: Kris Kennaway Cc: stable@FreeBSD.org Subject: Re: Problem with installworld In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jul 2000, Kris Kennaway wrote: >On Mon, 17 Jul 2000, Adam wrote: > >> Is this not worth a note in UPDATING? Theres *only* four entries in there >> past 4.0-release, I dont think its asking too much to be read :) > >Actually it's not the kind of thing that goes into UPDATING: namely hoops >you have to jump through to update your system. Maybe it should? I was obviously stumbling over this problem when _updating_ my system and since the base system already has (hopefully) working ssh, I'd probably never notice USA_RESIDENT was set to no since I wouldnt have to compile ssh from ports... Besides, it _was_ a hoop I had to jump through. In my mind UPDATING shows the oddball things a person has to do out of the ordinary when going from xx-release or date-xxx to present to upgrade your system without blowing toes off in any manner and causing extra posts to mailing lists asking whats going on??? like this one :) > >This is an erratum and should be listed on >http://www.freebsd.org/releases/4.0R/errata.html, except no-one notes bug >fixes in the errata for some reason. > >Kris > >-- >In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message