Re: Catalina: accepting incoming connections on unbound does not survive a reboot
On 14 Jan 2021, at 18:50, Tom wrote: Have you tried Lulu or Little Snitch? I've used both on various versions through 10.14. It is my understanding that due to Apple exempting their own software from the Network Extension Framework, both are hobbled on 10.15+, but that with 11.2 they will be reversing that choice. My issues with modern macOS for server applications are mostly with the broken logging and the difficulty of stripping down the operational environment to just what's needed on a Mac that doesn't normally function as a personal computer. Disabling the built-in firewall entirely may be your only solution. I am not sure because I have not bothered trying to make any macOS newer than El Capitan usable as a server. Life is short and FreeBSD exists. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
Re: Catalina: accepting incoming connections on unbound does not survive a reboot
On 13 Jan 2021, at 8:26, Gerben Wierda via macports-users wrote: I did not have this problem under Mojave, but since I have upgraded I do. I am running a backup nameserver (in my split-DNS setup) on a mac desktop (unbound via MacPorts). After a reboot, the first user to log in gets a panel from the firewall with the question to allow incoming connections for unbound. System administrator user name and password are given and incoming connections are then accepted. But after a reboot I have to do this again. Yes. Because modern macOS is unfit for server applications. Apple started making design choices circa Sierra aimed at converging it with iOS, for reasons that make sense for personal computers but without regard to how servers would be affected. Historically it has been possible to make specific persistent exceptions using the Firewall panel of the Security preferences pane and supposedly this still can be done on Catalina (see https://www.dummies.com/computers/macs/macbook/how-to-customize-your-macbooks-catalina-firewall/) but I have not tried that and it may not work for software that is not packaged as a macOS application. You definitely should disable "stealth mode" in that panel. Disabling the built-in firewall entirely may be your only solution. I am not sure because I have not bothered trying to make any macOS newer than El Capitan usable as a server. Life is short and FreeBSD exists. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
Re: Apple Silicon and universal builds
Add -universal to variants.conf Sent from my iPhone > On Jan 14, 2021, at 6:09 AM, Joshua Root wrote: > > Mark Bestley wrote: >> I have just got an Apple Silicon Mac Mini and am trying to install some ports >> I am trying to use just arm code. However some ports put a +universal >> variant as the default. This would not be a problem except some ports do not >> build if universal e.g. python38 and icu. >> Example ports that force unwanted +universal on are >> llvm-9.0 - which I managed to build using the manual fix in the icu ticket >> cargo which depends on python38. Now python38 works if arm build only. >> How do I force things to build for arm only. >> Why are +universal variants set as the default and how can you see which >> depenents are set this way (you can then force those to be single >> architecture) > > This is happening when you install a port that does not support the arm64 > architecture, which means the only way to proceed on arm64 hardware is to > install an x86_64 version. This means that the dependencies need to support > x86_64 as well, which results in them being installed with +universal. > > If you don't want this to happen, you could set universal_archs to just > 'arm64' in macports.conf. This will cause an error when you try to install > any port that would normally trigger installation of a universal dependency. > > - Josh
Re: Apple Silicon and universal builds
Mark Bestley wrote: I have just got an Apple Silicon Mac Mini and am trying to install some ports I am trying to use just arm code. However some ports put a +universal variant as the default. This would not be a problem except some ports do not build if universal e.g. python38 and icu. Example ports that force unwanted +universal on are llvm-9.0 - which I managed to build using the manual fix in the icu ticket cargo which depends on python38. Now python38 works if arm build only. How do I force things to build for arm only. Why are +universal variants set as the default and how can you see which depenents are set this way (you can then force those to be single architecture) This is happening when you install a port that does not support the arm64 architecture, which means the only way to proceed on arm64 hardware is to install an x86_64 version. This means that the dependencies need to support x86_64 as well, which results in them being installed with +universal. If you don't want this to happen, you could set universal_archs to just 'arm64' in macports.conf. This will cause an error when you try to install any port that would normally trigger installation of a universal dependency. - Josh
Re: old Macbook Pro
Sent: Thursday, January 14, 2021 at 1:23 AM From: "Bjarne D Mathiesen" > Dave Horsfall wrote: >> an oldish MacBook Pro (13", Mid 2010) running >> Sierra 10.12.6 (I've been told by the dealer that it cannot run High >> Sierra, and when I tried it on an older MacBook it was a disaster). > > Apple states that it can run 10.13.6 (see MacTracker app) > That one !is! able to run macOS 10.15.7 Cataina :-) > I've got a comrade who's got the same model, and it works perfectly :-) > http://dosdude1.com/catalina/ I have a MacBook Pro 2010 13-inch as well; 10.13 High Sierra worked fine on it. As I wrote in https://lists.macports.org/pipermail/macports-users/2019-June/046866.html I have been using dosdude1's patchers to run 10.14 Mojave and now 10.15 Catalina, and would recommend it for those sufficiently adventurous. The battery needed to be removed, and since I haven't replaced it, the CPU is underclocked to about 0.8GHz; but since I have 16GB RAM and an SSD installed, it rarely feels slow. (I probably won't be trying 11.x Big Sur on it, as more things like accelerated graphics do not work.) Christopher A. Chavez
