From owner-freebsd-pkgbase@freebsd.org Tue Apr 30 03:25:34 2019 Return-Path: Delivered-To: freebsd-pkgbase@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 913821581301 for ; Tue, 30 Apr 2019 03:25:33 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: from mail-yw1-xc2c.google.com (mail-yw1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F32B589CA1 for ; Tue, 30 Apr 2019 03:25:31 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: by mail-yw1-xc2c.google.com with SMTP id g29so4888640ywk.3 for ; Mon, 29 Apr 2019 20:25:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=r3wt8Ka/gEpopTKdVO1uzaTJ3ZVQ0NgugE/qUmB/P2Q=; b=rRSqKR+0qijZ3IlBE18+HTrdFNiMe28f5hgMTxq+pNb7qMVRNtloLxlWkTQtAci1BY dafQpSHxB4aA73cnMeZA2Kv8K2GV5aBileT+eoRvKHw/qrhyuHNZXHsipDMYh/fywEtg x/iRXz5Mv+URl/YJfSv5qHBxT5wj2iBgd+5Yr6JleI3FJfsgfju56jXST5IDV1xT27sm Nzf6Jiw9dbJ7K2gwSM23mUdw5Aqp4+FuPQg5nCivxVycQq+eYQyPpwxwQ6KjzDevsgXS PZZXynrvrFIrW2Dc4E0C3NG28f8ic20UUpZV1CrRenmrWmSntjNB/PIcb7xjKzDx3azs nuhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=r3wt8Ka/gEpopTKdVO1uzaTJ3ZVQ0NgugE/qUmB/P2Q=; b=WMsT/VcJwWPEKBPIdf2HzLPShLAIrGOs6yU0wSRzhayj1aIPYCDjHSRpz8weLQLg/B j9cctkSXN8RUWkjDpIbO1olIJ6LaTM14g+7Yqda6Vz9mNRo44wogSlzQ23KFUi8cJG1T 1Mf4emwEYlC2Z49sq8YvXn4Jg/jHu/KlVep4yeaA8UJ+f5a8obLxtkfobQd+hsyW+DQA b5A2bH8mWu83cPpFDykS5bDR21ju4NwCBEVNeEXBsrU9IwY/ktx8b3glBNRbpjPr/ORF idMnnFS341C141KsomQhe9lzWNMIXjoDBlWBuez7pPLfG23f/6dOWp/VlJJ4hzGs2Tn2 DiCQ== X-Gm-Message-State: APjAAAVbi1iu/Z5r7pvgJosrA9PNFDFwW7krGZBtHiyP2i7eGEKwzM51 vJqUy37SXN8i4Va3+I0FI3EzETRjWvRVXA== X-Google-Smtp-Source: APXvYqxcZnS7tUA/KLUnDk5BKyNTad+Tr/sLu4Pi2k8aN/EYaIqpfFXSNEFw8alDQ/UzOuDwRu50zA== X-Received: by 2002:a25:d9cd:: with SMTP id q196mr54909899ybg.410.1556594731224; Mon, 29 Apr 2019 20:25:31 -0700 (PDT) Received: from [192.168.1.97] (71-136-149-239.lightspeed.knvltn.sbcglobal.net. [71.136.149.239]) by smtp.gmail.com with ESMTPSA id a80sm6548611ywe.78.2019.04.29.20.25.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Apr 2019 20:25:30 -0700 (PDT) From: Joe Maloney Message-Id: Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Subject: Re: CFT: FreeBSD Package Base Date: Mon, 29 Apr 2019 23:25:28 -0400 In-Reply-To: <201904300241.x3U2femm075775@gndrsh.dnsmgr.net> Cc: Cy Schubert , freebsd-pkgbase@freebsd.org To: "Rodney W. Grimes" References: <201904300241.x3U2femm075775@gndrsh.dnsmgr.net> X-Mailer: Apple Mail (2.3445.104.8) X-Rspamd-Queue-Id: F32B589CA1 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ixsystems-com.20150623.gappssmtp.com header.s=20150623 header.b=rRSqKR+0; dmarc=pass (policy=none) header.from=ixsystems.com; spf=pass (mx1.freebsd.org: domain of jmaloney@ixsystems.com designates 2607:f8b0:4864:20::c2c as permitted sender) smtp.mailfrom=jmaloney@ixsystems.com X-Spamd-Result: default: False [-6.48 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[ixsystems-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-pkgbase@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: ALT3.ASPMX.L.GOOGLE.com]; DKIM_TRACE(0.00)[ixsystems-com.20150623.gappssmtp.com:+]; DMARC_POLICY_ALLOW(-0.50)[ixsystems.com,none]; RCVD_IN_DNSWL_NONE(0.00)[c.2.c.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-3.00)[ip: (-9.54), ipnet: 2607:f8b0::/32(-3.16), asn: 15169(-2.24), country: US(-0.06)]; NEURAL_HAM_SHORT(-0.96)[-0.964,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2019 03:25:34 -0000 What you describe is the sysup tool for managing updates with boot = environments which is not part of the CFT ISO. The pkg upgrade command = is used to update the base packages. Sysup is not necessary unless you = want a wrapper to create boot environments. =20 Having said that I cannot describe the problems I=E2=80=99ve had for = several years with FreeBSD=E2=80=99s pkg base without muddying the = waters with this CFT. So I sort of agree it should be called =E2=80=9Cpla= nned pkg-base=E2=80=9D, or =E2=80=9Cactually has a chance at being = integratabtle pkg-base=E2=80=9D. Try the ISO I think you will like it. Joe Maloney Quality Engineering Manager / iXsystems Enterprise Storage & Servers Driven By Open Source > On Apr 29, 2019, at 10:41 PM, Rodney W. Grimes = wrote: >=20 >> On April 29, 2019 1:50:00 PM PDT, Garrett Wollman = wrote: >>> <>> said: >>>=20 >>>> The discussion about granularity begs the question, why pkgbase in >>> the=20 >>>> first place? My impression was that it allowed people to select = which >>>=20 >>>> components they wanted to either create a lean installation or mix >>> and=20 >>>> match base packages and ports (possibly with flavours to install in=20= >>>> /usr rather than $LOCALBASE) such that maybe person A wanted a = stock=20 >>>> install while person B wanted to replace, picking a random example, >>> BSD=20 >>>> tar with GNU tar. Isn't that the real advantage of pkgbase? >>>=20 >>> No. The "real" advantage of pkgbase is that it allows the = distributor >>> of a customized version of the operating system to support = binary-only >>> updates, without all the (non-trivial) infrastructure of running a >>> custom FreeBSD-update builder and distribution server. >>>=20 >>> Consider my position: I have about 30 servers (and another ~10 = jails) >>> that all run the same local build of FreeBSD. Right now, the only >>> reliable way to update them is to NFS-mount /usr/src and /usr/obj = from >>> my build server, and run a (slow) "make installworld". It would >>> literally save me hours out of every upgrade (or base-system = security >>> fix) to be able to install compressed binary packages downloaded = over >>> http, and I'd have better security because binary packages are >>> signed. >>>=20 >>> For my use case, I don't much care what the granularity is, so long = as >>> I can safely upgrade (or update) the kernel independently of the >>> userland and independently of third-party packages -- just two >>> packages (kernel and userland) would suffice, although I'd probably >>> prefer the runtime libraries to be in a separate package just for >>> safety. >>>=20 >>> I'm not distributing packages to third parties, I just want to be = able >>> to install and upgrade my packages on my fleet of servers and jails >>> quickly and safely. This is not the entirety of the use cases the >>> project as a whole needs to support, but it's a major *end-user* use >>> case. (And I've said as much in various surveys.) >>>=20 >>> -GAWollman >>=20 >> An anaconda-like installer for freebsd could do that. Also a perfect = job for cfengine or ansible. Deploy and use a playbook to enforce = policy. >=20 > https://anaconda-installer.readthedocs.io/en/latest/ = >=20 >> You don't need to break up base into packages (not arguing against = packaging) to gain the benefits of configuration management. >>=20 >> As for updating, freebsd-update is mostly there to accomplish your = requirement without pkgbase. Which begs the question, if we're simply = replacing freebsd-update and it does most of what we want why the extra = effort? Unless we want to solve more than just this problem? Which BTW I = think we do. >>=20 >> I've seen pkgbase as a building block to build an anaconda-like = installer complete with scripting language. The ability to pick and = choose packages as many Linux distros do is one part of it. >=20 > What seems to be confusing here is that TrueOS/FreeNAS's > "package base" and the work that has been on going IN > the FreeBSD base system for 2+ (3?) years are 2=20 > different things with different goal sets and this > CFT has very much muddied that water as to what is > what. >=20 > Is there an advocation by iXsystems and TrueOS to replace > what is in the base system now with this new Go implementation > in ports? >=20 > Are they orthagonal? If so can we please rename one? >=20 >=20 > --=20 > Rod Grimes = rgrimes@freebsd.org > _______________________________________________ > freebsd-pkgbase@freebsd.org = mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-pkgbase = > To unsubscribe, send any mail to = "freebsd-pkgbase-unsubscribe@freebsd.org = "