You are not logged in.

#1 2013-05-21 19:16:23

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

hi there,

yes, i have used the search function on that, but still have unanswered questions.

1.
why do i need udev+udisks+udisks2+gvfs installed to dynamically mount internal (ntfs, ext4) partitions ?
If one these packages is missing, mounting an internal drive with "pcmanfm" is not possible.
I know how to static mount these drives via "fstab", but i want to mount them when i need the access.

2.
why are my removable devices not automatically mounted in "pcmanfm" when plugged in?
I have another OS (Lubuntu) running and this automatically recognizes when a cd is inserted or a usb stick is plugged in.
I have tried to install the package "gvfs-afc" and rebooted, still no usb stick to see. But when i enter:

sudo blkid -c /dev/null

The usb stick is listed as "sdb1"

I am using 64bit arch linux 3.9.3-1 with openbox+lxde.

Offline

#2 2013-05-22 00:01:22

sonoran
Member
From: sonoran desert
Registered: 2009-01-12
Posts: 161

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

Try SpaceFM + udevil, both in Community. There is also spacefm-gtk2 in the AUR.

http://ignorantguru.github.io/spacefm/

Offline

#3 2013-05-22 00:07:52

jasonwryan
Forum & Wiki Admin
From: .nz
Registered: 2009-05-09
Posts: 19,329
Website

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

LPS-Leipzig wrote:

why do i need udev+udisks+udisks2+gvfs installed to dynamically mount internal (ntfs, ext4) partitions ?

You don't. You need udev for a whole lot of other stuff, so leave that aside. To automount removable media, you can just use udisks and a helper like ud{iskie,evil}.
For an ntfs partition, you will also need that driver.

Comparing it with the Lubuntu; I am sure there is a lot more cruft preinstalled that makes this happen. In Arch, you just install what you need.
The udev page has the details.


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Online

#4 2013-05-22 08:11:27

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

hi sonoran,

i know spacefm already from another distro, i dont like the handling of spacefm although i know it provides a lot of desired functions and is highly configurable, but it looks too messy for me. Maybe someday a better gui for the libfm will be available.

I remember the distro "Bridge Linux" has made an elegant solution with udevil, it works fine!
Therefore i thought it can not be to difficult to copy that, but it didnt work or i didnt get it working.



hi jasonwryan,

yepp, i remember the times (with Debian and SuSe) before udev, so udev and ntfs-3g is all i need today, i thought so.

The problem is, when gvfs is not installed, no partitions show up in the filemanager (pcmanfm) although i can manually mount them via bash.
Installing gvfs also installs udisks2 as a dependency and so i end up using udev+udisks+udisks2+gvfs for automounting on demand my partitions and devices.

When you say that i can uninstall the gvfs+udisks2 packages and use udisks+udevil instead, i will give it a try and report the outcome.



Thanks so far, guys.

Last edited by LPS-Leipzig (2013-05-22 08:31:21)

Offline

#5 2013-05-22 09:08:19

bowshock
Member
From: Indonesia
Registered: 2013-02-08
Posts: 26

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

I remember removing udisks when udisks2 was introduced by regular update a few months ago. I don't think you need udisks if you already have udisks2. Your case may vary since I'm using KDE, and udisks2 is required by kdelibs.

Last edited by bowshock (2013-05-22 09:12:06)

Offline

#6 2013-05-22 09:33:27

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

bowshock wrote:

I remember removing udisks when udisks2 was introduced by regular update a few months ago. I don't think you need udisks if you already have udisks2. Your case may vary since I'm using KDE, and udisks2 is required by kdelibs.

yepp, i have tried that already a few month ago.
The problem is that libfm has udisks as dependancy, therefore uninstalling udisks means uninstalling libfm and pcmanfm.
Which is not a good idea, because lxde uses pcmanfm as default filemanager and i dont want to install a different one to perform a simple basic function of a filemanager.
I know that the distro Bridge Linux configured it the way jason mentioned, successfully. But i dont get it working...

Last edited by LPS-Leipzig (2013-05-22 10:31:38)

Offline

#7 2013-05-22 09:49:55

brebs
Member
Registered: 2007-04-03
Posts: 3,456

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

LPS-Leipzig wrote:

