Explore >> Select a destination
|
You are here 
|
nguyenhuythanh.com | ||
| | | | |
nora.codes
|
|
| | | | | ||
| | | | |
blog.thalheim.io
|
|
| | | | | No such file or directory: How I stopped worrying and started loving binaries on NixOS. In this article, I will discuss the technical issue of running pre-compiled executables on NixOS, and how we can improve the user experience by making these binaries work seamlessly using nix-ld. One of the key benefits of NixOS is its focus on purity and reproducibility. The operating system is designed to ensure that the system configuration and installed software are always in a known and predictable state. | |
| | | | |
rgoswami.me
|
|
| | | | | A short exploration of multi-user nix and interacting with the Nix User Repository without root Background For multi-user nix installations1, the NIX_PATH variable is empty. Here I briefly go over two approaches to mitigate this, one with nix-channel and the other by manual pinning. Note that this post will eventually be superseded for most cases by a better flake workflow. Channels The idea behind using a channel is essentially that the tar at a particular commit / tag will be downloaded and stored, typically at $HOME/.nix-defexpr/channels. This is in-fact a symlink typically as seen below. | |
| | | | |
reverse.put.as
|
|
| | | This is a guest post by a young and talented Portuguese exploiter, Federico Bento. He won this year's Pwnie for Epic Achievement exploiting TIOCSTI ioctl. Days ago he posted a video demonstrating an exploit for CVE-2017-5123 and luckly for you I managed to convince him to do a write-up about it. I hope you enjoy his work. Thanks Federico! | ||
