Enterprisely sending your hostname to DHCP

DHCP protocol supports sending the client host name to the server via the DHCP HOST NAME option.
See RFC2132 appendix and the original
DHCP Vendor Extension at RFC1497

Further info on the option structure is in the bootp documentation:

You can configure it

On debian:
uncomment the ‘send host-name’ directive in /etc/dhcp3/dhclient.conf

In RHEL:
add the following line to the interface with the ip you want to associate

vim /etc/sysconfig/network-scripts/ifcfg-eth0
DHCP_HOSTNAME=your-nice-hostname

Launch your patch (and Decode right)!

Ubuntu contributions are managed via the launchpad platform. Once you subscribe you can contribute checking out projects with bzr.

Ubuntu comes with a bzr “launchpad” plugin. You can register your ssh public key here

https://launchpad.net/~user/+editsshkeys

then join with:

#bzr launchpad-login user

Checkout your source project – eg u1ftp, the ubuntu one ftp gateway.

#bzr branch lp:u1ftp u1ftp-origin

Do your patch, commit and then push it!

bzr push lp:~rpolli/u1ftp/unicode_support

How to rsync with ftp

As you know is not possible to perform a rsync with a ftp site. Here you can find a simple workaround to perform a remote backup.

First install rsync and curlftpfs…

sudo apt-get install rsync curlftpfs

…then create the mountpoint and allow access to your user…

sudo mkdir /mnt/yourftp

sudo chown youruser /mnt/yourftp

…enable the fuse mount for non-root users…

sudo vi /etc/fuse.conf

uncomment the parameter user_allow_other on the last line

…and then mount your ftp site

curlftpfs -o user=username:password,allow_other ftp.yoursite.com /mnt/yourftp

Now you can navigate your ftp like a classic filesystem folder!

Finally enjoy your rsync (example):

rsync -r -t -v –progress –delete /home/folder_to_backup/ /mnt/yourftp

Remember that if you need to sync folders with different name you have to add the last slash on the source dir!

P.S. Don’t forget to unmount your ftp site after the rsync:

sudo umount /mnt/yourftp

Apple Calendar Server and 389org Directory Server

DISCLAIMER: Not An HowTo

Welcome to a short guide about binding Apple Calendar Server (ACS) to a 389 Directory Server. Aim of this guide is to point a couple of common pittfalls.

Prerequisites:

  1. install ACS with default authentication. Remember:
    1. enable user_xattr on your directory
  2. install 389org

Download ldapdirectory.py – the backend written for OpenLdap from http://trac.calendarserver.org/attachment/ticket/260/ldapdirectory.patch

Modify ldapdirectory.py to reflect your attributes (eg I use “mail” instead of “uid”, “nsUniqueId” instead of “entryUUID” ).

I suggest to add some more log and error lines to ldapdirectory to speed up debugging.

Modify your configuration file like http://trac.calendarserver.org/attachment/ticket/260/caldavd-sample.plist

Remember to fix it with your parameter and to DISABLE all authentication types but BASIC-AUTH.

This is because ACS uses MD5-DIGEST by default, making impossible to forward the password to the Ldap Server (see http://en.wikipedia.org/wiki/Digest_access_authentication)