![]() #3) With great power comes great responsibility.īut then it’s ok, you’re ready-to-use sudo with this user account. It usually boils down to these three things: We trust you have received the usual lecture from the local SystemĪdministrator. On the first access, you’ll get a warning message like this: ![]() To allow a user to run commands with sudo, add this user to the sudo group like this: Other users: no administrator privileges.īut if you need sudo on other users, it’s possible.pi (or first user): administrator privileges, if needed, via the sudo command.root: direct access to administrator privileges for any command.But would it be the same if you created other users? Default parametersīy default, the new users can’t use sudo. We just learned how to use sudo with the default user. Use “exit” to come back to the pi user terminal: Grab your free PDF file with all the commands you need to know on Raspberry Pi! So Debian developers have changed this to force the creation of the first user in the installation process and then give this user a way to elevate his privileges like an administrator: sudo. So it was easy to break something, and also as everyone logs as root, you don’t know who changed something, as it’s only “root”. Why did Debian developers hide it?īefore this, everyone used root, and mainly only root. But developers have changed this by asking to create a standard user in the installation process, and this user has no direct privileges. If you want to create files in /etc, reboot the system, or change the network configuration, you need root privileges.Īt the beginning of the Linux history, you got root access directly after the installation. This user has all permissions on the system. On Windows, you have the “Administrator” account (and most of the time anyone is admin), on Linux, it’s “root”. On Linux operating systems, “root” is the administrator user. If you start on Linux with your fresh new Raspberry Pi, the reminders below could help you understand better. I want to start with some reminders about Linux systems. The first third of the book teaches you the basics, but the following chapters include projects you can try on your own. It’s a 30-day challenge where you learn one new thing every day until you become a Raspberry Pi expert. If you’re looking to quickly progress on Raspberry Pi, you can check out my e-book here. And then I’ll show you how to do things as root on Raspberry Pi. In this post, I’ll explain what the sudo command is, and why Raspberry Pi OS developers added it and disabled the root user. To re-enable it, the user must use “sudo” and set a new password for the administrator account. ![]() Why? How does it work? How do you disable it? Keep reading to learn how to use root to change user privileges.įor security reasons, root is disabled by default on Raspberry Pi OS and most Linux distributions. ![]() The changes to /etc/pulse/nf did not seem necessary but I haven't tested thoroughly.įile /etc/systemd/system/pulseaudio.You only get one normal user on default with Raspberry Pi OS (it was “pi”, but now it’s the user created during the first boot), but it isn’t an administrator account and you can’t configure things with it (i.e. So if you find it doesn't work when you first boot but does after manual restart try adding ExecStartPre=/bin/sleep 30. Modified the file to delay startup of pulse and now it works. Managed to get sound from alsaplayer, removed all changes to /etc/pulse/default.pa and /etc/nf and started pulse as a user and it HDMI detected and can watch videos without hanging.Īdded this back to /etc/systemd/services, re-enabled, and it didn't work but after manual restart of pulse service as root the HDMI showed up again. I finally got an HDMI sound extractor to work with a 25w HDMI graphics card on the r620 but fiddling with /etc/pulse/default.pa default card settings didn't fix it. This solution has worked for me on several debian 11 servers but have a Dell r620 and r720 where the sound card causes the machine to hang after 2-3min of video.
0 Comments
Leave a Reply. |