MacInTouch Amazon link...

macOS 10.15 Catalina

Channels
Apple, News


Since I still had some 32-bit Adobe and Microsoft apps, I deleted them. Then to be sure, I ran EasyFind for "Adobe" and "Microsoft" - amazing how many extras are not needed. Hard to get rid of some, but I probably deleted over 200-300 extra files.
A lot of apps have their own uninstaller app to remove the original app and all related items. Unfortunately, in this scenario, that uninstaller app will probably be 32-bit as well.

In this case, instead of simply dragging the application file into the trash, try using an app uninstaller utility. My choice for this is AppDelete.app. Once you “AppDelete” an item, it will gather all the related files with it and gives you a choice to archive or delete them, with the option to save specific items on the list.

Even if the actual application has been deleted, try applying AppDelete to any related file, e.g., .plist files. It should find the rest of the items connected with the original app.

However, if you can spare the space, I suggest keeping your 32-bit apps, for now—at least the ones that you might still have a use for. Whenever I find the need to run them, I boot from an external Mojave system to access them. I’m pleasantly surprised that I can launch them directly from the Catalina volume.
 


Here's a problem I have which hasn't been mentioned yet. I upgraded both my 2018 Mac Mini and 2017 iMac 27" to Catalina. With both machines, I tend to share an Apple Magic Keyboard, Apple Magic Mouse and/or Apple Magic Trackpad.

Prior to Catalina, if I had used one of these input devices on, say, the iMac, if I wanted to then use it on the Mini, then, about 30 seconds after powering on the Mini, it would try to connect any of the devices via Bluetooth, and that connection dialogue usually executed to completion i.e., the devices were then available.

Since Catalina, no such thing happens. Using the above scenario as an example, the Mini will sit there looking all stupid until I connect a cable from the keyboard, mouse or trackpad to the Mini, after which it then becomes available via Bluetooth.
 


I haven't changed to Catalina and currently intend to stay on Mojave. But I did notice something that might be of interest to those brave souls who are early adopters. Louis Rossman - better known for his hardware repair videos - has made a brief video describing an issue with Catalina bricking machines, and refers to a fix that Apple is assiduously removing from their support forums. I hope it might be helpful:

 


I have a Deleted Users folder that contains 6 GB worth of stuff I cannot delete. Error message says needed by system, etc. I have tried all the simple Terminal tricks, but nothing will delete this damn folder. Anybody have suggestions?
I had that problem sometime ago. As I recall, what I did was "restore" the deleted user to active state, convert or verify the restored account had admin privileges, then carefully delete the contents of the account before again deleting the user from a different admin account.

My experience didn't occur when "upgrading" a version of OS X, and was well before APFS and the separate "read-only System" setup in Catalina.

Since your issue may be an artifact of installing Catalina, and not a user account you deleted yourself, this may not work, but here is a link to Apple Support:
Apple Support said:
Restore a deleted user on Mac
If you saved a deleted user’s home folder, you can restore the user and the user’s home folder.
I've read that Apple has "invented" a new kind of symlink, a "firmlink," to point at the application elements in the new-with-Catalina read-only system file. A Catalina "firmlink" pointing at something in the "Deleted User" folder is a possible source of your error messages and inability to delete.
 



Objective Development posted an interesting blog entry:
which explains why you'd better not run any installer that updates or installs a kernel extension until the Catalina bug is fixed.
So, if I understand the process, once it's fixed, this is the roadmap to infect Catalina-running Macs. SIP is still there but will have to be disabled in order to update such low-level processes. Maybe I'm just too much of a skeptic, but I'd rather stick with Mojave and put my trust in Malwarebytes/ClamXav.
 


... FireWire will not mount, so you have to use USB or Thunderbolt. An external drive booted with macOS Catalina will not see the Apple apps in the main Applications folder on your Mac [internal drive]. You will have to go into the system folder, where you will find them in another Applications folder hidden there. You can remove them by dragging them to the Trash and with admin privilege (password), you can remove them. To me, this is very important news for people wanting to back-up macOS Catalina (which is advised before any updates are done on any Mac) and for people (like myself) who want to remove unwanted Apple apps.
I received this today from Bombich Software, Inc. which produces Carbon Copy Cloner:
Oct 16, 9:22 AM EDT

