Laite 1.0

  • Purpose: User-space helper application for udev.
  • Requirements: Udev 056 or newer (not tested with ancient versions), Linux (udev already requires Linux 2.6 :-D )
  • Author: Joel Lehtonen (joel dot lehtonen št iki dot fi)
  • Licencing: GNU GPL version 2
  • IRC: #2ndpoint @ IRCNet

This is Laite, simple but useful tool for naming hot-pluggable devices after their contents, not by their vendor or insertion order. Some examples where this is useful:

  • You've got a memory card for a digital camera but multiple media readers
  • You've got multiple memory cards but a single USB media reader

In both cases you may find writing useful udev rules difficult. But here's the solution: We'll name them after the serial numer of the filesystem.

Nothing stops you from using multiple rules in a single machine. You can use this application for naming some of your block devices while other ruleset takes care about the other devices.

Currently supported filesystems are FAT12, FAT16, FAT32 and NTFS. Please note that in some countries handling proprietary filesystems is subject to a licence. So if you live in country where software patents are allowed, be careful. I can't give you legal advice but at least in Finland (at Autumn 2005) this software is legal.

Are you wondering where does the name laite come from? :) It's Finnish and in English it means device or unit.

Download

Future

In the middle of coding process I found out that there is already udev_volume_id. It seems to dig out the same information than this one (and even more). It doesn't make Laite totally useless because Laite has it's own configuration file. In future I may make version which uses udev_volume_id for reading the temporary device and more useful tools for adding and removing serial numbers from config file.

I'm also planning helper application for hotplug(?) which removes and makes mount points according to the devices which are present in the system. Connection between devices and mount points can be found from /etc/fstab.

[an error occurred while processing the directive]