From owner-freebsd-fs Mon Jun 1 00:00:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13367 for freebsd-fs-outgoing; Mon, 1 Jun 1998 00:00:25 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA13341 for ; Mon, 1 Jun 1998 00:00:15 -0700 (PDT) (envelope-from hiren@tagore.wipinfo.soft.net) From: hiren@tagore.wipinfo.soft.net Received: from tagore.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id MAA12952; Mon, 1 Jun 1998 12:26:49 -0500 Message-ID: <9806011236.AA21700@tagore.wipinfo.soft.net> Subject: macro definitions of VOP_??? To: freebsd-fs@FreeBSD.ORG Date: Mon, 1 Jun 1998 12:35:52 +0530 (IST) Reply-To: hiren@tagore.wipinfo.soft.net Content-Type: text Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Return-Receipt-To:hiren X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 641 Hi, I was looking at the sources of FreeBSD virtual file system (VFS) implementation. It uses all macros starting with VOP_ (e.g. VOP_OPEN, VOP_CLOSE, VOP_ACCESS, etc). I could not find the definition of this macro (#define) at all. Can somebody respond with the name of the file which contains the macro definition of VOP_???. Another thing is, I was trying to find structure declarations of the vop_???_args (e.g. vop_create_args, vop_mknod_args, vop_close_args, vop_access_args, vop_read_args, etc.) This also I could not find in the sources. It is very likely that both may be in the same file. Please help me out. Thanks Hiren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Jun 1 01:25:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23805 for freebsd-fs-outgoing; Mon, 1 Jun 1998 01:25:58 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA23766 for ; Mon, 1 Jun 1998 01:25:38 -0700 (PDT) (envelope-from hiren@tagore.wipinfo.soft.net) From: hiren@tagore.wipinfo.soft.net Received: from tagore.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id NAA15857; Mon, 1 Jun 1998 13:51:22 -0500 Message-ID: <9806011401.AA11364@tagore.wipinfo.soft.net> Subject: implementation of virtual file system and msdosfs To: freebsd-fs@FreeBSD.ORG Date: Mon, 1 Jun 1998 14:00:30 +0530 (IST) Reply-To: hiren@tagore.wipinfo.soft.net Content-Type: text Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Return-Receipt-To:hiren X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 165 Hi, Is there any documentation which explains the implementation of VFS and the implementation of msdosfs which fits into VFS implementation of FreeBSD -- Hiren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Jun 1 09:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06505 for freebsd-fs-outgoing; Mon, 1 Jun 1998 09:27:02 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06488 for ; Mon, 1 Jun 1998 09:26:59 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id JAA12470; Mon, 1 Jun 1998 09:26:41 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd012443; Mon Jun 1 09:26:35 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id JAA08011; Mon, 1 Jun 1998 09:26:33 -0700 (MST) From: Terry Lambert Message-Id: <199806011626.JAA08011@usr04.primenet.com> Subject: Re: macro definitions of VOP_??? To: hiren@tagore.wipinfo.soft.net Date: Mon, 1 Jun 1998 16:26:33 +0000 (GMT) Cc: freebsd-fs@FreeBSD.ORG In-Reply-To: <9806011236.AA21700@tagore.wipinfo.soft.net> from "hiren@tagore.wipinfo.soft.net" at Jun 1, 98 12:35:52 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I was looking at the sources of FreeBSD virtual file system (VFS) > implementation. > It uses all macros starting with VOP_ (e.g. VOP_OPEN, VOP_CLOSE, > VOP_ACCESS, etc). > I could not find the definition of this macro (#define) at all. > Can somebody respond with the name of the file which contains > the macro definition of VOP_???. > > Another thing is, I was trying to find structure declarations of the > vop_???_args (e.g. vop_create_args, vop_mknod_args, vop_close_args, > vop_access_args, vop_read_args, etc.) This also I could not find in the > sources. /sys/compile/*/vnode_if.[ch] These are generated files from the interface definition in the file /sys/kern/vnode_if.src. The interface definition is processed into the generated files by /sys/kern/vnode_if.sh. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Jun 1 09:31:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07305 for freebsd-fs-outgoing; Mon, 1 Jun 1998 09:31:22 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07275 for ; Mon, 1 Jun 1998 09:31:17 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id JAA14870; Mon, 1 Jun 1998 09:31:16 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd014816; Mon Jun 1 09:31:14 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id JAA08362; Mon, 1 Jun 1998 09:31:12 -0700 (MST) From: Terry Lambert Message-Id: <199806011631.JAA08362@usr04.primenet.com> Subject: Re: implementation of virtual file system and msdosfs To: hiren@tagore.wipinfo.soft.net Date: Mon, 1 Jun 1998 16:31:12 +0000 (GMT) Cc: freebsd-fs@FreeBSD.ORG In-Reply-To: <9806011401.AA11364@tagore.wipinfo.soft.net> from "hiren@tagore.wipinfo.soft.net" at Jun 1, 98 02:00:30 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Is there any documentation which explains the implementation of VFS and the > implementation of msdosfs which fits into VFS implementation of FreeBSD ftp://ftp.cs.ucla.edu/pub/ficus/heidemann_thesis.ps.gz See also other documents in the same directory. It's not totally accurate, since the BSD4.4 implementation does not match John Heidemann's design documents very well at all. Among other things, there is "struct fileops", "VOP_LOCK", the cookie argument to "VOP_READDIR", etc.. It would be nice if the code matched the design document. 8-|. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Jun 1 19:16:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10919 for freebsd-fs-outgoing; Mon, 1 Jun 1998 19:16:43 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10844 for ; Mon, 1 Jun 1998 19:15:16 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id CAA23673; Tue, 2 Jun 1998 02:13:53 GMT Date: Tue, 2 Jun 1998 11:13:53 +0900 (JST) From: Michael Hancock To: Cejka Rudolf cc: freebsd-fs@FreeBSD.ORG Subject: Re: VFSs in -current: Are they working? In-Reply-To: <199805281757.RAA20583@sts.dcse.fee.vutbr.cz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 28 May 1998, Cejka Rudolf wrote: > > I'm reading news about -current since April and it seems to me that nobody > has problems with virtual filesystems. And what about null layer & kern/6465? > (Does anybody use null layer?) Or is this only my problem on my -current box? > Should I write more information about kern/6465? > > I'm sorry, but I don't know, where I may search this critical bug. > In VFS? Null layer looks too simple... > In VM space? Are there still VM bugs? I'm working on fixing layering violations which will improve things. The next problem which is more serious for is name/object coherence. Operations like mmap, read, write, getpages, and putpages can get incoherent because they will operate on different objects. One solution is to proxy everything down to the underlying object. One pie in the sky solution is to separate the notion of who is the cacher and who is the pager. Then get/putpages would accept a cachevp and a pagervp. You would then have to write a sophisticated cachemgr to orchestrate everything including data pages and other object attributes. If you want to find papers on these topics then search the net for things like filesystems, the spring project, and heidemann. Regards, Mike > Any suggestions? (Please...) > > Thanks. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Jun 2 14:50:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17333 for freebsd-fs-outgoing; Tue, 2 Jun 1998 14:50:04 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from atena.eurocontrol.fr (atena.uneec.eurocontrol.fr [147.196.69.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA16910 for ; Tue, 2 Jun 1998 14:48:23 -0700 (PDT) (envelope-from roberto@eurocontrol.fr) Received: by atena.eurocontrol.fr; (5.65v3.2/1.3/10May95) id AA22476; Tue, 2 Jun 1998 23:47:16 +0200 Received: by caerdonn.eurocontrol.fr (VMailer, from userid 1193) id D3DA5FD; Tue, 2 Jun 1998 21:47:15 +0000 (GMT) Message-Id: <19980602234715.B1717@caerdonn.eurocontrol.fr> Date: Tue, 2 Jun 1998 23:47:15 +0200 From: Ollivier Robert To: freebsd-fs@FreeBSD.ORG Subject: Fwd: Re: ext2fs and the qmail list... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just found this on a mailing-list. Anyone's heard about this journaled Ext2 ? ----- Forwarded message from Sean Reifschneider ----- Date: Tue, 2 Jun 1998 15:24:26 -0600 From: Sean Reifschneider Subject: Re: ext2fs and the qmail list... On Sat, May 23, 1998 at 07:20:11PM -0400, Wietse Venema wrote: >In addition to running performance measurements on *BSD I also ran >them on LINUX, and found that LINUX was a bit too fast to be true. As I understand it, BSD variants will essentially sync the metadata after every operation (create, write, and remove). With Linux, it will only sync when you tell it to or it decides it's time. Linux is updating all the blocks for the previous remove, create, and writes when you call the fsync. Since the file-system tries to keep things close to eachother, it's not necessarily cheating... I don't know for sure that Linux does actually sync the data when you do an fsync, but I'd be suprised if they didn't. However, if they were *REALLY* cheating, why's it so slow? I ran it on my machine with "-c 10000" in 10.26 seconds -- 1.03ms per file. That's more the speed I'd be expecting if they were REALLY cheating. My numbers are so fast because I have my controller set up to ACK the write as soon as the data is deposited on the controller's cache. I just got back from Linux Expo, and one of the presentations was from Stephen Tweedie about Journaling EXT2. It sounds like the design is completed (and *VERY* well thought-out) and they are working on the implementation. They are claiming that they'll probably see increased performance as well as rock-solid reliability. >Someone observed that non-volatile cache (Prestoserve) can really >speed things up by a lot more than a factor of 2 because the disk >driver can sort writes into the most efficient order. Apparently Linux already does a fairly good job of that already. I have asked around and especially with todays more intelligent discs, elevator sorting is much less an issue than it used to be. I have noticed that ACKing the sync when data is written to the controller cache instead of to the discs can make a HUGE difference. With UPSs or things like the Mylex RAID boards (with optional NVRAM) it can be done reliably as well. >I wouldn't use LINUX for mission-critial applications. That seems a bit heavy-handed... Especially when Linux has just chosen async as the default. If you run it on a mission-critical server, add the "sync" option. On my notebook I ran your test program and it took roughly 3 seconds for 100 files with the fs mounted async, and 16 seconds with it mounted sync. Since it takes twice as long as your BSD/OS box, it must be *REALLY* good. :-) Sean -- Tools may limit the user, but the utility of tools is limited by the skill of the user. -- Leonard Compagno Sean Reifschneider, Inimitably Superfluous URL: HP-UX/Linux/FreeBSD/BSDOS scanning software. ----- End forwarded message ----- -- Ollivier ROBERT -=- Eurocontrol EEC/TS -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 3.0-CURRENT #5: Tue Apr 22 14:57:00 CEST 1997 roberto@caerdonn.eurocontrol.fr:/src/src/sys/compile/CAERDONN2 i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Jun 3 08:36:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02267 for freebsd-fs-outgoing; Wed, 3 Jun 1998 08:36:42 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from gatewayb.anheuser-busch.com (gatewayb.anheuser-busch.com [151.145.250.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA02029; Wed, 3 Jun 1998 08:35:26 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewayb.anheuser-busch.com; id KAA27771; Wed, 3 Jun 1998 10:34:00 -0500 Received: from stlabcexg003.anheuser-busch.com( 151.145.101.158) by gatewayb via smap (V2.1) id xma027648; Wed, 3 Jun 98 10:33:53 -0500 Received: by stlabcexg003.anheuser-busch.com with Internet Mail Service (5.5.1960.3) id ; Wed, 3 Jun 1998 10:32:24 -0500 Message-ID: <31B3F0BF1C40D11192A700805FD48BF9017765D7@STLABCEXG011> From: "Alton, Matthew" To: "'hackers@FreeBSD.ORG'" , "'FreeBSD-fs@FreeBSD.ORG'" Cc: "Smallie, Scott" Subject: Filesystem Development Toolkit Date: Wed, 3 Jun 1998 10:33:45 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hackers, My recent excursions into the wonderful world of filesystem development have led me to embark on the following Mondo Project which is currently in the lex-spec + stubs phase. The project spec follows. Well, it started out as one anyway, but turned into a sort of polemic rant. I wrote it in the throes of trad- itional development :-) Please help me come up with good ideas. Yes, I'm going to copyleft the software. I just can't stand the thought of Bill's henchmen holding my slightly modified code hostage in their nasty ten- tacles. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ $Id: SPEC,v 1.3 1998/06/03 00:09:30 matta Exp matta $ Filesystem Development Toolkit ============================== The Filesystem Development Toolkit (FDT) is software designed to ease the task of implementing, testing, and debugging filesystem designs. Traditional filesystem development is unduly complex. The procedure involves: 1) Design phase - The fundamental structure and properties of the filesystem are defined; 2) Coding - The filesystem code and operating system kernel interface code are written; 3) Testing - The filesystem modules are loaded into system space and run with superuser privileges; 4) Debugging - Problems detected in the testing phase are traced to root causes in the coding and/or design phases and are remedied. This procedure is fraught with alleviable difficulties. The coding phase nec- essarily involves a detailed knowledge of the inner workings of a specific oper- ating system. Such knowledge is often irrelevant to the purpose of the develop- ment effort. The filesystem interface particulars vary radically between oper- ating systems so that the code must be altered substantially for each new de- velopment platform. Testing new filesystem code invariably involves destabil- izing the operating system running on the test platform so that a machine must be dedicated to testing. The debugging phase is egregiously difficult as oper- ating system debugging is inherently more difficult than application debugging. Each cycle of the process may necessitate a reinstallation of the operating system due to media corruption caused by buggy filesystem code. A non-root user is not able to test a new filesystem design at all. Many of these problems are rendered geometrically more difficult when the filesystem in question is of the distributed variety and requires multiple network nodes for testing pur- poses. All of these difficulties may be relieved to various degrees by simply moving the development cycle entirely into user space. The difficulty involved in developing a new filesystem would then be on the order of that involved in app- lication development. The problem of "porting" the new filesystem to another operating system, while still difficult, would at least be distinct from the development cycle. The FDT provides a simulation environment for developing filesystems in user space by effectively "stepping down" the levels of the operating system. The filesystem under development actually exists as a regular file which the FDT manipulates. This regular file is in effect a "disk image" containing a bit- for-bit likeness of an instance of the filesystem under development. The FDT provides the layer of abstraction necessary to create filesystem objects in the disk image. Concurrent access may be controlled through file permissions and ... ... ... sfc - Simulation Fileystem Control program. Command-line interface for use in filesystem prototyping. Commands: ![cmd [args ...] ] - Shell command. Execute cmd in a subshell. mkpf < -s size pf_name > - Make prototype file. Create a zero-filled file named `pf_name' of `size' bytes analogous to a mass storage device. mkfs < pf_name > - Make file system. Create a bit-pattern analogous to a filesystem on the prototype file named `pf_name'. mount_lfs < pf_name > - Mount file system. Reset `pf_name' clean bit and enable read and write operations on `pf_name'. Analogous to mounting filesystem named `pf_name' on mount point `pf_name'. fsck < pf_name > - File system check. Check and optionally attempt to correct inconsistencies in bit-pattern on file `pf_name'. df [ pf_name [ pf_name ... ] ] - Summarize disk free space. Display summary of free space per prototype file argument. du [ pf_name [ pf_name ... ] ] - Summarize disk usage. Display summary of space usage per prototype file. cp < source dest > - Copy filesystem object from source to dest. `source' and `dest' may be files or bit-patterns within a prototype file. mv < source dest > - Move filesystem object from source to dest. `source' and `dest' may be files or bit-patterns within a prototype file. mknod < node b|c|u major minor > - Make device special file. Make ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Matthew Alton Computer Services - UNIX Systems Administration (314)632-6644 matthew.alton@anheuser-busch.com alton@plantnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Jun 5 02:24:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13690 for freebsd-fs-outgoing; Fri, 5 Jun 1998 02:24:09 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA13631 for ; Fri, 5 Jun 1998 02:23:52 -0700 (PDT) (envelope-from hiren@tagore.wipinfo.soft.net) From: hiren@tagore.wipinfo.soft.net Received: from tagore.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id OAA12412; Fri, 5 Jun 1998 14:49:58 -0500 Message-ID: <9806051459.AA26042@tagore.wipinfo.soft.net> Subject: User creds for MSDOSFS To: freebsd-fs@FreeBSD.ORG Date: Fri, 5 Jun 1998 13:11:56 +0530 (IST) Reply-To: hiren@tagore.wipinfo.soft.net Content-Type: text Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Return-Receipt-To:hiren X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 939 Hi All, Can somebody explain how user credentials are handled in case of MSDOSFS ? who all are allowed to access/modify files/directory once file system of type MSDOSFS is mounted ? -- Hiren `All rights left. All lefts reserved. All reserves removed. All removes right.' CHANGE IN EXTENSION NUMBER //// (o o) -------------------------oOO--(_)--OOo----------------------------------- Hiren Mehta --- Email address : AT&T Dedicated Facility /o o\ hiren@wipinfo.soft.net Wipro Infotech Ltd(ADF) | O | Phone: 91-080-2241735, 2241730 Divyasree Complex, \_-_/ 2241735, 2241768 30, Mission Road, Ist Main, Extn. 3411 S. R. Nagar, Bangalore - 560 027 Fax: 91-080-2241769 ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Jun 5 02:26:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13839 for freebsd-fs-outgoing; Fri, 5 Jun 1998 02:26:10 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA13711 for ; Fri, 5 Jun 1998 02:24:20 -0700 (PDT) (envelope-from hiren@tagore.wipinfo.soft.net) From: hiren@tagore.wipinfo.soft.net Received: from tagore.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id OAA12417; Fri, 5 Jun 1998 14:50:01 -0500 Message-ID: <9806051459.AA26054@tagore.wipinfo.soft.net> Subject: User creds for MSDOSFS To: freebsd-fs@FreeBSD.ORG Date: Fri, 5 Jun 1998 13:11:56 +0530 (IST) Reply-To: hiren@tagore.wipinfo.soft.net Content-Type: text Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Return-Receipt-To:hiren X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 939 Hi All, Can somebody explain how user credentials are handled in case of MSDOSFS ? who all are allowed to access/modify files/directory once file system of type MSDOSFS is mounted ? -- Hiren `All rights left. All lefts reserved. All reserves removed. All removes right.' CHANGE IN EXTENSION NUMBER //// (o o) -------------------------oOO--(_)--OOo----------------------------------- Hiren Mehta --- Email address : AT&T Dedicated Facility /o o\ hiren@wipinfo.soft.net Wipro Infotech Ltd(ADF) | O | Phone: 91-080-2241735, 2241730 Divyasree Complex, \_-_/ 2241735, 2241768 30, Mission Road, Ist Main, Extn. 3411 S. R. Nagar, Bangalore - 560 027 Fax: 91-080-2241769 ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Jun 5 11:19:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13605 for freebsd-fs-outgoing; Fri, 5 Jun 1998 11:19:10 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13591 for ; Fri, 5 Jun 1998 11:19:05 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA20456; Fri, 5 Jun 1998 11:18:57 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd020423; Fri Jun 5 11:18:49 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id LAA15966; Fri, 5 Jun 1998 11:18:47 -0700 (MST) From: Terry Lambert Message-Id: <199806051818.LAA15966@usr05.primenet.com> Subject: Re: User creds for MSDOSFS To: hiren@tagore.wipinfo.soft.net Date: Fri, 5 Jun 1998 18:18:47 +0000 (GMT) Cc: freebsd-fs@FreeBSD.ORG In-Reply-To: <9806051459.AA26054@tagore.wipinfo.soft.net> from "hiren@tagore.wipinfo.soft.net" at Jun 5, 98 01:11:56 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can somebody explain how user credentials are handled in case of MSDOSFS ? > who all are allowed to access/modify files/directory once file system of > type MSDOSFS is mounted ? All files are assumed to have the same user and group ownership, and permissions, that were specified at mount time via the -u, -g, and -m options, respectively. Udo Walter (sp?) created in Linux an FS called "UMSDOSFS", which supports full UNIX semantics on files using a seperate "poop file" named "-LINUX--.---" (better would have been "-UMSDOS-.--"; it's more symmetric, and it's not system-dependent). You could do a similar thing in FreeBSD, if the FS stacking issues were resolved, or if you wanted to modify the MS-DOS FS code (ie: make it a non-stacked monolithic implementation). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message