From owner-freebsd-stable@FreeBSD.ORG Mon Jun 1 13:19:49 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 42A9F63B for ; Mon, 1 Jun 2015 13:19:49 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE1E1131A for ; Mon, 1 Jun 2015 13:19:48 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: by labpy14 with SMTP id py14so89465855lab.0 for ; Mon, 01 Jun 2015 06:19:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fuVeHkhhs2GBsu0ikK3EhsVNOorGT4nFuKS3vLum86U=; b=Cp/H+zH2REABu9cpqtS/1dZX+ctxdZL5704lV6l/tmWEB6/JENKymRPFKh+BbIH35l yQlJq70mOPgaDRKs0dv/Qv/tDA4WDQBQod9ZSmjvgjBJVgfWtoIQnCH4JaBzfyB/zRkv FMXNaDXCCgodxeL6ElLP54upvrSH8N2AJGOvVXc7NBBdio0QGrYSlH570JrdDVBGcQU3 6jmMuJjxURpG/o+mlXHxQP1Nxas6iKbDksL8wuyryuXBtqooExJQVhROIFLTnJZaOMWL T83Jr5513THUy+23w3v63vwDFLdzdHiMc9Nnivuu98jIyFppdahGnTUs8p7rnP/JuaSn ybgw== MIME-Version: 1.0 X-Received: by 10.152.203.162 with SMTP id kr2mr21049628lac.68.1433164786745; Mon, 01 Jun 2015 06:19:46 -0700 (PDT) Received: by 10.152.137.193 with HTTP; Mon, 1 Jun 2015 06:19:46 -0700 (PDT) In-Reply-To: <20150601131020.GC58397@zxy.spb.ru> References: <20150601131020.GC58397@zxy.spb.ru> Date: Mon, 1 Jun 2015 16:19:46 +0300 Message-ID: Subject: Re: How to track stable on multiple servers? From: Kimmo Paasiala To: Slawa Olhovchenkov Cc: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 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:19:49 -0000 On Mon, Jun 1, 2015 at 4:10 PM, Slawa Olhovchenkov wrote: > 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? When I had to something like this I went with option 3. It's not completely automated as you say because of /etc/(make|src).conf but there are no better options at the moment because /usr/obj is not "self contained" because its contents and interpretation depends on auxillary files, the /etc/make.conf and /etc/src.conf files. -Kimmo