Re: upgrade issue 8.x to 9.0-RC2: libz.so.5 not found
al...@stokes.ca schreef: However, programs such as startx and portupgrade are failing with the message libz.so.5 not found. I know I can fix this with an evil symlink, but that doesn't seem right, and what else is broken? Is there not a facility in portupgrade to scan my live dependencies and warn me of breakage? I have not encountered such a beast in my gleanings to date. What you probably did is make delete-old-libs. This deletes the old 8.x libs that where used by your ports. What you need to do is rebuild all your ports. That way they get linked to the proper libs again. The next time when you go from one major to another major number eg from 7 to 8 or from 8 to 9 and so on, is to do the make delete-old-libs step later. Then after upgrading, rebuild all your ports, they still work with the old libs. Once the ports are rebuild against the newer libs then do the make delete-old-libs step. This is not nessacery when going from a minor number to amother minor number. eg from 8.1 to 8.2 and so on. Hope this helps. regards Johan Hendriks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: upgrade issue 8.x to 9.0-RC2: libz.so.5 not found
On Tue, Nov 29, 2011 at 12:49 AM, Johan Hendriks joh.hendr...@gmail.com wrote: al...@stokes.ca schreef: However, programs such as startx and portupgrade are failing with the message libz.so.5 not found. I know I can fix this with an evil symlink, but that doesn't seem right, and what else is broken? Is there not a facility in portupgrade to scan my live dependencies and warn me of breakage? I have not encountered such a beast in my gleanings to date. What you probably did is make delete-old-libs. This deletes the old 8.x libs that where used by your ports. What you need to do is rebuild all your ports. That way they get linked to the proper libs again. The next time when you go from one major to another major number eg from 7 to 8 or from 8 to 9 and so on, is to do the make delete-old-libs step later. Then after upgrading, rebuild all your ports, they still work with the old libs. Once the ports are rebuild against the newer libs then do the make delete-old-libs step. This is not nessacery when going from a minor number to amother minor number. eg from 8.1 to 8.2 and so on. In general yes.. but there have been occasions when this was required with libz... Cheers, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: upgrade issue 8.x to 9.0-RC2: libz.so.5 not found
On Tue, Nov 29, 2011 at 12:54:33AM -0800, Garrett Cooper wrote: On Tue, Nov 29, 2011 at 12:49 AM, Johan Hendriks joh.hendr...@gmail.com wrote: al...@stokes.ca schreef: However, programs such as startx and portupgrade are failing with the message libz.so.5 not found. I know I can fix this with an evil symlink, but that doesn't seem right, and what else is broken? Is there not a facility in portupgrade to scan my live dependencies and warn me of breakage? I have not encountered such a beast in my gleanings to date. What you probably did is make delete-old-libs. This deletes the old 8.x libs that where used by your ports. What you need to do is rebuild all your ports. That way they get linked to the proper libs again. The next time when you go from one major to another major number eg from 7 to 8 or from 8 to 9 and so on, is to do the make delete-old-libs step later. Then after upgrading, rebuild all your ports, they still work with the old libs. Once the ports are rebuild against the newer libs then do the make delete-old-libs step. This is not nessacery when going from a minor number to amother minor number. eg from 8.1 to 8.2 and so on. In general yes.. but there have been occasions when this was required with libz... I use sisutils/libchk: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/make-delete-old.html -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: upgrade issue 8.x to 9.0-RC2: libz.so.5 not found
on 29/11/2011 10:49 Johan Hendriks said the following: What you probably did is make delete-old-libs. This deletes the old 8.x libs that where used by your ports. What you need to do is rebuild all your ports. In my experience installing misc/compat8x was sufficient. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
upgrade issue 8.x to 9.0-RC2: libz.so.5 not found
Hello everyone, First a quick introduction, then my project, then my problem. ==My FreeBSD involvement== I've been dabbling with FreeBSD since I set up stokes.ca at pair.com over a decade ago. I liked the service at Pair, so I installed FreeBSD at home on a spare box. One of those evil Fujitsu disk drives took out my stable 4.x test system before I had a complete set of backups (Fujitsu was early into fluid dynamic bearings and I purchased on acoustics). I won't pain anyone by recalling the 5.x experience that followed. I had a 6.x system for a long time, but it never got much beyond a quasi offline backup spool. The 30GB system disk finally conked out--this was expected, so I slapped a new system disk into a box that had previously been my workstation, and performed a fresh 8 series installation. Unfortunately, I was never able to mount my PATA backup drive because of issues with the JMicron 363 PATA controller chip on the Asus P5B. These issues still exist in 9.x FWIW. Last week I finally shut down my firewall, stretched the drive cables across (to a different Core Duo mainboard not afflicted with a JMicron PATA controller) and scarfed the aging data. I had the data elsewhere in bits and pieces so there was never great urgency, the value was mainly that this was my only _organized_ backup set. ==7 men EGTB== I'm getting more serious about FreeBSD again because I'm becoming involved over the next few years in a hobby project to compute the chess seven-piece EGTB data set, which will total 60TB I think, when someday the computation completes. I'm mostly interested in compressed disk representations which permit high access speed that can be used by chess engines in real time. I might do a few pieces of the retrograde computation myself, but nowhere close to the whole thing. To perform the computation with full chess accuracy you need to begin with maximal promotion: two kings and five queens, and then work down through crazy promotions, such as two kings and five bishops, and then finally to positions that could possibly someday occur in a real chess game: many terabytes of computationally intense bootstrap to cover some very tiny corner cases (how tiny is a question I'm interested to explore, but most chess purists aren't). Even a small piece of the project would generate copious data so I've rigged up an experimental ZFS v28 box with a triple mirror on three 500GB disks I had lying around (two slightly enterprisy, one a Seagate refurb). I think of it as a two-way mirror with a pre-silvered hot spare that's better than nothing. I put 6GB of memory into the box and tried out deduplication. It ran great. I don't expect to use this feature (in hobby production) any time soon. I'll probably upgrade all the drives after the waters recede in Thailand and run fairly basic parameters. This week I'm intending to purchase a pair of Intel 311 SSD drives (20GB SLC) as a mirrored ZIL or ZIL/ARC option (Newegg.ca has them for $110). Warn me soon if I'm doing something stupid! I wish my ZFS box had chipkill ECC, but that upgrade is out of my budget at present, since it involves a whole new system board, CPU, and memory. I'm going to have to live a bit on the edge with other backups (and integrity checksums) available. I have some general interest in testing out what ZFS can do on fully configured box. I also do a lot of R programming and I'm experimenting with HDF5 for large data sets. The ZIL upgrade doesn't pertain much to my EGTB project. I'm either not brave enough or insane enough to put my FreeBSD system volume onto the ZFS mirror, as much as that seems kind of cool. Plain old UFS on a separate drive for me. Have others had success with ZFS system volumes? ==Broken upgrade problem== I was able to do a binary upgrade from 8.x to 9.0-RC2-p0. Slick. I once skimmed Colin's thesis, but the math is heavy--I understood enough to grasp that it's an excellent piece of work, and certainly much appreciated. After the binary upgrade my system runs well enough to initiate a ZFS pool and survive some ZFS pounding over the network (20GB data set with a recursive symlink deduplicated many times over until I finally killed it). However, programs such as startx and portupgrade are failing with the message libz.so.5 not found. I know I can fix this with an evil symlink, but that doesn't seem right, and what else is broken? Is there not a facility in portupgrade to scan my live dependencies and warn me of breakage? I have not encountered such a beast in my gleanings to date. On the first pass I skipped the package build step in my haste to break everything. That didn't work well (of course), so I rolled it back (sweet) and followed instructions: including the Ruby preamble and the triple Beetlejuice freebsd-update incantation. If there's an easy way to fix the mess, I'll do so, but otherwise there's no reason not to repair the problem with the blunt tool of a fresh system installation.
Re: upgrade issue 8.x to 9.0-RC2: libz.so.5 not found
Am Mon, 28 Nov 2011 17:49:50 -0800 schrieb al...@stokes.ca: Hello everyone, Hi, (I'll shorten this a bit, because I don't have opinions on everything you wrote) I'm either not brave enough or insane enough to put my FreeBSD system volume onto the ZFS mirror, as much as that seems kind of cool. Plain old UFS on a separate drive for me. Have others had success with ZFS system volumes? Since 8.2 I can confirm that ZFS was stable enough for me. But I have to admit that I'm still a bit sceptical because (even it's been long time ago) once I ended up with a broken zpool that spewed panics on zpool initialization. That was a horrible experience that I won't forget that easily. However, programs such as startx and portupgrade are failing with the message libz.so.5 not found. I know I can fix this with an evil symlink, but that doesn't seem right, and what else is broken? Is there not a facility in portupgrade to scan my live dependencies and warn me of breakage? I have not encountered such a beast in my gleanings to date. There is a little helper in port sysutils/bsdadminscripts called pkg_libchk. I use this tool very often like this: pkg_libchk -qo broken.txt And then I cat it to portmaster: portmaster -d `cat broken.txt` I don't know anymore how the portmaster step works with portupgrade, you need to figure this out by yourself. -- Martin signature.asc Description: PGP signature
