From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Kay Sievers <kay@vrfy.org>
Cc: Takashi Iwai <tiwai@suse.de>, Jens Axboe <axboe@kernel.dk>,
Oliver Neukum <oneukum@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to fix CDROM/DVD eject mess?
Date: Mon, 2 Feb 2015 19:34:38 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.11.1502021915110.22715@eddie.linux-mips.org> (raw)
In-Reply-To: <CAPXgP10BwNkXqMPGbRkjgt3R9rMv6sZ9EX1nP9X99cAfmcaOXw@mail.gmail.com>
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?
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.
All I want to say here is there seems to be a policy hidden somewhere
here where it should not. It's up to the user to decide what suits him or
her. We just need to give them the right tools.
> It is just a hardware button event which should not be masked out for
> rather weird reasons.
Precisely, and I should have a way to control it. If I used a GUI, I
might want the event to pop up a window with the list of current users
(accessing processes) of the device, perhaps asking if to terminate them.
Or flip a relay to make my kettle boil water.
FWIW,
Maciej
next prev parent reply other threads:[~2015-02-02 19:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 13:20 Takashi Iwai
2015-02-02 19:03 ` Kay Sievers
2015-02-02 19:34 ` Maciej W. Rozycki [this message]
2015-02-02 19:45 ` Kay Sievers
2015-02-02 21:12 ` Maciej W. Rozycki
2015-02-03 12:36 ` Takashi Iwai
2015-02-03 8:52 ` Oliver Neukum
2015-02-03 13:34 ` One Thousand Gnomes
2015-02-03 17:53 ` Theodore Ts'o
2015-02-02 20:02 ` Austin S Hemmelgarn
2015-02-02 20:53 ` Ondrej Zary
2015-02-03 12:31 ` Takashi Iwai
2015-02-03 13:39 ` One Thousand Gnomes
2015-02-03 13:49 ` Takashi Iwai
2015-02-03 13:40 ` Austin S Hemmelgarn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.11.1502021915110.22715@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=axboe@kernel.dk \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®