All parties in the matter of Sudo v. Root Account please rise...
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
View Poll Results: Do you use sudo or the root account to gain root privileges?
Actually, it's more secure, because you can't brute-force attack a userid if you don't know a valid userid.
I can do a remote login as root to my machines. But since I do not use a password for that, I wish you good luck and no boredom for the try to brute force that login. Or just a mainframe (or two).
I can do a remote login as root to my machines. But since I do not use a password for that, I wish you good luck and no boredom for the try to brute force that login. Or just a mainframe (or two).
I don't need to. All I need to do is pop the box you're logging in remotely from, and steal your public key.
In FreeBSD, you cannot log in as root even if you know the password. You have to be in the wheel group.
You shouldn't be using anything whose kernel is BSD instead of GPL in the first place, as it can be used by companies to make proprietary forks (like Apple for instance).
Sure, the Chromium browser may also be based on the BSD license, but the rest of the OS is GPL.
You shouldn't be using anything whose kernel is BSD instead of GPL in the first place, as it can be used by companies to make proprietary forks (like Apple for instance).
Sure, the Chromium browser may also be based on the BSD license, but the rest of the OS is GPL.
LOL, wait a minute, you are using Android and ChromeOS, but recommend to not use an OS that has a BSD-license?
I couldn't really take you serious before this post, but now I know that I really shouldn't.
LOL, wait a minute, you are using Android and ChromeOS, but recommend to not use an OS that has a BSD-license?
I couldn't really take you serious before this post, but now I know that I really shouldn't.
Only at the kernel level. Chrome OS and Android have the B$D license at the user level. If the kernel is B$D, that means that the whole OS can be forked into a proprietary version. In Chrome OS, only the browser can be forked into a proprietary version, and in Android, only Dalvik and above can be forked into a proprietary version.
And what makes that for a difference? ChromeOS without Chrome. Android without it's userland? Wouldn't that be useless?
Not really. And Android is the Apache License anyway. However, that's beside the point. Chrome OS without Chrome would just be Ubuntu JeOS with X and some added commands. Put Unity (and GNOME) back on it, and you've just turned it back into Ubuntu. And with Android? Programmers can still fork the version of Android without its userland using IcedTea (for instance) to create a FOSS alternative to Dalvik that is still compatible with Android apps. My point being: As much as someone tries to close something up, unless the kernel is partially closed, developers can easily fork the open source portion into something usable.
The Apache license is somewhat similar to the BSD license.
Quote:
Chrome OS without Chrome would just be Ubuntu JeOS with X and some added commands. Put Unity (and GNOME) back on it, and you've just turned it back into Ubuntu.
And would it run the ChromeOS apps? If ChromeOS becomes closed, I doubt so.
Quote:
developers can easily fork the open source portion into something usable.
Do you really think that it would be easy to write an Android-clone? How many developers are actually working on Android? And if you close Androids userland, do you really think it will be difficult for Google to make it so that the apps will not run on a clone?
First of all, even with something as permissive as the B$D license, you can't just take something that is open source and make the whole thing proprietary. You would have to open up some code, even if it may be nothing at all. And Google is usually generous enough to open up a lot of code (which they do; Chromium is no more different from Chrome than CentOS [or more properly Fedora] is from RHEL as I have said), so that argument is moot. And Chrome OS apps are mostly Web apps, so they can run from any browser and therefore any OS.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.