> "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
Ethan> On 9/1/2000 Brian May wrote:
Brian> [1] Dos/windows copes with this problem in a different (IMHO
Brian> broken) way - it keeps track of which disk is inserted, and if
Brian> it needs to read/write to another disk, it complains to the
I agree completely.
Sean
Joachim Trinkwitz wrote:
>
> Fish Smith <[EMAIL PROTECTED]> writes:
>
> > The bottom line is, it isn't appropriate for my
> > machine to be making decisions as to whether it is
> > appropriate to eject a dis(k/c) or not. I should be
> > making those decisions because t
Fish Smith <[EMAIL PROTECTED]> writes:
> The bottom line is, it isn't appropriate for my
> machine to be making decisions as to whether it is
> appropriate to eject a dis(k/c) or not. I should be
> making those decisions because the machine is
> unreliable and if I make a bad decision then I, as
Quoting Fish Smith ([EMAIL PROTECTED]):
> >It is not only newbies that can make stupid mistakes,
> >and remove a
> >floppy disk that is currently mounted...
>
> I was taught in kindergarten /never/ to remove a disk
> when the light was on, and I never do it. Removing
> while it is mounted but not
On 10/1/2000 Brian May wrote:
However, I see you are now correct. Now data is written to the disk
almost immediately (1 second delay) after it is dirty. This means the
developers have put the safety of the disk ahead of performance
issues...
this is not necessarily the case, from my tests some
On 9/1/2000 Fish Smith wrote:
I was taught in kindergarten /never/ to remove a disk
when the light was on, and I never do it. Removing
while it is mounted but not currently being read or
written isn't very damaging--you just get an error
message, have to unmount and remount.
this is true if
> "Fish" == Fish Smith <[EMAIL PROTECTED]> writes:
>> It is not only newbies that can make stupid mistakes, and
>> remove a floppy disk that is currently mounted...
Fish> I was taught in kindergarten /never/ to remove a disk when
Fish> the light was on, and I never do it. Rem
>It is not only newbies that can make stupid mistakes,
>and remove a
>floppy disk that is currently mounted...
I was taught in kindergarten /never/ to remove a disk
when the light was on, and I never do it. Removing
while it is mounted but not currently being read or
written isn't very damaging--
On Sat, 08 Jan 2000 23:09:43 -0900, Ethan Benson writes:
>On 9/1/2000 Brian May wrote:
>>as far as to suggest that the CD-ROM might be dirty. Now thats what I
>>call "machine is smarter"!!!
which reminds me of a user crying:
"you dumb computer, do what I want, not what I say!"
*g*
&rw
--
-- +++
On 9/1/2000 Brian May wrote:
[1] Dos/windows copes with this problem in a different (IMHO broken)
way - it keeps track of which disk is inserted, and if it needs to
read/write to another disk, it complains to the user to reinsert the
original disk. Why is this mechanism broken? For starters: som
> "Fish" == Fish Smith <[EMAIL PROTECTED]> writes:
Fish> Unlike many others, I don't share the view that "linux needs
Fish> to be made more newbie friendly." Doing that will kill
Fish> everything that made it great, and turn it into another
Fish> Windoze. I don't care if the
Disclaimer: Some of this can probably be interpreted
as flame bait. So let 'er rip =)
>> > I've hever been able to open a CD drive without
unmounting the
volume -- the
>> > drawer won't open.
>>
>> Along the same linesthis is the one mechanism
of mac/sun/other(?)
>> floppies that I would lik
Gary Hennigan said:
> My SGI is entirely "soft button". If it crashes sometimes I can't even
> turn the power off on it, I end up having to unplug the stupid thing
> to reset it!
That's excessive, of course, but I'd like to see something along the lines of
the option on most ATX BIOSes to have a m
13 matches
Mail list logo
