On Tue, August 29, 2006 3:53 pm, Jeremy Lyon wrote: > There is no need for a DEBUG parameter. You can get to a shell for > debugging by.. > > 1. not putting reboot in your ks.cfg > 2. Crtl-Alt-F2 That's a good point, and somewhat workable, especially if your %post is short and simple. But it's just basic good programming practice to check for errors as you proceed, and preferably offer useful error messages, such as echoing the command that failed. If you wait till the end, you may have well missed an error, not know how far back you need to check for problems, and if you want to finish without restarting, then you have to manually enter the rest of your script. Stopping at the first [critical - one you can't or don't want to proceed past] error, allowing a chance to fix it, and then resume, also can prevent many subsequent errors, besides being efficient and logical. I understand that the goal of kickstart is to run without intervention. But it takes time to develop robust %post scripts, and everything can and will go wrong in the future with scripts that work well now. It's such a simple idea really, it surprises me the resistance it meets. If your script is a few lines, then you might not need a DEBUG parameter. Our goal, frequently met, is that a server is completely configured, even online and in-service if it's a rebuild, as soon as it reboots the first time after being kickstarted, thanks to kickstart and cfengine. -Ed
