Oliver Falk <[EMAIL PROTECTED]> writes: > At Alphacore we used to patch the kernel headers for a while now; We > added syscalls __NR_openat (447) until __NR_tee (466). > > However, since 2.6.23 these syscall where added upstream, but with > different syscall numbers; What happens is the following: > > * glibc 2.6.90 compiled with 2.6.23 headers installed > * kernel 2.6.21 (our patched headers in place, different syscall > 'ordering'/numbers) installed > > [EMAIL PROTECTED] ~]# uname -r; touch x; rm -f x > 2.6.23-0.145.rc4.fc8 > rm: cannot remove `x': File exists > > :-( I don't want to live without rm :-P and chmod doesn't work as well...
It's all your own fault. Only mainline can assign syscall numbers. See it as a learning experience. Next time when you assign them you shouldn't use them before the patch has reached mainline. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
