Re: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012, Ken Smith wrote: Hi, let me reply to the very initial email in this monster of public thread. With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. RELENG_9_1 is now exported the CVS as well and will be for as long as things will be exported to CVS. It will take another few hours to get near your local mirror as they'll all be chewing on each other the next 12 hours. Enjoy! Any further discussions on src export I'll leave to other people wearing hats. /bz -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. ___ 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: FreeBSD 9.1-RC1 Available...
Yes, freebsd-update is the way to go... I got it done on my home/test server. back in the office where I have one machine on it thou. # uname -a FreeBSD rhino.matrix 9.1-BETA1 FreeBSD 9.1-BETA1 #0 r239929M: Fri Aug 31 12:42:47 EST 2012 root@rhino.matrix:/usr/obj/usr/src/sys/GENERIC amd64 # freebsd-update -v debug -r 9.1-RC1 upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update5.FreeBSD.org... fetch: http://update5.FreeBSD.org/9.1-BETA1/amd64/pub.ssl: Not Found failed. Fetching public key from update4.FreeBSD.org... fetch: http://update4.FreeBSD.org/9.1-BETA1/amd64/pub.ssl: Not Found failed. Fetching public key from update3.FreeBSD.org... fetch: http://update3.FreeBSD.org/9.1-BETA1/amd64/pub.ssl: Not Found failed. No mirrors remaining, giving up. browse to: http://update5.FreeBSD.org/ Someone has removed the whole 9.1-BETA1 directory/folder/branch making it impossible for anyone from beta1 to upgrade to rc1 using freebsd-update even thou I got one server upgraded. Can we get that restored? If not what is the CVS tag or as I noted what are the SVN details for rc1? Thanks On 24/08/12 03:37, Walter Hurry wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: The first release candidate of the 9.1-RELEASE release cycle is now available on the FTP servers for amd64, i386, and powerpc64. The MD5/SHA256 checksums are at the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ (or any of the FreeBSD mirror sites). snip I have just upgraded (an x86_64 VM) from 9.0-RELEASE to 9.1-RC1, using freebsd-update. Very smooth, and no apparent hitches at all. Thanks to all concerned, and well done. One thing (welcome, but puzzling) which surprised me was that my vboxguest.ko did *not* need to be recompiled. How did the upgrade manage that? ___ 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 -- Jurgen Weber Systems Engineer IT Infrastructure Team Leader THE ICONIC | E jurgen.we...@theiconic.com.au | www.theiconic.com.au ___ 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: FreeBSD 9.1-RC1 Available...
Jim Pingle schreef op : On 8/23/2012 11:43 AM, Ian Lepore wrote: On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote: I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. It may be difficult to run an svn mirror that allows you to commit locally and get those changes back to the project, but running a read-only mirror is trivial. The script I run nightly from cron to sync my local mirror is: #!/bin/sh # # svnsync to pull in changes from FreeBSD to my local mirror. # svnsync sync file:///local/vc/svn/base I can't remember how I initially created and populated the mirror, but it's likely I grabbed a snapshot of the mirror at work and brought it home on a thumb drive (just to avoid initial network DL time). I spent a little time today setting up an SVN mirror after reading this thread and wrote up a how-to for those looking to do the same. http://www.pingle.org/2012/08/24/freebsd-svn-mirror Comments/Flames/Corrections welcome... Just wondering: do you really need DAV if you are not going to allow writing? I serve my read-only GIT repositories using HTTP without WebDAV. ___ 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: FreeBSD 9.1-RC1 Available...
On 8/30/2012 9:53 AM, Stas Verberkt wrote: I spent a little time today setting up an SVN mirror after reading this thread and wrote up a how-to for those looking to do the same. http://www.pingle.org/2012/08/24/freebsd-svn-mirror Comments/Flames/Corrections welcome... Just wondering: do you really need DAV if you are not going to allow writing? I serve my read-only GIT repositories using HTTP without WebDAV. I'm not 100% sure on that part - previously I had setup a read+write SVN repo over HTTPS (at $oldjob) so I went with the directions I had for that, just adjusted for read-only. Some Googling suggests that DAV is required. The official Subversion book lists DAV as a requirement[1]. Wikipedia seems to suggest it's required as well Apache HTTP Server as network server, WebDAV/Delta-V for protocol. There is also an independent server process called svnserve that uses a custom protocol over TCP/IP. If someone knows a trick to serve it up over HTTP without DAV that would be good to know. Jim P.S. Realized I sent this directly, resending to the list, with an edit. [1] http://svnbook.red-bean.com/en/1.7/svn.serverconfig.httpd.html ___ 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: FreeBSD 9.1-RC1 Available...
Jim Pingle li...@pingle.org writes: On 8/23/2012 11:43 AM, Ian Lepore wrote: On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote: I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. It may be difficult to run an svn mirror that allows you to commit locally and get those changes back to the project, but running a read-only mirror is trivial. The script I run nightly from cron to sync my local mirror is: #!/bin/sh # # svnsync to pull in changes from FreeBSD to my local mirror. # svnsync sync file:///local/vc/svn/base I can't remember how I initially created and populated the mirror, but it's likely I grabbed a snapshot of the mirror at work and brought it home on a thumb drive (just to avoid initial network DL time). I spent a little time today setting up an SVN mirror after reading this thread and wrote up a how-to for those looking to do the same. http://www.pingle.org/2012/08/24/freebsd-svn-mirror Comments/Flames/Corrections welcome... thanx; works out of the box for me (using the svnserve_enable path). That said : I glanced at a diff of a stable/8 checkout both from /home/ncvs repo and new /home/freebsd-svn one, and saw a (maybe well-known ..) 'feature' : diff ./src/contrib/amd/include/am_defs.h /raid1/bsd/8/src/contrib/amd/include/am_defs.h 42c42 * $FreeBSD: stable/8/contrib/amd/include/am_defs.h 174299 2007-12-05 16:03:52Z obrien $ --- * $FreeBSD: src/contrib/amd/include/am_defs.h,v 1.15.2.1 2009/08/03 08:13:06 kensmith Exp $ I wondered why the date (and commiter ...) in the expansion were different (from the svn log ): r196045 | kensmith | 2009-08-03 10:13:06 +0200 (Mon, 03 Aug 2009) | 4 lines Copy head to stable/8 as part of 8.0 Release cycle. Approved by:re (Implicit) r174299 | obrien | 2007-12-05 17:03:52 +0100 (Wed, 05 Dec 2007) | 3 lines So the 'Copy head' chain does not update the $FreeBSD tag, whereas the consequent svn to cvs chain does. FYI, Arno Jim ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, Aug 23, 2012 at 6:50 AM, Ken Smith kensm...@buffalo.edu wrote: The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 9.0-RELEASE can upgrade as follows: # freebsd-update upgrade -r 9.1-RC1 This has not been working for me on i386 for the last few days. It fails with: [root@mist /usr/home/andrnils]# freebsd-update upgrade -r 9.1-RC1 Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update4.FreeBSD.org... failed. Fetching public key from update5.FreeBSD.org... failed. Fetching public key from update3.FreeBSD.org... failed. No mirrors remaining, giving up. Best regards Andreas ... -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | ___ 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: FreeBSD 9.1-RC1 Available...
On 28/08/2012, Arno J. Klaassen a...@heho.snv.jussieu.fr wrote: Jim Pingle li...@pingle.org writes: On 8/23/2012 11:43 AM, Ian Lepore wrote: On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote: I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. It may be difficult to run an svn mirror that allows you to commit locally and get those changes back to the project, but running a read-only mirror is trivial. The script I run nightly from cron to sync my local mirror is: #!/bin/sh # # svnsync to pull in changes from FreeBSD to my local mirror. # svnsync sync file:///local/vc/svn/base I can't remember how I initially created and populated the mirror, but it's likely I grabbed a snapshot of the mirror at work and brought it home on a thumb drive (just to avoid initial network DL time). I spent a little time today setting up an SVN mirror after reading this thread and wrote up a how-to for those looking to do the same. http://www.pingle.org/2012/08/24/freebsd-svn-mirror Comments/Flames/Corrections welcome... thanx; works out of the box for me (using the svnserve_enable path). That said : I glanced at a diff of a stable/8 checkout both from /home/ncvs repo and new /home/freebsd-svn one, and saw a (maybe well-known ..) 'feature' : diff ./src/contrib/amd/include/am_defs.h /raid1/bsd/8/src/contrib/amd/include/am_defs.h 42c42 * $FreeBSD: stable/8/contrib/amd/include/am_defs.h 174299 2007-12-05 16:03:52Z obrien $ --- * $FreeBSD: src/contrib/amd/include/am_defs.h,v 1.15.2.1 2009/08/03 08:13:06 kensmith Exp $ I wondered why the date (and commiter ...) in the expansion were different (from the svn log ): r196045 | kensmith | 2009-08-03 10:13:06 +0200 (Mon, 03 Aug 2009) | 4 lines Copy head to stable/8 as part of 8.0 Release cycle. Approved by:re (Implicit) r174299 | obrien | 2007-12-05 17:03:52 +0100 (Wed, 05 Dec 2007) | 3 lines So the 'Copy head' chain does not update the $FreeBSD tag, whereas the consequent svn to cvs chain does. That's because CVS does not consider tagging/branching a commit, whereas Subversion does. Chris ___ 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: FreeBSD 9.1-RC1 Available...
On 8/25/2012 4:33 AM, Harald Schmalzbauer wrote: But my real problem is that svn is not in the base system. And for example installing subversion package on my cvsup mirror failed because pkg-config-0-25_1 was installed and sqlite, a dependency of subversion, wants to install pkgconf-0.8.5. So I'm hit by the henn-egg problem. This is because pkg-config was removed and moved from devel/pkg-config to devel/pkgconf. To update or install any port, you'll need to deinstall pkg-config and install pkgconf. There is an associated UPDATING entry: 20120726: AFFECTS: users of devel/pkg-config AUTHOR: b...@freebsd.org devel/pkg-config has been replaced by devel/pkgconf # portmaster -o devel/pkgconf devel/pkg-config or # portupgrade -fo devel/pkgconf pkg-config-\* pkgng: # pkg set -o devel/pkg-config:devel/pkgconf # pkg install -f devel/pkgconf Bryan ___ 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: FreeBSD 9.1-RC1 Available...
[ Jim Pingle wrote on Fri 24.Aug'12 at 23:07:30 -0400 ] On 8/23/2012 11:43 AM, Ian Lepore wrote: On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote: I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. It may be difficult to run an svn mirror that allows you to commit locally and get those changes back to the project, but running a read-only mirror is trivial. The script I run nightly from cron to sync my local mirror is: #!/bin/sh # # svnsync to pull in changes from FreeBSD to my local mirror. # svnsync sync file:///local/vc/svn/base I can't remember how I initially created and populated the mirror, but it's likely I grabbed a snapshot of the mirror at work and brought it home on a thumb drive (just to avoid initial network DL time). I spent a little time today setting up an SVN mirror after reading this thread and wrote up a how-to for those looking to do the same. http://www.pingle.org/2012/08/24/freebsd-svn-mirror Comments/Flames/Corrections welcome... That's cool Jim. Certainly provides a clear explanation and simple steps. ___ 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: FreeBSD 9.1-RC1 Available...
schrieb Peter Wemm am 24.08.2012 00:14 (localtime): ... You'll also find out very quickly how much fsync(2) hurts on a softdep or su+j system. The svn fsfs backend does a fsync multiple times per revision to guarantee its transaction boundaries. Not only on softdep ufs, also with zfs I'm seeing big performance regressions (checkout ports from one zfs holding svnsynced repo to another on the same pool takes hours with svn, while completed in less than half an hour with csup) But my real problem is that svn is not in the base system. And for example installing subversion package on my cvsup mirror failed because pkg-config-0-25_1 was installed and sqlite, a dependency of subversion, wants to install pkgconf-0.8.5. So I'm hit by the henn-egg problem. I hope I can build subversion (sqlite) with pkg-config-0 dependency, but right now I still have to wait for this awful slow svn checkout (svn co file:///svn/repos/mirror/ports/head /usr/ports/) Can someone share any sensible tuning for svn and zfs? Is it possible to build any svn compatible (checkout-only-capable) binary without that much dependencies? If so, I hope this will be in the base very soon. Thanks, -Harry signature.asc Description: OpenPGP digital signature
Re: FreeBSD 9.1-RC1 Available...
[Removing re@] On 25 Aug 2012, at 10:33, Harald Schmalzbauer h.schmalzba...@omnilan.de wrote: schrieb Peter Wemm am 24.08.2012 00:14 (localtime): ... You'll also find out very quickly how much fsync(2) hurts on a softdep or su+j system. The svn fsfs backend does a fsync multiple times per revision to guarantee its transaction boundaries. Not only on softdep ufs, also with zfs I'm seeing big performance regressions (checkout ports from one zfs holding svnsynced repo to another on the same pool takes hours with svn, while completed in less than half an hour with csup) But my real problem is that svn is not in the base system. And for example installing subversion package on my cvsup mirror failed because pkg-config-0-25_1 was installed and sqlite, a dependency of subversion, wants to install pkgconf-0.8.5. So I'm hit by the henn-egg problem. I hope I can build subversion (sqlite) with pkg-config-0 dependency, but right now I still have to wait for this awful slow svn checkout (svn co file:///svn/repos/mirror/ports/head /usr/ports/) Can someone share any sensible tuning for svn and zfs? Is it possible to build any svn compatible (checkout-only-capable) binary without that much dependencies? If so, I hope this will be in the base very soon. If you are going to do checkouts from svn:// only you can disable Neon which should reduce the dependency chain some. I haven't found svn checkouts to be too slow most of the time, but of course I'm generally using systems with hardware RAID controller which likely helps some. PS. I don't think you should expect svn in base - it has too many dependencies, options, and is too fast moving to sanely be in the base system. -- Simon L. B. Nielsen ___ 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: FreeBSD 9.1-RC1 Available...
On Fri, Aug 24, 2012 at 10:19:36PM -0700, Dennis Glatting wrote: ... There are two things that I am confused about base. 1) What, exactly, is base? When I do a co, what tree branch is that? Using CVS, failure to specify a tag would get you HEAD. Using SVN, failure to specify a branch will get you head. This may help. As noted previously, I have a local private mirror of the FreeBSD SVN src repository located in /svn/freebsd/src/base; so: g1-227(9.1-P)[1] svn ls file:///svn/freebsd/src/base ROADMAP.txt cvs2svn/ head/ projects/ release/ releng/ stable/ svnadmin/ user/ vendor/ vendor-crypto/ vendor-sys/ g1-227(9.1-P)[2] svn ls file:///svn/freebsd/src/base/releng 2.0.5/ 4.10/ 4.11/ 4.3/ 4.4/ 4.5/ 4.6/ 4.7/ 4.8/ 4.9/ 5.0/ 5.1/ 5.2/ 5.3/ 5.4/ 5.5/ 6.0/ 6.1/ 6.2/ 6.3/ 6.4/ 7.0/ 7.1/ 7.2/ 7.3/ 7.4/ 8.0/ 8.1/ 8.2/ 8.3/ 9.0/ 9.1/ ALPHA_2_0/ BETA_2_0/ g1-227(9.1-P)[3] svn ls file:///svn/freebsd/src/base/stable 2.0.5/ 2.1/ 2.2/ 3/ 4/ 5/ 6/ 7/ 8/ 9/ g1-227(9.1-P)[4] svn ls file:///svn/freebsd/src/base/head COPYRIGHT LOCKS MAINTAINERS Makefile Makefile.inc1 ObsoleteFiles.inc README UPDATING bin/ cddl/ contrib/ crypto/ etc/ games/ gnu/ include/ kerberos5/ lib/ libexec/ release/ rescue/ sbin/ secure/ share/ sys/ tools/ usr.bin/ usr.sbin/ g1-227(9.1-P)[5] Does that help? 2) Base /appears/ not to contain releng/9.1 or stable/8. How do I mirror those? As shown above, they are there. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpso5GP1dxdt.pgp Description: PGP signature
Re: FreeBSD 9.1-RC1 Available...
On Saturday, August 25, 2012, Glen Barber wrote: On Sat, Aug 25, 2012 at 04:55:48AM +0100, Ben Morrow wrote: Quoth Ken Smith kensm...@buffalo.edu javascript:;: The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. Two questions: 1. Is is sensible|supported to use freebsd-update to update just the src component, followed by a normal buildworld/buildkernel to update the rest of the system? I would much prefer to avoid having to use svn, especially given that it isn't in the base system. No. freebsd-update(8) is a binary system updater. It does not touch your source tree. Glen Hi Glen, Freebsd-update tool installs binary updates for -RELEASE branch only (base system + GENERIC kernel). By default, /usr/src is synced. So you can upgrade your system and GENERIC kernel, then rebuild manually your custom kernel if you got one. This is described in the Handbook at the page FreeBSD update. You do not have to SVN or CSUP your /usr/src sources tree after used freebsd-update tool. Regards, Alexandre ___ 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: FreeBSD 9.1-RC1 Available...
On Sat, 2012-08-25 at 04:42 -0700, David Wolfskill wrote: On Fri, Aug 24, 2012 at 10:19:36PM -0700, Dennis Glatting wrote: ... There are two things that I am confused about base. 1) What, exactly, is base? When I do a co, what tree branch is that? Using CVS, failure to specify a tag would get you HEAD. Using SVN, failure to specify a branch will get you head. This may help. As noted previously, I have a local private mirror of the FreeBSD SVN src repository located in /svn/freebsd/src/base; so: g1-227(9.1-P)[1] svn ls file:///svn/freebsd/src/base ROADMAP.txt cvs2svn/ head/ projects/ release/ releng/ stable/ svnadmin/ user/ vendor/ vendor-crypto/ vendor-sys/ g1-227(9.1-P)[2] svn ls file:///svn/freebsd/src/base/releng 2.0.5/ 4.10/ 4.11/ 4.3/ 4.4/ 4.5/ 4.6/ 4.7/ 4.8/ 4.9/ 5.0/ 5.1/ 5.2/ 5.3/ 5.4/ 5.5/ 6.0/ 6.1/ 6.2/ 6.3/ 6.4/ 7.0/ 7.1/ 7.2/ 7.3/ 7.4/ 8.0/ 8.1/ 8.2/ 8.3/ 9.0/ 9.1/ ALPHA_2_0/ BETA_2_0/ g1-227(9.1-P)[3] svn ls file:///svn/freebsd/src/base/stable 2.0.5/ 2.1/ 2.2/ 3/ 4/ 5/ 6/ 7/ 8/ 9/ g1-227(9.1-P)[4] svn ls file:///svn/freebsd/src/base/head COPYRIGHT LOCKS MAINTAINERS Makefile Makefile.inc1 ObsoleteFiles.inc README UPDATING bin/ cddl/ contrib/ crypto/ etc/ games/ gnu/ include/ kerberos5/ lib/ libexec/ release/ rescue/ sbin/ secure/ share/ sys/ tools/ usr.bin/ usr.sbin/ g1-227(9.1-P)[5] Does that help? 2) Base /appears/ not to contain releng/9.1 or stable/8. How do I mirror those? As shown above, they are there. Thanks for the clue. Peace, david ___ 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: FreeBSD 9.1-RC1 Available...
On Sat, Aug 25, 2012 at 04:04:07PM +0200, Alexandre wrote: No. freebsd-update(8) is a binary system updater. It does not touch your source tree. Freebsd-update tool installs binary updates for -RELEASE branch only (base system + GENERIC kernel). By default, /usr/src is synced. So you can upgrade your system and GENERIC kernel, then rebuild manually your custom kernel if you got one. This is described in the Handbook at the page FreeBSD update. You do not have to SVN or CSUP your /usr/src sources tree after used freebsd-update tool. You're right, my mistake. I meant to remove that last sentence after realizing this. Sorry for the confusion. Glen pgpQHzHIOKP3w.pgp Description: PGP signature
Re: FreeBSD 9.1-RC1 Available...
On 23 Aug 2012, at 22:52, Simon L. B. Nielsen si...@freebsd.org wrote:
On 23 Aug 2012, at 20:41, Peter Wemm pe...@wemm.org wrote:
On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote:
With both the doc and ports repositories now moved to SVN it has been
decided to not export the 9.1 release branch activity to CVS. So
csup/cvsup update mechanisms are not available for updating to 9.1-RC1.
If you would like to use SVN the branch to use is releng/9.1.
* RIght now you can mirror
svn://svn.freebsd.org/base/{stable/9,release/9.1*,etc} to your laptop,
and Simon is setting up a US-east coast and US-west coast mirror. You
can easily switch your mirrors on the fly if there's a closer/faster
one.
Real world got in the way, but they should be ready by Friday or Saturday,
and will be documented in the Handbook.
Mirrors are now running and documented:
http://www.freebsd.org/doc/en/books/handbook/mirrors-svn.html
I'm still doing some final tweaks so there might be some shorter outages over
the weekend, but it should be 1m issues.
PS. also, if anyone are access http://svn.FreeBSD.org/ you are in fact now
using svn0.us-west.FreeBSD.org, to avoid having to run apache on the main svn
server, so - you might as well use the mirror directly and avoid going through
netcat...
--
Simon L. B. Nielsen
Hat: FreeBSD.org admins team
___
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: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012 09:01:06 -0700 (PDT)
Dennis Glatting d...@pki2.com wrote:
On Thu, 23 Aug 2012, Trond Endrest?l wrote:
On Thu, 23 Aug 2012 07:25-0700, Dennis Glatting wrote:
On Thu, 2012-08-23 at 09:47 -0400, Ken Smith wrote:
On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote:
On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote:
With both the doc and ports repositories now moved to SVN it
has been decided to not export the 9.1 release branch activity
to CVS. So csup/cvsup update mechanisms are not available for
updating to 9.1-RC1. If you would like to use SVN the branch
to use is releng/9.1.
Assuming the stupid question is the one you didn't ask, just to
clarify: does this mean that c*sup won't work with these RCs in
particular, or that CVS is dead and SVN becomes mandatory from
9.1-RELEASE?
cheers, Ian
The latter. If you are not using FreeBSD-Update to handle the
updates of a machine you'll need to update your source tree using
SVN for release branches (releng/*) from now on. Updates of the
CVS repository will continue for the existing stable/* and head
for now. I don't think anything has been decided on when that
will stop.
Looking in the handbook ([1]) I do not see the mechanics of how to
set up a mirror, of which I have three CVS mirrors in different
infrastructures. Is there a web page somewhere on how to set up,
synchronize, maintain, and use a local mirror?
[1]
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html
How about this one?
http://motoyuki.bsdclub.org/BSD/cvsup.html
I have CVS mirrors. The topic is SVN.
for src:
1. fetch tar.xz from
${mirror}/pub/FreeBSD/development/subversion/svnmirror-base-r238500.tar.xz
2. tar xf svnmirror-base-r238500.tar.xz
3.svnsync sync
file:///path/to/local/repo/base/
___
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
--
wbr, tiger
___
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: FreeBSD 9.1-RC1 Available...
On Thu, Aug 23, 2012 at 12:41:03PM -0700, Peter Wemm wrote: * We have some seed tarballs of recently synced repo images around somewhere. I'll see where they're available. But in a nutshell, you do this: /home/peter/svnsync$ fetch svnmirror-base-r123456.txz /home/peter/svnsync$ tar xf svnmirror-base-r123456.txz /home/peter/svnsync$ svnsync file:///home/peter/svnsync/base and run that from cron with a lock file, probably with -q for quiet. Then you can have a local copy of the repo for offline use. It has the same repo uuid so you can svn switch/relocate at will. I personally on my laptop. Why do you recommend lock file ? svnsync locks the repository on its own, AFAIR. More, the lock is quite sticky, so died svnsync usualy require manual intervention to allow other syncsync jobs to process. Is there something I am not aware of that requires lock file ? pgp54X45vIr4I.pgp Description: PGP signature
Re: FreeBSD 9.1-RC1 Available...
On Fri, 24 Aug 2012 00:18:09 -0500, Konstantin Belousov kostik...@gmail.com wrote: This is a statement that is false at least two times, if not three. This was a question about Kernel Binary Inteface, not Application Binary Interface. I actually did mean to say KBI instead of ABI :-/ First, we have zero guarantees about ability to load or have a system survive loading of the module compiled against the later kernel. Second, we do not have real KBI definition, and KBI stability is managed only ad-hock. E.g. VFS quite often breaks, while network or disk controllers drivers are usually fine. I'll have to search my email but I had a conversation with someone whom I trusted (I believe within the FBSD project) that either mislead me or I misread what they were saying. Either way, thank you for the clarification. YMMV. Snobby false statements hurt the project. There was nothing snobby about it; I was merely using Linux as a point of reference since most *nix users should have experience with Linux rejecting kernel modules that weren't compiled against that exact kernel. I could very well have said Plan9 instead but it would be meaningless because nobody actually runs Plan9. :-) Thanks again Konstantin :-) ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, Aug 23, 2012 at 8:06 PM, Thomas Mueller muelle...@insightbb.com wrote: Excerpt from announcement by Ken Smith kensm...@buffalo.edu: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. I read your message and followup messages and have questions about how to switch from csup to svn. System source is in /usr/src obtained by csup, apparently now being deprecated. Do I need to delete (rm -R /usr/src/*) before running svn co svn://svn.freebsd.org/base/stable/9 /usr/src As a data point.. if you're talking about stable/9, then that is still available via cvs/csup/cvsup as RELENG_9. If you track 9-stable, you're unaffected. But there will never be a RELENG_10* anything in cvs. -- Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV All of this is for nothing if we don't go to the stars - JMS/B5 If Java had true garbage collection, most programs would delete themselves upon execution. -- Robert Sewell ___ 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: FreeBSD 9.1-RC1 Available...
On Fri, Aug 24, 2012 at 11:34 AM, Peter Wemm pe...@wemm.org wrote: On Thu, Aug 23, 2012 at 8:06 PM, Thomas Mueller muelle...@insightbb.com wrote: Excerpt from announcement by Ken Smith kensm...@buffalo.edu: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. I read your message and followup messages and have questions about how to switch from csup to svn. System source is in /usr/src obtained by csup, apparently now being deprecated. Do I need to delete (rm -R /usr/src/*) before running svn co svn://svn.freebsd.org/base/stable/9 /usr/src As a data point.. if you're talking about stable/9, then that is still available via cvs/csup/cvsup as RELENG_9. If you track 9-stable, you're unaffected. I got two private emails about this. To be clear, yes, if you're tracking RELENG_9, you will get 9.1-STABLE, and future 9.2 things just like before. All that is missing is the release management branch. But there will never be a RELENG_10* anything in cvs. -- Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV All of this is for nothing if we don't go to the stars - JMS/B5 If Java had true garbage collection, most programs would delete themselves upon execution. -- Robert Sewell -- Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV All of this is for nothing if we don't go to the stars - JMS/B5 If Java had true garbage collection, most programs would delete themselves upon execution. -- Robert Sewell ___ 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: FreeBSD 9.1-RC1 Available...
On 8/23/2012 11:06 PM, Thomas Mueller wrote: Excerpt from announcement by Ken Smith kensm...@buffalo.edu: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. I read your message and followup messages and have questions about how to switch from csup to svn. System source is in /usr/src obtained by csup, apparently now being deprecated. Do I need to delete (rm -R /usr/src/*) before running svn co svn://svn.freebsd.org/base/stable/9 /usr/src I don't want an out-of-sync mess resulting from mixing two versions, assume that wouldn't work well. I guess I need to switch the doc (/usr/doc) also to svn. What about the ports? Would I need to switch the ports tree from portsnap fetch update, or is portsnap still the proper way? Tom As I see no answered your real question. But I agree with them: yes you can still use csup or cvsup for releng_9 (stable 9). But as to your question, if you are switching to svn to try it out: In my experience I had to remove (rm -rf /usr/src) /usr/src or the old files remained. The checkout process did not update the existing files. But maybe I did something wrong. Tools other than cvs and cvsup are unaffected. You can still use portsnap or make fetch in /usr/ports etc. Ken ___ 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: FreeBSD 9.1-RC1 Available...
On 8/23/2012 11:43 AM, Ian Lepore wrote: On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote: I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. It may be difficult to run an svn mirror that allows you to commit locally and get those changes back to the project, but running a read-only mirror is trivial. The script I run nightly from cron to sync my local mirror is: #!/bin/sh # # svnsync to pull in changes from FreeBSD to my local mirror. # svnsync sync file:///local/vc/svn/base I can't remember how I initially created and populated the mirror, but it's likely I grabbed a snapshot of the mirror at work and brought it home on a thumb drive (just to avoid initial network DL time). I spent a little time today setting up an SVN mirror after reading this thread and wrote up a how-to for those looking to do the same. http://www.pingle.org/2012/08/24/freebsd-svn-mirror Comments/Flames/Corrections welcome... Jim ___ 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: FreeBSD 9.1-RC1 Available...
Quoth Ken Smith kensm...@buffalo.edu: The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. Two questions: 1. Is is sensible|supported to use freebsd-update to update just the src component, followed by a normal buildworld/buildkernel to update the rest of the system? I would much prefer to avoid having to use svn, especially given that it isn't in the base system. 2. If I have patched my source tree, what will freebsd-update do? csup resets the patched files to the versions in the new tree, which is satisfactory (I can reapply any patches afterwards, adjusting them if necessary), but if freebsd-update leaves a mixture of new-and-unpatched and old-and-patched files in the tree that could be a problem. (Not an insoluble problem, of course, especially with ZFS snapshots.) Ben ___ 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: FreeBSD 9.1-RC1 Available...
On Sat, Aug 25, 2012 at 04:55:48AM +0100, Ben Morrow wrote: Quoth Ken Smith kensm...@buffalo.edu: The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. Two questions: 1. Is is sensible|supported to use freebsd-update to update just the src component, followed by a normal buildworld/buildkernel to update the rest of the system? I would much prefer to avoid having to use svn, especially given that it isn't in the base system. No. freebsd-update(8) is a binary system updater. It does not touch your source tree. Glen pgpZLNLT1eFGX.pgp Description: PGP signature
Re: FreeBSD 9.1-RC1 Available...
In article 20120825041357.gd1...@glenbarber.us, g...@freebsd.org writes: On Sat, Aug 25, 2012 at 04:55:48AM +0100, Ben Morrow wrote: 1. Is is sensible|supported to use freebsd-update to update just the src component, followed by a normal buildworld/buildkernel to update the rest of the system? I would much prefer to avoid having to use svn, especially given that it isn't in the base system. No. freebsd-update(8) is a binary system updater. It does not touch your source tree. It works just fine for that, actually -- PROVIDED that you installed the source tree the same way (from original installation media or with a previous freebsd-update invocation). I don't know what it will do if you've modified the sources. On the machines where I do this, I don't touch the sources. -GAWollman ___ 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: FreeBSD 9.1-RC1 Available...
On Sat, Aug 25, 2012 at 12:18:39AM -0400, Garrett Wollman wrote: In article 20120825041357.gd1...@glenbarber.us, g...@freebsd.org writes: On Sat, Aug 25, 2012 at 04:55:48AM +0100, Ben Morrow wrote: 1. Is is sensible|supported to use freebsd-update to update just the src component, followed by a normal buildworld/buildkernel to update the rest of the system? I would much prefer to avoid having to use svn, especially given that it isn't in the base system. No. freebsd-update(8) is a binary system updater. It does not touch your source tree. It works just fine for that, actually -- PROVIDED that you installed the source tree the same way (from original installation media or with a previous freebsd-update invocation). He asked followed by buildworld/buildkernel. This implies customization, as did the second question. I don't know what it will do if you've modified the sources. On the machines where I do this, I don't touch the sources. I do. It will overwrite them. Glen pgp78RtHs0SGK.pgp Description: PGP signature
Re: FreeBSD 9.1-RC1 Available...
On Fri, 2012-08-24 at 23:07 -0400, Jim Pingle wrote: On 8/23/2012 11:43 AM, Ian Lepore wrote: On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote: I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. It may be difficult to run an svn mirror that allows you to commit locally and get those changes back to the project, but running a read-only mirror is trivial. The script I run nightly from cron to sync my local mirror is: #!/bin/sh # # svnsync to pull in changes from FreeBSD to my local mirror. # svnsync sync file:///local/vc/svn/base I can't remember how I initially created and populated the mirror, but it's likely I grabbed a snapshot of the mirror at work and brought it home on a thumb drive (just to avoid initial network DL time). I spent a little time today setting up an SVN mirror after reading this thread and wrote up a how-to for those looking to do the same. http://www.pingle.org/2012/08/24/freebsd-svn-mirror Comments/Flames/Corrections welcome... There are two things that I am confused about base. 1) What, exactly, is base? When I do a co, what tree branch is that? 2) Base /appears/ not to contain releng/9.1 or stable/8. How do I mirror those? Jim ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. -- 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: FreeBSD 9.1-RC1 Available...
On Thu, 2012-08-23 at 09:47 -0400, Ken Smith wrote: On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. Looking in the handbook ([1]) I do not see the mechanics of how to set up a mirror, of which I have three CVS mirrors in different infrastructures. Is there a web page somewhere on how to set up, synchronize, maintain, and use a local mirror? [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012 09:47:54 -0400, Ken Smith wrote: On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. Thanks Ken. I'm a bit POLAxed; guess I don't read enough lists .. ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012 07:25-0700, Dennis Glatting wrote: On Thu, 2012-08-23 at 09:47 -0400, Ken Smith wrote: On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. Looking in the handbook ([1]) I do not see the mechanics of how to set up a mirror, of which I have three CVS mirrors in different infrastructures. Is there a web page somewhere on how to set up, synchronize, maintain, and use a local mirror? [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html How about this one? http://motoyuki.bsdclub.org/BSD/cvsup.html -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. dir. 61 14 54 39, | Office.: +47 61 14 54 39, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ 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: FreeBSD 9.1-RC1 Available...
On 8/23/2012 9:47 AM, Ken Smith wrote: On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. I missed this announcement as well. Should we all use the primary URL or is there a list of mirrors? Is anyone going to be updating the Handbook to reflect this? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html However I can see this does not even reflect the more recent use of csup instead of cvsup. I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. Thanks, Ken ___ 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: FreeBSD 9.1-RC1 Available...
On 8/23/2012 9:28 AM, Ian Smith wrote: On Thu, 23 Aug 2012 09:47:54 -0400, Ken Smith wrote: On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. Thanks Ken. I'm a bit POLAxed; guess I don't read enough lists .. I'm a bit surprised too. Shouldn't this mean svn should be in base? If not, should csup come OUT of base? Bryan ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote: I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. It may be difficult to run an svn mirror that allows you to commit locally and get those changes back to the project, but running a read-only mirror is trivial. The script I run nightly from cron to sync my local mirror is: #!/bin/sh # # svnsync to pull in changes from FreeBSD to my local mirror. # svnsync sync file:///local/vc/svn/base I can't remember how I initially created and populated the mirror, but it's likely I grabbed a snapshot of the mirror at work and brought it home on a thumb drive (just to avoid initial network DL time). -- Ian ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012, Trond Endrest?l wrote: On Thu, 23 Aug 2012 07:25-0700, Dennis Glatting wrote: On Thu, 2012-08-23 at 09:47 -0400, Ken Smith wrote: On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. Looking in the handbook ([1]) I do not see the mechanics of how to set up a mirror, of which I have three CVS mirrors in different infrastructures. Is there a web page somewhere on how to set up, synchronize, maintain, and use a local mirror? [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html How about this one? http://motoyuki.bsdclub.org/BSD/cvsup.html I have CVS mirrors. The topic is SVN. ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012, Ken Menzel wrote: On 8/23/2012 9:47 AM, Ken Smith wrote: On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. I missed this announcement as well. Should we all use the primary URL or is there a list of mirrors? Is anyone going to be updating the Handbook to reflect this? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html However I can see this does not even reflect the more recent use of csup instead of cvsup. I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. Thanks. I have several cases where I cannot have machines going to the Internet to update for various reasons, including WAN loading and policies, but I can have them hit local mirrors. I have three sites: #1, Static with less than ten servers. Strong maintenance policies. #2, Mostly static with twenty servers, virtual instances, laptops, and sticks. Loose maintenance policies #3, Largely dynamic but three servers and instances are static. Regulated environment with associated maintenance policies. If CVS is fading then I need to move my CVS mirrors to SVN mirrors. ___ 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: FreeBSD 9.1-RC1 Available...
Am Thu, 23 Aug 2012 09:43:01 -0600 schrieb Ian Lepore free...@damnhippie.dyndns.org: On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote: I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. It may be difficult to run an svn mirror that allows you to commit locally and get those changes back to the project, but running a read-only mirror is trivial. The script I run nightly from cron to sync my local mirror is: #!/bin/sh # # svnsync to pull in changes from FreeBSD to my local mirror. # svnsync sync file:///local/vc/svn/base I may have misunderstood all this, but I run a local read-only mirror of the source-repository for my tinderbox (via the cvsup-mirror port). Do I have to change that from csup to svn, too, then? Given the fuzz made here about deprecating (or not) pkg_* recently, I can hardly believe that this was broken just so. Is there a new port that does the same for svn? ___ 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: FreeBSD 9.1-RC1 Available...
On Aug 23, 2012, at 10:13 AM, Dennis Glatting wrote: If CVS is fading then I need to move my CVS mirrors to SVN mirrors. CVS is fading. Migrate to svn. Warner ___ 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: FreeBSD 9.1-RC1 Available...
On 8/23/2012 11:43 AM, Ian Lepore wrote: On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote: I found two good primers: http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER The second primer in the committer handbook seems to indicate that it is difficult to run an SVN mirror. This appears to me to be the biggest drawback. I have been using CVS and perforce for years, but subversion is new to me. It may be difficult to run an svn mirror that allows you to commit locally and get those changes back to the project, but running a read-only mirror is trivial. The script I run nightly from cron to sync my local mirror is: #!/bin/sh # # svnsync to pull in changes from FreeBSD to my local mirror. # svnsync sync file:///local/vc/svn/base I can't remember how I initially created and populated the mirror, but it's likely I grabbed a snapshot of the mirror at work and brought it home on a thumb drive (just to avoid initial network DL time). -- Ian Thanks Ian, The shame of it is I just setup a new read-only mirror on CVS about a month ago! The initial download did take quite awhile. I hope some doc committers can add this information to a wiki or update the committer handbook to reflect the Read only options. In the mean time I found some articles that may help others: http://csoft.net/docs/svnsync.html.en http://www.kirkdesigns.co.uk/mirror-svn-repository-svnsync http://blog.notreally.org/2006/11/30/setting-up-a-subversion-mirror-repository-using-svnsync/ http://blogs.collab.net/subversion/2007/08/mirroring-repos/ http://wordaligned.org/articles/how-to-mirror-a-subversion-repository Ken ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, Aug 23, 2012 at 09:13:33AM -0700, Dennis Glatting wrote:
...
The second primer in the committer handbook seems to indicate that it is
difficult to run an SVN mirror. This appears to me to be the biggest
drawback. I have been using CVS and perforce for years, but subversion
is new to me.
Thanks.
I have several cases where I cannot have machines going to the Internet to
update for various reasons, including WAN loading and policies, but I can
have them hit local mirrors. I have three sites:
...
I asked Dennis if a description of how I handle my private read-only SVN
mirrors might help, and his reaction was positive, so
First: here's what I'm trying (and succeeding, AFAICT) to accomplish:
* I have a build machine at home, where I currently track stable/8,
stable/9, and head (on different slices) on a daily basis. I also
update the installed ports on that machine daily.
Periodically (by default, weekly), I also install the Sunday
snapshot of stable/8 on my 2 production machines (and update their
installed ports). [I expect to switch these machines to stable/9
soon. The build machine has already been building stable/9 kerenls
for them. Shortly after that switch, I expect to stop tracking
stable/8.]
Separate from the above, I also track stable/8, stable/9, and head on
a daily basis on my laptop; I also update its installed ports on a
daily basis. One of the reasons I do this is to gain actual
experience with the code I'm expecting to install on the production
machines: the build machine is used only for that, and when its job is
done for the day, I power it off.
Since the laptop spends some of the time it may be building FreeBSD
or ports disconnected from a network (e.g., while I'm commuting
to work), I prefer to just keep a local mirror of the SVN repo
on my laptop.
* So, I started with one of the recent seed repositories in each case,
and have my build machine (freebeast.catwhisker.org) use svnsync to
re-sync its local mirror with the repo on svn.freebsd.org.
* As somewhat of a relic of my experiences doing this with CVS mirrors,
I perform the re-sync in 2 stages overnight. After the 2nd one, I
update the local /usr/ports hierarchy (which used to be a CVS working
direwctory, and is now an SVN working copy).
The timing is intended so that during the daytime, my local mirror
is stable: if I were to check out (say) head from that mirror
at 5AM, noon, 6PM, and 10PM, I would get the same result each
time (even if I didn't specify a GRN).
* As another relic of doing something similar with CVSup, I use the
login cvsupin to actually do this work.
* Somewhere, I acquired the perception that if, after setting up the
SVN mirror on freebeast, if I were to try to also use svnsync on my
laptop, that effort would end up talking back to svn.freebsd.org --
which is NOT what I want, for 2 reasons:
* I want to keep my mirrors in sync with one another, so I have
reasonable assurance that (kernel configs and other local
provisioning aside) I'm running the same code on my laptop that I
would be running on the others.
* I am also trying to avoid using more sv,freebsd.org resources tyhan
necessary.
Therefore, for re-syncing the SVN mirrors on my latop, I use rsync(1).
As a bit of an implementation detail, I consign my repositories to
separate file systems, and I have symlinks with names that depict the
function pointing to appropriate places in the file system -- e.g.:
d134(9.1-P)[13] df /repo
Filesystem 1K-blocks UsedAvail Capacity Mounted on
/dev/ada0s4f 40622796 22955728 1441724661%/repo
d134(9.1-P)[14] ls -F /repo
cvs/svn/
d134(9.1-P)[15] ls -F /repo/*
/repo/cvs:
local/
/repo/svn:
freebsd/local/
d134(9.1-P)[16] ls -lT /{cvs,svn}
lrwxr-xr-x 1 root wheel 9 Sep 27 08:49:09 2010 /cvs - /repo/cvs
lrwxr-xr-x 1 root wheel 9 Sep 27 08:49:09 2010 /svn - /repo/svn
d134(9.1-P)[17] ls -F /svn/freebsd
doc/ports/ src/
d134(9.1-P)[18]
I have attached a copy of the script I use to do this. It isn't really
set up for more general consumption -- it hard-codes the name of my
build machine, for example.
Here are some sample entries from /etc/crontab. First, for the build
machine:
# Local additions
3001 * * * cvsupin /usr/local/etc/svn-repo -f
3003 * * * cvsupin /usr/local/etc/svn-repo -f -w
/usr/ports
And from my laptop:
# Local additions
40 01 * * * cvsupin /usr/local/etc/svn-repo -l
40 03 * * * cvsupin /usr/local/etc/svn-repo -l -w
/usr/ports
# Copied from freebeast, for when I'm on the road
# 3001 * * * cvsupin /usr/local/etc/svn-repo -f
# 3003 * * * cvsupin /usr/local/etc/svn-repo -f -w
/usr/ports
One other thing: I rather like to have the logs from the svnsync
handy, so the
Re: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: The first release candidate of the 9.1-RELEASE release cycle is now available on the FTP servers for amd64, i386, and powerpc64. The MD5/SHA256 checksums are at the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ (or any of the FreeBSD mirror sites). snip I have just upgraded (an x86_64 VM) from 9.0-RELEASE to 9.1-RC1, using freebsd-update. Very smooth, and no apparent hitches at all. Thanks to all concerned, and well done. One thing (welcome, but puzzling) which surprised me was that my vboxguest.ko did *not* need to be recompiled. How did the upgrade manage that? ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, Aug 23, 2012 at 6:47 AM, Ken Smith kensm...@buffalo.edu wrote:
On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote:
On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote:
With both the doc and ports repositories now moved to SVN it has been
decided to not export the 9.1 release branch activity to CVS. So
csup/cvsup update mechanisms are not available for updating to 9.1-RC1.
If you would like to use SVN the branch to use is releng/9.1.
Assuming the stupid question is the one you didn't ask, just to clarify:
does this mean that c*sup won't work with these RCs in particular, or
that CVS is dead and SVN becomes mandatory from 9.1-RELEASE?
cheers, Ian
The latter. If you are not using FreeBSD-Update to handle the updates
of a machine you'll need to update your source tree using SVN for
release branches (releng/*) from now on. Updates of the CVS repository
will continue for the existing stable/* and head for now. I don't think
anything has been decided on when that will stop.
A couple of quick comments:
* RELENG_9 is still alive and will continue for the forseeable future.
You can track 9-STABLE via cvs/cvsup.
* This was an accident, not something that we'd planned on to doing.
cvs is just something we mostly don't think about anymore for src.
The switch was thrown around 4 years ago now, back in 2008. It's 2012
now.
* releases (isos, ftp.freebsd.org, etc) have been build from svn since
9.0. All the embedded $FreeBSD$ strings etc are svn-style. If you
tried to check out from RELENG_9_0 or RELENG_9_1 (which is missing)
from cvs and do a build, the binaries *DO NOT MATCH* the official
binaries. What's happening here is that there's no
RELENG_9_1_0_RELEASE tag in cvs.
* Don't expect to see any 10.0-alpha/beta/rc/release/stable to *ever*
make it to an official cvs tree. It's probably time to move a
freebsd-ified cvs from head to ports.
* RIght now you can mirror
svn://svn.freebsd.org/base/{stable/9,release/9.1*,etc} to your laptop,
and Simon is setting up a US-east coast and US-west coast mirror. You
can easily switch your mirrors on the fly if there's a closer/faster
one.
* We have some seed tarballs of recently synced repo images around
somewhere. I'll see where they're available. But in a nutshell, you
do this:
/home/peter/svnsync$ fetch svnmirror-base-r123456.txz
/home/peter/svnsync$ tar xf svnmirror-base-r123456.txz
/home/peter/svnsync$ svnsync file:///home/peter/svnsync/base
and run that from cron with a lock file, probably with -q for quiet.
Then you can have a local copy of the repo for offline use. It has
the same repo uuid so you can svn switch/relocate at will. I
personally on my laptop.
You can do your own personal svnsync all the way from rev 0, but it
takes some time. It's more time efficient to start with a seed and
let it catch up.
--
Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV
All of this is for nothing if we don't go to the stars - JMS/B5
If Java had true garbage collection, most programs would delete
themselves upon execution. -- Robert Sewell
___
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: FreeBSD 9.1-RC1 Available...
On 8/23/2012 10:36 AM, Bryan Drewery wrote: On 8/23/2012 9:28 AM, Ian Smith wrote: On Thu, 23 Aug 2012 09:47:54 -0400, Ken Smith wrote: On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. Thanks Ken. I'm a bit POLAxed; guess I don't read enough lists .. I'm a bit surprised too. Shouldn't this mean svn should be in base? If not, should csup come OUT of base? I rethought this. Ignore me. Bryan ___ 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: FreeBSD 9.1-RC1 Available...
On 23 Aug 2012, at 20:41, Peter Wemm pe...@wemm.org wrote:
On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote:
With both the doc and ports repositories now moved to SVN it has been
decided to not export the 9.1 release branch activity to CVS. So
csup/cvsup update mechanisms are not available for updating to 9.1-RC1.
If you would like to use SVN the branch to use is releng/9.1.
* RIght now you can mirror
svn://svn.freebsd.org/base/{stable/9,release/9.1*,etc} to your laptop,
and Simon is setting up a US-east coast and US-west coast mirror. You
can easily switch your mirrors on the fly if there's a closer/faster
one.
Real world got in the way, but they should be ready by Friday or Saturday, and
will be documented in the Handbook.
On a side note, the svn part of one mirror had to be re-created a few days ago
as svnsync gets very unhappy if you pull the power while it's running (we had a
PSU die). There seem to be a fair chance your local repository gets corrupted
enough in that case that svn just gives up. Not that it's a big problem, but is
a bit annoying.
We (clusteradm) are working on getting an EU mirror up, but no timeframe yet.
You can do your own personal svnsync all the way from rev 0, but it
takes some time. It's more time efficient to start with a seed and
let it catch up.
And if people are wondering, some time is really some time. The original ports
mirror took ~24h to create - and that was over the LAN. Don't do that yourself
unless you feel like doing a latency test of your internet connection :-).
--
Simon L. B. Nielsen
___
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: FreeBSD 9.1-RC1 Available...
On Thu, Aug 23, 2012 at 2:52 PM, Simon L. B. Nielsen si...@freebsd.org wrote:
On 23 Aug 2012, at 20:41, Peter Wemm pe...@wemm.org wrote:
On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote:
With both the doc and ports repositories now moved to SVN it has been
decided to not export the 9.1 release branch activity to CVS. So
csup/cvsup update mechanisms are not available for updating to 9.1-RC1.
If you would like to use SVN the branch to use is releng/9.1.
* RIght now you can mirror
svn://svn.freebsd.org/base/{stable/9,release/9.1*,etc} to your laptop,
and Simon is setting up a US-east coast and US-west coast mirror. You
can easily switch your mirrors on the fly if there's a closer/faster
one.
Real world got in the way, but they should be ready by Friday or Saturday,
and will be documented in the Handbook.
On a side note, the svn part of one mirror had to be re-created a few days
ago as svnsync gets very unhappy if you pull the power while it's running (we
had a PSU die). There seem to be a fair chance your local repository gets
corrupted enough in that case that svn just gives up. Not that it's a big
problem, but is a bit annoying.
We (clusteradm) are working on getting an EU mirror up, but no timeframe yet.
You can do your own personal svnsync all the way from rev 0, but it
takes some time. It's more time efficient to start with a seed and
let it catch up.
And if people are wondering, some time is really some time. The original
ports mirror took ~24h to create - and that was over the LAN. Don't do that
yourself unless you feel like doing a latency test of your internet
connection :-).
You'll also find out very quickly how much fsync(2) hurts on a softdep
or su+j system. The svn fsfs backend does a fsync multiple times per
revision to guarantee its transaction boundaries.
There's a reason why I wrote nofsync.ko for these scenarios. Back
when I did the first mirror for making a seed, it was the difference
between what was shaping up to take about 12 hours vs what ended up
taking 25 minutes with nofsync.ko + noatime + full async + no softdep
+ no softdep+j.
--
Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV
All of this is for nothing if we don't go to the stars - JMS/B5
If Java had true garbage collection, most programs would delete
themselves upon execution. -- Robert Sewell
___
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: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012 12:37:04 -0500, Walter Hurry walterhu...@gmail.com wrote: One thing (welcome, but puzzling) which surprised me was that my vboxguest.ko did *not* need to be recompiled. How did the upgrade manage that? FreeBSD has a stable ABI unlike Linux. A kernel module compiled for any 9.x release should work on any other 9.x release without needing to be recompiled. ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012 17:41:49 -0500, Mark Felder wrote: On Thu, 23 Aug 2012 12:37:04 -0500, Walter Hurry walterhu...@gmail.com wrote: One thing (welcome, but puzzling) which surprised me was that my vboxguest.ko did *not* need to be recompiled. How did the upgrade manage that? FreeBSD has a stable ABI unlike Linux. A kernel module compiled for any 9.x release should work on any other 9.x release without needing to be recompiled. Ah right, thanks. I am indeed a refugee fom Linux ducks for cover. ___ 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: FreeBSD 9.1-RC1 Available...
Excerpt from announcement by Ken Smith kensm...@buffalo.edu: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. I read your message and followup messages and have questions about how to switch from csup to svn. System source is in /usr/src obtained by csup, apparently now being deprecated. Do I need to delete (rm -R /usr/src/*) before running svn co svn://svn.freebsd.org/base/stable/9 /usr/src I don't want an out-of-sync mess resulting from mixing two versions, assume that wouldn't work well. I guess I need to switch the doc (/usr/doc) also to svn. What about the ports? Would I need to switch the ports tree from portsnap fetch update, or is portsnap still the proper way? Tom ___ 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: FreeBSD 9.1-RC1 Available...
On Thu, Aug 23, 2012 at 05:41:49PM -0500, Mark Felder wrote: On Thu, 23 Aug 2012 12:37:04 -0500, Walter Hurry walterhu...@gmail.com wrote: One thing (welcome, but puzzling) which surprised me was that my vboxguest.ko did *not* need to be recompiled. How did the upgrade manage that? FreeBSD has a stable ABI unlike Linux. A kernel module compiled for any 9.x release should work on any other 9.x release without needing to be recompiled. This is a statement that is false at least two times, if not three. This was a question about Kernel Binary Inteface, not Application Binary Interface. First, we have zero guarantees about ability to load or have a system survive loading of the module compiled against the later kernel. Second, we do not have real KBI definition, and KBI stability is managed only ad-hock. E.g. VFS quite often breaks, while network or disk controllers drivers are usually fine. YMMV. Snobby false statements hurt the project. pgpYJ1xbt3Q6F.pgp Description: PGP signature
