Dunstabzugshaubitze

sometimes i like that a lot of my work is typical enterprise stuff. nothing gets to prod without some poor soul working through a huge test catalogue on a seperate environment and/or a higher up signs off on it.

it's also annoying because, you cant "just ship" a small fix or change without someone signing off on it.

And no, I have not tested it because I don't know how I'm actually supposed to do that.

depends on what you backup and how.

if it's just "dumb" files (videos, music pictures etc.), just retrieve them from your backups and check if you can open the files.

complex stuff? probably try to rebuild the complex stuff from a backup and check if it works as expected and is in the state you expect it to be in. how to do that really depends on the complex stuff.

i'd guess for most people it's enough to make sure to backup dumb files and configurations, so they can rebuild their stuff rather than being able to restore a complex system in exactly the same state it was in before bad things happened.

so is dracut and weston.

i think that naming software after towns in Massachusetts is somekind of red hat in-joke.

technicaly correct, and i am no lawyer, but i can't see how in the world i owe anyone a warranty that loads code on their machines, compiles it and uses it, all without any input by me.

everything that i intend to be more than throw away code, that lives for whatever reason in a public repo gets either an MIT or an gplv3 license.

nah, than ibm will annoy you, that they need a special license that allows them to be a dick while using your code.

just like they asked the JSLint guys to use JSLint for evil.

code that needs a license, but i really don't care what you do with it gets a wftpl.

http://learnyouahaskell.com/

Good book.