Markizano.NET

I want to do a series on "rolling your own" and how you can use open-source software for just about all your needs. In this way, you can learn about how some software architectures work under the hood, how to configure, how to research and understand what is needed in order to get something like this setup and running. If you're like me, you're probably on a time-budget, so I won't delay, let's get right into it. Install bind9 Let's start with the software required. If you are starting from a bare headless linux install like a Docker container or a fresh image, there may be a few things to install like your favorite text editor since we will be editing files. If you don't know of a text editor in Linux, you can use nano (yes, I probably just infuriated a third of you -- I can already see you in the comments section). I like it because it's simple and key-combination based, rather than arcane spell based as far as the navigation is concern...

If you're in a situation where you aren't using a NetworkManager of sorts, then this post will guide you how to connect to Wi-Fi using just two commands: `wpa_supplicant` and `dhclient` , okay, maybe a 3rd command called `wpa_passphrase` . Let's get into the details. Install Packages If you have never connected to a Wi-Fi network in Linux on this system before, you probably have some packages to install. For at least the packages described in this post, I'll give the commands to execute: Debian/Ubuntu sudo apt-get update sudo apt-get install -y isc-dhcp-client wpasupplicant RHEL/RedHat/Fedora sudo yum install *help me in the comments section, please?* Create Wi-Fi WPA Key This first command using `wpa_passphrase` will allow you to create a Wi-Fi key that will be used to talk with your router. Checkout wpa_passphrase(8) when you get a chance. wpa_passphrase 'UVerse8654930234' 'myd0gN@m3!' Notice how I...

Hello and welcome to my blog. If you are finding this page, then you might be in a similar situation I found myself when I wanted to share audio with different apps if they were being used by different user accounts on your local *nix machine when using Pulse audio. Credits to Eli Billauer and Dhole for the configuration directives I needed to make this possible. The Problem I have multiple user accounts on my system that run various apps, like my web browser, chat apps, email and more. I don't like everything running as myself and try to create a user account with just enough privileges to do what it needs to do. Pulseaudio (herein "Pulse") runs as myself when my desktop environment starts. Apps that run normally need to connect to Pulse in some fashion in order to listen to the microphone or play audio on the speakers. When the apps all run as the logged in user, this works great. When the apps run as someone else, this doesn't work or is inconsistent...

So, after searching around, I didn't immediately find the answer. I hope this post proves useful to someone else searching for the same thing. I first came across this post on StackExchange . Then, I found this post on SuperUser . The gist of it: If you modify /var/lib/bluetooth/[CONTROLLER]/[DEVICE]/info , then it will modify the alias for the time being after restarting ( sudo service bluetooth restart ) and repairing to the device, it will yield the new name, but I noticed that it renames the device to its original alias after a few seconds/minute. Where: [CONTROLLER] is the mac address of your bluetooth controller (if you're only using the built-in controller and not an additional USB device, then you'll only have one directory here). Where [DEVICE] is the mac address of the remote device to connect and get metadata around the device. I discovered you could use `bt-device` to update the alias and it seems to be a bit more persistent than modifying the meta...