how to correctly create dbus-broker service and allow bus system service to start correctly
Hello, I am currently running dbus-broker, it is pretty simple to do just follow the guide on the ArchWiki. [1] If you would like to check whether you are currently running dbus-broker, you can look at the PIDs or you can simply run: systemctl status dbus If you see the dbus-broker service loaded, then you are successfully using dbus-broker. Also, Happy New Year. Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev [1] https://wiki.archlinux.org/title/D-Bus#dbus-broker
I don't know anything about dbus-broker, but I can find its information from [the Arch wiki][1]. Click on "enable". Note that it is convention for commands that should be ran with sudo to be prefixed with a # . Welcome to the mailing lists! Please read and follow our [guidelines][2]. Specifically, try to use plain text emails. [1]: https://wiki.archlinux.org/title/Dbus-broker [2]: https://wiki.archlinux.org/title/General_guidelines#Mailing_lists -- Cheers, Aᴀʀᴏɴ
Hi Aaron,
Note that it is convention for commands that should be ran with sudo to be prefixed with a # .
That sounds a little mixed up. PS1='$ ' for commands run by the user, PS1='# ' for those run by root. sudo is run by the user so it should be '$ '. -- Cheers, Ralph.
PS1='$ ' for commands run by the user, PS1='# ' for those run by root. sudo is run by the user so it should be '$ '.
... and to run a command as root, you need to use 'sudo' as a user. # command and $ sudo command are functionally the same.
Hi tippfehlr,
PS1='$ ' for commands run by the user, PS1='# ' for those run by root. sudo is run by the user so it should be '$ '.
... and to run a command as root, you need to use 'sudo' as a user.
sudo is one method.
# command
and
$ sudo command
are functionally the same.
Not necessarily, depending on how the root shell was obtained. But that's beside the point. Was there a point to your email which I'm missing? -- Cheers, Ralph.
Hi there, I was trying to dumb it down, since the original poster appeared to be a novice and may not know fancy terms such as “root”. sudo is one method, and the most commonly used one. Yes, the environment is different when using sudo, but that doesn’t matter for most commands. Functionally, they are mostly the same here, so I don’t know what your point was. Cheers, Aᴀʀᴏɴ
Hi Aaron,
so I don’t know what your point was.
You originally wrote:
Note that it is convention for commands that should be ran with sudo to be prefixed with a # .
That is wrong as it suggests # sudo ... but root, as indicated by PS1='# ', would not need to sudo. My reply tried to explain this:
That sounds a little mixed up. PS1='$ ' for commands run by the user, PS1='# ' for those run by root. sudo is run by the user so it should be '$ '.
I expect you knew this but just typo'd or thinko'd '$' for '#'. I replied because the OP might be confused if you thought they needed explaining to them. Then tippfehlr joined in. I don't think any of us are in disagreement. We just aren't taking the necessary time. -- Cheers, Ralph.
Hello, I would like to suggest 2 things. Firstly, please offlist if you are correcting someone, I doubt Aaron wants to be publicly shamed in front of the entire mailing list, and its a simple syntax mistake which is causing a ton of noise, the thread has went from helping someone to correcting someone which is unhelpful. Secondly, in response to this:
I was trying to dumb it down, since the original poster appeared to be a novice and may not know fancy terms such as “root”. sudo is one method, and the most commonly used one. Yes, the environment is different when using sudo, but that doesn’t matter for most commands. Functionally, they are mostly the same here, so I don’t know what your point was.
You shouldn't dumb it down, firstly you implied that Janusz isn't experienced enough to have the full explanation, which is mean. Secondly, Arch Linux is picked because it gives you full control over your system, it has no specific purpose, but can be installed to fit any role (server, CI, desktop etc), "dumbing it down" will only hinder users. Its better if you give them the entire picture, like the ArchWiki does, and walk them through each step explaining what it does and why you need to do it, spoon feeding is discouraged. A simple question has grown into a large thread. Note for Janusz, most of the time the ArchWiki will contain indepth (unless its flagged for expansion or for inaccuracy) explanations on how to setup things on Arch Linux. Often your answer will be found there. Asking before reading the Wiki will likely get you sent a wiki link, and not an explanation. If you don't understand a page feel free to bring it up in the talk pages so that the page can be improved, or ask in the mailing list for additional support (or on IRC). Happy new year to you all. Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev
Hello Polarian,
Firstly, please offlist if you are correcting someone
A public correction is sometimes the correct act. If X corrects Y wrongly then mailing X and Y offlist to explain leaves lurker Z believing the faulty correction. Also others who spot the mistake may either waste time also mailing X and Y or will still email the list.
I doubt Aaron wants to be publicly shamed in front of the entire mailing list
Shamed is an exaggeration.
A simple question has grown into a large thread.
Which is now two bigger. I suggest not making it three. The OP was being mislead by the faulty correction. The thread should have stopped with that being corrected. -- Cheers, Ralph.
Hi, I don’t see how it implies # sudo . To me, “# sudo …” implies “$ sudo sudo …”, which doesn’t make sense. I don’t see how “commands that should be ran with sudo [are] prefixed with a #” implies running that sudo as root. Also, I agree with you that this isn’t shaming of any kind :p Cheers, Aᴀʀᴏɴ
Simplest approach is to simply wait a bit. https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/25
Huh, that's news! Nice! However, AFAIK that wouldn't magically replace all the existing installations that use dbus-daemon. Existing systems would still need to replace it manually, unless I'm missing something. -- Cheers, Aᴀʀᴏɴ
Hello,
However, AFAIK that wouldn't magically replace all the existing installations that use dbus-daemon. Existing systems would still need to replace it manually, unless I'm missing something.
Yes, this is true, it is referenced within the RFC. [1] Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev [1] https://gitlab.archlinux.org/archlinux/rfcs/-/blob/163e6963e5a3faa7db2ea0f44...
participants (7)
-
Aaron Liu
-
Doug Newgard
-
Lime In a Jacket (Aaron Liu)
-
Mgr. Janusz Chmiel
-
Polarian
-
Ralph Corderoy
-
tippfehlr