Access multiple Google Calendars from KOrganizer



Access multiple Google Calendars from KOrganizer
Posted on June 11, 2011
Recently, a question came up on the KDE Community Forums regarding the use of multiple Google Calendars with KOrganizer. The preferred access up to now has been with googledata Akonadi resource, however that doesn’t support more than one calendar, and (at least from my unscientific observation) seems to be rather unmaintained these days.

Luckily, not all’s lost. Akonadi recently gained the opportunity of accessing CalDAV resources, and Google Calendar also offers a CalDAV interface, hence this is possible.
This post will briefly describe how (thanks go to PIMster krop, which casually mentioned the possibility on IRC and prompted me to investigate).

Notice: I am running trunk (4.7) so I have no idea if the steps posted below are possible in 4.6. Also, this worked for me with my particular setup. YMMV.
First of all, you need to obtain the calendar IDs you want to use. This is done in the web version of Google Organizer, in the settings page of your specific calendar, near the private links: it’s a string of alphanumeric characters followed by Copy it in full (even the address part) as you will need it later, and do it for every calendar you want to use.
Next, open KOrganizer, locate the list of the calendars, right click on an emtpy spot and select Add Calendar:

In the next screen, select “DAV Groupware resource”, then a wizard will come up. Fill in username and password (apologies for the language! I haven’t found a quick way to switch these dialogs to English) and click on Next:

In the following screen, choose Configure the resource manually:

Click on Finish, but you’re not finished yet. In fact, we will have to add more stuff here. In the new window, select the display name (here shown as Nome visualizzato) of the calendar, then click on Add (which is translated as Aggiungi in this screen):

In the next screen we’ll have to add what’s needed for our calendar to work. In Remote URL put (https, not http) then put (again) your Google account credentials in the relevant places. Then click on “Download” (Scarica here) and you will see (after a while) your Calendar being loaded in the “Found collections” pane, with the name you set in Google Calendar. Click OK to save the configuration.

This will bring you back to the previous window. For more calendars, repeat the steps (click on Add, insert URL, Download, OK) for all the calendars you have to display.
That’s it. If you encounter trouble, have a look at ~/.xsession-errors to see whether Akonadi managed to connect and download your existing items correctly. And don’t forget to file bugs!

309 total views, 1 views today

Setting up the HekaFS on Fedora




Use the following command to install all server nodes:
yum -y install glusterfs glusterfs-server glusterfs-fuse hekafs

On the client, user the following command to install:
yum -y install glusterfs glusterfs-fuse hekafs

Start the glusterd and hekafsd daemons on each server node with the following commands:
service glusterd start
service hekafsd start




Before setup:

You should get another storage drive other than the OS. Allows you to maintain speed if heavily accessed and in case a drive does wear out, you can just pop another in.
If that cannot be done, create a loop mount file using dd command(dd if=/dev/zero of=hekafs_loop1.iso bs=1024M count=32  Creates a nice 32GB empty file) and add loop mount entry in fstab(/mnt/hekafs_loop_file/hekafs_loop1.iso /mnt/heka_brick1 xfs,iso9660 loop 0 0). Then the HekaFS should be able to use it. However, it needs formatting with a filesystem for use(mkfs.xfs /mnt/hekafs_loop_file/hekafs_loop1.iso). I recommend XFS. Then mount it.

/etc/ssh/sshd_config file needs to allow root ssh access for the Hekafs to work.
Adjust “PermitRootLogin” to “yes”.
Also we need KEYs to work: “PubkeyAuthentication yes”
At least one of the storage bricks(call it the Main access machine) needs password-less access to  ALL other storage bricks via SSH keys on root user. This is why storage bricks are normally a standalone group and clients are another. I use one machine with a key that is in the authorized_keys file on all the other bricks. I only use this machine to setup the system. A better setup, but harder(time consuming, until scripted), is where EVERY machine can access any other.
After all that, you must make a one time connection from the main machine to all the other bricks so that SSH is confirmed on the yes/no prompt.




The HekaFS can be configured some through the web console. Accessed on port 8080 of the machine with Heka installed.

Under the Manage Servers link, you can type in the other servers holding storage “bricks” that you want to combine into the storage cluster.

