Re: kernel panic because I pulled a floppy?

2005-12-04 Thread David Gerard
Michael P. Soulier wrote:

> I'm reading "BSD Hacks" by Dru Lavigne, published by O'Reilly. In the
> section on managing floppies, it mentions that if you pull a floppy
> without umounting it first, the next time to try to access the
> filesystem, you'll get a kernel panic.
> Is this true? If so, it would be the very first Unix that I've seen
> crash from this kind of user-mistake.


I've crashed 5.x by pulling a USB umass device and then trying to look
at the directory where it was mounted.


- d.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: kernel panic because I pulled a floppy?

2005-12-04 Thread Kris Kennaway
On Sun, Dec 04, 2005 at 05:32:42PM -0500, Michael P. Soulier wrote:
> Hey all,
> 
> I'm reading "BSD Hacks" by Dru Lavigne, published by O'Reilly. In the
> section on managing floppies, it mentions that if you pull a floppy
> without umounting it first, the next time to try to access the
> filesystem, you'll get a kernel panic.
> 
> Is this true? If so, it would be the very first Unix that I've seen
> crash from this kind of user-mistake.

Turns out it's pretty hard to fix.

Kris


pgpxD7TqAfUw0.pgp
Description: PGP signature


Re: kernel panic because I pulled a floppy?

2005-12-05 Thread Michael P. Soulier
On 12/4/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > Is this true? If so, it would be the very first Unix that I've seen
> > crash from this kind of user-mistake.
>
> Turns out it's pretty hard to fix.

Well, all I know is that it does happen on Linux, Solaris... I don't
recall seeing it on HP-UX...

I've popped floppies on those OSs before without incident when I went
back to the directory. Luckily it's avoidable, just a little
disappointing given FreeBSD's rock-solid reputation.

Mike
--
Michael P. Soulier <[EMAIL PROTECTED]>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: kernel panic because I pulled a floppy?

2005-12-05 Thread Kris Kennaway
On Mon, Dec 05, 2005 at 08:37:23AM -0500, Michael P. Soulier wrote:
> On 12/4/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > > Is this true? If so, it would be the very first Unix that I've seen
> > > crash from this kind of user-mistake.
> >
> > Turns out it's pretty hard to fix.
> 
> Well, all I know is that it does happen on Linux, Solaris... I don't
> recall seeing it on HP-UX...
> 
> I've popped floppies on those OSs before without incident when I went
> back to the directory. Luckily it's avoidable, just a little
> disappointing given FreeBSD's rock-solid reputation.

OK.

Kris


pgpV3p6wIwWSR.pgp
Description: PGP signature


Re: kernel panic because I pulled a floppy?

2005-12-06 Thread Martin Tournoy
It happens, I've experienced quite some problems with floppy's and
FreeBSD 5.4 and 6.0

anyway, if you mount a floppy, pull it out and unmount it the kernel
might panic, if the floppy if reading writing and you pull it out the
kernel might panic, if you mount a floppy which is damaged or has a
damaged filesystem the kernel might panic

I think i've only seen FreeBSD crach about six times in the year I'm
using it, all of those were with floppy problems...

My advice:
Save all your work before you do anything with a floppy
Don't do anything with a floppy on critical machines
Think before you act when working with a floppy

It sucks, I know, I always use a windows machine when I need to write
or read something on a floppy.
Using windows instead of freebsd because it's better at something. . .
. . . . scary. . .

On 05/12/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 05, 2005 at 08:37:23AM -0500, Michael P. Soulier wrote:
> > On 12/4/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > > > Is this true? If so, it would be the very first Unix that I've seen
> > > > crash from this kind of user-mistake.
> > >
> > > Turns out it's pretty hard to fix.
> >
> > Well, all I know is that it does happen on Linux, Solaris... I don't
> > recall seeing it on HP-UX...
> >
> > I've popped floppies on those OSs before without incident when I went
> > back to the directory. Luckily it's avoidable, just a little
> > disappointing given FreeBSD's rock-solid reputation.
>
> OK.
>
> Kris
>
>
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: kernel panic because I pulled a floppy?

2005-12-06 Thread Lowell Gilbert
Don't top-post, please.

Martin Tournoy <[EMAIL PROTECTED]> writes:

> My advice:
> Save all your work before you do anything with a floppy
> Don't do anything with a floppy on critical machines
> Think before you act when working with a floppy

Using the mtools port is a lot easier.  It uses the Windows model of
separate devices instead of mounting the floppy into a unified
filesystem tree, so it avoids the kernel interaction with the mount
point. 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: kernel panic because I pulled a floppy?

2005-12-06 Thread Martin Tournoy
mtools, hmm, might want to check that one out

Ok, stupid question perhaps, but what is "top-posting", I'm new to the
whole mailling list stuff, so if you can explain a bit I won't do it
anymore

On 06 Dec 2005 10:12:40 -0500, Lowell Gilbert
<[EMAIL PROTECTED]> wrote:
> Don't top-post, please.
>
> Martin Tournoy <[EMAIL PROTECTED]> writes:
>
> > My advice:
> > Save all your work before you do anything with a floppy
> > Don't do anything with a floppy on critical machines
> > Think before you act when working with a floppy
>
> Using the mtools port is a lot easier.  It uses the Windows model of
> separate devices instead of mounting the floppy into a unified
> filesystem tree, so it avoids the kernel interaction with the mount
> point.
>
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: kernel panic because I pulled a floppy?

2005-12-06 Thread Giorgos Keramidas
On 2005-12-06 15:19, Martin Tournoy <[EMAIL PROTECTED]> wrote:
>
> Ok, stupid question perhaps, but what is "top-posting", I'm new to the
> whole mailling list stuff, so if you can explain a bit I won't do it
> anymore
>
> On 06 Dec 2005 10:12:40 -0500, Lowell Gilbert
> <[EMAIL PROTECTED]> wrote:
> > Don't top-post, please.

Top-posting is what you did just now.  Quoting the original message
near the bottom of your post and adding your reply on top of it.

It tends to create silly 'nested threads' of messages like the one
below:

Oh, I see.

-

Because you have to read the 'thread' of messages and their
replies in an entirely backwards order.

-

So why is top-posting bad?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: kernel panic because I pulled a floppy?

2005-12-06 Thread Bob Johnson
On 12/5/05, Michael P. Soulier <[EMAIL PROTECTED]> wrote:
> On 12/4/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > > Is this true? If so, it would be the very first Unix that I've seen
> > > crash from this kind of user-mistake.
> >
> > Turns out it's pretty hard to fix.
>
> Well, all I know is that it does happen on Linux, Solaris... I don't
> recall seeing it on HP-UX...
>
> I've popped floppies on those OSs before without incident when I went
> back to the directory. Luckily it's avoidable, just a little
> disappointing given FreeBSD's rock-solid reputation.
>

My understanding, and it could be completely wrong, is that Linux
distributions usually use something like amd(8) (the automount daemon)
to manage removable devices.  They automount automagically when
inserted, and unmount when they haven't been used for a while, so if
you forget about them and pull them out they are usually not mounted
and don't cause problems.

You might try setting up amd(8) to see if that makes things more robust.

- Bob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"