4 ms·
I think having persistent access is the file system equivalent of logging in and working entirely from root. The default should be a restricted system, with in
by nomel 7y ago
I think having persistent access is the file system equivalent of logging in and working entirely from root.
The default should be a restricted system, with intentional, temporary, jumps into unrestricted access for making whatever infrequent system configuration changes.
What’s the use case for constant RW access? What changes at this level so frequently?
- Wowfunhappy 7y ago> I think having persistent access is the file system equivalent of logging in and working entirely from root. Except that those system files are already protected behind root privileges, so they're only read-write if I have root. And, one reason the root privilege system works is because temporarily gaining root when necessary isn't painful. I indeed don't change root files on a daily basis, but when I do, I don't want to have to go through an extended rigamarole every single time. Typing in my password should be enough. I totally respect that Apple wants to keep normal users out of this stuff. I just want a way to remove the safety wheels one time, instead of again and again.
- pwinnski 7y agoI've shot myself in the foot enough to appreciate an ever-lengthening list of hurdles I need to jump to do so again. I would be protesting if there were no way to make the rootfs read-write, but as it is I'm happy with having to perform a command or two when I want to write. I suspect you can do that in a launchd script, but however much more involved it is than typing my password, I'm probably fine with leaving it as-is.
- chrisfinazzo 7y agoDisabling SIP, at least from Apple's POV does most of what you want. They've also implored people to be good UNIX citizens and make liberal use of /usr/local, which they explicitly give you - the user of the hardware - ownership of.
- saagarjha 7y ago> They've also implored people to be good UNIX citizens and make liberal use of /usr/local, which they explicitly give you - the user of the hardware - ownership of. /usr/local is root:wheel by default. macOS provides it to you as a place to put your software, but it not give your user ownership of this directory.
- stephenr 7y ago> but it not give your user ownership of this directory. Admin users can sudo, sudo should be used to install software. Your thinking is the shenanigans that Brew does, making `/usr/local/whatever` writable by anyone, without a password. This is not how smart people install software. Edit: wow what a typo. One character completely reversed the intend meaning of the last sentence.
- saagarjha 7y ago> This is now how smart people install software. On the contrary, I think what Homebrew does with regards to permissions is fundamentally incorrect. /usr/local, being shared, should be owned by root, and it should require administrator permissions to install software there.
- stephenr 7y agoGah, sorry typo in my comment, it should say "not", but it says "now. Anyway, I agree, it should be root owned and use sudo/similar to install. Sorry for the confusion!
- fiddlerwoaroof 7y agoIf I shared my Mac with anyone I’d agree, but as it is, my Mac is a single-user machine and I’d rather run brew as myuser:mygroup to avoid running the install scripts as root.
- stephenr 7y ago
- BlackRing 7y agorw file access doesn't mean there's a lack of file level permissions restricting a non sudo user from accessing an otherwise restricted file. case in point: try editing the /etc/hosts file without sudo. you can't save (without invoking sudo from within vim). ro means no matter what I try, that file is ro unless the fs is remounted rw. Again, it doesn't negate file system level user/group permissions. and remounting a system level partition rw isn't something I'd do on a whim. I like the idea of a ro partition for system level OS files, personally, but without user level access somehow - it's not something to be looked forward to.
- Wowfunhappy 7y ago> I like the idea of a ro partition for system level OS files, personally, but without user level access somehow - it's not something to be looked forward to. Apple is clearly stating that the user will have access, so I'm not concerned on that front. What bothers me is the "will revert to read-only after a reboot" part, which seems unnecessarily punitive. It's like Apple is saying "We're going to let you do this thing, but we don't like it, so we're going to make you redo it every single time to remind you of our disdain." Elsewhere in this thread, Pwinnski said he likes having an extra, persistent safety check. I think that's great. But, an extra command line flag to make the setting persistent really shouldn't be too much to ask for. If my launchd idea works in practice, this is all moot, and I retract all my complaints. I'm just nervous.
- saagarjha 7y agoHow often do you need to touch the system partition in the first place? Is this something you need to do every boot?