From owner-freebsd-questions@freebsd.org Fri Jul 7 03:45:53 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B014D98E35 for ; Fri, 7 Jul 2017 03:45:53 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 67BF765C00 for ; Fri, 7 Jul 2017 03:45:52 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:50974] helo=localhost) by dnvrco-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id DC/17-08177-7A30F595; Fri, 07 Jul 2017 03:44:40 +0000 Date: Fri, 07 Jul 2017 03:44:37 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-questions@freebsd.org Subject: Re: FreeBSD did it again (still) To: freebsd-questions@freebsd.org References: <27b3c757-1f00-a033-03f6-303a82ab65f2@columbus.rr.com> <3ce31ee2-5e35-d31c-71ca-dc95ece2dd61@intersonic.se> <020431a6-1a7d-d80e-0725-585c21f3ef27@columbus.rr.com> <563b14d5-ebfb-62b6-28ac-3ebbd663d067@intersonic.se> <8c1bb853-5eb0-4fae-ee26-5ff4684c2b3a@saunalahti.fi> <1499345128.3276.2.camel@gmail.com> <3cbeca30-8801-d800-edcb-f64ea2f079e0@columbus.rr.com> X-RR-Connecting-IP: 107.14.64.6:25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2017 03:45:53 -0000 from Baho Utot: > Well FYI the upgrade base 10.1 to 11.0-p10 when as expected. Update the ports > to the current quarterly was a tragic happening. I have done this before > upgrade a desktop from 10.3 to 11.0-p0 then to 11.0-p9. Again the ports just > did not work as it resulted in a broken desktop each time. I started using > the quarterly ports branch thinking I get some stablilty. No stability to be > found. Should I user be able to update without going thru a weeks worth of > debugging? I think that is not too much to ask. > I have doing this since RedHat 4.0 in the mid 1990's. I know how to build > software. When I was using LFS I could go from LFS 5.0 to LFS 6.0 all the way > to LFS &.5 and it always just worked. I thinking I'll need to return to my > own scratch built linux system to find some stability I am looking for. > FreeBSD not so much. Maybe OpenBSD will prove to be stable. > I am not looking to update my system more than I change underwear, so I can > chase the "Oh I have to have the latest". I am looking for stable/working. I updated on two computers from FreeBSD 10.1-STABLE to 11.0-STABLE, and experienced the same shared-library hell that you did. None, or almost none of the ports, ran, except pkg-static. I was able to rebuild portmaster and pkg, and then synth, on what had been upgraded to 11.1-BETA2. But after I configured synth, and ran synth upgrade-system, only a few ports made it, and then the system crashed, and again a second time. I can try on the other computer which also has the same FreeBSD version installed using NFS, see if maybe one computer is somehow especially unstable with FreeBSD 11-stable and HEAD. It could also be instability in the rsu wireless driver; re(4) recognizes the Ethernet but fails to connect. I have little experience with OpenBSD, never installed, used the LiveUSB from liveusb-openbsd.sourceforge.net, now outdated (OpenBSD 5.4). But there is less shared-library hell with NetBSD than with FreeBSD. I was able to startx after upgrading from NetBSD 7.99.15 i386 to 7.99.72 to 8.99.1, but after rebuilding modular-xorg, X would no longer start. I assume shared libraries were in sync, but getting X to work in NetBSD is inconsistent, I could call it a crapshoot. > Synth is one of the best tools for building ports for FreeBSD. > It started on DragonflyBSD and "ported" over to FreeBSD. After John Marino > had dust up with the FreeBSD folks the FreeBSD folks kicked him out as a > maintainer. I still think that BS and a bad move by FreeBSD folks. IMO he > was trying to bring some sanity to FreeBSD build process, something like Arch > linux does. Which is/was a good thing. I've been wondering if I should try to install DragonFlyBSD (cross-compile from FreeBSD or NetBSD?) and see how synth works there. One problem with DragonFlyBSD on the USB-stick installer was being unable to mount/read NetBSD and FreeBSD partitions, and FreeBSD and NetBSD partitions could not mount/read the DragonFlyBSD USB stick: maybe a different flavor of UFS? So I don't want to get into a mess and lose what I have on the hard drive. Synth has also been ported to NetBSD/pkgsrc, and I have one pristine NetBSD-current (8.99.1) amd64 installation to try it on. If it fails, back to regular pkgsrc. Tom