why do i need udev+udisks+udisks2+gvfs

Using the simplest method to mount, only udev is required.

Offline

#8 2013-05-22 10:27:43

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

jasonwryan wrote:

You don't. You need udev for a whole lot of other stuff, so leave that aside. To automount removable media, you can just use udisks and a helper like ud{iskie,evil}.
For an ntfs partition, you will also need that driver.

Comparing it with the Lubuntu; I am sure there is a lot more cruft preinstalled that makes this happen. In Arch, you just install what you need.
The udev page has the details.

so i have uninstalled the gvfs+udisks2 packages, rebooted and installed udevil-git and rebooted again.
No partition is shown in the filemanager now. I really dont get it. The udev wiki says udev needs rules but my "/etc/udev/rules.d" folder is empty.

The udisks wiki says that udisks and udisks2 are incompatible and that only one is needed and that udisks2 should be installed for gnome systems and udisks for xfce, but i have lxde installed. So it is not working with udisks and lxde (pcmanfm), when i try to install udisks2 additionally, it also does not work. Uninstalling udisks is also not possible because of the dependancy to libfm and so on...

Here is my /etc/udevil/udevil-user-harry.conf:

##############################################################################
#
# udevil configuration file    /etc/udevil/udevil.conf
#
# This file controls what devices, networks, and files users may mount and
# unmount via udevil (set suid).
# 
# IMPORTANT:  IT IS POSSIBLE TO CREATE SERIOUS SECURITY PROBLEMS IF THIS FILE
# IS MISCONFIGURED - EDIT WITH CARE
#
# Note:  For greater control for specific users, including root, copy this
# file to /etc/udevil/udevil-user-USERNAME.conf replacing USERNAME with the
# desired username (eg /etc/udevil/udevil-user-jim.conf).
#
# Format:
#   OPTION = VALUE[, VALUE, ...]
#
# DO NOT USE QUOTES except literally
# Lines beginning with # are ignored
#
##############################################################################


# To log all uses of udevil, set log_file to a file path:
#log_file = /var/log/udevil.log

# Approximate number of days to retain log entries (0=forever, max=60):
log_keep_days = 10


# allowed_types determines what fstypes can be passed by a user to the u/mount
# program, what device filesystems may be un/mounted implicitly, and what
# network filesystems may be un/mounted.
# It may also include the 'file' keyword, indicating that the user is allowed
# to mount files (eg an ISO file).  The $KNOWN_FILESYSTEMS variable may
# be included to include common local filesystems as well as those listed in
# /etc/filesystems and /proc/filesystems.
# allowed_types_USERNAME, if present, is used to override allowed_types for
# the specific user 'USERNAME'.  For example, to allow user 'jim' to mount
# only vfat filesystems, add:
# allowed_types_jim = vfat
# Setting allowed_types = * does NOT allow all types, as this is a security
# risk, but does allow all recognized types.
# allowed_types = $KNOWN_FILESYSTEMS, file, cifs, smbfs, nfs, curlftpfs, ftpfs, sshfs, davfs, tmpfs, ramfs
allowed_types = $KNOWN_FILESYSTEMS, file, ntfs, vfat


# allowed_users is a list of users permitted to mount and unmount with udevil.
# Wildcards (* or ?) may be used in the usernames.  To allow all users,
# specify "allowed_users=*".  UIDs may be included using the form UID=1000.
# For example:  allowed_users = carl, UID=1000, pre*
# Also note that permission to execute udevil may be limited to users belonging
# to the group that owns /usr/bin/udevil, such as 'plugdev' or 'storage',
# depending on installation.
# allowed_users_FSTYPE, if present, is used to override allowed_users when
# mounting or unmounting a specific fstype (eg nfs, ext3, file).
# Note that when mounting a file, fstype will always be 'file' regardless of
# the internal fstype of the file.
# For example, to allow only user 'bob' to mount nfs shares, add:
# allowed_users_nfs = bob
# The root user is NOT automatically allowed to use udevil in some cases unless
# listed here (except for unmounting anything or mounting fstab devices).
allowed_users = harry, root


