In my home pc, I don't use sudo because my wife is the main user, and in the ultra rare occasion I need to be root in the command line (for example, if she didn't update packages from the GUI for long, I'll update but I like aptitude better), then I use su. It's a LTS 18.04 Kubuntu btw. Real users don't need root. Distro hoppers and tinkerers (nothing wrong with it) do.
On servers, I also use su. I ssh as a normal user (root ssh is usually disabled), then often immediately su, as if I'm logging into the server, it's for root work. I sometimes su - down to some specific "service" user to do that user's tasks (such as git on a gitlab server, or ndbadm on a HANA DB server).
I only tinker with sudo if I want to create users that will have one single purpose, which needs root permissions, such as restarting a service. In this case that user will be in the sudoers file, with permission for a single script or command, and often that command will be its default shell in /etc/passwd, and someone can ssh (pre shared key) to trigger it if necessary.
PS: It happened sometimes that I was given a user with full sudo permissions to do root work in someone else's server, but no root password. Then the first thing I do after logging in is "sudo su -" :-)
In my home pc, I don't use sudo because my wife is the main user, and in the ultra rare occasion I need to be root in the command line (for example, if she didn't update packages from the GUI for long, I'll update but I like aptitude better), then I use su. It's a LTS 18.04 Kubuntu btw. Real users don't need root. Distro hoppers and tinkerers (nothing wrong with it) do.
On servers, I also use su. I ssh as a normal user (root ssh is usually disabled), then often immediately su, as if I'm logging into the server, it's for root work. I sometimes su - down to some specific "service" user to do that user's tasks (such as git on a gitlab server, or ndbadm on a HANA DB server).
I only tinker with sudo if I want to create users that will have one single purpose, which needs root permissions, such as restarting a service. In this case that user will be in the sudoers file, with permission for a single script or command, and often that command will be its default shell in /etc/passwd, and someone can ssh (pre shared key) to trigger it if necessary.
As it has been mentioned, it's a barrel plug, but there are dozens of barrel plugs of different sizes, some even have the same outer size but the receptacles for the central pin have different diameters.
Check the polarity and voltage, and try to measure the diameters if you're buying online.
If you're buying locally, take the lamp with you and ask for advice to the seller.
As it has been mentioned, it's a barrel plug, but there are dozens of barrel plugs of different sizes, some even have the same outer size but the receptacles for the central pin have different diameters.
Check the polarity and voltage, and try to measure the diameters if you're buying online.
If you're buying locally, take the lamp with you and ask for advice to the seller.
I like a wide variety of music styles, from Bach to Deep Purple, from Sade to Front 242, from Wagner to Technotronic, but according to my family, none of them were created after the 90s.
And I dress jeans with whatever is on the top when I open the shirt drawers. But I open the polo shirts drawer on workdays and the t-shirt drawer on weekends. My wife sometimes shuffles my clothes in the drawer so I don't keep rotating the same ones forever. She also sometimes throws away some of my clothes, unannounced. Can't believe she threw away a hoodie from my uni, brand new, from 1988. I can't say fashion means much to me ;-)
The misconception that you need to "know linux" to use a computer with linux.
You need to "know linux" to administer linux servers, or contribute to kernel development. My wife is a retired pharmacist, and she uses exclusively a computer with Linux since around 2008. She knows that's Linux, because I told her so. If I had told her it was a different version of Windows, she'd be using it anyway - she was using win95 at work before, so any current windows would have been a big change anyway (granted, nothing like gnome, that's why I gave her kubuntu).
This misconception is fed by "experienced" Linux users who like to be seen as "hackers" just because they "know Linux".
Nobody uses the OS. You use programs that run on the OS. My wife doesn't "use Linux". She uses Chrome, the file manager (whatever that is in the ancient LTS Kubuntu release I have there and update only when LTS is over), LibreOffice Writer and Calc, a pdf reader (not adobe's, whatever was in the distro), the HP scanner app. The closest she gets to "Linux" is occasionally accepting the popup asking for updates.
Users shouldn't need to care about which OS (or which distro, for that matters) they're running their apps on. The OS (and distro) should be as unobtrusive and transparent as possible.
Distro hopping cult. It's ok to try a few distros when adopting Linux, or even flirt with new ones after you've already settled with one. Even keep doing it forever, on a secondary machine or live usbs, if you're curious.
Doing it forever, on a primary machine is stupid; NO FSCK DISTRO WILL BE PERFECT. Windows users whine and cry every time Microsoft shoves a new and worse Windows version up their SSDs, but they stick with Windows anyway.
Distro hoppers hop often because they give up at the first inconvenience. They never feel at home or make it their home, because they never actually use their computers for long enough with any distro. They are more focused on the OS than in using the computer. Nothing wrong with that, but they'll forever be "linux explorers", not actual "linux users".
There will always be some other that has that small thing that doesn't come default on this one. There will always be compromises. It's like marriage. Commit, negotiate, adapt. Settle down ffs.
The OS/distro shouldn't be important for the average user; the OS/distro shouldn't get in the way between the user and the apps, which is what the user uses.
Of course there are distros with specific usage in mind (pen test, gaming, video production, etc), as they conveniently have all main utilities packaged and integrated. But for real average user apps, the OS shouldn't matter to the end user, let alone look like the user should know what window manager or packaging system they're using.
Then when they are faced with dozens of "experts" discussing about which distro has the edge over the other, and the gory technical details of why, and comparing number of distros hopped, well, it sounds like Linux is a goal by itself, when all they wanted was to watch YouTube and access their messages and social media.
When my wife started using a Linux computer I didn't tell her which distro was there (she probably knows the name kubuntu because it shows during boot). I didn't give her a lecture about Gnome vs KDE, rpm vs deb, or the thousands of customizations she could have now. "You log in here, here's the app menu, here's chrome, this is the file manager, here's the printer app". Done, linux user since 2008.
Linux will never be mainstream while we make it look like "using Linux", or "this distro", matters, and that is an objective in itself. Most users don't care. They want to use their apps.
But would it be possible to make AI John Smith "from the start"?
Every AI John Smith characteristic would be based in a real human - unless AI John Smith is a 100% alien lifeform. That applies not only to appearance, but mannerisms, voice, accent, etc.
AI cannot create a 100% "original" human, because it will always be based on information based on real humans.
The analogy is that any text or code "created" by AI is based on learning from texts and code that were written by humans.
Unless Harisson Ford has rights on the "Indiana Jones" franchise, where would be the line for his legal claim? Could AI create a character to play his part that looked nothing like him, but still mimic the way he moved? And how close the resemblance to Harisson Ford could be? Who would judge that?
What about James Bond? So many actors have played it, and there are gestures, sentences, behaviors which are part of the character, not of the actor. How would that be dealt with?
Batteries will have unique encrypted codes (readable by the device), so only original ones from the manufacturer will work. Pretty easy for manufacturers to justify that, based on safety and liability.
Then the replacement batteries will cost more than a new phone.
In my home pc, I don't use sudo because my wife is the main user, and in the ultra rare occasion I need to be root in the command line (for example, if she didn't update packages from the GUI for long, I'll update but I like aptitude better), then I use su. It's a LTS 18.04 Kubuntu btw. Real users don't need root. Distro hoppers and tinkerers (nothing wrong with it) do.
On servers, I also use su. I ssh as a normal user (root ssh is usually disabled), then often immediately su, as if I'm logging into the server, it's for root work. I sometimes su - down to some specific "service" user to do that user's tasks (such as git on a gitlab server, or ndbadm on a HANA DB server).
I only tinker with sudo if I want to create users that will have one single purpose, which needs root permissions, such as restarting a service. In this case that user will be in the sudoers file, with permission for a single script or command, and often that command will be its default shell in /etc/passwd, and someone can ssh (pre shared key) to trigger it if necessary.
PS: It happened sometimes that I was given a user with full sudo permissions to do root work in someone else's server, but no root password. Then the first thing I do after logging in is "sudo su -" :-)