I was actually reading this and though well OP is fine, but then I didnt post that because I was not sure what OP actually wants to do.
For generating keys thats fine, but an offline wallet would also sign transactions. So the "Transaction malleability-related fixes" might be an issue. Esp. the tightening of "IsStandard()" might result in transactions that are not broadcasted across the network.
Yeah, I couldn't be sure that I fully understood all the implications of the 0.9.0 version changes. It appears that I in deed didn't. The "IsStandard()" thing could be problematic.
How do you get it to run?
Did you make the file executable? (RClick in GUI -> Properties -> check "allow execution as programm")
Yeah, I tried that. Doesn't work whether I double click, or enter 'bitcoin-qt' or 'bash bitcoin-qt' in terminal. It's kind of ridiculous that the feature to run the client easily was removed for 0.9.1 ... I actually went through many other steps from a thread here a while ago, but it didn't help. Sorry, can't recall the thread, and don't have time to 'develop' a fix.
So does anyone know enough about the fine details of the client updates to know whether I'm actually safe to do what I described with 0.8.6?
Not sure if this would help.
Have you tried chmod +x bitcoin-qt then ./bitcoin-qt.
The first command will set bitcoin-qt to be executable then ./bitcoin-qt will try to run it.
Yes! I had tried chmod +x bitcoin-qt, but had then entered bitcoin-qt. Entering ./bitcoin-qt got it. Thanks.
One of these days I'll get round to learning linux properly...