Re: Patchkits: Was :Re: SMP changes and breaking kld object module compatibility

2000-04-25 Thread Richard Wackerbarth

On Tue, 25 Apr 2000, Wilko Bulte wrote:

> 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?

If you are using someone's patches, you must be patching the files that they 
provided. If you have created your own "imposters", you cannot expect to 
patch them.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Patchkits: Was :Re: SMP changes and breaking kld object module compatibility

2000-04-25 Thread Garrett Wollman

< said:

> I love binary answers :-) Which brings me to my original point: it looks
> like you can only do binary patches relative to a -release. Unless
> you want to blindly patch and hope for the best. Rather unlikely.

I think you are right.  Doing so would still require resolving the
full dependency graph, so that programs affected by a library change
could all be identified.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED]  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Patchkits: Was :Re: SMP changes and breaking kld object module compatibility

2000-04-25 Thread Wilko Bulte

On Tue, Apr 25, 2000 at 02:50:46PM -0400, Garrett Wollman wrote:
> < said:
> 
> > 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?
> 
> No.

I love binary answers :-) Which brings me to my original point: it looks
like you can only do binary patches relative to a -release. Unless
you want to blindly patch and hope for the best. Rather unlikely.

-- 
Wilko Bulte Powered by FreeBSD  http://www.freebsd.org
http://www.tcja.nl


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Patchkits: Was :Re: SMP changes and breaking kld object module compatibility

2000-04-25 Thread Garrett Wollman

< said:

> 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?

No.

-GAWollman



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Patchkits: Was :Re: SMP changes and breaking kld object module compatibility

2000-04-25 Thread Wilko Bulte

On Tue, Apr 25, 2000 at 01:00:28PM -0500, Richard Wackerbarth wrote:
> On Tue, 25 Apr 2000, Wilko Bulte wrote:
> 
> > > On a similar note: I think one of serious drawbacks of FreeBSD's model
> > > for updating and bugfixing the stable branch is 'make world'. It's very
> > > inefficient and cumbersome way to do this on production machines. STABLE
> > > is stable enough for us to be able to prepare binary patches, which can
> > > be applied to a system in some (known) version. 
> 
> > Question: are MD5 checksums the same for each and every
> > build (assuming static sources obviously) or is there some timestamp (or
> > something like that) in the generated binary. If there is, one could only
> > create binary patches relative to a -release.
> 
> Here your logic is wrong. When I make a binary patch, I don't HAVE to update 
> anything that is not substantively changed. Think "make all" rather than 

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?

> "make world". From there, it is easy enough to generate a chain of patches 
> just like CTM does for the sources. 
> However, is it worth the effort? I don't know.

I assume it is worth it to some end-users. The question is if the project
can find someone to do it ;)
-- 
Wilko Bulte Powered by FreeBSD  http://www.freebsd.org
http://www.tcja.nl


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Patchkits: Was :Re: SMP changes and breaking kld object module compatibility

2000-04-25 Thread Richard Wackerbarth

On Tue, 25 Apr 2000, Wilko Bulte wrote:

> > On a similar note: I think one of serious drawbacks of FreeBSD's model
> > for updating and bugfixing the stable branch is 'make world'. It's very
> > inefficient and cumbersome way to do this on production machines. STABLE
> > is stable enough for us to be able to prepare binary patches, which can
> > be applied to a system in some (known) version. 

> Question: are MD5 checksums the same for each and every
> build (assuming static sources obviously) or is there some timestamp (or
> something like that) in the generated binary. If there is, one could only
> create binary patches relative to a -release.

Here your logic is wrong. When I make a binary patch, I don't HAVE to update 
anything that is not substantively changed. Think "make all" rather than 
"make world". From there, it is easy enough to generate a chain of patches 
just like CTM does for the sources. 
However, is it worth the effort? I don't know.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message