John,
We did some testing in-house, none of our Firewire systems are compatible with MacOS 10.15 Catalina, and we were unable to boot with a Thunderbolt to Firewire adaptor.
Apple Apps are NOT seen on the Main HD when you have booted from another device with OS Catalina. Apple Apps are stored in the System Folder under a Second Applications Folder. If you go to that Apps Folder inside the System Folder you will see your Apple Apps and you can move unwanted apps to the Trash and remove them with Admin Privileges (Password).
Yes that's all part of the locking down that's going hand in hand with APFS groups.
Best wishes,
Rob
Bombich Software, Inc.
 



(Sorry for the bulk-reply. I've been on vacation for a few days....)
The resistance comes about due to my having about 1 zillion scripts which were done in bash and not having the time, nor inclination, to move all 1 zillion to zsh.
The shell you use for your interactive sessions should not impact your scripts. Any script that begins with a line of the form
Code:
#!/bin/sh
will always be executed using the shell specified on that line. If your scripts require Bash, then make sure their first line begins with
Code:
#!/bin/bash
then you can change your login shell to anything you like, and your scripts will still run via Bash. No need to change the script itself, unless Apple actually deletes Bash, and if they do, you will almost certainly be able to compile and install your own copy (e.g. via MacPorts or Fink).
In a previous life I maintained a library of shell scripts. You choose one shell that works everywhere (/bin/sh) and leave them in that shell forever. Moving to a new shell is really hard, especially since their "emulation mode" never quite works.
Sounds like you were also writing scripts without specifying the required shell at the top of the file. That has always been a dangerous thing to do, especially if your want your scripts to be portable, since your favorite shell might not be allowed as a login shell on some systems. (This was a very big deal when I was in college, where my home directory was shared by many different mostly-incompatible systems.)
It's been said before, but again: /bin/sh is not necessarily a Unix Bourne shell and in these modern times, it probably is not.
Yes, but when launched via a hard- or symbolic-link named sh, it should run in a sh-compatible mode. This doesn't mean all extensions will be disabled, but it should mean that any non-backward-compatible changes should be turned off.

On the other hand, all systems have bugs, so this may not always be the case.

On the other, other hand, if your scripts currently work via /bin/sh (whatever it ends up being), then there's no reason to assume that they will break if they begin with
Code:
#!/bin/sh
and you change your login shell to something else.
I’ve read and scrupulously followed several tutorials on how to change to Bash, and it simply won’t do it. My problem is that the new shell prompts for a password I simply don‘t have.The OS password doesn’t work. Keychain doesn’t show any passwords for Terminal. Any ideas?
Interesting. How are you trying to change it? I usually run the chsh command. When it prompts for a password, use the one you used to log in to the OS. It should be the same, unless you've done something funky with your Mac's configuration.
 


... My iTunes folder, again located in my Music folder, looks like this:
[Folder] Album Artwork​
[File] iTunes Library Extras.itdb​
[File] iTunes Library Genius.itdb​
[File] iTunes Library.itl​
[File] iTunes Library.xml​
[Alias] iTunes Media ----> points to "iTunes Media" folder on external drive​
[Folder] Previous iTunes Libraries​

... So, anyway, the fix is to start out with a good "iTunes" folder, but instead of pointing to your "iTunes Media" folder with an alias, use a symbolic link.
Thanks for the tip. Although it is too late for anyone who has already upgraded to Catalina, there's another option for those who have not yet updated. Instead of creating an iTunes Media symlink, another option is to configure iTunes to look in the folder on your external drive for the library. On my Mac (macOS Sierra, running iTunes 12.8.2.3), this is how:
  1. From the menubar, select "iTunes -> Preferences..."
  2. Click on the "Advanced" tab
  3. In the box labeled "ITunes Media folder location", it should show the location of your media folder. I suspect it was something like "/Users/username/Music/iTunes/iTunes Media" on your system
  4. Click "Change..." and select a new location
  5. Click "OK"
Once this is done, iTunes will start using that location for your media. If the new location is empty (e.g. if you did this as the first step of moving your media elsewhere), then you should consolidate the library (File -> Library -> Consolidate Files...). This will copy all of your files from their current locations to the selected iTunes Media folder, if they are not already there.

If you copied/moved your iTunes Media folder to a new location and simply selected that location, I think (but do not know for certain) that consolidating the library won't actually copy any files but will update the database to look for them in the new location. But don't take my word on that - make a full backup before you try. (Actually, you should make a full backup before any major file reorganization like this, since you never know if/when something may glitch.)

I suspect (and would love confirmation from someone who has done this) that Apple's automatic migration on Catalina will see the library-location preference and look there.
 


Ric Ford

MacInTouch
I received this today from Bombich Software, Inc. which produces Carbon Copy Cloner:
... We did some testing in-house, none of our Firewire systems are compatible with MacOS 10.15 Catalina, and we were unable to boot with a Thunderbolt to Firewire adaptor.
Wow, that's a pretty big deal, and I can't find any documentation of that from Apple (or anyone else). Thanks for the heads-up, and I'd like to hear from anyone who has more information about this.
 


Here's another finding for Catalina:
In Mojave you can record audio directly from your iPhone in QuickTime. There is an icon that appears in the New Audio Recording drop-down menu in QuickTime for your iPhone. In Catalina, that icon is gone, and you cannot record audio from your iPhone with Catalina QuickTime. That's definitely not right.
 


This is from Drive Genius concerning this apps compatibility with Catalina:
Drive Genius v5 will not support macOS 10.15 Catalina.

The following are known issues:
  • The startup drive is missing or appears disabled for some/most utilities.
  • Drive Pulse may report spurious errors for Consistency Check.
  • Clone will not properly clone the startup volume. Data may be missing and/or the cloned drive may not work as a startup drive.
  • Bootwell will not create a proper startup drive. Startup will likely fail using a Bootwell drive created in 10.15.
We are working on full 10.15 support for Drive Genius v6, and will update as further information becomes available.
 


Ric Ford

MacInTouch
Here's another finding for Catalina:
In Mojave you can record audio directly from your iPhone in QuickTime. There is an icon that appears in the New Audio Recording drop-down menu in QuickTime for your iPhone. In Catalina, that icon is gone, and you cannot record audio from your iPhone with Catalina QuickTime. That's definitely not right.
So, this doesn't work in Catalina?

 


… I suspect (and would love confirmation from someone who has done this) that Apple's automatic migration on Catalina will see the library-location preference and look there.
My iTunes library was located on an external drive and iTunes worked perfectly with the setup all the way to Mojave. After the Catalina upgrade, I ran the different apps that replaced iTunes, i.e. Books, Music, Podcasts, and TV. I was hoping that the conversion would be done in situ, thereby leaving all the original files on the external drive. Unfortunately, the files were copied to the default locations in my user folder.

My issue is that I have a large collection of audiobooks (about 500 GB), so after the migration was complete, I had less that 200 GB of space left on my one-terabyte internal SSD. Now I have to go through the ~1,500 titles to determine which ones I have read, so I can archive them to an external drive before deleting them from my library.

By the way, Catalina did not automatically locate my old iTunes library. I had to specify its path before it could import the files.
 



Ric Ford

MacInTouch
I received this today from Bombich Software, Inc. which produces Carbon Copy Cloner:
... We did some testing in-house, none of our Firewire systems are compatible with MacOS 10.15 Catalina, and we were unable to boot with a Thunderbolt to Firewire adaptor.
Here's some Apple Catalina documentation implying that FireWire should work....
macOS User Guide said:
Use FireWire devices with Mac
You can use FireWire (sometimes called IEEE 1394 or i.LINK) to connect external devices, such as a hard drive or a digital video camera, without needing to restart your computer. A FireWire port provides power, so the connected device usually doesn’t need its own power cord.
I guess this doesn’t address booting from FireWire drives, though.
 


Ric Ford

MacInTouch
FYI:
Broadcasting & Cable (B&C) said:
RME Ensures Compatibility with New macOS Catalina
RME, German manufacturer of premium interfaces, announced today that its interfaces are already compatible with the latest macOS Catalina 10.15.x which was released this month. Since RME drivers are written in-house and not outsourced to third party developers, RME’s users are able to update their firmware immediately and continue working without interruption or delay.

Recently, several pro-audio manufacturers and interface manufacturers have issued warnings to customers advising them not to upgrade their operating software, presumably due to compatibility issues with the new OS. Other companies have issued announcements referencing possible delays in supporting the new operating system, or even loss of data.

RME interfaces compatible with Catalina include: Babyface Pro, Digiface AVB, Digiface Dante, Digiface USB, Fireface 802, Fireface UC, Fireface UCX, Fireface UFX II, Fireface UFX+, MADIface Pro, MADIface USB and the MADIface XT. Apps must be fully 64-bit and drivers should be “notarized” as required for operation with Catalina OS 10.15.x.

RME’s non-USB interfaces, including the PCle, Thunderbolt and FireWire, have beta drivers available for download now so its customers do not experience interruption or delay in their projects.
 


Here's some Apple Catalina documentation implying that FireWire should work....

I guess this doesn’t address booting from FireWire drives, though.
Yes, you can use FireWire devices, like an RME audio device or Apogee Duet etc., however you cannot boot from a disk with a FireWire connection.

On my 2012 Mac Pro running Mojave, my Catalina drive connected with FireWire showed up on the desktop and also as a Startup Disk inside Preferences. However, when you try to boot a Catalina drive on a FireWire connection, the Mac Pro simply shuts down. The result is the same on Macs that officially support Catalina.
 


For an excellent description of the macOS bash vs. zsh situation, including very helpful information about migrating scripts, see Moving to zsh. There's video of a presentation and a series of in-depth articles.

It is now particularly important that all scripts begin with a "#!" line specifying the shell to be used to execute the script. Currently, a script without any such line will use bash (probably /bin/bash but I haven't checked), but when bash is removed "in some future version of macOS", that will probably change to zsh (or whatever strikes Apple's fancy at that moment).
 


My iTunes library was located on an external drive and iTunes worked perfectly with the setup all the way to Mojave. After the Catalina upgrade, I ran the different apps that replaced iTunes, i.e. Books, Music, Podcasts, and TV. I was hoping that the conversion would be done in situ, thereby leaving all the original files on the external drive. Unfortunately, the files were copied to the default locations in my user folder.

My issue is that I have a large collection of audiobooks (about 500 GB), so after the migration was complete, I had less that 200 GB of space left on my one-terabyte internal SSD. Now I have to go through the ~1,500 titles to determine which ones I have read, so I can archive them to an external drive before deleting them from my library.

By the way, Catalina did not automatically locate my old iTunes library. I had to specify its path before it could import the files.
I have found that some macOS apps have fixed paths for some functions and not for others, causing problems with external media access. My solution has been to create Music, Movies, and Pictures folders on an external volume and use soft links to connect these folders to my account directory. This also removes a terabyte or so of media files from the boot volume. And the affect apps think that the media library is in the default location. The resulting configuration survives through upgrades. In any case, Apple's 'upgrade' process now deletes any useful metadata such as "Plays".

Creating a soft-linked configuration can be a little daunting because of the security hoops. Here is my current template command file for the setup task:
Code:
#!/bin/sh
# 2018-11-01    jrc CreateMediaSoftLinks.command
# 2019-10-17    jrc Updated with edits from Ric Ford
# 2019-10-17    jrc Updated to use variables for shell command customization
# 2019-10-17    jrc Updated to increase verbosity of comments

# CreateMediaSoftLinks for ThisUser on ThisMaC

#   "ThisMacMedia" is a placeholder for the external volume to hold the media files.
#   "ThisUser" is a placeholder for the short username of the file owner affected.
#    Replace these placeholders with the desired values when creating and copying in Finder.

#    Edit the next two shell commands to automatically replace these placeholders 
#        with the desired values for the shell script actions.

ThisMacMedia="Put your external media volume name here";
ThisUser="Put your short username here";

#   Knowledge of disk management is assumed, including erasing, partitioning, and setting ownership and access.

#==================================================================
# PREPARATION STEPS:
#
#   Make your backups -- failure to do so is on your head!
#
#   These steps use Finder so that you don’t have to even think about permissions. 
#.  Logged on as ThisUser, do the following Finder creates and copies:
#
#   Create folder /Volumes/ThisMacMedia/ThisUser
#   —  The use of ThisUser folder on ThisMacMedia isolates user permissions from volume permissions
#        and keeps the user account files separate from other volume contents. 
#   Create folder /Volumes/ThisMacMedia/ThisUser/Movies
#   Create folder /Volumes/ThisMacMedia/ThisUser/Music
#   Create folder /Volumes/ThisMacMedia/ThisUser/Pictures
#
#   Copy contents of /Users/ThisUser/Movies to /Volumes/ThisMacMedia/ThisUser/Movies
#   Copy contents of /Users/ThisUser/Music to /Volumes/$ThisMacMedia/ThisUser/Music
#   Copy contents of /Users/ThisUser/Pictures to /Volumes/$ThisMacMedia/ThisUser/Pictures
#
#   Make at least a cursory check of the copied files.
#
#==================================================================

# The following steps should be done from administrative account other than ThisUser
# and may require booting from another volume if Mojave security rules interfere with rm commands.

# Remove existing directories in  boot drive ThisUser account folder
sudo rm -rf /Users/$ThisUser/Movies;
sudo rm -rf /Users/$ThisUser/Music;
sudo rm -rf /Users/$ThisUser/Pictures;

# Create Soft Links
sudo ln -s  /Volumes/$ThisMacMedia/$ThisUser/Movies    /Users/$ThisUser/Movies;
sudo ln -s  /Volumes/$ThisMacMedia/$ThisUser/Music        /Users/$ThisUser/Music;
sudo ln -s  /Volumes/$ThisMacMedia/$ThisUser/Pictures    /Users/$ThisUser/Pictures;

exit;
 


The shell you use for your interactive sessions should not impact your scripts. Any script that begins with a line of the form
Code:
#!/bin/sh
will always be executed using the shell specified on that line. If your scripts require Bash, then make sure their first line begins with
Code:
#!/bin/bash
then you can change your login shell to anything you like, and your scripts will still run via Bash....
Apparently I was successful with the change to Bash (I honestly have no reason to prefer one shell over another, I just like to tinker), because the opening script page suggests "To update your account to use zsh, please run `chsh -s /bin/zsh`.
 


Let me see if I understand the shell change correctly:
  • Currently the default interactive shell is Bash
  • The default interactive shell will change to zsh on new installs, or you can change it
  • Scripts that use the bash or zsh shebang will use bash or zsh with full bash or zsh functionality
  • All the scripts I've seen in macOS use a shebang of #!/bin/sh. If the default shell is Bash then the script is using Bash but in a POSIX compliant mode (i.e. it is more closely emulating the original Bourne sh shell).
  • If you change the default shell to zsh, scripts with the sh shebang will run zsh, but in its POSIX compliant mode.
  • When Bash runs in POSIX compliant mode, it doesn't mean that no Bashisms are allowed. It just means that if a script is written to be POSIX compliant, that script should run correctly according to the POSIX shell specifications.
  • I assume that zsh works the same way: when run in POSIX compliant mode it wouldn't reject all zsh syntax.
If all that is true, then it seems to me that since Bash has been the default OS X shell for so long, you could have scripts that are using the sh shebang but still are using some Bash specific syntax. Couldn't those scripts fail to work as expected with zsh as the default shell?
 


It is now particularly important that all scripts begin with a "#!" line specifying the shell to be used to execute the script. Currently, a script without any such line will use bash (probably /bin/bash but I haven't checked), but when bash is removed "in some future version of macOS", that will probably change to zsh (or whatever strikes Apple's fancy at that moment).
A script without any "#!" line at the top will attempt to run in whatever shell you launched the script from. If you are using bash, it will run in bash. If you are running zsh, it will run in zsh. If you are running tcsh, it will run in tcsh.

Needless to say, this can be disaster, because not all shells are compatible with each other (especially across the sh and csh families of shells).

By the way, you can use the "#!" mechanism to specify any application that should interpret the contents of the file. For instance you can put "#!/usr/bin/python" at the top of a Python script, then do a "chmod +x <filename>" to make the file exectuable, and your Python script can then be run like any other CLI command.
 


I've read through/searched the entire Catlina thread here and haven't found anyone mention issues with search in Apple Mail.

I've updated a test system to Catalina and, regardless of what I search for, the results number is always the total number of messages in the inbox at the moment and I never see just those that messages that I should see.

I've done the following:
  • Quit Mail, removed the Envelope Index files, restarted Mail and watched it "Import" the entire message store.
  • Turned Spotlight off, restarted, turned Spotlight back on: sudo mdutil -i off -E /; sudo mdutil -s /; sudo mdutil -i on /; sudo mdutil -s /
  • Disabled Spotlight indexing via System Preferences: drag Macintosh HD to Privacy tab, restart, removed Macintosh HD from Privacy tab.
  • Removed mail account from Internet Accounts, restarted, re-created account in Internet Accounts
Posts in various Apple Discussions show this working for some people (most?), but my message count via IMAP is ~120k and I haven't had any success with the steps outlined above.

Howard Oakley on eclecticlight.co mentions the possibility of a Quarantine flag being set on the files/folders of sandboxed apps (which Mail should be), so I tried removing said flag, to no avail.

Is anyone else having this issue and what have you done to resolve (or not)?

Thanks.
 


It is now particularly important that all scripts begin with a "#!" line specifying the shell to be used to execute the script.
... Unix (and descendants) has had multiple shells for several decades. It hasn't been a good practice to omit the shell specification from the top for just about as many decades.

Mac OS X's default shell didn't start off as Bash, so this is at least the second transition (Bash arrived at Mac OS X 10.3, so folks may have forgotten, or arrived after the transition). Given Mac OS X's Berkeley Unix tie-ins, csh was more aligned with the 'normal' default.
Currently, a script without any such line will use bash (probably /bin/bash but I haven't checked), but when bash is removed "in some future version of macOS", that will probably change to zsh (or whatever strikes Apple's fancy at that moment).
The default shell context is whatever shell you are in at the time, which is the point of the doing the specification, because the user's home/default shell is a settable parameter of the account. It doesn't have to be any specific shell.

Apple doesn't particularly like GPLv3, so Bash is currently stuck on a GPLv2 (bash 3.x), and that gap is getting significant (current version of Bash is v5, so it's about 10 years back now on macOS). This has been coming for a while.
 


