Path: csiph.com!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail From: D Newsgroups: comp.os.linux.misc Subject: Re: What programs do you make sure are installed on a new Linux Date: Mon, 18 Nov 2024 10:11:06 +0100 Organization: i2pn2 (i2pn.org) Message-ID: <21b22605-35be-2f46-1465-bbed8aed3533@example.net> References: <8db593ab-0793-2b31-ebc3-922a5d2fc241@example.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Injection-Info: i2pn2.org; logging-data="3013460"; mail-complaints-to="usenet@i2pn2.org"; posting-account="w/4CleFT0XZ6XfSuRJzIySLIA6ECskkHxKUAYDZM66M"; X-Spam-Checker-Version: SpamAssassin 4.0.0 In-Reply-To: Xref: csiph.com comp.os.linux.misc:61052 On Sun, 17 Nov 2024, rbowman wrote: > On Sun, 17 Nov 2024 17:17:37 GMT, Charlie Gibbs wrote: > >> Horses for courses. Never underestimate the value of a few printf()s >> sprinkled here and there (or log file writes if you're really headless). >> I'm still a fan of makefiles. > > I'm a dinosaur so my preferred technique is either printf or log files. > For production code I've sometimes created a sequence of log statements > that can be turned on with a flag that are a narrative of what's going on. > My goal is a support person can read the file and see where the problem > occurs. Often it is a configuration issue they can fix. > > The nice part is the technique can be used with any language and is > effective where a debugger isn't available. > I'm a printf-man, and since I've mostly worked with systems and not mainly code logfiles have been essential for me. Have never had the need to go deeper than that.