On Fri, Sep 27, 2002 at 12:38:25PM -0700, Jeremy C. Reed wrote:
> On Fri, 27 Sep 2002, Manuel Bouyer wrote:
> 
> > So you have getty on both ttyE0 and console ? As console is redirected to
> > ttyE0 this can lead to trouble as well ...
> 
> The default ttys has:
> 
> console "/usr/libexec/getty Pc"         vt100   on secure
> ttyE0   "/usr/libexec/getty Pc"         vt220   off secure
> 
> I changed it to:
> 
> console "/usr/libexec/getty Pc"         vt100   on secure
> ttyE0   "/usr/libexec/getty Pc"         vt220   on secure
> 
> My previous (with 1.5.3) /etc/ttys had:
> 
> console "/usr/libexec/getty Pc"         pc3     off secure
> ttyE0   "/usr/libexec/getty Pc"         vt220   on secure
> 
> But now I see that http://www.netbsd.org/Documentation/wscons/ says:
> 
>       Edit /etc/ttys and change the entries for ttyE{1,2,3}
>       from "off" to "on".
> 
> So I guess that ttyE0 entry should still be off. I see when I switch
> consoles with F1 key (i386), the login says "(console)", and when I switch
> with F2 it says "(ttyE1)".
> 
> I am curious: when is it okay to have ttyE0 and console both have gettys?

When console is redirected to com0 (or com1)

> 
> I could switch back to ttyE0 (F1 key) and just had a text console login. I
> used fstat to see that XFree86 was running at ttyE4 (which I could get to
> with F5).

OK, so maybe it was just something else

> 
> Anyways, I am not getting the error now. I wonder if I should turn "off"
> the ttyE0 entry in /etc/ttys though.

Yes, I think you should. Or the console entry.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
--