similar to: Please help, updated to 4.8 serious issues

Displaying 20 results from an estimated 1000 matches similar to: "Please help, updated to 4.8 serious issues"

2005 May 17
4
HOW TO Enable IPSec for FreeBSD.......???
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
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.
2009 Apr 25
1
installing crossbuilds
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
2012 Feb 11
3
9.0-RELEASE PV from scratch on XCP v1.1.0
Title: HOWTO-FreeBSD-on-XCP Author: John D. "Trix" Farrar Date: 2012-02-09 * The Challenge - ParaVirtualized FreeBSD 9.0-RELEASE under XCP 1.1.0 The idea here is to create a PV FreeBSD VM under Xen Cloud Platform (XCP) without starting with an HVM first. The documentation I''''ve been able to find on-line is at least a year old and is mostly written for Xen (under
2003 Jun 19
4
SMP goes away after installworld (4.8-STABLE)
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
2008 Jun 25
3
Problem with /boot/loader
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
2003 May 16
2
make installworld fails : touch not found ?
Hi, hackers : Yesterday night and this morning, I cvsup my system to latest STABLE branch source (RELENG_4). All make buildworld, buildkernel, and installkernel procedure was completed with no error. But when I boot into single user mode and try to make installworld, I always got " touch: not found " error. Does anyone encounter this situation ? I have no idea about that. :-( Here is
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
2003 Jul 08
4
Hardening production servers
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
2013 Feb 26
1
[releng_9 tinderbox] failure on arm/arm
TB --- 2013-02-26 21:23:55 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-26 21:23:55 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa at freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-26 21:23:55 - starting RELENG_9 tinderbox run for arm/arm TB --- 2013-02-26 21:23:55 - cleaning the
2013 Jul 04
1
Phantom nulls in usbdevs.h during 9-STABLE kernel build
We are seeing strange problems building the kernel on 9-STABLE. The problem is intermittent and will go away if we build enough times in a row without making any changes. The problem seems to be that the usbdevs.h file (which appears to be automatically generated) gets random NULL bytes in it. This occurs on multiple servers with ECC RAM and ZFS filesystems (sometimes mounted over NFS from
2003 Oct 02
8
upgrading 4.0 to stable
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
2003 Jul 27
4
Sound Driver Via
Hi, im a newbie to freebsd. I just installed 5.1, but my sound isnt working, im not sure if I have to install the alsa sound drivers or not. the integrated sound I have with my shuttle mv42n board is Via AC97 sound, and when I go into kde i get the error message Sound server informational message: Error while initializing the sound driver: device /dev/dsp can't be opened (No such file or
2004 Feb 06
2
IPFIREWALL_DEFAULT_TO_ACCEPT becomes default to deny
Hey Guys, today I upgraded to 4.8-RELEASE-p15. As usual I set IPFIREWALL to default accept in my kernel config file. Config & make weren't complaining so, installed the kernel, reboot and there it was: >IP packet filtering initialized, divert disabled, rule-based forwarding enabled, default to deny, logging disabled Another rebuild didn't work out so... I reviewed
2003 Aug 09
28
[releng_4 tinderbox] failure on alpha/alpha
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 ---
2003 Aug 09
18
[releng_4 tinderbox] failure on i386/i386
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 - ERROR: unable to check out the source tree TB ---
2005 Oct 23
2
Is it feasible to cross-build compat5x binary?
Hi folks, I think we need to update compat5x binary to fix FreeBSD-SA-05:21.openssl, but will the binaries built by ``make universe'' be identical with actual build on Alpha, Sparc64, etc? (Yes, I'm volunteering to do the work iff they are identical ;-) Cheers, -- Xin LI <delphij frontfree net> http://www.delphij.net/ See complete headers for GPG key and other information.
2003 Jul 07
2
FreeBSD 4.4-REL to FreeBSD 4.8-STABLE upgrade problem.
I sent this to freebsd-questions earlier via the newsgroup, but I just found out today that the list-to-news gateway has been down for half a month now. Any idea when it's going back up? Who was hosting that service anyway? And now for the question.. I have a test server that is being used to test a 4.4-REL to 4.8-STABLE upgrade, and I've found the system will no longer boot unless I
2003 Jun 22
2
Stable#1
Got a pretty stupid question... My kernel is now 4.8 Stable#1 but when does the number change when i do makeworld and the other things? or where can i see that?
2013 Nov 20
1
[releng_10 tinderbox] failure on sparc64/sparc64
TB --- 2013-11-19 23:00:41 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-11-19 23:00:41 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-19 23:00:41 - starting RELENG_10 tinderbox run for sparc64/sparc64 TB --- 2013-11-19 23:00:41 - cleaning the