Re: Install world fails, computer almost unusable
>From: "Joshua Lokken" <[EMAIL PROTECTED]> > * Artem Koutchine <[EMAIL PROTECTED]> [2004-04-08 06:44]: > > IMHO the upgrade pricedure is unstable and wrong in either case. > > > > What do you think? > > I don't pretend to understand *all* of the reasoning behind the > recommended upgrade procedure. Since I began using FreeBSD, I have > performed somewhere around 50 system upgrades on various machines, most > of them 4.x, and have upgraded 5.1->5.2 on four machines. Of those > system upgrades, two have failed, or 'not worked.' One of them was due > to the fact that I didn't follow the recommended procedure (admittedly, > supplemented with list wisdom), the other, because I didn't follow the > recommended procedure. > > It just works. > Actually it failed only once for me since 1996. But! I alway fill shaky when upgrading a remote server and rebootting it. Never failed once but i CAN SEE a case when it will fail because some utility does not match kernel at the time of installation. The ideal upgrade procedure must allow fall back to the previous version. So, the ideal upgrade must install everything into a temporary storage space and after reboot, try to replace existing files with the new onces and if after that boot failes after the next reboot restore the originals while keeping log. I don't think it is as hard to implement as 5.2 locking :) Artem ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install world fails, computer almost unusable
Kent Stewart wrote: On Thursday 08 April 2004 07:09 am, Remko Lodder wrote: install kernel, reboot, make buildworld, reboot in singleusermode make installworld, mergemaster -p , reboot, mergemaster. does the same imho. I may be confused here but if you do a buildworld after you do an install kernel, you used the old system to built the kernel. You want the new buildworld available when you do the buildkernel. ehm minor thinking problem in my "short summary of what freebsd advices" The Makeworld has to come first then the makebuildkernel and then reboot. Sorry for the inconvience:-) Thanks Kent for pointing it out :-) -- Kind regards, Remko Lodder Elvandar.org/DSINet.org www.mostly-harmless.nl A Dutch community for helping newcomers on the hackerscene ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install world fails, computer almost unusable
* Artem Koutchine <[EMAIL PROTECTED]> [2004-04-08 06:44]: > IMHO the upgrade pricedure is unstable and wrong in either case. > > What do you think? I don't pretend to understand *all* of the reasoning behind the recommended upgrade procedure. Since I began using FreeBSD, I have performed somewhere around 50 system upgrades on various machines, most of them 4.x, and have upgraded 5.1->5.2 on four machines. Of those system upgrades, two have failed, or 'not worked.' One of them was due to the fact that I didn't follow the recommended procedure (admittedly, supplemented with list wisdom), the other, because I didn't follow the recommended procedure. It just works. -- Joshua Worlds are conquered, galaxies destroyed -- but a woman is always a woman. -- Kirk, "Conscience of the King", stardate unknown ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install world fails, computer almost unusable
On Thursday 08 April 2004 07:09 am, Remko Lodder wrote: > Artem Koutchine wrote: > > IMHO the upgrade pricedure is unstable and wrong in either case. > > Then why is it a proven working procedure? (I upgraded my boxes from > 5.0-RC1 to 5.2.1-p4 (all the way) And it never failed on me!) I agree because I am one of the people that made the statfs transition on current just fine. I started following the boot -s procedure to do the installworld when you couldn't do an installworld on a 4.0 kernel. > > Previously on 4.x it also worked out fine (another method i used over > there, but that also worked out) > > > If you build, install a new kernel and reboot and they make > > installworld you may face code dumps because all world is not > > compatible with the new kernel. > > Not at my machine. I have had a few panics but they were due to bad changes being made to the kernel. Even then, backing up to kernel.old worked and continued to work until the problem was fixed. > > > IMHO this thing must be resolved in the future and it would be > > nice > > > > to do it this way: > > 1) build kernel and install it into a buffer > > /boot will be fine for me (like it does now) > > > 2) build workld and install it into a buffer > > That requires that you have a lot of diskspace, so some users can > have issues with this, and then again in my opinion there is no > problem, and if there is a problem this won't solve it. > > > 3) make changes to config files and install new config file into a > > buffer > > install kernel, reboot, make buildworld, reboot in singleusermode > make installworld, mergemaster -p , reboot, mergemaster. > does the same imho. I may be confused here but if you do a buildworld after you do an install kernel, you used the old system to built the kernel. You want the new buildworld available when you do the buildkernel. > > > 4) reboot > > we already done that > > > 5) during reboot load shoud check the install buffer and if there > > is something in it then copy it into a real working filesystem. > > > > This way we will abvoid nonmtaching executables and kernel at any > > given time. > > > > What do you think? > > My opinion is clear, i'll stick with the current way freebsd handles > new installations, they work for me, and they never failed on me. Me too!! It has worked for me over several serious changes that would break your system and they never failed. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install world fails, computer almost unusable
On Thu, Apr 08, 2004 at 05:38:27PM +0400, Artem Koutchine wrote: > IMHO the upgrade pricedure is unstable and wrong in either case. > > If you build, install a new kernel and reboot and they make installworld > you may face code dumps because all world is not compatible with the > new kernel. > > if yo build, install a new kernel and install world w/o reboot then > during installworld one program is substituted with a new one which > uses new kernel and make installworld may fail. > > IMHO this thing must be resolved in the future and it would be nice > to do it this way: > 1) build kernel and install it into a buffer > 2) build workld and install it into a buffer > 3) make changes to config files and install new config file into a buffer > 4) reboot > 5) during reboot load shoud check the install buffer and if there is > something in it then copy it into a real working filesystem. > > This way we will abvoid nonmtaching executables and kernel at any > given time. > > What do you think? I think your way just introduces spectacular new ways to screw up your system, but feel free to code up a prototype implementation and show how it works for some of the difficult upgrade cases like 5.1->5.2, 4.x->5.2, etc. Kris pgp0.pgp Description: PGP signature
Re: Install world fails, computer almost unusable
Artem Koutchine wrote: IMHO the upgrade pricedure is unstable and wrong in either case. Then why is it a proven working procedure? (I upgraded my boxes from 5.0-RC1 to 5.2.1-p4 (all the way) And it never failed on me!) Previously on 4.x it also worked out fine (another method i used over there, but that also worked out) If you build, install a new kernel and reboot and they make installworld you may face code dumps because all world is not compatible with the new kernel. Not at my machine. > IMHO this thing must be resolved in the future and it would be nice to do it this way: 1) build kernel and install it into a buffer /boot will be fine for me (like it does now) 2) build workld and install it into a buffer That requires that you have a lot of diskspace, so some users can have issues with this, and then again in my opinion there is no problem, and if there is a problem this won't solve it. 3) make changes to config files and install new config file into a buffer install kernel, reboot, make buildworld, reboot in singleusermode make installworld, mergemaster -p , reboot, mergemaster. does the same imho. 4) reboot we already done that 5) during reboot load shoud check the install buffer and if there is something in it then copy it into a real working filesystem. This way we will abvoid nonmtaching executables and kernel at any given time. What do you think? My opinion is clear, i'll stick with the current way freebsd handles new installations, they work for me, and they never failed on me. -- Kind regards, Remko Lodder Elvandar.org/DSINet.org www.mostly-harmless.nl A Dutch community for helping newcomers on the hackerscene ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install world fails, computer almost unusable
IMHO the upgrade pricedure is unstable and wrong in either case. If you build, install a new kernel and reboot and they make installworld you may face code dumps because all world is not compatible with the new kernel. if yo build, install a new kernel and install world w/o reboot then during installworld one program is substituted with a new one which uses new kernel and make installworld may fail. IMHO this thing must be resolved in the future and it would be nice to do it this way: 1) build kernel and install it into a buffer 2) build workld and install it into a buffer 3) make changes to config files and install new config file into a buffer 4) reboot 5) during reboot load shoud check the install buffer and if there is something in it then copy it into a real working filesystem. This way we will abvoid nonmtaching executables and kernel at any given time. What do you think? - Original Message - From: "Kris Kennaway" <[EMAIL PROTECTED]> To: "Andy Rozman (Aleksander)" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, April 07, 2004 9:11 PM Subject: Re: Install world fails, computer almost unusable ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install world fails, computer almost unusable
On Wed, Apr 07, 2004 at 01:45:38PM +0200, Andy Rozman (Aleksander) wrote: > > Hi ! > > I succesfully compiled FreeBSD 5.2.1, but problem happened when I wanted to do > install. After I run installworld install started but halted at one point > (with copying ld-so.1 in libexec). I found > ld-so.1.old file which I removed, and after I run installworld again, mtree > failed with core dump, and "Bad Syscall"... > > Now I can't do anything. Most of system programs now do core dump. > > Is there a way to solve this? Probably only with a binary install (i.e. from sysinstall and boot media) at this point. FWIW, it sounds like you did the upgrade incorrectly, e.g. by trying to installworld before you had built and booted a new kernel. Follow the steps documented in the handbook and in /usr/src/UPDATING next time and you should be fine. Kris pgp0.pgp Description: PGP signature
Re: Install world fails, computer almost unusable
On Wednesday 07 April 2004 04:45 am, Andy Rozman (Aleksander) wrote: > Hi ! > > I succesfully compiled FreeBSD 5.2.1, but problem happened when I > wanted to do install. After I run installworld install started but > halted at one point (with copying ld-so.1 in libexec). I found > ld-so.1.old file which I removed, and after I run installworld again, > mtree failed with core dump, and "Bad Syscall"... > > Now I can't do anything. Most of system programs now do core dump. > > Is there a way to solve this? > What were you upgrading to 5.2.1 from. If it was 5.1 or older, then there were serious problems if you tried to do an installworld from the older kernel. The upgrade to 5.2+ worked if you booted to single user mode on the new 5.2+ kernel and then did the installworld. You can find some of the solutions in the archive of -current. IIRC, people were able to use the fixit cd, boot from it, and finish the system installation. The other choice I remember is to do a clean 5.2.1 install. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Install world fails, computer almost unusable
Hi ! I succesfully compiled FreeBSD 5.2.1, but problem happened when I wanted to do install. After I run installworld install started but halted at one point (with copying ld-so.1 in libexec). I found ld-so.1.old file which I removed, and after I run installworld again, mtree failed with core dump, and "Bad Syscall"... Now I can't do anything. Most of system programs now do core dump. Is there a way to solve this? Andy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
