macOS 15 Sequoia on Unsupported Macs Thread

[MacinMan]

SIP not simple on/off status. The csrutil command only look at subset of SIP settings when returning enabled/disabled.

That's the part I'm a bit unclear on. According to OCLP, when I toggled the settings, the configuration was 0xfff, which according to an open core related page on Reddit, means SIP is fully disabled, and when I rebuilt Open core, and rebooted, the status shows everything disabled. What I'm trying to find out, is why is csrutil still saying I have a custom / unknown configuration, when I just want SIP completely disabled? Is it because of the sealed snapshot issue, where the volume isn't sealed? I'm not as familiar with the internal workings with macOS anymore, like I used to be in the days of of Snow Leopard, and earlier. For many years, I've just used the OS as Apple has removed a lot of the ways to customize and tweak things. Even with a native installed copy of macOS in terms of permissions and setup, I've mainly wanted to use macOS as a Unix environment with the familiar Mac desktop. The only reason I've left SIP enabled was because I have read, that disabling it can stop certain things from working. If that's not the case anymore, and I can disable SIP completely and still have things work, I'd much rather get rid of as much Apple-specific stuff as possible, and just use it as I would Linux, or any other Unix based OS, with only the specifics I need that make macOS worth it to me over the other options. Initially my understanding of disabling SIP, would remove Apple specific security, and give me more of a standard Unix environment.

 

[macpro_mid2014]

That's the part I'm a bit unclear on. According to OCLP, when I toggled the settings, the configuration was 0xfff, which according to an open core related page on Reddit, means SIP is fully disabled, and when I rebuilt Open core, and rebooted, the status shows everything disabled. What I'm trying to find out, is why is csrutil still saying I have a custom / unknown configuration, when I just want SIP completely disabled? Is it because of the sealed snapshot issue, where the volume isn't sealed? I'm not as familiar with the internal workings with macOS anymore, like I used to be in the days of of Snow Leopard, and earlier. For many years, I've just used the OS as Apple has removed a lot of the ways to customize and tweak things. Even with a native installed copy of macOS in terms of permissions and setup, I've mainly wanted to use macOS as a Unix environment with the familiar Mac desktop. The only reason I've left SIP enabled was because I have read, that disabling it can stop certain things from working. If that's not the case anymore, and I can disable SIP completely and still have things work, I'd much rather get rid of as much Apple-specific stuff as possible, and just use it as I would Linux, or any other Unix based OS, with only the specifics I need that make macOS worth it to me over the other options. Initially my understanding of disabling SIP, would remove Apple specific security, and give me more of a standard Unix environment.

In my opinion, if you just want to have total control on your system and still have a macOS desktop like working environment, I suggest you switch completely to Ubuntu and use something like this video shows

How to Make Ubuntu Look Like MacOS SEQUOIA​

(

), instead of keeping disabling all security stuff implemented on macOS.
By using Ubuntu (or any other Linux distro) you can keep your working environment with its toughest security implementation without compromising your personal data.

 

[TOM1211]

In my opinion, if you just want to have total control on your system and still have a macOS desktop like working environment, I suggest you switch completely to Ubuntu and use something like this video shows

How to Make Ubuntu Look Like MacOS SEQUOIA​

(

), instead of keeping disabling all security stuff implemented on macOS.
By using Ubuntu (or any other Linux distro) you can keep your working environment with its toughest security implementation without compromising your personal data.

I thought this is all that is needed to make it look like Tahoe on my Mac with sequoia rather than updating , technically “as far as I’m aware there’s no real new “features” for Intel Macs just a nice theme which is easily enough to do.

 

[MacinMan]

In my opinion, if you just want to have total control on your system and still have a macOS desktop like working environment, I suggest you switch completely to Ubuntu and use something like this video shows

How to Make Ubuntu Look Like MacOS SEQUOIA​

(

), instead of keeping disabling all security stuff implemented on macOS.
By using Ubuntu (or any other Linux distro) you can keep your working environment with its toughest security implementation without compromising your personal data.

I have Kubuntu set up on an external drive, the main reason I keep macOS around is for features like text message forwarding, so, technically I don't need to use Open core at all, as that still works in Monterey. The main reason I wanted to try Sequoia and really give OCLP a fair chance is a few apps now require Ventura, or newer. Text message forwarding for me, is more of an accessibility feature, as I find it hard to type on a touch screen, and voice dictation isn't always accurate, so have a physical keyboard helps. Also in terms of Linux, I think for the best experience with it, I would still need a new computer because I've had hardware quirks to work around on this iMac, this are Apple specific, so, even though I've got everything working now, and it's stable, the only thing I haven't been able to do is get Linux to use the full 5k display, it runs in 4k, which is fine, but the scaling doesn't work as it should, and I think that's due to lack of the display not running in full 5k. Also the audio doesn't work right without quirks installed for the kernel.

So, I'm stuck between two worlds, and not sure which choice to make moving forward

 

[Bigwaff]

To understand more about this, I recommend you take a look at Mykola's Blog, where he explains all about SIP:

System Integrity Protection: The misunderstood setting

For the number of years I’ve been in the macOS community, one fact has always stayed consistent: Developers and users don’t understand what System Integrity Protection really is. Thus in today’s blog post, I want to clear up some misconceptions about this setting in macOS and propose better ways...

khronokernel.com

Enjoy the reading..

That's the part I'm a bit unclear on.

@macpro_mid2014 provided link to khronokernel blog explaining SIP in explicit detail. It has answers.

 

