I tried running a 2nd instance of Roblox simultaneously on macos 15 with another account but this shows up, if my mac can handle it then why can’t it just let me do it? If I have two copies of an app like Roblox in separate User/Applications folders, macos moves them to the /Applications/ folder.

Sometimes it won’t run apps claiming to be corrupted, so I then have to do sudo xattr -cr /Applications/someapp.app in the terminal and they run perfectly fine. It always nags me if I download apps from anywhere but mac app store. Some of these messages can only be gotten rid of by disabling system integrity protection, but then macos blocks you from running MAS apps due to having “permissive security”.

I don’t daily drive macOS anymore, I switched to Linux on my M1 mac where I can do whatever the hell I want.

  • My dislike for MacOS started with this. I had a WordPerfect document, and WordPerfect, but it wouldn’t let me open it because it insisted that it wasn’t a WordPerfect document. And despite the fact that I could open it in WordPerfect on other computers.

    It’s always been this “I know better than you, idiot” mentality that drove me away. I went back, briefly, when businesses started letting employees request MacBooks instead of Windows - given those two options, OSX is preferable. Plus, it was Darwin by then, and the important UI - the shell - was essentially POSIX.

    I well always resent MacOS having the temerity to think it knew better than me, especially in cases when it was wrong but you just could not force it to do something.

    • alansuspect@aussie.zone
      link
      fedilink
      arrow-up
      7
      ·
      4 days ago

      I don’t like Apple, but I like Macs. Obviously macos is better than Windows, but it’s also Linux without the time spent figuring out why something isn’t working.

      I say that as someone who’s had a go with Linux a lot over the years, but for a daily work machine I need the reliability.

      They can piss off with their iClouds and iOS stuff though.

      • Dark Arc@social.packetloss.gg
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 days ago

        I think this is only conditionally true… A good AMD based system on say Fedora with a GPU that’s at least a year old … you really won’t have much of a problem on Linux in my experience or much to fix.

  • Samskara@sh.itjust.works
    link
    fedilink
    arrow-up
    5
    ·
    4 days ago

    While the app running permissions of macOS have become extremely obnoxious, you don’t need to disable system integrity protection. After macOS refuses to open an application, open system preferences -> security and there will be a button that says „open app anyway“, which you then confirm via password or fingerprint.

    • Russ@bitforged.space
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      My memory is probably hazy (it’s been a while since I used macOS) or it might’ve been removed but I recall that you were able to hold a key on the keyboard to bypass it as well. You’d have to right click the application, then hold down the key, and while holding it down click “Open”.

      Said key I believe was the “option” key

      • GenderNeutralBro@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        4
        ·
        3 days ago

        It’s an extra step in macOS 15. You need to go into System Settings now.

        Used to just be able to use the contextual menu to open it and get an approval dialog.

  • Arcane2077@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    6
    ·
    4 days ago

    I’ve never HAD to turn off system integrity for any reason, and I download all sorts of dodgy software from disreputable authors. It’s annoying as heck to micromanage permissions for non-MAS apps but I don’t think disabling integrity is worth it

  • Ephera@lemmy.ml
    link
    fedilink
    English
    arrow-up
    5
    ·
    4 days ago

    We’ve been mucking around with how to pre-configure Raspberry Pis after flashing at $DAYJOB and basically, the way the Raspberry Pi Imager works is that it writes a firstrun.sh onto the SD card which gets run during first boot.

    How does it know to not run that script from the second boot onwards? Well, one of the lines in that script is:

    rm -f firstrun.sh
    

    …it deletes itself while it’s running. 🙃

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 days ago

      That is not a great solution

      I would look into actual deployment tools. Stuff like Ignition, cloud-init and Ansible and your friend.

      • Ephera@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 days ago

        Oh yeah, we only want to pre-configure it with a static IP address on its Ethernet port, so that we can SSH into it in a controlled manner and then we intend to do the rest with a deployment tool.

        • Possibly linux@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 days ago

          That’s not what that is.

          You setup Ansible pull or you use something like Cloud init where you provide a declarative config file. I also think Dietpi has something simular

      • Ephera@lemmy.ml
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 days ago

        Yeah, that is a very good question. It’s one of the last commands in the script and initially I thought they had set up the script so that it would abort, if any of the commands before it would fail.

        But then a colleague pointed out that it’s actually the opposite. So, you can tell the shell to abort execution on error by running set -e. But what they had written at the top was set +e, which explicitly turns that off (even though it should be off by default).
        The last command in the script is also exit 0, so it always indicates success.
        So, yeah, they seem to have knowingly made it so that if the script fails, then it doesn’t retry or anything. It tries to plough through as many of the commands as it can manage (ignoring any that fail on the way) and then it always deletes itself.

        I guess, it’s not as egregious of an assumption, because it only runs on a fresh OS. That’s a pretty controlled environment to be executing in, so the chance of something going wrong is rather low.
        Well, and the other question is what else would you do? If the script fails and you don’t delete it, it’s going to re-run on the next boot. What’s going to be different on the next boot to make it succeed then? Might as well do as much as you can and then quit…

  • quartz@kbin.earth
    link
    fedilink
    arrow-up
    5
    ·
    4 days ago

    i remember on OSX elcapitan I just had to duplicate and rename an app to launch it twice and run it in parallel. But maybe you can’t do it anymore ?