Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
--- Dag-Erling Smørgrav [EMAIL PROTECTED] wrote: masta [EMAIL PROTECTED] writes: I found that if I put /rescue in my PATH before all the normal stuff, things tend to work (like ls). For me I got caught doing the: make buildworld make buildkernel KERNCONF=FOO make installkernel mergemaster make installworld BAM! installworld fails, and the signal 12's start to manifest. Reboot and run installworld. Your new kernel will run both old and new binaries just fine. I tried that and it didn't work because some of the binaries didn't get installed and caused signal 11's ??? So what I did was scp /bin/* /usr/bin/* /sbin/* /usr/sbin/* /usr/libexec/* Certainly not the most efficient solution and I probably shouldn't have had to do it but I had 4 servers stuck and only one up to dade and working with the changes and I just wanted to get through this and cut my losses :-) (But that is another story.) You might want to have a cdrom or another machine that is up to date and readily accessable, just in case. Good luck, ed __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
Richard Coleman wrote: Andy Farkas wrote: Richard Coleman wrote: 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 9.5 adjkerntz -i Yep, forgot that part. I keep all my system clocks on UTC so I never do this step when building world. Running -CURRENT, I've gotten into the pattern of always building and installing a new /usr/include, just to be extra safe. 10a. cd /usr; mv include inc.old; mkdir include; cd /usr/src; make includes 10. make installworld 11. mergemaster 12. reboot Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
masta [EMAIL PROTECTED] writes: I found that if I put /rescue in my PATH before all the normal stuff, things tend to work (like ls). For me I got caught doing the: make buildworld make buildkernel KERNCONF=FOO make installkernel mergemaster make installworld BAM! installworld fails, and the signal 12's start to manifest. Reboot and run installworld. Your new kernel will run both old and new binaries just fine. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
Date: Sat, 15 Nov 2003 09:51:40 +1000 (EST) From: Andy Farkas [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Richard Coleman wrote: 0. mergemaster -p 1. make buildworld 2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE 3. make installkernel KERNCONF=NAME_OF_KERNEL_FILE 2 and 3 may be combined into 'make kernel KERNCONF=NAME_OF_KERNEL_FILE' 4. shutdown -r now 5. boot into single user mode 6. fsck -p 7. mount -u / This is redundant. Since V4 days 'mount -a -t ufs' will make root (and any other devices listed as RW in fstab) RW. 8. mount -a -t ufs 9. swapon -a 9.5 adjkerntz -i 10. make installworld 11. mergemaster 12. reboot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
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: [EMAIL PROTECTED] Uwe Laverenz [EMAIL PROTECTED] writes: : [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
In message: [EMAIL PROTECTED] Brent Jones [EMAIL PROTECTED] writes: : 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: Already done. : 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. Yes. I just added a 'reboot to single user here' line. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] Uwe Laverenz [EMAIL PROTECTED] writes: : [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] Uwe Laverenz [EMAIL PROTECTED] writes: : [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] = edmund l wong assistant staff : mit lincoln lab cs/ece alumni : carnegie mellon [EMAIL PROTECTED] http://www.edmundlwong.com __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] Uwe Laverenz [EMAIL PROTECTED] writes: : [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] = edmund l wong assistant staff : mit lincoln lab cs/ece alumni : carnegie mellon [EMAIL PROTECTED] http://www.edmundlwong.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
Thanks Richard. So unfortunately, I was an idiot and ran installworld without rebuilding and installing a new kernel (the one I have was built on Nov. 1). Now everything coredumps, including rm, ls, etc. I cannot make installworld, installkernel, buildworld or buildkernel. I am able to get myself to a single-user prompt as root, but not much else. Does anyone have any suggestions as to how I can salvage this? Or will I have to reinstall anew? (for those in freebsd-questions, I apologize in advance, I asked there earlier this morning as well) Thanks, Ed --- Richard Coleman [EMAIL PROTECTED] wrote: 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] Uwe Laverenz [EMAIL PROTECTED] writes: : [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] = edmund l wong assistant staff : mit lincoln lab cs/ece alumni : carnegie mellon [EMAIL PROTECTED] http://www.edmundlwong.com = edmund l wong assistant staff : mit lincoln lab cs/ece alumni : carnegie mellon [EMAIL PROTECTED] http://www.edmundlwong.com __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
+---[ Edmund L. Wong ]-- | | I am able to get myself to a single-user prompt as | root, but not much else. Does anyone have any | suggestions as to how I can salvage this? Or will I | have to reinstall anew? Boot from a live/fixit CD/floppy, and mount your drives and rebuild and install the kernel? Having a bootable live cd around can be a lifesaver. -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | M:+61 416 022 411 | ACN: 082 081 472 ABN: 83 082 081 472 |[EMAIL PROTECTED]| Carpe Daemon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
Dag-Erling Smørgrav wrote: [EMAIL PROTECTED] writes: I'm building new kernels as I write this. My next question is: One of the machines I'm building on is remote and was last rebuilt just before the change. What would be be better sequence for making the change after a fresh cvsup ? RTFM. make buildworld make buildkernel make installkernel reboot make installworld mergemaster reboot DES I found that if I put /rescue in my PATH before all the normal stuff, things tend to work (like ls). For me I got caught doing the: make buildworld make buildkernel KERNCONF=FOO make installkernel mergemaster make installworld BAM! installworld fails, and the signal 12's start to manifest. I'm afraid to reboot at this point, and decided to backup my stuff before proceeding with anything (rebooting) that might result in my system becoming utterly useless. Should I manually copy the items in /usr/obj to their final destination, or take my chances with a reboot? Maybe wait for the jpsnap to catchup and boot a -current livecd to finish the makeinstall? I'm seeking the path of least resistance which involves anything other than flattening my -current install. Thanks in advance =) __ __ _ | \/ | __ _ ___| |_ __ _ | |\/| |/ _` / __| __/ _` | | | | | (_| \__ \ || (_| | |_| |_|\__,_|___/\__\__,_| unzip ; strip ; touch ; finger ; mount ; fsck ; more ; yes ; umount ; sleep [EMAIL PROTECTED] http://wifibsd.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
Richard Coleman wrote: 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 9.5 adjkerntz -i 10. make installworld 11. mergemaster 12. reboot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
Andy Farkas wrote: Richard Coleman wrote: 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 9.5 adjkerntz -i Yep, forgot that part. I keep all my system clocks on UTC so I never do this step when building world. 10. make installworld 11. mergemaster 12. reboot Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote: I installed an older current snap, Oct 26, on a brandnew dell power edge with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great. I installed everything except the kitchen sink. Then I decided it was time to update, I've got serveral other machines weathering the storms. Bad idea. It doesn't hang or anything that I can get my teeth into but it just give signal 12 core dumps on many if not most applications. I caught this before finishing an install on another box, yesterday morning. One of the apps that generates signal 12 is ls so I tried pulling ls from the other box and it no longer has a problem. I am at a lost. Any suggestions for where to start would be appreciated. Read /usr/src/UPDATING. Ceri -- pgp0.pgp Description: PGP signature
Re: signal 12's everywhere on Current with update this morning.
Mensaje citado por Ceri Davies [EMAIL PROTECTED]: | On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote: | I installed an older current snap, Oct 26, on a brandnew dell power edge | with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great. | I installed everything except the kitchen sink. Then I decided it was | time to update, I've got serveral other machines weathering the storms. | Bad idea. It doesn't hang or anything that I can get my teeth into but | it just give signal 12 core dumps on many if not most applications. I | caught this before finishing an install on another box, yesterday morning. | One of the apps that generates signal 12 is ls so I tried pulling ls | from the other box and it no longer has a problem. I am at a lost. | Any suggestions for where to start would be appreciated. | | Read /usr/src/UPDATING. | Thanks, I missed that. :( Sorry for the noise. ed - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
Mensaje citado por [EMAIL PROTECTED]: | Mensaje citado por Ceri Davies [EMAIL PROTECTED]: | | | On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote: | | I installed an older current snap, Oct 26, on a brandnew dell power edge | | with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great. | | I installed everything except the kitchen sink. Then I decided it was | | time to update, I've got serveral other machines weathering the storms. | | Bad idea. It doesn't hang or anything that I can get my teeth into but | | it just give signal 12 core dumps on many if not most applications. I | | caught this before finishing an install on another box, yesterday | morning. | | One of the apps that generates signal 12 is ls so I tried pulling ls | | from the other box and it no longer has a problem. I am at a lost. | | Any suggestions for where to start would be appreciated. | | | | Read /usr/src/UPDATING. | | | Thanks, I missed that. :( Sorry for the noise. | | ed I'm building new kernels as I write this. My next question is: One of the machines I'm building on is remote and was last rebuilt just before the change. What would be be better sequence for making the change after a fresh cvsup ? 1. Build and Install a new kernel 2. build a new world 3. Run mergemaster 4. ReBoot (I'm not sure it will come up multiuser with a new kernel and a 4 day old userland.) 5. Installworld and assess possible problems :-) or 1. Build and Install a new kernel 2. make buildworld 3. Run mergemaster 4. make installworld; shutdown -r now # and pray :-) Or is there a better option? Has anyone else already done this? Thanks, ed - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
[EMAIL PROTECTED] schrieb: Thanks, I missed that. :( Sorry for the noise. You're not the only one who missed that. We killed 2 machines yesterday evening (~11pm CET) this way. I think I did read UPDATING and I can't remember any warning entries?! It's there now, of course so we were just running cvsup a few hours too early I guess. ;) Anyway, things like this can happen if you decide to run -CURRENT. :-) cu, Uwe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
Mensaje citado por Uwe Laverenz [EMAIL PROTECTED]: | [EMAIL PROTECTED] schrieb: | | Thanks, I missed that. :( Sorry for the noise. | | You're not the only one who missed that. We killed 2 machines yesterday | evening (~11pm CET) this way. I think I did read UPDATING and I can't | remember any warning entries?! It's there now, of course so we were just | running cvsup a few hours too early I guess. ;) | | Anyway, things like this can happen if you decide to run -CURRENT. :-) Uwe, do you have any remote machines? I'm wondering what the correct sequence would be to update and reboot them. Thanks, ed - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
On Thu, Nov 13, 2003 at 07:39:15AM -0800, [EMAIL PROTECTED] wrote: Mensaje citado por [EMAIL PROTECTED]: | Mensaje citado por Ceri Davies [EMAIL PROTECTED]: | | | On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote: | | I installed an older current snap, Oct 26, on a brandnew dell power edge | | with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great. | | I installed everything except the kitchen sink. Then I decided it was | | time to update, I've got serveral other machines weathering the storms. | | Bad idea. It doesn't hang or anything that I can get my teeth into but | | it just give signal 12 core dumps on many if not most applications. I | | caught this before finishing an install on another box, yesterday | morning. | | One of the apps that generates signal 12 is ls so I tried pulling ls | | from the other box and it no longer has a problem. I am at a lost. | | Any suggestions for where to start would be appreciated. | | | | Read /usr/src/UPDATING. | | | Thanks, I missed that. :( Sorry for the noise. | | ed I'm building new kernels as I write this. My next question is: One of the machines I'm building on is remote and was last rebuilt just before the change. What would be be better sequence for making the change after a fresh cvsup ? 1. Build and Install a new kernel 2. build a new world 3. Run mergemaster 4. ReBoot (I'm not sure it will come up multiuser with a new kernel and a 4 day old userland.) 5. Installworld and assess possible problems :-) I upgraded a ancient -current last night, I did 1) cvsup 2) build and install new kernel 3) reboot 4) build and isntall new world 5) mergemaster 6) reboot /Jesper ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
[EMAIL PROTECTED] 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) 4. make installworld 5. mergemaster 6. *reboot* cu, Uwe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
Mensaje citado por Jesper Skriver [EMAIL PROTECTED]: | On Thu, Nov 13, 2003 at 07:39:15AM -0800, [EMAIL PROTECTED] wrote: CUT | I'm building new kernels as I write this. My next question is: | One of the machines I'm building on is remote and was last rebuilt | just before the change. What would be be better sequence for making | the change after a fresh cvsup ? | |1. Build and Install a new kernel |2. build a new world |3. Run mergemaster |4. ReBoot (I'm not sure it will come up multiuser with a new | kernel and a 4 day old userland.) |5. Installworld and assess possible problems :-) | | I upgraded a ancient -current last night, I did | | 1) cvsup | 2) build and install new kernel | 3) reboot | 4) build and isntall new world | 5) mergemaster | 6) reboot Jesper, Thanks. I'm already finishing a buildworld but I'm going to reboot after before installworld, I've already installed the kernel. I was afraid it would't go multiuser so I could finish with a ssh. Thanks for confirming that it will, or should :-) ed | | /Jesper | - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
[EMAIL PROTECTED] writes: I'm building new kernels as I write this. My next question is: One of the machines I'm building on is remote and was last rebuilt just before the change. What would be be better sequence for making the change after a fresh cvsup ? RTFM. make buildworld make buildkernel make installkernel reboot make installworld mergemaster reboot DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
In message: [EMAIL PROTECTED] Uwe Laverenz [EMAIL PROTECTED] writes: : [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
