This is going to be a real challenge to people want to build new renewable sources. Would you want to build a solar plant if it produces energy at a time that you can't sell it, and produces little at times when the prices are highest. (Nice if you want to sell storage systems though).
It is say that *if* we do nothing to reduce fossil fuel use and continue to emit as we do today, what is likely to happen. Its not predicting that we do nothing. The best guess is that at least some countries keep the Paris pledge and reduce emissions. But, if everyone decided that they could not be bothered to make the changes required, then we can expect significant warming.
" In the absence of global mitigation actions, five trillion tonnes of carbon (5 EgC), corresponding to the lower end of the range of estimates of the total fossil fuel resource"
i.e. assuming we take no action and keep burning fossil fuels at the current rates. From the time scales talked about on the first page, it looks like they assume burning it over the next couple of hundred years. Maybe some one want to give the full article a read?
X forwarding still just works if you are running wayland locally. behind the scenes its using xwayland, but from the user point of view nothing has changed.
I am sure there will be a more waylandy solution before the tool kits drop their X support (which probably wont happen for decades).
Why do you need the closed nvidia driver on a server? Nouveau should be fine or even just the vesa driver.
(I could say why do you even need a video card on a server, but I guess some folk prefer that to using ssh or a serial connection from a laptop)
I am using BTRFS on luks on my laptop. Even during a motherboard failure that cause repeated hard poweroffs I did not loose any data (and thanks to data checksumming I know that there is no corruption lurking in the files).
BTRFS has developers at Facebook, Fujitsu, SUSE, IBM and still gets patches from people at Oracle. Seems a fairly healthy project to me.
GPL gives the best chance that in the long term there will be multi vendor support. So in 20 years time I'll still be able to read my data, and no one can hold it hostage with crazy licence fees. Sure other open source licences are pretty close, but if the main sponsor behind a project goes closed, then it can sometimes take the community with it. Who knows if in the next 20 years Oracle will do a SCO and try suing anyone who uses their tech in a way that does not generate profit for them.
Maybe some static analysis tool recently gained a feature that finds it. Maybe some conference talk mentioned some new method that helped find it. Maybe they were both aware of someone using this exploit.
"ssh -X" already works fine on wayland. Install Fedora 23, start a wayland session and try it. (Ok, it starts up an xwayland server underneath, but from a user point of view it works indistinguishably)
"ssh -X" works fine on wayland. Install Fedora 23, start a wayland session and try it. (Ok, it starts up an xwayland server underneath, but from a user point of view it works indistinguishably)
Sorry I was not clear enough. The kernel value for max number of cores must be a power of 2. So to use that triple-core CPU the kernel would actually need to support up to 4 cores. So if AMD plans to release a 20-core, they can't just bump the number in the kernel to 20, they have to increase it to 32.
If the previous max cores per socket was 16, and the value in the kernel needs to be a power of 2, then at most this tells us that they have a 17 (more likely 18 or 20) core CPU on the way.
You also need the "--no-preserve-root" and to have a buggy motherboard UEFI implementation.
The problem is that deleting stuff in/sys/firmware/efi/efivars resets some variables in the UEFI. If the implementation follows the spec then that is like doing a factory reset on your motherboard. For some poor hardware they fail to boot after this. The kernel already has some protection for some bad hardware, more will be added shortly ( https://gist.github.com/mjg59/... ).
Now that Fairphone 2 is shipping, there is no excuse not to get a more ethical phone. (Its also quite a nice phone, modular, repairable, runs multiple OSs)
This is going to be a real challenge to people want to build new renewable sources. Would you want to build a solar plant if it produces energy at a time that you can't sell it, and produces little at times when the prices are highest. (Nice if you want to sell storage systems though).
Everyone here is already using Privacy Badger ( https://www.eff.org/privacybad... ) or similar right?
It is say that *if* we do nothing to reduce fossil fuel use and continue to emit as we do today, what is likely to happen. Its not predicting that we do nothing. The best guess is that at least some countries keep the Paris pledge and reduce emissions. But, if everyone decided that they could not be bothered to make the changes required, then we can expect significant warming.
" In the absence of global mitigation actions, five trillion tonnes of carbon (5 EgC), corresponding to the lower end of the range of estimates of the total fossil fuel resource" i.e. assuming we take no action and keep burning fossil fuels at the current rates. From the time scales talked about on the first page, it looks like they assume burning it over the next couple of hundred years. Maybe some one want to give the full article a read?
I'd be surprised if it did not include traditional brakes as well (as is standard in regenerative braking systems).
Yet still cheaper than wind or solar (even before you factor in storage).
X forwarding still just works if you are running wayland locally. behind the scenes its using xwayland, but from the user point of view nothing has changed. I am sure there will be a more waylandy solution before the tool kits drop their X support (which probably wont happen for decades).
Why do you need the closed nvidia driver on a server? Nouveau should be fine or even just the vesa driver. (I could say why do you even need a video card on a server, but I guess some folk prefer that to using ssh or a serial connection from a laptop)
I am using BTRFS on luks on my laptop. Even during a motherboard failure that cause repeated hard poweroffs I did not loose any data (and thanks to data checksumming I know that there is no corruption lurking in the files). BTRFS has developers at Facebook, Fujitsu, SUSE, IBM and still gets patches from people at Oracle. Seems a fairly healthy project to me.
GPL gives the best chance that in the long term there will be multi vendor support. So in 20 years time I'll still be able to read my data, and no one can hold it hostage with crazy licence fees. Sure other open source licences are pretty close, but if the main sponsor behind a project goes closed, then it can sometimes take the community with it. Who knows if in the next 20 years Oracle will do a SCO and try suing anyone who uses their tech in a way that does not generate profit for them.
I'll stick with BTRFS thanks. It gives me all those features, is GPL and has been trouble free for me on many TB of disks for several years.
Maybe some static analysis tool recently gained a feature that finds it. Maybe some conference talk mentioned some new method that helped find it. Maybe they were both aware of someone using this exploit.
>toolkits drop the X11 code I think that's a pretty long way off.
"ssh -X" already works fine on wayland. Install Fedora 23, start a wayland session and try it. (Ok, it starts up an xwayland server underneath, but from a user point of view it works indistinguishably)
"ssh -X" works fine on wayland. Install Fedora 23, start a wayland session and try it. (Ok, it starts up an xwayland server underneath, but from a user point of view it works indistinguishably)
Sorry I was not clear enough. The kernel value for max number of cores must be a power of 2. So to use that triple-core CPU the kernel would actually need to support up to 4 cores. So if AMD plans to release a 20-core, they can't just bump the number in the kernel to 20, they have to increase it to 32.
If the previous max cores per socket was 16, and the value in the kernel needs to be a power of 2, then at most this tells us that they have a 17 (more likely 18 or 20) core CPU on the way.
Something to spend the Jolla refund on
Fairphone
You also need the "--no-preserve-root" and to have a buggy motherboard UEFI implementation. The problem is that deleting stuff in /sys/firmware/efi/efivars resets some variables in the UEFI. If the implementation follows the spec then that is like doing a factory reset on your motherboard. For some poor hardware they fail to boot after this. The kernel already has some protection for some bad hardware, more will be added shortly ( https://gist.github.com/mjg59/... ).
I could be several months before our orbit lines up with it.
Now that Fairphone 2 is shipping, there is no excuse not to get a more ethical phone. (Its also quite a nice phone, modular, repairable, runs multiple OSs)
Filesystem check? are you still running ext2?
Intel would never do that
RHEL6 uses upstart, which is absent from most anti-systemd folks list of favourite init systems.