Does it work with
ldmc -r <path>
?
This is the only way you should unmount a ldm-owned device.
I was wondering how to unmount them But unfortunately 'ldmc -r [path]' and 'ldmc -l' return
connect: No such file or directory
But I know for sure the directory I'm providing is correct.
I have a separate issue with android devices. I have the 'android-udev' package from the AUR, which provides rules for many different devices including mine (HTC), yet ldm doesn't seem to recognise it. I'm not sure if this is an issue with udev or your program.
Here is the HTC section of '/usr/lib/udev/rules.d/51-android.rules':
# HTC
ATTR{idVendor}!="0bb4", GOTO="not_HTC"
# skip if debug mode off
ATTR{idProduct}=="0ff9", GOTO="android_usb_rules_end"
ENV{adb_user}="yes"
# fastboot mode enabled
ATTR{idProduct}=="0fff", SYMLINK+="android_fastboot", GOTO="android_usb_rule_match"
Many thanks for the great program btw, it is light indeed!
]]>ldmc -r <path>
?
This is the only way you should unmount a ldm-owned device.
]]>It doesn't matter whether I use pumount/sudo umount to unmount the device, the directory doesn't get deleted.
It looks like the created directory has the right permissions. E.g:
drwxr-xr-x 7 jalon users 32K ene 1 1970 IORI_PS3
And after unmounting, permissions change:
dr-----rwt 2 root root 4,0K jun 7 20:22 IORI_PS3
I hope this can be fixed!
]]>This is is really a nice little device mounter.
At the moment I can't make it automount my android phone for file access.
I know that Google is on the way to remove USB Mass Storage mode from android, so I was wondering if LDM could trigger a MTPfs automount with android devices somehow ?
Thanks for your help.
]]>USER_GID=100
USER_UID=1000
but when I try to start it requests my uid and gid. If I type:
ldm -d -u 1000 -g 100
it says I must run as root, which works, but I thought the config file was supposed to allow you to not run it as root. Is it seeing the config if it is requesting my uid and gid?
I'm trying to use ldm 0.4.3
Its not a good idea to put file systems on the root path of devices and i suspect the problem is here.
Partition your device and then put the file system on the partition.
Your device,as it currently is,is a special case/corner case and not everybody supports it as some tools expects to see file systems
only in partitions.
Thanks, I'll try that. Gotta say though that I formatted the drive via the Win7 context menu and that same drive used to work on my netbook using the same method formatting method. But maybe something went wrong, who knows. I'll report back.
]]>]]>Having a similar issue.
The drive mounts just fine via "mount /dev/sdb /mnt"Here's the output of "lsblk -f":
sdb vfat PATRIOT 1AA4-0AB2
Its not a good idea to put file systems on the root path of devices and i suspect the problem is here.
Partition your device and then put the file system on the partition.
Your device,as it currently is,is a special case/corner case and not everybody supports it as some tools expects to see file systems
only in partitions..
Downloaded the "ldm-git" package from the AUR yesterday, created the /etc/ldm.conf file with my IDs and started the service via "systemctl enable ldm.service".
systemctl | grep ldm
ldm.service loaded active running lightweight device mounter
So it's also active.
Now I plugged in my USB stick and nothing happened. So I stopped the service, removed the stick, and started manually to get the verbose output:
/dev/sda
dev_fs : (null)
/dev/sr0
dev_fs : (null)
/dev/fd0
dev_fs : (null)Now I plugged in the USB stick:
/dev/sda
dev_fs : (null)
/dev/sr0
dev_fs : (null)
/dev/fd0
dev_fs : (null)
/dev/sdb
dev_fs : vfat
dev_type : disk
dev_idtype : diskOutput didn't change back to three devices when I unplugged the stick (don't know if it should).
I should also mention that PCManFM didn't manage to mount the drive either. I disabled all of PCManFM's mounting options prior to running ldm, btw.
The drive mounts just fine via "mount /dev/sdb /mnt"
Here's the output of "lsblk -f":
NAME FSTYPE LABEL UUID MOUNTPOINT
fd0
sda
├─sda1 ext4 3bf33488-0c9c-4453-b8b2-8ee1c11d0977 /
└─sda2 ext4 43c5fcd1-1d81-45c8-98c8-420a16b553c0 /home
sdb vfat PATRIOT 1AA4-0AB2
sr0
Any input? I have no idea what's going on.
]]>The latest git commit should fix the issue
It most certianly did.
Many thanks, that's excellent.