From owner-freebsd-fs Sat Oct 30 14:55:12 1999 Delivered-To: freebsd-fs@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id A8C5514C2F for ; Sat, 30 Oct 1999 14:54:57 -0700 (PDT) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id RAA69835 for ; Sat, 30 Oct 1999 17:54:56 -0400 (EDT) Date: Sat, 30 Oct 1999 17:54:56 -0400 (EDT) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: freebsd-fs@freebsd.org Subject: Re: Journaling 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 > > It has been that way for a long time. I'm not sure why the limit is > > 8, but it is. (Someone might know. I suspect it was just an > > arbitrary value chosen a long time ago.) Changing it might break > > backwards compatibility, though. > > NetBSD currently supports 16.Yes, it > breaks backward compatability. > > Terry Lambert > terry@lambert.org Slightly off topic (as if the topic were about journalling anymore in this thread anyway :) )... From my perusal of the code, it looks as if the NetBSD change from 386BSD's partition ID of 165 (which we still use) to 169 is unrelated to the change to 16 partitions. Actually, I can't find where it is useful at all; I would have assumed that if they were going to break backward-compatibility by going to 16 partitions, switching MBR partition IDs at the same time would be logical. Does anyone here know the reasoning between switching MBR partition IDs? Just curious, Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message