Just closing the loop here. I'm fine with the solution of 'sudo -i' + the # prompts. We agreed on the approach in IRC. We try to avoid after-the-fact fixes because they may not hit RSS readers that already cached the article. That being said, always better to have things be accurate. On Tue, Nov 27, 2018 at 4:38 PM <gregory.lee.bartholomew@xxxxxxxxx> wrote: > > > On Tue, 2018-11-27 at 14:04 -0500, Paul Frields wrote: > > On Mon, Nov 26, 2018 at 11:38 AM <gregory.lee.bartholomew@xxxxxxxxx> wrote: > > > 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@xxxxxxxxx> wrote: > > > > > On Mon, Nov 19, 2018 at 2:28 PM <gregory.lee.bartholomew@xxxxxxxxx> wrote: > > > > > > 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 cut down > > > > > > significantly if the NFS4/KRB article is already published by simply including a > > > > > > 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 commands are > > > > > meant to be run as root which is normally indicated by a "#" prompt. I > > > > > thought the latter made everything look like comments though, so I > > > > > wanted the editor's opinion on how that should be represented. It is a > > > > > 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 > > cringe! > > > > 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 the > 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 > avoided? > _______________________________________________ Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/magazine@xxxxxxxxxxxxxxxxxxxxxxx
