similar to: mergemaster fails when building temproot

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 in

Hi, give me some tips please, first of all, first screen: ============================================= *** The directory specified for the temporary root environment, /var/tmp/temproot, exists. This can be a security risk if untrusted users have access to the system. Use 'd' to delete the old /var/tmp/temproot and continue Use 't' to select a new temporary root

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, On an 8.2 box, I run freebsd-update -r 8.3-RELEASE upgrade I am getting hundreds of files with "conflicts" like: <<<<<<< current version # $FreeBSD: src/etc/auth.conf,v 1.6.32.1.4.1 2010/06/14 02:09:06 kensmith Exp $ ======= # $FreeBSD: src/etc/auth.conf,v 1.6.32.1.8.1 2012/03/03 06:15:13 kensmith Exp $ >>>>>>> 8.3-RELEASE ... which is

Yeah, I don't have luck with mergemaster, may be after another 100 times I run it I will educate myself to properly use it. So, would '-i' option help me to automate the process? Best Regards, Anton

running 9.1-STABLE r247548 updating to 9.1-STABLE r248381 When updating to the new version in a zfs beadm environment, mergemaster -D /mnt fails with install: illegal option -- l install (1) in the new version has an added -l switch which is used in bsd.own.mk which in turn is used by mergemaster. Making mergemaster use the new install(1) fixes the problem. John Theus TheUsGroup.com

-----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 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

Well, 4 days after previous upgrade i cvs'ed RELENG_4 from local cvs tree (updated hourly), made buildworld buildkernel installkernel, rebooted into single user, made installworld and mergemaster. Mergemaster updated newsyslog.conf, syslogd.conf, ok, rebooted... Wow... All scripts from /usr/local/etc/rc.d refused to load. And the system is in "Amnesiac" mode Attempt to run

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

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 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'

Hi, Maybe this message should go to mobile. Machine: IBM ThinkPad 600 (Model 2645-85U) PII-300, 64 RAM, 4GB HDD Network card: Xircom CE3B-100BTX (pcmcia) I've SUP yesterday (Sept 30) from cvsup12.freebsd.org , make world, mergemaster, MAKEDEV, updated /stand , rebooted, everyting seems to be ok but I'm getting an error related to the pcmcia network card. uname -a : FreeBSD

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

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 -

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

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

David gave me some suggestions to check out on the servers, but so far, its all drawing a blank ... I have two servers right now that are updated to recent 4.8-STABLE kernels ... one was June 22nd, and the other was upgraded June 20th ... both of them have crashed since that date, and both of them tell me that they are unable to produce a core file, with the same errors: Jun 26 04:27:14 jupiter

Currently I have a 'master' STABLE box which nfs exports src and obj to all my STABLE 'clients' and a 'master' CURRENT box nfs exporting src and obj to my CURRENT 'clients'. Would it be possible to eliminate one of the 'master' boxes ? IE, could a STABLE box build and host CURRENT (via alternate src and obj) or could CURRENT box build and host STABLE (via

hi all. it was happened that i have no upgrade my system long time. Before that i used for upgrading "classic" way. make buildworld make buildkernel make installkernel mergemaster make installworld But in current moment as i can see the upgrading is totally changed. As i understand commands sequence is next: #freebsd-update fetch #freebsd-update install #freebsd-update upgrade -r