On Tue, Feb 28, 2006 at 10:30:16AM -0600, Donald J. O'Neill wrote: > > > Could you explain the logic of running mergemaster -p, when you > > > have nothing to run it on. /usr/obj was blown away at the beginning > > > of the buildworld sequence. What are you going to check at that > > > point? Please take a look at the handbook for the sequence that > > > things should occur in. I would say look at /usr/src/UPDATING, but > > > their sequence doesn't include installing the kernel anymore. > > > > He means to run mergemaster -p before make installworld, as in the > > instructions quoted at the top of this email and in > > /usr/src/UPDATING. Also, the documented sequence *does* include > > installing the kernel, so I don't know what you mean there either. > > > > Kris > > He may mean that, but it's not what he said. I went by what he said.
OK, but you were still confused, because mergemaster doesn't need a populated /usr/obj to do its thing (only a source tree). You can run it at any time, before during or after your buildworld. > make kernel KERNCONF=YOUR_KERNEL_HERE [8] > [1] > <reboot in single user> [3] > mergemaster -p [5] > make installworld > make delete-old > mergemaster -i [4] > <reboot> > > I just don't see where it says "make installkernel KERNCONF=YOUR_KERNEL. > It used to. That's where I got my original procedure from as the > handbook at the time was somewhat confusing. Now the procedure in the > handbook is better. 'make kernel' = 'make buildkernel' + 'make installkernel' Kris
pgpOBNb7fF3jG.pgp
Description: PGP signature
