From owner-freebsd-stable@FreeBSD.ORG Mon Jun 1 13:10:24 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0B6E1DC for ; Mon, 1 Jun 2015 13:10:24 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BA22710BC for ; Mon, 1 Jun 2015 13:10:23 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YzPTw-0002Kf-80 for freebsd-stable@freebsd.org; Mon, 01 Jun 2015 16:10:20 +0300 Date: Mon, 1 Jun 2015 16:10:20 +0300 From: Slawa Olhovchenkov To: freebsd-stable@freebsd.org Subject: How to track stable on multiple servers? Message-ID: <20150601131020.GC58397@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2015 13:10:24 -0000 I have some set of FreeBSD servers in public internet and continue to find optimal way for track -stable branch. Handbook give next metods: 1. Tracking -security branch by freebsd-update. I want -stable, -security don't have wanted features. 2. svn & rebuilding world localy. To long and wery badly automated, bad version synchronisation between servers. 3. svn & rebuilding world on build server, install localy by NFS. Servers in public internet, I am to be afraid exposing NFS to public internet. Also, need to have localy /etc/{make,src}.conf in sync with build server. Also badly automated. 4. Build private freebsd-update-server and build (simularity to security btanch) updates for -stable. Need essentially dedicated server -- during build system time changed and this is may be raise side effects. freebsd-update work wery long time (hours) and accumulate a lot of garbage: # du -ms /var/db/freebsd-update/ 2010 /var/db/freebsd-update/ freebsd-update-server/freebsd-update too bugly and debuggint is not easy. config mergering working worse mergemaster. Don't allow to repair damaged files (freebsd-update IDS detect changes but don't repair this). 5. nanobsd. Don't automatic save /etc and etc. pkg updated throw system image update and reboot. Unaccpetable. Something else?