From owner-freebsd-binup@FreeBSD.ORG Sat Jun 21 19:23:43 2003 Return-Path: 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 4715D37B401 for ; Sat, 21 Jun 2003 19:23:43 -0700 (PDT) Received: from protov.plain.co.nz (protov.plain.co.nz [202.36.174.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A94843F3F for ; Sat, 21 Jun 2003 19:23:41 -0700 (PDT) (envelope-from zombie@i4free.co.nz) Received: from i4free.co.nz (ppp65180.cyberxpress.co.nz [202.49.65.180]) by protov.plain.co.nz (Postfix) with ESMTP id 6F1BE3D02E for ; Sun, 22 Jun 2003 14:23:24 +1200 (NZST) Message-ID: <3EF512DF.10602@i4free.co.nz> Date: Sun, 22 Jun 2003 14:22:23 +1200 From: Andrew Turner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-binup@freebsd.org Content-Type: multipart/mixed; boundary="------------080603030600070109040309" Subject: Protocol & package independent draft X-BeenThere: freebsd-binup@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Design and development of the binary update system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2003 02:23:43 -0000 This is a multi-part message in MIME format. --------------080603030600070109040309 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I have been writing a design for binup to become protocol an package independent. This document dosn't specify how to build the packages or how to install the packages. This is the first draft and I would like feedback. With this draft the client is responsible to select the packages on the server to fetch then install them on it's own. Andrew -- There are 10 types of people in this world. Those who understand binary and those who dont. AlanH --------------080603030600070109040309 Content-Type: text/plain; name="binup-draft-1.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="binup-draft-1.txt" Package and Protocol independent binary update system. Abstract This document will look at a proposed system to update remote computers in a network protocol and binary package independent way. This document will only discuss getting the packages onto the client computer in a way the install script can predict. Status This is the first draft. All input will be considered. Definitions Client - The computer being updated Configuration - A named list of packages to install on a computer. Package - A file containing one or more files that can be read with the correct software Server - The computer the client connects to to get the updates Update - A binary package the client installs on the client. Problem When computers are distributed updating them can be problematic. Updating many computers takes time if it is not automated. Solution The server will have zero or more text files listing configurations in the root package directory. Each configuration will be listed in the master configurations file. The layout of the configurations file will be described in the final version of this document. The server also contains a file with its last update date. Each package will have a description contained within them. The client will have a list of known servers. The client follows this process: 1. The client connects to one at random. 2. It checks the updates are later then its local version. 3. If the computer was setup using a configuration file it will download the appropriate configuration. Otherwise go down to 4b. 4a. Download all the packages from the configuration file. 4b. Download all the packages in the local installed package list. 5. Run the package install script. The packages directory structure will be as follows: Note. all names in <> are variables. - The top of the package directorys, dosn't have to be the server root. /config.list - A list of the configurations on the server (only if the server contains configurations). /all - All packages on the server are stored here. /all/. - The package. /all/.sum - One or more checksums of the package, includes the version. /all/list - A list of all packages and a short (up to 72 characters) description. / - Packages and checksums only used in the configuration are linked here (only if the server contains configurations). //. - The package in the configuration. //.sum - The packages checksums. //list - A list of packages in the configuration. Only the /all/ directory and all files in it listed above are required. Author: Andrew Turner - zombie (at) i4free.co.nz --------------080603030600070109040309-- From owner-freebsd-binup@FreeBSD.ORG Sat Jun 21 20:19:06 2003 Return-Path: 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 DCA8837B401 for ; Sat, 21 Jun 2003 20:19:06 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-104-32.dsl.lsan03.pacbell.net [64.169.104.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7736C43F93 for ; Sat, 21 Jun 2003 20:19:01 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id B0B9A66CFB; Sat, 21 Jun 2003 20:18:49 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id A82218D4; Sat, 21 Jun 2003 20:18:48 -0700 (PDT) Date: Sat, 21 Jun 2003 20:18:48 -0700 From: Kris Kennaway To: Andrew Turner Message-ID: <20030622031848.GC89485@rot13.obsecurity.org> References: <3EF512DF.10602@i4free.co.nz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GZVR6ND4mMseVXL/" Content-Disposition: inline In-Reply-To: <3EF512DF.10602@i4free.co.nz> User-Agent: Mutt/1.4.1i cc: freebsd-binup@freebsd.org Subject: Re: Protocol & package independent draft X-BeenThere: freebsd-binup@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Design and development of the binary update system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2003 03:19:07 -0000 --GZVR6ND4mMseVXL/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 22, 2003 at 02:22:23PM +1200, Andrew Turner wrote: > I have been writing a design for binup to become protocol an package=20 > independent. This document dosn't specify how to build the packages or= =20 > how to install the packages. >=20 > This is the first draft and I would like feedback. >=20 > With this draft the client is responsible to select the packages on the= =20 > server to fetch then install them on it's own. IMO, what we need is working code, not more drafts that get bikeshedded around for a bit but then never get implemented. Kris --GZVR6ND4mMseVXL/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+9SAXWry0BWjoQKURAq7SAJ0Z1UP3gxpuxaCtweWuXQ1lZ6tb9wCff8yt 5XScdMk4NpdGHwHZN5dPeWg= =Is8G -----END PGP SIGNATURE----- --GZVR6ND4mMseVXL/--