From owner-freebsd-mobile@FreeBSD.ORG Tue Mar 29 10:44:17 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B140616A4CE; Tue, 29 Mar 2005 10:44:17 +0000 (GMT) Received: from mail23.syd.optusnet.com.au (mail23.syd.optusnet.com.au [211.29.133.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD74043D68; Tue, 29 Mar 2005 10:44:16 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j2TAhnfd022240 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 29 Mar 2005 20:43:49 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j2TAhm7l070056; Tue, 29 Mar 2005 20:43:48 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j2TAhlOk070055; Tue, 29 Mar 2005 20:43:47 +1000 (EST) (envelope-from pjeremy) Date: Tue, 29 Mar 2005 20:43:47 +1000 From: Peter Jeremy To: Stijn Hoop Message-ID: <20050329104347.GB69824@cirb503493.alcatel.com.au> References: <20050328131318.GC14532@cicely12.cicely.de> <31970.1112016818@critter.freebsd.dk> <20050329.011148.69987814.imp@bsdimp.com> <20050329081605.GA57775@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050329081605.GA57775@pcwin002.win.tue.nl> User-Agent: Mutt/1.4.2i cc: current@freebsd.org cc: vova@fbsd.ru cc: mdodd@freebsd.org cc: freebsd-mobile@freebsd.org cc: phk@phk.freebsd.dk cc: julian@elischer.org cc: ticso@cicely.de Subject: Re: Reattach/redetect allways connected umass device - is it possible ? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 10:44:17 -0000 On Tue, 2005-Mar-29 10:16:05 +0200, Stijn Hoop wrote: >From a desktop user experience point of view, it is rather nice to get >a notification if and when removable media disappears, without >continously polling said media. There's no reason why the kernel couldn't regularly poll removable media as long as it didn't interfere with normal operation of the device or intrude upon the user (who remembers Amiga FDD's ticking?). > This statement intentionally ignores >the question of how to get such an event through the kernel to >userspace. I don't believe this is a problem. For a command line interface, you run "ls" and get a snapshot of the directory contents - you don't expect the output from an old "ls" to magically update itself when a file is deleted, you re-run "ls". GUI file browsers are more of a problem but as long as the browser doesn't cache the results from one invocation to another, this wouldn't seem to be a problem. In any case, the majority of the computer users seem quite happy with a user interface that, upon ejecting a removable medium and inserting a different medium, will happily display the union of the contents of the old and new media. It would take a seriously warped mind to manage anything so non-intuitive so anything we achieve will be an improvement over the status quo. -- Peter Jeremy