281–290 of 298 posts
Earlier quoted context omitted.
Being required to reboot my computer into recovery mode just to add a directory is certainly a WTF worthy situation. BTW, thanks for the down vote?
No, it's not. Mainly because it's not just "adding a directory"
Earlier quoted context omitted.
Being required to reboot my computer into recovery mode just to add a directory is certainly a WTF worthy situation. BTW, thanks for the down vote?
99.99% of users will never need to touch those system directories, (They aren't even required for homebrew), and, at the same time, writing to them poses a huge gaping security hole for all OS X users. Locking them down (particularly in a way that can be trivially reversed with a user who has physical possession of the device and the password) is the right thing to do. For the 0.01% who need to screw around with the…
Sorry, but I can't resist mentioning that there's no need for that `cd /`; `sudo find / -cmin -5` would work just fine.
It does kind of make sense to me that user-owned things should kind of live in /Users/username. Unfortunately that pattern in this case would lead to the redundant-seeming /Users/username/usr/local, but at least that's rooted to the user in the event other users don't want a "global" Homebrew install. Also, I believe (even if it kills some ignorant build scripts) that Homebrew lets you reconfigure where this director…
It's very common for linux applications to store stuff in $XDG_DATA_HOME (~/.local/share by default) (config files and caches go somewhere else) In my ~/.local I also have a bin/ directory (created by some Haskell tool), so rather than putting stuff in /Users/username/usr/local, I think it might make more sense to recreate the (needed parts of) a unix fs hierarchy in /Users/username/.local There's also ~/LibrarySuppo…
You're probably thinking of `~/Library/"Application Support"`.
Earlier quoted context omitted.
I bought a new Air in mid September. I was a little annoyed that documentation seemed out of date, but it took all of five minutes to fix this. No song and dance needed, just a sudo mkdir.
But his comment refers to the new OS changes I believe thus it's going to be a pain going forward.
Earlier quoted context omitted.
You'd run into exactly the same problem. Apple doesn't provide /brew in the default image, so something would have to create a new inode in /, and that something presumably requires SIP be disabled (assuming / is protected in SIP at least). Even if it worked, you'd be no better off than just using ~/.homebrew or something like it. Their whole reason for wanting /usr/local is that (a) /usr/local/bin is in the default…
> You'd run into exactly the same problem. I think you misunderstand the problem. /usr/local exists in OSX, and is one of the recommended install locations for user software. But if you change the permissions on /usr/local, OSX will interpret that as damage and fix it. Homebrew does this, which is in conflict with all uses of /usr/local in Unix history. > and (b) it can be written to by a normal user. Critically, no.…
It is entirely possible I misunderstood SIP. The first thing I did was disable it, and I haven't bothered any more about it. My impression though was that it locked down all "system directories", however Apple chooses to define that. Which would disallow changing the permissions on /usr/local, but also would disallow creating new files or directories under a protected directory. Is that not what it does?
Earlier quoted context omitted.
No, it's not. Mainly because it's not just "adding a directory"
"mkdir /usr/local" is just making a directory. It's not like that suddenly triggers your battery to overheat and explode.
Earlier quoted context omitted.
They want /usr/local to be owned by you.
That kind of blows my mind... why not use homedirs instead of abusing global paths!?
Earlier quoted context omitted.
Unless you're making iOS software, why not just use Linux? I always have Ubuntu Server running in the background in a VM, so I get the desktop experience that I prefer (Windows) and a better Unix experience than OS X provides.
OS X has always provided a fine Unix experience for me.
Enjoy using Apple's computers...and they are Apple's, not yours because if they were, you'd be in control.