> From: Fritz Heinrichmeyer <fritz.heinrichmeyer_at_fernuni-hagen.de> > Date: Wed, 28 Apr 2004 09:16:51 +0200 > Sender: owner-freebsd-current_at_freebsd.org > > Am Dienstag, 27. April 2004 19:28 schrieb Doug White: > > On Mon, 26 Apr 2004, Fritz Heinrichmeyer wrote: > > > recently i had no success in using boot0cfg and bsdlabel to repair boot > > > process under current. The only way that worked was booting with a > > > live-cd and using sysinstall from there. Is there some documentation > > > regarding freebsd-current for this? > > > > Man pages :) I think there is a handbook section on boot0cfg too, > > although I'd have to check. > > the line > > boot0cfg -m 0x5 -B -o packet ad0 || echo there were problems > > worked, the new mask showed that that there was actually something written and > boot process was no more broken. > > Maybe "-o packet" is a good default these days ... It probably should be. The number of systems not supporting it is getting smaller all of the time and the number of cases where the FreeBSD partition is not bootable without it is rapidly growing. It's VERY common to have Windows in the first slice and FreeBSD in the second (or higher). The size of the slice dedicated to Windows is often rather large so that the FreeBSD slice becomes unbootable unless -o packet is added. There is a POLA issue, so it would clearly need reference in UPDATING and such. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman_at_es.net Phone: +1 510 486-8634Received on Wed Apr 28 2004 - 09:22:34 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:52 UTC