.. Apple doesn't particularly like GPLv3, so Bash is currently stuck on a GPLv2 (bash 3.x), and that gap is getting significant (current version of Bash is v5, so it's about 10 years back now on macOS). This has been coming for a while.
Can you tell us the minimum effort path to running Bash v5 on my Catalina system?
 


Another Catalina experience compilation from Michael Tsai: Catalina Vista. The comments from developers are especially insightful.
I think there is too much focus on the release cycle length, which really isn't the root cause. It is more how much is in the release, and how the parts are related. It is also how much of a window they allow for folks to adjust to changes to the foundational elements of the OS stack.

There is always a point in the WWDC roll-out of the updates where there is a slide with all the framework feature changes/additions listed (with a few highlighted that typically got talked about on stage). Rolling out 142 features every 12 months vs. every 18 months is different. Also, there is a difference between updating largely decoupled apps on top vs. the lower-level stuff coupled to a larger number of things layered on top.

The other problem they have is the coupling of WWDC to the release points. Apple now has 5-6 operating systems – iOS, iPadOS, macOS, tvOS, watchOS, services platforms – to cover in a 4-5 day period. Yes, they are related, but they have different tightly bundled apps on top and different couplings to the 3rd-party apps on top (e.g., tvOS).

The foundational change stuff needs a longer (more openly discussed) beta eval period than some highly decoupled, narrow API app does. However, both are thrown into the same beta length window, as though they were homogenous bullet points on a Keynote slide. They aren't.