Under the Manage Volumes link, you can A: checkmark the found mounts or B: specify the mounts under the “Add Directories” header. Check the ones you want and specify the Volume Type.
Plain, Replicated, Striped, SSL
As of right now, this interface does not allow a combined Replicated+Striped type. Should in the future.
Choose Replicated.

In the next box, type in how many replications. Type 2 for minimal.
This means on the cluster, two copies shall exist on different machines in case one machine fails.

Give a name to the new Volume in the Volume ID.
“General_Use”, “Office Docs”, “IT Programs”, “Backups”, ???

Click Provision

Your volume is created. Now onto WHO can use it.

Tenants are logins to the storage cluster. Each Tenant can have different permissions to access different Volumes.
Name and passwords are easy.
The UID and GIDs are up to you. Recommend starting at 10000 to 10500 for each.

Once the Tenants are setup, you must click the Volumes link next to each one and tell the HekaFS which volumes can be accessed via this Tenant.

Client usage of the newly setup volumes:

Pop this in a script or on a start-up file: “sudo hfs_mount heka1 General_Use ph ph /mnt/heka_client_storage/”
It reads as follows:
mount command | filesystem | Volume | UserName | Password | mount point on client system

Expand Volume:

To expand add in this config 2 new bricks and install as described. Stop at end of “Add bricks in cluster” section. Open Terminal of one brick you configured. Now we add the 2 new bricks to our volume volumeTest.

Check bricks and volume with

After expanding or shrinking a volume (using the add-brick and remove-brick commands respectively), you need to rebalance the data among the servers.

Now we have an Distributed-Replicate volume.

gluster volume info   Volume Name: volumeTest Type: Distributed-Replicate Status: Created Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: Brick2: Brick3: Brick4:

516 total views, no views today

Opera 10.5 Beta Adds Private Browsing and Excellent Windows 7 Integration [Downloads]


Windows only: The latest beta version of the Opera browser adds total Windows 7 integration, with Jump Lists, Aero Peek, and a beautiful Aero Glass interface—and we’ve got a quick tour of all the new features.

The first thing you’ll notice after installing the 10.5 beta is that the interface has been completely re-done with Aero Glass for Windows 7 or Vista users. The menu bar has been rolled up into a single button similar to the way Office 2007 works, with easy access to all common functions all from one place.

Windows 7 users can now hover their mouse over the taskbar button and see previews of each of the open tabs, and moving your mouse over a specific tab will enable the Aero Peek effect and show the Opera window with the contents of that particular tab—just the way Internet Explorer 8 does. You can even middle-click on the thumbnail preview to close a tab.

The Jump List menu shows the items from your Speed Dial, lets you open a new tab, or start a new private browsing session in a separate tab. Once you’ve opened a new private tab—which you can also do by right-clicking on the new tab button on the right of the tab bar—the icon in the tab will change to indicate that you are in a private browsing session.

You can choose to open a separate window for private browsing, but being able to include that private tab without requiring a new window is a nice feature that you can’t currently do in any of the other mainstream browsers.

Opera 10.5 beta is a free download for Windows only; Unix and Mac builds will be available later this week.

488 total views, no views today

Avast Free Antivirus 5.0 Adds Behavior Monitor, Heuristics Engine, and Improved Performance [Downloads]


Windows only: The newest version of the popular Avast Antivirus is finally available for download. It’s lighter, faster, and more feature-filled than ever, bringing a new behavior shield, heuristics engine, and code emulator to keep you protected at all times.

Apart from its far easier-to-navigate interface, Avast has a few new features that make it hard to turn down. Its new code emulator can emulate a suspicious executable’s code, isolated, for use in its new heuristics engine, designed to detect malware that would otherwise be undetectable with normal definitions—in other words, spotting malware by learning what the code does. If you use the pro version, you also get their new sandboxing feature for even further protection.

Apart from the new features, Avast has also lowered scanning times as well as the resources necessary to scan and update—a common issue with antivirus programs that are always running in the background. If you’re already an Avast lover (and many of you are), you can either wait for the program to update itself in the near future or go download 5.0 straight from Avast. If you’ve tried Avast and turned it down before, it may be worth another look—you may find that its former cons (such as the difficult-to-use GUI and resource use) are now more up to your standards.

Avast Antivirus is a free download, Windows only.

416 total views, no views today