Yap. And according to the same CIA World factbook it exported... 61.7 billion kWh (2008 est.) - all in all a surplus of about 20 billion kWh.
https://www.cia.gov/library/publications/the-world-factbook/fields/2043.html?countryName=Germany&countryCode=gm&regionCode=eu&#gm

Just to disappoint you...

Germany has just shut down 8 of its 17 nuclear reactors. It still does not need to import energy (in the last years Germany exported a massive amount of energy to other countries). Before the shutdown, Germany produced about 20% of its energy from nuclear and abount 17% from renewable energy sources (see wikipedia)

After the shutdown, Germany probably produces more power from renewable as from nuclear energy...

Nope, they will not.

Since 2004 France (which has more than 40 nuclear reactors) has imported power from Germany, not the other way round.

Germany still has a (admittedly small) surplus, even after powering down 8 nuclear reactors at once. And the dependence on Germany on nuclear power is not very great -- Germany gets approximately the same amount of power from wind energy as from nuclear energy.

So, replacing the nuclear plats without depending on outside power imports is not impossible...

Well, no, it does not necessary.

Convergent encryption is a widely used technique, where a file is encrypted with it's hash value.
Thus identical files are always are encrypted with the identical key.

However yes - this breaks privacy for files which are saved by several users.

Or, if you want to wait for your vendor patch, set vm.mmap_min_addr manually, if it hasn't been set by your vendor already - the only distribution I have where this is necessary is debian.

You can either do
# sysctl -w vm.mmap_min_addr = 65536
and redo that every reboot or do

# echo "vm.mmap_min_addr = 65536" > /etc/sysctl.d/mmap_min_addr.conf
# /etc/init.d/procps restart
and be done with it.

It says that it was only fixed " in the upcoming 2.6.32 release candidate of the Linux kernel" - hence everything before that is vulnerable.

But the bug is not exploitable on ubuntu, because they set vm.mmap_min_addr > 0 by default.

Nope, it is a new one, but the same old bugfix still works.

Just type sysctl -w vm.mmap_min_addr=4096 in your box (or any other number > 0) and you are safe.