[oclug] tracking the boot process
Brenda J. Butler
bjb at istop.com
Tue Apr 12 12:18:46 EDT 2005
On Tue, Apr 12, 2005 at 10:20:25AM -0400, Mike wrote:
> Well I've only found a work around to the boot troubles I've been having.
> Somewhere in boot.device-mapper it finds root already mounted rw and fails
> leaving several of the startup scripts not run.
> I am able to mount most of the remaining partitions and level three which lets
> me continue. days off is approaching and I am wondering if there is an
> easier way to track the boot process than putting echo into each script I
> think should be running.
Well, this is only a marginal improvement over what you say above:
[ -n "$VERBOSE" ] && echo "$0: debug output"
This way you can turn on all the debug output by assigning something
to VERBOSE, and turn it off again by unsetting VERBOSE or assigning
it an empty string.
Another thing you can do instead of (or in addition to) echo is logger:
[ -n "$LOGGING" ] && logger -p daemon.notice "$0: debug output"
puts messages in syslog system instead of on console.
More information about the OCLUG