On Wed, 2006-Aug-16 00:23:28 +0200, Alexander Leidinger wrote: >For the curious ones: the code is "activated" by changing osrelease, >because the glibc behaves differently depending on the osrelease. It >makes different syscalls based upon the linux kernel version. So if >there's a program which tries if a syscall does not return ENOSYS >instead of checking the osrelease, it may fail. If you are aware of >such a program, please tell us about it. I don't think this was mentioned before. IMHO, this is worth mentioning in the linuxolator documentation because it's not immediately obvious and it's likely to bite someone in a non- obvious way. -- Peter Jeremy
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:59 UTC