similar to: freebsd-update mergemaster options

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

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

Hello peoples, mergemaster fails saying freebsd.cf does not exist when building temproot. Have I missed something here? Thanks Michael Mercer cd /usr/src/etc/sendmail; make distribution install -C -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 /usr/src/etc/sendmail. ***

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

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

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

Hi All! I have the question, why reverted the ICH10 support from 7.1? This is the svn commit: http://svnweb.freebsd.org/viewvc/base/releng/?pathrev=186551 What is the PR number of the base of this commit or what is the problem description? I have a motherboard with ich10r with 3 sata2 disc (hitachi) + 1 sata dvd-rw (samsung), without any problem. Sorry for bad spelling or english

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

The first release candidate of the 9.1-RELEASE release cycle is now available on the FTP servers for amd64, i386, and powerpc64. The MD5/SHA256 checksums are at the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ (or any of the FreeBSD mirror sites). Current

I've built a domain member. It works pretty good with the exception that I want on-the-fly home directories being built. I'm not sure this is doable with a domain member as everything I've tried isn't even called - as far as I can tell. Using log level 3. If anyone can shed light on how to dynamically create home directories, that'd be great. anyway, here's my

Normally the FreeBSD Project tries very hard to avoid ABI breakage in "Stable Branches". However occasionally the fix for a bug can not be implemented without ABI breakage, and it is decided that the fix warrants the impact of the ABI breakage. We have one of those situations coming along for RELENG_7 (what will become FreeBSD 7.1). The ABI breakage should only impact kernel modules

Hello, I have been struggling for long with the above. The purpose behind attempting the same is to have a handsfree install from the first CD (bootable) including a customised kernel and application. There will be no user intervention required whatsoever during installation. In this regard this is what I am trying to do. At the end of a manual install of the above distro I can create a auto

Well folks I seem to have asked a purty dumb question with the above. But I still think I have to fill ya' ll in on how I solved it. You put the auto_inst.cfg file generated by the Mandriva/Mandrake installer in the root of the CD and in the isolinux.cfg file within the /isolinux directory point to the same by changing the append kickstart= line as follows append

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 -

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

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

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

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

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'