How do you even judge that something is "encrypted" if you are using a scheme that some grad student made up like a month ago?
This is a problem that has already been solved. The answer is: You treat it like it's simply "security by obscurity" and assume it will be broken any day soon. The sad fact is that this is true for most of the encryption schemes thought up over the years.
And honestly, if homomorphic encryption can't work with a well tested and analyzed encryption algorithm, I'm not sure I'm very impressed about it..
You can generally not compress an encrypted stream of data.
Good encryption masks all the structure/redundancy from the data, which the compressor needs in order to remove useless bits.
So how much did the slashdot ad cost, and how do I block this kind of ads with adblock?
Did timothy and Zothecula share the cash equally?
Every file system is/should be labled "experimental" in a way. The long answer from the btrfs FAQ is pretty good, and makes some sense:
Long answer: Nobody is going to magically stick a label on the btrfs code and say "yes, this is now stable and bug-free". Different people have different concepts of stability: a home user who wants to keep their ripped CDs on it will have a different requirement for stability than a large financial institution running their trading system on it. If you are concerned about stability in commercial production use, you should test btrfs on a testbed system under production workloads to see if it will do what you want of it. In any case, you should join the mailing list (and hang out in IRC) and read through problem reports and follow them to their conclusion to give yourself a good idea of the types of issues that come up, and the degree to which they can be dealt with. Whatever you do, we recommend keeping good, tested, off-system (and off-site) backups.
Pretty much anything open source. If you're not allowed to see the source (skype, hardware disk encryption, proprietary encryption, windows built-in encryption) you can bet that FBI has a master key.
Doesn't mean it's safe just because it's open source, but broken or bogus encryption solutions which are open source are quickly found out.
Scrolling all that text without 2D accelerated hardware (not likely to be in place that early) likely adds more to the startup time than loading and displaying a graphical progress bar, especially considering how any drive will read far more than necessary for booting in one go, so the extra load time will be virtually zero.
That's been taken care of by modern file systems.
Also, do you apply security patches to your kernel on-the-fly somehow, or how come you don't have to reboot?
Lies.
The balloon program is just 16 lines, and expanding it to the full version as presented in the book it's just 25 lines.
"If I do not want others to quote me, I do not speak." -- Phil Wayne