With Fedora-live sudo does not work as expected either. It leads to additonal confusion. -- Kam http://kamsalisbury.com GPG key: FAF1751E -----Original Message----- From: Jason Taylor <jmtaylor90@xxxxxxxxx> Subj: Re: prompts in command examples Date: Sat Oct 4, 2008 6:29 pm Size: 1K To: For participants of the Documentation Project <fedora-docs-list@xxxxxxxxxx> On Fri, 2008-10-03 at 08:20 +1000, Murray McAllister wrote: > On Fri, Oct 3, 2008 at 2:32 AM, Karsten 'quaid' Wade <kwade@xxxxxxxxxx> wrote: > > > > On Wed, 2008-10-01 at 22:32 -0400, Paul W. Frields wrote: > > > >> Note that the su command removes the need for the user to look for > >> niggling prompt details. It also clarifies that the user should > >> expect a prompt for the root password. > > > > In part of that discussion with the Content Services team, we discussed > > the need for sudo to be enabled by default. One person was in favor of > > having each document specify how to enable sudo, but I don't like that > > rat hole. That is another point we could discuss, however, if any > > Anonymous Cowards are interested in fixing the common usage. Meanwhile, > > I'm advocating for a sane sudo-by-default in future Fedora versions so > > we can stop having to use 'su -c'. > > > > - Karsten > > I leave this out. I have text preceding the command saying "Run the > following command as the Linux root user:", because I'm too lazy to > decide between sudo or su ;) I agree that a standard for documentation purposes of using 'su -c' or 'sudo' is a good thing. On a tangent, however, I have noticed with sudo that it doesn't always find the command that the user is trying to run. For example, try and run restorecon as sudo. It doesn't work out-of-the-box at least for me anyway. -Jason --- attachment signature.asc --- --- attachment noname 2.txt --- --- message truncated --- -- fedora-docs-list mailing list fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
