While this is technically true, you are expressly forbidden from printing it or saving a local copy. Moreover, they are not made available in a format that is searchable or otherwise conducive to actually finding what you want.
In other words, if you want to actually use them without being constantly annoyed, you'll have to pay up.
The scheduling policies listed on the man page I linked share some generic kernel code, but I wouldn't classify them as the same scheduler. If you look inside the kernel/sched/ directory in the source, you'll find that an instance of `struct sched_class` is defined for each scheduler class. There are dl_sched_class, rt_sched_class, fair_sched_class, and idle_sched_class. You can see in `pick_next_task` in core.c that these class structs are iterated over, calling into each scheduler's own `pick_next_task`: http://elixir.free-electrons.com/linux/v4.13.9/source/kernel...
Many US banks support OFX (though they may call it QFX, DirectConnect, or simply advertise Quicken support). The OFX spec is a bit of a pain, but there are a number of open-source libraries to query/parse it. I wrote one in Go: https://github.com/aclindsa/ofxgo
I'm working on a web application for tracking personal finances (think GnuCash for the web or an open source mint.com). My main issue with GnuCash is that I can't enter transactions from anywhere (if I eat out, I have to keep the receipt until I get home instead of being able to enter it on my phone).
I'm currently sidetracked implementing a Golang library to request bank and investment transactions from financial institutions using OFX. Automatically pulling transactions from banks is important for any project like this and I couldn't find a suitable library in Golang (or really at all - most open source OFX parsers I could find only support parsing, not making requests, and don't support investment transactions).
In other words, if you want to actually use them without being constantly annoyed, you'll have to pay up.