So, if Apple had a kernel/embedded/"long term" web services "conference" at some other point in time (and just about completely decoupled from shiny new product hardware) and kept WWDC as the synchronized ecosystem event/conference, then the beta (and secrecy) windows would not be overly homogenized. The other minor problem with WWDC is that it has gotten overly coupled to new shiny hardware, as opposed to being a developer's conference. If hardware happens to line up on time, then fine, but they shouldn't be trying to pull/push things into the time window that don't fit.

A principle issue is that the deployed operating systems on are on a mix of older and newer, "sold soon or recently" systems. Where Apple mixes the same secrecy veil uniformly over both, they run into problems. For systems where users have already bought the system (and future upgrades), the significant question Apple doesn't have a uniformly good answer for is, what is that 'buying' them? There is some stuff (usually lower-level and non-GUI) that will never make the WWDC keynote or even the State of Platforms speech nor perhaps even a later break-out session. The more Marketing has a finger on the scale as to content inclusion, then there is probably some "bang for the buck" for putting an ultra secret classification on that. It is more laziness to just throw it all into the same classified bucket.
 



Can you tell us the minimum effort path to running Bash v5 on my Catalina system?
If you are willing to put it into /usr/local/bin or /opt/bin/ then it's not that hard at all via Homebrew or another of the "ports" systems.
Scripting OS X said:
Moving to zsh
You can also download and install a newer version of bash yourself. Keep in mind that custom bash installations reside in a different directory, usually /usr/local/bin/bash.
If you are trying to jam it into /bin then that isn't a good fit at all. If you going to incrementally migrate a shell script collection over to v5, then you could incrementally change the #!/bin/bash preambles and test them out on the new version (and new location).

