4.7 Upgrade issue
Hello to all FreeBSD users, supporters, developers. I'm trying to upgrade from FreeBSD 4.6-STABLE #0: Sat Jun 29 to RELENG_4_7 sysctl -a | grep secure - kern.securelevel: -1 1) rm -rf /usr/src/* (backed up kernel cfg before) 2) rm -rf /usr/obj/* 3) cvsup-ed RELENG_4_7 4) make buildworld- successfull 5) make buildkernel KERNCONF=MYKERNEL - successfull 6) make installworld - following error: mkdir -p /tmp/install.55427 for prog in [ awk cat chflags chmod chown date echo egrep find grep ln make makewhatis mtree mv perl pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.55427; done usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory *** Error code 64 Stop in /usr/src. *** Error code 1 Stop in /usr/src. What is wrong? -- Get your FREE email, calendar, file storage, bookmarks, and other great services at http://www.doneasy.com ! doneasy.com Where timesaving is priceless! -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue
On Wed, Feb 26, 2003 at 01:34:31PM +, rew wrote: Hello to all FreeBSD users, supporters, developers. I'm trying to upgrade from FreeBSD 4.6-STABLE #0: Sat Jun 29 to RELENG_4_7 sysctl -a | grep secure - kern.securelevel: -1 1) rm -rf /usr/src/* (backed up kernel cfg before) 2) rm -rf /usr/obj/* 3) cvsup-ed RELENG_4_7 4) make buildworld- successfull 5) make buildkernel KERNCONF=MYKERNEL - successfull 6) make installworld - following error: mkdir -p /tmp/install.55427 for prog in [ awk cat chflags chmod chown date echo egrep find grep ln make makewhatis mtree mv perl pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.55427; done usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory *** Error code 64 Stop in /usr/src. *** Error code 1 Stop in /usr/src. What is wrong? You must installkernel and reboot before you can installworld. Read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html for more details. -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: 4.7 Upgrade issue
I did make installkernel, which was successful but make installworld failed again now, I ended up with a new kernel/old system. -Original Message- From: Daniel Bye Sent: Wednesday, February 26, 2003 9:01 AM To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: 4.7 Upgrade issue On Wed, Feb 26, 2003 at 01:34:31PM +, rew wrote: Hello to all FreeBSD users, supporters, developers. I'm trying to upgrade from FreeBSD 4.6-STABLE #0: Sat Jun 29 to RELENG_4_7 sysctl -a | grep secure - kern.securelevel: -1 1) rm -rf /usr/src/* (backed up kernel cfg before) 2) rm -rf /usr/obj/* 3) cvsup-ed RELENG_4_7 4) make buildworld- successfull 5) make buildkernel KERNCONF=MYKERNEL - successfull 6) make installworld - following error: mkdir -p /tmp/install.55427 for prog in [ awk cat chflags chmod chown date echo egrep find grep ln make makewhatis mtree mv perl pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.55427; done usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory *** Error code 64 Stop in /usr/src. *** Error code 1 Stop in /usr/src. What is wrong? You must installkernel and reboot before you can installworld. Read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html for more details. -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Get your FREE email, calendar, file storage, bookmarks, and other great services at http://www.doneasy.com ! doneasy.com Where timesaving is priceless! -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: 4.7 Upgrade issue
Quoting rew [EMAIL PROTECTED]: You must installkernel and reboot before you can installworld. Read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html for more details. Daniel Bye Hi Daniel ! I made/installed kernel and world quite a few times now and never, never, never reboot before installing world ! - make world - install world - make kernel - install kernel -- Pierrick Brossin IT Swiss - QUARK Media House 6a Puits Godet, 2000 Neuchatel, Switzerland Mail Prof: [EMAIL PROTECTED] Mail Priv: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue
On Wed, Feb 26, 2003 at 03:23:28PM +0100, Pierrick Brossin wrote: Quoting rew [EMAIL PROTECTED]: You must installkernel and reboot before you can installworld. Read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html for more details. Daniel Bye Hi Daniel ! I made/installed kernel and world quite a few times now and never, never, never reboot before installing world ! - make world - install world - make kernel - install kernel This looks like the old way of doing things. The new way (buildworld, buildkernel etc) is different, and you must boot the new kernel to safely and reliably install the new world. The instructions in the handbook are very explicit in this regard. It is the only supported method of updating your system from source, as it is the only method that is tested. While some variations work, they may create unforeseen problems. -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: 4.7 Upgrade issue
So you boot a new kernel with old system? -Original Message- From: Daniel Bye Sent: Wednesday, February 26, 2003 9:40 AM To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: 4.7 Upgrade issue On Wed, Feb 26, 2003 at 03:23:28PM +0100, Pierrick Brossin wrote: Quoting rew : You must installkernel and reboot before you can installworld. Read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html for more details. Daniel Bye Hi Daniel ! I made/installed kernel and world quite a few times now and never, never, never reboot before installing world ! - make world - install world - make kernel - install kernel This looks like the old way of doing things. The new way (buildworld, buildkernel etc) is different, and you must boot the new kernel to safely and reliably install the new world. The instructions in the handbook are very explicit in this regard. It is the only supported method of updating your system from source, as it is the only method that is tested. While some variations work, they may create unforeseen problems. -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Get your FREE email, calendar, file storage, bookmarks, and other great services at http://www.doneasy.com ! doneasy.com Where timesaving is priceless! -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue
rew wrote: I did make installkernel, which was successful but make installworld failed again now, I ended up with a new kernel/old system. Interrupt the boot process when it counts down and enter 'boot kernel.old' This will boot your previous kernel. Is it failing in the same place every time? If not, it's most likely a hardware problem. If so, you may want to cvsup again. It doesn't happen too often, but it is possible to cvsup exactly in the middle of a series of commits, leaving you with a combination of files that won't build. -Original Message- From: Daniel Bye Sent: Wednesday, February 26, 2003 9:01 AM To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: 4.7 Upgrade issue On Wed, Feb 26, 2003 at 01:34:31PM +, rew wrote: Hello to all FreeBSD users, supporters, developers. I'm trying to upgrade from FreeBSD 4.6-STABLE #0: Sat Jun 29 to RELENG_4_7 sysctl -a | grep secure - kern.securelevel: -1 1) rm -rf /usr/src/* (backed up kernel cfg before) 2) rm -rf /usr/obj/* 3) cvsup-ed RELENG_4_7 4) make buildworld- successfull 5) make buildkernel KERNCONF=MYKERNEL - successfull 6) make installworld - following error: mkdir -p /tmp/install.55427 for prog in [ awk cat chflags chmod chown date echo egrep find grep ln make makewhatis mtree mv perl pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.55427; done usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory *** Error code 64 Stop in /usr/src. *** Error code 1 Stop in /usr/src. What is wrong? You must installkernel and reboot before you can installworld. Read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html for more details. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue
On Wed, Feb 26, 2003 at 02:29:57PM +, rew wrote: So you boot a new kernel with old system? Yes, but how is that so different from installing a new world for an old kernel? When you have built a new kernel, you must reboot to start using it. After running make installworld with the new kernel, you have the new world installed as well. Your new kernel will only be running for a few minutes with the old world, until the new one is fully installed. -Original Message- From: Daniel Bye Sent: Wednesday, February 26, 2003 9:40 AM To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: 4.7 Upgrade issue On Wed, Feb 26, 2003 at 03:23:28PM +0100, Pierrick Brossin wrote: Quoting rew : You must installkernel and reboot before you can installworld. Read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html for more details. Daniel Bye Hi Daniel ! I made/installed kernel and world quite a few times now and never, never, never reboot before installing world ! - make world - install world - make kernel - install kernel This looks like the old way of doing things. The new way (buildworld, buildkernel etc) is different, and you must boot the new kernel to safely and reliably install the new world. The instructions in the handbook are very explicit in this regard. It is the only supported method of updating your system from source, as it is the only method that is tested. While some variations work, they may create unforeseen problems. -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue
On Wed, Feb 26, 2003 at 04:59:53PM +0200, Willie Viljoen wrote: On Wednesday 26 February 2003 16:50, someone, possibly Daniel Bye, typed: Yes, but how is that so different from installing a new world for an old kernel? The problem with a new world on an old kernel is that libraries in your world may have changed with the upgrade. If a library that interfaces directly with some feature in the kernel is changed, and is expecting the change to be present in the kernel, you will almost certainly have trouble with it. Agreed, but in this context, I think we are talking about running the disparate kernel and world, in either event, only as long as it takes to get both parts, the new kernel and the new world, installed. Surely, an old world on a new kernel will have the exact same problems (or the exact opposite problems?), in that newly-built programs such as ps and top may have been altered to take account of new kernel memory structures etc, which won't be available until the new kernel is installed and booted. Anyone who is up to using buildworld should have enough understanding to know that you have to build and install both parts for your system to work properly. When you have built a new kernel, you must reboot to start using it. After running make installworld with the new kernel, you have the new world installed as well. Your new kernel will only be running for a few minutes with the old world, until the new one is fully installed. That is exactly how it should be. The tried and trusted method, that works for me, and is the official method listed in the UPDATING file: cd /usr/src/sys/i386/conf vi YOURCONFIG cd /usr/src/ make buildworld kernel KERNCONF=YOURCONFIG The kernel target is a combination of buildkernel and installkernel. These targets are built in order and rely on the previous target making it. Thus, buildworld must succeed for buildkernel to begin, and after buildkernel has worked, installkernel will run. Once this is completed, continue with: shutdown now You will now have dropped to single user mode, then, pick /bin/sh for your shell (this is easier to use in single user than csh), and run: cd /usr/src mergemaster -p make installworld mergemaster reboot You will now have a properly functioning and fully upgraded system. But even then, there will be some disparity between the running kernel and the running world, no? This will only be resolved once all steps are complete, whichever particular sequence of events you follow. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: 4.7 Upgrade issue - Daniel Bye
I upgraded my system several times before, are you saying that one is unable to run successfuly 'make installworld' until the new kernel is booted? has anyone even try to look at the error? -Original Message- From: Daniel Bye Sent: Wednesday, February 26, 2003 10:16 AM To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: 4.7 Upgrade issue On Wed, Feb 26, 2003 at 04:59:53PM +0200, Willie Viljoen wrote: On Wednesday 26 February 2003 16:50, someone, possibly Daniel Bye, typed: Yes, but how is that so different from installing a new world for an old kernel? The problem with a new world on an old kernel is that libraries in your world may have changed with the upgrade. If a library that interfaces directly with some feature in the kernel is changed, and is expecting the change to be present in the kernel, you will almost certainly have trouble with it. Agreed, but in this context, I think we are talking about running the disparate kernel and world, in either event, only as long as it takes to get both parts, the new kernel and the new world, installed. Surely, an old world on a new kernel will have the exact same problems (or the exact opposite problems?), in that newly-built programs such as ps and top may have been altered to take account of new kernel memory structures etc, which won't be available until the new kernel is installed and booted. Anyone who is up to using buildworld should have enough understanding to know that you have to build and install both parts for your system to work properly. When you have built a new kernel, you must reboot to start using it. After running make installworld with the new kernel, you have the new world installed as well. Your new kernel will only be running for a few minutes with the old world, until the new one is fully installed. That is exactly how it should be. The tried and trusted method, that works for me, and is the official method listed in the UPDATING file: cd /usr/src/sys/i386/conf vi YOURCONFIG cd /usr/src/ make buildworld kernel KERNCONF=YOURCONFIG The kernel target is a combination of buildkernel and installkernel. These targets are built in order and rely on the previous target making it. Thus, buildworld must succeed for buildkernel to begin, and after buildkernel has worked, installkernel will run. Once this is completed, continue with: shutdown now You will now have dropped to single user mode, then, pick /bin/sh for your shell (this is easier to use in single user than csh), and run: cd /usr/src mergemaster -p make installworld mergemaster reboot You will now have a properly functioning and fully upgraded system. But even then, there will be some disparity between the running kernel and the running world, no? This will only be resolved once all steps are complete, whichever particular sequence of events you follow. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Get your FREE email, calendar, file storage, bookmarks, and other great services at http://www.doneasy.com ! doneasy.com Where timesaving is priceless! -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: 4.7 Upgrade issue - Kent Stewart
Hi, This is a remote box, with noone around. Dan -Original Message- From: Kent Stewart Sent: Wednesday, February 26, 2003 10:42 AM To: [EMAIL PROTECTED] Subject: Re: 4.7 Upgrade issue - Daniel Bye On Wednesday 26 February 2003 12:13 pm, rew wrote: I upgraded my system several times before, are you saying that one is unable to run successfuly 'make installworld' until the new kernel is booted? has anyone even try to look at the error? I have gone off list because it is rehasing old subjects. That isn't what he was saying. You boot to single user mode on the new kernel to test it. If something bad happens, re-booting using kernel.old is really easy. Reinstalling an old version is frequently called doing a clean install. Single user mode doesn't start any processes. There isn't a problem with the mixed up user world until you start running in multi-user mode. A shutdown now is not the same as booting in single user mode. I did all 4 in multi-user mode for a long time. It always worked but then, one day, there was a problem with the kernel and I realized that my method was dangerous to my systems operational health. In my mind, doing a make world is even more dangerous to your system operation health. Have a good day, Kent -Original Message- From: Daniel Bye Sent: Wednesday, February 26, 2003 10:16 AM To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: 4.7 Upgrade issue On Wed, Feb 26, 2003 at 04:59:53PM +0200, Willie Viljoen wrote: On Wednesday 26 February 2003 16:50, someone, possibly Daniel Bye, typed: Yes, but how is that so different from installing a new world for an old kernel? The problem with a new world on an old kernel is that libraries in your world may have changed with the upgrade. If a library that interfaces directly with some feature in the kernel is changed, and is expecting the change to be present in the kernel, you will almost certainly have trouble with it. Agreed, but in this context, I think we are talking about running the disparate kernel and world, in either event, only as long as it takes to get both parts, the new kernel and the new world, installed. Surely, an old world on a new kernel will have the exact same problems (or the exact opposite problems?), in that newly-built programs such as ps and top may have been altered to take account of new kernel memory structures etc, which won't be available until the new kernel is installed and booted. Anyone who is up to using buildworld should have enough understanding to know that you have to build and install both parts for your system to work properly. When you have built a new kernel, you must reboot to start using it. After running make installworld with the new kernel, you have the new world installed as well. Your new kernel will only be running for a few minutes with the old world, until the new one is fully installed. That is exactly how it should be. The tried and trusted method, that works for me, and is the official method listed in the UPDATING file: cd /usr/src/sys/i386/conf vi YOURCONFIG cd /usr/src/ make buildworld kernel KERNCONF=YOURCONFIG The kernel target is a combination of buildkernel and installkernel. These targets are built in order and rely on the previous target making it. Thus, buildworld must succeed for buildkernel to begin, and after buildkernel has worked, installkernel will run. Once this is completed, continue with: shutdown now You will now have dropped to single user mode, then, pick /bin/sh for your shell (this is easier to use in single user than csh), and run: cd /usr/src mergemaster -p make installworld mergemaster reboot You will now have a properly functioning and fully upgraded system. But even then, there will be some disparity between the running kernel and the running world, no? This will only be resolved once all steps are complete, whichever particular sequence of events you follow. Dan -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html -- Get your FREE email, calendar, file storage, bookmarks, and other great services at http://www.doneasy.com ! doneasy.com Where timesaving is priceless! -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue - Daniel Bye
On Wed, Feb 26, 2003 at 03:13:30PM +, rew wrote: I upgraded my system several times before, are you saying that one is unable to run successfuly 'make installworld' until the new kernel is booted? I am saying that according to the authors of the handbook, there is a particular order to follow when upgrading your system. Any deviation away from this procedure is likely to lead to problems. has anyone even try to look at the error? Yes, and the suggestions have been to follow the procedure in the handbook or the UPDATING file, as the buildworld process is carefully crafted to be done in that order. -Original Message- From: Daniel Bye Sent: Wednesday, February 26, 2003 10:16 AM To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: 4.7 Upgrade issue On Wed, Feb 26, 2003 at 04:59:53PM +0200, Willie Viljoen wrote: On Wednesday 26 February 2003 16:50, someone, possibly Daniel Bye, typed: Yes, but how is that so different from installing a new world for an old kernel? The problem with a new world on an old kernel is that libraries in your world may have changed with the upgrade. If a library that interfaces directly with some feature in the kernel is changed, and is expecting the change to be present in the kernel, you will almost certainly have trouble with it. Agreed, but in this context, I think we are talking about running the disparate kernel and world, in either event, only as long as it takes to get both parts, the new kernel and the new world, installed. Surely, an old world on a new kernel will have the exact same problems (or the exact opposite problems?), in that newly-built programs such as ps and top may have been altered to take account of new kernel memory structures etc, which won't be available until the new kernel is installed and booted. Anyone who is up to using buildworld should have enough understanding to know that you have to build and install both parts for your system to work properly. When you have built a new kernel, you must reboot to start using it. After running make installworld with the new kernel, you have the new world installed as well. Your new kernel will only be running for a few minutes with the old world, until the new one is fully installed. That is exactly how it should be. The tried and trusted method, that works for me, and is the official method listed in the UPDATING file: cd /usr/src/sys/i386/conf vi YOURCONFIG cd /usr/src/ make buildworld kernel KERNCONF=YOURCONFIG The kernel target is a combination of buildkernel and installkernel. These targets are built in order and rely on the previous target making it. Thus, buildworld must succeed for buildkernel to begin, and after buildkernel has worked, installkernel will run. Once this is completed, continue with: shutdown now You will now have dropped to single user mode, then, pick /bin/sh for your shell (this is easier to use in single user than csh), and run: cd /usr/src mergemaster -p make installworld mergemaster reboot You will now have a properly functioning and fully upgraded system. But even then, there will be some disparity between the running kernel and the running world, no? This will only be resolved once all steps are complete, whichever particular sequence of events you follow. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Get your FREE email, calendar, file storage, bookmarks, and other great services at http://www.doneasy.com ! doneasy.com Where timesaving is priceless! -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue
On Wednesday 26 February 2003 09:50 am, Daniel Bye wrote: On Wed, Feb 26, 2003 at 02:29:57PM +, rew wrote: So you boot a new kernel with old system? Yes, but how is that so different from installing a new world for an old kernel? And it's really usually not that big of a deal anyway. I successfully ran a 4.3 kernel on a 4.7 system. I could only make a few problems occur even when trying. top and ps worked just fine. Besides, when you installworld, you should be booting straight to single user mode, so not much is going on to cause problems in installworld. Of course don't try to do anything else when world and kernel are out of sync. Problems come in especially when trying to run a 3.x kernel on a 4.x system and some other cases. Tim When you have built a new kernel, you must reboot to start using it. After running make installworld with the new kernel, you have the new world installed as well. Your new kernel will only be running for a few minutes with the old world, until the new one is fully installed. -Original Message- From: Daniel Bye Sent: Wednesday, February 26, 2003 9:40 AM To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: 4.7 Upgrade issue On Wed, Feb 26, 2003 at 03:23:28PM +0100, Pierrick Brossin wrote: Quoting rew : You must installkernel and reboot before you can installworld. Read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.h tml for more details. Daniel Bye Hi Daniel ! I made/installed kernel and world quite a few times now and never, never, never reboot before installing world ! - make world - install world - make kernel - install kernel This looks like the old way of doing things. The new way (buildworld, buildkernel etc) is different, and you must boot the new kernel to safely and reliably install the new world. The instructions in the handbook are very explicit in this regard. It is the only supported method of updating your system from source, as it is the only method that is tested. While some variations work, they may create unforeseen problems. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue
On Wednesday 26 February 2003 09:23 am, Pierrick Brossin wrote: Quoting rew [EMAIL PROTECTED]: You must installkernel and reboot before you can installworld. Read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html for more details. Daniel Bye Hi Daniel ! I made/installed kernel and world quite a few times now and never, never, never reboot before installing world ! - make world - install world - make kernel - install kernel Agreed with Daniel. Pierrick, this is an incorrect method. the world target has been deprecated. Really, read the handbook and UPDATING for more info. To the OP, now that you borked your install by trying to installworld before you did installkernel, you may be in an indeterminate state that you can't get out of without a lot of work by hand sorting out the files. You may need to backup and start over (fresh install) Though possibly you can get it working with Bill's method of booting the old kernel and trying again. But if you've done buildworld buildkernel installworld installkernel installworld you may be up a creek without a paddle. (like I said not that you couldn't swim, but in this case it could be like swimming with a weight belt on) Always read UPDATING and the handook. Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue - Daniel Bye
At 03:46 PM 2.26.2003 +, Daniel Bye wrote: On Wed, Feb 26, 2003 at 03:13:30PM +, rew wrote: I upgraded my system several times before, are you saying that one is unable to run successfuly 'make installworld' until the new kernel is booted? I am saying that according to the authors of the handbook, there is a particular order to follow when upgrading your system. Any deviation away from this procedure is likely to lead to problems. Lot snipped out You do NOT have to boot the new kernel before running make installworld HOWEVER, it is recommended that you do boot the new kernel before proceding just to test it. If there is a problem with the new kernel, you can still revert back to the old and start over. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue
Daniel Bye [EMAIL PROTECTED] writes: Agreed, but in this context, I think we are talking about running the disparate kernel and world, in either event, only as long as it takes to get both parts, the new kernel and the new world, installed. Surely, an old world on a new kernel will have the exact same problems (or the exact opposite problems?), in that newly-built programs such as ps and top may have been altered to take account of new kernel memory structures etc, which won't be available until the new kernel is installed and booted. Anyone who is up to using buildworld should have enough understanding to know that you have to build and install both parts for your system to work properly. Yes, *assuming* everything goes fine, either method works equally well. The difference is what you can do if something goes wrong. If you are running a new kernel on an old world, you can reboot with your old kernel, but if you're running an old kernel on a new world when things blow up, you're hosed, and have to start installing from clean media. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue
Quoting rew [EMAIL PROTECTED]: I'm trying to upgrade from FreeBSD 4.6-STABLE #0: Sat Jun 29 to RELENG_4_7 mkdir -p /tmp/install.55427 for prog in [ awk cat chflags chmod chown date echo egrep find grep ln make makewhatis mtree mv perl pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.55427; done usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory *** Error code 64 Stop in /usr/src. *** Error code 1 Stop in /usr/src. If the install is still failing for you... It looks as if the 'which' command is failing to find the executables listed. Could root's path be improperly set? Since you mentioned that this host was remote. Did you 'su' to root or 'su -'? Just a thought. BTW, to find out which binary is missing, or can't be foundin the path, run this script. It will tell you what executable(s) is(are) the problem. #!/bin/sh for prog in [ awk cat chflags chmod chown date \ echo egrep find grep ln make makewhatis mtree \ mv perl pwd_mkdb rm sed sh sysctl test true \ uname wc zic; do echo WHICH $prog: ::`which $prog`::; done just look for the one with the empty value '' --daxbert To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue - Daniel Bye
On Wed, Feb 26, 2003 at 03:46:35PM +, Daniel Bye wrote: Yes, and the suggestions have been to follow the procedure in the handbook or the UPDATING file, as the buildworld process is carefully crafted to be done in that order. I'm trying to minimize the amount that has to be done in single-user mode (I don't have console access; I have to trust my hosting company's tech support for that part). Is there any serious reason that mergemaster needs to be run in single-user mode? Ideally, I'm trying to get something that needs no operator intervention during single-user mode. Currently, if mergemaster can be run just before booting into single-user mode, the operator needs to type one command (upgrade, a shell script in /root/bin which runs the fsck, mount, swapon, cd, make installworld, and fastboot commands). Thanks, Jim Trigg -- Jim Trigg, Lord High Everything Else O- /\ \ / ASCII RIBBON CAMPAIGN Hostmaster, Huie Kin family websiteXHELP CURE HTML MAIL Verger, All Saints Church - Sharon Chapel / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue - Daniel Bye
In [EMAIL PROTECTED], Jim Trigg [EMAIL PROTECTED] typed: On Wed, Feb 26, 2003 at 03:46:35PM +, Daniel Bye wrote: Yes, and the suggestions have been to follow the procedure in the handbook or the UPDATING file, as the buildworld process is carefully crafted to be done in that order. I'm trying to minimize the amount that has to be done in single-user mode (I don't have console access; I have to trust my hosting company's tech support for that part). Is there any serious reason that mergemaster needs to be run in single-user mode? No, there isn't. Ideally, I'm trying to get something that needs no operator intervention during single-user mode. Currently, if mergemaster can be run just before booting into single-user mode, the operator needs to type one command (upgrade, a shell script in /root/bin which runs the fsck, mount, swapon, cd, make installworld, and fastboot commands). If you really want, you can reboot multiuser on the new kernel, and run make installworld there. It's not tested, but I've done it successfully. I regularly boot multi-user, then drop back to single user to do installs from NFS-mounted /usr/src and /usr/obj. In fact, that's recommended at one place in the handbook. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 Upgrade issue - Daniel Bye
In [EMAIL PROTECTED], Bill Moran [EMAIL PROTECTED] typed: And _always_ back up /etc before running mergemaster. It only has to save you from a stupid mistake 1 time to be worth it! (I know) This has worked so well for me, I'm going to suggest it to everyone here. Don't back up /etc. Store the files you modify in a source code control system. Use rcs, as that's part of the base system. Use cvs if you prefer it. Personally, I use perforce. That means you have backups of all the files you've changed. It also means you can get change histories for the files. It beats the dickens out of umpteen files called foo-back, foo-old, and etc. It works better than dated backups as well. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
