Comments by "Scott Franco" (@scottfranco1962) on "DistroTube" channel.

Actually there are a number of issues with the binary (root/user) permissions method, and note that Windows really copied that system. Its not for nothing that hackers talk about "flipping the permission bit". There is no real reason to have a "super" access to everything. There are a number of ways to improve this. 1. Separate the permissions out by type and have users individually obtain each type (like access to a particular disk tree, for example). 2. Stop requiring applications be installed globally. Most applications can be installed in the user directory, meaning that installers don't need root access. 3. Give users the ability to form sandboxes easily. You are installing software. Why does the installer need root permissions? It only NEEDS permissions to its install directory and perhaps a few other resources. 4. Remove the "flip permissions" ability. The OS should not give every user in the system the ability to boost their access level. A better model is to have processes be able to restrict access, but never add it. Thus the root spawns user logins, and a user process can execute a subprocess with less permissions that that, but no process can boost their access back up again. It means if you want higher level access, you have to use a higher level account. The improvement is that there is no way to increase your access level programmatic ally via the OS. None.
6
Linus does not need to change. The world does.
2
Ok, so we are on the same page about Linus. He gets high subscription counts, but he basically takes fairly average facts about Linux and dresses it up with song and dance. That's fine, it just is not interesting to me.
2
I'm sorry, this is idiotic. The github says "it will be archived". Github IS and archive. They are going to erase it? They are going to stop developing and or fixing bugs on it? They can simply turn it over to other interested developers, and it can be forked. There are tons of projects that are no longer being worked on actively. The're still there. This is meaningless, sorry.
1
@user-he4ef9br7z Ok but I stay with my previous answer. If the project has interest, people can step up and handle it themselves. Walking away from a project and locking it up is a pure act of spite, IMHO. In any case, that is why god made forks, you just copy the original project and move on. The whole idea that FOSS can be "removed" from the web makes no sense to me.
1
Python is written in C. I think that says it all.
1
"sudo su". Why? Because I mod the sudoers file to let me sudo without a password, so it is a su without a password.
1
Back to 1985...
1
There are two types of people in the world. Those who classify people into two types, and those who don't.
1
The cat and ls utilities are from the time Jesus used Unix, so staying consistent with their (very old) options and formats was a thing. The --help was because the multiletter options came later, and didn't conflict with the original options. ls has -h, but it isn't help. Cat does not have -h. Why not just "modernize" the ls and cat commands? yea, possible for cat. You don't want to change ls options, its been around forever and probably built into a lot of programs. The --help standard makes sense, its a more modern option format, and Linux/GNU has been trying to normalize the options, starting with more readable multicharacter options. Since the single character options would make Unix/Linux old timers scream if you removed them, that's not an "option" he he. Command line mode is for programmers. Programmers bathe in obscurity and seem to really enjoy it. Its about job security and a general feeling of superiority. Whaddya gonna do?
1
There was a moment in the introduction of Windows NT at a microsoft convention in San Fransisco. The presenter was having an issue with making the graphical interface work, and eventually brought up a command line to fix it. The crowd started laughing.
1
You are in the sudoers file was an authorized user.
1