Long term, there may not be a 'first tier' shell in that /usr/local/bin/ location. The system-"approved" shells are in /etc/shells
and the Apple-controlled file system tree includes /bin , /etc and /usr/bin.

Also, jamming some foreign Bash into /bin/ will probably run afoul of some future security mechanisms in a future OS. I wouldn't count on that as a long-term plan.

If Apple is going to nuke Bash (and Python, Perl, etc.) from their locked-down subtree, it would be helpful if they would put more effort into enabling these third-party Unix toolchain solutions (or perhaps leave some symlink stubs or something like the /var/select/sh mechanism for other pragmatically standard Unix stuff).
 


I've read through/searched the entire Catlina thread here and haven't found anyone mention issues with search in Apple Mail.
I've updated a test system to Catalina and, regardless of what I search for, the results number is always the total number of messages in the inbox at the moment and I never see just those that messages that I should see....
I think (heavy emphasis on think) the problem with Mail search is fixed.

I installed the Catalina Supplemental Update and, after the update restart, search works.

Nothing in the release notes mentioned Spotlight or Mail.

So, either there was a fix for the problem in the update, or another restart fixed the problem.

Cheers
 


Two clients ordered their new iMacs (CTO with 512GB SSDs) a few days before Apple released Catalina. They shipped from Shanghai last week. One of the Macs has arrived and I'll know tomorrow whether it managed to ship out before Catalina was foisted onto the drive. I'm keeping my fingers crossed...
The first one arrived with Mojave. I expect the other will also have Mojave.
 


