laurelraven
I miss those old logos, the new ultra flat ultra simple logos are just so uninteresting compared to that era
Out of curiosity, what do you recommend? Last time I went looking the options sucked (though part of that was we still had a landline and that seriously limits your choices)
At no point has Microsoft gotten me to regret my decision to install Mint
Make necessary infrastructure municipal utilities... Water, gas, electric, telephone, Internet... If you need it to participate in society, it shouldn't have a profit motive attached, period.
Every few months I check to see if anyone's built fiber to my area or if I'm still stuck with the choice between shit tier cable marketed as 1.2gbit (but rarely even gets halfway there, often below a tenth of that), something else that's barely better than what we had twenty years ago, and wireless claiming to be 5G but performs like crap for everyone I know who's tried it
I've only been looking for the last dozen or so years...
So damned sick of the bureaucratic bullshit
I've heard this but don't really understand it... At a high level, what makes cuda so much better?
Yeah, but who wants their car to look like a Tesla? ;)
I don't think anyone is suggesting otherwise, but continuing to say that as a reason not to work towards that goal makes no sense
Hell, I could just bolt a laptop to the dash if I really wanted that
While that's literally what it is, that's not really how it's represented and requires also understanding binary numbers.
Even knowing that, I've always found it easiest to get to the permissions the way I described, which when you think about it is actually the same as what you'd do to translate binary into decimal/octal if you don't have them memorized: look at the values of each position that's set to 1 and add them together. So, 101 in binary would be 4+0+1, or 5, which is the same as saying read is 4 and execute is 1 and add them together, the latter of which I think is easier to learn (and is how I've always seen it taught, though clearly YMMV)
Both get you to the same place though
Quick and dirty: the basic permissions are read, write, and execute, and are applied to the owner, the group, and everyone else. They're applied to all files and directories individually.
It's represented by a 3 digit number (in octal, which is base 8, so 0 to 7). The first number is the permission given to the file's owner, the second to the file's group owner, and the third to everyone else. So, the owner of the file is the one user account that owns it, the group applies to all members of that group. User and group ownership are also applied to each file and directory individually.
Read, write, and execute are represented by the numbers 4, 2, and 1, respectively, and you add them together to get the permission, so 0 would be nothing, 1 would be execute but not read or write, 2 would be write but not read or execute (and yes there are uses for that), 3 would be write and execute but not read, 4 is read only, etc through to 7 which is basically full control.
This will take a little bit to make sense for most people.
chmod (change modifier, I think) is the program you use to set permissions, which you can do explicitly by the number (there are other modes but learn the numbers first), so chmod 777 basically means everyone has full control of the file or directory. Which is bad to do with everything for what I hope are obvious reasons.
chown (change owner) is the program you use to set the owner (and optionally the group) of a file or directory, and chgrp (change group) changes the group only.
It gets deeper with things like setuid bits and sticky bits, and when you get to SELinux it really gets granular and complex, but if you understand the octal 3 digit permissions, you'll have the basics that will be enough for quite a lot of use cases.
(Additionally to the 3 digit number, permissions can be represented a bit friendlier where it just lists letters and dashes, so 750 (full control user, read and execute group) could be shown as rwxr-x---, where r=read, w=write, and x=execute, and what they're applied to can be represented by the letters u for user (aka owner), g for group, and o for other)
This goes into more detail of those basics: https://opensource.com/article/19/6/understanding-linux-permissions