From: Bill Davidsen <davidsen@tmr.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Patrick McFarland <diablod3@gmail.com>,
gcoady@gmail.com, Andries.Brouwer@cwi.nl,
linux-kernel@vger.kernel.org
Subject: Re: umount
Date: Mon, 28 Nov 2005 16:11:09 -0500 [thread overview]
Message-ID: <438B726D.9090405@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0511281229560.8176@chaos.analogic.com>
linux-os (Dick Johnson) wrote:
> On Mon, 28 Nov 2005, Mark Knecht wrote:
>
>
>>On 11/27/05, Jim Crilly <jim@why.dont.jablowme.net> wrote:
>>
>>>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.
>>
>>Jim,
>> I'm not clear if 'both statements' included any of mine or not? :-)
>>
>> You discussed the event I was thinking of. I am writing to a 1394
>>drive, bus powered or not, and while the write is occuring I unplug
>>the cable. Clearly the data being written is not going to finish, and
>>that's expected, but the 'reduced confidence' issue is that I'm not
>>told directly of the event. Granted I'll eventually discover it in
>>some indrect manner, like a GUI action failing or something timing
>>out. However in Windows I do appreciate the clear message that this
>>has happened.
>>
>>Thanks,
>>Mark
>>
>
>
> Doesn't your GUI show a 'console' window? I don't use the GUI,
> but the last time I checked, there was a 'console' window that
> showed the error messages. This was standard with Sun.
>
> If you can find the 'console' window in your distribution, activate
> it. If it doesn't have one, contact your vendor or make one. There
> needs to be some visible evidence that something is going wrong.
xterm -C
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-11-28 21:08 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 ` umount Jim Crilly
2005-11-28 17:20 ` umount Mark Knecht
2005-11-28 17:51 ` umount linux-os (Dick Johnson)
2005-11-28 21:11 ` Bill Davidsen [this message]
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=438B726D.9090405@tmr.com \
--to=davidsen@tmr.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=diablod3@gmail.com \
--cc=gcoady@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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