5:06 p.m.
Hi, my name is Greg and I have an idea for an article. I saw your earlier post <a
href="https://fedoramagazine.org/writing-an-article-for-the-fedora-m...
rel="noopener" target="_blank">Writing an article for the Fedora
Magazine</a> and I would like permission to create new posts for review.
Thanks,
Greg Bartholomew
3:49 p.m.
On Mon, Nov 05, 2018 at 11:06:16PM -0000, Gregory Bartholomew wrote:
Hi, my name is Greg and I have an idea for an article. I saw your
earlier post <a
href="https://fedoramagazine.org/writing-an-article-for-the-fedora-m...
rel="noopener" target="_blank">Writing an article for the Fedora
Magazine</a> and I would like permission to create new posts for review.
Gregory,
The editors saw your pitch on netboot and *loved* it. I've moved it
in to the Drafts category. You now have rights that should allow you
to edit it in place. Go forth and write! And thank you for the
excellent contribution.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
3:20 p.m.
On Wed, Nov 07, 2018 at 04:49:14PM -0500, Paul W. Frields wrote:
On Mon, Nov 05, 2018 at 11:06:16PM -0000, Gregory Bartholomew wrote:
> Hi, my name is Greg and I have an idea for an article. I saw your earlier post
<a
href="https://fedoramagazine.org/writing-an-article-for-the-fedora-m...
rel="noopener" target="_blank">Writing an article for the Fedora
Magazine</a> and I would like permission to create new posts for review.
Gregory,
The editors saw your pitch on netboot and *loved* it. I've moved it
in to the Drafts category. You now have rights that should allow you
to edit it in place. Go forth and write! And thank you for the
excellent contribution.
Gregory, we were looking at the netboot article and it's *very* long.
The editors agreed we should come to some ideas on how to slim it
down.
One idea is that to have you pull out the NFS4/KRB section into a
separate article. We could publish that sooner. Then you could refer
back to that in the netboot article. This not only means double the
posts, it also means better searchability results for users.
What do you think?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
4:25 p.m.
On November 14, 2018 9:20:14 PM UTC, "Paul W. Frields"
<stickster(a)gmail.com> wrote:
On Wed, Nov 07, 2018 at 04:49:14PM -0500, Paul W. Frields wrote:
> On Mon, Nov 05, 2018 at 11:06:16PM -0000, Gregory Bartholomew wrote:
> > Hi, my name is Greg and I have an idea for an article. I saw your
earlier post <a
href="https://fedoramagazine.org/writing-an-article-for-the-fedora-m...
rel="noopener" target="_blank">Writing an article for the Fedora
Magazine</a> and I would like permission to create new posts for
review.
>
> Gregory,
>
> The editors saw your pitch on netboot and *loved* it. I've moved it
> in to the Drafts category. You now have rights that should allow you
> to edit it in place. Go forth and write! And thank you for the
> excellent contribution.
Gregory, we were looking at the netboot article and it's *very* long.
The editors agreed we should come to some ideas on how to slim it
down.
One idea is that to have you pull out the NFS4/KRB section into a
separate article. We could publish that sooner. Then you could refer
back to that in the netboot article. This not only means double the
posts, it also means better searchability results for users.
What do you think?
No problem, I expected that you might ask that. It should be trivial. I'll try to
get on IRC tomorrow for further feedback.
Thanks,
Greg Bartholomew
--
Gregory Lee Bartholomew
PGP Key ID: 3B67510E
2:28 p.m.
On Wed, 2018-11-14 at 16:20 -0500, Paul W. Frields wrote:
On Wed, Nov 07, 2018 at 04:49:14PM -0500, Paul W. Frields wrote:
> On Mon, Nov 05, 2018 at 11:06:16PM -0000, Gregory Bartholomew wrote:
> > Hi, my name is Greg and I have an idea for an article. I saw your earlier post
<a
href="https://fedoramagazine.org/writing-an-article-for-the-fedora-m...
rel="noopener" target="_blank">Writing an article for the Fedora
Magazine</a> and I would like permission to create new posts for review.
>
> Gregory,
>
> The editors saw your pitch on netboot and *loved* it. I've moved it
> in to the Drafts category. You now have rights that should allow you
> to edit it in place. Go forth and write! And thank you for the
> excellent contribution.
Gregory, we were looking at the netboot article and it's *very* long.
The editors agreed we should come to some ideas on how to slim it
down.
One idea is that to have you pull out the NFS4/KRB section into a
separate article. We could publish that sooner. Then you could refer
back to that in the netboot article. This not only means double the
posts, it also means better searchability results for users.
What do you think?
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.
9:23 a.m.
On Mon, Nov 19, 2018 at 2:28 PM <gregory.lee.bartholomew(a)gmail.com> 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.
2. I had an idea for a somewhat comical cover image showing the linux
penguin flying through a "series tubes" (an oblique reference to
senator Ted Stevens' comment:
https://en.wikipedia.org/wiki/Series_of_tubes) between a server and
some client workstations. Maybe next time? Or do you guys prefer to do
your own artwork?
Thanks,
Greg Bartholomew
9:16 a.m.
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> 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.")
2. I had an idea for a somewhat comical cover image showing the
linux
penguin flying through a "series tubes" (an oblique reference to
senator Ted Stevens' comment:
https://en.wikipedia.org/wiki/Series_of_tubes) between a server and
some client workstations. Maybe next time? Or do you guys prefer to do
your own artwork?
I get the humor for sure, but since this is somewhat USA-centric and
also we have a fairly well defined style language for images, I would
prefer we stick with something more standard.
--
Paul
10:38 a.m.
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> 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).
> 2. I had an idea for a somewhat comical cover image showing the
linux
> penguin flying through a "series tubes" (an oblique reference to
> senator Ted Stevens' comment:
> https://en.wikipedia.org/wiki/Series_of_tubes) between a server and
> some client workstations. Maybe next time? Or do you guys prefer to do
> your own artwork?
I get the humor for sure, but since this is somewhat USA-centric and
also we have a fairly well defined style language for images, I would
prefer we stick with something more standard.
OK; just wondered what the rules were. Thanks.
1:04 p.m.
On Mon, Nov 26, 2018 at 11:38 AM <gregory.lee.bartholomew(a)gmail.com> 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(a)gmail.com> wrote:
> > On Mon, Nov 19, 2018 at 2:28 PM <gregory.lee.bartholomew(a)gmail.com>
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!
--
Paul
3:38 p.m.
On Tue, 2018-11-27 at 14:04 -0500, Paul Frields wrote:
On Mon, Nov 26, 2018 at 11:38 AM
<gregory.lee.bartholomew(a)gmail.com> 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(a)gmail.com> wrote:
> > > On Mon, Nov 19, 2018 at 2:28 PM <gregory.lee.bartholomew(a)gmail.com>
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?
9:18 a.m.
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(a)gmail.com> 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(a)gmail.com>
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(a)gmail.com> wrote:
> > > > > On Mon, Nov 19, 2018 at 2:28 PM
<gregory.lee.bartholomew(a)gmail.com> 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?
>
1969
days inactive
1998
days old
magazine@lists.fedoraproject.org
10 comments
5 participants
participants (5)
-
Gregory Bartholomew -
Gregory Lee Bartholomew
-
gregory.lee.bartholomew＠gmail.com
-
Paul Frields -
Paul W. Frields