Monthly Archives: June 2013


Looking at the RPi and the CubieBoard (refer to previous post on Raspberry Pi), I’m wondering which one would be better. I think for a real laptop replacement, CubieBoard is better. As a single purpose device, maybe RPi would be. … Continue reading

Rate this:

Reading Murakami


Enjoying the read but I still think Murakami is a prick for his constant  bourgeois brand name dropping. It might be descriptive, but still very annoying.

Pi or Beagle?

And following up on a thought I had a few weeks ago about a portable LDAP server, my good friend Philipp recommended that I check out Raspberry Pi. I’d somehow mistaken RP for a programming language! And lo and behold a new world suddenly opened up. I’m on day 1, so perhaps I’ll have more ideas after day 6?

And since one path leads onto another, I ended up trying to evaluate other options like RP on the market and here’s what I’m reading now.

How hard is it to get to truth?

And that pretty much is the history of logic!

Building blocks of logic

And going through this video, I’m astounded at my own ignorance.

In search for lost time (UTC or local?)

Ah, this post is from my much beloved WLW!! And it remembers me Smile – I’d set up WLW as  keyword and it picked it up and linked to it – that’s something. And by gawd, WLW is an all around kick-ass blog client. I miss it deeply when I’m in my tux avatar. And now after diving deep into Linux, I see some awesome aspects of MS Windows. Sometimes, as in the case of time, an interesting dilemma turns up.

If you look at your watch, what time do you keep? UTC or your local? I think most of you and perhaps I too would laugh at this absurd question – not a doubt, I’d keep local time! And when you look at that clock on your screen what you expect is local time, and maybe you track a few other zones, like I do, so you want some other times too, but clearly – you do want local time.

Now, with default settings, in Linux you see your local time showing correctly when you look at the graphical clock. However, behind the scenes, Linux at the hardware level works on UTC (Universal Coordinated Time – I know it’s odd that the T and C are jumbled but look it up yourself!) and the developers thought it a great idea.

Microsoft shows local time on the clock, but with the difference that the machine’s time is set to the same. Which makes sense too, unless you fiddle a lot with time zones. However, put Windows and Linux on one machine (like I did) and you run into a nightmare with some fun discoveries for relief.

To resolve this you have to do one of two things:

  • Get Linux to work with local time, or
  • Get windows to work on universal

For Linux you’ll find quite a few sites showing you how to fix things, but for Windows, I was lucky to hit upon Arch Linux’s wiki entry which tells Windows that RealTimeIsUniversal – indeed! However, use it with care if your location uses DST.

Happiness is … fixing my sound issues! :)

I’ve got laugh about this! For now this is what will make me happy. I’ve been musing about how to reconfigure sound on my debian install, which I posted about (Darn, I do miss Windows Live Writer – I could link to previous posts… *sniff*)

Ha, so this Qumana thing has a blog control manager where I can see a list of my old blogs and copy links! So here it is – the link to my last post on sound. I’ve got Jackd working now. What I did, based on a suggestion on the debian-user list, was to keep PulseAudio and route its output through Jackd. Not recommended, but it works.

sound card <== alsa <== jackd <== pulseaudio <== gstreamer | alsa

Now, I’m on a different problem. My headset. Sound’s too weak and they work unpredictably – which is why I started this whole thing in the first place. Looking at this diagram, I see I need to refine it a bit.

There is a slight difference in a key stage.

jackd <== pulseaudio – it’s not straight forward. You have to create Jack’s sinks and sources using pactl – i.e., using PulseAudio. Which means my actual setup is a bit stranger 🙂

sound card <== alsa <== pulseaudio <== jackd <== pulseaudio <== gstreamer | alsa

Why?! Oh well, beyond me at present. But it clarifies why I can’t see the headset (sink) on my connections in the Jack control. I need to go lower and work on the pulse/alsa layer to create a sink and source for the headset. Now that I have an idea of what needs to be done. I’ve got to figure out the how.

I’m learning. 🙂

And happiness is … figuring it out.

Enabling gnome extensions across a number of users

This is progress! 🙂 A user posted a question about deploying an extension across multiple users. I got interested and so looked it up and I’m getting somewhere with this stuff I’m poring over.

Now if you’re here as a user, all you need to do is point your browser to this url, you’ll see all the installed extensions and the option to enable them:

As an admin, here’s what I posted:

This page gives you the bare bones of what needs to be done:

In short you need to do two things:
1. Install the extensions system-wide or per user
2. Enable the extensions

Step 1. Install the extension system-wide or per user:
If system wide then they need to be copied to the folders:
/usr/share/gnome-shell/extensions and

If per user then in folder:

The name of the folder is the extension name that you’ll use in the next step.

Step 2.
Enable it. Enabling involves using gsettings like so:
gsettings set enabled-extensions "[‘<name of folder>’,'<name of folder>’]"

So on my machine, it is:
gsettings set enabled-extensions "[‘’, ‘’]"

And there it is – the heart of the script. To an admin this should make sense.

And here’s the rough script for you:

Should work on Debian 7.

apt-get install gnome-shell-extensions
gsettings set enabled-extensions "[‘’, ‘’]"

Paste the text into a file with an extension .sh and set it’s permissions to executable.