similar to: cvsup with tag=. on src and upgrading (in general)

Displaying 20 results from an estimated 2000 matches similar to: "cvsup with tag=. on src and upgrading (in general)"

2003 Jul 26
1
Strange Kernel Compile Error....
merlin# rm GENERIC merlin# cd /usr/share/examples/cvsup/ merlin# cvsup stable-supfile Connected to cvsup.uk.FreeBSD.org Updating collection src-all/cvs Checkout src/sys/i386/conf/GENERIC Finished successfully merlin# cd /usr/src merlin# make buildkernel KERNCONF=GENERIC -------------------------------------------------------------- >>> Kernel build for GENERIC started on Sat Jul 26
2003 Jun 24
5
IPv6 CVSUP mirrors?
Hi. I am looking for an IPv6 capable CVSUP mirror. I found a discussion from one year ago where it was stated that CVSUP was not IPv6-capable. Does anyone know if this has changed? Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam
2003 Apr 18
1
4.8-STABLE cvsup & kernel compilation
hi guys, i have version 4.8-STABLE running. i've just update my stable-supfile and building, recompiling my custom kernel, my question is: if im going to cvsup my stable-supfile again, and compile the customed kernel again, do i have to: make buildworld, make installworld, mergemaster again or just make buildkernel KERNCONF & make install KERNCONF? hoping for your reply guys, thanks.
2003 Aug 26
1
cvsup error
Hello Mike, i got these error when i`m tried to cvsup my box (4.7 STABLE) to 4.8, these error showed up in the make buildworld step, at stage 4: populating /usr/obj/usr/src/i386/usr/include. and this is my supfile: *default host=cvsup12.FreeBSD.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs *default tag=RELENG_4 *default delete use-rel-suffix *default
2003 May 11
1
make release headaches
Hi there, When I do a make buildworld and try to do a make release it will fail telling that it needs the CVSROOT directory. I do cvsup /etc/cvs-supfile and receive nothing ; # /etc/cvs-supfile *default host=cvsup3.nl.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4_8 *default delete use-rel-suffix *default compress cvsroot-all If I remove
2003 Sep 03
2
Can get no STABLE
Hello all, well, the first problem i got is lsof wont work. I got the message "lsof: WARNING: compiled for FreeBSD release 4.3-RELEASE; this is 4.8-STABLE." Then I tried to to cvsup and rebuild world. The file i used is /usr/share/examples/cvsup/stable-supfile and tag is RELENG_4. After a few hours i got 4.9-PRERELEASE :( Next time i used RELENG_4_8 tag and got 4.8-RELEASE-p4 :((
2003 Sep 11
2
DNS related ports from ports/net/ to ports/dns
At 12:44 AM 9/12/2003 -0400, Adam Weinberger wrote: >New categories are added slowly to the cvsup category lists. It's best >to cvsup using ports-all, and add the directories you don't want (such >as languages: "ports/french*" etc.) to the refuse file. How is having a refuse file slowing down CVSup down best? The fact is a category does not appear often and for those
2006 Apr 13
1
6.1-RC1 fails to compile... missing header files in /usr/src/gnu/usr.bin/groff/src/libs/libgroff?
Hi. I am currently running 6.0 (here is uname -a). FreeBSD pc-racine1.mcmaster.ca 6.0-RELEASE-p2 FreeBSD 6.0-RELEASE-p2 #7: Thu Jan 12 09:30:38 EST 2006 root@pc-racine1.mcmaster.ca:/usr/obj/usr/src/sys/OPTIPLEX i386 Just tried a fresh cvsup from cvsup9, a standard compile via cvsup -g -L 2 /usr/share/examples/cvsup/current-supfile && cd /usr/obj && chflags -R noschg *
2008 Aug 06
2
FreeBSD 6.3/amd64: cvsup: Bus error (core dumped)
Hello. Dont know is this list right for this topic, but dont know witch one is. So I got 6.3-STABLE-200807-amd64-disc1.iso I have installed it cd /usr/ports/net/cvsup-without-gui/ make install make clean #cvsup some-stable-sup-file Connected to cvsup.xxxxxx.ru Bus error (core dumped) I cant get fresh src and ports trees and cant compile fresh 6.X-stable system with athlon64 optimization. :(
2003 Jun 13
2
exact difference between RELENG_4, RELENG_4_5 . . . RELENG_4_8
Read the documentation on the meaning of the various 4.X tags, and am not sure what is meant by this: "The release branch for FreeBSD-4.6 and FreeBSD-4.6.2, used only for security advisories and other seriously critical fixes." Similar descriptions are used for the other RELENG_4_X tags. If I specify RELENG_4 will cvsup also include RELENG_4_3 to RELENG_4_8? Sorry folks - I'm
2003 May 25
3
Tracking 4-stable rather than 4.8-stable
Hi, I would like to follow 4-stable on my FreeBSD box, and i can't fetch binaries from /stand/sysinstall. Can anyone help me? Here is how i did: 1) I installed 4.8-RELEASE from CD, 2) I used cvsup to upgrade. For this i used the stable-supfile as shown in the Handbook. => My OS version as shown by 'uname -a' and '/stand/sysinstall' is "4.8-STABLE". It
2003 Jul 12
1
Problems Compiling after upgrading via cvsup
I couldn't compile any thing after upgrading 4.6.2 to 4.8 via cvsup I also updated ports via cvsup And nothing would compile, nothing, just error after error I cd /usr/ports did a -"make clean"- (which takes over an hour on my machine) Now all my compile problems have gone away I think I will cd to /usr/ports after doing anything with cvsup or any install, just in case or am I
2006 Sep 04
1
documentation on cvsup for backing up cvs repositories
hey friends, I am trying to find out documentation on cvsup for backing up cvs repositories on Centos 4.0 Can somebody give me the link for the same ? Thanks & Regards Ankush Grover
2008 May 08
1
cvsup.uk.FreeBSD.org
Greetings, cvsup.uk.FreeBSD.org is outdated. I know this is not the proper list, but which one is? -- Best Wishes, Stefan Lambrev ICQ# 24134177
2003 Oct 01
3
cvsup error (again)
Dear all, i just cvsup my machine yesterday. but when i tried to make build kernel it shown this message : config: /usr/src/sys/i386/conf/TRISTANIA:52: devices with zero units are not likely to be correct *** Error code 1 every time i remarked those line, it came up with another error on another line on my kernel. could you please tell me what should i do? because it's a production box.
2003 Aug 19
3
Is rl broken?
Greetings, I cvsup'd and rebuilt a FreeBSD 4.8 system last Friday after receiving the realpath security advisory. The machine is remote and the NIC uses the rl driver. After booting the machine I had no network connectivity. The person at the remote site says the boot was normal and he could see that the NIC was properly configured but he could not ping it and I could not login. We booted
2008 Sep 10
2
Fixing cvsup bus error
I'm getting the bus error mentioned in PR bin/124353 and I need a bit more detail on how to apply the patch. Right now I'm getting the following error when I try to do a make on cvsup-without-gui: Fatal Error: bad version stamps: SupTCP.m3 I put the changes in the /usr/local/lib/m3/pkg/m3core/src/unix/freebsd-4.amd64/Unix.i3 file I created the file
2003 Sep 19
1
making 4.8-RELEASE-p7
Hello, freebsd-security. I'm trying to build 4.8-RELEASE-p7 to distribute it trought my clients. What am I doing: #cd /usr/share/examples/cvsup #cvsup standard-supfile (after I've done necessary changes) #cd /usr/src #make buildworld Thus, I have /usr/obj "populated with the output of ``make buildworld''" as it described in man 7 release. Then, I have read
2003 Oct 01
1
latest cvsup to stable kernel build fall down, go boom
GENERIC kernel build, cvsup as of 21:37 October 1 2003: ../../vm/vm_map.c: In function `vm_init2': ../../vm/vm_map.c:190: `maxfiles' undeclared (first use in this function) ../../vm/vm_map.c:190: (Each undeclared identifier is reported only once ../../vm/vm_map.c:190: for each function it appears in.) *** Error code 1 Using the freebsd protector patch (anti stack smashing), FYI.
2003 Apr 14
1
updating from 4.8-RELEASED to 4.8-STABLE
hi to all FreeBSD user. i have a problem about updating from 4.8-RELEASED to 4.8-STABLE, here's exactly what i did: first: cvsup -g -L 2 stable-supfile, where my stable-supfile is located at /root. 2nd: cd /usr/src; make buildworld; make buildkernel KERNCONF=BUFDAEMON; make installkernel KERNCONF=BUFDAEMON 3rd: reboot; mergemaster -p; make installworld; mergemaster; reboot. after