I’m going through a phase in life, where I’m feeling like how Calvin is, in this strip. I’m hoping that it will pass and I will feel relevant again.
NH7, my goto place to listen to my favourite artists and discover new ones, has released NH7 in Town, a brand new service to find things to do where you live. Currently only available for Mumbai, but they plan to roll out support for other cities too. Read more about it here.
Can’t wait for them to cover Bangalore.
After an update of my Arch OS over the weekend, my system refused to boot with this error:
Error: Root device mounted successfully, but /sbin/init does not exist. Bailing out, you are on your own. Good luck.
I should admit that I love the unassuming tone of the message.
For the latest update to happen, a bit of manual intervention is required. More details on that here. Once the update is done, the machine will refuse to boot when restarted. To get your system running again edit the grub entry in the grub menu, find the line init=/bin/systemd and replace it with init=/usr/lib/systemd/systemd and continue to boot the system with modified init parameter.
To make the change permanent, modify the /etc/default/grub file, and change the value of GRUB_CMDLINE_LINUX_DEFAULT by appending init=/usr/lib/systemd/systemd to it. On my machine, it looks like this:
And generate a new grub.cfg by running grub-mkconfig. Make sure that you replace your existing grub.cfg (typically in /boot/grub/) with the new one.
The reason for this problem is that with the latest version of systemd (version 204-1) on Arch, the symbolic link that existed earlier to /bin doesn’t anymore, since /bin doesn’t exist anymore (read this post, for the reason behind that).
A very interesting opinion from Mike Johnston :
A bit of encouragement or constructive criticism, goes a long way. I’ve had personal experiences where I have once been at the receiving end of very negative criticism for various reasons in the open source project that i contribute to. And such incident(s) impact ones self-confidence. Being sensitive to others feelings, tolerance and words of encouragement do make a lot of difference.
Somebody once told me, If you have nothing good to say, then don’t say anything. And I can’t help but agree.
This is the fastest internet connection i’ve ever used.
Here’s how it fared against the average global network speeds:
I just can’t wait to get one of those connections at home.
For a second year in a row, I’ve committed myself to growing, and more importantly, maintaining, facial hair for a cause.
It’s November and it’s time to grow a moustache in support for men’s health. The effort is to generate awareness among people about the men’s health. And this tiny bit of facial hair does manage to generate awareness, specially when people who are not used seeing me sporting a moustache, notice that i have one and ask me for the reason behind it.
‘Movember‘ started in Australia, has now spread to many countries around the world. And the funds generated during this campaign, are routed to research and treatment of prostrate cancer and depression in men the world over.
A few weeks ago, i completely moved to using systemd on my machine (it runs Arch). And since then i was facing a really weird issue when i closed my laptop lid. My laptop, with Gnome3, suspends itself when i close. And when i open my laptop lid, i was prompted with the familiar gnome-screensaver password dialog, as expected. But right after i could see the password dialog, the system went back to suspend state again. Looking through the system logs, i saw that the suspend was being called twice in succession. And i didn’t have the problem, if I ran pm-suspend from the command-line. It was clear that suspend was being done twice, but i wasn’t sure what was actually triggering it.
After a quick web search and not finding anything useful, i started digging into systemd’s man pages and found the logind.conf(5) man page. Voila, there it was:
Controls whether logind shall handle the system power and sleep keys and the lid switch to trigger actions such as system power-off or suspend. Can be one of
ignorelogind will never handle these keys. Otherwise the specified action will be taken in the respective event. Only input devices with the
power-switchudev tag will be watched for key/lid switch events.
I realised that gnome does its own power management and with systemd running, it does its job of suspended as well. So i had this happening twice. My first instinct was to disable suspend settings in Gnome, but that didn’t seem possible, even with the gnome-tweak-tool installed. So I just put the following lines in my /etc/systemd/logind.conf:
This essentially will make sure that systemd doesn’t handle the system lid and suspend functions.
This is the first issue that i encountered after i moved to using systemd. (A non-issue actually). I am very happy with how systemd works. I should admit i was quite skeptical before i started using it, but now I’m very used to the whole idea. And whats more, i do notice the faster boot and shutdown times. I haven’t actually measured it, but I’m quite sure that if i did, i would notice a difference. But, thats for later!