Explore >> Select a destination
|
You are here 
|
suraj.io | ||
| | | | |
blog.cetinich.net
|
|
| | | | | ||
| | | | |
outflux.net
|
|
| | | | | [AI summary] The post discusses the transition from setuid programs to fine-grained capabilities in Linux systems for enhanced security, using the example of the ping command and addressing challenges in implementing this change across distributions like Debian. | |
| | | | |
hjr265.me
|
|
| | | | | I have lines like these in my /etc/hosts file: 127.0.0.1 toph.local 127.0.0.1 drafts.toph.local 127.0.0.1 quiz.toph.local I can run development servers locally and access them over .local hostnames (e.g. toph.local) instead of the loopback IP addresses (e.g. 127.0.0.1). It works fine. But every time I start working on a new project, I needed to add a new line to the /etc/hosts file. It didn't sit right with me. I should be able to point all *. | |
| | | | |
sitr.us
|
|
| | | This is an excerpt of a post that I wrote for Olio Apps. I am always interested in making my coding process faster and more robust. I want to be confident that my code will work as expected. And I want to spend as little time as possible debugging, testing, and hunting down pieces of code that I forgot to update when I make changes to a project. That is why I am a fan of correct-by-construction methods. Those are methods of constructing programs where the program will not build / compile unless it behave... | ||
