From owner-freebsd-questions@FreeBSD.ORG Wed Dec 31 09:33:58 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E71C9DC2 for ; Wed, 31 Dec 2014 09:33:57 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B99C64FC6 for ; Wed, 31 Dec 2014 09:33:56 +0000 (UTC) Received: from r56.edvax.de (port-92-195-39-170.dynamic.qsc.de [92.195.39.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 9429A3D23E; Wed, 31 Dec 2014 10:26:28 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id sBV9QRnL003738; Wed, 31 Dec 2014 10:26:27 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Wed, 31 Dec 2014 10:26:27 +0100 From: Polytropon To: Roland Smith Subject: Re: Xwindow advise needed Message-Id: <20141231102627.c66b098b.freebsd@edvax.de> In-Reply-To: <20141231090208.GA23105@slackbox.erewhon.home> References: <55358.128.135.70.2.1419874589.squirrel@cosmo.uchicago.edu> <20141229235045.b8156cdf.freebsd@edvax.de> <20141231044147.fe7a9983.freebsd@edvax.de> <20141231090208.GA23105@slackbox.erewhon.home> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2014 09:33:58 -0000 On Wed, 31 Dec 2014 10:02:08 +0100, Roland Smith wrote: > On Wed, Dec 31, 2014 at 04:41:47AM +0100, Polytropon wrote: > > On Mon, 29 Dec 2014 20:25:53 -0700 (MST), Warren Block wrote: > > > On Mon, 29 Dec 2014, Polytropon wrote: > > > > > > > > For a long time, Xfce has been considered the "less fatty > > > > desktop" in comparison to the "big players" Gnome and KDE. > > > > But with the growing incompatibilities btweeen FreeBSD and > > > > Linux (the system Xfce is primarily being developed on and > > > > for), you might experience missing functionality. > > > > > > I use xfce. The only thing that does not work on FreeBSD, as far as I > > > know, is automounting. There are other ways to do that. I just > > > manually mount stuff. Otherwise, xfce has the standard desktop features > > > without being resource-hungry or having a huge list of dependencies. > > > > The problem is not the automounter itself. It's its > > integration with the GUI elements, in two ways: > > > > 1st, when the automounter mounts a device which has > > been appearing, either by a label or by a device name, > > this new mountpoint must be "picked up" by the GUI > > and be shown on the desktop. > > It was my impression that the new automount/autofs in 10.1 does *not* do that. > AFAICT it tries to mount a filesystem when a directory is accessed. > Which is nice for say NFS or SMBFS, but doesn't cater to the common use of > using a memstick. As far as I remember, the system's amd itsel (not the "automounter" port) is intended for exactly that task, and primary targeting the use of NFS. It's not intended primarily for the use with removable media, but _can_ be used for that task. The different approach via devd (in Linux: based on HAL and DBus, now deprecated, replaced by udisk et al., probably on the road to deprecation, replaced by kdbus) is that if a matching device appears, the device is being identified and mounted. A notification is then provided in some way, for example via FAM (file alteration monitor) that watches the mountpoint root directory (for example /media) for a new entry, causing the GUI to display an icon shortcut, with a context menu entry of matching actions (like unmount). As there is no "timeout", unmounting has to be ordered manually, either by point & click, or via command line. Today's automatical mounts have become a great mystery to me, I don't entirely understand which parts are involved in which way, and how they work, or why they work, so I'd be happy about a working solution for the settings where this is an "urgent" requirement... :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...