Andi Kleen wrote:
On Sun, Apr 19, 2009 at 09:23:36AM -0700, David VomLehn wrote:
Andi Kleen wrote:
VomLehn writes:
...
Also a setting to panic in this case might be useful, normally a system
without console is not very useful and needs to be rebooted anyways.
Umm, those of us in the embedded
On Sun, Apr 19, 2009 at 09:23:36AM -0700, David VomLehn wrote:
> Andi Kleen wrote:
> >VomLehn writes:
> >>History
> >>v2 Wait for the preferred console rather than any console. Make the
> >>delay interval a tunable.
> >
> >CONFIG tunables are usually a bad idea. What should a binary distribut
Andi Kleen wrote:
VomLehn writes:
History
v2 Wait for the preferred console rather than any console. Make the
delay interval a tunable.
CONFIG tunables are usually a bad idea. What should a binary distribution
kernel set? Better make it a boot option with a reasonable default.
VomLehn writes:
>
> History
> v2Wait for the preferred console rather than any console. Make the
> delay interval a tunable.
CONFIG tunables are usually a bad idea. What should a binary distribution
kernel set? Better make it a boot option with a reasonable default.
Also a setting to p
Parallelization to improve boot times has been successful enough that race
conditions now exist between the init_post() open of /dev/console and
initialization of the console device. When this occurs, opening /dev/console
fails and any applications inherited for init have no standard in/out/err
dev