[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9e4733910810210843v2b45d798xe8f448e75e5c2a6b@mail.gmail.com>
Date: Tue, 21 Oct 2008 11:43:25 -0400
From: "Jon Smirl" <jonsmirl@...il.com>
To: "Theodore Tso" <tytso@....edu>,
"Rogério Brito" <rbrito@....usp.br>,
"Alexandre Lymberopoulos" <lymber@...il.com>,
502583@...s.debian.org, 502583-submitter@...s.debian.org,
linux-kernel@...r.kernel.org, rafael@...ian.org
Subject: Re: Bug#502583: scary messages in dmesg
On Tue, Oct 21, 2008 at 11:31 AM, Theodore Tso <tytso@....edu> wrote:
> Solving this problem for desktop users is harder; probably the best
> thing you can do is to throw up "shame" dialog box telling them that
> they did Something Wrong, and while they may have gotten lucky this
> time, that next time they should close all programs using the USB
> storage device, and then right-click on the mounted disk icon and
> select "eject". That's what Windows does, and IIRC, what Mac OS X
> does; there really isn't much else that can be done.
Can we do something about atime on removable media? It is
non-intuitive to most users that sticking a drive in and copying a
couple files off from it is going to cause writes to the device. A
normal user would think that this is read-only access and it is ok to
yank the drive. I've burnt myself several times from this.
Another thing that gets normal users is yanking out a drive that was
definitely idle and then not having the icon for the drive disappear
on the desktop.
Maybe change distro mount defaults for removable media to noatime? And
add an event when the drive is yanked with no pending writes to tell
the desktop the drive is gone?
Of course yanking with writes pending should generate a big error box.
Can it ask the user to reinsert the drive and pick up where it left
off?
--
Jon Smirl
jonsmirl@...il.com
--
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/
Powered by blists - more mailing lists