[MacinMan]

@macpro_mid2014 provided link to khronokernel blog explaining SIP in explicit detail. It has answers.

Sorry, somehow I missed the Link. I have read his Blog before, but it's been a while. I'll look over it now. By the way, after turning off all the boxes in the OCLP settings, rebuilding OCLP, and rebooting the OS feels much smoother and faster without SIP enabled.

 

[MacinMan]

OK, after reading the blog over again, I think I need to change the question(s) I'm asking.

I think a better question in my situation is, how many of the changes I've experienced, and issues / incompatibilities that have come as a result, are OCLP related vs the changes Apple has made to macOS? E.g, how much of this stuff would I have to deal with with a new supported mac vs just staying on older versions regardless if apple supports them or not. Especially until I can find software I'm happy with that works going forward, and also in terms of my niche stuff like cross platform gaming, what should I do as a solution for keeping 32-bit compatibility for older DOS and windows games / software, and good windows compatibility such as proton, etc.
Basically All I want is a good balance between legacy support, and enough to be current (if needed.)

 

[MacinMan]

OK, I did some testing in my Sequoia install which is an APFS volume on the same drive as the main Monterey install. I installed my Epson software drivers for my ET 2800 series, and my Perfection V600 scanner, and everything seems to work. The thing that really made me question if the system was working correctly, or not in regards to permissions is:
Many of Epson installer packages, behave differently under Sequoia than Monterey, for example under Monterey, it just goes through the standard screens of where it will be installed, agree, enter the password for admin, and done. Under Sequoia, it adds the screen saying who do you want it installed for, and for all users is the default, and since some of the installers took slightly longer than on Monterey, I wasn't sure if this was a difference in the version of macOS, or if OCLP was doing something to the system where it wouldn't be reliable. Everything works, so I'm guessing it's mainly a difference in the versions of macOS, but that's why I specifically asked how can I know what's causing the difference in expected behavior, since I don't have newer mac to test with right now. This is also why I asked How I can get as close as possible to a standard setup with OCLP by disabling SIP, since it's not possible to fully enabled it with a patched OS.

As far as printing, I was able to do my test patterns through Preview as normal.

By the way, the GPU related stuff I've figured out how to work with, so it's not as much of a limitation. So, now it's permissions and overall functionality of newer versions of macOS I'm still trying to sort out.

Also after using Sequoia for a while as a daily OS, there really isn't anything it has that I need on a daily basis over Monterey. The two main things I've seen in my case, is simply being able to update apps to the latest version. Even with that though, at this time, the differences are usually very minor, and not worth relying on an unsupported configuration for. At least not without a supported install to go back to.

 

[xboxbml]

OK, I did some testing in my Sequoia install which is an APFS volume on the same drive as the main Monterey install. I installed my Epson software drivers for my ET 2800 series, and my Perfection V600 scanner, and everything seems to work. The thing that really made me question if the system was working correctly, or not in regards to permissions is:
Many of Epson installer packages, behave differently under Sequoia than Monterey, for example under Monterey, it just goes through the standard screens of where it will be installed, agree, enter the password for admin, and done. Under Sequoia, it adds the screen saying who do you want it installed for, and for all users is the default, and since some of the installers took slightly longer than on Monterey, I wasn't sure if this was a difference in the version of macOS, or if OCLP was doing something to the system where it wouldn't be reliable. Everything works, so I'm guessing it's mainly a difference in the versions of macOS, but that's why I specifically asked how can I know what's causing the difference in expected behavior, since I don't have newer mac to test with right now. This is also why I asked How I can get as close as possible to a standard setup with OCLP by disabling SIP, since it's not possible to fully enabled it with a patched OS.

As far as printing, I was able to do my test patterns through Preview as normal.

By the way, the GPU related stuff I've figured out how to work with, so it's not as much of a limitation. So, now it's permissions and overall functionality of newer versions of macOS I'm still trying to sort out.

Also after using Sequoia for a while as a daily OS, there really isn't anything it has that I need on a daily basis over Monterey. The two main things I've seen in my case, is simply being able to update apps to the latest version. Even with that though, at this time, the differences are usually very minor, and not worth relying on an unsupported configuration for. At least not without a supported install to go back to.

Right.. I went back to Monterey finally.. I think I'm done playing in OCLP/Sonoma/Sequoia, at least until I get a new Mac... which will probably be a while yet..

 

[ronton3]

Seq 15.6 b2 is available.

 

[MacinMan]

Right.. I went back to Monterey finally.. I think I'm done playing in OCLP/Sonoma/Sequoia, at least until I get a new Mac... which will probably be a while yet..

Have you found anything that you use, no longer works in Monterey going forward? I have a few little apps that dropped support, but nothing I would demand to have the latest version of for daily use. Also for the DRM issues, because you've also been affected by that, I don't use Apple TV on the computer, I use the TV for that because of lack of HDR support on the computer, and also the larger screen is more comfortable to watch from a distance. However, prime works fine on Firefox, and chrome when I've tested it, and since the computer isn't my primary viewing for commercial content, in a pinch, it works for streaming in HD, and downloads in SD, so the only thing that doesn't work for me is downloading content in HD from iTunes. (Just providing feedback here.). The one thing I'm still getting used to, and really don't like is how Apple has rearranged the settings and security settings. Things were much easier to find and remember in older versions of system preferences. So for me, it's not just about OCLP, and unsupported macs. It's also about the changes Apple has made to the OS, that I personally don't want, or need.