First, unstable machine.
Then, regular crashes of the Finder and Safari.
Now, weird font bugs:
My 6 months test period of Leopard is over. Time to switch back to a Linux/KDE desktop.
Free Softwares, Computers & Linux
First, unstable machine.
Then, regular crashes of the Finder and Safari.
Now, weird font bugs:
My 6 months test period of Leopard is over. Time to switch back to a Linux/KDE desktop.
I’m used to access distant machine’s file systems via ssh. My favorite environment, KDE, makes things easy thanks to the support of sftp:// URLs via a kio_slave. MacOSX is not as friendly and don’t have any built-in mechanism of that kind.
To get similar features in Leopard, we have to rely on MacFuse and sshfs. I’ll explain here how I’ve installed these components on MacOSX 10.5.
First, download the latest MacFuse dmg and install it. FYI, the version I’ve got was MacFuse 2.0.3,2.
Then, download the sshfs executable for Leopard, either the gzipped version or the binary from the SVN as explained in the MacFuse wiki.
From a terminal, rename the binary:
sudo mv ./sshfs-static-leopard ./sshfs
Then allow the binary to be executed and place it in the system:
sudo chmod +x sshfs sudo install sshfs /usr/local/bin
From now you can test sshfs mounting with the following command:
sshfs user@myserver.net:/folder/ /Network/distant-folder -p 22
I personally had a problem here: sshfs complained about a missing library. I fixed this by downloading the required file from the MacFusion project and copying it beside the sshfs binary:
sudo wget http://www.macfusionapp.org/trac/export/86/trunk/SSHFS/sshnodelay.so sudo mv ./sshnodelay.so /usr/local/bin/ sudo chmod +x /usr/local/bin/sshnodelay.so
If this fail you can also check:
ssh user@myserver.net command;mkdir -p /Network/distant-folder);-o debug option to the sshfs command above to get additional clues.Now we will automate the mounting of sshfs at every start.
At this point I recommend you to register the root user of your MacOSX system to the distant server:
sudo cat ~/.ssh/id_rsa.pub | sudo ssh -p 22 user@myserver.net "cat >> ~/.ssh/authorized_keys"
If doesn’t exists, we have to create the /etc/fstab to edit it:
sudo touch /etc/fstab sudo vi /etc/fstab
And add the following directives:
dummy:user@myserver.net:/folder/ /Network/distant-folder sshfs allow_other,auto_cache,reconnect,port=22,follow_symlinks,volname="Distant folder" 0 0
As you can see I’ve added lots of options to accommodate my uses. You can get more informations about sshfs options through traditional help pages:
sshfs --help
MacOSX’s automount daemon will look for a script called mount_sshfs at start. Actually it doesn’t exists on your system, but sshfs command line is compatible with what automount expect. So creating a symbolic link will do the trick:
sudo ln -s /usr/local/bin/sshfs /sbin/mount_sshfs
Finally, we can tell automount to acknowledge all our modifications:
sudo automount -vc
Let’s say you have a local copy a mail folder you want to browse with Kmail. This folder is normally found on a dedicated mail server and you access it through the IMAP protocol. I was in this situation some days ago and I will tell you how I’ve done it.
Instinctively, I assumed that my folder was of the Maildir format, and Kmail local mails too. So I tried to copy my ~/Maildir folder from the mail server to my local machine (~/.kde/share/apps/kmail/mail/). And that was the result in Kmail:

It looks good but it’s not: there is no sub-folders !
After some googling, I found what was wrong: my ~/Maildir folder is not a Maildir, but a Maildir++ folder. This kind of folder is handle by popular IMAP MTA like qmail, Dovecot and courier-imap (which was used on the mail server where my ~/Maildir come from). There is some advantages of using the “++” flavor of Maildir over the classic one, like quotas and sub-folders. Unfortunately Kmail is not able to read the Maildir++ folder structure.
To fix this, I’ve created a tiny python script to migrate a Maildir++ folder to Kmail.
How-to use it ? Simply:
MAILDIR_SOURCE and KMAILDIR_DEST variables to match your local configuration,I advise you to try it first in a safe environment (like under a temporary user account). And don’t forget to backup everything before playing with it: because this script work for me doesn’t mean that it will work for you !
I’ve just backported Amarok 1.4.7 from cooker to Mandriva 2007.1 (aka “Spring” edition).
Packages are downloadable from my RPM repository for i586 and x86_64 architecture and both build support SQLite, MySQL and Postgresql as database backend.
Amarok 1.4.6 was released two weeks ago. Even if this version is available in Mandriva 2007.1 official backports, it doesn’t support MySQL and PostgreSQL databases. My RPMs of Amarok 1.4.6 does. They can be found in my Mandriva 2007.1 repository, which now include a sub repository for the 64 bit flavous of Mandriva.
Latest blog activity
kev, djib
Hrr, bhanu, Amor, Miller, Teodoro, Darius [...]
Toma, kev, Toma
William Kulich, Roland Gesthuizen, bbr, Girish, Ozmumcu, gavjof [...]
kev, djib