Wednesday 01 September 2010 at 12:13 am
When I wrote the autoEqualizer plug-in for the Amarok (1.x) media player, to the best of my knowledge, there weren't any media players with this feature nor were there any plug-ins.
Recently, I came to know that the Samsung Galaxy S's media player looks to be having the Automatic Equalizer functionality. Not sure if this player is specific to Samsung Galaxy S or the Android Platform in general.
Read More
Thursday 08 July 2010 at 2:08 pm
The latest kernel upload (2.6.32-16) brings goodies to SystemTap in Debian. This version has added support for kprobes, on which systemtap has a major dependency, for many of its features.
Most of the systemtap instrumentation should work now and all of this will be part of the Squeeze release. Instrumenting the kernel modules still needs some work (DBTS: #555549) but can be done.
Monday 10 May 2010 at 11:50 pm
Just uploaded tomoyo-tools and is waiting in the NEW queue.
Thanks to Moritz Muehlenhoff, tomoyo kernel support should be available in Debian with kernel 2.6.32-13 and above.
What is Tomoyo ?
Description: Lightweight and easy-use Mandatory Access Control for Linux
TOMOYO Linux is Lightweight and Usable Mandatory Access Control with
- "automatic policy configuring" feature by "LEARNING mode"
- administrators friendly policy language
- no need libselinux nor userland program modifications
.
TOMOYO Linux consists of patches to Linux kernel and administrative
utilities, and this package contains its audit daemon and tools.
Description: Lightweight and easy-use Mandatory Access Control for Linux
TOMOYO Linux is Lightweight and Usable Mandatory Access Control with
- "automatic policy configuring" feature by "LEARNING mode"
- administrators friendly policy language
- no need libselinux nor userland program modifications .
TOMOYO Linux consists of patches to Linux kernel and administrative utilities, and this package contains its audit daemon and tools.
Tuesday 04 May 2010 at 6:04 pm
As you must have noticed, the interface of the blog has changed. I just am in the middle of migrating to PivotX.
I started blogging around 5 yrs back. Having had my domain, I wanted to have my own blogging software. Most of the blogging tools had dependency on databases and stuff where as I was looking for something very simple while at the same time easy to use, feel and administer.
Pivot was my decision then. And it was the right one. Today, migration to PivotX was not that very difficult. All my blog posts were easily migrated to the new PivotX tool.
One of my pre-req was to have my blogging software _not_ use a db. It should provide a flat file interface. Pivot[X] was and is the same way today. It still supports flat file databases without compromising on any of the features.
Thank you to the Pivot[X] team from an old time user.
Wednesday 14 October 2009 at 12:15 pm
It all started long back when I worked for a giant computer manufacturing company. Certain IT policies led fo the need for an Offline APT Package Manager
While I got it working for a long time, I didn't have the aggression to polish and push it for general usage. Thanks to my friend appaji, apt-offline (a.k.a pypt-offilne) is now part of Debian.
Thursday 06 August 2009 at 3:06 pm
Given the recent switch to a stronger key by everyone, here's mine.
The old key that I'll still keep using till I get the new key signed by a good amount of people.
pub 1024D/04F130BC 2003-08-18
Key fingerprint = CF0F EDEF 1052 83D2 62A4 0549 E118 62EA 04F1 30BC
uid Ritesh Raj Sarraf <rrs@researchut.com>
uid Ritesh Raj Sarraf <riteshsarraf@users.sourceforge.net>
uid Ritesh Raj Sarraf (NetApp) <rsarraf@netapp.com>
uid [jpeg image of size 52128]
sub 1024g/A876BF8F 2003-08-18
sub 4096R/5D93A273 2009-04-25
sub 4096R/7FBB6077 2009-04-25
And here's the new key, that's been duly signed with the above old key.
pub 4096R/F00A2BE6 2009-08-06
Key fingerprint = 43DE F582 F9E6 7111 CE00 8917 F2F1 1C23 F00A 2BE6
uid Ritesh Raj Sarraf <rsarraf@netapp.com>
uid Ritesh Raj Sarraf <rrs@researchut.com>
uid [jpeg image of size 52128]
sub 4096R/0B488290 2009-08-06
Wednesday 04 March 2009 at 5:25 pm
Backups
Most of the users using computers have a very high dependency on it. Day-by-Day, our data is getting digitized. Everything is getting into electronic formats (Movies/Pictures/Music et cetera). If you are one, you know how important it is to have a backup. 
Lately, I haven't been using Microsoft Windows on a daily basis. So I'll comment on Linux here.
The definition of Backup can be different. People like backing-up only the Important data. The problem is that the term Important is very volatile. What is important to X is not necessarily important to Y.
For my backup solutions, in the past, I've relied on a KDE Backup tool, Keep. It internally uses rdiff-backup. It was good. It allowed incremental backups. There were some hiccups here and there but overall it was pretty good. But it was very difficult to tell the application about What all it should backup. And then, it needed to do a diff verification for every file that was a candidate.
Restoration from rdiff-backup was not always great. Especially the incremental backups. If something was messed up, it was tough to recover. For example, assume that the backup was in progress. And you needed to rush for home immediately aborting your backup. Keep wouldn't play good there.
Then came LVM. I've used LVM for years but never really looked at it as a backup option. To start with, I'd say, LVM is the Best Backup Tool for my needs. I described Important above. For me, Important is my HOME dir, my /var/tmp/kdecache-rrs dir, and my /tmp/kde-rrs dir. Apart from that, my /etc/ dir, my /usr/loca/ dir. And many more that I can't recollect. If there was one simple tool to backup all without worrying of Permission, Security Labels et cetera, that'd be LVM.
And LVM allows Online Backups. So I can have my / volume online and still go ahead with the backup while I'm working.
And depending on I want, I can do a File or a Block based backup.
Recovery
So we know how important our data has become for us, depending on how dependent you are on computers for your day-to-day life. I hate thinking about it but increasing dependency on computers gets me worried about security. Yeah!! You'd say Linux is more secure. (Wouldn't want to discuss in that direction)
I really like the SELinux Security Features. Most of the people (including Enterprise Customers) I know, disable SELinux on their machines. Currently SELinux doesn't see a widespread integration into the entire Application Stack. Thus apps just fail as SELinux restricts their access.
On my Debian Box, SELinux is miles away from the kind of integration packages have through apt. That sometimes makes me run to Red Hat based distributions to see what their state is, on SELinux.
So yesterday, I wiped off my Debian setup and installed Fedora. Used it for a couple of hours and decided to go back to Debian again (More of a personal taste).
That's what I do once in a year. 
The thing I have the most, is to lose data. Data being - My Settings and other stuff I mentioned above.
So to recover Debian was just a couple of hours. Just had to do a Block Restoration of the Block Backed ROOT LV to the new LV. And then, a minor grub and kenrel installation. And voila, everything was back just as it was yesterday.
Nothing much to say. Thank you Alasdair and Team Device Mapper @ Red Hat
Thursday 19 February 2009 at 2:51 pm
So there was a recent thread on the Destop Architect's forum, where Dan Kegel discussed the idea of silent upgrades (for Security, at least).
I for one, am not very fond of the idea. Updates/Upgrades (Security or Features) are something which should be done with some Human Intervention. But still it is not an idea to be completely ruled out. Free Software is about choice. There definitely are use cases where Silent Updates look a good choice. With a carefully crafted policy, this could really help achieve the ultimate goal that Dan was looking after. Closing down vulnerabilities asap.
One of the concerns I had was that a mere upgrade is not what can protect vulnerabilites. Standard Package Managers will do the job of updating the vulnerable libraries with the newer patched ones. But they don't come into effect untill re-loaded. Take the browser as an example. It is vulnerable. You silently got it updated by your distro's package manager. But still it is vulnerable. For the patches to be effective, the browser needs a re-start.
In Debian, you could attain Silent Upgrades with some settings defined in apt.
apt ships a /etc/cron.daily/apt script.
So with the following in place:
APT {
Get {
Assume-Yes "true"; Upgrade "true";
}
}
So, with the above settings in place, one can achieve Silent Updates. This ofcourse comes with an assumption that you are not on a Rolling Release of Debian.
But my focus was about getting those patched libraries/binaries effective. So here's the cooled feature of Debian, which has been there for years. apt/dpkg allows you the debconf interface. And there you can set the priority of messages/questions that you'd like to see. So assume that your remote machine, that you access through ssh, has a sshd vulnerability:
Debian updates the sshd package
It'll ask you (Depending of debconf priority), whether it should restart the sshd daemon
And thus you get a patched sshd package, installed, with the patch effective.
I haven't tried but I believe, if you don't install debconf, dpkg/apt will go with the default action that is defined in the package by itself.
So with all this in place, Debian has a very nice approach to package management. I haven't come across a similar interface in any other non-Debian derived distribution.
Sunday 15 February 2009 at 5:27 pm
Amazing Moments
Debian Lenny has been released.
Go, grab now.
Thursday 12 February 2009 at 2:21 pm
So my friend game me a cute little birthday present, a Motorola S9 Bluetooth Headset.
Making it work under Linux was not very difficult but still has to catch-up in terms of utils.
To make the headset work, I just had to run a scan on the Linux host, and get the hw address and specify it in .asoundrc.
pcm.bluetooth {
type bluetooth {
address = xx.xx.xx.xx.xx
description "Motorola S9 Bluetooth Headset"
}
}
And then to play a file, like in mplayer, you just specify the alsa device.
mplayer -ao alsa:device=bluetooth foo.ogg
KDE's Phonon currently doesn't show the Bluetooth Headset even if it is paired.
PulseAudio doesn't work good. (I couldn't make it work in my limited attempt)