I've discovered, with the help of several levels of Apple techs, that there is a problem in the current version of Catalina with keeping one's movie folder on an external drive (at least if it's a spinning hard drive).

I thought to save myself a lot of SSD space by moving my movies to an external drive. It turned out to be a massive pain... and they are now back on my internal drive.

First, you cannot merely move all your movies to a folder on the external drive and then "point" to that folder in the TV app – or add them from the Media folder, though that seemed to work at first, as the app "processed" them, but that corrupted the library folder, and the only foolproof way to add them is to drag them into the app window, at which point they copy into your chosen folder, taking way longer than just "processing" them, or, longer yet, downloading them.

And it turns out that re-downloading them is the only way to replace HD movies with the newer 4K versions. But, then, the 4K movies, the ones that show up in the 4K & HDR section of the library, will not play; in fact, they wouldn't even download to the external drive. In the TV app, these files are of the kind "HLS video (purchased)." Sometimes, I could hear the audio of the movie but there was no video...

The tech talked me through a, I thought, brilliant move of changing the preferred Media Files location back to the internal drive, downloading them there, and then resetting the Media Files location to the external drive and dragging them into the app window (placing them in the folder on the external drive). All that worked, but they still won't actually play!
 


... The system-"approved" shells are in /etc/shells
and the Apple-controlled file system tree includes /bin , /etc and /usr/bin.
... solutions (or perhaps leave some symlink stubs or something like the /var/select/sh mechanism for other pragmatically standard Unix stuff).
Apologies. There is a /var and /etc on the Apple system read-only volume, but they bounce through some symlinks and firmlink to the Data volume. Makes sense, since there should only be text-based configuration files in /etc (and mostly similar text-based stuff in /var/). So it is probably in good shape, long-term.

Still some smoothing of the long-term script compatibility pain if #!/usb/bin/bash could be an alias to where it really sits in the future versions of macOS.

The long-term issue to track, though, is just how much will be brought into /usr/local/bin. If the majority of that is applications that are addition to what is in the base /usr/bin /usb/sbin, then that can be stable.

Note also, if you have an "admin" account for a Mac that is separate from the regular account, then that can track what Apple defaults to, because the shell is likely to be present on a clean install – similar to (old time Unix folks) knowing something about vi: it will always be there, versus Emacs, which may not. (Apple's Emacs is another stuck in a pre-GPLv3 time bubble, Pico/Nano, too.)
 


That's not a bug; it's a feature since at least Sierra. By design, macOS now opens a .webloc file using the Default web browser [which can be chosen] in System Preferences > General.
Perhaps not being able to change the default program to open the file is a feature. But the disappearance of the .webloc icon and its replacement by a generic white file icon is certainly not.
 


One other problem I have with Catalina is that it is not downloading my iMessage conversations, though it is giving me notifications of incoming messages. In addition, if I start composing a message to someone, then the conversation with them appears, though their name is never present in the side bar, and the conversation disappears again if I'm not sending a message.

I've tried various combinations of logging in and out of Messages, syncing etc. I'm running the Supplemental Update of Mojave, and when I did the original install, the [installer] got stuck for many hours (something mentioned in the supplemental update's release notes), meaning I had to force-restart the Mac.

Anyone else had a similar problem and managed to fix it?
 


Why not just call it macOS Vista? I am setting up a new Mac Mini. I edit the /etc/nfs_mounts file.

Apple pops up:
Terminal would like to administer your computer...
<Don't Allow> <OK>​
[And I type:]
Bash:
whoami
root
This is not adding security.
 


I've discovered, with the help of several levels of Apple techs, that there is a problem in the current version of Catalina with keeping one's movie folder on an external drive (at least if it's a spinning hard drive).
[Short version:] My 'iTunes' media folder lives on an external spinner. The only issues I'm seeing are with a 4K film purchased in the past week.

Some added notes re the new iTunes:

Music (the app, I don't subscribe to Apple Music):
I've always kept my 'iTunes' folder on an external drive. I wasn't anticipating any issues with this. On first launch of Music after the split, attempting to play a track brought up a dialogue box saying something to the effect that it couldn't find the file. I checked Music > Preferences > Files, and it was pointing to the folder on the external drive. Quit and relaunched Music, and this time all the tracks in the 'songs' view had an '!' in the first column. Checked the external drive, and all the tracks were still there. Back to Music. Clicked on one track, and Music asked me to locate the file. Browsed down through the directory tree and selected it. Music then asked me if I wanted to use this location for all tracks (well, Doh!). Clicked yes, and after a bit of churn, all the '!' disappeared. Sampled some tracks, and everything seems to be working. Album art downloaded over the course of several hours. Album art is not available in 'songs' view! Great programming, Apple.

TV (the app):
The 'iTunes' folder lives on a spinner1.. My video 'collection' has moved from VHS -> LaserDisc -> DVD -> BluRay -> iTunes downloads. My location recently got cable internet with speeds that allow streaming; I still download a copy for those times when cable is down. Wasn't a problem until this past week when I purchased two movies: one HD and one 4K. The HD film downloaded to my local iTunes folder. The 4K film will not. Some interesting points:
1) I did the usual: logout and back into my account; relaunch 'TV'; restart my Mac; wait 24 hours and repeat the above steps. It won't download to my Mac.​
2) It will stream to my Mac.​
3) It will download to my iPad Pro, or at least it does the little circle icon for an hour or so and shows up on my iPad as 'downloaded'.​
4) It does not show up in 'TV' on my Mac when iPad is attached via lightning port.​
5) I did check my external drive's 'iTunes' folder and the 'Movies' folder is there. I noticed that previous 4K downloads (back in the day when iTunes was one) were all 1080p -- I can live with that for backup purposes as I currently stream movies directly from Apple to my iPad (12.3" is fine for me).​

