From owner-freebsd-alpha Wed Jan 9 8:55:26 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id 3446537B41F for ; Wed, 9 Jan 2002 08:55:19 -0800 (PST) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Wed, 9 Jan 2002 17:55:17 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA23E@l04.research.kpn.com> From: "Koster, K.J." To: "'naddy@mips.inka.de'" Cc: freebsd-alpha@FreeBSD.ORG Subject: RE: -CURRENT boot1 broken? Date: Wed, 9 Jan 2002 17:55:14 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear All, > > > > This suggests that boot1 is broken. > > > > Ugh, it shouldn't be. :( > > Well, I guess it isn't. When I moved my system to a new disk, I > created all filesystems with 16384/2048. Pretty useless for the > root filesystem, I admit, except for consistency's sake. Turns out > that boot1 doesn't handle this. Jumping through some hoops I have > moved / back to 8192/1024 and it works fine now. *Sigh* > I ran into this myself a few years back (on i386). At the very least the loader might detect the block size mismatch and complain. On the other hand: "man newfs" tells us: BUGS The boot code of FreeBSD assumes that the file system that carries the kernel has blocks of 8 kilobytes and fragments of 1 kilobyte. You will not be able to boot from a file system that uses another size. IIRC this was put in after I whined about it for a bit. :) Kees Jan ===================================================== You can't have everything. Where would you put it? [Steven Wright] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message