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: 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: 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: 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: 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]
