So another good question this opens up now is whether the version of “bash” in macOS I am using is a recent one, or an old one that might no longer be appropriate to use, or have installed, in some circumstances. I also should add to my previous comment that yet another thing I did yesterday, after finally installing Big Sur, was to change from what has been the new default system user shell in macOS since Catalina, and so now also in Big Sur, called “zsh”, back to my preferred one, “bash”, that was the default one since October of 2003, when “Panther” was introduced as the 10.3 version of OS X (later renamed macOS), and for sixteen years remained the default shell all the way through Mojave. Well, the answer now seems rather more likely to be “Yes” than “No”, after the experience I had going directly from Mojave to Big Sur yesterday. I had been asking a closely related question myself before making the upgrade from Mojave: do I need to upgrade first to Catalina (that I was skipping because it was repeatedly commented as being rather flaky) to make things ready for Big Sur? Although the three were of the same size, so that might be an argument against it. Pmcjr6142: That is a very good question and your reasoning might just explain the second and third downloads I had of the system, not the first one that failed. So: not exactly “I started the download, then installed Big Sur, logged in and everything worked.” Then, with the compilers working, I started testing various applications I use frequently and consequently need them to work. The other needed to have a script modified using something I found, again, looking around in the Web. Then I tried running the two compilers to compile some source files, as a test. That took another half hour, between figuring out what to do and doing it. It worked, only it took over an hour to get all that done, but first I had to create several directories that were missing for the Homebrew upgrade’s install to work. I did that, then tried again to use xcode and then to upgrade Homebrew. Looking around in the web, I decided to install missing tools with “xcode”, but first I had to install some other missing, or in Big Sur obsolete, versions of command tools. So I thought, maybe if I used “Homebrew” to install them again I may get their Big Sur compatible versions, if there are such things?īut it turned out that also did not work. Once back in business, I started by testing the things I most needed to use, my compilers. ![]() ![]() and then started to install and took some 50 minutes doing that. I tried again, and once the third full download ended, magically, the installer asked me if I wanted to proceed to install, I clicked affirmatively, It asked me to accept the EULA, I did, etc. I click a “go ahead” button (by some other name).Īnd it started to download again the 12.44 GB for another hour! ![]() This time it downloaded everything again for another hour and at the end the installer asked me if I wanted to install. The first time ended with an error code that some application was missing. I have tried to upgrade macOS Mojave to Big Sur three successive times last night and each attempt took one hour because it was a full download.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |