From owner-freebsd-fs Sun Feb 23 15:01:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA07356 for fs-outgoing; Sun, 23 Feb 1997 15:01:42 -0800 (PST) Received: from clgrps05.agt.net (clgrps05.agt.net [198.161.156.16]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA07333; Sun, 23 Feb 1997 15:01:34 -0800 (PST) Received: from scottgum ([204.209.197.208]) by mail.telusplanet.net with ESMTP id <153356-7865>; Sun, 23 Feb 1997 16:01:22 -0700 Message-ID: <3310CBB7.2EF5@hg.uleth.ca> Date: Sun, 23 Feb 1997 15:59:03 -0700 From: Scott Guminy Reply-To: gumism@hg.uleth.ca Organization: The University of Lethbridge X-Mailer: Mozilla 4.0b2 (Win95; I) MIME-Version: 1.0 To: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Newbie: Install question X-Priority: 3 (Normal) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm just new to FreeBSD. Is it possible to install FreeBSD on top of a MS-DOS (Win95 -- not FAT32) filesystem without creating a separate partition? I've done this with the slackware distribution of Linux using the UMSDOS install. TIA, Scott From owner-freebsd-fs Sun Feb 23 16:39:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA13433 for fs-outgoing; Sun, 23 Feb 1997 16:39:56 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA13407; Sun, 23 Feb 1997 16:39:46 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA03378; Mon, 24 Feb 1997 11:09:33 +1030 (CST) From: Michael Smith Message-Id: <199702240039.LAA03378@genesis.atrad.adelaide.edu.au> Subject: Re: Newbie: Install question In-Reply-To: <3310CBB7.2EF5@hg.uleth.ca> from Scott Guminy at "Feb 23, 97 03:59:03 pm" To: gumism@hg.uleth.ca Date: Mon, 24 Feb 1997 11:09:32 +1030 (CST) Cc: freebsd-fs@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Scott Guminy stands accused of saying: > > Is it possible to install FreeBSD on top of a MS-DOS (Win95 -- not > FAT32) filesystem without creating a separate partition? I've done this > with the slackware distribution of Linux using the UMSDOS install. No. Whilst it might be marginally useful, the performance of such a filesystem would be so apalling that there aren't any FreeBSD hackers that feel that it's worth the effort. > Scott -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-fs Sun Feb 23 22:36:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA01965 for fs-outgoing; Sun, 23 Feb 1997 22:36:15 -0800 (PST) Received: from clgrps05.agt.net (clgrps05.agt.net [198.161.156.16]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA01950; Sun, 23 Feb 1997 22:36:10 -0800 (PST) Received: from scottgum ([204.209.197.184]) by mail.telusplanet.net with ESMTP id <154217-7865>; Sun, 23 Feb 1997 23:34:55 -0700 Message-ID: <331135AE.F5E@hg.uleth.ca> Date: Sun, 23 Feb 1997 23:31:10 -0700 From: Scott Guminy Reply-To: gumism@hg.uleth.ca Organization: The University of Lethbridge X-Mailer: Mozilla 4.0b2 (Win95; I) MIME-Version: 1.0 To: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Install question X-Priority: 3 (Normal) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I read somewhere that you shouldn't install FreeBSD on a partition that starts after a certain cylinder (I forget which one). Is this true? I'd like to install it on a partition that starts at cylinder 845 or higher, will I have problems if I do this? TIA, Scott From owner-freebsd-fs Tue Feb 25 04:55:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA20344 for fs-outgoing; Tue, 25 Feb 1997 04:55:17 -0800 (PST) Received: from nyx.pr.mcs.net (nyx.pr.mcs.net [204.95.55.81]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA20335 for ; Tue, 25 Feb 1997 04:55:11 -0800 (PST) Received: from nyx.pr.mcs.net (localhost [127.0.0.1]) by nyx.pr.mcs.net (8.8.5/8.8.4) with ESMTP id GAA03348 for ; Tue, 25 Feb 1997 06:55:03 -0600 (CST) Message-Id: <199702251255.GAA03348@nyx.pr.mcs.net> X-Mailer: exmh version 2.0beta 12/23/96 To: freebsd-fs@freebsd.org Subject: Coda File system... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Feb 1997 06:55:03 -0600 From: Chris Csanady Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For those who are interested, I came across a rather interesting project at CMU. The Coda file system is a file system based on AFS, but extended to provide increased availability even when completely disconnected--suitable for mobil users as well. I've not had a chance to look at the copyright, or source, but I think the terms would be ok. The page is at: http://www-cgi.cs.cmu.edu/afs/cs/project/coda/Web/coda.html If the code is fairly mature, perhaps its worth a look. If not, I think its essentially AFS, plus more. Possibly we could reverse engineer it and end up with a standard AFS. Either way, I would love to see a real remote filesysem for FreeBSD. :) Although I've looked, I've never been able to find the original AFS source from before it went commercial. :( If anyone has this, I'd love to get a copy... --Chris Csanady From owner-freebsd-fs Tue Feb 25 05:34:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA21517 for fs-outgoing; Tue, 25 Feb 1997 05:34:16 -0800 (PST) Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA21508 for ; Tue, 25 Feb 1997 05:34:13 -0800 (PST) Received: (from assar@localhost) by assaris.sics.se (8.7.5/8.7.3) id OAA09827; Tue, 25 Feb 1997 14:32:54 +0100 (MET) To: Chris Csanady Cc: freebsd-fs@FreeBSD.org Subject: Re: Coda File system... References: <199702251255.GAA03348@nyx.pr.mcs.net> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 25 Feb 1997 14:32:53 +0100 In-Reply-To: Chris Csanady's message of Tue, 25 Feb 1997 06:55:03 -0600 Message-ID: <5l3eulgge2.fsf@assaris.sics.se> Lines: 25 X-Mailer: Gnus v5.2.40/Emacs 19.34 Sender: owner-fs@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Chris Csanady writes: > For those who are interested, I came across a rather interesting project at > CMU. The Coda file system is a file system based on AFS, but extended to > provide increased availability even when completely disconnected--suitable > for mobil users as well. I've not had a chance to look at the copyright, or > source, but I think the terms would be ok. The page is at: > http://www-cgi.cs.cmu.edu/afs/cs/project/coda/Web/coda.html Yes, Coda is nice. > If the code is fairly mature, perhaps its worth a look. If not, I think its > essentially AFS, plus more. Possibly we could reverse engineer it and end > up with a standard AFS. Either way, I would love to see a real remote > filesysem for FreeBSD. :) Although I've looked, I've never been able to find > the original AFS source from before it went commercial. :( If anyone has this, > I'd love to get a copy... Keep in mind that Coda branched of during AFS2 and thus have very little in common with AFS3 from Transarc, so you'll not be able to make an AFS out of Coda. And I don't think there is any AFS2 code available, because it was funded by IBM and they kept all the rights. And then, I think it would take lots of work to make something stable and usable out of it (it took Transarc some time, as well). /assar From owner-freebsd-fs Fri Feb 28 15:32:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA25459 for fs-outgoing; Fri, 28 Feb 1997 15:32:24 -0800 (PST) Received: from citrine.cyberstation.net (hannibal@citrine.cyberstation.net [205.167.0.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA25452 for ; Fri, 28 Feb 1997 15:32:22 -0800 (PST) Received: from localhost (hannibal@localhost) by citrine.cyberstation.net (8.8.5/8.8.4) with SMTP id RAA06619 for ; Fri, 28 Feb 1997 17:32:20 -0600 (CST) Date: Fri, 28 Feb 1997 17:32:20 -0600 (CST) From: Dan Walters To: freebsd-fs@freebsd.org Subject: How to get the parent directory vnode of a vnode? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm starting on an attempt to implement an ACL filesystem layer, mostly using some ideas from a message I found of Terry Lambert's back in December (part of it is below my sig). So far I've got the bytestuffing for the filenames done, the necessary changes in VOP_READDIR to un-bytestuff the filenames and hide the actual ACL files, and a decent start on the userland utility... Not much, but it's my first time touching the kernel... Anyway, I'm now trying to have it read the actual ACL file into a buffer in the layer's per-vnode structure. I just noticed, however, that there is no reference to the parent directory's vnode in a vnode structure, so I'm having some difficulty deciding on the proper way to lookup the vnode for the ACL file (which is kept in the same directory). There is mention of putting the parent directory inode in the ufs layer, but I'm figuring this would probably not work with NFS, multiple layers, etc.? If I just trap VOP_LOOKUP, VOP_CREATE, and save the parent directory for each vnode at that point, would there ever be any case where I wouldn't have a parent directory vnode? Also, I want to make sure nobody else is working on something like this. :) I'd also like to get ahold of the VOP_*.9 manpages that I see mention of in the list archives - I can't locate them on freefall. I broke down and bought the 4.4BSD book, but it doesn't really go to the level of depth I was expecting on much anything. Thanks! ====================================================================== Dan Walters hannibal@cyberstation.net ====================================================================== 1) Modify the VOP_ADVLOCK to be veto-based 2) Modify the VOP_LOCK code to be veto based. Call a top level vn_lock to call the underlying VOP_LOCK. Move the vclean locking to the top level code. Now NULLFS will no longer crash. If you have a 2.1.5 kernel, take my patches from -current in June of 1995; they contain this fix. Using NULLFS, prototype an FS layer that sits on top of an FS using the following user name space intrusions: 1) If a file name starts with #, byte-stuff it to ## 2) Use all #... file names as names associated with a base inode number 3) Add in the stacking layer a VOP_IOCTL operation for ACL's. 4) Add subfunctions for "create/delete/add/delete/get" ACL. 5) Write a user space utility to manipulate ACL's. 6) For a file in the directory named "foo", with inode "1745", the ACL file will be named "#1745". 7) Store all ACL's in the appropriate file. I recommend a sparse file. 8) Modify the VOP's which take names and call the common lookup code to enforce your ACL's. 9) remount the FS using the new NULL-derived ACL layer onto the same mount point. When backing up, unmount the ACL layer so the backup utility can see the ACL containers as files in the underlying FS. 10) If you support reverse inheritance, modify the UFS create to store the parent directory inode in the underlying inode. Add an option to fsck (during pass 7) to set these for the first time you start using the new UFS code. You now have *real* ACL's.