# allowed_groups is a list of groups permitted to mount and unmount with
# udevil.  The user MUST belong to at least one of these groups.  Wildcards
# or GIDs may NOT be used in group names, but a single * may be used to allow
# all groups.
# Also note that permission to execute udevil may be limited to users belonging
# to the group that owns /usr/bin/udevil, such as 'plugdev' or 'storage',
# depending on installation.
# allowed_groups_FSTYPE, if present, is used to override allowed_groups when
# mounting or unmounting a specific fstype (eg nfs, ext3, file).  For example,
# to allow only members of the 'network' group to mount smb and nfs shares,
# use both of these lines:
# allowed_groups_smbfs = network
# allowed_groups_nfs = network
# The root user is NOT automatically allowed to use udevil in some cases unless
# listed here (except for unmounting anything or mounting fstab devices).
allowed_groups = storage


# allowed_media_dirs specifies the media directories in which user mount points
# may be located.  The first directory which exists and does not contain a
# wildcard will be used as the default media directory (normally /media or
# /run/media/$USER).
# The $USER variable, if included, will be replaced with the username of the
# user running udevil.  Wildcards may also be used in any directory EXCEPT the
# default.  Wildcards will not match a /
# allowed_media_dirs_FSTYPE, if present, is used to override allowed_media_dirs
# when mounting or unmounting a specific fstype (eg ext2, nfs).  For example,
# to cause /media/network to be used as the default media directory for
# nfs and ftpfs mounts, use these two lines:
# allowed_media_dirs_nfs   = /media/network, /media, /run/media/$USER
# allowed_media_dirs_ftpfs = /media/network, /media, /run/media/$USER
# NOTE: If you want only the user who mounted a device to have access to it
# and be allowed to unmount it, specify /run/media/$USER as the first
# allowed media directory.
# IMPORTANT:  If an allowed file is mounted to a media directory, the user may
# be permitted to unmount its associated loop device even though internal.
# INCLUDING /MNT HERE IS NOT RECOMMENDED.  ALL ALLOWED MEDIA DIRECTORIES
# SHOULD BE OWNED AND WRITABLE ONLY BY ROOT.
allowed_media_dirs = /media, /run/media/$USER


