From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>,
"Rogério Brito" <rbrito@ime.usp.br>,
"Alexandre Lymberopoulos" <lymber@gmail.com>,
502583@bugs.debian.org, 502583-submitter@bugs.debian.org,
linux-kernel@vger.kernel.org, rafael@debian.org
Subject: Re: Bug#502583: scary messages in dmesg
Date: Tue, 21 Oct 2008 11:43:25 -0400 [thread overview]
Message-ID: <9e4733910810210843v2b45d798xe8f448e75e5c2a6b@mail.gmail.com> (raw)
In-Reply-To: <20081021153105.GD15685@mit.edu>
On Tue, Oct 21, 2008 at 11:31 AM, Theodore Tso <tytso@mit.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@gmail.com
next prev parent reply other threads:[~2008-10-21 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2bfaaf400810172145g4aba4827l87a19e67b9742815@mail.gmail.com>
2008-10-18 6:04 ` Rogério Brito
2008-10-20 23:54 ` Alexandre Lymberopoulos
2008-10-21 10:15 ` Rogério Brito
2008-10-21 12:33 ` Theodore Tso
2008-10-21 14:35 ` Rogério Brito
2008-10-21 15:31 ` Theodore Tso
2008-10-21 15:43 ` Jon Smirl [this message]
2008-10-21 21:21 ` Alexandre Lymberopoulos
2008-10-21 20:55 ` Alexandre Lymberopoulos
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=9e4733910810210843v2b45d798xe8f448e75e5c2a6b@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=502583-submitter@bugs.debian.org \
--cc=502583@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lymber@gmail.com \
--cc=rafael@debian.org \
--cc=rbrito@ime.usp.br \
--cc=tytso@mit.edu \
/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®