FreeBSD 8.0 released!
in [FreeBSD]
|
From: Spam on 2 Dec 2009 14:52 On Fri, 27 Nov 2009, Stan Barr wrote: > Date: 27 Nov 2009 16:28:18 GMT > From: Stan Barr <plan.b(a)dsl.pipex.com> > Newsgroups: comp.unix.bsd.freebsd.misc > Subject: Re: FreeBSD 8.0 released! > > On Fri, 27 Nov 2009 07:39:26 +0100, Torfinn Ingolfsen <tingo(a)start.no> wrote: >> In case anybody missed it: >> http://www.freebsd.org/releases/8.0R/announce.html > > Anyone know of anything to watch out for when upgrading? > I've got 2 machines to do - amd64 and sparc64... > Well, I'm in the process of upgrading a 7.2-R AMD64 release to 8.0R, and so far, so good, *HOWEVER* in following the binary update instructions, I've succeeded in the first part, by updating the system and binaries, but when recompiling the installed packages, I've stumbled into a *NIGHTMARE*. It seems that installed ports/packages must be recompiled/relinked. I have 680 installed packages, and each one is being systematically recompiled from the ports. This would be OK, were it not for the fact that some (not all) ports launch a curses based window manager (text based) to ask for configuration options, and the build freezes at that point, waiting for input. Its been running for 3 days, with no end in sight, and I have to constantly check to see if the port/package build requires input. Were this to default to the package default, I'd be happy. The fact that it runs interactively, makes it untenable. Oh, and while I'm on a rant, when the freebsd-update package reports upon the files that it will delete, it launches more, and if you "q"uit out of the very long file list before it reaches the end, the update script simply stops -- SILENTLY. perhaps I've missed some step or option to make this process less painful, but I will *NEVER* again use freebsd-update to move to a new release. I would STRONGLY recommend a fresh install from the release DVD ... Cheers, Rob Sciuk
From: Bob Eager on 2 Dec 2009 14:58 On Wed, 02 Dec 2009 14:52:06 -0500, Spam wrote: > It seems that installed ports/packages must be recompiled/relinked. I > have 680 installed packages, and each one is being systematically > recompiled from the ports. This would be OK, were it not for the fact > that some (not all) ports launch a curses based window manager (text > based) to ask for configuration options, and the build freezes at that > point, waiting for input. Its been running for 3 days, with no end in > sight, and I have to constantly check to see if the port/package build > requires input. man ports is your friend. Set the environment variable BATCH to make it use defaults, or previously set options. -- Use the BIG mirror service in the UK: http://www.mirrorservice.org
From: Balwinder S Dheeman on 2 Dec 2009 15:05 On 12/03/2009 01:22 AM, Spam(a)ControlQ.com wrote: > On Fri, 27 Nov 2009, Stan Barr wrote: > >> Date: 27 Nov 2009 16:28:18 GMT >> From: Stan Barr <plan.b(a)dsl.pipex.com> >> Newsgroups: comp.unix.bsd.freebsd.misc >> Subject: Re: FreeBSD 8.0 released! >> >> On Fri, 27 Nov 2009 07:39:26 +0100, Torfinn Ingolfsen <tingo(a)start.no> >> wrote: >>> In case anybody missed it: >>> http://www.freebsd.org/releases/8.0R/announce.html >> >> Anyone know of anything to watch out for when upgrading? >> I've got 2 machines to do - amd64 and sparc64... >> > > Well, I'm in the process of upgrading a 7.2-R AMD64 release to 8.0R, and > so far, so good, *HOWEVER* > > in following the binary update instructions, I've succeeded in the first > part, by updating the system and binaries, but when recompiling the > installed packages, I've stumbled into a *NIGHTMARE*. > > It seems that installed ports/packages must be recompiled/relinked. I > have 680 installed packages, and each one is being systematically > recompiled from the ports. This would be OK, were it not for the fact > that some (not all) ports launch a curses based window manager (text > based) to ask for configuration options, and the build freezes at that > point, waiting for input. Its been running for 3 days, with no end in > sight, and I have to constantly check to see if the port/package build > requires input. > > Were this to default to the package default, I'd be happy. The fact > that it runs interactively, makes it untenable. > > Oh, and while I'm on a rant, when the freebsd-update package reports > upon the files that it will delete, it launches more, and if you "q"uit > out of the very long file list before it reaches the end, the update > script simply stops -- SILENTLY. > > perhaps I've missed some step or option to make this process less > painful, but I will *NEVER* again use freebsd-update to move to a new > release. > > I would STRONGLY recommend a fresh install from the release DVD ... Append: BATCH=yes to your /etc/make.conf -- Balwinder S "bdheeman" Dheeman Registered Linux User: #229709 Anu'z Linux(a)HOME (Unix Shoppe) Machines: #168573, 170593, 259192 Chandigarh, UT, 160062, India Plan9, T2, Arch/Debian/FreeBSD/XP Home: http://werc.homelinux.net/ Visit: http://counter.li.org/
From: Helmut Schneider on 3 Dec 2009 06:36 Spam(a)ControlQ.com wrote: > On Fri, 27 Nov 2009, Stan Barr wrote: > > > Date: 27 Nov 2009 16:28:18 GMT > > From: Stan Barr <plan.b(a)dsl.pipex.com> > > Newsgroups: comp.unix.bsd.freebsd.misc > > Subject: Re: FreeBSD 8.0 released! > > > >On Fri, 27 Nov 2009 07:39:26 +0100, Torfinn Ingolfsen > <tingo(a)start.no> wrote: > > > In case anybody missed it: > > > http://www.freebsd.org/releases/8.0R/announce.html > > > > Anyone know of anything to watch out for when upgrading? > > I've got 2 machines to do - amd64 and sparc64... > > > > Oh, and while I'm on a rant, when the freebsd-update package reports > upon the files that it will delete, it launches more, and if you > "q"uit out of the very long file list before it reaches the end, the > update script simply stops -- SILENTLY. > > perhaps I've missed some step or option to make this process less > painful, but I will NEVER again use freebsd-update to move to a new > release. Allthough I think freebsd-update is great for most users, especially for minor patches I prefer: - Get the new sources. - start sysinstall. - at "Options" in the "Release name" enter "8.0-RELEASE". - Chose "Upgrade". - Select an ftp/http server of your choice. - (When there is a "wrote -1 Bytes"-error just exist sysinstall and restart it) - Check that the kernel exists at /boot/kernel - Run "mergemaster -Fi". - Reboot Takes about 10 minutes. After upgrading your ports/packages using "BATCH=YES" cd to /usr/src and run "make check-old" (/delete-old/check-old-libs/delete-old-libs). Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn
From: Stan Barr on 3 Dec 2009 11:35
On Wed, 2 Dec 2009 14:52:06 -0500, Spam(a)ControlQ.com <Spam(a)ControlQ.com> wrote: > It seems that installed ports/packages must be recompiled/relinked. I > have 680 installed packages, and each one is being systematically > recompiled from the ports. This would be OK, were it not for the fact > that some (not all) ports launch a curses based window manager (text > based) to ask for configuration options, and the build freezes at that > point, waiting for input. Its been running for 3 days, with no end in > sight, and I have to constantly check to see if the port/package build > requires input. Oh dear...I guess I'll have the same problem :-( -- Cheers, Stan Barr plan.b .at. dsl .dot. pipex .dot. com The future was never like this! |