Date: Wed, 9 Jan 2002 17:55:14 +0100 From: "Koster, K.J." <K.J.Koster@kpn.com> To: "'naddy@mips.inka.de'" <naddy@mips.inka.de> Cc: freebsd-alpha@FreeBSD.ORG Subject: RE: -CURRENT boot1 broken? Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA23E@l04.research.kpn.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59063B5B4D98D311BC0D0001FA7E452205FDA23E>