From owner-freebsd-questions Tue Sep 28 0:33:29 1999 Delivered-To: freebsd-questions@freebsd.org Received: from gina.esfm.ipn.mx (Gina.esfm.ipn.mx [148.204.102.61]) by hub.freebsd.org (Postfix) with ESMTP id 45CE6157DE for ; Tue, 28 Sep 1999 00:33:25 -0700 (PDT) (envelope-from mrspock@esfm.ipn.mx) Received: from localhost (mrspock@localhost) by gina.esfm.ipn.mx (8.9.3/8.9.2) with ESMTP id CAA44810 for ; Tue, 28 Sep 1999 02:32:27 -0500 (CDT) (envelope-from mrspock@esfm.ipn.mx) Date: Tue, 28 Sep 1999 02:32:26 -0500 (CDT) From: Eduardo Viruena Silva To: freebsd-questions@freebsd.org Subject: msdos file systems and frozen systems... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello there! I'm looking for your advice. I have a FreeBSD 3.2 box. When I first installed FreeBSD I had a win95 slice in my hard drive. My hard disk was not completely used, so I created another slice for FreeBSD and I installed it there. When the time came, I ask to the installation program to mount my win95 slice on /win95 directory, so this directory was created and the file system mounted on it. But... while created, /win95 directory got permission for reading and writing only by root. Now, I did not notice it until... One day I tried to write on this directory as a simple user (not root), my freebds box tried to do it and apparently it did it!! but suddenly it got frozen. I said to myself: "Well, it happens on normal win95 operation, it must happen in every operating system that handles this kind of file systems..." ha ha ha... No, more seriously, I did not know what happend until fortunately I read the /win95 directory permissions. win95 file systems cannot safe the owner of the files they hold and when they are mounted on freebsd directories they inheireted the owner and permission of the mounting directory. Installation program creates mounting directories without writing permissions for common users and when it is made, the system gets frozen. Even more, I do not know how it happend but I lost the FreeBSD DISK LABEL on my FreeBSD slice!!! What about give mounting directories permission "1333" universal writing but adding sticky bit, writing permision only for owner, in this case, root. Common can write files there, they can execute programs and directories but only root can erase them. I do not know how wise is what I'm trying to do, so please can you tell me your oppinion about it? Getting frozen systems is kind of scary. Erased FreeBSD disk labels can make people take their own lives. I know giving universal writing permision is not a good practice but there is no harm using these permissions and root's privacy is kept, because there is no reading permission on msdos file systems. On the other hand... I can use mtools and forget all this mess but, I think mounted msdos file systems are more user-friendly. You are making a very good job with this incredible operating system: FreeBSD - ______ _ * / /###\ / \ __ /\ /\ * / ./#### \ * \__|_/ | | / \/ \ | b#####| * _ | __ | | __ = .. \____ \ \_\#####/ / \| / \ | | /\_\/ = \_| * \___\###/ * \_/\_/\__/\__\/_/\__/ = \______/ _ | | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message