Re: upgrade qjail
Guys! I have a similar problem. But from your answer I don't understand, is it needed to create all jails from scratch?!! Or it possible recreate existed jails with qjail-3.0? Tell me please how to do that procedure without reinstalling all jails from scratch. 09.06.2013, 07:55, Fbsd8 fb...@a1poweruser.com: Masayoshi Fujimoto wrote: Hi. Could you tell me how to upgrade qjail-1.7 to qjail-3.0 ? I can not start www. So I have to use qjail-1.7 now. _ root@freebsd:/root # pkg_info | grep qjail qjail-1.7 Utility to quickly deploy and manage jails root@freebsd:/root # jls JID IP Address Hostname Path 1 192.168.0.20 www /usr/jails/www root@freebsd:/root # portmaster qjail root@freebsd:/root # rehash root@freebsd:/root # pkg_info | grep qjail qjail-3.0 Utility to quickly deploy and manage jails root@freebsd:/root # reboot I got the following message. jail: qjail: path : not an absolute pathname Error: /usr/sbin/jail failed to start jail www. because of errors in jail.conf file. root@freebsd:/root # cat /etc/jail.conf qjail { host.hostname = qjail; path = ; mount.fstab = ; exec.start = /bin/sh /etc/rc; exec.stop = /bin/sh /etc/rc.shutdown; exec.consolelog = /var/log/qjail.qjail.console.log; devfs_ruleset = 4; allow.mount.devfs; } So I edited /etc/jail.conf : www { host.hostname = www; path = /usr/jails/www; mount.fstab = ; exec.start = /bin/sh /etc/rc; exec.stop = /bin/sh /etc/rc.shutdown; exec.consolelog = /var/log/qjail.qjail.console.log; devfs_ruleset = 4; allow.mount.devfs; ip4.addr = 192.168.0.20; interface = alc0; } root@freebsd:/root # /usr/local/etc/rc.d/qjail.bootime restart jail: qjail: path : not an absolute pathname Error: /usr/sbin/jail failed to start jail www. because of errors in jail.conf file. I got same massage. My /etc/jail.conf has been changed default one. qjail-1.7 is way out of date. you have to delete all your 1.7 jails then do pkg_delete qjail-1.7 then portsnap fetch portsnap extract cd /usr/ports/sysutils/qjail ee Makefile and make sure it says qjail-3.0 make install clean man qjail recreate your jails ___ [1]freebsd-questions@freebsd.org mailing list [2]http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [3]freebsd-questions-unsubscr...@freebsd.org References 1. mailto:freebsd-questions@freebsd.org 2. http://lists.freebsd.org/mailman/listinfo/freebsd-questions 3. mailto:freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade qjail
Masayoshi Fujimoto wrote: Hi. Could you tell me how to upgrade qjail-1.7 to qjail-3.0 ? I can not start www. So I have to use qjail-1.7 now. _ root@freebsd:/root # pkg_info | grep qjail qjail-1.7 Utility to quickly deploy and manage jails root@freebsd:/root # jls JID IP Address Hostname Path 1 192.168.0.20www /usr/jails/www root@freebsd:/root # portmaster qjail root@freebsd:/root # rehash root@freebsd:/root # pkg_info | grep qjail qjail-3.0 Utility to quickly deploy and manage jails root@freebsd:/root # reboot I got the following message. jail: qjail: path : not an absolute pathname Error: /usr/sbin/jail failed to start jail www. because of errors in jail.conf file. root@freebsd:/root # cat /etc/jail.conf qjail { host.hostname = qjail; path= ; mount.fstab = ; exec.start = /bin/sh /etc/rc; exec.stop = /bin/sh /etc/rc.shutdown; exec.consolelog = /var/log/qjail.qjail.console.log; devfs_ruleset = 4; allow.mount.devfs; } So I edited /etc/jail.conf : www { host.hostname = www; path= /usr/jails/www; mount.fstab = ; exec.start = /bin/sh /etc/rc; exec.stop = /bin/sh /etc/rc.shutdown; exec.consolelog = /var/log/qjail.qjail.console.log; devfs_ruleset = 4; allow.mount.devfs; ip4.addr = 192.168.0.20; interface = alc0; } root@freebsd:/root # /usr/local/etc/rc.d/qjail.bootime restart jail: qjail: path : not an absolute pathname Error: /usr/sbin/jail failed to start jail www. because of errors in jail.conf file. I got same massage. My /etc/jail.conf has been changed default one. qjail-1.7 is way out of date. you have to delete all your 1.7 jails then do pkg_delete qjail-1.7 then portsnap fetch portsnap extract cd /usr/ports/sysutils/qjail ee Makefile and make sure it says qjail-3.0 make install clean man qjail recreate your jails ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade packages
On Thu, 25 Apr 2013 15:05:25 +0200, Pol Hallen wrote: Hi all! I come from linux os and I read a lot documentations about freebsd. I've a doubt: when I've some packages installed and I need upgrade it, I need to recompile those packages or there's another (fast) way to do this? With the new pkgng (the replacement for the traditional pkg infrastructure that handles precompiled binary packages) this won't be a problem, as long as the default compile options and settings are fine for you. If not, today's PCs have multiple plenticore CPUs with tons of RAM and endless hard disks, so running portmaster -a won't be a big deal. :-) On FreeBSD, it's _your_ choice. It's already in The FreeBSD Handbook: http://www.freebsd.org/doc/en/books/handbook/pkgng-intro.html Soon, it will be the system's default. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
On 27/03/2013 17:43, Volodymyr Kostyrko wrote: 2013-03-27 18:37, Loic Capdeville wrote: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? It hasn't printed anything since the first time I tried to run it... and still print nothing. So here is a main problem. If it prints nothing it doesn't work. Do you have portupgrade or portmaster installed? Did it yield at least one line? Some errors? If it doesn't that's surely a sign that something is going wrong. I use portupgrade regularly to upgrade my ports, and usually everything goes right. If fails only with that particular operation (or these portupgrade options) Do I have to install devel/py-distribute separately, or should the portupgrade -fo command do everything itself (uninstall py-setuptools and install py-distribute) ? This command should forcefully deintsall second package and replace it with first one. I'm not using portupgrade, I switched to portmaster long time ago so I can't help you with it. If you want to make the switch by hand I think you should: pkg_delete -f py27-setuptools-0.6c11_3 # now write down the whole list of dependent packages cd /usr/ports/devel/py-distribute ; make install clean portupgrade -f ..list of packages that require setuptools.. If finally did it by hand. Note: upgrading packages that require setuptools isn't necessary, since py-distribute is backward compatible with py-setuptools. Thanks for your help. Loic ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
On Wed, 27 Mar 2013 13:22:19 +0100 Loic Capdeville articulated: I'm trying to update devel/py-setuptools which has been replaced by devel/py-distribute. As mentioned in /usr/ports/UPDATING I did portupgrade -fo devel/py-distribute devel/py-setuptools since I'm using ports, but nothing happens. Output of pkg_version -vIL= : py27-setuptools-0.6c11_3 succeeds index (index has 0.6.35) I already tried to fix the package registry using pkgdb -F. I've been trying to fix this for days, but still can't find a solution. I have the same problem. However, since everything is apparently working I just chose to ignore it. It probably should get corrected though. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
2013-03-27 14:22, Loic Capdeville wrote: Hi ! I'm trying to update devel/py-setuptools which has been replaced by devel/py-distribute. As mentioned in /usr/ports/UPDATING I did portupgrade -fo devel/py-distribute devel/py-setuptools since I'm using ports, but nothing happens. Output of pkg_version -vIL= : py27-setuptools-0.6c11_3 succeeds index (index has 0.6.35) I already tried to fix the package registry using pkgdb -F. I've been trying to fix this for days, but still can't find a solution. Any idea ? Can you post contents of /usr/local/lib/python2.7/site-packages/easy-install.pth* files? -- Sphinx of black quartz, judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
On 27/03/2013 13:50, Volodymyr Kostyrko wrote: 2013-03-27 14:22, Loic Capdeville wrote: Hi ! I'm trying to update devel/py-setuptools which has been replaced by devel/py-distribute. As mentioned in /usr/ports/UPDATING I did portupgrade -fo devel/py-distribute devel/py-setuptools since I'm using ports, but nothing happens. Output of pkg_version -vIL= : py27-setuptools-0.6c11_3 succeeds index (index has 0.6.35) I already tried to fix the package registry using pkgdb -F. I've been trying to fix this for days, but still can't find a solution. Any idea ? Can you post contents of /usr/local/lib/python2.7/site-packages/easy-install.pth* files? Thanks for your quick response. Here is what you requested: -rw-r--r-- 1 root wheel 395 Mar 13 04:50 /usr/local/lib/python2.7/site-packages/easy-install.pth -rw-r--r-- 1 root wheel 215 Dec 30 15:04 /usr/local/lib/python2.7/site-packages/easy-install.pth.dist ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
On 27/03/2013 14:00, Loic Capdeville wrote: On 27/03/2013 13:50, Volodymyr Kostyrko wrote: 2013-03-27 14:22, Loic Capdeville wrote: Hi ! I'm trying to update devel/py-setuptools which has been replaced by devel/py-distribute. As mentioned in /usr/ports/UPDATING I did portupgrade -fo devel/py-distribute devel/py-setuptools since I'm using ports, but nothing happens. Output of pkg_version -vIL= : py27-setuptools-0.6c11_3 succeeds index (index has 0.6.35) I already tried to fix the package registry using pkgdb -F. I've been trying to fix this for days, but still can't find a solution. Any idea ? Can you post contents of /usr/local/lib/python2.7/site-packages/easy-install.pth* files? Thanks for your quick response. Here is what you requested: -rw-r--r-- 1 root wheel 395 Mar 13 04:50 /usr/local/lib/python2.7/site-packages/easy-install.pth -rw-r--r-- 1 root wheel 215 Dec 30 15:04 /usr/local/lib/python2.7/site-packages/easy-install.pth.dist ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ... and the files content: /usr/local/lib/python2.7/site-packages/easy-install.pth: import sys; sys.__plen = len(sys.path) ./setuptools-0.6c11-py2.7.egg ./Pygments-1.5-py2.7.egg ./Babel-0.9.6-py2.7.egg ./MarkupSafe-0.15-py2.7-freebsd-9.0-RELEASE-amd64.egg ./Jinja2-2.6-py2.7.egg ./Sphinx-1.1.3-py2.7.egg ./virtualenv-1.9.1-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) /usr/local/lib/python2.7/site-packages/easy-install.pth.dist: import sys; sys.__plen = len(sys.path) ./setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
2013-03-27 15:06, Loic Capdeville wrote: /usr/local/lib/python2.7/site-packages/easy-install.pth: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg ../Pygments-1.5-py2.7.egg ../Babel-0.9.6-py2.7.egg ../MarkupSafe-0.15-py2.7-freebsd-9.0-RELEASE-amd64.egg ../Jinja2-2.6-py2.7.egg ../Sphinx-1.1.3-py2.7.egg ../virtualenv-1.9.1-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) /usr/local/lib/python2.7/site-packages/easy-install.pth.dist: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? -- Sphinx of black quartz, judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
On 27/03/2013 14:27, Volodymyr Kostyrko wrote: 2013-03-27 15:06, Loic Capdeville wrote: /usr/local/lib/python2.7/site-packages/easy-install.pth: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg ../Pygments-1.5-py2.7.egg ../Babel-0.9.6-py2.7.egg ../MarkupSafe-0.15-py2.7-freebsd-9.0-RELEASE-amd64.egg ../Jinja2-2.6-py2.7.egg ../Sphinx-1.1.3-py2.7.egg ../virtualenv-1.9.1-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) /usr/local/lib/python2.7/site-packages/easy-install.pth.dist: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? It hasn't printed anything since the first time I tried to run it... and still print nothing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
2013-03-27 15:33, Loic Capdeville wrote: On 27/03/2013 14:27, Volodymyr Kostyrko wrote: 2013-03-27 15:06, Loic Capdeville wrote: /usr/local/lib/python2.7/site-packages/easy-install.pth: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg ../Pygments-1.5-py2.7.egg ../Babel-0.9.6-py2.7.egg ../MarkupSafe-0.15-py2.7-freebsd-9.0-RELEASE-amd64.egg ../Jinja2-2.6-py2.7.egg ../Sphinx-1.1.3-py2.7.egg ../virtualenv-1.9.1-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) /usr/local/lib/python2.7/site-packages/easy-install.pth.dist: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? It hasn't printed anything since the first time I tried to run it... and still print nothing. So here is a main problem. If it prints nothing it doesn't work. Do you have portupgrade or portmaster installed? Did it yield at least one line? Some errors? If it doesn't that's surely a sign that something is going wrong. -- Sphinx of black quartz, judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
On 27/03/2013 17:30, Volodymyr Kostyrko wrote: 2013-03-27 15:33, Loic Capdeville wrote: On 27/03/2013 14:27, Volodymyr Kostyrko wrote: 2013-03-27 15:06, Loic Capdeville wrote: /usr/local/lib/python2.7/site-packages/easy-install.pth: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg ../Pygments-1.5-py2.7.egg ../Babel-0.9.6-py2.7.egg ../MarkupSafe-0.15-py2.7-freebsd-9.0-RELEASE-amd64.egg ../Jinja2-2.6-py2.7.egg ../Sphinx-1.1.3-py2.7.egg ../virtualenv-1.9.1-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) /usr/local/lib/python2.7/site-packages/easy-install.pth.dist: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? It hasn't printed anything since the first time I tried to run it... and still print nothing. So here is a main problem. If it prints nothing it doesn't work. Do you have portupgrade or portmaster installed? Did it yield at least one line? Some errors? If it doesn't that's surely a sign that something is going wrong. I use portupgrade regularly to upgrade my ports, and usually everything goes right. If fails only with that particular operation (or these portupgrade options) Do I have to install devel/py-distribute separately, or should the portupgrade -fo command do everything itself (uninstall py-setuptools and install py-distribute) ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
2013-03-27 18:37, Loic Capdeville wrote: import sys; sys.__plen = len(sys.path) ../setuptools-0.6c11-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) Looks like py-distribute is not installed at all. what was the outcome of portupgrade -fo devel/py-distribute devel/py-setuptools? Can you try running that again? It hasn't printed anything since the first time I tried to run it... and still print nothing. So here is a main problem. If it prints nothing it doesn't work. Do you have portupgrade or portmaster installed? Did it yield at least one line? Some errors? If it doesn't that's surely a sign that something is going wrong. I use portupgrade regularly to upgrade my ports, and usually everything goes right. If fails only with that particular operation (or these portupgrade options) Do I have to install devel/py-distribute separately, or should the portupgrade -fo command do everything itself (uninstall py-setuptools and install py-distribute) ? This command should forcefully deintsall second package and replace it with first one. I'm not using portupgrade, I switched to portmaster long time ago so I can't help you with it. If you want to make the switch by hand I think you should: pkg_delete -f py27-setuptools-0.6c11_3 # now write down the whole list of dependent packages cd /usr/ports/devel/py-distribute ; make install clean portupgrade -f ..list of packages that require setuptools.. -- Sphinx of black quartz, judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade devel/py-setuptools
On 27-3-2013 17:37, Loic Capdeville wrote: I use portupgrade regularly to upgrade my ports, and usually everything goes right. If fails only with that particular operation (or these portupgrade options) Do I have to install devel/py-distribute separately, or should the portupgrade -fo command do everything itself (uninstall py-setuptools and install py-distribute) ? I had some problems with this one as well. I eventually ended up by pkg_deleting -f the package, delete manually some file portinstall complaints about, and after that it worked. Peter -- http://www.boosten.org - Geen virus gevonden in dit bericht. Gecontroleerd door AVG - www.avg.com Versie: 2013.0.2904 / Virusdatabase: 2641/6206 - datum van uitgifte: 03/26/13 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade from 6.4 to 9.1?
On 3/16/2013 3:46 PM, Fbsd8 wrote: Dan Nelson wrote: In the last episode (Mar 16), Drew Tomlinson said: I have an old system happily running 6.4 but am finding that it can no longer download or build a ports index. Thus I guess it's time to upgrade. What gotchas do I need to look out for? In the past my upgrades have always been simply downloading new source, reviewing kernel config file, and then rebuilding the system. Any ports that didn't work after that I would just rebuild as well. However I've never waited this long to upgrade. Do I need to do anything different? You won't be able to do a straight source build from 6.4 to 9.1; too many low-level changes like Makefile syntax and compiler options have changed. If you are comfortable with temporarily disabling non-essential things that fail to build, it is definitely possible to do a long jump to 9.1, but it'd be safer to either hop from 6.4 - (7-stable or 8-stable) - 9 doing buildkernels and buildworlds, or just do a binary upgrade of kernel and base system to 9.1. The best approach is to backup your user data and do a fresh install from 9.1 cdrom. You will bypass a bunch of headaches which may in the end force you to do a fresh install anyway. And it will save you a lot of compile time. It's alway a good feeling to know you have a pristine system when you start having problems. Thanks for the suggestions. I'll give these a try. Cheers, Drew -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade from 6.4 to 9.1?
In the last episode (Mar 16), Drew Tomlinson said: I have an old system happily running 6.4 but am finding that it can no longer download or build a ports index. Thus I guess it's time to upgrade. What gotchas do I need to look out for? In the past my upgrades have always been simply downloading new source, reviewing kernel config file, and then rebuilding the system. Any ports that didn't work after that I would just rebuild as well. However I've never waited this long to upgrade. Do I need to do anything different? You won't be able to do a straight source build from 6.4 to 9.1; too many low-level changes like Makefile syntax and compiler options have changed. If you are comfortable with temporarily disabling non-essential things that fail to build, it is definitely possible to do a long jump to 9.1, but it'd be safer to either hop from 6.4 - (7-stable or 8-stable) - 9 doing buildkernels and buildworlds, or just do a binary upgrade of kernel and base system to 9.1. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade from 6.4 to 9.1?
Dan Nelson wrote: In the last episode (Mar 16), Drew Tomlinson said: I have an old system happily running 6.4 but am finding that it can no longer download or build a ports index. Thus I guess it's time to upgrade. What gotchas do I need to look out for? In the past my upgrades have always been simply downloading new source, reviewing kernel config file, and then rebuilding the system. Any ports that didn't work after that I would just rebuild as well. However I've never waited this long to upgrade. Do I need to do anything different? You won't be able to do a straight source build from 6.4 to 9.1; too many low-level changes like Makefile syntax and compiler options have changed. If you are comfortable with temporarily disabling non-essential things that fail to build, it is definitely possible to do a long jump to 9.1, but it'd be safer to either hop from 6.4 - (7-stable or 8-stable) - 9 doing buildkernels and buildworlds, or just do a binary upgrade of kernel and base system to 9.1. The best approach is to backup your user data and do a fresh install from 9.1 cdrom. You will bypass a bunch of headaches which may in the end force you to do a fresh install anyway. And it will save you a lot of compile time. It's alway a good feeling to know you have a pristine system when you start having problems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On Wed, Feb 13, 2013 at 11:35 AM, Bernt Hansson b...@bananmonarki.se wrote: A blind Linux user's homepage: http://juliencoder.de/ The homepage of my provider: http://www.o2online.de/ What site is more pleasant ;)? The first one. Agree, it contains more information than the second one which is picture-flash based and I cannot see ~80% of its content :-) Anyway the best thing in BSD is that you can do ANYTHING from the commandline with a simple command set, including full system configuration, package creation, kernel build, etc :-) Best regards :-) Tomek Cedro -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On 12/02/2013 21:38, Ronald F. Guilmette wrote: In general, I don't upgrade my ports very often, so up until recently I was running a fairly old version of firefox (firefox-15.0.1,1). But over the weekend, I moved everything over to a new drive containing the latest 9.1-RELEASE FreeBSD, and with a complete set of freshly rebuilt ports, including the latest firefox 18.0.1. (As part of this process, I copied my entire /home directory over to the new drive.) So anway, mostly everything is still working ok, however at some time during this process, firefox apparently lost track of all of my personal settings... my start page, all of my bookmarks, and all of my saved web site user IDs an passwords. I looked in the /usr/ports/UPDATING file for some clue as to why this might have happened and found none. Looking into this issue a bit deeper, I've now learned that all of one's personal settings are stored in a directory having a name which has the following general form: ~/.mozilla/firefox/.default where the part is some eight character apparently random combination of lower case letters and digits. The odd thing is that it appears that all of my old firefox setting are still alive and well and living under a subdirectory of the ~/.mozilla/firefox directory called 4up9dkb1.default. However it does also appear that my execution of firefox, for the first time, on this new system I've been putting together has resulted in the creation of a brand new parallel subdirectory, located in the same directory as my original personal settings .default directory, but this new one is named nh2ykiym.default. And now, firefox is apparently saving and retrieving my (new set of) personal settings out of that new directory. So, um, what gives? Why did this happen? And more to the point, can I get back all of my personal settings just via the following seemingly intutive commands: rm -fr nh2ykiym.default mv 4up9dkb1.default nh2ykiym.default or will that break something else in some obscure but annoying way? Is there a file .mozilla/firefox/profiles.ini? If so it should list which profile to use. Just change it to the one you want and it should just work. I'm using an older version so don't know how the latest works Chris Regards, rfg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On Wed, 2013-02-13 at 13:13 +, Chris Whitehouse wrote: Is there a file .mozilla/firefox/profiles.ini? If so it should list which profile to use. Just change it to the one you want and it should just work. I'm using an older version so don't know how the latest works Good point Chris! I've forgotten, that there is such a file, when using profiles. Btw. they are formated like this: spinymouse@precise:~$ ls -l /mnt/archlinux/home/spinymouse/.mozilla/firefox total 8 lrwxrwxrwx 1 spinymouse users 18 Dec 13 2011 archfox - /mnt/data2/archfox drwx-- 13 spinymouse users 4096 Oct 31 15:11 ndos9d6q.default -rw-r--r-- 1 spinymouse users 143 Apr 18 2012 profiles.ini spinymouse@precise:~$ cat /mnt/archlinux/home/spinymouse/.mozilla/firefox/profiles.ini [General] StartWithLastProfile=1 [Profile0] Name=d IsRelative=1 Path=ndos9d6q.default Default=1 [Profile1] Name=x IsRelative=1 Path=archfox ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
In message CAFYkXjmA_DTP=Bzf=D+QSw890tbrz0+ZNTiLaWNj=dmr749...@mail.gmail.com CeDeROM cede...@tlen.pl wrote: On Tue, Feb 12, 2013 at 10:38 PM, Ronald F. Guilmette r...@tristatelogic.com wrote: Looking into this issue a bit deeper, I've now learned that all of one's personal settings are stored in a directory having a name which has the following general form: ~/.mozilla/firefox/.default Hey Ronald, are you sure there is no corruption on the disk? I have no reason whatsoever to suspect that there is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
The profile should be available by 'firefox -ProfileManager' [1], OTOH I'm booted to Ubuntu Precise and the ProfileManager doesn't start, for Arch Linux I used two profiles, one shared with another Linux and after a while I couldn't use the shared profiles anymore, but the ProfileManger still started. In the past rm -fr nh2ykiym.default mv 4up9dkb1.default nh2ykiym.default worked, or instead simply chose it with the ProfileManger, but nowadays there might be something fishy. [1] IIRC only one could have the name *.default, the other must have another name, *.foo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On Tue, 2013-02-12 at 22:49 +0100, Ralf Mardorf wrote: The profile should be available by 'firefox -ProfileManager' [1], OTOH I'm booted to Ubuntu Precise and the ProfileManager doesn't start, for Arch Linux I used two profiles, one shared with another Linux and after a while I couldn't use the shared profiles anymore, but the ProfileManger still started. In the past rm -fr nh2ykiym.default mv 4up9dkb1.default nh2ykiym.default worked, or instead simply chose it with the ProfileManger, but nowadays there might be something fishy. [1] IIRC only one could have the name *.default, the other must have another name, *.foo. simply try mv nh2ykiym.default nh2ykiym.test perhaps it then will use 4up9dkb1.default automatically ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On Tue, Feb 12, 2013 at 10:38 PM, Ronald F. Guilmette r...@tristatelogic.com wrote: Looking into this issue a bit deeper, I've now learned that all of one's personal settings are stored in a directory having a name which has the following general form: ~/.mozilla/firefox/.default Hey Ronald, are you sure there is no corruption on the disk? Have you preformatted your new drive? I had disks that lost data if used with no pre-format stage. Have you tried forcing fsck? Sometimes when my machine crash there is a silent corruption on the filesystem and some settings are lost/changed... -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On Tue, 2013-02-12 at 22:52 +0100, Ralf Mardorf wrote: On Tue, 2013-02-12 at 22:49 +0100, Ralf Mardorf wrote: The profile should be available by 'firefox -ProfileManager' [1], OTOH I'm booted to Ubuntu Precise and the ProfileManager doesn't start, for Arch Linux I used two profiles, one shared with another Linux and after a while I couldn't use the shared profiles anymore, but the ProfileManger still started. In the past rm -fr nh2ykiym.default mv 4up9dkb1.default nh2ykiym.default worked, or instead simply chose it with the ProfileManger, but nowadays there might be something fishy. [1] IIRC only one could have the name *.default, the other must have another name, *.foo. simply try mv nh2ykiym.default nh2ykiym.test perhaps it then will use 4up9dkb1.default automatically After a 'killall -9 -w firefox' the ProfileManager did start :). Closing the windows wasn't enough ;). FWIW version for this Linux install is 15.0.1. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On Tue, 2013-02-12 at 23:00 +0100, CeDeROM wrote: Hey Ronald, are you sure there is no corruption on the disk? Have you preformatted your new drive? I had disks that lost data if used with no pre-format stage. Have you tried forcing fsck? Sometimes when my machine crash there is a silent corruption on the filesystem and some settings are lost/changed... Firefox is my preferred browser, but it has some disadvantages compared to other browsers. 1. It's slow and bloated, even without add-ons, fortunately it doesn't matter on my relatively modern machine. 2. It's known for all kind of issues. Some years ago there sometimes was the need to delete the configuration, to get Firefox running again, it simply couldn't be started sometimes, because there were bugs. Regarding to the kind of issue, it's more likely that Firefox is buggy and the HDD still is ok. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On Tue, Feb 12, 2013 at 11:11 PM, Ralf Mardorf ralf.mard...@rocketmail.com wrote: Firefox is my preferred browser, but it has some disadvantages compared to other browsers. Give a try to Chromium :-) I have been using Opera for long time because it was fast and small. Not that long ago I have switched to Chromium and this was really good step - it is opensource/bsd, faster than firefox, you will find shortcut keys almost the same as in firefox/gnome, very good integration with google, h264 support, lots of applications/applets, etc etc :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On Tue, 2013-02-12 at 23:26 +0100, CeDeROM wrote: On Tue, Feb 12, 2013 at 11:11 PM, Ralf Mardorf ralf.mard...@rocketmail.com wrote: Firefox is my preferred browser, but it has some disadvantages compared to other browsers. Give a try to Chromium :-) I have been using Opera for long time because it was fast and small. Not that long ago I have switched to Chromium and this was really good step - it is opensource/bsd, faster than firefox, you will find shortcut keys almost the same as in firefox/gnome, very good integration with google, h264 support, lots of applications/applets, etc etc :-) My favorites are Firefox and Opera, but I also have Chromium installed for both, FreeBSD and Linux. I don't like the new style of Opera and the style of Chromium. I prefer classic menus. In the future I might need to install Chrome :S. I'm not a flash fan, but I already couldn't download the last Internet provider bill :D, perhaps a flash or some other script issue. Btw. the design of Opera still is closer to my workflow than the design of Chromium. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On Tue, 12 Feb 2013 23:40:41 +0100, Ralf Mardorf wrote: I don't like the new style of Opera and the style of Chromium. I prefer classic menus. Luckily you can change that in Opera and give it the traditional style. Still Opera suffers from ongoing disimprovement (e. g. reduction of functionality in file save dialog or printing support). I'm not a flash fan, but I already couldn't download the last Internet provider bill :D, perhaps a flash or some other script issue. Maybe Java? Some old fasioned guys still use it... ;-) Even though I don't like Flash especially because it has become what animated GIFs have been used for in the past - replacement for HTML, nagging, stealing focus, aggressive advertising with sound and so on - it perfectly works with Opera. Btw. the design of Opera still is closer to my workflow than the design of Chromium. That's my problem with Chromium and Firefox too. I like the possibility to remove visual controls (red X button on tabs for example) without losing functionality (middle click on tab closes tab). From my very individual experience, Opera offers the best integration of mouse and keyboard. It's sufficiently fast and renders stuff acceptably correct. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
On Wed, 2013-02-13 at 00:16 +0100, Polytropon wrote: Even though I don't like Flash especially because it has become what animated GIFs have been used for in the past - replacement for HTML, nagging, stealing focus, aggressive advertising with sound and so on - it perfectly works with Opera. The best websites are made by people using braille instead of displays. Sometimes they choose less good color combinations :D, but they usually are willing to fix it, if you ask them. I'm a musician, I need to activate the sound card and to turn on additional audio gear, before I get sound. I don't like noise all the times. It reminds me of the idiotic sounds on the main bridge of the Enterprise. Desktop sound is disabled and if I need audio notification I want the bell, a simple beep from the computer case's thingy. Idiotic animations stealing focus are a serious issue for me, regarding to dyslexia signs already are animated for me, when they aren't animated. I already can't use applications that animate a mini icon in a menu bar, if it's impossible to disable it. It's drivin' me crazy. It's drivin' me nuts. Even if old printers are slow, loud and the printing wasn't brilliant, I'm missing my ink ribbon listing paper printers. Printing was cheap that time and reading was much nicer than using the monitor of my computer or my tablet PC. I've got inkjet printer, but it's to expensive for me, to use them. I heard that reading should be more comfortable on a cheap reader than on an iPad, but I won an iPad and will keep it as a toy and reader and won't buy a reader, since they aren't really cheap. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade causes loss of all firefox settings (?)
Forwarded Message From: Ralf Mardorf ralf.mard...@alice-dsl.net To: freebsd-questions@freebsd.org Subject: Re: Upgrade causes loss of all firefox settings (?) Date: Wed, 13 Feb 2013 00:52:34 +0100 On Wed, 2013-02-13 at 00:47 +0100, Ralf Mardorf wrote: The best websites are made by people using braille instead of displays. Sometimes they choose less good color combinations :D, but they usually are willing to fix it, if you ask them. A blind Linux user's homepage: http://juliencoder.de/ The homepage of my provider: http://www.o2online.de/ What site is more pleasant ;)? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade icu failed
Am 23.12.12 17:56, schrieb Walter Hurry: pkg_info should be reporting 'no packages installed'. What is the output from pkg2ng? I get there a lot of error messages: pkg_info: the package info for package 'ImageMagick-6.8.0.7' is corrupt usage: pkg info pkg-name pkg info -a pkg info [-eDgxXdrlBsqOf] pkg-name pkg info [-drlBsqfR] -F pkg-file For more information see 'pkg help info'. pkg_info: the package info for package 'ImageMagick-6.8.0.7' is corrupt make: don't know how to make showconfig. Stop cat: /var/db/pkg/ImageMagick-6.8.0.7/+COMMENT: No such file or directory pkg_info: the package info for package 'ImageMagick-6.8.0.7' is corrupt egrep: /var/db/pkg/ImageMagick-6.8.0.7/+CONTENTS: No such file or directory pkg: open(/tmp/pkg2ngfNwkS/+DESC): No such file or directory Segmentation fault (core dumped) Registration of ImageMagick-6.8.0.7 failed. name: ImageMagick version: 6.8.0.7 origin: comment: | maintainer: prefix: licenselogic: single deps: pkg_info: the package info for package 'ORBit2-2.14.19' is corrupt usage: pkg info pkg-name pkg info -a pkg info [-eDgxXdrlBsqOf] pkg-name pkg info [-drlBsqfR] -F pkg-file It continues with a lot of packages, it seems for all packages upgraded since the change from pkg to pkgng. Is this maybe a problem with portmaster? Thanks, Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade icu failed
On Sun, 23 Dec 2012 17:16:02 +0100, Matthias Fechner wrote: Dear list, I checked the file /usr/ports/UPDATING and there is noted 20121218 for icu to execute the command: portmaster -w -r icu (my system is already on pkgng as described a in the UPDATING file, 20121015). If I execute now portmaster i get the following error message: * === icu-4.8.1.1_1 1/1 === Currently installed version: icu-4.8.1.1_1 === Port directory: /usr/ports/devel/icu === Starting check for build dependencies === Gathering dependency list for devel/icu from ports === Launching child to update pkg-1.0.3_1 to pkg-1.0.4_1 === icu-4.8.1.1_1 1/1 pkg-1.0.3_1 (1/16) === Currently installed version: pkg-1.0.3_1 === Port directory: /usr/ports/ports-mgmt/pkg === Starting check for build dependencies === Gathering dependency list for ports-mgmt/pkg from ports === No dependencies for ports-mgmt/pkg === Cleaning for pkg-1.0.4_1 You are about to convert your system to pkgng while you have ports/packages installed with the old pkg_install tools. You can choose to: - keep pkg_install as the package management system by adding this line to /etc/make.conf: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. === make failed for ports-mgmt/pkg === Aborting update === Update for pkg-1.0.3_1 failed === Aborting update Is this a know problem or the there someting in the UPDATING file not mentioned? In /etc/make.conf I have: WITH_PKGNG=yes (as descriped in 20121015) What's the output from pkg_info? Have you done any other upgrades of ports since migrating to pkgng? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade icu failed
Am 23.12.12 17:29, schrieb Walter Hurry: What's the output from pkg_info? pkg info gives me a full list of all installed ports, pkg_info complains about a lot of corrupted package infos, but i think this is related to, pkg is new and pkg_info is the old tool. Have you done any other upgrades of ports since migrating to pkgng? yes, I did my last upgrade 12.12.2012. Till the note in /usr/ports/UPDATING 20121212. After these steps I executed portmaster -a, which was successfully. Thanks, Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade icu failed
On Sun, 23 Dec 2012 17:44:26 +0100, Matthias Fechner wrote: Am 23.12.12 17:29, schrieb Walter Hurry: What's the output from pkg_info? pkg info gives me a full list of all installed ports, pkg_info complains about a lot of corrupted package infos, but i think this is related to, pkg is new and pkg_info is the old tool. Have you done any other upgrades of ports since migrating to pkgng? yes, I did my last upgrade 12.12.2012. Till the note in /usr/ports/UPDATING 20121212. After these steps I executed portmaster -a, which was successfully. pkg_info should be reporting 'no packages installed'. What is the output from pkg2ng? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade of portupgrade
On 23/04/2012 17:13, n dhert wrote: Today, my nightly run of portsnap informed me there is un update for: # pkg_version -vIL= portupgrade-2.4.9.3.2 needs updating (index has 2.4.9.3_1,2) = SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M === Giving up on fetching files: pkgtools-2.4.9.3.tar.bz2 ^M Make sure the Makefile and distinfo file (/usr/ports/ports-mgmt/portupgrade/dist info)^M are up to date. If you are absolutely sure you want to override this^M check, type make NO_CHECKSUM=yes [other args].^M *** Error code 1^M What's this problem with pkgtools ??? I have a $ ls -la /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 -rw-r--r-- 1 root wheel 79394 Aug 23 2011 /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 but no 2.4.9.3_1,2 version And, strange: if I try http://www.freebsd.org/ports, Search for pkgtools in All it finds nothing ??? Isn't that package described ?? What's going on here and how to solve it ?? The issue would appear to be the recent update was messed up. You are getting an error as the distfile you have has a different md5sum than what was saved to the port files. pkgtools is the name of the project, even though the sourceforge project name and the port name is portupgrade. On github it is pkgtools. I would guess the port name was chosen to prevent conflicts with pkg_* named tools in the base system. I would wait for the maintainer to sort things out. Currently you can download a tar.gz from github or a tar.bz from sourceforge both identified as 2.4.9.3 but there is some file differences between them. As this is a new maintainer just taken over the port about a week ago you may want to email them or submit a pr. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade of portupgrade
n dhert wrote: Today, my nightly run of portsnap informed me there is un update for: # pkg_version -vIL= portupgrade-2.4.9.3.2 needs updating (index has 2.4.9.3_1,2) Since there is no special entry in /usr/ports/UPDATING about the portupgrade update, I started my weekly # portupgrade -yaRrpb this gives: ... --- Upgrade of ports-mgmt/portupgrade started at: Mon, 23 Apr 2012 08:37:14 +0 200 --- Upgrading 'portupgrade-2.4.9.3,2' to 'portupgrade-2.4.9.3_1,2' (ports-mgmt /portupgrade) --- Build of ports-mgmt/portupgrade started at: Mon, 23 Apr 2012 08:37:14 +020 0 --- Building '/usr/ports/ports-mgmt/portupgrade' === Cleaning for portupgrade-2.4.9.3_1,2^M === License BSD accepted by the user^M === Found saved configuration for portupgrade-2.4.6,2^M === Extracting for portupgrade-2.4.9.3_1,2^M = SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M === Refetch for 1 more times files: pkgtools-2.4.9.3.tar.bz2 ^M === License BSD accepted by the user^M === Found saved configuration for portupgrade-2.4.6,2^M = pkgtools-2.4.9.3.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/.^M = Attempting to fetch http://heanet.dl.sourceforge.net/project/portupgrade/pkgt ools/2.4.9.3/pkgtools-2.4.9.3.tar.bz2^M fetch: http://heanet.dl.sourceforge.net/project/portupgrade/pkgtools/2.4.9.3/pkg tools-2.4.9.3.tar.bz2: Moved Temporarily^M it does 5 more at other places, then = Attempting to fetch http://freefr.dl.sourceforge.net/project/portupgrade/pkgt ools/2.4.9.3/pkgtools-2.4.9.3.tar.bz2^M fetch: pkgtools-2.4.9.3.tar.bz2: local file (79394 bytes) is longer than remote file (79377 bytes)^M ... then 10 more 'Attempting to fetch' with Moved temporarily then = Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/pkgtool s-2.4.9.3.tar.bz2^M === License BSD accepted by the user^M === Found saved configuration for portupgrade-2.4.6,2^M = SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M === Giving up on fetching files: pkgtools-2.4.9.3.tar.bz2 ^M Make sure the Makefile and distinfo file (/usr/ports/ports-mgmt/portupgrade/dist info)^M are up to date. If you are absolutely sure you want to override this^M check, type make NO_CHECKSUM=yes [other args].^M *** Error code 1^M ^M Stop in /usr/ports/ports-mgmt/portupgrade.^M *** Error code 1^M ^M Stop in /usr/ports/ports-mgmt/portupgrade.^M *** Error code 1^M ^M Stop in /usr/ports/ports-mgmt/portupgrade.^M --- Build of ports-mgmt/portupgrade ended at: Mon, 23 Apr 2012 08:37:45 +0200 (consumed 00:00:30) --- Upgrade of ports-mgmt/portupgrade ended at: Mon, 23 Apr 2012 08:37:45 +020 0 (consumed 00:00:30) What's this problem with pkgtools ??? I have a $ ls -la /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 -rw-r--r-- 1 root wheel 79394 Aug 23 2011 /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 but no 2.4.9.3_1,2 version And, strange: if I try http://www.freebsd.org/ports, Search for pkgtools in All it finds nothing ??? Isn't that package described ?? Search for portupgrade instead. What's going on here and how to solve it ?? I just did this upgrade utilizing portupgrade 2 days ago - 04/20/12 03:34 and did not experience any trouble. However, I noticed the name of the file that was downloaded here was: pkgtools-pkgtools-b99f3ce.tar.gz. This file was 98949 bytes in size. Today I have csup'd my ports tree and did a make fetch for this port and it downloaded a file of the same name as you have described. This file is 79377 bytes in size. I did a make for the port and it again built without error. Sounds like something was out of sync at the time you tried this. Try refreshing your ports again and see if it has been fixed. Also consider the possibility that the mirror you were using wasn't completely up to date. Either the mirror will have caught up since then, or try another mirror. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade to 9.0 - Mount to root failed..
On 8 April 2012 09:53, Airosoβicz fb. airosov...@gmail.com wrote: Greetings all, It's my 1st time on any of the FreeBSD lists I'm fairly new to FreeBSD to please bear with me.. So I've upgraded from 8.1 to 9.0 now the system can't mount in single user mode to go through the final step of installing the world.. # cvsup.. Done.. # make buildworld.. Done.. # make buildkernel.. Done.. # make installkernel.. Done.. # reboot in single user mode to install world.. Failed to mount to /dev/ad2s1a.. {Yes, that *is* my HD} I rebooted from the loader prompt with my old (GENERIC) kernel came up with the following.. peggy# ls -l /dev/ad* crw-r- 1 root operator 0, 79 Apr 8 08:47 /dev/ad2 crw-r- 1 root operator 0, 82 Apr 8 08:47 /dev/ad2s1 crw-r- 1 root operator 0, 84 Apr 8 08:47 /dev/ad2s1a peggy# cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ad2s1a / ufs rw 1 1 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 peggy# disklabel /dev/ad2s1a # /dev/ad2s1a: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 20044017 0 4.2BSD 2048 16384 28552 c: 20044017 0 unused 0 0 # raw part, don't edit peggy# fsck ** /dev/ad2s1a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 415735 files, 3148200 used, 1702923 free (40563 frags, 207795 blocks, 0.8% fragmentation) peggy# kldstat Id Refs Address Size Name 1 7 0xc040 bb5504 kernel 2 1 0xc2e1a000 26000 linux.ko I know there's many 'mount' problem discussions out there but I can't seem to find out how to overcome this problem.. Many thanx in advance for any assistance.. Regards, E. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org try specifying 'ufs:/dev/adas1a' at the kernel prompt or editing that into you fstab if you can. My devices changed and the 8-9 jump. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade to 9.0 - Mount to root failed..
On 08/04/2012 09:53, Airosoβicz fb. wrote: So I've upgraded from 8.1 to 9.0 now the system can't mount in single user mode to go through the final step of installing the world.. # cvsup.. Done.. # make buildworld.. Done.. # make buildkernel.. Done.. # make installkernel.. Done.. # reboot in single user mode to install world.. Failed to mount to /dev/ad2s1a.. {Yes, that *is* my HD} As was mentioned else-thread, you are probably hitting problems due to the name change from ad(4) to ada(4) for PATA/SATA disk devices. One way to fix this is simply to type in the new boot device in the loader and then edit /etc/fstab from single user mode -- which is fine, but you'ld have to go through the same sort of rigmarole again to revert back to 8.1 should that be necesssary. The preferred method nowadays is to label the partitions. There are three options: glabel(8) -- generic labels for geom devices, which will appear in /dev/label/foo tunefs(8) -- specifically the -L option. For UFS, labels will appear as /dev/ufs/foo gpart(8) -- GPT partitioning has built-in label support. Devices appear as /dev/gpt/foo (Additionally partitions can be referred to by uuid for the tunefs and gpart labelling schemes, but that's not relevant here.) Quite why FreeBSD needs so many different labelling schemes escapes me. gpart(8) labelling is the default for new installs of 9.0. However, given you're upgrading from 8.1, then you will likely be using MBR + bsdlabel oldstyle partitioning, so probably tunefs(8) labelling would be the best choice to get you through the 8.1 - 9.0 reboot. ie. Create the label: # tunefs -L ROOT /dev/as2s1a then edit /etc/fstab so the line for the root filesystem reads like so: /dev/ufs/ROOT / ufs rw 0 1 Repeat this for all the other UFS filesystems you have -- a good system is to label them according to their mountpoint (USR, VAR, HOME, LOCAL, and so forth.) This should work with both 8.1 and 9.0 kernels -- however, untested, so apply appropriate levels of caution. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Upgrade to 9.0 - Mount to root failed..
On Sun, 8 Apr 2012, Airoso?icz fb. wrote: It's starting to make sense now.. Mounting ufs:/dev/ad*a*2s1a i.o. from ufs:/dev/ad2s1a simply doesn't work because as I've put in my original post with # ls -l /dev/ad* it doesn't exist.. Only ad2,ad2s1 ad2s1a do.. ada device numbering is relative, so the first drive found is always ada0. If there are no ada devices in /dev at all, I'd guess too much has been removed from the custom kernel. # man 8 tunefs: The tunefs can not be run on an active filesystem. To change an active filesystem it must be downgraded to read only or to unmounted.. [Which I've done with # mount -r -f..] # tunefs: /dev/ad2s1a: failed to write superblock.. I've updated the /etc/fstab with the ROOT label but I can't get the single-user mount nor the tunefs to work.. http://www.wonkity.com/~wblock/docs/html/labels.html shows a full example. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade to 9.0 - Mount to root failed..
On 4/8/2012 8:51 AM, Airosoβicz fb. wrote: Hi Matthew, Thanx for the quick reply.. Can't get it to work though.. On 08/04/2012 09:53, Airosoβicz fb. wrote: So I've upgraded from 8.1 to 9.0 now the system can't mount in single user mode to go through the final step of installing the world.. As was mentioned else-thread, you are probably hitting problems due to the name change from ad(4) to ada(4) for PATA/SATA disk devices. It's starting to make sense now.. Mounting ufs:/dev/ad*a*2s1a i.o. from ufs:/dev/ad2s1a simply doesn't work because as I've put in my original post with # ls -l /dev/ad* it doesn't exist.. Only ad2,ad2s1 ad2s1a do.. One way to fix this is simply to type in the new boot device in the loader and then edit /etc/fstab from single user mode Which boot device..? I wish it was simple.. When you get to the loader, escape to the loader prompt. Then type lsdev to see what the loader finds. You'll have to find which one looks right, and type that into the mount failed prompt. After it's done booting, check /dev to make sure it looks right and change your fstab. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade to 9.0 - Mount to root failed..
On 04/09/12 02:17, Joshua Isom wrote: On 4/8/2012 8:51 AM, Airosoβicz fb. wrote: Hi Matthew, Thanx for the quick reply.. Can't get it to work though.. On 08/04/2012 09:53, Airosoβicz fb. wrote: So I've upgraded from 8.1 to 9.0 now the system can't mount in single user mode to go through the final step of installing the world.. As was mentioned else-thread, you are probably hitting problems due to the name change from ad(4) to ada(4) for PATA/SATA disk devices. It's starting to make sense now.. Mounting ufs:/dev/ad*a*2s1a i.o. from ufs:/dev/ad2s1a simply doesn't work because as I've put in my original post with # ls -l /dev/ad* it doesn't exist.. Only ad2,ad2s1 ad2s1a do.. One way to fix this is simply to type in the new boot device in the loader and then edit /etc/fstab from single user mode Which boot device..? I wish it was simple.. When you get to the loader, escape to the loader prompt. Then type lsdev to see what the loader finds. You'll have to find which one looks right, and type that into the mount failed prompt. After it's done booting, check /dev to make sure it looks right and change your fstab. From a theoretical point of view (I'll have to consider this for my own needs in the near future) I'd say the labeling option mentioned by Warren would be better for the long term. It may seem a little complicated to setup but it will work just about anywhere. If you continue with devices as you are at the moment you run the risk of having this trouble every time something changes. My 2c. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from 8.2 to 9.0
Op 14-1-2012 17:04, Mike Clarke schreef: On Saturday 14 January 2012, Dick Hoogendijk wrote: I had not heard of this project before. Sounds very nice if it works. Manging BE's is one of the main things I miss in the FreeBSD ZFS support. Coming from (open)Solaris this was quite a disappointment. BE's rock! Yes, it's working fine here. [...] Thank you very much for giving these examples. Sounds really nice. Have not tried it yet however. Still feel it's a pity FreeBSD did not incorporate the creation and managing of BE's within the system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from 8.2 to 9.0
Op 13-1-2012 15:00, Polytropon schreef: On Fri, 13 Jan 2012 14:42:03 +0100, Dick Hoogendijk wrote: I possible I want my server to upgrade from 8.2-RELEASE to 9.0-RELEASE. I guess the binary upgrade will not be a problem with freebsd-update -r 9.0-RELEASE fetch If so, I do like to hear the caveats. Source update also shouldn't be a problem. Setup your CVS supfile to get the 9.0-RELEASE sources and follow the instructions in the handbook and in /usr/src/Makefile's comment header. I will use the binary upgrade path. It seems easier for a non high-tech system ;-) My system is running ZFS on root now, so I would very much like to hear if the binary upgrade through freebsd-update works well for such a system (w/ zfs on root). I don't want to get stuck with a system that won't boot again because something goes wrong with zfs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from 8.2 to 9.0
On Saturday 14 January 2012, Dick Hoogendijk wrote: My system is running ZFS on root now, so I would very much like to hear if the binary upgrade through freebsd-update works well for such a system (w/ zfs on root). I don't want to get stuck with a system that won't boot again because something goes wrong with zfs. Have you considerd using manageBE http://anonsvn.h3q.com/projects/freebsd-patches/wiki/manageBE? With this tool you can set up cloned alternative Boot-Environments (BE) so that you can go back to your old BE if the new one doesn't work. I'm in the process of upgrading to 9.0 and taking the opportunity of changing over to ZFS. I needed to re-arrange my filesystem structure to boot from tank/ROOT/someBEname/ instead of tank/ (and make sure the mountpoints of any descendent file systems are suitably adjusted) but it was worth the effort. I installed 9.0-RC2 from the ISO onto a spare drive so I haven't done an 8 to 9 binary upgrade but I have used freebsd-update to upgrade from 9.0-RC2 to 9.0-RELEASE and that went through without any problems. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from 8.2 to 9.0
Op 14-1-2012 12:37, Mike Clarke schreef: On Saturday 14 January 2012, Dick Hoogendijk wrote: My system is running ZFS on root now, so I would very much like to hear if the binary upgrade through freebsd-update works well for such a system (w/ zfs on root). I don't want to get stuck with a system that won't boot again because something goes wrong with zfs. Have you considerd using manageBE http://anonsvn.h3q.com/projects/freebsd-patches/wiki/manageBE? With this tool you can set up cloned alternative Boot-Environments (BE) so that you can go back to your old BE if the new one doesn't work. I had not heard of this project before. Sounds very nice if it works. Manging BE's is one of the main things I miss in the FreeBSD ZFS support. Coming from (open)Solaris this was quite a disappointment. BE's rock! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from 8.2 to 9.0
On Saturday 14 January 2012, Dick Hoogendijk wrote: I had not heard of this project before. Sounds very nice if it works. Manging BE's is one of the main things I miss in the FreeBSD ZFS support. Coming from (open)Solaris this was quite a disappointment. BE's rock! Yes, it's working fine here. You can even upgrade a new environment while you continue working with the current one with manageBE create -n newBE -s sourceBE -p pool manageBE freebsd-upgrade -n newBE -p pool -r release manageBE activate -n newBE -p pool Then reboot into the new BE and complete the upgrade with the final freebsd-update install step. But I needed to change chroot /${bootfs} near the end of the script to chroot /${pool}/ROOT/${bootfs} to get manageBE freebsd-upgrade command to work. Along similar lines, if you need to do a massive ports upgrade which you suspect might go pear shaped then you can do it in a new BE without upsetting your working system: chroot /tank/ROOT/newBE mount -t devfs devfs /dev chroot /tank/ROOT/newBE portmaster -a chroot /tank/ROOT/newBE umount /dev ... then, if all went well, activate the new BE and reboot. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from 8.2 to 9.0
On 01/13/2012 02:42 PM, Dick Hoogendijk wrote: I possible I want my server to upgrade from 8.2-RELEASE to 9.0-RELEASE. I guess the binary upgrade will not be a problem with freebsd-update -r 9.0-RELEASE fetch If so, I do like to hear the caveats. My main problem lies with the installed ports. I know the -all- have to be recompiled, but I don't know an easy way for this job. I always use portmaster. Do I have to make a list manually for all installed ports? Or is there a procedure to follow in this matter? I'd like to get some pointers if possible. Thanks. _ It works great with source upgrade, so freebsd-update should not be a problem but i haven't used it yet to upgrade to 9. It is used like this: freebsd-update -r 9.0-RELEASE upgrade (i.e. not fetch) See also the handbook for a good explanation You can use portmaster --list-origins to make a list of all root and leaf ports and use this to reinstall all ports after the upgrade. See man portmaster for a good example. Or you can use portmaster -af to recompile all ports. Disclaimer: http://www.ose.nl/email ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from 8.2 to 9.0
On Fri, 13 Jan 2012 14:42:03 +0100, Dick Hoogendijk wrote: I possible I want my server to upgrade from 8.2-RELEASE to 9.0-RELEASE. I guess the binary upgrade will not be a problem with freebsd-update -r 9.0-RELEASE fetch If so, I do like to hear the caveats. Source update also shouldn't be a problem. Setup your CVS supfile to get the 9.0-RELEASE sources and follow the instructions in the handbook and in /usr/src/Makefile's comment header. My main problem lies with the installed ports. I know the -all- have to be recompiled, but I don't know an easy way for this job. Not have to, but it's often considered best practice. If you don't want to recompile all your ports, make sure two things are met: 1. You have COMPAT_FREEBSD8 in your kernel. 2. You have compat8x-i386-8.2.12345.67890 installed (or amd64 respectively). This will work as long as you're not starting to install something new (which may cause library version trouble). However, using a port management tool to do the job of update all ports is often highly recommended. I always use portmaster. Did you look into its manual already? :-) Do I have to make a list manually for all installed ports? Depends. A possible approach is that you make a list of your primary ports, i. e. the stuff that you are _really_ intending to use, where secondary ports they depend on (i. e. the dependencies) are not mentioned, as they will be installed anyway. So for example, if firefox is on your list as you intend to use it, there's no need to list all its dependencies as well because they are implicit. Or is there a procedure to follow in this matter? I'd like to get some pointers if possible. Sure. See man portmaster, section EXAMPLES, where you'll find Using portmaster to do a complete reinstallation of all your ports with a complete procedure. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from 8.2 to 9.0
Op 13-1-2012 14:56, Bas Smeelen schreef: On 01/13/2012 02:42 PM, Dick Hoogendijk wrote: I possible I want my server to upgrade from 8.2-RELEASE to 9.0-RELEASE. I guess the binary upgrade will not be a problem with freebsd-update -r 9.0-RELEASE fetch If so, I do like to hear the caveats. My main problem lies with the installed ports. I know the -all- have to be recompiled, but I don't know an easy way for this job. I always use portmaster. Do I have to make a list manually for all installed ports? Or is there a procedure to follow in this matter? I'd like to get some pointers if possible. Thanks. _ It works great with source upgrade, so freebsd-update should not be a problem but i haven't used it yet to upgrade to 9. It is used like this: freebsd-update -r 9.0-RELEASE upgrade (i.e. not fetch) See also the handbook for a good explanation You can use portmaster --list-origins to make a list of all root and leaf ports and use this to reinstall all ports after the upgrade. See man portmaster for a good example. Or you can use portmaster -af to recompile all ports. Ah, yes, I remember the latter is disadviced because some ports can have differences so you have some garbage if you run portmaster -af I will look up the example in the manual. It also will tell me (probably) if all ports have to be removed beforehand or that this does not matter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from 8.2 to 9.0
Hi, Am 13.01.2012 14:42, schrieb Dick Hoogendijk: I possible I want my server to upgrade from 8.2-RELEASE to 9.0-RELEASE. I guess the binary upgrade will not be a problem with freebsd-update -r 9.0-RELEASE fetch If so, I do like to hear the caveats. I did last week a source upgrade and the new generic kernel has not able to detected my hard disks anymore and therefor the system could not be booted, because the zfs file system was not mountable anymore. But if some users are reporting here good results, I maybe will try it again. Bye Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade/Change of ARCH
On 28/09/2011 21:17, Odhiambo Washington wrote: I have a 8.2-STABLE server which I am considering upgrading. I have a full backup on a disk so no worries about receovery. 1. I'd like to upgrade this server to 9.0-BETA3. What cvs tag should I use? Is *default release=cvs tag=. okay? No -- you want RELENG_9 for that. 2. Is it possible/safe to change ARCH? Like I'd like to change from i386 tp amd64. What is the procedure? i386 to amd64 is probably not impossible, but moving from one arch to another one by compiling source and upgrading is serious guru level stuff. Apart from anything else cross compiling to amd64 binaries on an i386 system is a potential source of grief. The best and surest way to change arch is to do a complete reinstall from scratch. Wipe out your i386 system and overwrite the space with amd64 from install media. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: upgrade of portupgrade to 2.4.9,2
On Sun, 21 Aug 2011 15:18:28 +0200 Andrea Venturoli m...@netfence.it mentioned: On 08/21/11 08:26, n dhert wrote: I did a portupgrade on a freebsd 8.2-RELEASE of the portupgrade program itself portupgrade-2.4.8_1,2needs updating (index has 2.4.9,2) (that upgraded also ruby to 1.9: I did the same on some boxes and I'm having a lot of troubles too... # pkgdb -L Look for lost dependencies: undefined method `map' for #String:0x0801e60218 Hi! Can you, please, try the portupgrade version from the ports? It should fix those issues. Sorry for the inconvinences! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments pgp0hdEIsQdvG.pgp Description: PGP signature
Re: upgrade of portupgrade to 2.4.9,2
On 08/23/11 09:58, Stanislav Sedov wrote: On Sun, 21 Aug 2011 15:18:28 +0200 Andrea Venturolim...@netfence.it mentioned: On 08/21/11 08:26, n dhert wrote: I did a portupgrade on a freebsd 8.2-RELEASE of the portupgrade program itself portupgrade-2.4.8_1,2 needs updating (index has 2.4.9,2) (that upgraded also ruby to 1.9: I did the same on some boxes and I'm having a lot of troubles too... # pkgdb -L Look for lost dependencies: undefined method `map' for #String:0x0801e60218 Hi! Can you, please, try the portupgrade version from the ports? It should fix those issues. Not really. I tried portupgrade -R portupgrade, but still had a messed-up system. Since I don't use Ruby for much and had only portupgrade and libchk using it, I wiped them all and reinstalled portupgrade from scratch. This also reinstalled ruby. I'm still getting undefined method `map'... when I run pkgdb, however. # pkg_info -r portupgrade\* Information for portupgrade-2.4.9.2,2: Depends on: Dependency: libyaml-0.1.4_1 Dependency: openssl-1.0.0_5 Dependency: pkg-config-0.25_1 Dependency: libffi-3.0.9 Dependency: ruby-1.9.2.290,1 Sorry for the inconvinences! You're welcome, I appreciate your work and help. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade of portupgrade to 2.4.9,2
On Tue, 23 Aug 2011 11:00:48 +0200 Andrea Venturoli m...@netfence.it mentioned: On 08/23/11 09:58, Stanislav Sedov wrote: On Sun, 21 Aug 2011 15:18:28 +0200 Andrea Venturolim...@netfence.it mentioned: On 08/21/11 08:26, n dhert wrote: I did a portupgrade on a freebsd 8.2-RELEASE of the portupgrade program itself portupgrade-2.4.8_1,2 needs updating (index has 2.4.9,2) (that upgraded also ruby to 1.9: I did the same on some boxes and I'm having a lot of troubles too... # pkgdb -L Look for lost dependencies: undefined method `map' for #String:0x0801e60218 Hi! Can you, please, try the portupgrade version from the ports? It should fix those issues. Not really. I tried portupgrade -R portupgrade, but still had a messed-up system. Since I don't use Ruby for much and had only portupgrade and libchk using it, I wiped them all and reinstalled portupgrade from scratch. This also reinstalled ruby. I'm still getting undefined method `map'... when I run pkgdb, however. Hi! Are you sure you have the latest one (2.4.9.2_2,2). If not, you can grab it from here: http://www.freebsd.org/cgi/cvsweb.cgi/ports/ports-mgmt/portupgrade/ (the page has a small download as a tarball link at the bottom). Let me know if it works! Thanks! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments pgpIFzfzVWD0P.pgp Description: PGP signature
Re: upgrade of portupgrade to 2.4.9,2
This ruby+portupgrade upgrade seems to be quite a mess. My systems fetch new ports tree nightly and I upgrade during the day when I have some spare time. So, this morning my systems had the new ruby versions and the UPDATING instruction, but not the new portupgrade port version (not that it had helped, but anyway). So, portupgrade -fr lang/ruby18 failed. Right now, I've got one system (the less critical one) upgraded with the latest and portupgrade is still failing. The other I backed down to ruby18 and portupgrade-2.4.8_1,2 and that works. Information from the upgraded system: # pkg_info -Ia | egrep 'ruby|portupgrade' portupgrade-2.4.9.2_2,2 FreeBSD ports/packages administration and management tool s ruby-1.9.2.290,1 An object-oriented interpreted scripting language ruby19-bdb-0.6.6 Ruby interface to Sleepycat's Berkeley DB revision 2 or lat Here's an example failure output. I get the same errors whatever port I try to upgrade.. # portupgrade -f portupgrade-2.4.9.2_2,2 --- Session started at: Tue, 23 Aug 2011 11:10:02 +0200 --- ** Upgrade tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed --- Listing the results (+:done / -:ignored / *:skipped / !:failed) ! ports-mgmt/portupgrade (portupgrade-2.4.9.2_2,2) (can't modify frozen string) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed --- Saving the results to '/var/log/portupgrade.results' ** Failed to save the results: undefined method `install_data' for # --- Session ended at: Tue, 23 Aug 2011 11:10:08 +0200 (consumed 00:00:05) Regards, Andréas On Tue, 23 Aug 2011 11:00:48 +0200, Andrea Venturoli wrote: On 08/23/11 09:58, Stanislav Sedov wrote: On Sun, 21 Aug 2011 15:18:28 +0200 Andrea Venturoli mentioned: On 08/21/11 08:26, n dhert wrote: I did a portupgrade on a freebsd 8.2-RELEASE of the portupgrade program itself portupgrade-2.4.8_1,2 needs updating (index has 2.4.9,2) (that upgraded also ruby to 1.9: I did the same on some boxes and I'm having a lot of troubles too... # pkgdb -L Look for lost dependencies: undefined method `map' for # Hi! Can you, please, try the portupgrade version from the ports? It should fix those issues. Not really. I tried portupgrade -R portupgrade, but still had a messed-up system. Since I don't use Ruby for much and had only portupgrade and libchk using it, I wiped them all and reinstalled portupgrade from scratch. This also reinstalled ruby. I'm still getting undefined method `map'... when I run pkgdb, however. # pkg_info -r portupgrade* Information for portupgrade-2.4.9.2,2: Depends on: Dependency: libyaml-0.1.4_1 Dependency: openssl-1.0.0_5 Dependency: pkg-config-0.25_1 Dependency: libffi-3.0.9 Dependency: ruby-1.9.2.290,1 Sorry for the inconvinences! You're welcome, I appreciate your work and help. bye Thanks av. ___ freebsd-questions@free freebsd.org/mailman/listinfo tions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org [2] Links: -- [1] mailto:m...@netfence.it [2] mailto:freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade of portupgrade to 2.4.9,2
On 08/23/11 11:11, Stanislav Sedov wrote: Are you sure you have the latest one (2.4.9.2_2,2). If not, you can grab it from here: http://www.freebsd.org/cgi/cvsweb.cgi/ports/ports-mgmt/portupgrade/ (the page has a small download as a tarball link at the bottom). You are right: I had just csupped, and saw a portupgrade update, but it was not _2. Probably it.cvsup.freebsd.org is a little behind :-) Let me know if it works! For pkgdb, so far, so fine. I'm still getting stack level too deep (see other post), but this is not on all boxes and I'm investigating it. Thanks a lot. bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade path from STABLE to RELEASE
On Friday 07 January 2011, Matthew Seaman wrote: Your choices are to backup and reinstall using a release version, or to grab the latest -STABLE or -RELEASE sources and upgrade by compiling from source. Note that last option still won't allow you to use freebsd-update subsequently: you have to stick with the binaries from the install media for that to work. This has got me puzzled. I appreciate that freebsd-update won't update the sources so an attempt to recompile after using freebsd-update to change between versions will lead to trouble unless the new sources are also downloaded but I'd assumed that freebsd-update would manage to update the binaries irrespective of whether they'd been installed as binary downloads or compiled locally. My present system started as 8.0-RELEASE, installed as a binary from DVD. I subsequently used csup to upgrade through 8.1-STABLE and 8.1-RELEASE. I've been using freebsd-update to keep 8.1-RELEASE up to date with the latest security patches. I didn't see any error messages when I ran freebsd-update so I assumed that everything went fine. Is there something I've overlooked and should I recompile from source to be safe? -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade path from STABLE to RELEASE
On 07/01/2011 11:14, Paul Macdonald wrote: I have a box which i installed 7.0 stable on and i want to do a binary update to 8.1 REL, is this possible via the freebsd-update utility? freebsd-update -r 8.1-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 4 mirrors found. Fetching public key from update5.FreeBSD.org... failed. Fetching public key from update4.FreeBSD.org... failed. Fetching public key from update2.FreeBSD.org... failed. Fetching public key from update3.FreeBSD.org... failed. No mirrors remaining, giving up. (Its only on stable that it fails, works fine). No. freebsd-update only works with -RELEASE branches, as you have discovered for yourself. Your choices are to backup and reinstall using a release version, or to grab the latest -STABLE or -RELEASE sources and upgrade by compiling from source. Note that last option still won't allow you to use freebsd-update subsequently: you have to stick with the binaries from the install media for that to work. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Upgrade from 7.x to 8.x
Forget the manual process. Use tested procedures: http://people.freebsd.org/~rse/upgrade/freebsd-upgrade-7x-8x.txthttp://people.freebsd.org/%7Erse/upgrade/freebsd-upgrade-7x-8x.txt I even used those procedures http://people.freebsd.org/%7Erse/upgrade/ to upgrade one system from 6.4 to 7.x and finally to 8.1. One thing you should note: *s/*compat7x-`uname -m`-7.2.702000.200906.1.tbz*/*compat7x-`uname -m`-7.3.703000.201008.tbz*/g* On Tue, Nov 23, 2010 at 1:04 PM, Uroš Gruber uros.gru...@gmail.com wrote: Hi, I was looking for help about this on forum, but a the moment without and luck. I would like to upgrade one of my servers from 7.2 release to 8.1 stable. I've done this on other servers and all went well. But with this one I can't get through. I'm testing all this in virtual machine where I transfer all data from real server. Here is my procedure 1. cd /usr/src 2. make update (using RELENG_8) 3. make cleanworld make cleandir 4. make buildworld 5. make buildkernel Through here everything works, but from now on I tried manny different steps but unfortunately I can't make it work. If I run make installkernel and reboot the server with single user a new kernel loads ok the only problem I have is that some of the programs don't actually work. For example awk /libexec/ld-elf.so.1: /lib/libm.so.5: version FBSD_1.0 required by /usr/bin/awk same problem is with ps, more etc. If I continue to run mergemaster and make installworld nothing really works, because installworld throws me a bunch of errors because some of the utilities needed does not work at all. So I tried other method. After make installworld I put server in single user mode without restarting (shutdown now). From there I can continue with 7. mergemaster -p 8. make installworld 9. make delete-old 10. make delete-old-lib 11. mergemaster Btw I tried reversing order of step 10 and 11 but it make no difference. Then I reboot the machine and first it looks I'll done my job well but right after it started complaining about the same thing as with awk but now with ps etc. and then crash with kldload process. The only thing that it works is single user mode. Because of all the problems with buildworld stuff i tried to use freebsd-update utility but this one failed even more. So I abandon this idea completely. I would appreciate some help to successfully upgrade this server. Fresh install is at the moment no option. Server is running 7.2 release with amd64 kernel. Best regards Uros ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade 6.4-stable to 7.3
Hi, I did a source upgrade on one box from 6.4 to 7.2 or 7.3 without any problems. I later did a source upgrade to 8.0 on the same machine just to find out that USB has some problems, I went then back to 7.3 on this machine. I also did some source upgrades from 7.x to 8.0 on some other machines without any problems. On Tuesday 27 July 2010 22:02:48 Michael Doyle wrote: In the past, I've usually done a wipe-and-reinstall when moving between major version numbers but I would rather avoid that this time around. I never did this since 5.2. The upgrades always worked for me. Also, would people recommend staying with version 7.3 or jumping all the way to version 8.1 ? I would first install 7.3, check if all works and then do a source upgrade. Save the source tree for 7.3 just for the case you have to go back. CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.11-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Not so new. Just like the machine which gave me the problem with 8.0. I never tried 8.1 on this machine. uhci0: UHCI (generic) USB controller port 0xcce0-0xccff irq 20 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Somewhere here were the problems. uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 You have Intel, I have NEC, so, you should not face the same problems I did. If they are not solved meanwhile. atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 Just one note. You are managing this machine remotely? No X on it? Take the two step approach and you should have a running system afterwards. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade 6.4-stable to 7.3
On 28 July 2010 11:47, Erich Dollansky erichfreebsdl...@ovitrap.com wrote: Hi, I did a source upgrade on one box from 6.4 to 7.2 or 7.3 without any problems. I later did a source upgrade to 8.0 on the same machine just to find out that USB has some problems, I went then back to 7.3 on this machine. I also did some source upgrades from 7.x to 8.0 on some other machines without any problems. On Tuesday 27 July 2010 22:02:48 Michael Doyle wrote: In the past, I've usually done a wipe-and-reinstall when moving between major version numbers but I would rather avoid that this time around. I never did this since 5.2. The upgrades always worked for me. the jump from 4-5 was funk if i remember, due to the rc structure changing completely and you would normally have wanted to take advantage of ufs2 Also, would people recommend staying with version 7.3 or jumping all the way to version 8.1 ? I would first install 7.3, check if all works and then do a source upgrade. Save the source tree for 7.3 just for the case you have to go back. CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.11-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Not so new. Just like the machine which gave me the problem with 8.0. I never tried 8.1 on this machine. uhci0: UHCI (generic) USB controller port 0xcce0-0xccff irq 20 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Somewhere here were the problems. uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 You have Intel, I have NEC, so, you should not face the same problems I did. If they are not solved meanwhile. atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 Just one note. You are managing this machine remotely? No X on it? Take the two step approach and you should have a running system afterwards. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade 6.4-stable to 7.3
On 28 Jul 2010, at 11:47, Erich Dollansky wrote: Just one note. You are managing this machine remotely? No X on it? Take the two step approach and you should have a running system afterwards. It's a mail server, no X but I do have physical access. Michael Doyle Network Administrator, Co-operation Ireland mdo...@cooperationireland.org http://www.cooperationireland.org/ Co-operation Ireland Events: http://www.cooperationireland.org/supportus/overview Phone: +353-1-6610588 Fax: +353-1-6618456 Mobile: 00353-87-2357853 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade 6.4-stable to 7.3
On Tue, Jul 27, 2010 at 03:02:48PM +0100, Michael Doyle wrote: I would like to upgrade a server that is currently running version 6.4 up to version 7.3 Having looked at /usr/src/UPDATING on a 7.3 machine, I don't see any major problems flagged. Given that I have console access to this machine, and I want to preserve the user directories (it's our mail server) would I be better off doing a source upgrade or a binary upgrade? Since you are running 6.4-STABLE, I think you will have to do a source upgrade. AFAIK binary upgrades are only supported when going from one -RELEASE to another (so 6.4-RELEASE to 7.3-RELEASE should be possible with a binary upgrade, 6.4-STABLE to 7.3-RELEASE would not.) In the past, I've usually done a wipe-and-reinstall when moving between major version numbers but I would rather avoid that this time around. Also, would people recommend staying with version 7.3 or jumping all the way to version 8.1 ? Unless you have some specific reason to use 7.3 you might as well go all the way up to 8.1. You should probably do it in two steps though - first from 6.4 to 7.3 and then from 7.3 to 8.1 Just remember to make good backups first, just in case something goes wrong. (There should not be any serious problems involved - the source upgrades I have done from 6.x to 7.x and later from 7.x to 8.x were fairly uneventful - but you never know what might happen.) -- Insert your favourite quote here. Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade 6.4-stable to 7.3
On 27 July 2010 16:13, Erik Trulsson ertr1...@student.uu.se wrote: On Tue, Jul 27, 2010 at 03:02:48PM +0100, Michael Doyle wrote: I would like to upgrade a server that is currently running version 6.4 up to version 7.3 Having looked at /usr/src/UPDATING on a 7.3 machine, I don't see any major problems flagged. Given that I have console access to this machine, and I want to preserve the user directories (it's our mail server) would I be better off doing a source upgrade or a binary upgrade? Since you are running 6.4-STABLE, I think you will have to do a source upgrade. AFAIK binary upgrades are only supported when going from one -RELEASE to another (so 6.4-RELEASE to 7.3-RELEASE should be possible with a binary upgrade, 6.4-STABLE to 7.3-RELEASE would not.) In the past, I've usually done a wipe-and-reinstall when moving between major version numbers but I would rather avoid that this time around. Also, would people recommend staying with version 7.3 or jumping all the way to version 8.1 ? Unless you have some specific reason to use 7.3 you might as well go all the way up to 8.1. You should probably do it in two steps though - first from 6.4 to 7.3 and then from 7.3 to 8.1 Just remember to make good backups first, just in case something goes wrong. (There should not be any serious problems involved - the source upgrades I have done from 6.x to 7.x and later from 7.x to 8.x were fairly uneventful - but you never know what might happen.) -- Insert your favourite quote here. Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I did a remote upgrade of our dns caches at work (24 boxes) from various 6.x builds. I did it all from source, and in two steps, once to 7-STABLE then once to 8-STABLE. It went fine in most cases. One thing i noticed though was some of the boxes were in dangerously dedicated disk layout. The dev tree in 6.x and 7.x had devices in the format of /dev/ad0a and /dev/ad0s1a. However 8.x only presented /dev/ad0a devices, like you would predict. Whoever origionally built the boxes had s1 type in the fstab which caught me out on a few of them. Not ideal on remote boxes. Other than that though the upgrades we nice and easy. Make sure you recompile all your ports though with something like portmaster. After you have done that do a make delete-old delete-old-libs and delete-old-dirs from usr/src, once your done to clean up the base distro. here's my mergemaster conf to speed things up a little if you aren't familier with it. Just make sure the ignore files is tailored to you then run mergemaster with no flags $ cat /etc/mergemaster.rc AUTO_INSTALL=YES AUTO_UPGRADE=YES PRESERVE_FILES=yes #IGNORE_FILES=/etc/rc.d/* PRESERVE_FILES_DIR=/var/mergemaster/preserved-files-`date +%y%m%d-%H%M%S` IGNORE_FILES=/etc/crontab /etc/fstab /etc/group /etc/hosts /etc/inetd.conf /etc/make.conf /etc/master.passwd /etc/motd /etc/newsyslog.conf /etc/ntp.conf /etc/ntp.drift /etc/profile /etc/rc.conf /etc/resolv.conf /etc/services /etc/shells /etc/syslog.conf /etc/ssh/sshd_config /etc/ssh/ssh_host_key /etc/ssh/ssh_host_key.pub /etc/ssh/ssh_host_rsa_key /etc/ssh/ssh_host_rsa_key.pub /etc/passwd /etc/rc.conf.local /etc/zfs/exports /etc//namedb/named.conf /etc/periodic.conf /etc/hosts.allow /etc/hosts /etc/pf.conf /etc/sysctl.conf /etc/make.conf /etc/src.conf /etc/mail/aliases /etc/mail/mailer.conf /etc/remote ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from FBSD from 8.0-release to stable-8
On 06/06/2010 4:37 μ.μ., Giorgos Tsiapaliokas wrote: hello, i have seach to net but i haven't find a way to update my system from 8.0-release to stable-8. can you tell me a way to do this? thanks in advance Since you are just starting with this, I would advise against it. Unless you know STABLE contains something you really need (i.e. a must have driver or fix for your particular hardware), I would say stay on RELEASE until you are more comfortable with your system. Going from RELEASE to STABLE involves recompiling the system from source. It is not really difficult, but it will save you a lot of trouble if you first get better acquainted with your system. If you would like to try it anyway, here are the instructions: http://www.freebsd.org/doc/el/books/handbook/current-stable.html (starting from 24.5.2) Since you are experimenting and don't have any data on the system, you may also wish to directly install one of the snapshots that will get you directly to a STABLE system. You can find snapshot ISOs here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201005/ or you may even wish to try 8.1-BETA1 which is also available in local mirrors (like otenet): ftp://ftp.otenet.gr/pub/FreeBSD/releases/i386/ISO-IMAGES/8.1/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from FBSD from 8.0-release to stable-8
On Sun 2010-06-06 13:37:58 UTC+, Giorgos Tsiapaliokas (terie...@gmail.com) wrote: i have seach to net but i haven't find a way to update my system from 8.0-release to stable-8. can you tell me a way to do this? My immediate thought was that if you can't work out how to update your system to FreeBSD-STABLE then you probably shouldn't be doing that. You should read the FreeBSD handbook then decide whether running STABLE is actually what you want to do. Particularly this page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html Most FreeBSD users install FreeBSD-RELEASE then use the freebsd-update command to either patch it with security updates or upgrade to a newer version of RELEASE. As far as I know you can't use freebsd-update to upgrade to/from STABLE, only RELEASE. Regards Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: upgrade from FBSD from 8.0-release to stable-8
On Sun, 6 Jun 2010 13:37:58 +, Giorgos Tsiapaliokas terie...@gmail.com wrote: hello, i have seach to net but i haven't find a way to update my system from 8.0-release to stable-8. can you tell me a way to do this? Basically, this process contains two main steps: fetching the sources, and compiling and installing the system. Step 1 can easily be done by using csup (it's in the base) with the following configuration: This into /etc/make.conf: SUP_UPDATE= yes SUP=/usr/bin/csup SUPFLAGS= -g -L 2 SUPHOST=cvsup.freebsd.org SUPFILE=/etc/sup/stable.sup This into /etc/sup/stable.sup: *default host=cvsup.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_8 *default delete use-rel-suffix *default compress src-all You can of course select a mirror near your location. The tag= parameter selects what you will get, e. g. a certain specifig RELEASE, patches for a RELEASE, STABLE, or even CURRENT. The keyword RELENG_8 will give you 8-STABLE. If you've updated your sorces, read /usr/src/UPDATING, and for the steps how to start, refer to /usr/src/Makefile. You can also add compiling options to /etc/make.conf to be involved here; a typical setting could be setting CPUTYPE. Then you start. # cd /usr/src # make buildworld buildkernel # make installkernel Then reboot into single user mode: # reboot ... Ok boot -s ... When arrived in single user mode, check your partitions via fsck, and then mount them (mount -a). # cd /usr/src # mergemaster -p # make installworld # make delete-old # mergemaster # reboot When you now have reached multi user mode again, finally do # cd /usr/src # make delete-old-libs Check the result via # uname -a If you do have a custom kernel, add KERNCONF=name to the make calls, e. g. # make buildkernel KERNCONF=FOOBAR or # make installkernel KERNCONF=FOOBAR respectively. Finally, see the excellent documentation in the FreeBSD Handbook. It should cover everything that hasn't been mentioned yet. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 19:10:32 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: After being advised to upgrade after a freebsd-update I have successfully upgraded from 7.2 to 8.0-p3. OK but have come across a major problem for me. OK time for a BIG rant this has been going on for 2 days (very sorry) After the install of the new kernel Samba isn't working. I TTL's onto the server and tried a testparm but the error messages suggest I have dependancies missing?! - surely this should be taken into account when upgrading versions - Major schoolboy error on FreeBSD when Linux can do this basic task seamlessly! When you upgraded from 7 to 8, you need to recompile your ports (or delete and re-install from packages). You can also install the 7 compatibility libraries. OK I try sysinstall and find SAMBA isn't marked as installed. The sysinstall program doesn't know what's installed. It's just a selection interface to the pkg_add program. I select samba for install but when installing SAMBA get a error code -1 (WTF is that all about REALLY USEFUL error message mate!) The sysinstall program can't tell you what's the problem. The pkg_add program probably exited with -1, and that's what sysinstall is informing you about. Looked on google and keeps referring to PORTS being installed. Tried the examples of how to install SAMBA but get loads of failed command line instructions - Doesn't say anything about installing PORTS during initial installation. At this moment, it would be useful if you could provide (1st) what command you entered and (2nd) what the system responded. Basically, in order to perform a major update of a system, you first update your ports tree (e. g. using portsnap), then you enter the port's directory in question and do make deinstall, followed by make reinstall. You can of course use programs like portmaster, portupgrade or portmanager to take care of this. For example, per- forming the upgrade of all installed applications, the command portupgrade -a can be used. I may repeat: Major version updates of the OS usually require the re-compilation of all installed ports. So I guess you can say I don't have Ports installed - why isn't this done automatically if its absolutely so critical for the OS to function right? In fact, it isn't. You can live without the ports collection. This collection is just a subtree /usr/ports that is usually installed together with the OS. You can use sysinstall to install the ports collection after the system has been installed, or you can use portsnap to obtain it. This subtree contains a hierarchy with files describing how to handle (configure, install, deinstall, upgrade) applications. It is meant to make compiling programs easier (no ./configure make make install), and there are programs interfacing with this system. If you don't want to use ports, use packages. This is usually done through sysinstall or pkg_add (see man pkg_add), as well as, for example, portinstall -PP samba (see man portupgrade) which will install sanba by utilizing the ports tree, but not by compiling - instead by getting the package. Error messages that mean nothing to the every day user. When you're dealing with ports and packages, you're not an every day user (in terms of average user). In such a case, you shouldn't even consider upgrading your system without reading the instructions telling you how to do it. I may politely point you at the excellent documentation provided for FreeBSD - The FreeBSD Handbook and the FAQ. Feel free to read more about OS and application upgrade there, and find out how easy it is as soon as you *know* what to do. Apparently I am meant to have something called PORTS installed before I've even setup the server. No. You don't need the ports collection, and you can install it whenever you want. Please read in the documentation what a port exactly is, and what a package is. Im really beginning to lose my rag with this OS. Is it meant for gurus only? No. So what am I meant to do now. Maybe first you bring your ports tree up to date, then install portupgrade, and finally do portupgrade -a. Before you do this, read man portupgrade, and maybe man ports. Now I have XXX GB of data I cant access though SAMBA prior to the install? I don't understand, sorry. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On 6/3/10, Andy Hiscock andyjhisc...@yahoo.com wrote: After being advised to upgrade after a freebsd-update I have successfully upgraded from 7.2 to 8.0-p3. OK but have come across a major problem for me. OK time for a BIG rant this has been going on for 2 days (very sorry) After the install of the new kernel Samba isn't working. I TTL's onto the server and tried a testparm but the error messages suggest I have dependancies missing?! - surely this should be taken into account when upgrading versions - Major schoolboy error on FreeBSD when Linux can do this basic task seamlessly! [snip rest of useless rant] Never come across this myself til now, but it seems there's a problem in ports that touches Samba. Probably related to your Samba install complaining. From a ports tree updated just a while ago: bash3-3.2.51 Dependency: gettext-0.17_1 gettext-0.17_1 Information for gettext-0.17_1: lynx-2.8.7.1_1,1 Dependency: gettext-0.18_1 mutt-devel-1.5.20_5 Dependency: gettext-0.18_1 popt-1.14_1 Dependency: gettext-0.18_1 samba34-3.4.5_1 Dependency: gettext-0.18_1 wget-1.12_1 Dependency: gettext-0.18_1 I guess it's a choice between bash working, or everything else working. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
Again Ports? What is that about... I've run the server and upgraded from 7.0-7,2 with no problem or need to change any config files before. Its upgraded with no problem before. How do I install Ports? How do I reinstall Samba without getting a error -1 in sysinstall? From: David Allen the.real.david.al...@gmail.com To: Andy Hiscock andyjhisc...@yahoo.com Cc: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:15:55 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED On 6/3/10, Andy Hiscock andyjhisc...@yahoo.com wrote: After being advised to upgrade after a freebsd-update I have successfully upgraded from 7.2 to 8.0-p3. OK but have come across a major problem for me. OK time for a BIG rant this has been going on for 2 days (very sorry) After the install of the new kernel Samba isn't working. I TTL's onto the server and tried a testparm but the error messages suggest I have dependancies missing?! - surely this should be taken into account when upgrading versions - Major schoolboy error on FreeBSD when Linux can do this basic task seamlessly! [snip rest of useless rant] Never come across this myself til now, but it seems there's a problem in ports that touches Samba. Probably related to your Samba install complaining. From a ports tree updated just a while ago: bash3-3.2.51 Dependency: gettext-0.17_1 gettext-0.17_1 Information for gettext-0.17_1: lynx-2.8.7.1_1,1 Dependency: gettext-0.18_1 mutt-devel-1.5.20_5 Dependency: gettext-0.18_1 popt-1.14_1 Dependency: gettext-0.18_1 samba34-3.4.5_1 Dependency: gettext-0.18_1 wget-1.12_1 Dependency: gettext-0.18_1 I guess it's a choice between bash working, or everything else working. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
Re-including the list... On Thu, 3 Jun 2010 20:14:03 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: Right how can I uninstall back to 7.2? Well... I have to admit that I've never done that. Basically, it should be possible if you install the sources of 7.2 (e. g. from the CD) to overwrite /usr/src. Then you basically do what the Handbook says about upgrading from source, or, to quote from /usr/src/Makefile (worth reading its beginning): # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster' (you may wish to use -U or -ai). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) This should then give you the 7.2 version of FreeBSD back - removing everything that freebsd-update might have updated. I am not sure if you can use freebsd-update for this task (but I don't see why it should not be possible); in this case, refer to man freebsd-update, especially the -r parameter (new release). Maybe a third possibility is to install FreeBSD 7.2 from the CD (I just assume you installed from CD or have the CD there), without any formatting, just overwriting. But this may be problematic - MAY, I'm not sure. Sorry, I'm really lacking experience in downgrading a system, as I have never done this, so I sadly can't be more specific. Maybe somebody on-list can be more precise (that's why I took the freedom to re-include the list, hope that's okay). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
Why during the upgrade process the inspecting system shouldnt be able to find and identify and prepair everything that needs to be upgraded and reconfigured accordingly. Surely thats what Inspecting system is meant to be doing. No matter if it is FreeBSD 1.0 or the prior version to the upgrade From: Andy Hiscock andyjhisc...@yahoo.com To: David Allen the.real.david.al...@gmail.com Cc: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:21:29 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Again Ports? What is that about... I've run the server and upgraded from 7.0-7,2 with no problem or need to change any config files before. Its upgraded with no problem before. How do I install Ports? How do I reinstall Samba without getting a error -1 in sysinstall? From: David Allen the.real.david.al...@gmail.com To: Andy Hiscock andyjhisc...@yahoo.com Cc: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:15:55 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED On 6/3/10, Andy Hiscock andyjhisc...@yahoo.com wrote: After being advised to upgrade after a freebsd-update I have successfully upgraded from 7.2 to 8.0-p3. OK but have come across a major problem for me. OK time for a BIG rant this has been going on for 2 days (very sorry) After the install of the new kernel Samba isn't working. I TTL's onto the server and tried a testparm but the error messages suggest I have dependancies missing?! - surely this should be taken into account when upgrading versions - Major schoolboy error on FreeBSD when Linux can do this basic task seamlessly! [snip rest of useless rant] Never come across this myself til now, but it seems there's a problem in ports that touches Samba. Probably related to your Samba install complaining. From a ports tree updated just a while ago: bash3-3.2.51 Dependency: gettext-0.17_1 gettext-0.17_1 Information for gettext-0.17_1: lynx-2.8.7.1_1,1 Dependency: gettext-0.18_1 mutt-devel-1.5.20_5 Dependency: gettext-0.18_1 popt-1.14_1 Dependency: gettext-0.18_1 samba34-3.4.5_1 Dependency: gettext-0.18_1 wget-1.12_1 Dependency: gettext-0.18_1 I guess it's a choice between bash working, or everything else working. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
ok so then running testparm i'm getting leopard# testparm /libexec/ld-elf.so.1: Shared object libcrypt.so.4 not found, required by testparm leopard# From: Polytropon free...@edvax.de To: Andy Hiscock andyjhisc...@yahoo.com Cc: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:27:33 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Re-including the list... On Thu, 3 Jun 2010 20:14:03 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: Right how can I uninstall back to 7.2? Well... I have to admit that I've never done that. Basically, it should be possible if you install the sources of 7.2 (e. g. from the CD) to overwrite /usr/src. Then you basically do what the Handbook says about upgrading from source, or, to quote from /usr/src/Makefile (worth reading its beginning): # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster' (you may wish to use -U or -ai). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) This should then give you the 7.2 version of FreeBSD back - removing everything that freebsd-update might have updated. I am not sure if you can use freebsd-update for this task (but I don't see why it should not be possible); in this case, refer to man freebsd-update, especially the -r parameter (new release). Maybe a third possibility is to install FreeBSD 7.2 from the CD (I just assume you installed from CD or have the CD there), without any formatting, just overwriting. But this may be problematic - MAY, I'm not sure. Sorry, I'm really lacking experience in downgrading a system, as I have never done this, so I sadly can't be more specific. Maybe somebody on-list can be more precise (that's why I took the freedom to re-include the list, hope that's okay). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
Anyone want to log on to my server and investigate/correct? From: Andy Hiscock andyjhisc...@yahoo.com To: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:29:28 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Why during the upgrade process the inspecting system shouldnt be able to find and identify and prepair everything that needs to be upgraded and reconfigured accordingly. Surely thats what Inspecting system is meant to be doing. No matter if it is FreeBSD 1.0 or the prior version to the upgrade From: Andy Hiscock andyjhisc...@yahoo.com To: David Allen the.real.david.al...@gmail.com Cc: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:21:29 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Again Ports? What is that about... I've run the server and upgraded from 7.0-7,2 with no problem or need to change any config files before. Its upgraded with no problem before. How do I install Ports? How do I reinstall Samba without getting a error -1 in sysinstall? From: David Allen the.real.david.al...@gmail.com To: Andy Hiscock andyjhisc...@yahoo.com Cc: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:15:55 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED On 6/3/10, Andy Hiscock andyjhisc...@yahoo.com wrote: After being advised to upgrade after a freebsd-update I have successfully upgraded from 7.2 to 8.0-p3. OK but have come across a major problem for me. OK time for a BIG rant this has been going on for 2 days (very sorry) After the install of the new kernel Samba isn't working. I TTL's onto the server and tried a testparm but the error messages suggest I have dependancies missing?! - surely this should be taken into account when upgrading versions - Major schoolboy error on FreeBSD when Linux can do this basic task seamlessly! [snip rest of useless rant] Never come across this myself til now, but it seems there's a problem in ports that touches Samba. Probably related to your Samba install complaining. From a ports tree updated just a while ago: bash3-3.2.51 Dependency: gettext-0.17_1 gettext-0.17_1 Information for gettext-0.17_1: lynx-2.8.7.1_1,1 Dependency: gettext-0.18_1 mutt-devel-1.5.20_5 Dependency: gettext-0.18_1 popt-1.14_1 Dependency: gettext-0.18_1 samba34-3.4.5_1 Dependency: gettext-0.18_1 wget-1.12_1 Dependency: gettext-0.18_1 I guess it's a choice between bash working, or everything else working. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
LOL - now stuck in and endless loop of: Message ─┐ │Unable to get packages/INDEX file from selected media. This is like a poorly written shareware app! Really getting pissd here! From: Andy Hiscock andyjhisc...@yahoo.com To: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:43:41 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Anyone want to log on to my server and investigate/correct? From: Andy Hiscock andyjhisc...@yahoo.com To: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:29:28 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Why during the upgrade process the inspecting system shouldnt be able to find and identify and prepair everything that needs to be upgraded and reconfigured accordingly. Surely thats what Inspecting system is meant to be doing. No matter if it is FreeBSD 1.0 or the prior version to the upgrade From: Andy Hiscock andyjhisc...@yahoo.com To: David Allen the.real.david.al...@gmail.com Cc: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:21:29 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Again Ports? What is that about... I've run the server and upgraded from 7.0-7,2 with no problem or need to change any config files before. Its upgraded with no problem before. How do I install Ports? How do I reinstall Samba without getting a error -1 in sysinstall? From: David Allen the.real.david.al...@gmail.com To: Andy Hiscock andyjhisc...@yahoo.com Cc: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:15:55 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED On 6/3/10, Andy Hiscock andyjhisc...@yahoo.com wrote: After being advised to upgrade after a freebsd-update I have successfully upgraded from 7.2 to 8.0-p3. OK but have come across a major problem for me. OK time for a BIG rant this has been going on for 2 days (very sorry) After the install of the new kernel Samba isn't working. I TTL's onto the server and tried a testparm but the error messages suggest I have dependancies missing?! - surely this should be taken into account when upgrading versions - Major schoolboy error on FreeBSD when Linux can do this basic task seamlessly! [snip rest of useless rant] Never come across this myself til now, but it seems there's a problem in ports that touches Samba. Probably related to your Samba install complaining. From a ports tree updated just a while ago: bash3-3.2.51 Dependency: gettext-0.17_1 gettext-0.17_1 Information for gettext-0.17_1: lynx-2.8.7.1_1,1 Dependency: gettext-0.18_1 mutt-devel-1.5.20_5 Dependency: gettext-0.18_1 popt-1.14_1 Dependency: gettext-0.18_1 samba34-3.4.5_1 Dependency: gettext-0.18_1 wget-1.12_1 Dependency: gettext-0.18_1 I guess it's a choice between bash working, or everything else working. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [#24536008] Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
Ah seems like FTP as well as Samba is blocked after the upgrade I have ran FreeBSD 7 to 7.2 using the freebsd upgrade process painless in the past, however.. Have followed the instructions for upgrade 7.2 to 8.0-P3 from the FreeBSD website. As I am not a FreeBSD guru all I can say is the update process is NOT a smooth process as per EVERY OTHER O/S in the open source market. I appreciate the support you have given but whatever you suggest just doesn't work. I am very angered being lead in to believing freebsd-update will be the able to update your OS - this isn't the case. Does FreeBSD want to be a fanatics only OS? No other OS's seems to have no such problems updating. I have even offered access to my server to sort out the problem but no one has offered. I just get cut/copy emails in reply that doesn't work. After 5 years of painless usage perhaps I ought to look at another better support OS? From: freebsd-questions@freebsd.org freebsd-questions@freebsd.org To: Andy Hiscock andyjhisc...@yahoo.com Sent: Thu, 3 June, 2010 22:02:05 Subject: [#24536008] Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Hello, This is an automated response to inform you that your question has been entered into our system, and will be reviewed shortly. Your ticket has been submitted into the General Support department. We will respond to you as soon as possible. == Please keep this information, and use it when refering to your ticket: Ticket subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Ticket number: 24536008 Ticket link: https://secure.mpcustomer.com/ticket.php?ticket=24536008 Ticket body: LOL - now stuck in and endless loop of: Message ─┐ │Unable to get packages/INDEX file from selected media. This is like a poorly written shareware app! Really getting pissd here! From: Andy Hiscock andyjhisc...@yahoo.com To: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:43:41 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Anyone want to log on to my server and investigate/correct? From: Andy Hiscock andyjhisc...@yahoo.com To: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:29:28 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Why during the upgrade process the inspecting system shouldnt be able to find and identify and prepair everything that needs to be upgraded and reconfigured accordingly. Surely thats what Inspecting system is meant to be doing. No matter if it is FreeBSD 1.0 or the prior version to the upgrade From: Andy Hiscock andyjhisc...@yahoo.com To: David Allen the.real.david.al...@gmail.com Cc: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:21:29 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED Again Ports? What is that about... I've run the server and upgraded from 7.0-7,2 with no problem or need to change any config files before. Its upgraded with no problem before. How do I install Ports? How do I reinstall Samba without getting a error -1 in sysinstall? From: David Allen the.real.david.al...@gmail.com To: Andy Hiscock andyjhisc...@yahoo.com Cc: freebsd-questions@freebsd.org Sent: Thu, 3 June, 2010 21:15:55 Subject: Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED On 6/3/10, Andy Hiscock andyjhisc...@yahoo.com wrote: After being advised to upgrade after a freebsd-update I have successfully upgraded from 7.2 to 8.0-p3. OK but have come across a major problem for me. OK time for a BIG rant this has been going on for 2 days (very sorry) After the install of the new kernel Samba isn't working. I TTL's onto the server and tried a testparm but the error messages suggest I have dependancies missing?! - surely this should be taken into account when upgrading versions - Major schoolboy error on FreeBSD when Linux can do this basic task seamlessly! [snip rest of useless rant] Never come across this myself til now, but it seems there's a problem in ports that touches Samba. Probably related to your Samba install complaining. From a ports tree updated just a while ago: bash3-3.2.51 Dependency: gettext-0.17_1 gettext-0.17_1 Information for gettext-0.17_1: lynx-2.8.7.1_1,1 Dependency: gettext-0.18_1 mutt-devel-1.5.20_5 Dependency: gettext-0.18_1 popt-1.14_1 Dependency: gettext-0.18_1 samba34-3.4.5_1 Dependency: gettext-0.18_1 wget-1.12_1 Dependency: gettext-0.18_1 I guess it's a choice between bash working, or everything else working. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 20:21:29 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: Again Ports? What is that about... I've run the server and upgraded from 7.0-7,2 with no problem or need to change any config files before. Its upgraded with no problem before. That's correct. Upgrading the base system usually doesn't require you to upgrade your applications as well. The freebsd-update binary updating program takes care of everything. How do I install Ports? The ports collection can be installed via sysinstall. Choose configure - distributions - ports. The /usr/ports subtree will then be installed. How do I reinstall Samba without getting a error -1 in sysinstall? You can first use pkg_delete to delete it, e. g. # pkg_delete -x samba and then re-install it from packages, e. g. # pkg_add -r samba See man pkg_add and man pkg_delete to make sure you're understanding that you're doing the right thing. I'm not sure if you need to explicitely add a version number for samba as I am not using it. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On 04/06/2010 12:01 π.μ., Andy Hiscock wrote: LOL - now stuck in and endless loop of: Message ─┐ │Unable to get packages/INDEX file from selected media. This is like a poorly written shareware app! Really getting pissd here! My guess is you need to do some reading first, it seems you are administering a system you don't quite understand. When doing a minor version upgrade (i.e. from 7.0 to 7.2) there is no need to touch anything in the extra programs you've installed (hint: those that come from packages or ports). Minor versions are binary compatible (few apps may need some attention but this is rare). When you do a major upgrade, you will be able to execute your 7.x installed apps on 8.x. But by the time you start installing programs to your new version, you will start replacing libraries of the 7.x system with new ones and the programs compiled for 7.x will stop functioning. My guess is you already installed some packages from the 8.0 media, so this has happened already. The recommended path for such an upgrade is to upgrade all your installed ports for your new system. Most people use ports (meaning they build the software on their own machine, it is quite straightforward and mostly automated) but it seems you are using packages. It should still be possible to do this. Please read the following section in the FreeBSD Handbook: http://www.freebsd.org/doc/en/books/handbook/updating-upgrading-freebsdupdate.html esp. 24.2.3 When upgrading from packages, change the command: portupgrade -af to portupgrade -af -PP which effectively means: Use packages only And yes, you will need a ports tree for portupgrade to work properly (although you won't be compiling anything). You don't need to keep it afterwords but it is handy to have and does not consume a lot of space. So get one: portsnap fetch extract And after finishing the upgrade, you can rm -rf /usr/ports if you don't want to keep it. You may wish to have a good read of the FreeBSD Handbook, esp. chapter 4 that deals with ports and packages. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 20:29:28 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: Why during the upgrade process the inspecting system shouldnt be able to find and identify and prepair everything that needs to be upgraded and reconfigured accordingly. Because this is the responsibility of the administrator - to decide WHAT to upgrade, WHY and WHEN, and even HOW. The base system tools (such as sysinstall, freebsd-upgrade) do not have any clue about what's going on in /usr/local. This subtree is reserved for installed applications (that do NOT belong to the base system). There are two files you should ALWAYS have a look at when performing an update: /usr/src/UPDATING /usr/ports/UPDATING They continue very important information for the person who does the administration for a particular system, e. g. it tells you that libxyz has gotten a major update and all applications linked to this library need to be recompiled. Surely thats what Inspecting system is meant to be doing. I could come up with hundreds of other ideas what Inspecting system could mean. :-) No matter if it is FreeBSD 1.0 or the prior version to the upgrade -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 20:33:49 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: # 1. `cd /usr/src' (or to the directory containing your source tree). Doesn't exist To install FreeBSD from source, you need to install the src distribution, or get the desired sources via CVS (csup). There are examples in /usr/share/examples/cvsup/ for this paritular task. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 20:38:22 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: ok so then running testparm i'm getting leopard# testparm /libexec/ld-elf.so.1: Shared object libcrypt.so.4 not found, required by testparm leopard# Seems like something failed during the update. Program version and major OS release don't match. This is a reason to install the compat- ports. For example, if you are on 7.2 and update to 8.0, your system will run, but most of your applications wouldn't. Installing misc/compat7x from ports (or via pkg_add -r compat7x as a package) will provide the libraries for compatibility to 7 on a 8 system. It's a good solution if you don't want to recompile / reinstall, but personally, I consider it a short-time solution. Of course, there can be settings where this is your only solution, e. g. if you have a binary that's compiled for 7, and you can not compile it for 8 (because there is no source code). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 21:01:25 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: LOL - now stuck in and endless loop of: Message ─┐ │Unable to get packages/INDEX file from selected media. Do you obtain data via network (up running checked?) or from CD? If you know which package to install - if you know its NAME - why bother with sysinstall? Simply use pkg_add -r name. This is like a poorly written shareware app! No, I think it's acting completely as intended and predictable. Maybe it's due to a partially failed upgrade process? Really getting pissd here! You lack patience, maybe knowledge, at least experience. :-) But that's no problem as long as you're willing to learn from the given sources and hints. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 21:38:42 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: Ah seems like FTP as well as Samba is blocked after the upgrade This explains the error message presented. If you want to install from FTP, but FTP can't reach anything, then... well... no INDEX for you. :-) I have ran FreeBSD 7 to 7.2 using the freebsd upgrade process painless in the past, however.. Have followed the instructions for upgrade 7.2 to 8.0-P3 from the FreeBSD website. As I am not a FreeBSD guru all I can say is the update process is NOT a smooth process as per EVERY OTHER O/S in the open source market. I have different experiences, but that doesn't matter here. :-) I appreciate the support you have given but whatever you suggest just doesn't work. Maybe because the conditions aren't meeting the requirements. I am very angered being lead in to believing freebsd-update will be the able to update your OS - this isn't the case. It IS the case. Keep in mind that FreeBSD differentiates between the OS (which is updated by freebsd-update) and installed appli- cations, or everything else, which is updated by the tools of your choice (make update, portmaster, portmanager, portupgrade). Check uname -r. Do you get a version number of the 8 branch? If yes - update has been performed correctly. Does FreeBSD want to be a fanatics only OS? I'm not sure what it wants, but I may say that I'm not a fanatic, but still using FreeBSD for many years nearly exclusively. No other OS's seems to have no such problems updating. I could show you some that have. :-) I have even offered access to my server to sort out the problem but no one has offered. Sorry, I don't think freebsd-questions@ is intended to fix your problems for you, keeping you from learning important skills in IT business. I just get cut/copy emails in reply that doesn't work. For my replies, I have no source where I do copy them from. I write them by myself; copied things are obviously marked as copied (e. g. some lines from /usr/src/Makefile). After 5 years of painless usage perhaps I ought to look at another better support OS? Maybe you should. But 5 years or painless usage should convince you that it may be worth to invest 5 hours to read, learn and repair. If I would be impolite, I would ask you why you don't use your backups to restore the has worked for 5 years state, but I know how annoying a malfunctioning system can be. Did you take the time to read man freebsd-update? I just did it, and found this: rollback Uninstall the most recently installed updates. (I copied this line from the manual page.) Did you try # freebsd-update rollback For safety, this should be done in single-user mode. I'm not sure if this really applies, but I'm a bit nervous anyway, so I do all dangerous stuff in SUM, under least-dangerous circumstances. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 22:02:44 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: leopard# pkg_delete -x samba pkg_delete: file '/usr/local/share/swat/js' doesn't exist pkg_delete: unable to completely remove directory '/usr/local/share/swat/js' pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) WARNING: If you will *NOT* use this package anymore, please remove the following directories manually: /usr/local/etc/samba /var/log/samba /var/db/samba That's okay. leopard# pkg_add -r samba Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.0-release/Latest/samba.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.0-release/Latest/samba.tbz' by URL Ah, I guess you need to specify a version number. There are different versions of Samba in the ports tree, so I think there are also different packages, e. g. try # pkg_add -r samba34 This should give you the latest version, 3.4. There's also 3, 3.2 and 3.3 available (same naming scheme for the package). Anyway, check if you can connect to (or just ping) ftp.freebsd.org to make sure - REALLY SURE - that a connection is possible. PS. Please try to avoid top-posting plus full quotes, or quoted replies, it makes the list unreadable. Thanks! -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 22:15:16 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: OK now I know... Why should I have to know this in the fist place? Hey, that's no problem - I also learned about this some time AFTER is has been common. :-) If Im just as User getting worrying messages about needing to upgrade. Where did those messages come from? FreeBSD 7.2 is still supported and no problem to run. I even know a setting where somebody is using a 4.0 server for internal backups. You should consider thinking about updating more intensively. There has just been a related discussion about this topic on this list. If I don't I am under the impression no security patches will be available? No. FreeBSD 7 (releases) still gets patches, allthough they are called legacy. Depending on what you're doing with your server, it may be wise to upgrade to 8 - or not - depends. The point I'm making to the end user, shouldn't a seamless update experience be achieved? :) Usually, it does - honestly; freebsd-update and portupgrade -af, and the show is running again. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 22:20:50 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: well surely if the upgrade IS going to affect ANY pre installed package that should be taken into consideration? - Im not having a dig, Im just suggesting how FreeBSD has fallen behind in the User Experience This depends on the users, not the OS. :-) Honestly: How are system upgrading tools supposed to know what's going on in the application area? There ARE tools to take care of that - freebsd-update is not one of them. Of course it takes knwoledge and experience to find out how to correctly perform an update of the operating system AND the installed software, but that's what you learn by using FreeBSD. I also did crash some of my systems by skipping the step think, but it's a great chance to learn, and if it's just how you dump restore. :-) BTW I got an error after the last message: leopard# pkg_add -r samba Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.0-release/Latest/samba.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.0-release/Latest/samba.tbz' by URL leopard# Have you tried adding a version number, e. g. samba34? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 22:29:28 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: I have sort of giving up and the cant be arsed Ill put windows on factor has stepped in. Have you considered entering single user mode and trying to get back to 7.2 (freebsd-update rollback)? In this case, you will need to re-install samba (you've removed it); but as you are already in 8, have you tried pkg_add -r samba43? I understand config files and DOS scripting but BSD is unsupported? Well, FreeBSD isn't DOS, nor is it Windows. It's a complex operating system (as all operating systems are a complex thing), and it needs more than knowledge about config files and scripts to maintain it properly and provide good administration. But finally, that's what you learn by using it. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 22:32:56 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: I assume the only other solution is download all the CDs of the latest FreeBSD. Do a clean install and replace the data? It's possible, but why reach for the big weapons in the first place? Did you (1) check FTP is up running, (2) run pkg_add -r samba34 or maybe (3) run freebsd-upüdate rollback in SUM? - This is not a clean upgrade admittedly! I think the OS has been upgraded properly. What does uname -r say? It would REALLY be helpful to see some output of the suggested commands. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 22:47:57 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: I stopped reading after the line freebsd-update is not one of them. You're missing the best parts. :-) I know its not your fault. But before progressing with technology perhaps support and support while upgrading is more important - especially when receiving alerts suggesting your version is no longer supported rather than failed installs being solved by people like yourself. FreeBSD has excellent support, in my opinion. The documentation is far better than most things I've seen in other open source projects. The mailing list is friendly and very helpful. Where did you get alerts from that FreeBSD 7 isn't supported anymore? Did you take the time to verify this? Allthough 7 is a legacy release, it's still FULLY supported, and many users are still using it. You've received many suggestions from this mailing list, but I fail to see that you're working with it. Without YOU, your actions, your activity, the problem won't go away. Of course, you can just copy your important data, then get the install CD for FreeBSD 8 (or maybe install it via net, which is very common), then install samba, and finally get your data back onto the system. But from my diagnostics (which are, in fact, mostly guessings, due to the lack of information from you, your performed commands and the respnses), I would not reach for such a big weapon at this moment. It's far easier to upgrade your applications (as your OS is already updated, just install the ports subtree as suggested by Giorgos Keramidas - portsnap fetch extract, then pkg_add -r portupgrade, and portupgrade -af -PP). This should give you a working Samba (as well as all other applications upgraded). Always keep in mind: Upgrading a system is something that you should do CAREFULLY. You can run into big trouble if you do it wrong (as I know from my own experience). FreeBSD is a system that does not tell you what you do and holds your hand while it does what it thinks is the best for you; instead, it does EXACTLY what you tell it to do. You can even take that literally. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 22:58:48 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: So am I lead to believe FreeBSD is mean to be a Mechanics Operating system? I say that in the nicest way. I wouldn't go that far, but FreeBSD, as well as repairing a car, requires certain knowledge and experience, I agree. We are not interested about the uneducated user. But PC-BSD is interested in them. :-) No, honestly, I don't want to insult PC-BSD. Maybe you should have a look at it: It's a FreeBSD based operating system and application bundle, just like a Linux distribution, and comes preconfigured with KDE and many tools aiming at users who are not able or do not want to know about their OS. It's an every day task system that perfectly fits Joe Q. Sixpack users. And I really mean this as a positive statement. You should really take a look at their website to see if this is what you want. By the way, PC-BSD is a good starting point for better BSD education, but nothing is better than building your own system from scratch. :-) or Leave the idiots to Windows/Mac or Linux point and click? Using a real operating system requires real knowledge. It is very important to understand that computers aren't easy, in contra- diction to what advertising wants people to believe. As updating my BSD version has been nothing but problems. Because you haven't fully performed it. To use a car analogy: You put a new motor in the car, but you didn't connect it with all the other parts inside the car, and you notice: Hey, I can't drive this damn car! :-) The transition from BSD 7 to 8 is equivalent to a windows service pack or Mac OS release, both which happen seamlessly. The transition from 7 to 8 involves more work than the transition within 7. I think Giorgos Keramidas explained this better than I did. Just imagine my fun when having to go from 5 to 7! I got 20 years older in one week. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 23:18:48 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: right scrolling to to top... Gonna go back to VHS here.. Do a clean install as far as i'm concerned freebsd-update only works for patches and not for OS upgrades from experiences or considering ubuntu who's updates works. The freebsd-update program REALLY WORKS for OS updates. It works for patches (i. e. staying within a certain release) and even across major releases (e. g. from 7.2 to 8.0). As I mentioned before: There's MORE you have to take care of. If your applications are made for a version 7 system, and you suddenly have a version 8 system, problems may occur, for example if a library is required that's not present anymore. Have to say after 2 years of using BSD am seriously disappointed with FreeBSD, every other OS perform a clean upgrade except I'm sad to hear that, as it contradicts my own experiences, and surely those of other FreeBSD users. There are users who update their OS and applications once a week, and others once a month; others perform the update when a new patchlevel is offered, and others do stay with the same system for years (install once, then use). How you handle things absolutely depends on your goals and requirements. As FreeBSD leaves you the freedom to decide what to do, YOU have to decide. That's what system administration basically is: Decisions lead by knowledge, experience and facts. With not support to fix online. As I said, the mailing list is not a free support center with support in terms of what you usually get when paying for a maintenance contract. But did YOU already try to fix it? You got so much suggestions of what to do and how. I'm missing your cooperation. It won't fix itself, sorry. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On Thu, 3 Jun 2010 23:19:28 + (GMT), Andy Hiscock andyjhisc...@yahoo.com wrote: enough sarcasm No sarcasm in here, just honest and fact-based statements (except those obviously signed by a smiley). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade/Install in one command?
On Wednesday 21 April 2010 18:06:23 Atom Powers wrote: I would like to make my configuration management system update and/or install packages on FreeBSD. I've been avoiding that little thorn because I haven't had very many hosts and updates have been fairly rare recently; but no more. (cfengine2) Basically, I wish pkg_add would upgrade a package if it was already installed; of that portupgrade would install a package if it was missing. Neither seem to work. How do you manage packages on a large number of FreeBSD hosts? I use portmaster, since it seems to mostly DTRT. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade/Install in one command?
Atom Powers atom.pow...@gmail.com writes: I would like to make my configuration management system update and/or install packages on FreeBSD. I've been avoiding that little thorn because I haven't had very many hosts and updates have been fairly rare recently; but no more. (cfengine2) Basically, I wish pkg_add would upgrade a package if it was already installed; of that portupgrade would install a package if it was missing. Neither seem to work. The '-N' option for portupgrade doesn't do what you want? How do you manage packages on a large number of FreeBSD hosts? I have a small number, but I still follow the build server approach... -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade error for fbsd-7.2 or 7.3
At 08:06 AM 4.17.2010 -0500, Jack L. Stone wrote: I hope someone can help me with this one. I've searched and nothing found yet. I 've been running fbsd-7.0p3 for quite a while just fine with 4 SATA drives always recognized as: ad8, ad10, ad12 and ad14 The boot drive is ad8 Upgraded to 7.1p11 and all still fine. However, when upgrading to 7.2 or 7.3, the system recognizes the drives differently as: ad6, ad8, ad10 and ad12 respectively in place of the normal ones above. Of course the system won't boot without telling it to mount ad6 instead of ad8 and then go into fstab and changing the letters. Plus, my jail no longer works although it was updated properly. Anyone with a similar problem or ideas? All the best, Jack OK, I get it. Will just change my FSTB to match the new HD numbers before first bootup after upgrade. Just was worried that soemthing else was wrong that I missed. Jail OK too now. Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade from i386-8.0 to amd64-8.0 possible?
On Fri, Jan 22, 2010 at 04:16:53PM -0600, LoH wrote: I've got a system currently running FreeBSD-i386-8.0, and was wondering whether or not it's possible to move the system to FreeBSD-amd64-8.0 without bringing it down for more than a reboot or two It is possible, but not recommended. First of all, you'll need a free (root) partition to install the new amd64 kernel and world into. And you need to rebuild not only the kernel, but the userland binaries (world) as well. (and avoid reinstalling all of the client software on the box itself). Realize that if you _ever_ want to update a port (which is still a i386 binary), those ports will be rebuilt as amd64 binaries, and linking (to libraries that are still i386) will fail. Likewise, is you update a library, all i386 binaries that depend on it will stop working because the library becomes amd64. Unless you copy the old library to a lib32 directory which you then have to tell ldconfig how to find. The box itself will be undergoing a hardware change from a dual xeon (P4, not 64bit) to a dual opteron. I think I can boot i386, set up a amd64 cross-compile, then compile a new kernel with it, or do a binary change to the new arch and then reboot. Do yourself a big favor. Back up your data, configuration files and a list of your ports, en delete all ports. Then install amd64 cleanly on the new machine. Restore your data. Re-build your ports from scratch, or install packages. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgprWwZxTp7Yx.pgp Description: PGP signature
Re: Upgrade from i386-8.0 to amd64-8.0 possible?
On Fri, 22 Jan 2010 16:16:53 -0600 LoH lordofhyph...@gmail.com wrote: I've got a system currently running FreeBSD-i386-8.0, and was wondering whether or not it's possible to move the system to FreeBSD-amd64-8.0 without bringing it down for more than a reboot or two (and avoid reinstalling all of the client software on the box itself). Just in case you're not aware of it, I find this site very useful: http://www.google.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade 7.0 to 7.2 installworld failed - SOLVED
On 25/12/2009 00:44, Mel Flynn wrote: Take the reboot out of the equation and keep it simple: su to root mkdir /usr/testdir cd /usr/src env -i make buildworld env -i make installworld DESTDIR=/usr/testdir Kernel has nothing to do with installworld target. Taking the reboot out of the equation with the normal process doesn't make a difference however using env -i doe thus it must be a setting. Can I safely rm /ust/testdir without anything breaking now? On 25/12/2009 06:36, Igor V. Ruzanov wrote: These things are for cvsup utility setup and they are not invoked to point on options responsible for specific system building. Try to add the following lines to /etc/make.conf: CFLAGS= -O -pipe NO_FORTRAN= true NO_OBJC=true NO_X= true NO_GAMES=true NO_PROFILE= true and re-make buildworld, then make installworld. When I run cvsup it uses a specific supfile anyway that has much the same settings, I think the ones in make.conf are there for one of my nightly port updating scripts. Adding the options you have mentioned to make.conf however made no difference to the installworld error. Thus I started playing I took out the following which make it work: #PERL_VERSION=5.8.9 #BATCH=YES #CRYPT_DES=0 #WITHOUT_ALT_CONFIG_PREFIX=YES Take your pick as to which one it was but I thought I'd post back so anyone else having the problem can look into it. Its a bit odd that moving make.conf aside didn't work though so there must be some other stuff in make.conf that is also required to prevent the problem.. Thanks for all the help folks! Now on to the ports... -- Regards, Colin Waring, +44 (0)1704 564047 Southport Computers Local IT Support http://www.southportcomputers.co.uk Southport Web Web Design and Hosting Services http://www.southportweb.co.uk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrade 7.0 to 7.2 installworld failed
On Thu, Dec 24, 2009 at 03:10:21PM +, Colin wrote: Hi folks, I have started trying to upgrade my 7.0 to 7.2 and it all seemed to be going well until I got to installworld. First off I did a cvsup for src-all from cvsup.ie.freebsd.org with the tag RELENG_7_2 I have then done: cd /usr/src make buildworld Are you sure that buildworld phase completed successfully? Have you tried cleaning /usr/obj/ before building world? Have you tried updating your src tree from different cvsup mirror (cvsup.freebsd.org, just to be sure)? make kernel-toolchain make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=TED make -DALWAYS_CHECK_MAKE installkernel KERNCONF=TED shutdown -r now mergemaster -p make installworld snip Thanks, Colin. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org