@Thomas Richter
what concerns fs-use, you can enable jit somewhere, which should leave you with a rather fast emulation, but i have mentioned it already, and i dont want to talk you out of using your a2k. on the other hand, when underway, an emulation comes in handy, when you want to contribute something on a quicker schedule.
It's a debian 8.3 64bit here, the jitter is not available. Concenring "not to code outside of my A2k" - that's not quite true. I'm just looking for better solutions, and I'm really working on better solutions and contributing to them.
I believe I posted this before, but I've invested quite some work into "vamos" and that *almost* works now as I'd like it to work.
The problem is not the emulation part. The problem is really the handling. I need an environment where I can switch quickly between the emulation and the native environment, an environment that I can script and that allows automated processing. The former for compilation and assembly, and the latter for all the software management around. I cannot conveniently do that with UAE (two different keymaps, mouse capture... this all breaks the "flow" if you get what I want to say, no scriptability, does not work over ssh...), but I can do that with vamos. I need an enviroment for development, not for gaming, and that's quite a different requirement.
"vamos" still has a couple of bugs unfortunately, but I really got a lot closer by spending my entire Christmas vacation on it. I've now a native Amiga shell, can write commands in there and *most* builds work. Unfortunately, AmigaOs does not yet build, but my vacation was over before I had the chance to find out more.