Date: Thu, 3 Aug 2006 18:03:27 -0400 From: "John Rogers" <ruralriver@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: binary upgrade issues Message-ID: <100416c30608031503n721c1583labb86a1e8abe7978@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Wow, I did not expect Colin's direct reply - and so prompt! Thanks, and great to know binary updates will be foreseeable. I actually already did it again, since it doesn't make sense to binary upgrade all those source files, I renamed /usr/src to something else, and this greatly reduced the number of files for fetching to 435 ones. The old error message is gone (it's a fairly new and high quality server). It was eventless until to the following: Installing new kernel into /boot/GENERIC... done. Moving /boot/kernel to /boot/kernel.old... done. Moving /boot/GENERIC to /boot/kernel... done. Removing schg flag from existing files... Then my connection to the server froze and I found the server rebooted itself. After login I found it was 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:32:43 UTC 2006. Don't know why it rebooted, and my concern it: had it finished upgrading? I looked into the upgrade.sh and found it should continue working on files referred in old-index, new-index-nonkern, new-index. However none of these files were found in the directory. Also I am worried whether the schg flags were recovered. How can I check these? Thank you. > Colin Percival wrote: > > John Rogers wrote: > > Hi, I was upgrading following Colin's "FreeBSD 6.0 to FreeBSD 6.1 > > binary upgrade" > > > > http://www.daemonology.net/freebsd-upgrade-6.0-to-6.1/ > > > > but it failed. I installed freebsd 6.0 release and only used Colin's > > freebsd-update to updae before. There is plenty of free space on that > > partition. What do you advise me to do to finish the upgrade? > > Based on what you pasted below, I suggest > 1. Figure out why /usr/bin/gdbtui can't be read. In particular, make > sure your hard drive isn't dying. > 2. The error which made the script terminate is either due to a dying > hard drive or a network problem which made it impossible to fetch some > files. Re-run the script; it won't bother fetching files which it > already has. > > Note that at this point all the script has done is to examine your > system and download files; it won't start actually upgrading anything > until it makes sure that it has all the files it needs. :-) > > > I also wonder why these binary update and upgrade are not legitimized > > in the freebsd core distribution. An important reason why linux is > > used by more is its easy update solution similar to Microsoft's > > Windows Update. Sure "make world" is fun especially to developers. > > But providing easy update and upgrade tools in addition will attract a > > large user base who just need a stable and easy to use operation > > system - and many of them can be companies who can be potential donors > > to the freebsd project. So the effort to this path will be well > > rewarded. > > We're moving in that direction. Everything starts out by being experimental > before becoming officially supported and endorsed. > > Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?100416c30608031503n721c1583labb86a1e8abe7978>