On Fri, Sep 08, 2017 at 05:36:44PM -0400, Pinaki Mukherjee wrote: > I missed the link. Thanks for pointing this out. > > https://fedoramagazine.org/?p=18588&preview=1&_ppp=2ec1ecfacf Hi Pinaki, Thanks for contributing. We usually follow this process, although I see you may have skipped a couple steps: https://fedoramagazine.org/writing-an-article-for-the-fedora-magazine/ In reading the article, I think the purpose and the scope seem very good. However, the article seems rather low on details. Rather than simply listing these five commands, why not present one or two real-world cases of debugging, and how a combination these commands are used to do the actual debugging? This would show how readers can follow a logical flow to discover an issue with the container they're running. -- 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 _______________________________________________ Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx
