From owner-freebsd-hackers Tue Oct 1 12:02:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11850 for hackers-outgoing; Tue, 1 Oct 1996 12:02:35 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA11844 for ; Tue, 1 Oct 1996 12:02:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA02235; Tue, 1 Oct 1996 12:01:06 -0700 From: Terry Lambert Message-Id: <199610011901.MAA02235@phaeton.artisoft.com> Subject: Re: VPS mailing list, BSD interest? To: michaelh@cet.co.jp (Michael Hancock) Date: Tue, 1 Oct 1996 12:01:06 -0700 (MST) Cc: ccsanady@friley216.res.iastate.edu, hackers@freebsd.org In-Reply-To: from "Michael Hancock" at Oct 1, 96 01:45:04 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > NTFS also uses b-trees. Actually it uses a linear directory structure for > small directories and b-trees for larger directories. This optimization > reminds me of the direct inode/indirect inode scheme used in FFS. NTFS would be a better choice, since JFS is pretty much IBM specific. The only reason I pursued JFS at all was for cross developement in my PPC porting environment. My developement is hosted under AIX. Biunary compatability issues were a secondary consideration (after making the thing boot). One of my big blocks has been replacing the IBM boot code with freely distributable boot code; I don't have a decent PPC disassembler, and Arrow Electronics has failed to send the PPCBug documentation to the right address or via the right shipper to the tune of multiple hundreds of dollars. This is made worse by the fact that PPCBug is "going away", to be replaced by OpenBoot. All in all, for compatability, an NTFS would be a better choice, since FreeBSD is currently very Intel specific anyway. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.