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.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.
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.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'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.Apple Support said:
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.Objective Development posted an interesting blog entry:
I received this today from Bombich Software, Inc. which produces Carbon Copy Cloner:... 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.
Oct 16, 9:22 AM EDT
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.
Yes that's all part of the locking down that's going hand in hand with APFS groups.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).
Bombich Software, Inc.
The shell you use for your interactive sessions should not impact your scripts. Any script that begins with a line of the formThe 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.
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.)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.
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.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.
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.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?
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 220.127.116.11), this is how:... 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.
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.
Drive Genius v5 will not support macOS 10.15 Catalina.
The following are known issues:
We are working on full 10.15 support for Drive Genius v6, and will update as further information becomes available.
- 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.
So, this doesn't work in Catalina?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.
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.… 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.
Here's some Apple Catalina documentation implying that FireWire should work....
I guess this doesn’t address booting from FireWire drives, though.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.
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.
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.Here's some Apple Catalina documentation implying that FireWire should work....
I guess this doesn’t address booting from FireWire drives, though.
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".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.
#!/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;
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`.The shell you use for your interactive sessions should not impact your scripts. Any script that begins with a line of the form
will always be executed using the shell specified on that line. If your scripts require Bash, then make sure their first line begins withCode:
then you can change your login shell to anything you like, and your scripts will still run via Bash....Code:
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.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).
sudo mdutil -i off -E /; sudo mdutil -s /; sudo mdutil -i on /; sudo mdutil -s /
... 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.It is now particularly important that all scripts begin with a "#!" line specifying the shell to be used to execute the script.
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.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).
Can you tell us the minimum effort path to running Bash v5 on my Catalina system?.. 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.
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.
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.
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).Scripting OS X said:
I think (heavy emphasis on think) the problem with Mail search is fixed.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....
The first one arrived with Mojave. I expect the other will also have Mojave.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...
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.... The system-"approved" shells are in /etc/shells
/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).
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.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.
[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.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 ran across this thread:
As an Amazon Associate I earn from qualifying purchases.