I suspect your machine predates the ping/ping6 merge, and as a result you have different files, and subsequent upgrades and syspatch (basically tar extract) are skipping the 2nd one.
Peter J. Philipp <p...@centroid.eu> wrote: > I noticed that /sbin/ping and /sbin/ping6 were not hardlinked, on all > my computers (home and dedicated servers). How likely is it that the > signify keys have been compromised? I'm having a hard time with > OpenBSD these days, part of it is my clumsyness other parts are > pointing to a rootkit on my computers... > > 01:59 <@pbug44> syspatch never touched ping though, so how come > they're split? > 02:07 <@pbug44> I don't know about the 67 openbsd.. what am I missing? > 02:10 <@pbug44> beta# md5 ping > 02:10 <@pbug44> MD5 (ping) = 2409896ee1773f3e6006df0f4f2fb213 > 02:10 <@pbug44> beta# md5 /sbin/ping > 02:10 <@pbug44> MD5 (/sbin/ping) = f217ac5ed6aef55742e3b8c37453a342 > > I'm sick of reinstalling these, please provide a guide on what I > should do/look at to find reason why ping and ping6 are split in the > filesystem? Because in base67.tgz they should be hardlinked. > > With best regards (I'm going to have a hard time reinstalling > everything next week, likely but for how long will it stay unrooted?), > > -peter >
