public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jim Crilly" <jim@why.dont.jablowme.net>
To: Patrick McFarland <diablod3@gmail.com>
Cc: Mark Knecht <markknecht@gmail.com>,
	gcoady@gmail.com, Andries.Brouwer@cwi.nl,
	linux-kernel@vger.kernel.org
Subject: Re: umount
Date: Mon, 28 Nov 2005 02:15:35 -0500	[thread overview]
Message-ID: <20051128071535.GB3638@voodoo> (raw)
In-Reply-To: <200511272101.07771.diablod3@gmail.com>

On 11/27/05 09:01:07PM -0500, Patrick McFarland wrote:
> On Sunday 27 November 2005 20:42, Mark Knecht wrote:
> > On 11/27/05, Grant Coady <grant_lkml@dodo.com.au> wrote:
> > > It leaves me with a little distrust of linux' handling of non-locked
> > > removable media (as opposed to lockable media like a zipdisk or cdrom).
> > >
> > > Grant.
> >
> > Under Windows, if a 1394 drive is unplugged without unmounting, it you
> > get a pop up dialog on screen telling you that data may be lost, etc.
> > while under any of the main environments I've tried under Linux
> > (Gnome, KDE, fluxbox) there are no such messages to the user. I have
> > not investigated log files very deeply, other than to say that dmesg
> > will show the drive going away but doesn't say it was a problem.
> >
> > I realize it's probably 100x more difficult to do this under Linux, at
> > least at the gui level, but I agree with your main point that my trust
> > factor is just a bit lower here.
> 
> No, WIndows says that because it is unable to mount a partition as sync, 
> unlike Linux. Linux Desktop Environments simply don't tell the user because 
> no data is lost if they unplug the media.

Both of those statements are not true. At least in XP removable media is
mounted sync by default, you have to go into the device manager and toggle
a radio button to "optimize for performance" before it'll do async writes.
I think the setting was the opposite in Win2K but I can't say for sure.

And even with sync writes it's possible to unplug the drive before the
write completes and if the drive is powered by USB there's no way to know
just how much data made it to disk. Ideally the kernel would emit some
message so that HAL or something can catch it and popup a message or
something.

> 
> -- 
> Patrick "Diablo-D3" McFarland || diablod3@gmail.com
> "Computer games don't affect kids; I mean if Pac-Man affected us as kids,
> we'd all be running around in darkened rooms, munching magic pills and
> listening to repetitive electronic music." -- Kristian Wilson, Nintendo,
> Inc, 1989
>

Jim.

  reply	other threads:[~2005-11-28  7:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-27 21:54 umount Andries.Brouwer
2005-11-28  0:45 ` umount Grant Coady
2005-11-28  1:42   ` umount Mark Knecht
2005-11-28  2:01     ` umount Patrick McFarland
2005-11-28  7:15       ` Jim Crilly [this message]
2005-11-28 17:20         ` umount Mark Knecht
2005-11-28 17:51           ` umount linux-os (Dick Johnson)
2005-11-28 21:11             ` umount Bill Davidsen
2005-11-28 21:16               ` umount linux-os (Dick Johnson)
2005-11-29  0:11             ` umount Mark Knecht
  -- strict thread matches above, loose matches on Subject: below --
2005-11-29  2:13 umount Steve French

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=20051128071535.GB3638@voodoo \
    --to=jim@why.dont.jablowme.net \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=diablod3@gmail.com \
    --cc=gcoady@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markknecht@gmail.com \
    /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