Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933473AbbBBTqO (ORCPT ); Mon, 2 Feb 2015 14:46:14 -0500 Received: from mail-we0-f169.google.com ([74.125.82.169]:59580 "EHLO mail-we0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754962AbbBBTqL (ORCPT ); Mon, 2 Feb 2015 14:46:11 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Kay Sievers Date: Mon, 2 Feb 2015 20:45:50 +0100 Message-ID: Subject: Re: How to fix CDROM/DVD eject mess? To: "Maciej W. Rozycki" Cc: Takashi Iwai , Jens Axboe , Oliver Neukum , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1905 Lines: 40 On Mon, Feb 2, 2015 at 8:34 PM, Maciej W. Rozycki wrote: > On Mon, 2 Feb 2015, Kay Sievers wrote: > >> > I thought that fixing the udev behavior would solve the problem. But >> > it turned out that I was too naive. A bigger problem is that all >> > user-space stuff misinterprets DISK_EVENT_EJECT_REQUEST event: they >> > see this as if the disk is *ready* to be ejected. KDE, for example, >> > dismisses the DVD icon when it receives this event even if it's still >> > mounted. >> >> It is not really about being "ready to eject", if the user presses the >> button, the user does not want to wait for anything else than actually >> ejecting the media as fast as possible. It is the same as ripping out >> a USB cable. It needs to work, no matter if things are mounted or >> busy. > > All the technical details aside, this is a bold statement -- how do you > know what the user actually wants? By working with people who spent a lot of time with the questions what the default behavior of user interfaces should be. Buttons, especially physical ones, need to give immediate feedback to the user. If they don't give it it, people will look for something else to get what they want. > I for one want to see the medium locked if in use, just as it has been > since 1990s. If I wanted to do an emergency eject (the equivalent of > ripping out a USB cable), then I would use a paperclip in the manual eject > hole. So you've got a counterexample to your assertion now. All people > are not the same. It's just the current default setup and intentional behavior. You or your distribution can for sure implement something else. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/