signal 12's everywhere on Current with update this morning.

[Richard Coleman]

Sure.  I can do that.  Some structures in statfs changed size.  So you 
need to rebuild and install your kernel before you update the world. 
The instructions in the handbook should work just fine.

1. make buildworld
2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE
3. make installkernel KERNCONF=NAME_OF_KERNEL_FILE
4. shutdown -r now
5. boot into single user mode
6. fsck -p
7. mount -u /
8. mount -a -t ufs
9. swapon -a
10. make installworld
11. mergemaster
12. reboot

There are a couple ports that also need rebuilt.  I've heard cfs and 
postfix mentioned.  There could be more.  If you don't have many ports, 
just rebuild them all (that's what I'm doing).  If you are using 
portupgrade, it's easy (portupgrade -afR).  Obviously this could take 
awhile.

Richard Coleman
richardcoleman at mindspring.com

Edmund L. Wong wrote:

> Could someone bring me up to speed on this thread?  I
> just joined current and I also updated this morning
> and have all kinds of issues.
> 
> THanks,
> Ed
> 
> 
> --- Richard Coleman <richardcoleman at mindspring.com>
> wrote:
> 
>>Someone just needs to bring the build(7) man page up
>>to date with the 
>>handbook.
>>
>>Also, I noticed that build(7) still lists the
>>"installmost" build 
>>target.  I believe that was removed.
>>
>>I would file a PR except that my man pages always
>>suck.
>>
>>Richard Coleman
>>richardcoleman at mindspring.com
>>
>>Brent Jones wrote:
>>
>>
>>>If this is true, perhaps the "build" man page
>>
>>should be updated.  Here's 
>>
>>>what the man page has to say on the topic:
>>>
>>>     The ``approved'' method of updating your
>>
>>system from the latest 
>>
>>>sources
>>>     is:
>>>
>>>           make buildworld
>>>           make buildkernel KERNCONF=FOO
>>>           make installkernel KERNCONF=FOO
>>>           make installworld
>>>           mergemaster
>>>
>>>     After running these commands a system reboot
>>
>>is required...
>>
>>>This gives the impression that you're safe running
>>
>>all the builds 
>>
>>>without rebooting, especially as the word
>>
>>"approved" is used.
>>
>>>Brent
>>>
>>>On Nov 13, 2003, at 11:18 PM, M. Warner Losh
>>
>>wrote:
>>
>>>>In message: <3FB3BB9A.8080703 at despammed.com>
>>>>            Uwe Laverenz <laverenz at despammed.com>
>>
>>writes:
>>
>>>>: eculp at encontacto.net schrieb:
>>>>:
>>>>: > Uwe, do you have any remote machines?  I'm
>>
>>wondering what the correct
>>
>>>>: > sequence would be to update and reboot them.
>>>>:
>>>>: I would suggest to do it this way:
>>>>:
>>>>: 1. make buildworld
>>>>: 2. make kernel KERNCONF=<YOURCONF>
>>>>: 3. *reboot* (with new kernel and old userland)
>>>>
>>>>Into single user...
>>>>
>>>>: 4. make installworld
>>>>: 5. mergemaster
>>>>: 6. *reboot*
>>>>
>>>>This is the order that's recommended in UPDATING
>>
>>since 3.something.
>>
>>>>Warner
>>
>>
>>
>>_______________________________________________
>>freebsd-current at freebsd.org mailing list
>>
> 
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> 
>>To unsubscribe, send any mail to
> 
> "freebsd-current-unsubscribe at freebsd.org"
> 
> 
> =====
> edmund l wong
> assistant staff : mit lincoln lab 
> cs/ece alumni : carnegie mellon
> 
> ewong at alumni.cmu.edu
> http://www.edmundlwong.com