Re: dpkg 220.127.116.11.1 bug
Carlos Carvalho <email@example.com> writes:
> What I don't understand is why it doesn't fail on x86/2.1.102. Does
> dpkg behave differently on x86?
No. Nor on m68k where it also works just fine..
> Maybe libc has been hacked for "compatibility" on x86 [ ... ]
No. From chown(2):
| In versions of Linux prior to 2.1.81 (and distinct from
| 2.1.46), chown did not follow symbolic links. Since Linux
| 2.1.81, chown does follow symbolic links, and there is a
| new system call lchown that does not follow symbolic
| links. Since Linux 2.1.86, this new call (that has the
| same semantics as the old chown) has got the same syscall
| number, and chown got the newly introduced number.
I'm still convinced that the alpha kernel is wrong for not doing what
the i386 & m68k kernels are doing.
~Yawn And Walk North~
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com