Pro­gress in the linux 2.6.x com­pat­ib­il­ity

Since my call for test­ing the ex­ten­ded linuxu­lat­or in FreeBSD–cur­rent we got not much neg­at­ive re­sponses. Ping doesn’t work on the linux side (fixed in p4), or­din­ary net­work con­nec­tions (e.g. down­load­ing some stuff) works fine. There seems to be a dead­lock on SMP sys­tems when com­pil­ing a lot of stuff in par­al­lel (e.g. us­ing emerge in a gentoo–ch­root with MAKEFLAGS=-j4), this is be­ing un­der in­vest­ig­a­tion by Ro­man. Com­pil­ing stuff seri­ally on an UP sys­tem works just fine so far.

I’m won­der­ing if the lack of re­sponses means that everything is run­ning just fine, or that nobody is giv­ing it a try. So far the daily use of linux pro­grams (acror­ead, linux-​firefox, …) with 2.6.16 com­pat­ib­il­ity seems to just work fine on UP and SMP sys­tems and cur­rently I don’t see a reas­on to not switch the de­fault in i386 in a week.

Jung-​uk Kim is work­ing on the linux-​TLS on amd64 part. ATM he is chas­ing bugs. It looks we can get fea­ture par­ity between i386/​linux and amd64/​linux32 soon.

In­tron did send in a patch for the linux-​aio stuff. Now I just need to get time to have a look at it.