Linuxu­lat­or pro­gress

This week­end I made some pro­gress in the linuxu­lat­or:

  • I MFCed the re­port­ing of some linux-​syscalls to 9–stable and 8-​stable.
  • I up­dated my linuxu­lat­or-dtrace patch to a re­cent -cur­rent. I already com­piled it on i386 and arundel@ has it com­piled on amd64. I coun­ted more than 500 new DTrace probes. Now that DTrace res­cans for SDT probes when a ker­nel mod­ule is loaded, there is no ker­nel pan­ic any­more when the linux mod­ule is loaded after the DTrace mod­ules and you want to use DTrace. I try to com­mit this at a morn­ing of a day where I can fix things dur­ing the day in case some prob­lems show up which I did not no­tice dur­ing my test­ing.
  • I cre­ated a PR for portmgr@ to re­po­copy a new linux_​base port.
  • I set the ex­pir­a­tion date of linux_​base-​fc4 (only used by 7.x and up­stream way past its EoL) and all de­pend­ent ports. It is set to the EoL of the last 7.x re­lease, which can not use a later linux_​base port. I also ad­ded a com­ment which ex­plains that the date is the EoL of the last 7.x re­lease.

v4l sup­port in the linuxu­lat­or MFCed to 8-​stable

I merged the v4l trans­la­tion lay­er in­to the linuxu­lat­or of 8–stable. As in -cur­rent, this just means that linux apps (like Skype) can now use FreeBSD nat­ive devices which con­form to the v4l ABI. The port multimedia/​webcamd provides ac­cess to some web­cams (or DVB hard­ware) via the v4l ABI.

People which want to test the linuxu­lat­or part should first make sure a nat­ive FreeBSD ap­plic­a­tion has no prob­lem ac­cess­ing the device.