Thanks Paul for your comments. I will update the article and submit it for
review once I am done.
On Thu, Sep 14, 2017 at 1:30 PM, Paul W. Frields <stickster(a)gmail.com>
On Fri, Sep 08, 2017 at 05:36:44PM -0400, Pinaki Mukherjee wrote:
> I missed the link. Thanks for pointing this out.
Thanks for contributing. We usually follow this process, although I
see you may have skipped a couple steps:
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://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
Mob- +1 4157996610
"Success usually comes to those who are too busy to be looking for it"