Package Details: ldm 0.7-2

Git Clone URL: (read-only)
Package Base: ldm
Description: A lightweight device mounter
Upstream URL:
Licenses: MIT
Conflicts: ldm-git
Provides: ldm
Submitter: Rolinh
Maintainer: TheLemonMan
Last Packager: TheLemonMan
Votes: 47
Popularity: 0.006184
First Submitted: 2012-06-15 20:32
Last Updated: 2016-02-21 14:01

Latest Comments

nrq commented on 2016-03-12 10:40

I guess some people doesn't have /usr/bin/core_perl/ in their PATH and this throws an error message about pod2man command not found, aborting the build process.

I don't know if there's a better way to do this but I got it working by adding a check inside build() before cd and make:

build() {
echo " $PATH " | sed 's/:/ /g' | grep " $_folder " > /dev/null
[ $? -ne 0 ] && [ -d $_folder ] && [ -x $_folder ] && PATH=$_folder:$PATH
export PATH

cd "$srcdir/$pkgname-$pkgver"

loonies commented on 2016-02-14 10:08

.SRCINFO was not generated for the version 0.7, hence AUR showing 0.6.2-2 although PKGBUILD is updated to 0.7

MaoCPU commented on 2016-01-20 18:35

AUR still shows version 0.6.2-2 although the source from 0.6.3 is used. Also I couldn't find the package ldm-git any more. I suggest the following patch:

diff --git a/.SRCINFO b/.SRCINFO
index bb5009c..fa1871c 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,7 +1,9 @@
pkgbase = ldm
pkgdesc = A lightweight device mounter
- pkgver = 0.6.2
- pkgrel = 2
+ pkgver = 0.6.3
+ pkgrel = 3
url =
install = ldm.install
arch = i686
@@ -12,8 +14,8 @@ pkgbase = ldm
depends = glib2
provides = ldm
conflicts = ldm-git
- source = ldm-0.6.2.tar.gz::
- sha256sums = 14484ac229f8d6558f007ec1c139e5ada2d3c60230a55f99f939022cfd493c9b
+ source = ldm-0.6.3.tar.gz::
+ sha256sums = 7e5e2b406bc627d4df7676b470ead6af75739ce96dc283e25467bb123b2717d9

pkgname = ldm

diff --git a/PKGBUILD b/PKGBUILD
index 09ef7b7..c4c319c 100644
@@ -3,14 +3,13 @@

pkgdesc="A lightweight device mounter"
arch=('i686' 'x86_64' 'armv7h')
depends=('udev' 'glib2')

benoliver999 commented on 2015-04-16 17:21


BASE_MOUNTPOINT is what worked for me rather than LDM_MOUNTPOINT

benoliver999 commented on 2015-04-16 16:21

I get this:

ldm[342]: The path (null) doesn't name a folder or doesn't exist!

When I try to start via systemd.

My /etc/ldm.conf looks like this:

USER_GID = 100
USER_UID = 1000

Any idea what could be causing the issue? It was working fine until the recent update.

pejobo commented on 2015-04-14 11:29

It's working now (v0.6), and armv7h is also included in arch). Thumbs up!

pejobo commented on 2015-04-04 11:19

I installed yesterday from tar (on raspberry pi 2, so had to add armv7h in arch list). It's working like a charm, but it's version 0.4.3. Is the tarball outdated? Didn't try ldm-git by now.

I extended the ldm.service file with a prestart script so that after a power failure orphaned mount directories are cleared on reboot (I use the pi with a local usb drive for media files and tv recordings, so mount points should be 'stable'):

ExecStartPre=/etc/ $BASE_MOUNTPOINT
ExecStart=/usr/bin/ldm -u $USER_UID -g $USER_GID -p $BASE_MOUNTPOINT

with /etc/

# try to delete orphaned mount directories (e.g. after crash or power off)
if [ "$dir" = "" ]; then
echo $0 - cleaning up mount directory $dir
for f in $dir/* ; do rmdir --ignore-fail-on-non-empty $f; done
exit 0

al3hex commented on 2014-04-14 14:55


* Remove provides array
* Properly quote all variables
* Remove export LDFLAGS="" (Fixed by GH issue #17)
* Set a meaningful name to the source tarball
* Fix .install file

EvanPurkhiser commented on 2014-03-03 06:44

Here's a PKGBUILD that is slightly more modern

addamm_aur commented on 2014-01-03 15:06

Could be nice that ldm doesn't mount a device into another mountpoint if the *same* device is still pugged-in when system reboots or shutdown/starts!

- When 1st plugged-in my external USB HDD, ldm created this muntpoint "/mnt/44B829F3B829E460/";
- Then I rebooted Arch with the external USB HDD still plugged-in;
- When the system came up, I saw that the ldm created another new mountpoint for the same device and mounted it at "/mnt/44B829F3B829E460_/" (note the underscore added!!!) and the previous mountpoint ("/mnt/44B829F3B829E460/") still exists but it's empty.

Thanks! :)

All comments