Date: Wed, 23 Oct 2002 15:09:01 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: "David W. Chapman Jr." <dwcjr@inethouston.net> Cc: Brooks Davis <brooks@one-eyed-alien.net>, Steven Ames <steve@virtual-voodoo.com>, Andrew Mishchenko <andrew@driftin.net>, freebsd-current@FreeBSD.ORG Subject: Re: Request: remove ssh1 fallback Message-ID: <3DB71DFD.51817D13@mindspring.com> References: <007501c27a5c$27203fc0$6501a8c0@VAIO650> <20021023155753.GB7503@HAL9000.homeunix.com> <004401c27aad$740a5400$33d90c42@officescape.net> <20021023161643.GA7813@HAL9000.homeunix.com> <20021023143917.GA3222@driftin.net> <3DB6F2E1.799FF6F7@mindspring.com> <009001c27ac8$af6d77f0$33d90c42@officescape.net> <20021023123349.A9132@Odin.AC.HMC.Edu> <3DB6FF07.5DAC9CCB@mindspring.com> <20021023200151.GA42945@leviathan.inethouston.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"David W. Chapman Jr." wrote: > > Changing behaviour on an upgrade, without the user's consent, is > > a bad thing (note: *consent*, not *knowledge*: it's not up to the > > user to know about everything some programmer has diddled into > > non-operability in the two years since FreeBSD 5.x was branched). > > Isn't that what UPDATING is for and wouldn't between 4.x and 5.x be > better than 5.x and 5.x+n? No. The UPDATING file is for people updating their system by building and installing the world from source code. The UPDATING file is not really visible on the CDROM, or on the system, until /usr/src is installed. If you update a system with an existing /usr/src, sysinstall's "upgrade" option will refuse to install new source code in /usr/src, so you won't get the "UPDATING" file there, either. Even if the file did get installed as part of the "upgrade" option, if you booted off the CDROM for the upgrade, you can't deal with the issues listed in the file until after you reboot. In fact, since there is a history of ABI changes, you will not be able to deal with the contents of the UPDATING file except before you install any binaries that may required a new interface -- or the UPDATING file itself. It's a catch-22, even if you don't boot the CDROM, and do the upgrade from a copy of "sysinstall" that you obtained from another machine that you have already upgraded (since it's nested to vnconfig'ed devices deep on the CDROM, and practically unavailabe otherwise). If you want to change the default for new installs, fine with me (though I'm sure it will piss some people off); but don't break existing functionality on already installed systems that are upgraded. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DB71DFD.51817D13>