Daily Weekly Monthly

Weekly Shaarli

All links of one week in a single page.

Week 18 (April 27, 2020)

Vous allez pouvoir profiter des derniers drivers DCH d’Intel pour votre GPU sans attendre le fabricant de votre PC – Korben

Vous allez pouvoir profiter des derniers drivers DCH d’Intel pour votre GPU sans attendre le fabricant de votre PC

APT Browse - Home

APT Browse — know your packages

A web browser for the contents of Debian (and Ubuntu) packages.
Query

processhacker/processhacker: A free, powerful, multi-purpose tool that helps you monitor system resources, debug software and detect malware.

Logo
Process Hacker

A free, powerful, multi-purpose tool that helps you monitor system resources, debug software and detect malware.

Official Website
Nightly Builds

System requirements

Windows 7 or higher, 32-bit or 64-bit.
Features

A detailed overview of system activity with highlighting.
Graphs and statistics allow you quickly to track down resource hogs and runaway processes.
Can't edit or delete a file? Discover which processes are using that file.
See what programs have active network connections, and close them if necessary.
Get real-time information on disk access.
View detailed stack traces with kernel-mode, WOW64 and .NET support.
Go beyond services.msc: create, edit and control services.
Small, portable and no installation required.
100% Free Software (GPL v3)
Defensive BASH programming - Say what?

Defensive BASH Programming

Nov 14th, 2012 | Comments

Here is my Katas for creating BASH programs that work. Nothing is new here, but from my experience pepole like to abuse BASH, forget computer science and create a Big ball of mud from their programs.
Here I provide methods to defend your programs from braking, and keep the code tidy and clean.
Immutable global variables

Try to keep globals to minimum
UPPER_CASE naming
readonly decleration
Use globals to replace cryptic $0, $1, etc.
Globals I allways use in my programs:
Bash Strict Mode

Use Bash Strict Mode (Unless You Love Debugging)

Let's start with the punchline. Your bash scripts will be more robust, reliable and maintainable if you start them like this:

#!/bin/bash
set -euo pipefail
IFS=$'\n\t'