Date: Sun, 28 Mar 1999 16:38:45 -0600 From: "Brian D. Woodruff" <wood@eris.quintessential.com> To: "Paul T. Root" <proot@iaces.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 3.1 UNstable Message-ID: <3.0.6.32.19990328163845.008d02b0@freeq.com> In-Reply-To: <199903282155.PAA26891@iaces.com> References: <3.0.6.32.19990327211654.008b91f0@freeq.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"dangerously dedicated" *IS* a 165 FreeBSD slice, so called because you can't share it with another operating system, and no, that was not the problem. THIS was the problem ... If you want to get 3.1-RELEASE or 3.1-STABLE (which is currently a link back to 3.1-RELEASE), you MUST use the floppy disks for 3.1-RELEASE, because the install program puts its own kernel loader on the hard disk, regardless whether it is appropriate for the kernel it is installing. The resultant error message is "invalid format!" if you use the wrong loader. This also happens if you try to upgrade using /stand/systinstall on any previous version of FreeBSD, including 3.0! - please see my lengthy post on the list for details. BDW At 03:55 PM 3/28/99 -0600, you wrote: >> >- Did you install new boot blocks? >> >> yup. "dangerously dedicated" FreeBSD ones, no boot manager, cos we *LIKE* >> being dangerously dedicated. >> >> >- Did you build your own kernel? > >I've found that dangerously dedicated fails much more often than just >making a FBSD (165) slice, even when it's the whole disk. You'll often >run into geometry problems this way. Which, btw, I suspect in this case. > > > >-- >The car ran out of gas. >--from "Excuses, Excuses" *the* compendium of excuses by Leigh W. Rutledge > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.6.32.19990328163845.008d02b0>