Re: 8.2/7.4-RELEASEs Announced...
Le Thu, 24 Feb 2011 16:26:23 -0500, Ken Smith kensm...@buffalo.edu a écrit : Hello, 8.2-RELEASE and 7.4-RELEASE have been announced. The announcement messages are available here: http://www.freebsd.org/releases/8.2R/announce.html There is a small typo in the name of the usb image: « memstick This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a livefs based rescue mode. The documentation packages are provided but no other packages. ... # dd if=8.2-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync » should be FreeBSD-8.2-RELEASE-amd64-memstick.img Enjoy. :-) Thanks! Regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
On Tue, Mar 01, 2011 at 10:26:07AM +0100, Patrick Lamaiziere wrote: Le Thu, 24 Feb 2011 16:26:23 -0500, Ken Smith kensm...@buffalo.edu a écrit : Hello, 8.2-RELEASE and 7.4-RELEASE have been announced. The announcement messages are available here: http://www.freebsd.org/releases/8.2R/announce.html There is a small typo in the name of the usb image: « memstick This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a livefs based rescue mode. The documentation packages are provided but no other packages. ... # dd if=8.2-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync » should be FreeBSD-8.2-RELEASE-amd64-memstick.img Not to mention, the block size specified doesn't jibe with what's in the FreeBSD Handbook (which uses bs=64k): http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html Other users have pointed this out to me on my blog, wondering exactly where bs=10240 came from. So, the release notes going forward should probably use bs=64k. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
On Tue, 2011-03-01 at 10:26 +0100, Patrick Lamaiziere wrote: Le Thu, 24 Feb 2011 16:26:23 -0500, Ken Smith kensm...@buffalo.edu a écrit : Hello, 8.2-RELEASE and 7.4-RELEASE have been announced. The announcement messages are available here: http://www.freebsd.org/releases/8.2R/announce.html There is a small typo in the name of the usb image: « memstick This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a livefs based rescue mode. The documentation packages are provided but no other packages. ... # dd if=8.2-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync » should be FreeBSD-8.2-RELEASE-amd64-memstick.img Enjoy. :-) Thanks! Regards. Hmm, it's right in the message sent to announce@ but not in the Web version. I had made that typo in previous announcements but corrected it with 8.2's announcement. I'll see if it can be fixed in the Web version. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: 8.2/7.4-RELEASEs Announced...
On Tue, 2011-03-01 at 02:05 -0800, Jeremy Chadwick wrote: Not to mention, the block size specified doesn't jibe with what's in the FreeBSD Handbook (which uses bs=64k): http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html Other users have pointed this out to me on my blog, wondering exactly where bs=10240 came from. So, the release notes going forward should probably use bs=64k. I'll try to remember to adjust that for 8.3. I started off suggesting the 10240 value because that's what gets used in the script that builds the memstick images (and the block size there is used for some mathematics to determine file sizes so a larger size would potentially waste more space...). But as people with less patience than me have noticed 64k results in a much faster transfer... ;-) -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: 8.2/7.4-RELEASEs Announced...
On Fri, Feb 25, 2011 at 03:01:11PM -0500, John Baldwin wrote: ... No, release branches long pre-date freebsd-update. However, before we switched to svn for source, new branches did not bump all the $FreeBSD$ tags. That is a side effect of the way that the SVN - CVS exporter works (and arguably a bug). BTW, I did design etcupdate to support this sort of use case (you can build a tarball from a given release tree and use that as the basis for comparisons assuming you were bootstrapped to use etcupdate). Currently freebsd-update doesn't use etcupdate and the author doesn't have any interest in changing it to do so. At some point if I have some time to hack on freebsd-update to be more useful for modified versions of FreeBSD (e.g. building snaps from tags in an SVN repository instead of a directory of patches against a CVS checkout), I will probably hack it to support using etcupdate to manage /etc updates as well. (etcupdate uses something akin to 'svn up' to update files in /etc, so things like $FreeBSD$ changes just auto-update assuming they don't result in merge conficts.) That would be nice. Since freebsd-update clearly has done something like generate the deltas for X.Y-Z.W for /etc files, if it were to assume the status quo ante is that files in /etc are based on the X.Y version of the /etc, it should already be able to do slightly smarter things than it's doing. Hmmm. -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
On Fri, Feb 25, 2011 at 03:01:11PM -0500, John Baldwin thus spake: On Friday, February 25, 2011 1:00:19 pm jhelf...@e-e.com wrote: On Fri, Feb 25, 2011 at 02:42:25PM +0100, Marco van Tol wrote: Read up on the mergemaster manual for options -F and -i :-) freebsd-update does not use mergemaster, though probably it should. My understanding is that freebsd-update was introduced prior to releases being branched, so this issue surfaced at that time. The patch I believe would be a fix to the freebsd-update client to better handle the tag. I can't see mergemaster as being an easier solution, as the actual binary would need to be verified against a known good index that would exist on the update server. No, release branches long pre-date freebsd-update. However, before we switched to svn for source, new branches did not bump all the $FreeBSD$ tags. That is a side effect of the way that the SVN - CVS exporter works (and arguably a bug). Yes. This is what I was trying to explain. Thanks for clearing this up, John. BTW, I did design etcupdate to support this sort of use case (you can build a tarball from a given release tree and use that as the basis for comparisons assuming you were bootstrapped to use etcupdate). Currently freebsd-update doesn't use etcupdate and the author doesn't have any interest in changing it to do so. Speaking as an administrator of my own set of freebsd-update-servers, I would suggest a different path to solve the issue. I am not certain what the exact path would be, but let me attempt to explain the issues I believe would come up. The freebsd-update-server software builds binary updates for distribution using that are updated using the freebsd-client off of an actual distribution iso that is built using the standard 'make release' process. So in edition to modifying the freebsd-update-server code to not build this portion of the release, or at least not distribute it, the client would need to be aware not to look for it, as well. You can update the client to use a different method for updating /etc, however the freebsd-update mirror servers will still be distributing the files, so you will have either a similar issue, or a new issue. Using the freebsd-update-software, I am not only able to apply security patches that are distributed by the security team, but I can also apply patches to /etc, or any part of the release for that matter, when it comes to distribution of updates from my updates servers. This is the flexibility I enjoy, and celebrate, in using FreeBSD. All of this being said, if an update software, and respective client were created specifically for /etc, it would be great to have similar functionality, in building off of a distributed iso, with the possibility of patching available, so this functionality is not lost. In addition to this, also using keyprints to authenticate the client, and distribute in a similar matter. I am copying Colin on this, in case he has any thoughts on the matter, or ideas that may make this a possibility. At some point if I have some time to hack on freebsd-update to be more useful for modified versions of FreeBSD (e.g. building snaps from tags in an SVN repository instead of a directory of patches against a CVS checkout), I will probably hack it to support using etcupdate to manage /etc updates as well. This would be great, if you can have it build and work off of a distributed iso. It would be very disappointing to be restricted to an svn/cvs tag/branch from FreeBSD, without the flexibility that is possible now using the freebsd-update-server software. This flexibility allows me to distribute binary updates for a custom kernel, and to modify /etc and distribute it at my leisure. (etcupdate uses something akin to 'svn up' to update files in /etc, so things like $FreeBSD$ changes just auto-update assuming they don't result in merge conficts.) -- John Baldwin Thanks, and would enjoy being in on any future development thoughts, or ideas regarding your work on this. Jason -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
When I was looking at this problem myself recently it occurred to me that one way to handle it would be to have the freebsd-update code build and populate the temproot directory that mergemaster uses and then offer the user the option to use that alternative. The process could use something like what's done in src/release/scripts/mm-mtree.sh if this direction is desirable. Obviously the temproot directory would have to be distributed as an additional blob by freebsd-update, but this method has the advantage of reusing existing tools, and it's able to handle updates from arbitrarily old existing installations. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
Ken Smith, 2011-02-24 22:26 (+0100): Just a quick note for those of you who are not subscribed to the freebsd-announce mail list... 8.2-RELEASE and 7.4-RELEASE have been announced. The announcement messages are available here: http://www.freebsd.org/releases/8.2R/announce.html http://www.freebsd.org/releases/7.4R/announce.html Enjoy. :-) Great news. However, a freebsd-update from a straight binary installed 8.1-RELEASE gives me a dialogue to merge a lot of files in /etc/ with just the $Id$ tag being different. That is, I get: The following changes, which occurred between FreeBSD 8.1-RELEASE and FreeBSD 8.2-RELEASE have been merged into /etc/manpath.config: --- current version +++ new version @@ -1,6 +1,6 @@ -# $FreeBSD: src/gnu/usr.bin/man/manpath/manpath.config,v 1.26.2.1.4.1 2010/06/14 02:09:06 kensmith Exp $ +# $FreeBSD: src/gnu/usr.bin/man/manpath/manpath.config,v 1.26.2.1.6.1 2010/12/21 17:09:25 kensmith Exp $ # # This file is read by manpath(1) to configure the mandatory manpath, # optional manpath and to map each path element to a manpath element. # The format is: # Does this look reasonable (y/n)? I'm afraid this will go on for all files in /etc. What just happened? How can I avoid it? I had this problem before and then in my frustration just commented out this line in freebsd-update.conf: #MergeChanges /etc/ /var/named/etc/ /boot/device.hints I got lucky that time, but is this really safe? What if, say, a new daemon has been installed in the upgrade and needs a new user. Any suggestions? -- http://hack.org/mc/ Use plain text e-mail, please. OpenPGP welcome, 0xE4C92FA5. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
On Fri, Feb 25, 2011 at 11:56:46AM +0100, Michael Cardell Widerkrantz wrote: Ken Smith, 2011-02-24 22:26 (+0100): Just a quick note for those of you who are not subscribed to the freebsd-announce mail list... 8.2-RELEASE and 7.4-RELEASE have been announced. The announcement messages are available here: http://www.freebsd.org/releases/8.2R/announce.html http://www.freebsd.org/releases/7.4R/announce.html Enjoy. :-) Great news. However, a freebsd-update from a straight binary installed 8.1-RELEASE gives me a dialogue to merge a lot of files in /etc/ with just the $Id$ tag being different. That is, I get: The following changes, which occurred between FreeBSD 8.1-RELEASE and FreeBSD 8.2-RELEASE have been merged into /etc/manpath.config: --- current version +++ new version @@ -1,6 +1,6 @@ -# $FreeBSD: src/gnu/usr.bin/man/manpath/manpath.config,v 1.26.2.1.4.1 2010/06/14 02:09:06 kensmith Exp $ +# $FreeBSD: src/gnu/usr.bin/man/manpath/manpath.config,v 1.26.2.1.6.1 2010/12/21 17:09:25 kensmith Exp $ # # This file is read by manpath(1) to configure the mandatory manpath, # optional manpath and to map each path element to a manpath element. # The format is: # Does this look reasonable (y/n)? I'm afraid this will go on for all files in /etc. What just happened? How can I avoid it? I had this problem before and then in my frustration just commented out this line in freebsd-update.conf: #MergeChanges /etc/ /var/named/etc/ /boot/device.hints I got lucky that time, but is this really safe? What if, say, a new daemon has been installed in the upgrade and needs a new user. Any suggestions? Read up on the mergemaster manual for options -F and -i :-) Marco -- Micro$oft likes to discard vulnerabilities by `no standard client would do this.' No, and no `standard visitor' would apply a crowbar to your patio door, either. - H. Peter Anvin in linux-kernel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
[snip] I had this problem before and then in my frustration just commented out this line in freebsd-update.conf: #MergeChanges /etc/ /var/named/etc/ /boot/device.hints I got lucky that time, but is this really safe? What if, say, a new daemon has been installed in the upgrade and needs a new user. Any suggestions? Read up on the mergemaster manual for options -F and -i :-) perhaps you mean -Ui ? problem is, he might have no src tree when using freebsd-update, so mergemaster is a no-go :( Marco Buki pgpbAqMAPsaty.pgp Description: PGP signature
Re: 8.2/7.4-RELEASEs Announced...
On Fri, Feb 25, 2011 at 02:47:44PM +0100, Marek 'Buki' Kozlovský wrote: [snip] I had this problem before and then in my frustration just commented out this line in freebsd-update.conf: #MergeChanges /etc/ /var/named/etc/ /boot/device.hints I got lucky that time, but is this really safe? What if, say, a new daemon has been installed in the upgrade and needs a new user. Any suggestions? Read up on the mergemaster manual for options -F and -i :-) perhaps you mean -Ui ? problem is, he might have no src tree when using freebsd-update, so mergemaster is a no-go :( My apologies. I went ahead to fast and replied with source-upgrade in mind. Sorry, -- Marco van Tol pgp2ZaT44x7jD.pgp Description: PGP signature
Re: 8.2/7.4-RELEASEs Announced...
On Fri, Feb 25, 2011 at 02:42:25PM +0100, Marco van Tol wrote: Read up on the mergemaster manual for options -F and -i :-) freebsd-update does not use mergemaster, though probably it should. We had this discussion a month or two ago. Currently there is no way around verifying the changes for each file with a changed $ID$ field, frustrating as it is. (Also, if you realize you've made a mistake and say N at the end when it asks if all the merges are OK, it kicks you out of the update process instead of going through the merges again.) -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
On Fri, Feb 25, 2011 at 02:42:25PM +0100, Marco van Tol wrote: Read up on the mergemaster manual for options -F and -i :-) freebsd-update does not use mergemaster, though probably it should. My understanding is that freebsd-update was introduced prior to releases being branched, so this issue surfaced at that time. The patch I believe would be a fix to the freebsd-update client to better handle the tag. I can't see mergemaster as being an easier solution, as the actual binary would need to be verified against a known good index that would exist on the update server. But then, again, I may be wrong. We had this discussion a month or two ago. Do you have a link to this thread? Currently there is no way around verifying the changes for each file with a changed $ID$ field, frustrating as it is. (Also, if you realize you've made a mistake and say N at the end when it asks if all the merges are OK, it kicks you out of the update process instead of going through the merges again.) -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
On Fri, Feb 25, 2011 at 10:00:19AM -0800, jhelf...@e-e.com wrote: On Fri, Feb 25, 2011 at 02:42:25PM +0100, Marco van Tol wrote: Read up on the mergemaster manual for options -F and -i :-) freebsd-update does not use mergemaster, though probably it should. My understanding is that freebsd-update was introduced prior to releases being branched, so this issue surfaced at that time. The patch I believe would be a fix to the freebsd-update client to better handle the tag. I can't see mergemaster as being an easier solution, as the actual binary would need to be verified against a known good index that would exist on the update server. But then, again, I may be wrong. You may well be right; I haven't investigated how the two calculate the differences. We had this discussion a month or two ago. Do you have a link to this thread? Thread title is: Accidentally aborted upgrade via freebsd-update - how to recover? Relevant discussion starts here, on Dec 27 2010: http://lists.freebsd.org/pipermail/freebsd-stable/2010-December/060763.html -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
On Friday, February 25, 2011 1:00:19 pm jhelf...@e-e.com wrote: On Fri, Feb 25, 2011 at 02:42:25PM +0100, Marco van Tol wrote: Read up on the mergemaster manual for options -F and -i :-) freebsd-update does not use mergemaster, though probably it should. My understanding is that freebsd-update was introduced prior to releases being branched, so this issue surfaced at that time. The patch I believe would be a fix to the freebsd-update client to better handle the tag. I can't see mergemaster as being an easier solution, as the actual binary would need to be verified against a known good index that would exist on the update server. No, release branches long pre-date freebsd-update. However, before we switched to svn for source, new branches did not bump all the $FreeBSD$ tags. That is a side effect of the way that the SVN - CVS exporter works (and arguably a bug). BTW, I did design etcupdate to support this sort of use case (you can build a tarball from a given release tree and use that as the basis for comparisons assuming you were bootstrapped to use etcupdate). Currently freebsd-update doesn't use etcupdate and the author doesn't have any interest in changing it to do so. At some point if I have some time to hack on freebsd-update to be more useful for modified versions of FreeBSD (e.g. building snaps from tags in an SVN repository instead of a directory of patches against a CVS checkout), I will probably hack it to support using etcupdate to manage /etc updates as well. (etcupdate uses something akin to 'svn up' to update files in /etc, so things like $FreeBSD$ changes just auto-update assuming they don't result in merge conficts.) -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.2/7.4-RELEASEs Announced...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just a quick note for those of you who are not subscribed to the freebsd-announce mail list... 8.2-RELEASE and 7.4-RELEASE have been announced. The announcement messages are available here: http://www.freebsd.org/releases/8.2R/announce.html http://www.freebsd.org/releases/7.4R/announce.html Enjoy. :-) - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1mzP8ACgkQ/G14VSmup/ZnuQCfc2N5EcvKele/VmpqkhzoWZwR 1oIAniNIyI2Zy+eVTJ3q4joEd7wHGZD6 =mc7p -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2/7.4-RELEASEs Announced...
Quoth Ken Smith on Thursday, 24 February 2011: Just a quick note for those of you who are not subscribed to the freebsd-announce mail list... 8.2-RELEASE and 7.4-RELEASE have been announced. The announcement messages are available here: http://www.freebsd.org/releases/8.2R/announce.html http://www.freebsd.org/releases/7.4R/announce.html Enjoy. :-) Congratulations to the team! -- Sterling (Chip) Camden | sterl...@camdensoftware.com | 2048D/3A978E4F http://chipsquips.com | http://camdensoftware.com | http://chipstips.com pgpCuAWU1Va3z.pgp Description: PGP signature
