On Wed, 2008-01-02 at 22:43 +0100, Timothy Murphy wrote:
> It is probably slightly impractical if you have say 10 commands
> one after the other.
This is true and we haven't decided a best practice here. The reason we
use 'su -c' is that avoids having to point to a sudo how-to.
We probably need to decide that switching to root is OK at some point.
You lose a layer of security auditing, but make the user's life much
easier. Then we can teach either the 'su -' or 'su -c "/bin/bash"'
methods.
Another option is to have a standard paragraph at the start of all
documents. It says something like:
We use the 'su -c' option for commands, but an easier method
over the long-term is to go through the steps in this [Sudo
How-to]. Thereafter, replace the 'su -c' option with 'sudo' and
remove the "" from around the command.
> I was actually referring more to Linux documents in general,
> when I said the lack of a prompt often causes confusion.
Ah, yes, the source of the confusion that caused Red Hat's docs team
years ago to decide to eschew the prompt in command examples. So now
you have come full-circle on the reasoning. :)
- Karsten
--
Karsten Wade, Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list mailing list fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
