Re: freebsd-update question.
On Thu, 23 Aug 2012 11:36:51 -0400 (EDT), d...@safeport.com wrote: I wanted to see if I could get an 8.1 system updated to 9.0 (mostly) with freebsd-update. I did this with a source update to RELENG_8_3 and then did the standard stuff to get to 9.0 perl and xdm both gave errors that libutil.so.9 was missing. scanning google and questions suggested this module was removed. Also in some basic way the ports make scripts view the system as an 8.X system as make index gives 'Generating INDEX-8 - please wait.. Can this be repaired? Building from source is out of the question for this system. After a major version update (8.x - 9.x) you should reinstall _all_ ports. See man portmaster (EXAMPLES section) for suggestions on how to do this. If you want to avoid it. you can install the compat8x port on your system. Unaltered (!) installs from 8.x should continue running. But as soon as you're introducing new software, trouble may occur. In that case, a clean install of your applications should be the better way. (Note that you can do this either by source or by packages, just as you prefer.) The described problem with libutil can be avoided when working with the compat8x port. There are more such ports for older versions that allow running binaries compiled for those OS versions (API/ABI remapping). -- 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: freebsd-update question.
On Thu, 23 Aug 2012, Polytropon wrote: On Thu, 23 Aug 2012 11:36:51 -0400 (EDT), d...@safeport.com wrote: I wanted to see if I could get an 8.1 system updated to 9.0 (mostly) with freebsd-update. I did this with a source update to RELENG_8_3 and then did the standard stuff to get to 9.0 perl and xdm both gave errors that libutil.so.9 was missing. scanning google and questions suggested this module was removed. Also in some basic way the ports make scripts view the system as an 8.X system as make index gives 'Generating INDEX-8 - please wait.. Can this be repaired? Building from source is out of the question for this system. After a major version update (8.x - 9.x) you should reinstall _all_ ports. See man portmaster (EXAMPLES section) for suggestions on how to do this. If you want to avoid it. you can install the compat8x port on your system. Unaltered (!) installs from 8.x should continue running. But as soon as you're introducing new software, trouble may occur. In that case, a clean install of your applications should be the better way. (Note that you can do this either by source or by packages, just as you prefer.) The described problem with libutil can be avoided when working with the compat8x port. There are more such ports for older versions that allow running binaries compiled for those OS versions (API/ABI remapping). After seeing if xorg and twm would just work, I did remove all packages with pkg_delete. That did not clear out all of /usr/local. When pkg_add of perl failed, I just built that. pkg_add of xorg worked. pkg_add of xdm got an error something along the line of unliking lib/X11/auth... so I deleted that dir and did pkg_add again. This installed but xdm fails on execution with libutil.so.9 missing. monhegan:~ uname -a FreeBSD monhegan.boltsys.com 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 01:47:53 UTC 2012 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 But make index thinks (I think) this is an 8.x system. pkg_add did add from ...lastest..9.0 for xorg and xdm. AFAIK there are no 8.x components. ___ 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: freebsd-update question.
On Thu, 23 Aug 2012 13:49:18 -0400 (EDT), d...@safeport.com wrote: After seeing if xorg and twm would just work, I did remove all packages with pkg_delete. That did not clear out all of /usr/local. You can do a manual cleanup of /usr/local, entirely removing it and then reconstructing its structure from the /etc/mtree file. # cd /usr/local # rm -rf * # mtree -f /etc/mtree/BSD.local.dist # mtree -f /etc/mtree/BSD.x11.dist (Not tested, see the manpage for reference.) That should give you a clean environment for a full re-installation. Also note that /var/db/pkg could be manually deleted in this case. When pkg_add of perl failed, I just built that. pkg_add of xorg worked. pkg_add of xdm got an error something along the line of unliking lib/X11/auth... so I deleted that dir and did pkg_add again. This installed but xdm fails on execution with libutil.so.9 missing. Seems that there are complications with leftover stuff in /usr/local. monhegan:~ uname -a FreeBSD monhegan.boltsys.com 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 01:47:53 UTC 2012 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 But make index thinks (I think) this is an 8.x system. pkg_add did add from ...lastest..9.0 for xorg and xdm. AFAIK there are no 8.x components. You could install the ports tree from a 9.0 installation media or simply use CVS to obtain (or at least update) 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: freebsd-update question
On 09/09/2010 19:40:19, Murray S. Kucherawy wrote: I'm reading http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html in preparation for an update of a 6.2-RELEASE machine in a colocation faciilty. However, that page says 6.3 or later is needed to do it via the freebsd-update(8) mechanism. Are there any references for using freebsd-update for a 6.2 installation, or am I looking at doing the update from source as per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html? Yes. 6.2 is long out of support, so you will need to use the makeworld route to get to something more recent. 6.4 is just about to go out of support -- you should be able to buildworld to that version, and then use freebsd-update to get to something up to date. Or just use the buildworld route to get to the latest (it takes some time for all the compilation but works reliably) -- you might be able to get to 8.1 in one step, but I think that's probably unlikely. You should always be able to update from the latest version on any major branch to any version on the next branch, so 6.2 - 6.4 - 7.3 - 8.1 should work. You will need to rebuild all your ports for a major version upgrade, although (if it isn't obvious) if you're going to go up two major versions, you only need to rebuild all the ports once at the end of the process of updating the system. 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: freebsd-update question
--- On Thu, 9/9/10, Murray S. Kucherawy m...@blackops.org wrote: From: Murray S. Kucherawy m...@blackops.org Subject: freebsd-update question To: questi...@freebsd.org Date: Thursday, September 9, 2010, 1:40 PM Hi, I'm reading http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html in preparation for an update of a 6.2-RELEASE machine in a colocation faciilty. However, that page says 6.3 or later is needed to do it via the freebsd-update(8) mechanism. Are there any references for using freebsd-update for a 6.2 installation, or am I looking at doing the update from source as per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html? Thanks, -MSK ___ 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 Depending on how the computer is used, to bring it up to 8.1 I'd backup data, config files, make a list of installed software and do a reinstall. The time it takes to build world, merg files and rebuild software a fresh install may be quicker than to try the jump from 6.2 to 8.1. YMMV ___ 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: Freebsd-update question
Hi Richard, On Sat, Aug 8, 2009 at 10:16 AM, Richard Mahlerweinmahle...@yahoo.com wrote: I thought I'd give freebsd-update a try since I run a GENERIC kernel. mobius# freebsd-update -s update.freebsd.org fetch Looking up update.freebsd.org mirrors... none found. Fetching public key from update.freebsd.org... failed. No mirrors remaining, giving up. Thinking perhaps a networking issue, I checked the machine is accessible... mobius# ping update.freebsd.org PING update1.FreeBSD.org (72.21.59.252): 56 data bytes 64 bytes from 72.21.59.252: icmp_seq=0 ttl=51 time=64.557 ms 64 bytes from 72.21.59.252: icmp_seq=1 ttl=51 time=64.580 ms ^C --- update1.FreeBSD.org ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 64.557/64.569/64.580/0.012 ms It responds with update1, so I tried again using update1.freebsd.org (and several others that I could ping) but it always gives me the same response. A quick check of the handbook and the man pages for both freebsd-update(5) and freebsd-update.conf(8) didn't tell me much about this. I'm sure it's something stupidly simple. Does anyone have some ideas? There's quite a bit of useful information missing. For starters, what is the output of 'uname -a'? -- Glen Barber ___ 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: Freebsd-update question
--- On Sat, 8/8/09, Glen Barber glen.j.bar...@gmail.com wrote: From: Glen Barber glen.j.bar...@gmail.com Subject: Re: Freebsd-update question To: mahle...@yahoo.com Cc: freebsd-questions@freebsd.org Date: Saturday, August 8, 2009, 10:20 AM Hi Richard, On Sat, Aug 8, 2009 at 10:16 AM, Richard Mahlerweinmahle...@yahoo.com wrote: I thought I'd give freebsd-update a try since I run a GENERIC kernel. mobius# freebsd-update -s update.freebsd.org fetch Looking up update.freebsd.org mirrors... none found. Fetching public key from update.freebsd.org... failed. No mirrors remaining, giving up. Thinking perhaps a networking issue, I checked the machine is accessible... mobius# ping update.freebsd.org PING update1.FreeBSD.org (72.21.59.252): 56 data bytes 64 bytes from 72.21.59.252: icmp_seq=0 ttl=51 time=64.557 ms 64 bytes from 72.21.59.252: icmp_seq=1 ttl=51 time=64.580 ms ^C --- update1.FreeBSD.org ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 64.557/64.569/64.580/0.012 ms It responds with update1, so I tried again using update1.freebsd.org (and several others that I could ping) but it always gives me the same response. A quick check of the handbook and the man pages for both freebsd-update(5) and freebsd-update.conf(8) didn't tell me much about this. I'm sure it's something stupidly simple. Does anyone have some ideas? There's quite a bit of useful information missing. For starters, what is the output of 'uname -a'? -- Glen Barber Sorry, forgot to paste that. mobius# uname -a FreeBSD mobius.mahlerwein.homeip.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Sep 5 02:34:20 CDT 2008 r...@mobius.mahlerwein.homeip.net:/usr/obj/usr/src/sys/GENERIC i386 ___ 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: Freebsd-update question
On Sat, Aug 8, 2009 at 10:25 AM, Richard Mahlerweinmahle...@yahoo.com wrote: I thought I'd give freebsd-update a try since I run a GENERIC kernel. mobius# freebsd-update -s update.freebsd.org fetch Looking up update.freebsd.org mirrors... none found. Fetching public key from update.freebsd.org... failed. No mirrors remaining, giving up. [snip] There's quite a bit of useful information missing. For starters, what is the output of 'uname -a'? Sorry, forgot to paste that. mobius# uname -a FreeBSD mobius.mahlerwein.homeip.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Sep 5 02:34:20 CDT 2008 r...@mobius.mahlerwein.homeip.net:/usr/obj/usr/src/sys/GENERIC i386 I was able to get a mirror using: freebsd-update -r 7.1-PRERELEASE fetch -- Glen Barber ___ 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: Freebsd-update question
On Sat, 8 Aug 2009 07:16:15 -0700 (PDT) Richard Mahlerwein mahle...@yahoo.com wrote: I thought I'd give freebsd-update a try since I run a GENERIC kernel. mobius# freebsd-update -s update.freebsd.org fetch Looking up update.freebsd.org mirrors... none found. Fetching public key from update.freebsd.org... failed. No mirrors remaining, giving up. Can you access the svr record? $ dig +short _http._tcp.update.freebsd.org srv 1 50 80 update5.FreeBSD.org. 2 10 80 update1.FreeBSD.org. 1 35 80 update4.FreeBSD.org. If not try running freebsd-update with servers 4 and 5. ___ 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: Freebsd-update question
[random snippage all over] From: Glen Barber glen.j.bar...@gmail.com Subject: Re: Freebsd-update question On Sat, Aug 8, 2009 at 10:25 AM, Richard Mahlerweinmahle...@yahoo.com wrote: mobius# freebsd-update -s update.freebsd.org fetch Looking up update.freebsd.org mirrors... none found. Fetching public key from update.freebsd.org... failed. No mirrors remaining, giving up. mobius# uname -a FreeBSD mobius 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Sep 5 02:34:20 CDT 2008 r...@mobius.mahlerwein.homeip.net:/usr/obj/usr/src/sys/GENERIC i386 I was able to get a mirror using: freebsd-update -r 7.1-PRERELEASE fetch -- Glen Barber mobius# freebsd-update -r 7.1-PRERELEASE fetch Looking up update1.FreeBSD.org mirrors... none found. Fetching public key from update1.FreeBSD.org... failed. No mirrors remaining, giving up. I'm puzzled. It seems like this shouldn't be hard, and google seems to agree. There must be something stupidly simple messed up with my system, or configured incorrectly. What protocols/ports does freebsd-update use? Watching tcpdump while running freebsd-update shows no traffic whatsoever relating to this that I can tell. Makes me wish for a verbose mode on freebsd-update. I fiddled with truss, but that seems harder to interpret than strace on linux (which I'm installing from the ports as I write this). I mean, I'd just update it the old fashioned way, but now I'm curious (and, let's face it, I've not updated it in quite a while, so I suspect another day or two won't hurt any more). I'm about to add a verbose option to freebsd-update and see if I can get it to print out in more detail what it's actually trying to do... ___ 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: Freebsd-update question
From: RW rwmailli...@googlemail.com Subject: Re: Freebsd-update question To: freebsd-questions@freebsd.org Date: Saturday, August 8, 2009, 11:46 AM On Sat, 8 Aug 2009 07:16:15 -0700 (PDT) Richard Mahlerwein mahle...@yahoo.com wrote: I thought I'd give freebsd-update a try since I run a GENERIC kernel. mobius# freebsd-update -s update.freebsd.org fetch Looking up update.freebsd.org mirrors... none found. Fetching public key from update.freebsd.org... failed. No mirrors remaining, giving up. Can you access the svr record? $ dig +short _http._tcp.update.freebsd.org srv 1 50 80 update5.FreeBSD.org. 2 10 80 update1.FreeBSD.org. 1 35 80 update4.FreeBSD.org. If not try running freebsd-update with servers 4 and 5. mobius# dig +short _http._tcp.update.freebsd.org srv (returns nothing) I tried various of the update servers both via 'dig' and via 'freebsd-update', all returned the same. I attempted using a -s 216.14.97.73 seeing if pointing it to IP would work, but no go - same failure. For what it's worth, making up a -s responds identically (like '-s bleh.a.oorg'). How is freebsd-update resolving addresses? I'm sure this is all user error somewhere along the line. ___ 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: Freebsd-update question
Thanks for the help, I figured out the [likely] answer and included it at the bottom. --- On Sat, 8/8/09, Richard Mahlerwein mahle...@yahoo.com wrote: From: Richard Mahlerwein mahle...@yahoo.com Subject: Re: Freebsd-update question To: freebsd-questions@freebsd.org Date: Saturday, August 8, 2009, 2:06 PM [random snippage all over] From: Glen Barber glen.j.bar...@gmail.com Subject: Re: Freebsd-update question On Sat, Aug 8, 2009 at 10:25 AM, Richard Mahlerweinmahle...@yahoo.com wrote: mobius# freebsd-update -s update.freebsd.org fetch Looking up update.freebsd.org mirrors... none found. Fetching public key from update.freebsd.org... failed. No mirrors remaining, giving up. mobius# uname -a FreeBSD mobius 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Sep 5 02:34:20 CDT 2008 r...@mobius.mahlerwein.homeip.net:/usr/obj/usr/src/sys/GENERIC i386 I was able to get a mirror using: freebsd-update -r 7.1-PRERELEASE fetch -- Glen Barber mobius# freebsd-update -r 7.1-PRERELEASE fetch Looking up update1.FreeBSD.org mirrors... none found. Fetching public key from update1.FreeBSD.org... failed. No mirrors remaining, giving up. I mean, I'd just update it the old fashioned way, but now I'm curious (and, let's face it, I've not updated it in quite a while, so I suspect another day or two won't hurt any more). I'm about to add a verbose option to freebsd-update and see if I can get it to print out in more detail what it's actually trying to do... Found what I believe to be the answer, and yes it's mostly user error. :) Your test above notwithstanding, it seem the PRERELEASE isn't supported for freebsd-update, or at least it's not signed. I found the source to freebsd-update (it's a shell script) and found that there was a way to specify --debug. So, when I ran... mobius# freebsd-update --debug -s update1.freebsd.org fetch Looking up update1.freebsd.org mirrors... none found. Fetching public key from update1.freebsd.org... fetch: http://update1.freebsd.org/7.1-PRERELEASE/i386/pub.ssl: Not Found failed. That gave me a good lead to follow. Browsing around update1.freebsd.org for a bit leads me to find things under, say, http://update.freebsd.org/7.1-RELEASE/i386/pub.ssl Just not under 7.1-PRERELEASE. I'll update the old fashioned way. NP. I think once I'm off PRERELEASE I'll be able to use freebsd-update. ___ 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: Freebsd-update question
On Sat, 8 Aug 2009 11:14:10 -0700 (PDT) Richard Mahlerwein mahle...@yahoo.com wrote: mobius# dig +short _http._tcp.update.freebsd.org srv (returns nothing) This is typically either due either to broken SRV support in DNS, or the absence of full dns on a private network behind proxies. Perhaps you need to set HTTP_PROXY. ___ 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: Freebsd-update question
--- On Sat, 8/8/09, RW rwmailli...@googlemail.com wrote: From: RW rwmailli...@googlemail.com Subject: Re: Freebsd-update question To: freebsd-questions@freebsd.org Date: Saturday, August 8, 2009, 4:59 PM On Sat, 8 Aug 2009 11:14:10 -0700 (PDT) Richard Mahlerwein mahle...@yahoo.com wrote: mobius# dig +short _http._tcp.update.freebsd.org srv (returns nothing) This is typically either due either to broken SRV support in DNS, or the absence of full dns on a private network behind proxies. Perhaps you need to set HTTP_PROXY. I currently have my little westell DSL router set to be my DNS for all my boxes behind it. While a neat little box, it has its issues from time to time. Should I at least point my DNS to the DNS it uses to save an extra relay? Sort of off topic, but it has begun to annoy me that Verizon has decided to redirect requests to domains that don't exist to their search pages. I haven't noticed they are proxying, but they could be if they did so reasonably transparently. And, with hijacking nonexistent domains, they've led me to believe they COULD be doing something goofy like that. Is there any easy way to actually confirm or deny they're doing more goofy stuff? ___ 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: Freebsd-update question
Richard Mahlerwein wrote: [snip] I currently have my little westell DSL router set to be my DNS for all my boxes behind it. While a neat little box, it has its issues from time to time. Should I at least point my DNS to the DNS it uses to save an extra relay? Depends. I don't know if the Westell does any caching of recursive queries. I don't use it as I have a FreeBSD gateway box that runs my DNS. I have it forwarding to OpenDNS DNS servers, so I don't even use Verizon's. Locally caching DNS lookups locally saves trips. Various different configs are possible, and all will probably do the job effectively. YMMV Sort of off topic, but it has begun to annoy me that Verizon has decided to redirect requests to domains that don't exist to their search pages. I haven't noticed they are proxying, but they could be if they did so reasonably transparently. And, with hijacking nonexistent domains, they've led me to believe they COULD be doing something goofy like that. Is there any easy way to actually confirm or deny they're doing more goofy stuff? This is how you opt out of this service: http://www.verizon.net/central/vzc.portal?_nfpb=true_pageLabel=vzc_help_contentDisplaycase=dns_assist Essentially just change the Verizon DNS server IP last two numbers from .12 to .14 for both Primary and Secondary in your Westell. -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: freebsd update question
Hi, Jason On Thu, Jun 11, 2009 at 8:10 PM, Jasonjhelf...@e-e.com wrote: Hi, I have just started getting into the realm of kernel building, and I have a question in so far as upgrades. Is it possible to do a freebsd-update fetch then install, reboot, and then install again to get to the latest release you want to run? Yes, this is possible. Update /usr/src with sources and build a kernel from that, and use that kernel. Yep. After this, assuming this is the correct path, can the same path be used to upgrade other servers, and then just plop the kernel on (same hardware.) If it is a GENERIC kernel on the other servers, you can follow the freebsd-update path mentioned above. I am not sure if this is the right path, but looking to understand it a little better. If you only want binary upgrades, freebsd-update is probably your best bet. If you like pain (like most of us do), you can build from source. :) -- Glen Barber ___ 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: freebsd update question
On Thu, 11 Jun 2009, Jason wrote: Hi, I have just started getting into the realm of kernel building, and I have a question in so far as upgrades. Is it possible to do a freebsd-update fetch then install, reboot, and then install again to get to the latest release you want to run? Update /usr/src with sources and build a kernel from that, and use that kernel. In general when you make an updated kernel you should rebuild and install world too. This doesn't apply to building a different (custom) kernel when world has not changed. Okay, it is often true that within major versions you can run with an updated kernel on the old world for a long time without encountering a problem, but problems from kernel-world mismatch are not extremely rare. If and when you install the sources, check the procedures in UPADATING (near the bottom) for best practices procedure. After this, assuming this is the correct path, can the same path be used to upgrade other servers, and then just plop the kernel on (same hardware.) With the above concern about kernel-world mismatch in mind, yes this is likely to work, but the best practice would be to make a release. This should work even if there is a minor, perhaps unknown, variation in hardware. I am not sure if this is the right path, but looking to understand it a little better. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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: freebsd-update question
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RJ45 Sent: Friday, May 16, 2008 9:29 AM To: freebsd-questions@freebsd.org Subject: freebsd-update question hello, I have updated qith command freebsd-update and hte command freebsd-update fetch shows me I have already hte latest patch level 7.0-RELEASE-p1 anyway uname -a shows me always 7.0-RELEASE #0 how can I do to have uname to show me the correct patch level ? thanks Rick I've noticed this was solved after recompiling the kernel. Maybe it's also another method available, but since I'm using a custom kernel I did not looked for it. Best Regards Catalin Miclaus Network/Security ISP-Data Starcomms Ltd. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update question
RJ45 wrote: hello, I have updated qith command freebsd-update and hte command freebsd-update fetch shows me I have already hte latest patch level 7.0-RELEASE-p1 anyway uname -a shows me always 7.0-RELEASE #0 how can I do to have uname to show me the correct patch level ? thanks Rick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] As another reader already said, this can be fixed by recompiling the kernel. In fact, you may notice that this file changes every time freebsd-update fetches new patches: /usr/src/sys/conf/newvers.sh This is responsible for giving your custom kernels the -p1, -p2 and so on designations. It is not however always necessary to recompile the kernel. Some updates do not really contain any changes to kernel code. For example, AFAIR, p1 for 7.0 RELEASE only had some updates for the ssh daemon. In this case recompiling the kernel will only give you the p1 designation, but nothing much else. However this is still useful for people maintaining a number of machines: They can quickly tell which ones are updated and which not. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update question
shows me I have already hte latest patch level 7.0-RELEASE-p1 anyway uname -a shows me always 7.0-RELEASE #0 how can I do to have uname to show me the correct patch level ? uname tells you about running kernel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update question
On 5/16/08, Catalin Miclaus [EMAIL PROTECTED] wrote: I've noticed this was solved after recompiling the kernel. Maybe it's also another method available, but since I'm using a custom kernel I did not looked for it. I have the same problem here. Uname shows 7.0-RELEASE after reboot and freebsd-update to 7.0-RELEASE-p1. How to solve this without recompiling kernel? cheers Simon -- XMPP: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update question
I know that recompiling the kernel was a way to do it but I Wanted to avoid it. thanks On Fri, 16 May 2008, Simon Jolle wrote: On 5/16/08, Catalin Miclaus [EMAIL PROTECTED] wrote: I've noticed this was solved after recompiling the kernel. Maybe it's also another method available, but since I'm using a custom kernel I did not looked for it. I have the same problem here. Uname shows 7.0-RELEASE after reboot and freebsd-update to 7.0-RELEASE-p1. How to solve this without recompiling kernel? cheers Simon -- XMPP: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update question
On Wed, Jul 18, 2007 at 01:46:51PM +0200, n j wrote: Hello, while updating my FreeBSD box, freebsd-update reported: Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature from update1.FreeBSD.org... done. ... No updates needed to update system to 6.2-RELEASE-p6. However, uname -a reveals: FreeBSD my.hostname.here 6.2-RELEASE-p4 FreeBSD 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 which suggests that my system is still running 6.2-RELEASE-p4, not 6.2-RELEASE-p6 that I guess it should be running. The box was rebooted a couple of times, but still reports the same. My question: am I reading something wrong here or is there a problem with freebsd-update? More specifically, is the problem that the system is running SMP? The cause for this confusion is the fact that patches 5 and 6 were for a userland utility (file) and a library (libarchive), not for the kernel. So for these patches, the kernel (which contains the release-level string) isn't rebuilt and so it isn't updated. The only ways to fix this are: 1) change the update mechanism to update the kernel(s) version string 2) rebuild the kernel locally. Whether 1 is appropriate is up to the maintainer, I guess. You could submit a problem report about it with the send-pr tool. 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) pgpppJlWFA7D7.pgp Description: PGP signature
Re: freebsd-update question
The cause for this confusion is the fact that patches 5 and 6 were for a userland utility (file) and a library (libarchive), not for the kernel. So for these patches, the kernel (which contains the release-level string) isn't rebuilt and so it isn't updated. 1) change the update mechanism to update the kernel(s) version string Roland, thank you very much for the information. Digging a little deeper, I discovered two sysctl variables that contain this information: kern.osrelease: 6.2-RELEASE-p4 kern.version: FreeBSD 6.2-RELEASE-p4 #0: Thu Apr 26 17:40:53 UTC 2007 And the sysctl(8) man page reveals: Name TypeChangeable kern.osrelease stringno kern.version stringno meaning that it is probably impossible to change these values without indeed recompiling the kernel. Regards, -- Nino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-update question
Angelin Lalev wrote: I have machine wich is build from sources (FreeBSD 6.2p3 , RELENG_6_2). Can I use freebsd-update on that machine straight away? Yes. If you made any changes to the source code before compiling, you may need to edit /etc/freebsd-update.conf (and in particular, the IgnorePaths and UpdateIfUnmodified directives). In the article that appears on top of google (http://www.daemonology.net/freebsd-update/binup.html), there is section about removing kernel counters, perllocal.pod etc. It's not clear for me if that step should be taken at server's or the client's side. That's done at the server side, as part of the process of building the updates. Colin Percival ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
