Progress in the lin­ux 2.6.x com­pat­i­bil­i­ty

Since my call for test­ing the extend­ed lin­ux­u­la­tor in FreeB­SD-cur­rent we got not much neg­a­tive respons­es. Ping does­n’t work on the lin­ux side (fixed in p4), ordi­nary 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. using emerge in a gentoo-chroot with MAKEFLAGS=-j4), this is being under inves­ti­ga­tion by Roman. Com­pil­ing stuff seri­al­ly on an UP sys­tem works just fine so far.

I’m won­der­ing if the lack of respons­es means that every­thing is run­ning just fine, or that nobody is giv­ing it a try. So far the dai­ly use of lin­ux pro­grams (acrore­ad, linux-firefox, …) with 2.6.16 com­pat­i­bil­i­ty seems to just work fine on UP and SMP sys­tems and cur­rent­ly I don’t see a rea­son to not switch the default 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­i­ty between i386/linux and amd64/linux32 soon.

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

Send to Kin­dle