On 11 Feb 1999, [EMAIL PROTECTED] writes: > i'm sure i asked this before, but i don't recall seeing a reply. > what's the easiest way to see what linuxconf is doing behind the > scenes for each action -- the command being run, the files being > edited, and so on. Read the source code?? <grin> Or, if you are desperate but can't read code, do something like: touch mystartfile linuxconf (do whatever changes you want) find / -newer mystartfile and you'll get a list of files newer than just before you ran Linuxconf... so any files Linuxconf edited will be in that list. Is there something specific you need to know to get work done, or are you just curious about how Linuxconf works? Jonathan -- Jonathan Marsden | Internet: [EMAIL PROTECTED] | Making electronic 1849 N. Wabash Ave.| Phone: +1 (909) 794 1151 | communications work Redlands, CA 92374 | FAX: +1 (909) 794 3016 | reliably for Christian USA | http://www.xc.org/jonathan | missions worldwide --- You are currently subscribed to linuxconf as: [[email protected]] To unsubscribe, forward this message to [EMAIL PROTECTED]
