On 06/01/2010 05:32 AM, Philip Guenther wrote:
Was there a common thread to what did turn up? My recall is that
basically every time people get "Operation not supported by device"
errors from pfctl, it's because their userland and kernel don't match.
Review your upgrade procedure, because it's clearly broken.
Thanks for your help, seriously. And I don't want to start arguing, not
at all, but this is one of my production boxes, without access, and I
have been running the boot.bsd.rd updates since 3.8 twice a year.
Being production, I diligently watched, and saw with my own eyes the
asterisks advancing. I can only say, I followed standard procedures; if
just for my own sanity.
I *am* losing the latter, because it seems that all files in /sbin are
identical to my box still on 4.6; though something has happened to them
yesterday:
(this is my 4.6-box, upgraded only on April 19th:)
$ ls -l /sbin/p*
-r-xr-xr-x 1 root bin 492664 Apr 19 13:44 /sbin/pfctl
-r-xr-xr-x 1 root bin 390264 Apr 19 13:44 /sbin/pflogd
-r-sr-xr-x 1 root bin 210040 Apr 19 13:44 /sbin/ping
-r-sr-xr-x 1 root bin 234616 Apr 19 13:44 /sbin/ping6
(This is my box upgraded yesterday, May 31st, to 4.7:)
# ls -l /sbin/p*
-r-xr-xr-x 1 root bin 492664 May 31 20:28 /sbin/pfctl
-r-xr-xr-x 1 root bin 390264 May 31 20:28 /sbin/pflogd
-r-sr-xr-x 1 root bin 210040 May 31 20:28 /sbin/ping
-r-sr-xr-x 1 root bin 234616 May 31 20:28 /sbin/ping6
So it did something, from where did it get the old files? I guess not
from a mistake on my side, because I accepted the upgrade path in the
Upgrade shell. Plus:
OpenBSD 4.7 (GENERIC.MP) #130: Wed Mar 17 20:48:50 MDT 2010
[email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
I never copied any myself down here. As I mentioned, production, upgrade
twice per year through serial console.
And now my sanity seems to fade: I did the same to one of my i386-boxen,
and exactly the same happens there!! (Please, now I am starting to lose
ground under my feet!)
This is after the update to 4.7, i386, in front of the screen!:
(mnt is /altroot, mounted just now to check; since pfctl did the same
thing, again, here)
# ls -l /mnt/sbin/p*
-r-xr-xr-x 1 root bin 422648 Apr 19 12:51 /mnt/sbin/pfctl
-r-xr-xr-x 1 root bin 328440 Apr 19 12:51 /mnt/sbin/pflogd
-r-sr-xr-x 1 root bin 180984 Apr 19 12:51 /mnt/sbin/ping
-r-sr-xr-x 1 root bin 197368 Apr 19 12:51 /mnt/sbin/ping6
# ls -l /sbin/p*
-r-xr-xr-x 1 root bin 422648 Jun 1 12:54 /sbin/pfctl
-r-xr-xr-x 1 root bin 328440 Jun 1 12:54 /sbin/pflogd
-r-sr-xr-x 1 root bin 180984 Jun 1 12:54 /sbin/ping
-r-sr-xr-x 1 root bin 197368 Jun 1 12:54 /sbin/ping6
A mix-up of versions? I don't think so, because
$ tar xzf /home/ftp/pub/OpenBSD/4.7/amd64/base47.tgz ./sbin/pfctl
$ md5 sbin/pfctl
MD5 (sbin/pfctl) = 7720c9a4dc100fe29d2d3c4a16954eb4
exactly what you had.
Now I start to not exclude a bug any longer. Maybe under some
circumstances, the files are not overwritten, but touched; or whatnot.?
This leaves me with two questions:
1. How to debug what goes on?
2. (and more important for me): What to do? Should I tar xzvphf
{file}47.tgz; or try an new upgrade?
Uwe
