In short, yes - it'd be difficult. Akaros is an OS, not just a
scheduler, so it's not so much that you'd be replacing a scheduler with
another scheduler, but that you'd be replacing an OS with another OS
(albeit one with different scheduling mechanisms).
I'd imagine that porting your app to Akaros would be the most difficult
part of it. For instance we don't have GTK+, since we're a datacenter
OS. Not sure if gsequencer can run via command line only... Even then,
our console support is pretty rough - we don't do curses or even
halfway decent console/screen stuff. We also don't have audio drivers.
All that being said, Kevin ported Akaros's user-level threading library
(Parlib) to Linux (https://github.com/klueska/parlib
) though the code
hasn't been touched in a number of years. So that might be useful if
you want to mess around with user-level threading.
Parlib is actually a lower-level library, and isn't an actual threading
library. An example one that you could use is upthreads
For more info, check out http://akaros.cs.berkeley.edu/parlib/
Maybe start there, actually.