8,335 karma · joined February 6, 2016
What do you mean?
> NB. if you're updating via source, please restart sshd after installing, otherwise you run the risk of locking yourself out.
https://github.com/openssh/openssh-portable/commit/03e3de416...
Edit: Already reported at https://gitlab.archlinux.org/archlinux/packaging/packages/op...
And nothing of value will be lost.
Fun fact: The machine actually supports up to 96GB (2x CT48G56C46S5).
It's been 20 minutes and the email still has not arrived.
https://github.com/systemd/systemd/pull/33353#issuecomment-2...
- It wins in multi-core (14352 vs 12087) and transcode (6:50 vs 7:19) while requiring 4 more cores (12 vs 8 (4+4)) and active cooling
Where's the blowing away part?
Sounds about right. I'm not interested to hear about yet another horrible thing that happened somewhere in the world completely out of my control.
What's with all those "unsafe" keywords then? https://github.com/search?q=repo%3AConst-me%2FVrmac+unsafe&t...
Tmux breaks interacting with the clipboard so much that it has its own dedicated Wiki page dealing with all of the different issues and settings: https://github.com/tmux/tmux/wiki/Clipboard
Until there's a vulnerability in one of the dependencies and now you have to rebuild all of the packages which use it. Specifically for Rust, there's also the fact that most projects use a lock file and if your build process respects it, you now have to wait for the upstream to update it and release a new version (or update it yourself). And if your build process doesn't respect the lock file (or the project doesn't use it) and you just fetch the latest compatible dependencies at the time of build, you now have no idea if you're affected or not by the vulnerability because you don't have the exact resolved versions stored anywhere (https://github.com/rust-lang/rfcs/pull/2801).