2.6.16 for linuxulator & 7.0 release

[Divacky Roman]

> >I was talking about setting LD_ASSUME_KERNEL.. this DOES NOT work in  
> > our current
> >linuxulator and will BREAK things.
> >
> >the linux_use26() function works on the sysctl   
> >compat.linux.osrelease and doesnt care
> >about LD_ASSUME_KERNEL so kernel things its running 2.6 and userland  
> > thinks its running
> >2.4 -> things must break.
> 
> It depends on what is used. 2.6 in the kernel changes how some stuff  
> is handled. If LD_...=2.4.20 expect that the kernel behaves in those  
> areas like 2.6.16 and at the same times disallows the use of epoll()  
> and other stuff we don't want to be used, this would be an option. But  
> this depends upon how java determines how to use epoll() and upon the  
> expectations of glibc with LD_...=2.4.20. I didn't verified this but  
> it is easy to verify.
 
no.. this just wont work. this will break if you do this... the linux_use26
mainly mangles pids which are vital for threading. feel free to prove me
wrong but I am not going to waste a single second trying this :)

> A thought which just crossed my mind is: is an user able to panic the  
> kernel when 2.6.16 is in effect in the kernel and LD_... is set to  
> 2.4.x and vice versa?

highly unlikely approaching "definitely no"