<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Daemonic Dispatches - Latest Comments in FreeBSD Update to 8.0-BETA1</title><link>http://daemonicdispatches.disqus.com/</link><description></description><atom:link href="https://daemonicdispatches.disqus.com/freebsd_update_to_80_beta1/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 08 Apr 2010 12:13:21 -0000</lastBuildDate><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-43882766</link><description>&lt;p&gt;Thanks for posting the instructions on performing a major version upgrade of FreeBSD using FreeBSD Update; Just keep on posting. Thanks  a lot!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">transfer to ipod</dc:creator><pubDate>Thu, 08 Apr 2010 12:13:21 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-37253976</link><description>&lt;p&gt;Yes, RELENG_8 is the tag for 8-STABLE, while RELENG_8_0 is the tag for the 8.0-RELEASE errata branch.  (And RELENG_8_0_0_RELEASE is the tag for the release itself.)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cperciva</dc:creator><pubDate>Sat, 27 Feb 2010 13:19:18 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-37237899</link><description>&lt;p&gt;After some delay, I upgraded my server. I grabbed the source with cvsup, then did the customary buildworld/build kernel/installworld sequence. My system is now upgraded, but it appears to be again a STABLE rather than a release version. Perhaps I misunderstood the tag option in the supfile; I used RELENG_8. Should I have used RELENG_8_0?&lt;/p&gt;&lt;p&gt;Anyway, looks like I will have to wait until the next RELEASE to get back into the STABLE sequence, so I can use freebsd-update.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Colin Brace</dc:creator><pubDate>Sat, 27 Feb 2010 11:18:05 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-29670473</link><description>&lt;p&gt;me again.. i installed misc/compat7x and that fixed the problem. would love a more detailed explanation on this.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jim</dc:creator><pubDate>Wed, 13 Jan 2010 15:30:22 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-29667754</link><description>&lt;p&gt;FreeBSD# smbd&lt;br&gt;/libexec/ld-elf.so.1: Shared object "libz.so.4" not found, required by "smbd"&lt;/p&gt;&lt;p&gt;FreeBSD# find / -name 'ld-elf.so.1' -print&lt;br&gt;/usr/libexec/ld-elf.so.1&lt;/p&gt;&lt;p&gt;Looks like the path changed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jim</dc:creator><pubDate>Wed, 13 Jan 2010 14:58:51 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-29667524</link><description>&lt;p&gt;trying to upgrade from 7.2-RELASE to 8.0-RELEASE and not sure where i'm going wrong any advice would be helpful.&lt;/p&gt;&lt;p&gt;i followed your steps but after the final reboot i'm trying to start samba and i'm getting the following library errors:&lt;/p&gt;&lt;p&gt;FreeBSD# /usr/local/etc/rc.d/samba onestart&lt;br&gt;Starting nmbd.&lt;br&gt;/libexec/ld-elf.so.1: Shared object "libcrypt.so.4" not found, required by "nmbd"&lt;br&gt;/usr/local/etc/rc.d/samba: WARNING: failed to start nmbd&lt;br&gt;Starting smbd.&lt;br&gt;/libexec/ld-elf.so.1: Shared object "libz.so.4" not found, required by "smbd"&lt;br&gt;/usr/local/etc/rc.d/samba: WARNING: failed to start smbd&lt;br&gt;Starting winbindd.&lt;br&gt;/libexec/ld-elf.so.1: Shared object "libcrypt.so.4" not found, required by "winbindd"&lt;br&gt;/usr/local/etc/rc.d/samba: WARNING: failed to start winbindd&lt;/p&gt;&lt;p&gt;any ideas?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jim</dc:creator><pubDate>Wed, 13 Jan 2010 14:56:16 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-28723557</link><description>&lt;p&gt;I understand better what was going on now.  When I tried to install 8.0, I noticed it was complaining about the GPT secondary partitions being corrupt, or some such.  After searching for GPT issues, I found that FreeBSD can use GPT partition tables, but with some manual steps OR you have to wipe out the GPT tables by dd'ing the first two and last two sectors of the disk from /dev/zero (FreeBSD doesn't overwrite the partition table when making entries apparently).  I zeroed my GPT, and now it works fine (though I still get some GEOM label removed warnings in 7.2).&lt;/p&gt;&lt;p&gt;I hadn't understood any of this the first time around, and didn't even know GPT existed.  The handbook makes no mention of GPT issues whatsoever, and neither does the installer.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">epte</dc:creator><pubDate>Wed, 06 Jan 2010 17:25:22 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-28203743</link><description>&lt;p&gt;Well, it just bit me, and here's what I've been able to figure out:&lt;/p&gt;&lt;p&gt;Ever after my 7.2 install, I had GEOM warnings, and GEOM labels being removed, and other nasty-looking messages.  I googled for it, and some people seemed to think it was benign, so I went on believing the extra messages were debug-level internal workings that could safely be ignored.  My computer worked like a charm for quite some time.&lt;/p&gt;&lt;p&gt;Then, when I upgraded to 8.0, several really nasty things happened.  As per the suggestion on the freebsd install site, I used freebsd-upgrade.  Nowhere did it tell me that it would whack my kernel, and not back up my old one.  I mean, c'mon.  Backing up the kernel is a given.&lt;/p&gt;&lt;p&gt;So here I am trying to boot my 8.0 kernel, and it can't mountroot.  It can't find the root partition.  Why is that?  The disklabel seems to be correct, because I can see my partitions with correct sizes when doing a "lsdev -v" from the bootloader prompt.  Booting into an install disk, however, shows that my primary labels (the fdisk-able partition table) is completely wrong!  Wrong numbers of partitions.  Wrong types.  Wrong starts and ends.  Wrong sizes.&lt;/p&gt;&lt;p&gt;So it seems that the 7.2 installer did a sucky job at partitioning my disk, the 7.2 kernel was able to read this mess (paying attention to the secondary labels -- the BSD disklabels), and the 8.0 kernel is no longer so tolerant.  Even if I _could_ get back my 7.2 kernel, I'd still be screwed in the end, because of my messed up partition table, which I've had since my install, it would seem.  It would be stuck in 7.2 without option to upgrade.&lt;/p&gt;&lt;p&gt;So, my options from this point are:&lt;br&gt;1) Try and deduce correct numbers and boot to a partitioning tool, and try to fix the DOS partition table.  I'm not a fan of the high probability of being one-off on my disk boundaries though.&lt;br&gt;2) Reinstall from scratch with 8.0, hoping that its installer knows what it's doing.&lt;/p&gt;&lt;p&gt;This is not giving me a good first impression of FreeBSD.  I've used various Linuxes and BSDs, and was giving FreeBSD a try.  I know better now than to trust the stability of the releases.  I'll have to double check everything.  :-(&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">epte</dc:creator><pubDate>Tue, 05 Jan 2010 02:01:32 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-24461158</link><description>&lt;p&gt;This is a GEOM issue which seems to bite some people but not others -- I'm not quite sure why.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cperciva</dc:creator><pubDate>Tue, 01 Dec 2009 15:26:30 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-24457617</link><description>&lt;p&gt;I upgraded a 7.2-RELEASE system. All went swimmingly, save that my disk devices where changed from daNs1D, where N is the drive number, and D the partition number. All of my devices were on slice 1. This isn't, I'm sure, a freebsd-update issue, but it was definitely a surprise. I may have caught a cold from going barefoot into the cellar where the machine is to fix the fstab file&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">B2Pi</dc:creator><pubDate>Tue, 01 Dec 2009 15:07:25 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-24249797</link><description>&lt;p&gt;When upgrading from 7.2-RELEASE, ipfw will be broken after booting into the new kernel.  I saw multiple ipfw kernel messages:&lt;/p&gt;&lt;p&gt;ipfw: size mismatch (have 64 want 68)&lt;br&gt;ipfw: size mismatch (have 44 want 48)&lt;/p&gt;&lt;p&gt;One workaround is to set firewall_enable="NO" before rebooting.  Otherwise, be prepared to grab console.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Benjamin Lee</dc:creator><pubDate>Sat, 28 Nov 2009 16:51:18 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-23295000</link><description>&lt;p&gt;I'm not sure where else to post issues with freebsd-update, so this seems like the best place for now to get Colin's attention. For users who have compiled a /boot/loader with ZFS support (since they are booting from ZFS), the freebsd-update to RC3 will replace that with a version which does NOT support booting from ZFS. This is very very annoying when the server is in a data centre...&lt;/p&gt;&lt;p&gt;Can I suggest that freebsd-update detect this condition and either:&lt;/p&gt;&lt;p&gt;1. install a loader with the broadest possible support (no one will complain will they?)&lt;br&gt;2. warn the user they are about to shoot themselves in the foot very painfully.&lt;/p&gt;&lt;p&gt;(1) would be much nicer.&lt;/p&gt;&lt;p&gt;Thanks for a great tool.&lt;br&gt;Ari&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ari Maniatis</dc:creator><pubDate>Mon, 16 Nov 2009 22:23:01 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-22862694</link><description>&lt;p&gt;The problem is that you're running 7.0-STABLE.  There is no way for freebsd-update to know where along the 7-STABLE branch you are between 7.0-RELEASE and 7.1-RELEASE, so it can't do things like figuring out what files you've modified locally etc.&lt;/p&gt;&lt;p&gt;You'll have to upgrade to a RELEASE via buildworld/buildkernel/installkernel/installworld before you can use FreeBSD Update to update your system.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cperciva</dc:creator><pubDate>Thu, 12 Nov 2009 17:45:27 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-22813847</link><description>&lt;p&gt;Hi,&lt;/p&gt;&lt;p&gt;I've used freebsd-update several times to upgrade systems quite successfully.&lt;/p&gt;&lt;p&gt;At the moment, I have 7.0-STABLE installed on a small server. I would like to upgrade it to 8.0-RC2.&lt;/p&gt;&lt;p&gt;To start with, I've updated all my ports with portupgrade.&lt;/p&gt;&lt;p&gt;However when I run freebsd-update the first time, I get error messages:&lt;/p&gt;&lt;p&gt;$ sudo freebsd-update -r 8.0-BETA1 upgrade&lt;br&gt;Looking up &lt;a href="http://update.FreeBSD.org" rel="nofollow noopener" target="_blank" title="update.FreeBSD.org"&gt;update.FreeBSD.org&lt;/a&gt; mirrors... 3 mirrors found.&lt;br&gt;Fetching metadata signature for 7.0-STABLE from &lt;a href="http://update5.FreeBSD.org" rel="nofollow noopener" target="_blank" title="update5.FreeBSD.org"&gt;update5.FreeBSD.org&lt;/a&gt;... failed.&lt;br&gt;Fetching metadata signature for 7.0-STABLE from &lt;a href="http://update4.FreeBSD.org" rel="nofollow noopener" target="_blank" title="update4.FreeBSD.org"&gt;update4.FreeBSD.org&lt;/a&gt;... failed.&lt;br&gt;Fetching metadata signature for 7.0-STABLE from &lt;a href="http://update2.FreeBSD.org" rel="nofollow noopener" target="_blank" title="update2.FreeBSD.org"&gt;update2.FreeBSD.org&lt;/a&gt;... failed.&lt;br&gt;No mirrors remaining, giving up.&lt;/p&gt;&lt;p&gt;I've googled this, and found various hits, but the problem and solution still aren't clear to me.&lt;/p&gt;&lt;p&gt;Thanks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Colin Brace</dc:creator><pubDate>Thu, 12 Nov 2009 05:12:28 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-20582847</link><description>&lt;p&gt;Yes.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cperciva</dc:creator><pubDate>Mon, 19 Oct 2009 17:45:37 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-20499743</link><description>&lt;p&gt;couldn't you simply revert to the generic kernel, perform the update, then revert back to your customised kernel (making appropriate changes due to version changes?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jamie</dc:creator><pubDate>Mon, 19 Oct 2009 11:58:21 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-16836810</link><description>&lt;p&gt;I've often started a portupgrade run, and come back an hour later to see that it's been waiting for me to answer a configuration question.   This can be especially frustrating when performing upgrades like this one on a system with many ports.&lt;/p&gt;&lt;p&gt;The solution is portupgrade's '-c' or '--config' option.  It makes portupgrade ask you all of the config dialogs at the *beginning* of the portupgrade run.  Much preferable.&lt;/p&gt;&lt;p&gt;So I recommend:&lt;/p&gt;&lt;p&gt;portupgrade -afc&lt;/p&gt;&lt;p&gt;Enjoy!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Royce</dc:creator><pubDate>Thu, 17 Sep 2009 17:23:31 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-12674940</link><description>&lt;p&gt;You cannot use this mechanism for updating a custom kernel. You need to compile from source the old fashioned way.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ari Maniatis</dc:creator><pubDate>Tue, 14 Jul 2009 23:31:32 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-12674920</link><description>&lt;p&gt;Last night we upgraded one of our servers from 7.2 to 8.0-beta1 using the freebsd-update tool and following the instructions on this blog. I believe this problem will occur even if we had used a source update mechanism.&lt;/p&gt;&lt;p&gt;The usual upgrade path is to install the new kernel, reboot, then install world. This fails because when rebooting into the 8.0 kernel with 7.2 userland, ZFS is unable to properly initialise and the file systems are not mounted. In our case we are booting with a small UFS partition to load the kernel, and then mounting /usr /var, etc from ZFS as per these instructions [1].&lt;/p&gt;&lt;p&gt;The problem with ZFS userland being out of sync with the kernel has been seen before [2] [3]. However now with lots of people running ZFS and starting to upgrade to 8.0, I think this will bite many more.&lt;/p&gt;&lt;p&gt;The workaround is to drop into single user mode, mount all the zfs partitions, and do the userland install.&lt;/p&gt;&lt;p&gt;mount -t zfs /usr&lt;br&gt;mount -t zfs /var&lt;br&gt;mount -o rw tank/root /&lt;/p&gt;&lt;p&gt;Those mount commands are slightly non-obvious and took a little guessing to get right. You can't use the 'zfs mount' command since it is broken at this point in time.&lt;/p&gt;&lt;p&gt;The other solution is to install userland BEFORE you reboot into the new kernel, although that may cause its own set of problems. Whatever the final solution, this needs to be clearly documented and ideally freebsd-update needs to detect the problem and advise the user about what to do.&lt;/p&gt;&lt;p&gt;Ari Maniatis&lt;/p&gt;&lt;p&gt;[1] &lt;a href="http://www.ish.com.au/solutions/articles/freebsdzfs" rel="nofollow noopener" target="_blank" title="http://www.ish.com.au/solutions/articles/freebsdzfs"&gt;http://www.ish.com.au/solut...&lt;/a&gt;&lt;br&gt;[2] &lt;a href="http://www.nabble.com/Re%3A-ZFS-MFC-heads-up-p23651130.html" rel="nofollow noopener" target="_blank" title="http://www.nabble.com/Re%3A-ZFS-MFC-heads-up-p23651130.html"&gt;http://www.nabble.com/Re%3A...&lt;/a&gt;&lt;br&gt;[3] &lt;a href="http://www.nabble.com/zfs-version-13-kernel-and-zfs-version-6-userland-tool--td20650216.html" rel="nofollow noopener" target="_blank" title="http://www.nabble.com/zfs-version-13-kernel-and-zfs-version-6-userland-tool--td20650216.html"&gt;http://www.nabble.com/zfs-v...&lt;/a&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ari Maniatis</dc:creator><pubDate>Tue, 14 Jul 2009 23:30:40 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-12623262</link><description>&lt;p&gt;Please sorry for my english.&lt;br&gt;How upgrade system with custom kernel?&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kegf</dc:creator><pubDate>Tue, 14 Jul 2009 07:16:34 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-12550813</link><description>&lt;p&gt;If you're installing a new system, you won't have to do any of the above -- this is just for upgrading existing systems.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cperciva</dc:creator><pubDate>Sun, 12 Jul 2009 13:17:32 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html#comment-12531577</link><description>&lt;p&gt;Mr. Percival -&lt;/p&gt;&lt;p&gt;So, if I'm starting from ground zero (fresh) with Sunday's AMD-x64 .iso on a wholly dedicated 80GB harddrive....there should be minimal additional hoops to jump thru, such as above. ...yes?  :-)&lt;/p&gt;&lt;p&gt;I'd had smooth working FreeBSD systems over the past couple of years and touted the features and ease of operation/install to others.  I underwent a major change in locale a year ago and just (now) coming back to FreeBSD.  It's not as I recalled.  Several of the 7-Betas did not work as expected.  With additional duties surrounding my job....I've lagged in keeping up.  I realize 99% of the problems are right in front of the keyboard!&lt;/p&gt;&lt;p&gt;I'll let 8-BETA1 download overnight as internet is not the quickest from the part of the world.  I will also update my FreeBSD Handbook.&lt;/p&gt;&lt;p&gt;Best Regards from South Asia,&lt;/p&gt;&lt;p&gt;Mike&lt;br&gt;Negombo, Sri Lanka &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">michaelathissell</dc:creator><pubDate>Sun, 12 Jul 2009 03:19:30 -0000</pubDate></item></channel></rss>