From owner-freebsd-questions Wed Aug 18 7:44: 2 1999 Delivered-To: freebsd-questions@freebsd.org Received: from ns.clientlogic.com (ns.clientlogic.com [207.51.66.75]) by hub.freebsd.org (Postfix) with ESMTP id 9426C14C25 for ; Wed, 18 Aug 1999 07:43:59 -0700 (PDT) (envelope-from ChrisMic@clientlogic.com) Received: by site0s1 with Internet Mail Service (5.5.2448.0) id ; Wed, 18 Aug 1999 10:42:02 -0400 Message-ID: <6C37EE640B78D2118D2F00A0C90FCB4401105BA0@site2s1> From: Christopher Michaels To: "'Boune, Damian'" , freebsd-questions@FreeBSD.ORG Subject: RE: bug which crashes FreeBSD 3.2 Date: Wed, 18 Aug 1999 10:44:34 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Point well taken, that this is common knowledge for anyone who has any familiarity with the system. I think the point being made is that if a mistake is made or an inexperienced user is at the system, there should be some failsafe to prevent the system from locking down or panic'ing. When we're talking about a floppy (or any removable media) there is a vary good chance that, the mounted file system could be removed w/o unmounting it. It would be just good practice to protect the system against that. If FreeBSD is to stay primarily a server oriented OS or a 'nitche market', than for the most part, no one cares because 99% of people who use FreeBSD know to mount / unmount the floppy (as inconvenient and un-intuitive as that may be). If FreeBSD does want more of a user base, and is going to be touted as a 'desktop operating system', then certain concessions and falsifies need to be integrated into the system, as to not drive those potential users away. That's just my opinion. -Chris > -----Original Message----- > From: Boune, Damian [SMTP:DBoune@co.napa.ca.us] > Sent: Tuesday, August 17, 1999 5:57 PM > To: freebsd-questions@FreeBSD.ORG > Subject: bug wich crashes freebsd 3.2 > > Our friend makes a good point. What Reinoud did is only "improper use" if > the operating system does not provide some kind of catch in the case that > someone does this. > > You can assume he came from the Microsoft world. In that horrid world, it > is > known that the USER is not supposed to be able to cause such a crash, > though > we all know better. In the unix world we assume that you are familiar with > how unix does things and will pay attention to such details. Who would > have > thought, coming from the microsoft world, that one would have to "unmount" > (whatever THAT is) a disk! > > It would have been possible for the designers of any particular flavor of > unix to implement something that would prevent this. However actually > doing > it is another thing. We have a base "format" in which we "mount" media in > general that has been around for a long time. If we change that, we risk > incompatibility, and we also make our kernel quite a bit larger as we > would > have to have more than one base function (rather, set of 's) for making > media available to the user. Anyway, it just isn't something anybody wants > to waste time on, as we know how it works currently, and if you follow the > directions, which happen to be posted all over the place, you won't get > into > too much trouble. > > Some os's actually "mount" and "unmount" some media, each time an action > is > taken upon it. This creates a high amount of overhead that us unix buffs > don't want, but it does prevent the user from crashing the system. > > Under unix it is also assumed that the "user" will not be mounting and > unmounting media, but that an experienced "Administrator" would be doing > it. > Well, the face of unix has changed, and now the pocket hacks are all > running > it. Most of us take on the challenge knowing we will have to learn how to > play by the *nix rules. > > So to those who do not like it, please write some code to send to our good > friends at the FreeBSD project that will fix this little annoyance :) > > (had to put my "2 cents" in.) > > -d > > > -----Original Message----- > > From: William Melanson [mailto:wjm@gate.net] > > Sent: Tuesday, August 17, 1999 1:41 PM > > To: freebsd-questions@FreeBSD.ORG > > Subject: Re: bug wich crashes freebsd 3.2 (HA!) > > > > > > On Tue, 17 Aug 1999, Reinoud Koornstra wrote: > > > > % > > % No i didnt umount the disk first. > > % But i didnt umount it on purpose to see. > > % And what if a user forgets to umount it before removing? > > % A whole os cant just hang by a user mistake now can it? > > % Bye, > > % > > > > If you use the os improperly of course it can! Please tell me this > > is some type of practical (let's kill the os) joke. Where is that > > FreeBSD for Dummies book when ya need it? > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message