The scandalous status of linux-flashplugin9

Alexander Leidinger Alexander at
Mon Oct 8 10:29:59 PDT 2007

Quoting John Reynolds <johnjen at> (Mon, 8 Oct 2007 08:10:11 -0700):

> [ On Monday, October 8, Scot Hetzel wrote: ]
> > The port is not broken as the flash9 port is not compiled, it just
> > installs the linux flash9 binary.  What is broken is the linux
> > emulation on FreeBSD < 7. Work is underway to improve the linux
> > emulation in -CURRENT.
> > 
> > I agree the port should be marked broken for OSVERSION < 7000xx, and
> > compat.linux.osrelease = 2.4.2, as the flash9 plugin may require
> > 2.6.16 linux emulation.
> Is there a handbook or wiki entry which would point one to the procedure for
> "properly" moving from 2.4.2 to 2.6.16 emulation under -current? I believe I
> saw some posts that 2.6.x would not be default for 7.0-RELEASE for whatever
> technical reason.....

% grep linux /etc/sysctl.conf

Be warned, you may run into bugs (2.6 emulation has not as much
widespread testing as 2.4). If you stumble upon problems have a look at
the archive of emulation@ and search for your problem there. If you can
not find it, tell emulation@ about your problem. Be prepared to do some
guided debugging.

> Can anybody report success on -current with 2.6.16 emulation with the flash9
> plugin? 

No, there are bugs we didn't manage to track down yet (partly because of
lack of time, partly because of the closed source nature of flash9,).
If someone wants to help to track this down: install dtrace (I don't
know where install instructions are; it's back from hibernation just
recently), run flash9 and try to get a backtrace of a crash with
dtrace. If someone manages to do this, post the backtrace to emulation at .


Violence in reality is quite different from theory.
		-- Spock, "The Cloud Minders", stardate 5818.4  Alexander @ PGP ID = B0063FE7     netchild @  : PGP ID = 72077137

More information about the freebsd-ports mailing list