Re: Anyone running X11 apps on Mojave?
Hi, I just installed XQuartz 2.7.11 today on a fresh Mac running Mojave 10.14.2. I installed XQuartz from the XQuartz.pkg found in the disk image (dmg) file on the XQuartz support site: https://www.xquartz.org/ I didn't have any problems installing and then later running XQuartz. However, on Mojave, there was an interesting alert panel which appeared during the pkg installation process which I have not seen on previous versions of macOS when installing XQuartz, which alert panel with two buttons, one which stated "Don't Allow" and the other stated "OK", and text which stated the following: "Installer.app" wants access to control "System Events.app". Allowing control will provide access to documents and data in "System Events.app", and to perform actions within that app. I didn't know what to do so I waited. There must have been a timeout because the panel disappeared on its own without me making a selection. The package installer process then finished on its own and stated XQuartz had been installed successfully. I was then able to run XQuartz without any issues. Interestingly, when I now run System Preferences and select Security & Privacy -> Privacy -> Automation there is an entry for "Installer.app" and underneath a check box next to "System Events.app". The check box is unchecked. I gather this all has something to do with changes to Mojave's security and privacy settings. Has anyone else seen this with or without XQuartz involved? If so, any ideas of what this means? Thanks, -T.M. On Fri, Nov 23, 2018 at 8:37 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > > > On Nov 23, 2018, at 9:52 PM, Randolph M. Fritz wrote: > > Does Xquartz still work? or MacPorts X11? Or…? > > > yep, just fine. > > XQuartz 2.7.11 works from the XQuartz website, which is what I’m using > right now, and the MacPorts versions are there as well: > > > http://packages.macports.org/xorg-server-devel/xorg-server-devel-1.20.1_0.darwin_18.x86_64.tbz2 > > > http://packages.macports.org/xorg-server/xorg-server-1.18.4_3.darwin_18.x86_64.tbz2 > > > Ken >
MacPorts and /opt/local on Catalina and Big Sur read only volumes
Hi all, I haven't installed a fresh MacPorts system in quite some time but will soon be doing so on a few Macs one running Catalina and the other Big Sur. Starting with Catalina, the root volume / is read-only so how do the MacPorts package installers set things up such that /opt/local can remain the default path to MacPorts for both read and write functionality on Catalina and Big Sur? Do the MacPorts package installers make use of Apple's new bi-directional firmlinks capability defined in /etc/synthetic.conf as also described on this page? https://derflounder.wordpress.com/2020/01/18/creating-root-level-directories-and-symbolic-links-on-macos-catalina/ Thank you. -TM
Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes
On a fresh Catalina or Big Sure system, if you cd to root / then sudo then try mkdir /opt or something else such as mkdir /hello the system won't allow it, I get this: mkdir: /hello: Read-only file system note: the MacBook I just tried this on also has FileVault enabled and its got one of those Apple T2 chips with a touch bar How does the MacPorts Catalina or Big Sur pkg installer work around this restriction? On Fri, Jun 25, 2021 at 3:26 PM Ryan Schmidt wrote: > > > On Jun 25, 2021, at 18:07, Tabitha McNerney wrote: > > > Hi all, > > > > I haven't installed a fresh MacPorts system in quite some time but will > soon be doing so on a few Macs one running Catalina and the other Big Sur. > Starting with Catalina, the root volume / is read-only so how do the > MacPorts package installers set things up such that /opt/local can remain > the default path to MacPorts for both read and write functionality on > Catalina and Big Sur? Do the MacPorts package installers make use of > Apple's new bi-directional firmlinks capability defined in > /etc/synthetic.conf as also described on this page? > > > > > https://derflounder.wordpress.com/2020/01/18/creating-root-level-directories-and-symbolic-links-on-macos-catalina/ > > > > Thank you. > > I'm not aware of MacPorts doing anything special for this. It just works? > > >
Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes
Maybe the pkg installer software looks to see if an installation is trying to mkdir in root and it automatically creates /etc/synthetic.conf with an entry. That would be quintessential Apple to do something like that. Thank you Apple, it just works. On Fri, Jun 25, 2021 at 5:20 PM Ryan Schmidt wrote: > On Jun 25, 2021, at 21:03, Tabitha McNerney wrote: > > > On a fresh Catalina or Big Sure system, if you cd to root / then sudo > then try mkdir /opt or something else such as mkdir /hello the system won't > allow it, I get this: > > > > mkdir: /hello: Read-only file system > > > > note: the MacBook I just tried this on also has FileVault enabled and > its got one of those Apple T2 chips with a touch bar > > > > How does the MacPorts Catalina or Big Sur pkg installer work around this > restriction? > > I don't know that we're doing anything. It just works. > > There is some mechanism, that I don't understand, by which the system > volume and the data volume are combined into a single presentation. > Presumably the Installer app knows that you cannot install to the system > volume, so it installs MacPorts to the data volume. > >
Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes
Thank you Bjarne, this is great to know especially for those of us lagging somewhat and getting ourselves more acquainted with the new volume formats of Catalina and Big Sur, with Monterrey in the works. I would not be surprised if Apple included the opt directory in /System/Volumes/Data thanks in large part to MacPorts having a very long history of using /opt and if I recall correctly Apple has long been supportive of MacPorts. What a nice thing to learn today, making for a lovely day, in a world full of noise and chaos. Have a great day and stay well. -TM On Fri, Jun 25, 2021 at 10:35 PM Bjarne D Mathiesen < macint...@mathiesen.info> wrote: > > > Tabitha McNerney wrote: > > Hi all, > > > > I haven't installed a fresh MacPorts system in quite some time but will > > soon be doing so on a few Macs one running Catalina and the other Big > > Sur. Starting with Catalina, the root volume / is read-only so how do > > the MacPorts package installers set things up such that /opt/local can > > remain the default path to MacPorts for both read and write > > functionality on Catalina and Big Sur? > > /opt is one of the directories Apple defines at the / level as part of > the Data Volume > > > Do the MacPorts package > > installers make use of Apple's new bi-directional firmlinks capability > > defined in /etc/synthetic.conf as also described on this page? > > > > > https://derflounder.wordpress.com/2020/01/18/creating-root-level-directories-and-symbolic-links-on-macos-catalina/ > > No. That's not necessary as /opt transparently exists and is writable. > > > > > Thank you. > > > > -TM > > In depth explanations are here : > > https://arstechnica.com/gadgets/2019/10/macos-10-15-catalina-the-ars-technica-review/11/#h1 > > https://arstechnica.com/gadgets/2020/11/macos-11-0-big-sur-the-ars-technica-review/11/#h1 > > So, If you go to /System/Volumes/Data in Terminal & do 'ls -l' you'll > see the opt directory. > > -- > Bjarne D Mathiesen > Korsør ; Danmark ; Europa > --- > denne besked er skrevet i et totalt M$-frit miljø > MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina > 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM > ATI Radeon RX 590 8 GB >
