I created a raid-Z zpool in 2010 on FreeBSD and those same bits, with two different drives, are still floating around intact 6 years later, across multiple different operating systems.
Absurdly high taxes (my parents pay half my tax on a non-rural property twice as big about 120 miles north of me), but still, owning a home is hardly a fiscally ruinous proposition around here.
My property taxes this year were ~$4200 on an average sized lot and home, or roughly $350/month.
My last apartment cost $1050/month for a small two bedroom condo rental.
Well, in some areas, but it really depends on the market - the property taxes on my home in a University city of 200,000 are 1/3 of what I was paying in rent - with the interest on my mortgage the amount of "lost" money comes out to roughly the same amount for now.
As long as property taxes do not outstrip my interest rate, that ratio should stay in my favor going forward.
The /proc/kallsyms values are identical across identical kernel compilations.
Suppose you have a vulnerable CentOS 7 system that you want to exploit - you could get the proper addresses from your own CentOS 7 VM running the same kernel, apply those to a modified exploit compilation, and run that compilation on your target host.
The "postcard -> unencrypted email as letter-in-envelope -> encrypted email" seems to be a very good analogy for explaining the need for encryption to laypeople.
The technicals are trickier (and outside my scope of expertise), but the "why do I need to use this" answer is one of the trickiest and most important questions to answer for any security application.
I'd love to expand this concept and do full window manager integration with tmux/screen, actually.
I can't see any problems with having a bottom-tabbed UI with nice tmux keybindings - "C-a 0" to go over to Chrome, quick split of current X view with "C-a %', etc would be phenomenal.
Does anyone know if this exists in some form already?