News for hackers. Stuff that matters.
Re:What’s New in macOS Big Sur: Human Interface Guidelines by breakfastduck on Monday June 22, 2020 @06:30PM (#23607677)
I disagree, I don't think they're anywhere near locking down to the iOS level.

Could you explain some of these incremental lock downs? I honestly can't think of any that are genuine restrictions, but that might just be because I don't encounter them with what I do.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by 72deluxe on Monday June 22, 2020 @07:56PM (#23608375)
How about the non-modifiable hidden system partition? Inability to create directories under /

That alone has stopped me moving my Macs to the latest OS after testing.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by chipotle_coyote on Monday June 22, 2020 @08:36PM (#23608716)
I'm genuinely curious: why do you want to create new directories at the root level? Is this something you're just used to doing and it breaks your customary way of working? Is it a "general principle" thing (which I suspect is a lot of the objection the HN crowd really has at the root, no pun intended)? I've been using OS X-based Macs since 2002 and used Linux and FreeBSD for a decade before that, and I don't recall ever having an actual need to create a root-level directory.
Re:What’s New in macOS Big Sur: Human Interface Guidelines by perryizgr8 on Monday June 22, 2020 @09:42PM (#23609121)
> why do you want to create new directories at the root level?

Why not? It's his system, he should be able to do whatever he likes. On most Linux I can rm -rf / all day long and nobody cares. What's the problem with creating root level directories?

Re:What’s New in macOS Big Sur: Human Interface Guidelines by chipotle_coyote on Tuesday June 23, 2020 @12:22AM (#23609896)
I didn't say there was a problem with it; I just asked what the reason for wanting it was.

> On most Linux I can rm -rf / all day long and nobody cares.

So let me turn this around: Why do you think a system that doesn't make it difficult to completely destroy it with one command is a bad idea? "It's my system, I should be able to do whatever I like" is an answer, to be sure.

(N.B.: in fact, "rm -rf /" won't work without "--no-preserve-root" in most Linux distributions, AFAIK, and I presume sudo.)

Re:What’s New in macOS Big Sur: Human Interface Guidelines by 72deluxe on Tuesday June 23, 2020 @06:46AM (#23612205)
DOS survived perfectly fine with deltree, whereupon it was possible to delete your file system.

The decision on which bits of the system I can destroy should be mine, not theirs. That's the issue. At the moment, I am getting pushed out of my machine, bit by bit. Every binary I run is getting report to Apple etc.

It is also possible to destroy the system by dropping your MacBook from a very great height. Should it be padded to cope with this eventuality?

Re:What’s New in macOS Big Sur: Human Interface Guidelines by suyjuris on Tuesday June 23, 2020 @05:49AM (#23611789)
> Why do you think a system that doesn't make it difficult to completely destroy it with one command is a bad idea?

This does not seem very charitable.

It is fine if the system warns you about doing potentially dangerous operations (which --no-preserve-root amounts to) but it must not prevent you from ignoring that warning.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by perryizgr8 on Tuesday June 23, 2020 @07:26AM (#23612502)
Well I make all my directories in C:/ or / just because the paths are shorter to type. That's one reason.
Re:What’s New in macOS Big Sur: Human Interface Guidelines by 72deluxe on Tuesday June 23, 2020 @04:52AM (#23611410)
I put all developer libraries that I do not want to put into a system path into /DevelopLibs. On Windows I put them in C:\DeveloperLibs. That way I can build supporting libraries of different versions software under there, eg. /DeveloperLibs/abc-1, /DeveloperLibs/abc-2 and test that I have a self-contained executable that runs on my development system without relying on anything in $PATH.

It was a habit on macOS since /Developer used to be where xcode lived until they moved it to /Applications.

It also makes it easy to look in the /DeveloperLibs directory and see if I've got all libraries I need on this machine (I have different development machines under different OSes).

Removing ability to create directories under the root seems draconian for no good reason, other than the iOS-ification of my machine. Not Apple's machine - my machine.

I don't understand why people would ask "why would you want to do that?" because everybody used to defend the ability to only resize windows from the bottom right corner under macOS until a few versions ago, when it became obvious that resizing a window from any edge was a good idea and always had been. But people oddly defended it for decades before that.

What if they now remove the ability to change your desktop wallpaper? Would we all say "but why would you want to change your wallpaper?"? We seem to accept the gradual lock-down of our own machines. Apple users (and I am one) seem to be the most defensive of the company's behaviours and it doesn't make sense - we just have to accept it.

If Microsoft removed the ability to create a directory under C:\, what would the result be? Would we be asking "but why would you want to create a directory under C:\?"? I think not. It'd be the apocalypse.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by chipotle_coyote on Tuesday June 23, 2020 @03:00PM (#23618588)
As happymellon noted, I just use /opt when I need to.

There are certainly many decisions Apple makes that I don't like and I am always keeping my eye on Linux in case I really feel the need to pull the rip cord. But for me, this is just not a hill of sufficient size to die on. "Apple now mounts the system partition as read-only" just doesn't feel like a slippery slope that leads inexorably to... well, I'm not really sure where people imagine it's going. "This is something I used to be able to do and now I can't and soon that means I won't be able to open a shell!" I mean, maybe, but... probably not. If I had to choose whether "Macs in five years will only be able to install programs from the Mac App Store" or "iPads in five years will be able to install programs from places other than the iOS App Store" is more likely, I'd honestly go with the latter.

> I don't understand why people would ask "why would you want to do that?"

I guess I don't understand why asking the question is controversial; I'm not trying to lead anyone into a rhetorical trap that forces them to admit only axe murderers would ever use this functionality. :) It's simply that in what I'm pretty sure is over a quarter-century of Unix use on my part I don't recall ever putting anything in the root directory of any of my systems except by mistake.

As for "defending the ability to only resize windows from the bottom right corner until a few versions ago," your memory of this is different from mine, I suppose. I recall a lot of Mac users thinking that Apple's one-corner-only approach was a bad leftover from the pre-OS X days that needed to change!

Re:What’s New in macOS Big Sur: Human Interface Guidelines by happymellon on Wednesday June 24, 2020 @12:27PM (#23630002)
Yeah, TBH I think that more file systems should be mounted as RO by default, and only moved to RW during an operation then restored to RO post system activity.

It would get rid of shitty Mac application documentation that rather than installing itself in correct locations, has troubleshooting steps like:

> Just chown your entire `/` to your current user and `chmod +w *`...

Until Atomic installations become the norm like SilverBlue its probably a good step.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by happymellon on Tuesday June 23, 2020 @08:36AM (#23613034)
So two things here. The first is that it sounds like you want to be using `/opt`.

The second, is that I am able to create root folders, I just have to remount as rw before creating it and after that I can mount any data folder to `/foo`. I'm not entirely clear why not having `/` as rw by default is such an issue, but you are cetainly not prevented from doing it if you wanted to.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by henriquez on Monday June 22, 2020 @10:13PM (#23609274)
I put symlinks in the root directory for my commonly used paths. Or I did before Catalina. Yes it’s kind of a dumb thing but it also seems dumb and arbitrary that I’m no longer _allowed_ to.
Re:What’s New in macOS Big Sur: Human Interface Guidelines by raxxorrax on Tuesday June 23, 2020 @03:18AM (#23610795)
> I'm genuinely curious: why do you want to create new directories at the root level?

Why would Apple want to restrict access to certain memory locations?

Re:What’s New in macOS Big Sur: Human Interface Guidelines by thoughtsimple on Monday June 22, 2020 @08:27PM (#23608632)
Turn off System Integrity Protection. Not a good idea but it will let you make unnecessary changes to /.
Re:What’s New in macOS Big Sur: Human Interface Guidelines by filleduchaos on Monday June 22, 2020 @08:36PM (#23608708)
All they really did was make it harder to thoughtlessly do. If you can't cope with the procedure needed to make changes to the write-protected folders, maybe whatever it is you wanted to write there isn't actually that important.
Re:What’s New in macOS Big Sur: Human Interface Guidelines by 72deluxe on Tuesday June 23, 2020 @04:58AM (#23611458)
That doesn't make sense. What is in / that is dangerous?

Finder hides all of /etc and /bin and /usr for the "protection" of normal users, just like the default view for Windows Explorer under C:\Windows\System. But you can still change the contents on Windows, or see the directories in Terminal on macOS.

Should they hide those directories when you use Terminal too? After all, /etc is important. Your reasoning would also stand up there - perhaps whatever files you were attempting to modify under /etc wasn't actually that important.

When does the "you cannot easily modify files on your own machine" stop?

Would you also accept the inability to change your wallpaper with such glee? Perhaps the wallpaper you wanted wasn't actually that important.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by filleduchaos on Tuesday June 23, 2020 @05:33AM (#23611673)
> What is in / that is dangerous?

...it's...the root of your entire system? Are you really asking me why `rm -rf /` is a meme, or are you just being contrarian?

> Finder hides all of /etc and /bin and /usr for the "protection" of normal users

And you can change Finder's preferences to show those folders, like any actual macOS user that's qualified to be making changes to those folders should know. If you lack both the curiosity and the ability to look up how to enable that option, then you frankly have no business modifying them yourself. If whatever you wanted to copy or edit there wasn't important enough for you to take ten seconds to look up how to do it and then follow through with the instructions, then why on earth would you be complaining about it to anybody?

Re:What’s New in macOS Big Sur: Human Interface Guidelines by 72deluxe on Tuesday June 23, 2020 @06:42AM (#23612164)
I'm not being contrarian, I am asking why I wouldn't be able to modify my filesystem. It's quite simple.

I can also do rm -rf ~/Documents or rm -rf /Applications or rm -rf /Library which has a similar devastating effect to my life/machine - should we block that too?

I can also fling a hammer into the screen and break the screen - should we put extra thick glass on the screen? I guess I have no business using a MacBook if it is possible to break the screen.

I can also pour liquid into the keyboard - should the keyboards be waterproof? I guess I am not qualified to use a Macbook and have no business using one if I spill a drink.

Using the keyboard is dangerous too because someone can type dangerous commands. Let's stop people using it. Only those with sufficient "curiosity" and those "qualified" should use it, right? How do I get "qualified"?

I am saying that as it is my machine, I get to decide which parts are dangerous. But I no longer can because someone the other side of the world has decided that I am cannot create a directory under /.

I do not ever modify /etc using Finder. Should I only be allowed to edit files under there using Finder or is Terminal permitted?

I guess if we follow this "lock down" and "only those qualified" route that you encourage, we'll soon see permission prompts to do anything anyway.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by Xylakant on Tuesday June 23, 2020 @05:10AM (#23611531)
> That doesn't make sense. What is in / that is dangerous?

There have been examples of (un)installer scripts removing substantial parts of your system, steam for example. Linux in this case https://github.com/ValveSoftware/steam-for-linux/issues/3671, but not generally unthinkable on MacOS. It's generally good if the system puts up barriers to prevent such occurrences.

You're entirely welcome to disable these protections, but MacOS is designed to protect Joe User who may have substantially less knowledge and who has no general need to mess around in /etc

Re:What’s New in macOS Big Sur: Human Interface Guidelines by 72deluxe on Tuesday June 23, 2020 @06:50AM (#23612237)
It seems to be solving a problem that doesn't exist, as if edge cases were the reason to apply blanket restrictions.

It's like banning knives because there's been a few stabbings. It removes the general utility due to misuse by a few.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by viro on Tuesday June 23, 2020 @09:56AM (#23613964)
"solving a problem that doesn't exist" ... um I nuked plenty linux machines by removing the wrong file early in my linux days. Hell I nuked a couple OS X machines when I first got Mac. Turning off SIP isn't that hard ... if you consider it hard you probably need to keep it on.
Re:What’s New in macOS Big Sur: Human Interface Guidelines by 72deluxe on Thursday June 25, 2020 @09:13AM (#23640308)
But typing the correct command also isn't that hard!
Re:What’s New in macOS Big Sur: Human Interface Guidelines by mayoff on Tuesday June 23, 2020 @03:33AM (#23610888)
man synthetic.conf:

> synthetic.conf describes virtual symbolic links and empty directories to be created at the root mount point.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by saagarjha on Tuesday June 23, 2020 @06:58AM (#23612298)
That doesn't actually create real directories; it's just symbolic links. For certain use cases (nix) this isn't enough.
Re:What’s New in macOS Big Sur: Human Interface Guidelines by lwhi on Monday June 22, 2020 @06:39PM (#23607771)
Every new release of OS X has been an increasing disappointment for years now. Security issues, bugs, incompatibilities.

It's almost as if they've been actively devesting in OS X.

At least we now understand why.

Mac's are no longer machines fit for professional development. It's a damn shame, but it's true in my mind.

Re:What’s New in macOS Big Sur: Human Interface Guidelines by saagarjha on Monday June 22, 2020 @07:44PM (#23608296)
They just switched Macs to an entirely new architecture. I think they probably put more effort into macOS than iOS this year.
Re:What’s New in macOS Big Sur: Human Interface Guidelines by lwhi on Tuesday June 23, 2020 @06:47AM (#23612216)
That's not my point. This new OS version is not OS X.
Re:What’s New in macOS Big Sur: Human Interface Guidelines by saagarjha on Tuesday June 23, 2020 @06:49AM (#23612235)
Neither was the last one!
Re:What’s New in macOS Big Sur: Human Interface Guidelines by lwhi on Tuesday June 23, 2020 @08:01AM (#23612733)
The 10 in the version number is a clue[1]

[1] https://en.m.wikipedia.org/wiki/MacOS_Catalina

[dead]
Re:What’s New in macOS Big Sur: Human Interface Guidelines by viro on Tuesday June 23, 2020 @10:02AM (#23614017)
You got down voted because you didn't say anything. Go ahead read it again, I'll wait. Notice how the closest you got to making a point was Macs are not "fit for professional development"
Re:What’s New in macOS Big Sur: Human Interface Guidelines by lwhi on Tuesday June 23, 2020 @10:15AM (#23614158)
I disagree and I think you're incorrect.

For a long time, I and other people I know chose MBP for professional web-development / video editing / music production because they were provided with a slick GUI on top of a solid operating system.

It's fairly apparent to most people who read tech news, that the quality of the operating system isn't what it was. For instance, think back to the 'no password necessary for root user' debacle a few years ago.

I don't think it's beyond the realms of credulity to consider why this type of problem was allowed to occur in Apple's 'professional' line.

If you're still with me, perhaps you'd also be able to follow my line of reasoning when I surmise that the reason for this degradation of support, may have been because they were planning on dropping their support for OS X .. with this convergence event being its replacement.

In reality, it's your own sassy comment that's devoid of content. Hope you really did wait! :)