Package Details: pmount 0.9.23-17

Git Clone URL: https://aur.archlinux.org/pmount.git (read-only, click to copy)
Package Base: pmount
Description: mount removable devices as normal user
Upstream URL: https://salsa.debian.org/debian/pmount
Licenses: GPL2
Submitter: Barthalion
Maintainer: ralphptorres
Last Packager: ralphptorres
Votes: 96
Popularity: 0.000000
First Submitted: 2012-12-12 19:55 (UTC)
Last Updated: 2025-03-12 04:23 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

dreieck commented on 2023-07-24 08:46 (UTC)

Suggesion: Add optdepends=('cryptsetup: For mounting of encrypted devices.').

Regards!

dreieck commented on 2023-07-24 08:16 (UTC) (edited on 2023-07-24 13:05 (UTC) by dreieck)

Regarding the problem of not beeing able to mount vfat USB drives anymore:

I created a topic ↗ in the Arch Linux and ↗ in the Artix Linux forum.

Regards!

dreieck commented on 2023-07-24 08:10 (UTC) (edited on 2023-07-24 08:10 (UTC) by dreieck)

$url target does not exist: Server not found.

DNS resolving fails: dig pmount.alioth.debian.org | grep '.' | grep -v '^;':

debian.org.     542 IN  SOA denis.debian.org. hostmaster.debian.org. 2023072430 1800 600 1814400 600

Regards!

calamity commented on 2023-06-05 20:59 (UTC)

@frankspace: I'm getting the same errors on my Arch.

@Lone_Wolf: ntfs-3g and dosfstools are installed. I'm trying to mount a fat32 fs, as is frankspace, because he wrote pmount -t vfat.

Lone_Wolf commented on 2023-06-03 10:27 (UTC) (edited on 2023-06-03 10:29 (UTC) by Lone_Wolf)

Did some further checking and it appears pmount doesn't work with the ntfs3 in-kernel module, only with ntfs-3g (which goes over fuse2) .

I haven't tried to apply the udev rukle mnetioned in https://wiki.archlinux.org/title/NTFS#Known_issues

Does it make a diference if you install ntfs-3g ?

For clarity : dosfstools is installed ?

frankspace commented on 2023-06-01 12:35 (UTC)

Thank you! However, it's actually a FAT32 stick, and I get the exact same error when I try to use pmount to mount a LUKS-encrypted drive (which is actually EXT4 inside the encryption). So anyway, I replaced exfat-utils with exfat progs, rebooted, and recompiled pmount in a chroot. That did fix the first two lines about FUSE, so this was obviously something I should have done anyway. However, it didn't otherwise fix anything else. I'm prepared to accept that the problem is with my box and not with pmount itself, but I truly have no clue where to continue the hunt. I appreciate the hint, though.

Lone_Wolf commented on 2023-06-01 07:30 (UTC)

pmount can mount/unmount ntfs on usb stick fine here, your issue looks like it's fuse related.

Since 5.4 there is a native exfat kernel module, try removing exfat-utils. (you may want/need to install the exfatprogs package)

frankspace commented on 2023-06-01 02:55 (UTC) (edited on 2023-06-01 03:23 (UTC) by frankspace)

I have no problem compiling, but it seems the update to util-linux 2.39 broke pmount somehow. Unfortunately, as an Artix user, I'm not sure there's a whole lot I can do in the way of a bug report, either, and I have no clue how to go about fixing it. EDIT: I spoke too soon; pmount is definitely broken, but downgrading util-linux didn't help. I'm getting the following error when I try to use pmount now:

FUSE exfat 1.4.0 (libfuse2)
FUSE exfat 1.4.0 (libfuse2)
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

If I try to specify pmount -t vfat /dev/sda1, I just get told mount: /media/sda1: not mount point or bad option. Running the same with sudo gets the same thing. I'm stumped and don't even know where to begin.

Valenoern commented on 2023-03-22 23:12 (UTC)

I successfully built this package on aarch64.

But I had one problem with ./configure I don't quite understand. I started from a minimal Manjaro image and pamac said:

UNAME_MACHINE = aarch64
UNAME_RELEASE = 6.1.12-1-MANJARO-ARM
UNAME_SYSTEM  = Linux
UNAME_VERSION = #1 SMP PREEMPT Tue Feb 14 22:16:04 UTC 2023
configure: error: cannot guess build type; you must specify one
==> ERROR: A failure occurred in build().

I feel like this is actually my system missing a package that would give me "configure guess information", but I couldn't find that package, and every guide said it's an issue with ./configure and to contact package maintainers.

To build on my system, I had to change the ./configure line to:

./configure --prefix=/usr --disable-hal --with-cryptsetup-prog=/usr/bin/cryptsetup \
    --build=aarch64-unknown-linux-gnu

dreieck commented on 2021-05-30 12:13 (UTC)

$url does not exist:

wget -O /dev/null http://pmount.alioth.debian.org/:

--2021-05-30 14:12:30--  http://pmount.alioth.debian.org/
Resolving pmount.alioth.debian.org (pmount.alioth.debian.org)... failed: Name or service not known.
wget: unable to resolve host address ‘pmount.alioth.debian.org’

Can you please update upstream URL?

Thanks for maintaining!