search for: releng_4

TB --- 2003-08-09 16:00:12 - starting RELENG_4 tinderbox run for i386/pc98 TB --- 2003-08-09 16:00:12 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:12 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:12 - ER...

TB --- 2003-08-09 16:00:11 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-08-09 16:00:11 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:11 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:11...

TB --- 2003-08-09 16:00:11 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-08-09 16:00:11 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:11 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:11 - ER...

TB --- 2003-10-02 04:44:07 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-10-02 04:44:07 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:49:12 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/i386/src...

TB --- 2003-10-02 04:00:01 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-10-02 04:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:07:38 - building world TB --- cd /home/des/tinderbox/RELENG_4/alpha/alp...

TB --- 2003-07-21 05:27:28 - starting RELENG_4 tinderbox run for i386/pc98 TB --- 2003-07-21 05:27:28 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-07-21 05:33:30 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98/src...

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 just getting wet behind the ears with cvsup. --Richard

On the advisory about the realpath problem it says that it was corrected: RELENG_4_8 src/UPDATING 1.73.2.80.2.3 src/lib/libc/stdlib/realpath.c 1.9.14.1 src/sys/conf/newvers.sh 1.44.2.29.2.2 I ran cvsup and when I look at my src/lib/libc/stdlib/realpath.c I see src...

I use FreeBSD RELENG_4 with rsync version 2.5.4 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 32-bit system inums, 64-bit internal inums and when I try to trans...

Hello -stable: I'm getting an error & stoppage from mergemaster in RELENG_4 (now 4.9-PRERELEASE), just updated a few minutes ago, vis: -------------------- cd /usr/src/etc/sendmail; make distribution install -o root -g wheel -m 644 /usr/src/etc/sendmail/freebsd.mc freebsd.cf /var/tmp/temproot/etc/mail install: freebsd.cf: No such file or directory *** Error code 71 Stop...

...ome feedback from people running with INVARIANTS turned on in -stable, I'd appreciate it. If it seems to work for people, I'll talk to re@ about getting this in before 4.9 goes out the door. Ken -- Kenneth Merry ken@kdm.org -------------- next part -------------- ==== //depot/FreeBSD-ken-RELENG_4/src/sys/cam/scsi/scsi_cd.c#9 - /usr/home/ken/perforce2/FreeBSD-ken-RELENG_4/src/sys/cam/scsi/scsi_cd.c ==== *** /tmp/tmp.5698.0 Mon Sep 1 16:06:53 2003 --- /usr/home/ken/perforce2/FreeBSD-ken-RELENG_4/src/sys/cam/scsi/scsi_cd.c Mon Sep 1 15:51:14 2003 *************** *** 60,65 **** --- 60,66 ----...

I've built RELENG_4 isos no problem, is there a trick to building the RELENG_4_8 isos? I am building the 'miniinst' disk - that is, with the release, docs, and a port tree, but no ports. This is so I can do a fresh install without having to update the world... I am using a script that looks like this... #!...

[bcc: to re@] Considering the amount of changes between 4.x and 5.x, and the performance issues of the latter, I think I can safely predict that RELENG_4 will be around for a long time after the RELENG_5 branch. While I understand that some will resist making RELENG_4 any more useful than it currently is (to encourage users to move to 5.x), I think there is one issue that should be addressed: the in-tree version of Perl. -STABLE currently has 5.005...

...nch.) * There is usually only a single -STABLE branch, although during the transition from one major development line to another (such as from FreeBSD 4.x to 5.x), there is a time span in which there are two -STABLE branches. The -STABLE branch tags have names like RELENG_4. The corresponding builds have names like FreeBSD 4.6-STABLE. * Each FreeBSD Release has an associated Security Branch. The Security Branch tags have names like RELENG_4_6. The corresponding builds have names like FreeBSD 4.6-RELEASE-p7. Each branch is supported by th...

Any information on when (or if) the following timestamp vulnerability will be fixed for 4.X? Any information would be appreciated. http://www.kb.cert.org/vuls/id/637934 Thanks. Richard Coleman rcoleman@criticalmagic.com

Hello... In regards to http://www.freebsd.org/security/ , from what I understand the FreeBSD 4.x branch is generally winding down in favor of the 5.x/6.x branches. It would be nice to know ahead of time if 4.11 will also be an extended release, or if that would fall to 4.12. For those of running 4.8 (expiring about the same time as 4.11 is released) we would be in a better position to know

Very shortly after starting the buildworld, it fails in colldef: ===> usr.bin/colldef /usr/obj/home/src/i386/home/src/usr.bin/colldef created for /home/src/usr.bin/colldef yacc -d /home/src/usr.bin/colldef/parse.y cp y.tab.c parse.c lex -t -8 -i /home/src/usr.bin/colldef/scan.l > scan.c rm -f .depend mkdep -f .depend -a -I. -I/home/src/usr.bin/colldef

...The FreeBSD Project Topic: Jailed processes can manipulate host routing tables Category: core Module: kernel Announced: 2004-06-07 Credits: Pawel Malachowski Affects: All FreeBSD 4.x releases prior to 4.10-RELEASE Corrected: 2004-04-06 20:11:53 UTC (RELENG_4) 2004-06-07 17:44:44 UTC (RELENG_4_9, 4.9-RELEASE-p10) 2004-06-07 17:42:42 UTC (RELENG_4_8, 4.8-RELEASE-p23) CVE Name: CAN-2004-0125 FreeBSD only: YES For general information regarding FreeBSD Security Advisories, including descriptions of the fields above,...

since august 8th, 2003 the kernel on my i386 pentiumIII won't compile. the problem arises in locore.s with the definition of the constants $PAGE_SHIFT and $PTESHIFT used in `shr' and `shl' instructions within the macros `fillkpt' and `fillkptphys'. i've tried to cvsup(1) RELENG_4 and RELENG_4_8 every day for over a week now, but kernel builds (as part of a buildworld) don't work anymore. i have set up an area different from the usual /usr/obj/, so i can experiment. if somebody has tips for me, i could do a lot without destroying what's left of my last clean instal...

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 :(( Could you prompt me what's wrong with lsof and how can i get STABLE now ? ----- Regards, Andrew.