Re: A possibly odd upgrade question
On 05/20/2011 03:58 AM, Chris Brennan wrote: On Thu, May 19, 2011 at 5:04 PM, Polytropon free...@edvax.de wrote: Yes, the recommended order. :-) One last question ... hopefully lol. am I going to run into any issues w/ the default fbsd6 layout? [root@Ziggy [~]# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a496M328M128M72%/ devfs 1.0K1.0K 0B 100%/dev /dev/ad0s1e496M234K456M 0%/tmp /dev/ad0s1f 33G5.7G 25G19%/usr /dev/ad0s1d1.3G1.0G226M82%/var /dev/ad1s1d 54G8.9G 41G18%/usr/home /dev/ad6s1 74G 61G 13G82%/mnt/music linprocfs 4.0K4.0K 0B 100%/usr/compat/linux/proc [root@Ziggy [~]# What I think I failed to previously mention is that this machine started out with fbsd6.x, was upgraded many times from 6x though 7.1 where it fell into disuse. With my recent repurpose of this box ... I'm concerned that it might be a moot point if base won't fit on rot root slice. It can fit, however don't build the kernel with debug symbols and move or remove the current debug symbol files of your kernel. See below, our development box. It has GENERIC with debug symbol files, a kernel.old and a kernel without debug symbols on /boot which is on the / partition FreeBSD dev.ose.nl 7.4-RELEASE FreeBSD 7.4-RELEASE #0: Fri Mar 18 23:05:18 CET 2011 free...@dev.ose.nl:/usr/obj/usr/src/sys/DEV amd64 dev:/home/Freebee #df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/da0s1a496M295M162M65%/ devfs 1.0K1.0K 0B 100%/dev /dev/da0s1e7.7G642K7.1G 0%/tmp /dev/da0s1f135G 46G 78G37%/usr /dev/da0s1d7.7G1.1G6.0G16%/var -- Systeembeheerder OverNite Software Europe BV Dr. Nolenslaan 157 6136 GM Sittard THE NETHERLANDS phone: +31464200933 fax: +31464200934 web: http://www.ose.nl DISCLAIMER: This e-mail is for the intended recipient(s) only. Access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you have received it by mistake please let us know by reply and then delete it from your 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: A possibly odd upgrade question
On Thu, 19 May 2011 21:58:13 -0400, Chris Brennan xa...@xaerolimit.net wrote: One last question ... hopefully lol. am I going to run into any issues w/ the default fbsd6 layout? [root@Ziggy [~]# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a496M328M128M72%/ Maybe not so good (as a default) as soon as you're going to compile kernels for 8.x, where a / size of 1G would be better (although you can even get a FreeBSD / partition fully functional in 500 MB). The rest of the df output looks normal. What I think I failed to previously mention is that this machine started out with fbsd6.x, was upgraded many times from 6x though 7.1 where it fell into disuse. With my recent repurpose of this box ... I'm concerned that it might be a moot point if base won't fit on rot root slice. In this case, you should switch off all debugging for the kernel, and maybe even omit the backup kernel.OLD mechanism. But attention! This can be dangerous! Still you have the option to boot from a live system (Fixit should be enough) to manually make a backup copy of the running kernel, and in case anything fails at boot stage, use the live sytem to re-install the old kernel. But in fact, this should not be required. -- 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: A possibly odd upgrade question
On Fri, May 20, 2011 at 10:18 AM, Polytropon free...@edvax.de wrote: On Thu, 19 May 2011 21:58:13 -0400, Chris Brennan xa...@xaerolimit.net wrote: One last question ... hopefully lol. am I going to run into any issues w/ the default fbsd6 layout? [root@Ziggy [~]# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a496M328M128M72%/ Maybe not so good (as a default) as soon as you're going to compile kernels for 8.x, where a / size of 1G would be better (although you can even get a FreeBSD / partition fully functional in 500 MB). The rest of the df output looks normal. What I think I failed to previously mention is that this machine started out with fbsd6.x, was upgraded many times from 6x though 7.1 where it fell into disuse. With my recent repurpose of this box ... I'm concerned that it might be a moot point if base won't fit on rot root slice. In this case, you should switch off all debugging for the kernel, and maybe even omit the backup kernel.OLD mechanism. But attention! This can be dangerous! Still you have the option to boot from a live system (Fixit should be enough) to manually make a backup copy of the running kernel, and in case anything fails at boot stage, use the live sytem to re-install the old kernel. But in fact, this should not be required. OK, I am off now to research how to build the kernel w/o debugging symbols ... then I shall embark on this. -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? ___ 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: A possibly odd upgrade question
On Fri, 20 May 2011 12:09:43 +0200, Bas Smeelen b.smee...@ose.nl wrote: It can fit, however don't build the kernel with debug symbols and move or remove the current debug symbol files of your kernel. See below, our development box. It has GENERIC with debug symbol files, a kernel.old and a kernel without debug symbols on /boot which is on the / partition FreeBSD dev.ose.nl 7.4-RELEASE FreeBSD 7.4-RELEASE #0: Fri Mar 18 23:05:18 CET 2011 free...@dev.ose.nl:/usr/obj/usr/src/sys/DEV amd64 dev:/home/Freebee #df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/da0s1a496M295M162M65%/ Similar here, 7-STABLE (home desktop), system still contains default kernel and a backup, but without debugging info. % df -h / Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a496M336M120M74%/ % du -hs /boot/kernel* 30M/boot/kernel 112M/boot/kernel.GENERIC-7.0-RELEASE 29M/boot/kernel.RVS 29M/boot/kernel.old However, I think increasing the default size to 1GB for / would be a nice addition for the next release (at least for 9.0), or default sizes could be percentages of the available slice or disk space. -- 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: A possibly odd upgrade question
On Fri, 20 May 2011 10:26:01 -0400, Chris Brennan xa...@xaerolimit.net wrote: OK, I am off now to research how to build the kernel w/o debugging symbols ... then I shall embark on this. It should be makeoptions DEBUG=-g _NOT_ being present in the config file. Another idea would be to omit the backup of the old kernel. -- 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: A possibly odd upgrade question
On Fri, May 20, 2011 at 11:23 AM, Polytropon free...@edvax.de wrote: On Fri, 20 May 2011 10:26:01 -0400, Chris Brennan xa...@xaerolimit.net wrote: OK, I am off now to research how to build the kernel w/o debugging symbols ... then I shall embark on this. It should be makeoptions DEBUG=-g _NOT_ being present in the config file. Another idea would be to omit the backup of the old kernel. I will modify my kernel config to reflect that change and I was going to make a backup ... I'm using the same config from 7.x, only slightly modified to reflect this machine, that said, how do I clobber the current kernel and not back it up when I install the new one? -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? ___ 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: A possibly odd upgrade question
On Fri, 20 May 2011 11:36:37 -0400, Chris Brennan xa...@xaerolimit.net wrote: I will modify my kernel config to reflect that change and I was going to make a backup ... I'm using the same config from 7.x, only slightly modified to reflect this machine, that said, how do I clobber the current kernel and not back it up when I install the new one? I think / should have enough space for installing a new kernel without debugging symbols, I assume it will require 50 MB max, and if we assume that the current GENERIC kernel will be kept as a backup, you should be fine. Coming back to your initial partitioning data, Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a496M328M128M72%/ indicates that you have 128 MB free, so it should work. In case make installkernel will fail due to capacity reasons, you can easily switch back to the backup kernel, and maybe you find some stuff you can safely delete from the / partition (e. g. check /root). Also, read /usr/src/Makefile's comment header about the recommended procedure for updating the system. -- 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: A possibly odd upgrade question
On Fri, 20 May 2011, Polytropon wrote: However, I think increasing the default size to 1GB for / would be a nice addition for the next release That was recently implemented, maybe even for 8.2. It was in there the last time I ran sysinstall, anyway. 8-) ___ 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: A possibly odd upgrade question
On Wed, May 4, 2011 at 6:11 PM, Jerry je...@seibercom.net wrote: Yes, from the man pages it states it will rebuild all packages and their dependencies. I simply include the l so he would have a log file available if something did go wrong. In any case, I thought it might save him some trouble rebuilding his system. There are some ports; however, that will not build correctly unless the program is first removed from the system. Obviously not a friendly concept; however, a reality. The OP would have to remove them first I suppose before doing a force rebuild. Maybe just doing a pkg_delete -adv would be a better idea. Sorry it took me so long to get back to this e-mail, been busy w/ a bunch of stuff lately, but this box is still on my todo list. portupgrade/portmaster don't comeplete due to some bazaar issues that I no longer wish to try and fix. A recent development that I've discovered is that I can no longer compile anything, even as a user, it all just fails and it's one colossal headache I no longer want. If I go the way of pkg_delete -fravd, will it save configs in /usr/local/etc/ ? I just need to know if I need to take the extra step to archive that directory beforehand or not I'm just looking at possibilities of saving myself any other potential conf file reconfigurations in the future ... like I know I will need to reinstall samba and I would hate to loose that config and have to rewrite it... -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? ___ 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: A possibly odd upgrade question
On Thu, 19 May 2011 16:29:41 -0400, Chris Brennan xa...@xaerolimit.net wrote: If I go the way of pkg_delete -fravd, will it save configs in /usr/local/etc/ ? I just need to know if I need to take the extra step to archive that directory beforehand or not I would advice to do so, no matter what the pkg_delete command will cause. If I remember correctly, MODYFIED files will not be touched (checksum test), and a directory won't be removed if it contains something that won't be deleted according to the initial packing list. So if anything unexpected happens - you can consult your before configuration files to change the after ones, or simply re-use them if possible. -- 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: A possibly odd upgrade question
On Thu, May 19, 2011 at 4:40 PM, Polytropon free...@edvax.de wrote: I would advice to do so, no matter what the pkg_delete command will cause. If I remember correctly, MODYFIED files will not be touched (checksum test), and a directory won't be removed if it contains something that won't be deleted according to the initial packing list. So if anything unexpected happens - you can consult your before configuration files to change the after ones, or simply re-use them if possible. Thanks for getting back to me so quick on this :D. That was pretty much what I needed to know, so I shall embark on this shortly. After much thought, I think my process would be this: chsh back to bin/sh (I currently use bash as my primary shell) logout back in for shell change pkg_delete -fravd get new base srcs portsnap (re)install desired tools (vim mostly, although I can function in vi) rebuild world/kernel for new version rebuild new tools for new libs am I forgetting something? -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? ___ 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: A possibly odd upgrade question
On Thu, 19 May 2011 16:47:26 -0400, Chris Brennan xa...@xaerolimit.net wrote: After much thought, I think my process would be this: chsh back to bin/sh (I currently use bash as my primary shell) logout back in for shell change pkg_delete -fravd get new base srcs portsnap (re)install desired tools (vim mostly, although I can function in vi) rebuild world/kernel for new version rebuild new tools for new libs am I forgetting something? Yes, the recommended order. :-) First, update your ports/ and src/ trees (e. g. using portsnap and csup), then compile and install. You don't need any tools provided by ports for this task. After you've started your new system, install the additional software you need. Mentioning the shell was good: In case you remove bash from the system, it may cause trouble when a shell is requested for a user that is not there (the shell), as bash is not part of the base system. Still it seems that you'll do most of the work mentioned in the above paragraph as root, you will use root's default shell (which is csh) anyway. -- 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: A possibly odd upgrade question
On Thu, May 19, 2011 at 5:04 PM, Polytropon free...@edvax.de wrote: Yes, the recommended order. :-) First, update your ports/ and src/ trees (e. g. using portsnap and csup), then compile and install. You don't need any tools provided by ports for this task. After you've started your new system, install the additional software you need. Mentioning the shell was good: In case you remove bash from the system, it may cause trouble when a shell is requested for a user that is not there (the shell), as bash is not part of the base system. Still it seems that you'll do most of the work mentioned in the above paragraph as root, you will use root's default shell (which is csh) anyway. One last question ... hopefully lol. am I going to run into any issues w/ the default fbsd6 layout? [root@Ziggy [~]# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a496M328M128M72%/ devfs 1.0K1.0K 0B 100%/dev /dev/ad0s1e496M234K456M 0%/tmp /dev/ad0s1f 33G5.7G 25G19%/usr /dev/ad0s1d1.3G1.0G226M82%/var /dev/ad1s1d 54G8.9G 41G18%/usr/home /dev/ad6s1 74G 61G 13G82%/mnt/music linprocfs 4.0K4.0K 0B 100%/usr/compat/linux/proc [root@Ziggy [~]# What I think I failed to previously mention is that this machine started out with fbsd6.x, was upgraded many times from 6x though 7.1 where it fell into disuse. With my recent repurpose of this box ... I'm concerned that it might be a moot point if base won't fit on rot root slice. -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? ___ 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: A possibly odd upgrade question
On Wed 2011-05-04 12:50:05 UTC-0400, Chris Brennan (xa...@xaerolimit.net) wrote: I have an old PIII running FreeBSD7.3 currently, ports is all kinds of screwed up, when I did my first cross-version upgrade from 6.x to 7.x, I didn't know I had to rebuild ports, I subsequently upgrades though every version upto to 7.3. Ports is still FUBAR, half of them no longer work. So my question is this, now I know for the future to upgrade ports after every upgrade, is it safe to nuke /usr/local (excluding /usr/local/home), rebuild world/kernel for 8.2 and start with a fresh ports tree? You only need to rebuild all your ports after a major FreeBSD upgrade, eg. 6.x to 7.x, or 7.x to 8.x. Deleting /usr/local is a bit of an extreme step. You can run pkg_delete -av to delete all installed ports. Starting with a fresh ports tree is probably only necessary if your ports tree is very out of date. Only because if it's stale it could take longer to update it with portsnap than to start the tree from scratch. Of course deleting an existing ports tree can also take a while, too. You shouldn't need to build world kernel for 8.2 unless you need a custom kernel or something else peculiar to your setup. I have no way of knowing, but I suspect most FreeBSD users just use freebsd-update these days to install the premade binaries of world kernel. I thought about a clean reinstall but this machine cannot boot from USB, both CD-ROM's are dead and have been disconnected to use IDE hard-drives and the floppy driver is dead as well. You could put the boot HDD into another machine with a working CD-ROM, install it onto that, then put the HDD back into the P3 when you're done. There's no requirement that the installation needs to be done on the same machine it's going to ultimately boot from. Do you actually need to upgrade to 8.x? I'm not sure there's much to gain from putting 8.x on an old P3... 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: A possibly odd upgrade question
On Wed, 4 May 2011 12:50:05 -0400 Chris Brennan xa...@xaerolimit.net articulated: I have an old PIII running FreeBSD7.3 currently, ports is all kinds of screwed up, when I did my first cross-version upgrade from 6.x to 7.x, I didn't know I had to rebuild ports, I subsequently upgrades though every version upto to 7.3. Ports is still FUBAR, half of them no longer work. So my question is this, now I know for the future to upgrade ports after every upgrade, is it safe to nuke /usr/local (excluding /usr/local/home), rebuild world/kernel for 8.2 and start with a fresh ports tree? I thought about a clean reinstall but this machine cannot boot from USB, both CD-ROM's are dead and have been disconnected to use IDE hard-drives and the floppy driver is dead as well. So it would seem an inline/online rebuild is my only upgrade solution but with ports in it's current state of FUBAR, it leaves me with the question of what to do with that too. P.S. I've tried a portmaster/portsupgrade of ports, both met with disastrous results and with 193 current ports installed, over 75% of which is broke and isn't used any more ... I need to start over Chris, when I have had to do major rebuilds, I have found portmanager to be the best tool. It just seems to work. In any case, if it were me, I would clean out the /usr/ports/distfiles directory, update your ports tree, and then update you OS. When you are finished with that fun chore, run; portmanager -u -l -y -f. Depending on the number of ports installed, it might take some time though. Obviously, you need portmanager installed first. By the way, if you know you need a distfile installed first, something like diablo-jdk or diablo-jre that require you to have the distfile all ready in the /usr/ports/distfiles directory prior to attempting to build the port, then do that prior to updating your system and running portmanager. -- Jerry ✌ jerry+f...@seibercom.net Disclaimer: off-list followups get on-list replies, ignored or reported as Spam. Do not CC this poster. 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: A possibly odd upgrade question
On 4 May 2011 12:50, Chris Brennan xa...@xaerolimit.net wrote: is it safe to nuke /usr/local (excluding /usr/local/home), rebuild world/kernel for 8.2 and start with a fresh ports tree? Yes, though pkg_delete -af will probably suffice for removing the ports ( /var/db/pkg/ as well). -- -- ___ 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: A possibly odd upgrade question
On Wed, May 4, 2011 at 2:26 PM, Jerry je...@seibercom.net wrote: Chris, when I have had to do major rebuilds, I have found portmanager to be the best tool. It just seems to work. In any case, if it were me, I would clean out the /usr/ports/distfiles directory, update your ports tree, and then update you OS. When you are finished with that fun chore, run; portmanager -u -l -y -f. Depending on the number of ports installed, it might take some time though. Obviously, you need portmanager installed first. By the way, if you know you need a distfile installed first, something like diablo-jdk or diablo-jre that require you to have the distfile all ready in the /usr/ports/distfiles directory prior to attempting to build the port, then do that prior to updating your system and running portmanager. The problem here (as I have previously mentioned and further discussed in my reply to Andrew Clarke) is that the most of the ports won't rebuild for various reasons. I'm pretty handy, but not brilliant. So instead of asking for my hand to be held by the mailing list, I thought nuking everything I installed from ports after moving to 8.x would be the smartest move, then from there reinstall (from a fresh ports tree) only what I need for the retasked purpose. ___ 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: A possibly odd upgrade question
On Wed, May 4, 2011 at 2:40 PM, ill...@gmail.com ill...@gmail.com wrote: On 4 May 2011 12:50, Chris Brennan xa...@xaerolimit.net wrote: is it safe to nuke /usr/local (excluding /usr/local/home), rebuild world/kernel for 8.2 and start with a fresh ports tree? Yes, though pkg_delete -af will probably suffice for removing the ports ( /var/db/pkg/ as well). Someone else suggested 'pkg_delete -av' ... would -avf then be a safe assumption? I want to make sure I have a solid leg to stand on before I start anything... ___ 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: A possibly odd upgrade question
On 4 May 2011 15:54, Chris Brennan xa...@xaerolimit.net wrote: On Wed, May 4, 2011 at 2:40 PM, ill...@gmail.com ill...@gmail.com wrote: On 4 May 2011 12:50, Chris Brennan xa...@xaerolimit.net wrote: is it safe to nuke /usr/local (excluding /usr/local/home), rebuild world/kernel for 8.2 and start with a fresh ports tree? Yes, though pkg_delete -af will probably suffice for removing the ports ( /var/db/pkg/ as well). Someone else suggested 'pkg_delete -av' ... would -avf then be a safe assumption? I want to make sure I have a solid leg to stand on before I start anything... -v is just for verbose. I honestly don't know if the -f makes a difference with -a either. Probably not. -- -- ___ 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: A possibly odd upgrade question
On 04/05/2011 20:53, Chris Brennan wrote: On Wed, May 4, 2011 at 2:26 PM, Jerryje...@seibercom.net wrote: Chris, when I have had to do major rebuilds, I have found portmanager to be the best tool. It just seems to work. In any case, if it were me, I would clean out the /usr/ports/distfiles directory, update your ports tree, and then update you OS. When you are finished with that fun chore, run; portmanager -u -l -y -f. Depending on the number of ports installed, it might take some time though. Obviously, you need portmanager installed first. By the way, if you know you need a distfile installed first, something like diablo-jdk or diablo-jre that require you to have the distfile all ready in the /usr/ports/distfiles directory prior to attempting to build the port, then do that prior to updating your system and running portmanager. The problem here (as I have previously mentioned and further discussed in my reply to Andrew Clarke) is that the most of the ports won't rebuild for various reasons. I'm pretty handy, but not brilliant. So instead of asking for my hand to be held by the mailing list, I thought nuking everything I installed from ports after moving to 8.x would be the smartest move, then from there reinstall (from a fresh ports tree) only what I need for the retasked purpose. ___ 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 second Jerry, portmanager is indeed a very effective tool, it's simple and thorough and probably has as good a chance of fixing ports issues as anything. Or used to, I've been trying out tinderbox so haven't used it for a year or so. If you do use portmanager there are a few tricks you can do to make it effectively unattended. However, doesn't -u -f mean rebuild all dependencies of all ports? In which case wouldn't it be just as effective and cleaner for the OP to nuke the lot and rebuild, particularly in view of the retasked purpose. Chris ___ 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: A possibly odd upgrade question
On Wed, 04 May 2011 22:51:05 +0100 Chris Whitehouse cwhi...@onetel.com articulated: I second Jerry, portmanager is indeed a very effective tool, it's simple and thorough and probably has as good a chance of fixing ports issues as anything. Or used to, I've been trying out tinderbox so haven't used it for a year or so. If you do use portmanager there are a few tricks you can do to make it effectively unattended. However, doesn't -u -f mean rebuild all dependencies of all ports? In which case wouldn't it be just as effective and cleaner for the OP to nuke the lot and rebuild, particularly in view of the retasked purpose. Yes, from the man pages it states it will rebuild all packages and their dependencies. I simply include the l so he would have a log file available if something did go wrong. In any case, I thought it might save him some trouble rebuilding his system. There are some ports; however, that will not build correctly unless the program is first removed from the system. Obviously not a friendly concept; however, a reality. The OP would have to remove them first I suppose before doing a force rebuild. Maybe just doing a pkg_delete -adv would be a better idea. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies, ignored or reported as Spam. Do not CC this poster. Please do not ignore the Reply-To header. __ Getting the job done is no excuse for not following the rules. Corollary: Following the rules will not get the job done. ___ 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
