HN user
I'm on mobile, so it's not super easy to read the source, but it seems like it only checks for the parent processes?
Also I don't think this approach works correctly, because a disowned/nohup process will show up as PPID 1 (systemd), which is not correct
In France, the last construction is Flamanville EPR. It is at least 5 times over budget and 15 years late
https://en.m.wikipedia.org/wiki/Flamanville_Nuclear_Power_Pl...
Why not dm-integrity?
That's why on some configurations (RHEL 7 I think), journald will happily fill up your ram via /run/
In Rust, there is no unsafe String, only blocks of code can be unsafe, no?
You should add some screenshots!
The memory is still owned by the electron process, so ASLR is not involved here. Also in case of OOB, you still land into the electron process.
VIRT is not a good measure of actual memory usage because it includes shared pages like file cache and libraries, RES is better.
Shameless plug: I developed a tool that try to compute a better value for memory usage: https://github.com/tatref/linux-mem
If you do this, then you can't add new fields
EDF is losing money because of stupid decision like ARHEN that forces EDF to sell electricity at a low price, and also forces them to buy at a high price...
So called electricity "providers" can sell electricity to customers without generating electricity in the first place, and also without transporting it. And at the same time, they get money from EDF through ARHEN!
Isn't simpler to use perl?
Perl -pe 's/.(capture this)./$1/'
That way, you can capture multiple groups, and change the format in the output. You can also do simple calculations if you capture numbers
Do you also feel nervous when resizing a FS that has files in use?
I've never thought about the AV scan of such a file!
Can't the function just return `(a.clone, a.clone())`?
Maybe you mean something like this? `fn extend_vec(to: &mut Vec<i32>, from: &Vec<i32>) { ... }`
This does not compile if you pass the same Vec as to and from, because of the `&mut`
The target architectures of the rust compiler are very limited compared to GCC.
So if you port some core functionality of the kernel to rust, that would make rust a hard dependency for the whole kernel.
Do you have any issue with drivers or license when switching between the VM and normal?
Seems like this runs qemu inside the container.
It depends on the distance
If you send me 1kg of gold, I'll send back double the amount!
I think it's way clearer!
It's a tool to manage dependencies for rust and can also install rust programs (it will download, compile and install)
Benchmarking cpu firmwares is forbidden by the license (same thing for databases)
I'm replying to all the answers here.
It seems that everyone has a different experience on the subject! Just a precision: I had an ATI card (laptop) from 2005 to 2010, then an ATI (desktop) from 2010 to 2017.
I supported AMD several years because of this... Then I got tired of the low quality of both the open source, and the closed driver. Crashes, glitches in movies, flickering...
Some time ago, I bought an Nvidia. It works like charm with the closed driver on Linux and windows. I do mainly games on Linux/windows, some gpgpu (machine learning with tensor flow), and the usual stuff. I couldn't be happier... Except if it was open source ;-)
No, VirtualBox is Windows, Linux, MacOS
The readme didn't specify the --release flag in the cargo run command, this should make a pretty big difference
No, but variable size lookahead/behind do. This is because the engine has to go back if the remaining part of a regex fails. For some examples, see http://www.regular-expressions.info/recursebacktrack.html)
EDIT: you are correct, backreferences do require backtracking, my bad.
I have read that the client version of OpenVPN, which is also vulnerable to heartbleed, should be upgraded, as well as the server.
I wonder what could be a possible exploitation on the client side? Obviously, one can not send heartbeat packets to grab the secret key!
Either way, as long as GB = 10^9, and GiB = 2^30
I don't think that giving the users something that _is_ wrong is a better solution... Why not switching to GiB? Power users would understand, and others wouldn't even notice!
Windows uses GiB, but displays GB. On Linux, most tools uses standard SI (1000 = K, 1024 = Ki), but not all of them...