My thoughts are: Apple is saving me from myself by not allowing me to download 4K video to my Mac Mini, because it can't display 4K video. Actually it can, because it's got a 4K Dell display driven by an external GPU. Thank you, Apple.

1. 2TB Toshiba Canvio Advance portable, purchased as an experiment ($65). Bus-powered USB 3. Previously, 'iTunes' media lived on an Icy Dock RAID 1 (two 2TB 3.5" drives). It was noisy, so mostly it was off. Not terribly convenient. It's now serving as backup along with a single 3.5" 2TB drive in an OWC case kept in sealed storage. Yes, I'm paranoid about losing my files. Hurricanes.
 


Can you tell us the minimum effort path to running Bash v5 on my Catalina system?
I ran across this thread:

The upshot of it all is:
  • Compile your own copy from sources. Since most people are not going to be interested in manually porting it, you should use a service that has done the work for you. I see Bash 5 is available from MacPorts and Homebrew. Fink only goes up to version 4.4.18 at this time.

  • Your new copy will not overwrite Apple's, so it will probably end up in /usr/local/bin/bash. In order to allow its use as your shell, you'll need to add a line to /etc/shells specifying your new bash as a valid shell for use as a user's login shell.

    I don't know if SIP or other parts of Apple's security model may make you jump through a few hoops to do this. I also don't know if subsequent system updates may revert the change, so be on the lookout if something breaks in the future. (You may want to also keep around a normally-unused admin account configured for an Apple-approved shell like zsh that you can use to get in and fix this file if/when it gets reverted.)

  • Finally, if your scripts specify a shell (as they should) and you need to force them into using your own bash, then you'll need to update the first line so it is
    #!/usr/local/bin/bash
    Keep in mind that this change will make the script incompatible with other computers that are still using the system bash.
 


Amazon disclaimer:
As an Amazon Associate I earn from qualifying purchases.

Latest posts