You are not logged in.
And the PKGBUILDs have been updated.
Talking about deprecation: /etc/rc.d/ldm could be dropped as well.
Offline
Finally moved from /media/ to /mnt/, also the config file is now at /etc/ldm.conf since the conf.d directory has been deprecated
Thank you. I have removed my patch now.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Finally moved from /media/ to /mnt/, also the config file is now at /etc/ldm.conf since the conf.d directory has been deprecated
May mount dir defined in ld.conf ? I like /media more.
Offline
TheLemonMan, here are some rather important (to my mind) features which ldm lacks:
a man page (ldm is the first package I came across without it)
mounting multiple partitions on the same device
unmounting by udisks without gaining root privileges
multiple users support
Offline
ldm should already mount all the partitions found on a devices, post a dmesg log if doesn't work for you.
The multiple user support is feasible, I'll work on it when I have a break from study heh
Offline
Anyone would mind maintaining ldm on the AUR? As I do not use it, it would maybe be better if an actual user maintains it.
Offline
Anyone would mind maintaining ldm on the AUR? As I do not use it, it would maybe be better if an actual user maintains it.
This saddens me a bit heh, anyway you can leave it to me
Offline
Offline
A man page has been added! Along with a couple of bugfixes (NTFS and LVM related) and new functions
If there's nothing else to add/fix in the next couple of days I'll tag another stable release!
Offline
I'm having issues unmounting with ldm.
My service file line is:
/usr/bin/ldm -u $USER_UID -g $USER_GID
Devices mount great, but if I try and use "ldm -r /mnt/LEXAR" (LEXAR is the folder that shows up), it does not unmount. I have to unmount with umount. I've also tried "ldm -r /mnt".
Any ideas?
EDIT: Silly me. Found the issue. Didn't add /usr/local/bin to my path.
REEDIT: Still does not unmount. Any ideas?
Last edited by ttz (2014-02-21 23:24:52)
Character shines in the great moments, but is polished in the little ones.
Offline
v0.5 is out
Awesome Tried for the first time and works almost
(some trouble with the .service, but have to move the file I think.)
Any ideas or examples on how to inegrate it into Awesome (WM) ?
Offline
There's a callback system that allows you to integrate ldm with your DE as you like
It's written in the man-page how to use it.
Oh, and please use the git version, the stable release has a slightly bug regarding the callback system.
Last edited by TheLemonMan (2014-04-17 16:19:14)
Offline
Sometime in the last 2-3 weeks, ldm has stopped mounting an SD card that it used to mount for me. Unfortunately it's been that long since I last mounted it, so I don't know what change may have triggered this. The issue occurs with both ldm and ldm-git (I used the PKGBUILD from the comments at AUR for ldm-git).
I can mount it manually, no problem, so I don't think the card's corrupt.
I've tried plugging in a usb disk and ldm mounted it, no problem.
Journalctl gives no errors, and if I run it in non-daemon mode, I get no errors.
Below are the dmesg output and udevadm monitor output:
[11026.588974] tifm_core: MMC/SD card detected in socket 0:1
[11026.916422] mmc1: new SDHC card at address 59b4
[11026.917642] mmcblk0: mmc1:59b4 00000 7.34 GiB
[11026.919474] mmcblk0: p1
KERNEL[10700.975869] add /devices/pci0000:00/0000:00:1e.0/0000:02:06.2/tifm_sd0:1 (tifm)
UDEV [10700.977309] add /devices/pci0000:00/0000:00:1e.0/0000:02:06.2/tifm_sd0:1 (tifm)
KERNEL[10701.032479] add /devices/pci0000:00/0000:00:1e.0/0000:02:06.2/tifm_sd0:1/mmc_host/mmc1 (mmc_host)
UDEV [10701.033249] add /devices/pci0000:00/0000:00:1e.0/0000:02:06.2/tifm_sd0:1/mmc_host/mmc1 (mmc_host)
KERNEL[10701.303387] add /devices/pci0000:00/0000:00:1e.0/0000:02:06.2/tifm_sd0:1/mmc_host/mmc1/mmc1:59b4 (mmc)
KERNEL[10701.303858] add /devices/virtual/bdi/179:0 (bdi)
UDEV [10701.304913] add /devices/pci0000:00/0000:00:1e.0/0000:02:06.2/tifm_sd0:1/mmc_host/mmc1/mmc1:59b4 (mmc)
UDEV [10701.304945] add /devices/virtual/bdi/179:0 (bdi)
KERNEL[10701.306653] add /devices/pci0000:00/0000:00:1e.0/0000:02:06.2/tifm_sd0:1/mmc_host/mmc1/mmc1:59b4/block/mmcblk0 (block)
KERNEL[10701.306696] add /devices/pci0000:00/0000:00:1e.0/0000:02:06.2/tifm_sd0:1/mmc_host/mmc1/mmc1:59b4/block/mmcblk0/mmcblk0p1 (block)
UDEV [10701.408897] add /devices/pci0000:00/0000:00:1e.0/0000:02:06.2/tifm_sd0:1/mmc_host/mmc1/mmc1:59b4/block/mmcblk0 (block)
UDEV [10701.505486] add /devices/pci0000:00/0000:00:1e.0/0000:02:06.2/tifm_sd0:1/mmc_host/mmc1/mmc1:59b4/block/mmcblk0/mmcblk0p1 (block)
Not sure what else I can provide.
Any help would be greatly appreciated.
Also, as an aside, there's nothing in the man page about the call-back mechanism (unless you mean the scripts that can be run at mount/umount time)?
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Thanks for this.
I had the sd card plugged in when I started it, so I unplugged it and re-plugged it back in, which is why it's repeated.
$ sudo ldm -g 100 -u 1000 -V
/dev/sdb
dev_fs : (null)
dev_type : disk
dev_idtype : disk
/dev/mmcblk0
dev_fs : (null)
dev_type : disk
dev_idtype : (null)
/dev/mmcblk0p1
dev_fs : vfat
dev_type : partition
dev_idtype : (null)
/dev/sr0
dev_fs : (null)
dev_type : disk
dev_idtype : cd
/dev/sda
dev_fs : (null)
dev_type : disk
dev_idtype : disk
/dev/sda3
dev_fs : swap
/dev/loop0
dev_fs : (null)
dev_type : disk
dev_idtype : (null)
/dev/loop1
dev_fs : (null)
dev_type : disk
dev_idtype : (null)
/dev/loop2
dev_fs : (null)
dev_type : disk
dev_idtype : (null)
/dev/loop3
dev_fs : (null)
dev_type : disk
dev_idtype : (null)
/dev/loop4
dev_fs : (null)
dev_type : disk
dev_idtype : (null)
/dev/loop5
dev_fs : (null)
dev_type : disk
dev_idtype : (null)
/dev/loop6
dev_fs : (null)
dev_type : disk
dev_idtype : (null)
/dev/loop7
dev_fs : (null)
dev_type : disk
dev_idtype : (null)
/dev/mmcblk0
dev_fs : (null)
dev_type : disk
dev_idtype : (null)
/dev/mmcblk0p1
dev_fs : vfat
dev_type : partition
dev_idtype : (null)
Last edited by skanky (2014-05-08 13:29:54)
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
The latest git commit should fix the issue
It most certianly did.
Many thanks, that's excellent.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Having a similar issue.
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.
Offline
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..
Offline