Re: downgrade
Wed, May 23, 2001 at 15:43:50, nk (Norbert Koch) wrote about downgrade: Is it possible to downgrade a machine from -current to -stable? A ~month ago I downgraded my home system from -current to -stable (RELENG_4) via buildworld+installworld. But to do it successfully I had to replace /usr/include with the same from working 4.2-STABLE system, because of too many fallings of buildworld with -current headers. Current (not -current;)) but contemporary) world building procedure does not exclude headers from /usr/include out of compiler view. /netch To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: downgrade
On Fri, 25 May 2001, Valentin Nechayev wrote: Current (not -current;)) but contemporary) world building procedure does not exclude headers from /usr/include out of compiler view. This was broken in src/Makefile.inc1 rev.1.105. /usr/include was still still needed in rev.1.104 for building cross-tools, so unportabilities in the cross-tools might have caused problems. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: downgrade
On Fri, 25 May 2001 09:47:13 +0300, Valentin Nechayev wrote: Wed, May 23, 2001 at 15:43:50, nk (Norbert Koch) wrote about downgrade: Is it possible to downgrade a machine from -current to -stable? A ~month ago I downgraded my home system from -current to -stable (RELENG_4) via buildworld+installworld. But to do it successfully I had to replace /usr/include with the same from working 4.2-STABLE system, because of too many fallings of buildworld with -current headers. Current (not -current;)) but contemporary) world building procedure does not exclude headers from /usr/include out of compiler view. The following procedure should work if you don't have access to a 4-STABLE system to copy includes from (assuming that you have 4-STABLE sources in /usr/src): $ cp -r /usr/include /usr/include.5 # could be useful if you will change your mind $ cd /usr/src $ make includes $ make buildworld $ make installworld $ rm -rf /usr/include.5 -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: downgrade
Norbert Koch writes: Hi! Is it possible to downgrade a machine from -current to -stable? Yes, it's possible, but if you've got much on your system I don't think it's worth it. I (almost) did it a couple of months ago. It's not for the faint of heart. One thing that you've got to keep in mind is the bump in shared library versions; you'll probably have to reinstall anything you built yourself or via the ports system, and make sure you've removed the -current libraries (with the higher version numbers) first. After I'd spent most of a day deinstalling and reinstalling various ports, I decided it would be a lot safer and easier to just do a binary-only install from the CD, check out the latest -stable sources, and upgrade that way. If you were tracking -current before, you've got a local copy of the repository, right :-)? That's a good argument for multiple partitions, by the way. Since I have a partition for projects, one for src (both FreeBSD and /usr/ports/distfiles), and one for my mp3s I just told sysinstall to newfs /, /usr and /var but leave /home and all the rest alone. -- Richard Kuhns [EMAIL PROTECTED] PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Roadx319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: downgrade?
* Philipp Huber [EMAIL PROTECTED] [001007 04:08] wrote: hi! is it possible to downgrade a freebsd-current installation to -stable? or is it better to reinstall the whole system? It's possible by building a 4.x-stable system and tar'ing the /usr/src and /usr/obj over to your -current then doing several 'make -k installworld' followed by a 'make installworld' to make sure it's all been installed then by building a kernel using the "make buildkernel" method described in src/UPDATING. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: downgrade to stable?
In message [EMAIL PROTECTED] Philipp Huber writes: : is it possible to downgrade a freebsd-current installation to -stable? : or is it better to reinstall the whole system? Yes. However, it is tricky and not for the feign of heart. It involves doing an install world onto the system, rebooting the stable kernel and then looking for libraries that are too new. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: downgrade to stable?
On Sat, Oct 07, 2000 at 12:04:15PM -0600, Warner Losh wrote: and then looking for libraries that are too new. Would one not want to keep the libraries that are too new for things in /usr/local that would need them. Since the shlib symlink will be for the "older" lib, there really isn't any problem having too new ones present. -- -- David ([EMAIL PROTECTED]) Gnu is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: downgrade?
* Salvo Bartolotta [EMAIL PROTECTED] [001007 12:14] wrote: Original Message On 10/7/00, 12:13:28 PM, Alfred Perlstein [EMAIL PROTECTED] wrote regarding Re: downgrade?: * Philipp Huber [EMAIL PROTECTED] [001007 04:08] wrote: hi! is it possible to downgrade a freebsd-current installation to -stable? or is it better to reinstall the whole system? It's possible by building a 4.x-stable system and tar'ing the /usr/src and /usr/obj over to your -current then doing several 'make -k installworld' followed by a 'make installworld' to make sure it's all been installed then by building a kernel using the "make buildkernel" method described in src/UPDATING. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." Dear Alfred Perlstein, caution type="I haven't (as yet) tried this" From the posts I have been reading, I seem to understand that the following may apply (depending on the divergence/relationship between -CURRENT and -STABLE): -- It may be necessary to downgrade the toolchain (e.g. binutils; gcc); -- It may be necessary to downgrade "script"utils (ie perl). /caution Yes you're correct there will be problems with perl, that's why you need a 4.x machine to do the building on and that's also why you may need several 'make -k installworld' runs to finally get a 'make installworld' to work. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: downgrade?
On Sat, 7 Oct 2000, Alfred Perlstein wrote: Yes you're correct there will be problems with perl, that's why you need a 4.x machine to do the building on and that's also why you may need several 'make -k installworld' runs to finally get a 'make installworld' to work. How about: sh -c "while true ; do make -k installworld break ; done" Would this work? This is assuming that make -k returns a success (0) error code when there are no errors. Does make -k return an error code when the last command in the Makefile is successful, even if there are errors? - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: downgrade?
Dear Alfred Perlstein, caution type="I haven't (as yet) tried this" From the posts I have been reading, I seem to understand that the following may apply (depending on the divergence/relationship between -CURRENT and -STABLE): -- It may be necessary to downgrade the toolchain (e.g. binutils; gcc); -- It may be necessary to downgrade "script"utils (ie perl). /caution Yes you're correct there will be problems with perl, that's why you need a 4.x machine to do the building on and that's also why you may need several 'make -k installworld' runs to finally get a 'make installworld' to work. Oooops, I had another problem in mind. I thought of the theoretical general problem of downgrading a -CURRENT machine in a "self-consistent" fashion (ie on the same machine). I haven't done that (so far), so I am not aware of any [other] unwanted side-effects. AFAIR, a few weeks ago, someone performed such an operation (in the first week of August or so); I read several posts about the matter. If somebody has successfully tried such an operation recently (on a PRE_SMPNG machine), s/he will be able to help Phillip. Anyway, your suggestion sounds safer. Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Downgrade ????
On Sun, Aug 22, 1999 at 02:49:49PM -0700, william woods wrote: OK, this is kinda a crazy questions, but..what the hell ...snip... How possible is it to cvsup stable ( I would blow away /uusr/src first) and then do a make world and have a 3.2-stable system or should I just re-install 3.2-stable? I think it would be better if you did a binary upgrade. That way you don't have to worry about build tools from CURRENT doing something funny to your 'make world'. In either case you will want to remove libraries from CURRENT not present in STABLE and any that may have had a version bump for CURRENT, ie. libfoo.so.1 in STABLE was libfoo.so.2 in CURRENT. Any ports that you compiled with c++ in CURRENT will have to be recompiled after you downgrade. Those are the types of issues I think you will run into. Doing the binary upgrade should preserve your /etc so your password database should be OK. It would of course be prudent to back up /etc anyway. Good luck. -- Glenn Johnson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message