# allowed_devices is the first criteria for what block devices users may mount
# or unmount.  If a device is not listed in allowed_devices, it cannot be
# un/mounted (unless in fstab).  However, even if a device is listed, other
# factors may prevent its use.  For example, access to system internal devices
# will be denied to normal users even if they are included in allowed_devices.  
# allowed_devices_FSTYPE, if present, is used to override allowed_devices when
# mounting or unmounting a specific fstype (eg ext3, ntfs).  For example, to
# prevent all block devices containing an ext4 filesystem from being
# un/mounted use:
# allowed_devices_ext4 =
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "allowed_devices=*" which allows any device.  The recommended setting is
# allowed_devices = /dev/*
# WARNING:  ALLOWING USERS TO MOUNT DEVICES OUTSIDE OF /dev CAN CAUSE SERIOUS
# SECURITY PROBLEMS.  DO NOT ALLOW DEVICES IN /dev/shm
allowed_devices = /dev/*


# allowed_internal_devices causes udevil to treat any listed block devices as
# removable, thus allowing normal users to un/mount them (providing they are
# also listed in allowed_devices).
# allowed_internal_devices_FSTYPE, if present, is used to override
# allowed_internal_devices when mounting or unmounting a specific fstype
# (eg ext3, ntfs).  For example, to allow block devices containing a vfat
# filesystem to be un/mounted even if they are system internal devices, use:
# allowed_internal_devices_vfat = /dev/sdb*
# Some removable esata drives look like internal drives to udevil.  To avoid
# this problem, they can be treated as removable with this setting.
# WARNING:  SETTING A SYSTEM DEVICE HERE CAN CAUSE SERIOUS SECURITY PROBLEMS.
# allowed_internal_devices =


# allowed_internal_uuids and allowed_internal_uuids_FSTYPE work similarly to
# allowed_internal_devices, except that UUIDs are specified instead of devices.
# For example, to allow un/mounting of an internal filesystem based on UUID:
# allowed_internal_uuids = cc0c4489-8def-1e5b-a304-ab87c3cb626c0
# WARNING:  SETTING A SYSTEM DEVICE HERE CAN CAUSE SERIOUS SECURITY PROBLEMS.
# allowed_internal_uuids = 


# forbidden_devices is used to prevent block devices from being un/mounted
# even if other settings would allow them (except devices in fstab).
# forbidden_devices_FSTYPE, if present, is used to override
# forbidden_devices when mounting or unmounting a specific fstype
# (eg ext3, ntfs).  For example, to prevent device /dev/sdd1 from being
# mounted when it contains an ntfs filesystem, use:
# forbidden_devices_ntfs = /dev/sdd1
# NOTE: device node paths are canonicalized before being tested, so forbidding
# a link to a device will have no effect.
forbidden_devices =


# allowed_networks determines what hosts may be un/mounted by udevil users when
# using nfs, cifs, smbfs, curlftpfs, ftpfs, or sshfs.  Hosts may be specified
# using a hostname (eg myserver.com) or IP address (192.168.1.100).
# Wildcards may be used in hostnames and IP addresses, but CIDR notation 
# (192.168.1.0/16) is NOT supported.  IP v6 is supported.  For example:
# allowed_networks = 127.0.0.1, 192.168.1.*, 10.0.0.*, localmachine, *.okay.com
# Or, to prevent un/mounting of any network shares, set:
# allowed_networks =
# allowed_networks_FSTYPE, if present, is used to override allowed_networks
# when mounting or unmounting a specific network fstype (eg nfs, cifs, sshfs,
# curlftpfs).  For example, to limit nfs and samba shares to only local
# networks, use these two lines:
# allowed_networks_nfs = 192.168.1.*, 10.0.0.*
# allowed_networks_cifs = 192.168.1.*, 10.0.0.*
allowed_networks = *


# forbidden_networks and forbidden_networks_FSTYPE are used to specify networks
# that are never allowed, even if other settings allow them (except fstab).
# NO REVERSE LOOKUP IS PERFORMED, so including bad.com will only have an effect
# if the user uses that hostname.  IP lookup is always performed, so forbidding
# an IP address will also forbid all corresponding hostnames.
forbidden_networks = 


# allowed_files is used to determine what files in what directories may be
# un/mounted.  A user must also have read permission on a file to mount it.
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "allowed_files=*" which allows any file.  For example, to allow only
# files in the /share directory to be mounted, use:
# allowed_files = /share/*
# NOTE:  Specifying allowed_files_FSTYPE will NOT work because the fstype of
# files is always 'file'.
allowed_files = *


# forbidden_files is used to specify files that are never allowed, even if
# other settings allow them (except fstab).  Specify a full path.
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "forbidden_files = *".
# NOTE: file paths are canonicalized before being tested, so forbidding
# a link to a file will have no effect.
forbidden_files = 


# default_options specifies what options are always included when performing
# a mount, in addition to any options the user may specify.
# Note:  When a device is present in /etc/fstab, and the user does not specify
# a mount point, the device is mounted with normal user permissions using
# the fstab entry, without these options.
# default_options_FSTYPE, if present, is used to override default_options
# when mounting a specific fstype (eg ext2, nfs).
# The variables $USER, $UID, and $GID are changed to the user's username, UID,
# and GID.
# FOR GOOD SECURITY, default_options SHOULD ALWAYS INCLUDE: nosuid,noexec,nodev
# WARNING:  OPTIONS PRESENT OR MISSING CAN CAUSE SERIOUS SECURITY PROBLEMS.
default_options           = nosuid, noexec, nodev, noatime
default_options_file      = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, ro
# mount iso9660 with 'ro' to prevent mount read-only warning
default_options_iso9660   = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, ro, utf8
default_options_udf       = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_vfat      = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID, utf8
default_options_msdos     = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID
default_options_umsdos    = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID
default_options_ntfs      = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, utf8
default_options_cifs      = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_smbfs     = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_sshfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, nonempty, allow_other
default_options_curlftpfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, nonempty, allow_other
default_options_ftpfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_davfs     = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_tmpfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_ramfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID


# allowed_options determines all options that a user may specify when mounting.
# All the options used in default_options above must be included here too, or
# they will be rejected.  If the user attempts to use an option not included
# here, an error will result.  Wildcards may be used.
# allowed_options_FSTYPE, if present, is used to override allowed_options
# when mounting a specific fstype (eg ext2, nfs).
# The variables $USER, $UID, and $GID are changed to the user's username, UID,
# and GID.
# If you want to forbid remounts, remove 'remount' from here.
# WARNING:  OPTIONS HERE CAN CAUSE SERIOUS SECURITY PROBLEMS - CHOOSE CAREFULLY
allowed_options           = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID, ro, rw, sync, flush, iocharset=*, utf8, remount
allowed_options_nfs       = nosuid, noexec, nodev, noatime, ro, rw, sync, remount, port=*, rsize=*, wsize=*, hard, proto=*, timeo=*, retrans=*
allowed_options_cifs      = nosuid, noexec, nodev, ro, rw, remount, port=*, user=*, username=*, pass=*, password=*, guest, domain=*, uid=$UID, gid=$GID, credentials=*
allowed_options_smbfs     = nosuid, noexec, nodev, ro, rw, remount, port=*, user=*, username=*, pass=*, password=*, guest, domain=*, uid=$UID, gid=$GID, credentials=*
allowed_options_sshfs     = nosuid, noexec, nodev, noatime, ro, rw, uid=$UID, gid=$GID, nonempty, allow_other, idmap=user, BatchMode=yes, port=*
allowed_options_curlftpfs = nosuid, noexec, nodev, noatime, ro, rw, uid=$UID, gid=$GID, nonempty, allow_other, user=*
allowed_options_ftpfs     = nosuid, noexec, nodev, noatime, ro, rw, port=*, user=*, pass=*, ip=*, root=*, uid=$UID, gid=$GID


# mount_point_mode, if present and set to a non-empty value, will cause udevil
# to set the mode (permissions) on the moint point after mounting  If not
# specified or if left empty, the mode is not changed.  Mode must be octal
# starting with a zero (0755).
# mount_point_mode_FSTYPE, if present, is used to override mount_point_mode
# when mounting a specific fstype (eg ext2, nfs).
# NOT SETTING A MODE CAN HAVE SECURITY IMPLICATIONS FOR SOME FSTYPES
mount_point_mode = 0755
# don't set a mode for some types:
mount_point_mode_sshfs =
mount_point_mode_curlftpfs =
mount_point_mode_ftpfs =


# Use the settings below to change the default locations of programs used by
# udevil, or (advanced topic) to redirect commands to your scripts.
# When substituting scripts, make sure they are root-owned and accept the
# options used by udevil (for example, the mount_program must accept --fake,
# -o, -v, and other options valid to mount.)
# Be sure to specify the full path and include NO OPTIONS or other arguments.
# These programs may also be specified as configure options when building
# udevil.
# THESE PROGRAMS ARE RUN AS ROOT
# mount_program   = /bin/mount
# umount_program  = /bin/umount
# losetup_program = /sbin/losetup
# setfacl_program = /usr/bin/setfacl


# validate_exec specifies a program or script which provides additional
# validation of a mount or unmount command, beyond the checks performed by
# udevil.  The program is run as a normal user (if root runs udevil,
# validate_exec will NOT be run).  The program is NOT run if the user is
# mounting a device without root priviledges (a device in fstab).
# The program is passed the username, a printable description of what is
# happening, and the entire udevil command line as the first three arguments.
# The program must return an exit status of 0 to allow the mount or unmount
# to proceed.  If it returns non-zero, the user will be denied permission.
# For example, validate_exec might specify a script which notifies you
# of the command being run, or performs additional steps to authenticate the
# user.
# Specify a full path to the program, with NO options or arguments.
# validate_exec =


# validate_rootexec works similarly to validate_exec, except that the program
# is run as root.  validate_rootexec will also be run if the root user runs
# udevil.  If both validate_exec and validate_rootexec are specified, 
# validate_rootexec will run first, followed by validate_exec.
# The program must return an exit status of 0 to allow the mount or unmount
# to proceed.  If it returns non-zero, the user will be denied permission.
# Unless you are familiar with writing root scripts, it is recommended that
# rootexec settings NOT be used, as it is easy to inadvertently open exploits.
# THIS PROGRAM IS ALWAYS RUN AS ROOT, even if the user running udevil is not.
# validate_rootexec =


# success_exec is run after a successful mount, remount, or unmount.  The 
# program is run as a normal user (if root runs udevil, success_exec
# will NOT be run).
# The program is passed the username, a printable description of what action
# was taken, and the entire udevil command line as the first three arguments.
# The program's exit status is ignored.
# For example, success_exec might run a script which informs you of what action
# was taken, and might perform further actions.
# Specify a full path to the program, with NO options or arguments.
# success_exec =


# success_rootexec works similarly to success_exec, except that the program is
# run as root.  success_rootexec will also be run if the root user runs udevil.
# If both success_exec and success_rootexec are specified,  success_rootexec
# will run first, followed by success_exec.
# Unless you are familiar with writing root scripts, it is recommended that
# rootexec settings NOT be used, as it is easy to inadvertently open exploits.
# THIS PROGRAM IS ALWAYS RUN AS ROOT, even if the user running udevil is not.
# success_rootexec =

I have no idea what to do next, the only way it works, is the combination i mentioned in the title of this post. Any suggestion to solve that problem?

Offline

#9 2013-05-22 10:31:18

Gusar
Member
Registered: 2009-08-25
Posts: 3,470

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

Compile libfm with --disable-udisks. This way it won't use it's internal udisks handling, it'll use GIO. Which means either gvfs/udisks2 or udevil.

Offline

#10 2013-05-22 12:57:34

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

i dont know how to compile libfm only and then merge it with pcmanfm.
There is a package called "libfm-git" in the AUR which is based on glib/GIO.

Offline

#11 2013-05-22 13:37:27

Gusar
Member
Registered: 2009-08-25
Posts: 3,470

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

Make friends with this awesome tool called ABS. The wiki has all the details.

Offline

#12 2013-05-22 14:23:11

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

well, i think that this is not simple. The libfm-git version also didnt work and no, i dont want to install the ABS and its tons of source files...

Maybe it is not related to archlinux because the dependancy problem of libfm+udisks and the fact that pcmanfm needs gvfs which has udisks2 as dependancy comes from lxde.
But why are there other archlinux derivates like bridgelinux or manjaro which dont have that problem?
Am i the only one using archlinux with lxde trying to mount my devices with pcmanfm when i need them?

Last edited by LPS-Leipzig (2013-05-22 14:58:07)

Offline

#13 2013-05-22 15:01:53

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

LPS-Leipzig wrote:

well, i think that this is not simple. The libfm-git version also didnt work and no, i dont want to install the ABS and its tons of source files...

Maybe it is not related to archlinux because the dependancy problem of libfm+udisks and the fact that pcmanfm needs gvfs which has udisks2 as dependancy comes from lxde.
But why are there other archlinux derivates like bridgelinux or manjaro which dont have that problem?
Am i the only one using archlinux with lxde trying to mount my devices with pcmanfm when i need them?

Dude, you are really not making this easy on yourself.  If you learned even a little bit about ABS, you would have found out that it is not the sources you are downloading, it is just the PKGBUILDs (or more precisely the PKGBUILDs and any patches and install files).  On my machine it takes a whopping 46MB which includes all the testing stuff.  A bit more learning and you would have found out that you can use ABS to download the build scripts for a single package.

If you are not willing to learn how to use the tools available to you, or try anything new, it is rather pointless to ask people here to help you.

Offline

#14 2013-05-22 15:46:49

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

WonderWoofy wrote:

Dude, you are really not making this easy on yourself.  If you learned even a little bit about ABS, you would have found out that it is not the sources you are downloading, it is just the PKGBUILDs (or more precisely the PKGBUILDs and any patches and install files).  On my machine it takes a whopping 46MB which includes all the testing stuff.  A bit more learning and you would have found out that you can use ABS to download the build scripts for a single package.

If you are not willing to learn how to use the tools available to you, or try anything new, it is rather pointless to ask people here to help you.

I know it is difficult for you, but please try to post ONTOPIC!
You posting doesnt help or inform anybody...

Offline

#15 2013-05-22 16:04:57

Gusar
Member
Registered: 2009-08-25
Posts: 3,470

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

Actually, his post is very on topic and *very* informative. But if you refuse to take the advice you're given, suit yourself.

Offline

#16 2013-05-22 16:55:18

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

The question was "why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?" and not how do i use the ABS to build or manipulate the libfm package.
So why should i try an option i am not interested in at this point? If i would think the coexistence of udev+udisks+udisks2+gvfs is steeling my sleep, then i would consider using the ABS.

The text "you are not willing to learn how to use the tools available to you, or try anything new," is not helping or informing, it is offending and a stupid projection anyway.

Offline

#17 2013-05-22 17:22:00

teateawhy
Member
From: GER
Registered: 2012-03-05
Posts: 1,060
Website

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

LPS-Leipzig wrote:

I know how to static mount these drives via "fstab", but i want to mount them when i need the access.

Is there a reason not to use fstab besides that you are not willing to?

LPS-Leipzig wrote:

The question was "why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

You do not need udev installed. It is not even a package. But you need the udev functionality for archlinux.
You do not need udisks and udisks2 installed at the same time.
You do not need gvfs for automounting.

Offline

#18 2013-05-22 17:44:59

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

The answer to your question has been answered over and over again.  You don't strictly need all that crap installed.  But you use a binary distribution, where the packages are compiled in a certain way.  Therefore the removal of some of these packages, that I am assuming you think are unnecessary, can be accomplished by compiling the packages with different configuration options.  So they are only necessary if you insist on using the particular set of tools that you would like to use (pcmanfm and gvfs) and you insist on using only the packages from the repositories.

I don't think that my intention was to offend you by asking you why you are asking for advice you are not willing to take.  In fact, my question I think still stands.  You have gotten a number of answers here, both suggesting you use different packages/tools to accomplish the same thing and by modifying the packages in a way that will allow you to achieve the same thing without all those dependencies.  It seems like so far, you have tried the different package approach and failed, so you have deemed that impossible.  And you have also indicated that the amazing tools for package building and modification are too much for you to learn, so are also an impossibility.

I don't know what more you expect from this community.  Arch Linux is a wonderful opportunity to learn about Linux, but only if you are willing to learn.


Edit: BTW, libfm is only a dependency of pcmanfm.  So something as simple as using a different file manager would accomplish the removal of udisks... that is if you are willing to learn to use the proper pacman switches to remove the pacage and its dependencies...

Last edited by WonderWoofy (2013-05-22 17:47:08)

Offline

#19 2013-05-24 10:47:29

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

teateawhy wrote:

Is there a reason not to use fstab besides that you are not willing to?

No reason, you are right. I can just use my fstab and have the access to my ntfs and ext4 partitions.
I thought it would be an increase of my overall system security to not have all my partitions mounted all the time.
Like 13 years ago (or more) static mount via fstab was the normal way, you got me i´m a victim of the laziness produced by all the autoconfig scripts.
Allthough i still have a configured fstab as backup, it sounded so nice just to install LXDE and thats it.

teateawhy wrote:

You do not need udev installed. It is not even a package. But you need the udev functionality for archlinux.
You do not need udisks and udisks2 installed at the same time.
You do not need gvfs for automounting.

I remember very well the times before hwdetect and udev occured. Before these automatic hardware detection scripts came up, a normal suse or slackware installation could become quickly a real pain in the ass, so i´m quite thankful for udev.

The reason for this post was that i also think the combination udisks+udisks2 is redundant.
Udev+udisks would be enough to do the job and i know that because i am using more than one linux distri on my system.

But auto mounting on demand a filesystem on my optical drive or my usb stick without gvfs?
I dont know how to do that, probably via udev rules, but i didnt need to do that since gvfs is available.

Dont get me wrong, i´m quite happy with my archlinux install, nearly everything is working and looking the way i wanted it.
Beside the questions in my first post wink

Offline

#20 2013-05-24 12:38:42

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

WonderWoofy wrote:

The answer to your question has been answered over and over again.  You don't strictly need all that crap installed.  But you use a binary distribution, where the packages are compiled in a certain way.  Therefore the removal of some of these packages, that I am assuming you think are unnecessary, can be accomplished by compiling the packages with different configuration options.

What a detour, why do you not suggest a simple "sudo pacman -Rd udisks"?

So they are only necessary if you insist on using the particular set of tools that you would like to use (pcmanfm and gvfs) and you insist on using only the packages from the repositories.

Dont know what you mean, i tried it as advised by jasonwryan with the git version of udevil and wrote the outcome 5 posts before you wrote that...

I don't think that my intention was to offend you by asking you why you are asking for advice you are not willing to take.  In fact, my question I think still stands.  You have gotten a number of answers here, both suggesting you use different packages/tools to accomplish the same thing and by modifying the packages in a way that will allow you to achieve the same thing without all those dependencies.

You didnt read post #8 right?

And you have also indicated that the amazing tools for package building and modification are too much for you to learn, so are also an impossibility.

Thats another crazy projection, where do you read this crazy stuff?

I don't know what more you expect from this community.  Arch Linux is a wonderful opportunity to learn about Linux, but only if you are willing to learn.

Amen!

So something as simple as using a different file manager would accomplish the removal of udisks...

Now i can be sure that you did not read what i have written, read post #6

that is if you are willing to learn to use the proper pacman switches to remove the pacage and its dependencies...

This is the line you have added with the "EDIT" right? The whole rest of your post is questionable...

I would say, vaya por dios, just grep your bible and try your luck on the next one wink

Offline

#21 2013-05-24 14:23:38

anonymous_user
Member
Registered: 2009-08-28
Posts: 3,058

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

LPS-Leipzig wrote:

What a detour, why do you not suggest a simple "sudo pacman -Rd udisks"?

Because using -Rdd to remove a dependency is not the best way. You should recompile the program to not use the dependency.

LPS-Leipzig wrote:

Dont know what you mean, i tried it as advised by jasonwryan with the git version of udevil and wrote the outcome 5 posts before you wrote that...

You don't need the git version, the normal udevil from community repo is enough. Also in order to actually get automounting, you have to run devmon. You can either enable the systemd service or put in your autostart script (like .xinitrc).

Offline

#22 2013-05-25 17:29:44

LPS-Leipzig
Member
Registered: 2013-05-21
Posts: 21

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

i have tried both versions, the repository and the git version, with the same result...

a simple "sudo systemctl enable devmon.service" produced the errormessage "no such file or directory".
Checking the "/usr/lib/systemd/system" folder, shows that the file "devmon.service" is existent.
I dont understand why the service can not be activated although it is installed.

As i dont have a ".xinitrc" i have tried to autostart it with "~/user/.config/autostart/devmon.desktop", alternatively "~/user/.config/openbox/autostart.sh" with "devmon &".
The point is, although devmon is running, pcmanfm is not showing any devices or partitions when "gvfs" is not installed.
No internal drives or partitions and no external ones.

Last edited by LPS-Leipzig (2013-05-25 18:43:44)

Offline

#23 2013-05-26 02:35:02

anonymous_user
Member
Registered: 2009-08-28
Posts: 3,058

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

LPS-Leipzig wrote:

a simple "sudo systemctl enable devmon.service" produced the errormessage "no such file or directory".
Checking the "/usr/lib/systemd/system" folder, shows that the file "devmon.service" is existent.
I dont understand why the service can not be activated although it is installed.

To enable the service it should be:

sudo systemctl enable devmon@username.service

Just replace username.

LPS-Leipzig wrote:

The point is, although devmon is running, pcmanfm is not showing any devices or partitions when "gvfs" is not installed.

Because PCManFM depends on gvfs for mounting.

Offline

#24 2013-05-26 04:07:28

jasonwryan
Forum & Wiki Admin
From: .nz
Registered: 2009-05-09
Posts: 19,329
Website

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

anonymous_user wrote:
LPS-Leipzig wrote:

The point is, although devmon is running, pcmanfm is not showing any devices or partitions when "gvfs" is not installed.

Because PCManFM depends on gvfs for mounting.


No, it doesn't. An active session and udiskie with udev helper is sufficient for PCManFM to automount.


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Online

#25 2013-05-26 05:23:24

anonymous_user
Member
Registered: 2009-08-28
Posts: 3,058

Re: why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

I thought PCManFM/libfm did use udisks2/gvfs but either it was changed or I have bad memory.

Offline

Board footer

Powered by FluxBB