Alexander Leidinger

Just another weblog

Jan
20

Lin­ux­u­la­tor in –cur­rent ready for test­ing the 2.6.16 emulation

Today I com­mit­ted two patches which fix the last two pan­ics we know about in the 2.6.16 emu­la­tion. Now we need testers. Here’s the text of the mail I did send to current@ a few moments ago:

Hi,

today I com­mit­ted the last fixes for the show­stop­per prob­lems (pan­ics) in the linux 2.6.16 emu­la­tion. I intend to switch the default ver­sion to 2.6.16 on i386 “soon” (see below), so please help test­ing it.

More recent linux dis­tri­b­u­tions (e.g. FC5) require a 2.6 ker­nel and don’t work with 2.4.2 any­more. And because FC4 is “abandon-ware” (no secu­rity fixes from fedo­rale­gacy any­more), get­ting 2.6.16 emu­la­tion up an run­ning is very important.

If you use a linux pro­gram, please add compat.linux.osrelease=2.6.16 to /etc/sysctl.conf (my desk­top is run­ning with 2.6.16 emu­la­tion since some days already). After the next boot (or after run­ning “sysctl compat.linux.osrelease=2.6.16″, please make sure no linux pro­gram is run­ning already) any linux pro­gram will start with a linux ker­nel ver­sion of 2.6.16 instead of 2.4.2. The default linux base port (FC4) will then use dif­fer­ent code paths (e.g. within glibc). In case you want to switch back to the 2.4.2 emu­la­tion with­out a reboot, please make sure no linux pro­gram is run­ning anymore.

So far we fixed all known/repeat­able prob­lems with acroread, realplayer, skype and linux fire­fox. If you encounter strange behav­ior with any linux pro­gram, please tell us (emulation@freebsd.org) which pro­gram you used, how to repeat the prob­lem, what the prob­lem is, and if it only is vis­i­ble with 2.6.16 or with 2.4.2 too. You should also watch out for mes­sages in the dmesg (unim­ple­mented sys­tem calls or other stuff, this is used to deter­mine the pri­or­ity of miss­ing syscalls). Please also have a look at http://wiki.FreeBSD.org/linux-kernel, I intend to doc­u­ment the known prob­lems there. If you find your prob­lem there, please tell us about it if you are will­ing to test fixes.

We are spe­cially inter­ested in reports (good or bad) on SMP sys­tems. Please beat the hell out of the lin­ux­u­la­tor!

On amd64 sys­tems we have not the same func­tion­al­ity as on i386, miss­ing are futexes and TLS. In P4 we already have the futex part cov­ered, but the TLS part is still miss­ing (any­one with a clue about the ker­nel side of TLS on amd64 is wel­come to give a hint or two to jkim@ and rdivacky@). So if you get a mes­sage about miss­ing futexes or TLS on amd64: we know about it (testers for the futex stuff are wel­come, but first you need to use a pro­gram which uses futexes and complains).

As long as we get prob­lem reports with 2.6.16 I will not switch the default to 2.6.16. If we don’t get a report at all, I will switch the default on i386 to 2.6.16 in two weeks. If we get some prob­lem reports, we will push back the switch a lit­tle bit depend­ing on the sever­ity of the problem.

Bye,
Alexander.

GD Star Rat­ing
load­ing…
GD Star Rat­ing
load­ing…
Share/Save

Tags: , , , , , , , , ,

One Response to “Lin­ux­u­la­tor in –cur­rent ready for test­ing the 2.6.16 emulation”

  1. Video for linux (v4l) emulation coming to the linuxulator « The Daily BSD Says:

    […] Lin­ux­u­la­tor in –cur­rent ready for test­ing the 2.6.16 emulation […]

Leave a Reply