-On [20040913 18:42], Matthew Dillon (dillon@apollo.backplane.com) wrote:
> That isn't necessarily meaningful, because GCC embeds a timestamp in the
> binary.
Which has nothing to do with the boot0/1/2 stuff, they don't get timestamped
by (g)as.
> You have to objdump -d the resulting binaries and compare the code rather
> then just do a binary compare of the binaries.
Why? You can just compare the boot2 resulting object files, it's not an ELF
binary. It doesn't even have sections objdump could dump from.
> In anycase, it sounds to me that you've munged your machine somehow and
> that a full buildworld/installworld and make upgrade is in order to try
> to clean it up.
Sorry, I didn't even *had* a system to boot from.
But that's ok, because I think you are confusing my issue with a bunch of
others, I'm sure you're swamped in email. :)
> If boot1 and boot2 are installed in the standard place, then it is
> sufficient to type 'disklabel -B ad0s2'. You do not need to specify
> -b and -s.
Given all the issues I wanted to be explicit in my testing.
--
Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
Free Tibet! http://www.savetibet.org/ | http://ashemedai.deviantart.com/
http://www.tendra.org/ | http://www.in-nomine.org/
Forgive us our debts, as we forgive our debtors...