From owner-freebsd-binup Wed Oct 23 7:56:14 2002 Delivered-To: freebsd-binup@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4061137B401; Wed, 23 Oct 2002 07:56:12 -0700 (PDT) Received: from aeimail.aei.ca (aeimail.aei.ca [206.123.6.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BEC643E6A; Wed, 23 Oct 2002 07:56:11 -0700 (PDT) (envelope-from anarcat@anarcat.ath.cx) Received: from shall.anarcat.ath.cx (cbe71qptg7jou2ah@dsl-130-203.aei.ca [66.36.130.203]) by aeimail.aei.ca (8.11.6/8.10.1) with ESMTP id g9NEtuS19179; Wed, 23 Oct 2002 10:55:56 -0400 (EDT) Received: from lenny.anarcat.ath.cx (lenny.anarcat.ath.cx [192.168.0.4]) by shall.anarcat.ath.cx (Postfix) with SMTP id A28D34E5; Wed, 23 Oct 2002 10:55:55 -0400 (EDT) Received: by lenny.anarcat.ath.cx (sSMTP sendmail emulation); Wed, 23 Oct 2002 10:55:24 -0400 Date: Wed, 23 Oct 2002 10:55:24 -0400 From: The Anarcat To: Gerardo Enrique Paredes Cc: Gerardo Enrique Paredes Mancia , freebsd-binup@freebsd.org, Murray Stokely Subject: Re: Fwd: Breaking up base (was: current state of the binup project) Message-ID: <20021023145524.GC321@lenny.anarcat.ath.cx> References: <200210230212.04522.g.paredes@unitec.edu> <20021023105216.GA28355@musiquera.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ctP54qlpMx3WjD+/" Content-Disposition: inline In-Reply-To: <20021023105216.GA28355@musiquera.com> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-binup@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ctP54qlpMx3WjD+/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [wrapping lines] On Wed Oct 23, 2002 at 03:52:16AM -0700, Gerardo Enrique Paredes wrote: > On Wed, Oct 23, 2002 at 02:12:04AM -0600, Gerardo Enrique Paredes Mancia = wrote: > >=20 > >=20 > > ---------- Forwarded Message ---------- > >=20 > > Subject: Breaking up base (was: current state of the binup project) > > Date: Tue, 22 Oct 2002 13:46:18 -0400 > > From: The Anarcat > > To: Murray Stokely > > Cc: GERARDO ENRIQUE PAREDES MANCIA ,=20 > > freebsd-binup@freebsd.org > >=20 > > On Sat Oct 19, 2002 at 10:54:17AM -0700, Murray Stokely wrote: > > [...] > >=20 > > > the same mechanism. We were not interested in changing the package > > > format, because other groups (i.e. libh / openpackages) are more > > > focussed on that. We were focussed on updates, delivery, and breaking > > > up the base system into discrete components. > >=20 > > Really? I've been dreaming about breaking up base for a long time > > now. Have binup started any work in this direction? > >=20 > > I have a "paper" I started writing that I've been thinking to send to > > -arch for a while now, should it be sent here instead? > > > Well, maybe i am wrong, but for doing a binary update everythin is > almost laid, at least that's how i am trying to make it, this is the > general approach i am gonna take: >=20 > - the client contact the server and ask to see if a profile is > available, let the profile be FreeBSD-4.7-RELEASE then asks for a > certain "distribution", let' the distribtuion be doc. > - The client now request the doc.aa, doc.ab, doc.?? chunks from the > server, the server get them from their location on disk and send > them to the client using sendfile(2) as Murray suggested. >=20 > - Happilly the client get the chunks then checksum them and follow a > silimar approach to install them (i.e: cat doc.?? | tar --unlink > -xpzf - -C ${DESTDIR:-/}) as the current sysintall binary update > procedure does. >=20 > As i said before, correct me if i am wrong but this an "It Works" > way of doing it , but i may be wrong about this is the way the > project wants to do it. Please correct me if i am wrong and expect > patches by the next week. Sure it works. The point is that this could be improved, but not necessarly on the binup side. The client/server protocol is interesting and should provide a powerful tool. But everything about the doc.* chunks and the client checksumming and installing them is not part of binup. It's part of the package system. My point is that binup should be package-system agnostic. I would have a directory of "packages" (whatever the format) associated with profiles, but wouldn't impose a file format. A. --=20 Stop the bombings. Stop the murders. Anti-war. --ctP54qlpMx3WjD+/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE9trhbttcWHAnWiGcRAkqGAJ9wCORF1y9MQQuEkjnIGxCCHIeTygCgkMOo qOXbr8xCTHjGZ16wVR88wUQ= =rCDF -----END PGP SIGNATURE----- --ctP54qlpMx3WjD+/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-binup" in the body of the message