Re: FreeBSD 10.0-RC3 Now Available
Hi re@ cc stable@ current@ etc, Ref. my Fri Dec 27 15:25:57 UTC 2013 http://lists.freebsd.org/pipermail/freebsd-stable/2013-December/076604.html http://lists.freebsd.org/pipermail/freebsd-current/2013-December/047555.html Has someone checked src/ + ports/ has been re-made a seamless functional combination for named/bind ? There were various loose ends earlier (paths, defaults etc), after removal from src/. I'm asking as I think I will not be able to catch up in time to look check before release, ( I'm at RC2 downloading RC3 images rebuilding my svn tree that got corrupt, before I'll svn export make kernel world cd /usr/ports/dns/bind9* ; make install ) Ref 10.0-RC3 /usr/src/UPDATING 20130930 Bind threads listed below. A release without a bind that integrates as well as the one in src/ did, would probably be shunned by server admins get a bad name. Please stipulate which if any of ports/dns/bind9* is certified to integrate as seemlessly for 10.0-RC3, as did the one removed from src/ . Else consider reversion (except on current) of commits that removed named, until removers tidy loose ends. http://lists.freebsd.org/pipermail/freebsd-ports/2013-December/088649.html dns/bind* ports overwriting conf files Doug Barton dougb at dougbarton.us Thu Dec 26 06:16:08 UTC 2013 http://lists.freebsd.org/pipermail/freebsd-ports/2013-December/088294.html bind99 port Dennis Glatting dg at pki2.com Sat Dec 7 17:52:28 UTC 2013 http://lists.freebsd.org/pipermail/freebsd-stable/2013-December/076109.html BIND chroot environment in 10-RELEASE Lee Brown leeb at ratnaling.org Thu Dec 5 00:16:01 UTC 2013 http://lists.freebsd.org/pipermail/freebsd-current/2013-November/046591.html bind9 remnants Olivier Smedts olivier at gid0.org Thu Nov 14 10:02:59 UTC 2013 http://lists.freebsd.org/pipermail/freebsd-stable/2013-December/076065.html BIND segway - python - first-class ports Julian Elischer julian at freebsd.org Wed Dec 4 01:59:02 UTC 2013 http://lists.freebsd.org/pipermail/freebsd-ports/2013-December/088458.html BIND needs more TLC Erwin Lansing erwin at FreeBSD.org (who is MAINTAINER= of ports/dns/bind9* Tue Dec 17 13:27:19 UTC 2013 Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Interleave replies below like a play script. Indent old text with . Send plain text, not quoted-printable, HTML, base64, or multipart/alternative. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
On 12/27/13, Mathieu Arnold m...@freebsd.org wrote: +--On 27 décembre 2013 00:42:36 +0100 Zenny garbytr...@gmail.com wrote: | Much awaited release, thanks!. However, does the freebsd-update from | the earlier version bork in case of ZFS on Root? Or is there a safe | way to upgrade without borking. I had a very bad experience when I | upgraded from FreeBSD-10B3 to RC1. Thanks! I upgraded from 9.2 to 10.0-RC1, 10.0-RC2 and 10.0-RC3 with freebsd-update using zfs only boxes, never had any problem. The only thing is, if you run zpool upgrade, do remember to do what it tells you about updating the bootcode. In my case, I didn't receive any instructions to update the bootcode and the bug was acknowledged by the developer. However, can you tell me exactly what did you do exactly to update the bootcode? Appreciate it! -- Mathieu Arnold ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
+--On 27 décembre 2013 12:26:49 +0100 Zenny garbytr...@gmail.com wrote: | On 12/27/13, Mathieu Arnold m...@freebsd.org wrote: | +--On 27 décembre 2013 00:42:36 +0100 Zenny garbytr...@gmail.com | wrote: | | Much awaited release, thanks!. However, does the freebsd-update from | | the earlier version bork in case of ZFS on Root? Or is there a safe | | way to upgrade without borking. I had a very bad experience when I | | upgraded from FreeBSD-10B3 to RC1. Thanks! | | I upgraded from 9.2 to 10.0-RC1, 10.0-RC2 and 10.0-RC3 with | freebsd-update using zfs only boxes, never had any problem. The only | thing is, if you run zpool upgrade, do remember to do what it tells you | about updating the bootcode. | | | In my case, I didn't receive any instructions to update the bootcode | and the bug was acknowledged by the developer. | | However, can you tell me exactly what did you do exactly to update the | bootcode? Appreciate it! Well, when you run : # zpool upgrade yourpool it will not print a lot of things, but it will end with : If you boot from pool 'yourpool', don't forget to update boot code. Assuming you use GPT partitioning and da0 is your boot disk the following command will do it: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 All you have to do is adapt it to run your particular setup, replacing da0 with the correct disk (and running it for each disk where your pool is, in my case, it was mfid0 and mfid1.) -- Mathieu Arnold ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
On Thu, Dec 26, 2013 at 11:25:21AM -0500, Glen Barber wrote: [...] Pre-installed virtual machine images for 10.0-RC3 are also available for amd64 and i386 architectures. The images are located under the 'snapshots' directory on FTP, here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-RC3/ [...] - 10.0-RC3 i386: SHA256 (FreeBSD-10.0-RC3-i386.qcow2.xz) = 057610738176e19eab80b4a127e34ba4a2d1f1e8760c093c016a7f20c7d208d3 SHA256 (FreeBSD-10.0-RC3-i386.vhd.xz) = 4c798503632ae625ddf616a0006ff6039376e3dca0c2ac2375e5980beed99145 SHA256 (FreeBSD-10.0-RC3-i386.vmdk.xz) = 0edc8aaa7b7e968f560fa7dbf5dcad8a5e588f62dd793f0ebbecbc349db85084 MD5 (FreeBSD-10.0-RC3-i386.qcow2.xz) = 5857e8613c3b0685826a2b006d25564a MD5 (FreeBSD-10.0-RC3-i386.vhd.xz) = da0acf0bf5b3412fa4922e625a1c651e MD5 (FreeBSD-10.0-RC3-i386.vmdk.xz) = f4f0d948d4fd3afc3e41bbf511fd5240 An issue with the 10.0-RC3 i386 virtual machine images was brought to our attention. It is still unclear what exactly went wrong, but the images with the checksums above appear to be incomplete. The virtual machine images for i386 have been recreated, and are propagating to FTP now. It may still be a while yet before they are picked up by all mirrors. Checksums for the corrected images are: - 10.0-RC3 i386: SHA256 (FreeBSD-10.0-RC3-i386-20131223-r259778.qcow2.xz) = 76092c843bd91037cf94d48007cd5a054b0ee2744f5475ee50c558ba880520fa SHA256 (FreeBSD-10.0-RC3-i386-20131223-r259778.vhd.xz) = da8632d78cc89e1812c20f18a6aaac727e78ef44f1c3aedd4ffbe9318e50030e SHA256 (FreeBSD-10.0-RC3-i386-20131223-r259778.vmdk.xz) = 137ae9e44e419fc78823ac8f3cc7c9e32bfe5d7a80b7997a96d857dc1f3bd4fb MD5 (FreeBSD-10.0-RC3-i386-20131223-r259778.qcow2.xz) = 936736ff87b11d99408b5b7135c8a025 MD5 (FreeBSD-10.0-RC3-i386-20131223-r259778.vhd.xz) = 770895367a4b22631f54c25d81e11608 MD5 (FreeBSD-10.0-RC3-i386-20131223-r259778.vmdk.xz) = ba62a266ab560711bed0ff53a3177b94 Sorry for the inconvenience to those who have downloaded the incomplete images. Glen pgpQ52lXbeYc2.pgp Description: PGP signature
Re: FreeBSD 10.0-RC3 Now Available
The third RC build of the 10.0-RELEASE release cycle is now available Nice :-) Has someone checked src/ + ports/ has been re-made a seamless functional combination for named/bind ? There were various loose ends earlier (paths, defaults etc), after removal from src/. I'm asking as I think I will not be able to catch up in time to look check before release, ( I'm at RC2 downloading RC3 images rebuilding my svn tree that got corrupt, before I'll svn export make kernel world cd /usr/ports/dns/bind9* ; make install ) Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Interleave replies below like a play script. Indent old text with . Send plain text, not quoted-printable, HTML, base64, or multipart/alternative. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
All the examples I've seen for updating bootcode assume GPT. If one has MBR (as I do) and assuming the following basic scheme: gpart show ada0 = 63 976773105 ada0 MBR (466G) 63 976773105 1 freebsd [active] (466G) gpart show ada0s1 =0 976773105 ada0s1 BSD (466G) 0 943218736 1 freebsd-zfs (450G) 943218736 33554369 2 freebsd-swap (16G) would the equivalent bootcode statement be: gpart bootcode -b /boot/pmbr -p /boot/zfsboot ada0s1 where the boot code is /boot/zfsboot (rather than /boot/gptzfsboot) and ada0s1 is the slice on which FreeBSD is installed? Thanks. On Fri, Dec 27, 2013 at 9:33 AM, Mathieu Arnold m...@freebsd.org wrote: +--On 27 décembre 2013 12:26:49 +0100 Zenny garbytr...@gmail.com wrote: | On 12/27/13, Mathieu Arnold m...@freebsd.org wrote: | +--On 27 décembre 2013 00:42:36 +0100 Zenny garbytr...@gmail.com | wrote: | | Much awaited release, thanks!. However, does the freebsd-update from | | the earlier version bork in case of ZFS on Root? Or is there a safe | | way to upgrade without borking. I had a very bad experience when I | | upgraded from FreeBSD-10B3 to RC1. Thanks! | | I upgraded from 9.2 to 10.0-RC1, 10.0-RC2 and 10.0-RC3 with | freebsd-update using zfs only boxes, never had any problem. The only | thing is, if you run zpool upgrade, do remember to do what it tells you | about updating the bootcode. | | | In my case, I didn't receive any instructions to update the bootcode | and the bug was acknowledged by the developer. | | However, can you tell me exactly what did you do exactly to update the | bootcode? Appreciate it! Well, when you run : # zpool upgrade yourpool it will not print a lot of things, but it will end with : If you boot from pool 'yourpool', don't forget to update boot code. Assuming you use GPT partitioning and da0 is your boot disk the following command will do it: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 All you have to do is adapt it to run your particular setup, replacing da0 with the correct disk (and running it for each disk where your pool is, in my case, it was mfid0 and mfid1.) -- Mathieu Arnold ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
+--On 27 décembre 2013 10:28:07 -0500 Thomas Hoffmann trh...@gmail.com wrote: | All the examples I've seen for updating bootcode assume GPT. If one has | MBR (as I do) and assuming the following basic scheme: | | gpart show ada0 | = 63 976773105 ada0 MBR (466G) | 63 976773105 1 freebsd [active] (466G) | | gpart show ada0s1 | =0 976773105 ada0s1 BSD (466G) | 0 943218736 1 freebsd-zfs (450G) | 943218736 33554369 2 freebsd-swap (16G) | | would the equivalent bootcode statement be: | | gpart bootcode -b /boot/pmbr -p /boot/zfsboot ada0s1 | | where the boot code is /boot/zfsboot (rather than /boot/gptzfsboot) and | ada0s1 is the slice on which FreeBSD is installed? Hum, no, if you're using MBR and not GPT, you can't use gpart, you have to do something aweful like this : # dd if=/boot/zfsboot of=/dev/ada0 count=1 # sysctl kern.geom.debugflags=0x10 # dd if=/boot/zfsboot of=/dev/ada0 skip=1 seek=1024 might be ada0s1 and not ada0, or something (please, don't do that unless you're sure you're doing it right.) -- Mathieu Arnold ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
On Fri, 27 Dec 2013, Mathieu Arnold wrote: +--On 27 décembre 2013 10:28:07 -0500 Thomas Hoffmann trh...@gmail.com wrote: | All the examples I've seen for updating bootcode assume GPT. If one has | MBR (as I do) and assuming the following basic scheme: | | gpart show ada0 | = 63 976773105 ada0 MBR (466G) | 63 976773105 1 freebsd [active] (466G) | | gpart show ada0s1 | =0 976773105 ada0s1 BSD (466G) | 0 943218736 1 freebsd-zfs (450G) | 943218736 33554369 2 freebsd-swap (16G) | | would the equivalent bootcode statement be: | | gpart bootcode -b /boot/pmbr -p /boot/zfsboot ada0s1 No, the PMBR is for GPT partitioning only. | where the boot code is /boot/zfsboot (rather than /boot/gptzfsboot) and | ada0s1 is the slice on which FreeBSD is installed? Hum, no, if you're using MBR and not GPT, you can't use gpart, Why not? gpart is not GPT-specific. It handles MBR and BSDlabel bootcode correctly. you have to do something aweful like this : # dd if=/boot/zfsboot of=/dev/ada0 count=1 That will overwrite the MBR partition table. # sysctl kern.geom.debugflags=0x10 # dd if=/boot/zfsboot of=/dev/ada0 skip=1 seek=1024 That seems dangerous. I have not tried with zfsboot, but this should be close: # gpart bootcode -b /boot/zfsboot ada0 # gpart bootcode -b /boot/zfsboot ada0s1 Untested! The first one may need to use /boot/mbr. A better way to do this, provided the system does not have a broken BIOS, would be to backup, repartition with GPT, and restore, avoiding the complication of multiple partitioning schemes. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
On Fri, Dec 27, 2013 at 03:33:23PM +0100 I heard the voice of
Mathieu Arnold, and lo! it spake thus:
All you have to do is adapt it to run your particular setup,
replacing da0 with the correct disk (and running it for each disk
where your pool is, in my case, it was mfid0 and mfid1.)
I've taken to just dumping a rewrite-bootcode.sh script in /boot/ on
systems. That way I don't have to remember or re-figure the
invocation, or worry about typos, or whatnot. Makes it easy to just
kick the script after every installworld whether I really need it or
not, without having to think about it.
e.g.,
% cat /boot/rewrite-bootcode.sh
#!/bin/sh -x
for i in /dev/ada0 /dev/ada1; do
gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ${i}
done
--
Matthew Fuller (MF4839) | fulle...@over-yonder.net
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
+--On 27 décembre 2013 10:17:14 -0600 Matthew D. Fuller fulle...@over-yonder.net wrote: | On Fri, Dec 27, 2013 at 03:33:23PM +0100 I heard the voice of | Mathieu Arnold, and lo! it spake thus: | | All you have to do is adapt it to run your particular setup, | replacing da0 with the correct disk (and running it for each disk | where your pool is, in my case, it was mfid0 and mfid1.) | | I've taken to just dumping a rewrite-bootcode.sh script in /boot/ on | systems. That way I don't have to remember or re-figure the | invocation, or worry about typos, or whatnot. Makes it easy to just | kick the script after every installworld whether I really need it or | not, without having to think about it. You *don't* need it after installworld, or freebsd-update install. You *only* need it if you *explicitly* run zpool upgrade yourzpool. And if you do that, zpool upgrade tells you to run it. If you forget to run zpool upgrade, or you don't run it, you don't need to upgrade the bootcode. -- Mathieu Arnold ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
After I posted, it occurred to me to check out the ../bsdinstall/scripts/zfsboot script to see how the boot code was laid down when the MBR was created. It shows only: dd if=/boot/zfsboot of=/dev/ada0s1 count =1 But, adding to my confusion, the FreeBSD wiki for ZFS on root (MBR-style) shows something very close to what Mathieu suggested. Unfortunately, I'm using an iMac with FreeBSD as the only OS. MBR is the only way I can get it to boot after an install. Looks like I've got some testing (and possible system restores) ahead of me. Thanks. On Fri, Dec 27, 2013 at 11:08 AM, Warren Block wbl...@wonkity.com wrote: On Fri, 27 Dec 2013, Mathieu Arnold wrote: +--On 27 décembre 2013 10:28:07 -0500 Thomas Hoffmann trh...@gmail.com wrote: | All the examples I've seen for updating bootcode assume GPT. If one has | MBR (as I do) and assuming the following basic scheme: | | gpart show ada0 | = 63 976773105 ada0 MBR (466G) | 63 976773105 1 freebsd [active] (466G) | | gpart show ada0s1 | =0 976773105 ada0s1 BSD (466G) | 0 943218736 1 freebsd-zfs (450G) | 943218736 33554369 2 freebsd-swap (16G) | | would the equivalent bootcode statement be: | | gpart bootcode -b /boot/pmbr -p /boot/zfsboot ada0s1 No, the PMBR is for GPT partitioning only. | where the boot code is /boot/zfsboot (rather than /boot/gptzfsboot) and | ada0s1 is the slice on which FreeBSD is installed? Hum, no, if you're using MBR and not GPT, you can't use gpart, Why not? gpart is not GPT-specific. It handles MBR and BSDlabel bootcode correctly. you have to do something aweful like this : # dd if=/boot/zfsboot of=/dev/ada0 count=1 That will overwrite the MBR partition table. # sysctl kern.geom.debugflags=0x10 # dd if=/boot/zfsboot of=/dev/ada0 skip=1 seek=1024 That seems dangerous. I have not tried with zfsboot, but this should be close: # gpart bootcode -b /boot/zfsboot ada0 # gpart bootcode -b /boot/zfsboot ada0s1 Untested! The first one may need to use /boot/mbr. A better way to do this, provided the system does not have a broken BIOS, would be to backup, repartition with GPT, and restore, avoiding the complication of multiple partitioning schemes. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
On Fri, Dec 27, 2013 at 05:21:12PM +0100 I heard the voice of Mathieu Arnold, and lo! it spake thus: You *don't* need it after installworld, or freebsd-update install. You *only* need it if you *explicitly* run zpool upgrade yourzpool. Well, that was my point; by removing the need to have to think about how to do it, I can just do it any time I rebuild bootcode, whether I need it or not. Makes life simpler. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
On Friday, December 27, 2013 11:08:08 am Warren Block wrote: On Fri, 27 Dec 2013, Mathieu Arnold wrote: +--On 27 décembre 2013 10:28:07 -0500 Thomas Hoffmann trh...@gmail.com wrote: | All the examples I've seen for updating bootcode assume GPT. If one has | MBR (as I do) and assuming the following basic scheme: | | gpart show ada0 | = 63 976773105 ada0 MBR (466G) | 63 976773105 1 freebsd [active] (466G) | | gpart show ada0s1 | =0 976773105 ada0s1 BSD (466G) | 0 943218736 1 freebsd-zfs (450G) | 943218736 33554369 2 freebsd-swap (16G) | | would the equivalent bootcode statement be: | | gpart bootcode -b /boot/pmbr -p /boot/zfsboot ada0s1 No, the PMBR is for GPT partitioning only. | where the boot code is /boot/zfsboot (rather than /boot/gptzfsboot) and | ada0s1 is the slice on which FreeBSD is installed? Hum, no, if you're using MBR and not GPT, you can't use gpart, Why not? gpart is not GPT-specific. It handles MBR and BSDlabel bootcode correctly. you have to do something aweful like this : # dd if=/boot/zfsboot of=/dev/ada0 count=1 That will overwrite the MBR partition table. # sysctl kern.geom.debugflags=0x10 # dd if=/boot/zfsboot of=/dev/ada0 skip=1 seek=1024 That seems dangerous. I have not tried with zfsboot, but this should be close: # gpart bootcode -b /boot/zfsboot ada0 # gpart bootcode -b /boot/zfsboot ada0s1 No, the ZFS MBR bootstrap doesn't use the standard boot block areas. The only standard boot block area for ada0 is the MBR itself, but ZFS uses a larger bootloader that installs one part into the MBR and another part a few sectors later in the disk. gpart has no knowledge of that AFAIK. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
On Fri, Dec 27, 2013 at 10:08 AM, Warren Block wbl...@wonkity.com wrote: On Fri, 27 Dec 2013, Mathieu Arnold wrote: +--On 27 décembre 2013 10:28:07 -0500 Thomas Hoffmann trh...@gmail.com wrote: | All the examples I've seen for updating bootcode assume GPT. If one has | MBR (as I do) and assuming the following basic scheme: | | gpart show ada0 | = 63 976773105 ada0 MBR (466G) | 63 976773105 1 freebsd [active] (466G) | | gpart show ada0s1 | =0 976773105 ada0s1 BSD (466G) | 0 943218736 1 freebsd-zfs (450G) | 943218736 33554369 2 freebsd-swap (16G) | | would the equivalent bootcode statement be: | | gpart bootcode -b /boot/pmbr -p /boot/zfsboot ada0s1 No, the PMBR is for GPT partitioning only. | where the boot code is /boot/zfsboot (rather than /boot/gptzfsboot) and | ada0s1 is the slice on which FreeBSD is installed? Hum, no, if you're using MBR and not GPT, you can't use gpart, Why not? gpart is not GPT-specific. It handles MBR and BSDlabel bootcode correctly. you have to do something aweful like this : # dd if=/boot/zfsboot of=/dev/ada0 count=1 That will overwrite the MBR partition table. # sysctl kern.geom.debugflags=0x10 # dd if=/boot/zfsboot of=/dev/ada0 skip=1 seek=1024 That seems dangerous. I have not tried with zfsboot, but this should be close: # gpart bootcode -b /boot/zfsboot ada0 # gpart bootcode -b /boot/zfsboot ada0s1 Untested! The first one may need to use /boot/mbr. A better way to do this, provided the system does not have a broken BIOS, would be to backup, repartition with GPT, and restore, avoiding the complication of multiple partitioning schemes. The correct way to install/update ZFS Boot code on an MBR disk is: Install boot Manager (required on first install) # gpart bootcode -b /boot/boot0 ad0 Note: /boot/mbr could also be used if you are not multibooting Install ZFS boot1 stage # sysctl kern.geom.debugflags=0x10 # dd if=/boot/zfsboot of=/dev/ada0s1 count=1 or # dd if=/boot/zfsboot of=/tmp/zfsboot1 count=1 # gpart bootcode -b /tmp/zfsboot1 /dev/ada0s1 Install ZFS boot2 stage # dd if=/boot/zfsboot of=/dev/ada0s1a skip=1 seek=1024 -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
On Fri, Dec 27, 2013 at 12:15 PM, Scot Hetzel swhet...@gmail.com wrote: The correct way to install/update ZFS Boot code on an MBR disk is: Install boot Manager (required on first install) # gpart bootcode -b /boot/boot0 ad0 Note: /boot/mbr could also be used if you are not multibooting Install ZFS boot1 stage # sysctl kern.geom.debugflags=0x10 # dd if=/boot/zfsboot of=/dev/ada0s1 count=1 or # dd if=/boot/zfsboot of=/tmp/zfsboot1 count=1 # gpart bootcode -b /tmp/zfsboot1 /dev/ada0s1 Install ZFS boot2 stage # dd if=/boot/zfsboot of=/dev/ada0s1a skip=1 seek=1024 This ties everything together nicely for me, especially the part about the first bootcode install, which had me really confused. Thanks. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
FreeBSD 10.0-RC3 Now Available
The third RC build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are available here (or any of the FreeBSD mirror sites): ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.0/ If you notice problems you can report them through the normal GNATS PR system or here on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the releng/10.0 branch. Important note to freebsd-update(8) users: Please be sure to follow the instructions in the following FreeBSD Errata Notices before upgrading the system to 10.0-RC3: - EN-13:04.freebsd-update: http://www.freebsd.org/security/advisories/FreeBSD-EN-13:04.freebsd-update.asc - EN-13:05.freebsd-update: http://www.freebsd.org/security/advisories/FreeBSD-EN-13:05.freebsd-update.asc Pre-installed virtual machine images for 10.0-RC3 are also available for amd64 and i386 architectures. The images are located under the 'snapshots' directory on FTP, here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-RC3/ The disk images are available in both QCOW2, VHD, and VMDK format. The image download size is approximately 135 MB, which decompress to a 20GB sparse image. The partition layout is: - 512k - freebsd-boot GPT partition type (bootfs GPT label) - 1GB - freebsd-swap GPT partition type (swapfs GPT label) - ~17GB - freebsd-ufs GPT partition type (rootfs GPT label) Changes between -RC2 and -RC3 include: - Several minor bugfixes and functionality enhancements to bhyve. - Add new sysctl, kern.supported_archs, containing the list of FreeBSD MACHINE_ARCH values whose binaries this kernel can run. - Add a pkg(8) repository configuration file for cdrom-based package installation. - Implement a fix to allow bsdconfig(8) to be able to install packages included on the DVD. - Fix pkg(8) multi-repository support by properly respecting 'enabled' flag. - Fix Xen build without INET. - Several bugfixes to bsdinstall(8). - Fix a ZFS-related panic triggered by an incorrect assertion. - Fix mountroot prompt eating most of the characters by not enabling RXRDY interrupts in the attach routine. - Fix a regression in ng_ksocket(4). - Apply patch from upstream Heimdal for encoding fix The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 10.0-RC3 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 9.x. Alternatively, the user can install misc/compat9x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == - 10.0-RC3 amd64: SHA256 (FreeBSD-10.0-RC3-amd64-bootonly.iso) = a446af2ca4da7b5a5f7513f025fc5727abf0dac051540b1f04596223700e60cd SHA256 (FreeBSD-10.0-RC3-amd64-disc1.iso) = a4b16d3e4e04f1dbb9184fdbe18d6587124a6ea2a1794f79122d57373865ab6b SHA256 (FreeBSD-10.0-RC3-amd64-dvd1.iso) = ce4edab5d5b485f6478e6171c1de64e9b337109256c5eb5257aceccd78224255 SHA256 (FreeBSD-10.0-RC3-amd64-memstick.img) = 642ff8ad66ead06b18bcf171be79f3f42e6c36bbe0b741c6d98d32a89fb6724a MD5 (FreeBSD-10.0-RC3-amd64-bootonly.iso) = 584745fc67ca974c146065aa3b3a9a94 MD5 (FreeBSD-10.0-RC3-amd64-disc1.iso) = fc93de26dc0b2ca1e88cc2fcda18ec05 MD5 (FreeBSD-10.0-RC3-amd64-dvd1.iso) = ed93640aca43b484697d203c7b6f0ab3 MD5 (FreeBSD-10.0-RC3-amd64-memstick.img) = 416ca9f9973e405afba58c11a90c6d7a - 10.0-RC3 i386: SHA256 (FreeBSD-10.0-RC3-i386-bootonly.iso) = 1c191afa34e4a8119362c7b08b4e6265fcb0017afd508b060c49de7bcbd5ece3 SHA256 (FreeBSD-10.0-RC3-i386-disc1.iso) = 2d03929465da9042a5424cf97577c4811500a0df4a454631a2aaef41350fe211 SHA256 (FreeBSD-10.0-RC3-i386-dvd1.iso) = 517aced324eac22fe6e65716d63b6d112c0fbac33c243ff327f97e7b6b7cd584 SHA256 (FreeBSD-10.0-RC3-i386-memstick.img) = d4edc43daf0026d2914f8960a81a2511d8cf8a99c7b8537a7354dfce5066f4ab MD5 (FreeBSD-10.0-RC3-i386-bootonly.iso) =
Re: FreeBSD 10.0-RC3 Now Available
On Thu, Dec 26, 2013 at 11:25 AM, Glen Barber g...@freebsd.org wrote: The third RC build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are available here (or any of the FreeBSD mirror sites): ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.0/ If you notice problems you can report them through the normal GNATS PR system or here on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the releng/10.0 branch. Important note to freebsd-update(8) users: Please be sure to follow the instructions in the following FreeBSD Errata Notices before upgrading the system to 10.0-RC3: - EN-13:04.freebsd-update: http://www.freebsd.org/security/advisories/FreeBSD-EN-13:04.freebsd-update.asc - EN-13:05.freebsd-update: http://www.freebsd.org/security/advisories/FreeBSD-EN-13:05.freebsd-update.asc Pre-installed virtual machine images for 10.0-RC3 are also available for amd64 and i386 architectures. The images are located under the 'snapshots' directory on FTP, here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-RC3/ The disk images are available in both QCOW2, VHD, and VMDK format. The image download size is approximately 135 MB, which decompress to a 20GB sparse image. The partition layout is: - 512k - freebsd-boot GPT partition type (bootfs GPT label) - 1GB - freebsd-swap GPT partition type (swapfs GPT label) - ~17GB - freebsd-ufs GPT partition type (rootfs GPT label) Changes between -RC2 and -RC3 include: - Several minor bugfixes and functionality enhancements to bhyve. - Add new sysctl, kern.supported_archs, containing the list of FreeBSD MACHINE_ARCH values whose binaries this kernel can run. - Add a pkg(8) repository configuration file for cdrom-based package installation. - Implement a fix to allow bsdconfig(8) to be able to install packages included on the DVD. - Fix pkg(8) multi-repository support by properly respecting 'enabled' flag. - Fix Xen build without INET. - Several bugfixes to bsdinstall(8). - Fix a ZFS-related panic triggered by an incorrect assertion. - Fix mountroot prompt eating most of the characters by not enabling RXRDY interrupts in the attach routine. - Fix a regression in ng_ksocket(4). - Apply patch from upstream Heimdal for encoding fix The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 10.0-RC3 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 9.x. Alternatively, the user can install misc/compat9x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == - 10.0-RC3 amd64: SHA256 (FreeBSD-10.0-RC3-amd64-bootonly.iso) = a446af2ca4da7b5a5f7513f025fc5727abf0dac051540b1f04596223700e60cd SHA256 (FreeBSD-10.0-RC3-amd64-disc1.iso) = a4b16d3e4e04f1dbb9184fdbe18d6587124a6ea2a1794f79122d57373865ab6b SHA256 (FreeBSD-10.0-RC3-amd64-dvd1.iso) = ce4edab5d5b485f6478e6171c1de64e9b337109256c5eb5257aceccd78224255 SHA256 (FreeBSD-10.0-RC3-amd64-memstick.img) = 642ff8ad66ead06b18bcf171be79f3f42e6c36bbe0b741c6d98d32a89fb6724a MD5 (FreeBSD-10.0-RC3-amd64-bootonly.iso) = 584745fc67ca974c146065aa3b3a9a94 MD5 (FreeBSD-10.0-RC3-amd64-disc1.iso) = fc93de26dc0b2ca1e88cc2fcda18ec05 MD5 (FreeBSD-10.0-RC3-amd64-dvd1.iso) = ed93640aca43b484697d203c7b6f0ab3 MD5 (FreeBSD-10.0-RC3-amd64-memstick.img) = 416ca9f9973e405afba58c11a90c6d7a - 10.0-RC3 i386: SHA256 (FreeBSD-10.0-RC3-i386-bootonly.iso) = 1c191afa34e4a8119362c7b08b4e6265fcb0017afd508b060c49de7bcbd5ece3 SHA256 (FreeBSD-10.0-RC3-i386-disc1.iso) = 2d03929465da9042a5424cf97577c4811500a0df4a454631a2aaef41350fe211 SHA256 (FreeBSD-10.0-RC3-i386-dvd1.iso) = 517aced324eac22fe6e65716d63b6d112c0fbac33c243ff327f97e7b6b7cd584 SHA256
Re: FreeBSD 10.0-RC3 Now Available
On Thu, Dec 26, 2013 at 04:17:27PM -0500, Joe Nosay wrote: I take it that building world and kernel from source should present no problems, right? Is the latest CLang at 3.5 being used or will I need to hack the Makefile in /usr/ports/lang to build it? Both world and kernel are built with clang by default. Glen pgp70eH4pPDIK.pgp Description: PGP signature
Re: FreeBSD 10.0-RC3 Now Available
Much awaited release, thanks!. However, does the freebsd-update from the earlier version bork in case of ZFS on Root? Or is there a safe way to upgrade without borking. I had a very bad experience when I upgraded from FreeBSD-10B3 to RC1. Thanks! On 12/26/13, Glen Barber g...@freebsd.org wrote: On Thu, Dec 26, 2013 at 04:17:27PM -0500, Joe Nosay wrote: I take it that building world and kernel from source should present no problems, right? Is the latest CLang at 3.5 being used or will I need to hack the Makefile in /usr/ports/lang to build it? Both world and kernel are built with clang by default. Glen ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC3 Now Available
+--On 27 décembre 2013 00:42:36 +0100 Zenny garbytr...@gmail.com wrote: | Much awaited release, thanks!. However, does the freebsd-update from | the earlier version bork in case of ZFS on Root? Or is there a safe | way to upgrade without borking. I had a very bad experience when I | upgraded from FreeBSD-10B3 to RC1. Thanks! I upgraded from 9.2 to 10.0-RC1, 10.0-RC2 and 10.0-RC3 with freebsd-update using zfs only boxes, never had any problem. The only thing is, if you run zpool upgrade, do remember to do what it tells you about updating the bootcode. -- Mathieu Arnold ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
