18
Documenting commands # or $ before sudo?
(feditown.com)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I don't work much with Linux systems these days, but I would vote for
$ sudoover#. Two reasons:#is also used for comments. I think it would be confusing to use the same character for two wildly different things.So
$ sudoin general any time I need to run something as root?I'll have to think about that some more. I think I rather dislike "forcing" sudo on all commands as root.
Ok, maybe I misunderstood your question. I though you were proposing
#instead of$ sudoand I meant to say that being explicit is better.I typed the post in a minute and published, so it definitely isn't the most coherent or well thought out post.
I'm currently using
#for commands executed by the root user orsudo.Currently, I only use
sudoif the command depends on one of its features. Like the example above where I execute a command as thewww-datauser.My dilemma was whether to use
$ sudoor# sudofor those few cases. But based on yours and other comments, it might make sense to use$ sudofor commands executed as root as well.