The RCS info stored in the binaries is insufficient for this purpose. There is no record of the versions of all included files. Changes to constants and/or macros would not be identifiable. Jim Bloom [EMAIL PROTECTED] Kris Kennaway wrote: > > On Tue, 25 Apr 2000, Brandon D. Valentine wrote: > > > The only way something like this is feasible is if the binaries > > themselves contain information about what version they are. In other > > words some sort of a header in the binary which contains the RCS version > > number the binary was compiled from so that whatever method you were > > You've never run ident(1), right? :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: Patchkits: Was :Re: SMP... Wilko Bulte
- Re: Patchkits: Was :Re: SMP... Garrett Wollman
- Re: Patchkits: Was :Re: SMP... Wilko Bulte
- Re: Patchkits: Was :Re: SMP... Garrett Wollman
- Re: Patchkits: Was :Re: SMP... Richard Wackerbarth
- Re: Patchkits: Was :Re: SMP... Kris Kennaway
- Re: Patchkits Richard Wackerbarth
- Re: Patchkits: Was :Re: SMP... Brandon D. Valentine
- Re: Patchkits: Was :Re: SMP... Kris Kennaway
- Re: Patchkits: Was :Re: SMP... Brandon D. Valentine
- Re: Patchkits: Was :Re: SMP... Jim Bloom
- Re: Patchkits: Was :Re: SMP... Andrzej Bialecki
- Re: SMP changes and breaking kld obj... Daniel O'Connor
- Re: SMP changes and breaking kl... Andrzej Bialecki
- Re: SMP changes and breakin... Daniel O'Connor
- Re: SMP changes and breakin... David Malone
- Re: SMP changes and breakin... Jesper Skriver
- Re: SMP changes and breaking kld object module compat... Steve Passe
- Re: SMP changes and breaking kld object module c... Matthew Dillon
- Re: SMP changes and breaking kld object modu... Jonathan M. Bresler
- Re: SMP changes and breaking kld object ... Matthew Dillon