Howdy,

I've found the following sequence to be optimal from going from
pre-dirpref -current to post-dirpref -current and 4-stable to -current:

make buildworld
make buildkernel KERNCONF=YOUR_KERNEL_HERE
make installkernel KERNCONF=YOUR_KERNEL_HERE
make installworld
mergemaster
<reboot to single user>
fsck all partitions, answering yes to all prompts
tunefs -A -s <n> all partitions, where N > 0

I found that the newer fsck didn't help any.

Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664  Fax: +61 3 6331 7032  Mob: +61 419 528 795
Web: http://www.aims.com.au



> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of John Baldwin
> Sent: Sunday, 22 April 2001 3:27
> To: David W. Chapman Jr.; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: kernel core
>
>
>
> On 21-Apr-01 David W. Chapman Jr. wrote:
> > I just tried to do an installkernel on a new kernel I built
> and I got the
> > same error except the last line changed to
> >
> > stopped at    ffs_dirpref+0x210    movzbl    0(%ECX,%EAX,1),%EAX
> >
> > Do I have any hope at recovering from this or should I
> start again with 4
> > and upgrade to -current.  I'm assuming is a problem with
> the kernel and
> > without being able to update the kernel and install a new
> one, I don't think
> > I can fix it.
>
> You need to rebuild fsck and install it and fsck your
> filesystems.  This is the
> dirpref changes biting you.  Warner, we probably need an
> entry in UPDATING for
> the dirpref changes that warn people to build and install a
> new fsck before
> booting a dirpref kernel.
>
> --
>
> John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
> PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
> "Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to