If you have ever had to reattach a disconnected SR to your XenServer (I published a blog post with instructions on how to do this some time ago), you will be already familiar with the xe-pbd-plug command.
Page 3 of 12
Comodo offer free email certificates, which is awesome as email is an inherently insecure method of communication. So, if you were toying with the idea of playing around with email encryption and signing, you have no more excuses now.
Getting the free cert to work on macOS, however, might be tricky if you don’t pay attention to a couple of things. Here are the pitfalls I have encountered in the process and how I was able to fix them.
I couldn’t help myself, I needed to write a short rant. I am using a Netgear GS116Ev2 switch as my core switch at the moment, and it works great when it works. When it doesn’t, it’s pretty stupid. Twice in the last week, while performing some changes to the configuration (and not even something big, I am talking about adding a VLAN) the switch became unresponsive and I had to restore to factory settings. Trying to find a support email is close to impossible, so that doesn’t help either. Getting a reply from their Twitter account looks even more difficult, they really seem not to give a fuck.
We all know this: one of the biggest issues with Windows 10 Mobile (previously known as Windows Phone) is the lack of apps. I am convinced it’s one of the main causes of the platform failing massively in the global smartphone market (only 0.7% market share last year according to Gartner).
This kinda makes me sad a little, as I felt the mobile OS market could use a bit of fresh air after all these years of iOS and Android which, even if constantly improved, always felt like more of the same to me. I agree that Windows Phone sucks on so many levels that it would be hard to list all of its problems without forgetting about some others, but at least it was different, you know? And it looked awesome.
Anyway, enough with the melancholic intro. If you want to configure a Private Internet Access VPN on your Windows Mobile or Windows Phone device, you will have to take care of things manually, as PIA does not offer a Windows Mobile app (hence my introduction, just to tie up all loose ends).
When you perform an upgrade of your Ghost installation, you might run into a little issue towards the end of the upgrade process, specifically when you run this command:
npm install --production
This step might end abruptly with no explanation whatsoever on what is going on. On my machine, this is what happened:
root@hostname:/var/www/ghost# npm install --production extract → gunzTarPerm ▌ ╢██████████████████████████████████░░░░░░░░░░░░░░░╟ Killed root@hostname:/var/www/ghost# npm install --production cloneCurrentTree → attemp ▀ ╢████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟ Killed
As you can see, even attempting to run the command again didn’t help. After a little bit of digging around, I found out that this is a RAM issue.
After booting my GitLab VM, I saw this error message when I tried to access its web interface:
502 Whoops, GitLab is taking too much time to respond
Even though the service name when you run a BIND DNS server is
bind9, this will only work with start, stop, restart and similar commands.
If you want to check what version of BIND DNS you are currently running on your Linux server, you need to use this:
I admit, I am a fan of Nylas, I think it’s one of the nicest looking email apps out there (if not the nicest looking one) and I admire the intent to simplify handling emails by abstracting all the differences between the various email protocols, so I am keeping an eye on the project’s development.
Most importantly, I love the option to self-host their sync engine as I like having things under my control. Email servers are something I have never wanted to deal with myself however, due to the very high complexity of managing such a thing, but with the sync engine it’s different. Emails are still handled by your email provider, but your sync engine is hosted by you locally, which in my mind gives me the best of both worlds.
I was taking a look at the network configuration of one of my FreeNAS machines, and I noticed a few network interfaces that I did not immediately recognize, something I am sure I had not created manually myself. These interfaces are named bridge0, epair0a and epair1a.
After my post which explained how to build the Nylas N1 email client on macOS, here is the second post in the series which focuses on Windows 10 instead.
I had no shortage of issues and error messages trying to build N1 on Windows (and I wasn’t the only one, as the issues I opened in GitHub were often reproduced by others as well), but they all happened because I was trying to use an unsupported version of Visual Studio (2015 Community Edition, in my case) so here is all you need to do to be able to successfully build Nylas N1 on Windows 10.