Hi again
Carsten Aulbert schrieb:
> Piyty that, I wish you could remember.
A collegue suggested it might be related to SMP. When booting with
noapic and nosmp this error does not show itself again.
> I'll try it on another box as well.
>
I've seen that now on all systems with the same hardware
Thomas Lange schrieb:
>> On Fri, 08 May 2009 10:21:19 +0200, Carsten Aulbert
>> said:
>
> >> PS: Is there an easy way to enable an accessible terminal on tty2 and
> 3?
> >> I've tried editing /etc/inittab in the live image, but that did not do
> >> the trick. I'm currently
>
>
> Thomas Lange schrieb:
> >> On Fri, 08 May 2009 10:21:19 +0200, Carsten Aulbert
> >> said:
> >
> > >> PS: Is there an easy way to enable an accessible terminal on tty2
> > and 3?
> > >> I've tried editing /etc/inittab in the live image, but that did not
> > do
> > >>
Hi
Michael Tautschnig schrieb:
> Did you add createvt to your FAI_FLAGS? I don't think there will be any open
> ttys without this one.
Ahh, that's the cause. I'll add it, head down into the basement and try
again.
Thanks for the hint, that one did somehow slipped by.
Cheers
Carsten
Per Foreby wrote:
> Sounds wise as long as the initial installation can be done from a
> Debian fai server.
Or in any other way - manual basic install, image deployment on a
web/virtual root server, ...
In these situations, you can still manage configuration details with FAI.
You could also use
> On Fri, 08 May 2009 10:21:19 +0200, Carsten Aulbert
> said:
>> PS: Is there an easy way to enable an accessible terminal on tty2 and 3?
>> I've tried editing /etc/inittab in the live image, but that did not do
>> the trick. I'm currently looking into the main fai cfengine s
