linux-kernel - Re: How to fix CDROM/DVD eject mess?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 2 Feb 2015 21:12:34 +0000 (GMT)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Kay Sievers <kay@...y.org>
cc:	Takashi Iwai <tiwai@...e.de>, Jens Axboe <axboe@...nel.dk>,
	Oliver Neukum <oneukum@...e.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: How to fix CDROM/DVD eject mess?

On Mon, 2 Feb 2015, Kay Sievers wrote:

> >  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.

 It still covers a group of people only, not all of them.  A UI is a 
convention, there may be different ones.  There is little if anything more 
frustrating in interacting with computers than an UI that "knows better" 
what I want to do than I do, with no way to override the built-in logic.  
I am not a statistical sample, I am an individual with my own preferences.  
I have suffered from such built-in assumptions myself and I talked many 
times to people who complained about them too.

> >  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.

 Fair enough, but if this is a matter of decisions made by a distribution, 
then why is this an issue raised on LKML?  What does it have to do with 
the kernel or why does it have to be addressed in the kernel, one way or 
another?  Or does it indeed?

  Maciej
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/