Re: FreeBSD 9.1-RC1 Available...
On Thu, 23 Aug 2012 09:01:06 -0700 (PDT)
Dennis Glatting 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 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: Removing CVS from base
John Baldwin wrote: > On Thursday, August 23, 2012 3:41:03 pm Peter Wemm wrote: > > * 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. > > I think this is a bit premature. Just because we are moving away from > using CVS as FreeBSD's scm doesn't mean CVS isn't a useful > general-purpose tool still. For smaller repositories that don't need > fancier things like branches, CVS is quite useful and far lighter weight. > > I could see moving csup out to ports, but not necessarily CVS. Agreed. Principle of least suprise. CVS seems a standard Unix tool & source archive format, something people from other Unix distribs might expect by default. ( Like SCCs once was, between the mists of PWB, forward & beyond a BSD-4.2&3 Symmetric 375 (ex Bill Jollitz of 386BSD) For those of us that have [had to] work with lots of different Unix flavours, it's a PITA having gratuitious extra UNIX variant weirdnesses; (This missing here, that missing or renamed there etc). No need to make standard FreeBSD base awkward for people visiting from other Unixes. To avoid making 7.4M of src/contrib/cvs We have WITHOUT_CVS in man src.conf. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from Yahoo & Hotmail to be dumped @Berklix. http://berklix.org/yahoo/ ___ 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"
9.1-RC1 make buildworld with WITHOUT_LPR NO_LPR not cleaning up properly
/etc/make.conf contains NO_LPR=YES /etc/src.conf contains WITHOUT_LPR=YES make buildworld consistently (9.0 through 9.1-RC1) leaves /usr/share/doc/smm/07.lpd/paper.ascii.gz which is then deleted by make delete-old. This behaviour was not apparent in 8.x. I have systems available to test a fix. ___ 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: 9.1-RC1 make buildworld with WITHOUT_LPR NO_LPR not cleaning up properly
On Friday, August 24, 2012 12:47:45 pm David Boyd wrote:
> /etc/make.conf contains NO_LPR=YES
>
> /etc/src.conf contains WITHOUT_LPR=YES
>
> make buildworld consistently (9.0 through 9.1-RC1) leaves
>
> /usr/share/doc/smm/07.lpd/paper.ascii.gz
>
> which is then deleted by make delete-old.
>
> This behaviour was not apparent in 8.x.
>
> I have systems available to test a fix.
Try this:
Index: share/doc/smm/Makefile
===
--- Makefile(revision 239655)
+++ Makefile(working copy)
@@ -18,7 +18,7 @@ SUBDIR= title \
04.quotas \
05.fastfs \
06.nfs \
- 07.lpd \
+ ${_07.lpd} \
${_08.sendmailop} \
11.timedop \
12.timed \
@@ -28,4 +28,8 @@ SUBDIR= title \
_08.sendmailop=08.sendmailop
.endif
+.if ${MK_LPR} != "no"
+_07.lpd= 07.lpd
+.endif
+
.include
--
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"
Re: FreeBSD 9.1-RC1 Available...
On Thu, Aug 23, 2012 at 8:06 PM, Thomas Mueller wrote: > Excerpt from announcement by Ken Smith : > >> 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 wrote: > On Thu, Aug 23, 2012 at 8:06 PM, Thomas Mueller > wrote: >> Excerpt from announcement by Ken Smith : >> >>> 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 : > >> 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: Updated isboot 0.2.6 and FreeBSD 9.1-RC1
Thank you for the quick response! On Aug 23, 2012, at 6:25 PM, Daisuke Aoyama wrote: > It seems a bug of isboot. Your NIC is link down, but isboot never retry > on first connection. Because of this, it failed to find the boot device. > > I have updated isboot and created 9.1-RC based image. > Please try it: > > http://www.peach.ne.jp/archives/isboot/isboot-0.2.6.tar.gz Working great with the new version of the module. It retries 3-4 times until the link comes up then continues. Performing pretty well, too--this is over a 1Gbps LAN on somewhat dated consumer hardware, with istgt and a ZFS zvol on the other end. > http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-9.1-RC1-amd64-memstick-isboot-0.2.6.img > >> I have a few questions for you (or other knowledgeable people on the list): >> 1) Does iBFT require hardware support in the NIC? >> 2) Does iBFT require NIC driver support? > > NO. You can use both iBFT software like gPXE and NIC's rom like Intel iSCSI > boot agent. > The isboot should work with any NIC supported by FreeBSD. Fantastic. >> 3) Is anything required in loader.conf besides isboot_load="YES"? > > If your NIC driver is within the kernel, you need only isboot_load="YES". > >> 4) Is it likely to work (better) if I find an em(4) card instead? > > I have tested with Intel cards/onboard. If you want the maximum performance, > I recommend you to use Intel card, but other cards should work with isboot. I'll stick with what I have for this machine since it's working. In case you're interested, here is the dmesg output from the machine: mptable_probe: MP Config Table has bad signature: 4\^C\^_ Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #2 r239337M: Fri Aug 24 12:58:51 EDT 2012 r...@stealth.jnielsen.net:/usr/obj/i386.i386/usr/src/sys/BUFF i386 CPU: AMD Athlon(tm) XP 2800+ (2079.60-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Family = 6 Model = a Stepping = 0 Features=0x383fbff AMD Features=0xc0400800 real memory = 1342177280 (1280 MB) avail memory = 1300516864 (1240 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 4fef (3) failed cpu0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x73 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 Correcting nForce2 C1 CPU disconnect hangs agp0: on hostb0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 nfsmb0: port 0xd800-0xd81f irq 23 at device 1.1 on pci0 smbus0: on nfsmb0 nfsmb1: on nfsmb0 smbus1: on nfsmb1 ohci0: mem 0xe5085000-0xe5085fff irq 20 at device 2.0 on pci0 usbus0 on ohci0 ohci1: mem 0xe5081000-0xe5081fff irq 21 at device 2.1 on pci0 usbus1 on ohci1 ehci0: mem 0xe5082000-0xe50820ff irq 22 at device 2.2 on pci0 usbus2: EHCI version 1.0 usbus2 on ehci0 pci0: at device 5.0 (no driver attached) pcm0: port 0xdc00-0xdcff,0xe000-0xe07f mem 0xe5086000-0xe5086fff irq 21 at device 6.0 on pci0 pcm0: pcib1: at device 8.0 on pci0 pci1: on pcib1 skc0: port 0x9000-0x90ff mem 0xe402-0xe4023fff irq 17 at device 4.0 on pci1 skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) sk0: on skc0 sk0: Ethernet address: 00:11:2f:57:f4:bf miibus0: on sk0 e1000phy0: PHY 0 on miibus0 e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto pci1: at device 7.0 (no driver attached) ath0: mem 0xe401-0xe401 irq 18 at device 8.0 on pci1 [ath] enabling AN_TOP2_FIXUP ath0: DMA setup: legacy ath0: [HT] enabling HT modes ath0: [HT] 2 RX streams; 2 TX streams ath0: AR9220 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0 atapci0: port 0x9400-0x9407,0x9800-0x9803,0x9c00-0x9c07,0xa000-0xa003,0xa400-0xa40f mem 0xe4024000-0xe40241ff irq 18 at device 11.0 on pci1 ata2: at channel 0 on atapci0 ata3: at channel 1 on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 9.0 on pci0 ata0: at channel 0 on atapci1 ata1: at channel 1 on atapci1 fwohci0: <1394 Open Host Controller Interface> mem 0xe5083000-0xe50837ff,0xe5084000-0xe508403f
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 : > > 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 : > > > > 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"
