On Tue, 2018-11-27 at 14:04 -0500, Paul Frields wrote:
On Mon, Nov 26, 2018 at 11:38 AM
> On Mon, 2018-11-26 at 10:16 -0500, Paul Frields wrote:
> > On Fri, Nov 23, 2018 at 10:23 AM Gregory Bartholomew
> > <gregory.lee.bartholomew(a)gmail.com> wrote:
> > > On Mon, Nov 19, 2018 at 2:28 PM <gregory.lee.bartholomew(a)gmail.com>
> > > > I have created a separate pitch with the NFS4/KRB content titled
"How to Secure
> > > > NFS4 with Kerberos Authentication".
> > > >
> > > > I also tried to break the Netboot article up into a "Part
1" that could be done
> > > > without needing NFS4/KRB and a "Part 2" that will show how
to add the NFS4/KRB
> > > > to the setup created in Part 1. Part 2 can, as you pointed out, be
> > > > significantly if the NFS4/KRB article is already published by simply
> > > > link over to it.
> > > >
> > > > Let me know what you think should be done next.
> > > >
> > >
> > > Wow! That went to publication fast! Thanks!
> > >
> > > I actually had a few small questions:
> > >
> > > 1. I used the "$" symbol for the bash prompt, but all the
> > > meant to be run as root which is normally indicated by a "#"
> > > thought the latter made everything look like comments though, so I
> > > wanted the editor's opinion on how that should be represented. It is
> > > very minor detail and probably doesn't matter either way.
> > I recommend you use 'sudo' for those commands since that makes the
> > situation clearer. Also we typically recommend use of sudo across the
> > entire Magazine. We have a sudo article you can link to as well, for
> > anyone who hasn't set it up. (Just link it on first use with some text
> > like "use sudo to run this command.")
> I considered sudo, but when *everything* needs to be run as root, then it seems
> like a bit of a waste of space (not to mention a recipe for carpal tunnel).
On the other hand, if it's a lot of commands, five extra characters
for each are probably not a make-or-break issue. ;-)
However, I'm also comfortable with saying at the top, "Run these
commands as root. To become root temporarily, use 'sudo su -' and when
finished, use 'exit' to return to your regular shell." (Or something
to that effect.) We should discourage people from logging in as root,
though -- I still see plenty of people doing it IRL and it makes me
Personally, I like the idea of putting an explanation at the top better than
riddling the article with "sudo ...". With the explanation, I could just point
out that any lines beginning with "#" need to be run as root and anything
beginning with "$" should be run as a normal user and leave it to the user to
decide if they want to stick sudo in front of everything or use "sudo -i" or
whatever. It is probably good to point out to people that that "#" symbol at
end of the prompt is a bit of a red flag anyway.
Are the articles editable after being published or is that something to be