From owner-freebsd-current Tue Apr 25 12:38:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 944EF37BDD5; Tue, 25 Apr 2000 12:38:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA11553; Tue, 25 Apr 2000 12:38:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 25 Apr 2000 12:38:39 -0700 (PDT) From: Kris Kennaway To: wc.bulte@chello.nl Cc: Richard Wackerbarth , freebsd-current@FreeBSD.ORG Subject: Re: Patchkits: Was :Re: SMP changes and breaking kld object module compatibility In-Reply-To: <20000425201600.A1134@yedi.wbnet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Apr 2000, Wilko Bulte wrote: > OK. But you do have to uniquely identify the binary that needs to be > patched. So, my question is when you generate 10x the same binary, will all > these 10 binaries have the same MD5 checksum? In other words: if people did > a local buildworld once on a -release sourcetree will all the executables > have the same MD5 as the ones on the -release cdrom? I don't think a binary patch is workable: all it takes is a single local buildworld and you've got an unpatchable system. Furthermore, I'd speculate that binary patches would usually be on the same order of size as the file itself. What *would* work is including the entire new file in the package. This is what solaris does. However, there are serious regression-testing and dependency problems with a scheme like this - i.e. making sure you've included *all* of the relevant changes. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message