similar to: Problem with /boot/loader

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.

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

Hi! I'm trying to cross-compile 4.8-STABLE world to install it over NFS later. I have ./make.conf: # start of file CPUTYPE=i486 KERNCONF?=CONS MODULES_WITH_WORLD=true DESTDIR=/mnt/cons # end of file I run: dir=`pwd` make __MAKE_CONF=$dir/make.conf buildworld 2>&1 | tee $dir/bw.log It fails: ===> gnu/usr.bin/groff/contrib ===> gnu/usr.bin/groff/contrib/mm sh

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

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

I upgraded my 7.0 system to 7.1-RELEASE with freebsd-update only to find that it no longer boots correctly, instead crashing with a BTX backtrace. If I break to the loader prompt and use 'ls /boot', I also get a backtrace. A new install of 7.1 on this hardware using a separate SCSI card and drive array also leads to a BTX backtrace. I have copied this below as the first (most

Hi, Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled This is stripped down kernel with everything possible loaded from modules. Any ideas? Did not see any warnings in UPDATING... ./danfe

mmmm... stable... :D /usr/src # make installworld ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. /usr/src # grep audit /usr/src/UPDATING /usr/src # ??? -- - Alfred Perlstein - CTO Okcupid.com / FreeBSD Hacker / All that jazz -

Question... I do alot of stable upgrades and as a result I spend alot of time with mergemaster. My changes in etc are minimal, so I rather wipe out my existing /etc (except for machine specific files like fstab, and so on) and have mergemaster install everything from /usr/src/etc. This way I don't have to spend time going through all the diffs. I have found that there is no quick and

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.

I administer a remote server and want to apply some of the security patches. (I assume this is the best way to go since I can't go into single-user mode to use CVsup). I have a couple of questions. First, I have installed one of the pgp ports to verify the patches. When I run it, I get this message: > File 'buffer46.patch.asc' has signature, but with no text. > Text is

Hi, I was under the impression a successful make world was updating include files in /usr/include/netinet too. When I have a good make world, the files in /usr/include have new time stamps, but the ones in netinet have not! Am I missing something here? My current stable doesn't compille properly it fails in kdump on a missing ioctlcmd_t typedef. Peter

Hi, I've got a problem with booting zfs-on-root FreeBSD 9.2-PRERELEASE. I'm getting: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool klawisz gptzfsboot: failed to mount default pool klawisz Machine is VM running under KVM on Proxmox 2.3-13. VM has 8 GB of RAM, 400 GB of local storage with SCSI Controller type: Default (lsi). I'm not sure what I did to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There has been a lot of discussion on these two mailing lists about the upcoming EoL of FreeBSD 4.x which I mentioned in my email entitled "HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon". Now that everybody (hopefully) has had their say, I'd like to offer some background and explanation. The concept of "security branches"

I'm currently administering a machine about 1500mi from me with nobody local to the machine to assist me. Anyways, my only access to this machine is via SSH, no remote serial console or anything. When I try to do a "make installworld" I end up with install: rename: /lib/INS@aTxk to /lib/libcrypt.so.3: Operation not permitted very shortly thereafter. I cannot boot

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

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

I'm cvsupping 4.8-STABLE to 4.8-STABLE. The cvsup run finished about 23:32 on 7/13. After make buildworld, make buildkernel, mergemaster -p, make installworld, and mergemaster -v, I do (per mostgraveconcern, RIP): cd /usr/src/release/sysinstall make clean make all install The 'make all install' gives errors: In file included from keymap.c:40: keymap.h:4436: `keymap_be_iso'

The stack dump message is white text on black background. Right above the stack dump message, still in yellow-on-blue from the PXELINUX settings, is the text: Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader <change to white-on-black> BTX loader 1.00 BTX version is 1.01 <stack dump> Would that business of "arguments...