From: Jim Crilly <jim@why.dont.jablowme.net>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Joshua Schmidlkofer <kernel@pacrimopen.com>,
"David B. Stevens" <dsteven3@maine.rr.com>,
Jos Hulzink <josh@stack.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.7 (future kernel) wish
Date: Tue, 30 Dec 2003 19:18:54 -0500 [thread overview]
Message-ID: <3FF215EE.9000509@why.dont.jablowme.net> (raw)
In-Reply-To: <20031230142004.GA14655@hh.idb.hist.no>
Helge Hafting wrote:
> On Sat, Dec 27, 2003 at 10:03:17PM -0500, Jim Crilly wrote:
>
>>>Sometimes Windows 2k or XP dump (BSOD), or maybe you just get an error.
>>>
>>>
>>>
>>
>>Generally it just complains that you pulled out the device prematurely,
>
>
> Depends on what the device is used for, I guess.
Of course different things may happen depending on what's using the
device, but IME I've never seen the OS give a STOP error from that.
>
>
>>I've never seen one give a STOP error from that but I guess a bad driver
>>or USB controller could cause anything.
>>
>
> Well, try having a partially loaded system dll on removable
> media when you pull the plug - it won't be pretty.
If you go through all the work to get Windows to use a system file from
removable device then pull it out while using it, you deserve what you
get. The only thing you could do is page in the entire system file if
you notice it's on a removable device then put a copy in swap for the
case that someone pulls it out, but I don't think the special case would
be worth it on Windows or Linux. Not that I have any proof Windows
doesn't attempt to do that already =)
>
>
>>When you insert a device like a USB stick Windows puts a little icon
>>next to the clock in the system tray that you're supposed to use to stop
>>the device before pulling it, effectively it unmounts and stops (or
>>atleast releases the device from) the driver so the device can be
>>'safely' removed. I also believe Windows mounts any removable device
>>synchronously so that if you do pull it out prematurely the damage done
>>is limited.
>
>
> Linux has sync mounts too. :-) the rest is a gui thing, i.e. not kernel.
I know, but I felt like mentioning the rest because it's relevant to a
number of people on the list.
>
> Helge Hafting
Jim.
next prev parent reply other threads:[~2003-12-31 0:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 22:42 Jos Hulzink
2003-12-26 23:38 ` Helge Hafting
2003-12-26 23:57 ` David B. Stevens
2003-12-27 6:51 ` Joshua Schmidlkofer
2003-12-28 3:03 ` Jim Crilly
2003-12-28 3:08 ` Kevin P. Fleming
2003-12-28 3:13 ` Rob Love
2003-12-28 11:17 ` Kevin Krieser
2003-12-28 11:23 ` Gaël Le Mignot
2003-12-28 3:11 ` Rob Love
2003-12-28 3:19 ` Jim Crilly
2004-01-04 21:05 ` Pat Erley
2003-12-28 3:57 ` Joshua Schmidlkofer
2003-12-28 4:33 ` Elladan
2003-12-30 14:20 ` Helge Hafting
2003-12-31 0:18 ` Jim Crilly [this message]
2003-12-30 15:41 Pacheco Jason NPRI
2003-12-30 16:18 ` mjt
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=3FF215EE.9000509@why.dont.jablowme.net \
--to=jim@why.dont.jablowme.net \
--cc=dsteven3@maine.rr.com \
--cc=helgehaf@aitel.hist.no \
--cc=josh@stack.nl \
--cc=kernel@pacrimopen.com \
--cc=linux-kernel@vger.kernel.org \
/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®