similar to: 4.8-STABLE cvsup & kernel compilation

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

TB --- 2008-08-27 11:26:00 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-08-27 11:26:00 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2008-08-27 11:26:00 - cleaning the object tree TB --- 2008-08-27 11:26:30 - cvsupping the source tree TB --- 2008-08-27 11:26:30 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2008-08-27

I just drudged through a bit of the archives and see a FreeBSD bits floating in there that are of some value, but aren''t on the wiki. I posted a few bits on the wiki regarding some FreeBSD cobbling that I''ve done recently and hope that folk find it of use (and start posting their useful bits there as well). http://reductivelabs.com/trac/puppet/wiki/PuppetFreeBSD The

Greetings, After I updated my FreeBSD box from 4.7 to 4.8 I "lost" my users, but heck with users, what I mean by lost is that I can't login, when I try to login as the root or a regular user it says: pam_authanticate: permission denied so, I went ahead and re-updated my box from the very beginning, including unnecessary at this point cvsup. I used this command: make buildworld

I noticed that there were quite a few files with version ids of '$FreeBSD$' when I ran mergemaster after an install of 4.8R. This isn't right is it? What are the consequences of installing over your files with unexpanded version ids? I would like to build a release(make release) and want to know if I can continue or if this is going to be a problem for future

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

Hi, I have tried to enable IPSec support for my FreeBSD( 4.11-RELEASE) system. First, I copied the generic kernel configuration file to a file I called MYKERNEL: #cp /usr/src/sys/i386/conf/GENERIC /usr/src/sys/i386/conf/MYKERNEL Then, I added the following three lines to the options section of /usr/src/sys/i386/conf/MYKERNEL: options IPSEC options IPSEC_ESP options

Hello, I have a problem with loader. I recently upgraded from 6_rel to 7_rel. Now when I install world there is a problem booting. Here is what I do: cd /usr/src make buildworld make buildkernel KERNCONF=BLACK make installkernel KERNCONF=BLACK At this point I can reboot and all is good. After boot I install the new world: cd /usr/src mergemaster -p reboot into single user mode cd /usr/src make

TB --- 2008-07-29 09:37:14 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-07-29 09:37:14 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2008-07-29 09:37:14 - cleaning the object tree TB --- 2008-07-29 09:37:32 - cvsupping the source tree TB --- 2008-07-29 09:37:32 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB ---

Greetings, Apologies if this is not the appropriate list, but my questions are about best practices in maintaining production servers (so I believe I can justify a post in -stable, short of a -release list :) I maintain a modest installation of 6 FreeBSD servers. They're CVSUP'd to RELENG_4_8 (I make buildworld on each individually) and I portupgrade ports as necessary. In an attempt to

Hello, I installed 4.8-RELEASE a few weeks ago, and since I let the effort sit stagnant for a while I decided to do the cvsup/buildworld/buildkernel/installkernel/installworld/mergemaster/MAKEDEV steps to get current. Went fine, rebooted, then noticed that just one CPU was recognized: FreeBSD 4.8-STABLE #0: Thu Jun 19 17:05:20 PDT 2003

I'm just getting into regular use with cvsup (way over do on that one), and I tried to specify a tag=. in the cvsup file. Here's the file: # This file specifies src files are to be uploaded. *default host=cvsup2.FreeBSD.org # *default tag=RELENG_5_1_0_RELEASE *default tag=. *default prefix=/usr *default release=cvs delete use-rel-suffix compress *default base=/usr/local/etc/cvsup

I'm still kind of hung up looking for some definitive answers on this issue. Perhaps you guys can help me out? Frank Date: Mon, 29 Sep 2003 17:55:33 -0500 (CDT) From: "F. Even" <freebsdlists@elitists.org> Subject: re: upgrading 4.0 to stable To: freebsd-questions@freebsd.org Message-ID: <20030929225533.81D352FE@elitists.org> Content-Type: text/plain; charset=iso-8859-1

Hello All, I'm trying to figure out where the problem is, but I'm not having much luck as I seem to get conflicting information from the various logs on my FreeBSD 6.1 system. I'm getting this in the /var/log/samba/log.smbd: [2006/06/05 12:31:43, 0] smbd/oplock.c:release_level_2_oplocks_on_change(771) release_level_2_oplocks_on_change: failed to lock share mode entry for

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

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

TB --- 2008-06-03 08:42:30 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-03 08:42:30 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2008-06-03 08:42:30 - cleaning the object tree TB --- 2008-06-03 08:43:09 - cvsupping the source tree TB --- 2008-06-03 08:43:09 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/i386/supfile TB --- 2008-06-03 08:43:22

Team I have a Dell PowerEdge R720xd, with the Broadcom NetXtreme bcm5720. I found the following thread: http://forums.freebsd.org/showthread.php?t=31769 I find I am unable to use the NIC's (there are 4 on the server). When we put a cable into it we get a "watchdog timeout -- resetting" error, and the machine will pause for 5 or so seconds. IP may or may not come up randomly.

Back before the 7.0 Release I used to install cross builds by NFS-mounting /usr/src and /usr/obj of the build machine on the target machine and running: # cd /usr/src # env MAKEOBJDIRPREFIX=/usr/obj/<stuff> make installkernel KERNCONF=<kernconf> ... This doesn't work any more because all the installation tools are built for the architecture of the build system. The alternative

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 - ERROR: unable to check out the source tree TB ---