<br><br><div><span class="gmail_quote">On 9/10/07, <b class="gmail_sendername">David Nicol</b> <<a href="mailto:davidnicol@gmail.com">davidnicol@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So what happens when there is a problem with the fallback-to-crawl system?<br><br>I believe there appears in recent kernels a system for loading a<br>different kernel,<br>so you might be able to rig something to switch to your known-good instead of
<br>requiring you to reboot again, if you are in a panic/recompile/repeat cycle, but<br>setting that up would certainly harder be than the problem at hand fixing.</blockquote><div><br>So far- some good starting points and thanks!
<br><br>The direction I hope we could use as a "target" is one I can best describe as - "Load a stable minimal live assist with communication-THEN begin the install or whatever-save the Oh, let's call it ID for InitialDegubber to a USB device bootable if possible- then any later event causing a Something Bad has a way to cry for more skilled help" Shorter statement is - something akin to a netboot yet only invoked upon a drastic failure. The teaser is a searchable "BreakFix" repository that such an ID could query as "self remedy"
<br>with the dividend of FEEDBACK to learn hardware compatibilities etc.<br><br>Oh, think of it this way as a closer- " do you always feed back false driver detects"?<br><br>Oren Beck<br></div><br></div><br>