Hi Forum,

I've been having some trouble with tty12, manifested by interruption of key entries when I attempt to put in my username& password at the prompt. I suspect the issue stems ;) from the root tree.

Is it expected to have BOTH tty@ tty12 and tty-earlier@ tty12 in my boot tree? It seems redundant, can one be removed?

Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : tty@ tty12-log tty@ tty12 tty-earlier@ tty12....
edit;

Nevermind, should be fixed with: 66-disable -t boot tty@ tty12
Did you intentionally enable tty@ tty12 or was this left from an old installation?

I had this behavior once, I disabled ttys from the boot module, and tried to enable them in a following tree, only after I edited the boot module I forgot to pass the change with 66-enable -F to the boot tree. So I had double ttys fighting each other, but tty12 worked.

I also made an installation without a user, and something went wrong in boot and I couldn't log in because tty12 is restricted to user only.

So don't feel bad :)
I doubt it was somehow carried over while transitioning to the recent boot@ system module. Probably, I must have enabled it thru 66-enable when my brain was on wrong autopilot or something. Thanks for the reassurance, I do stupid things from time to time. We all have blindspots as humans after all.
I thought I had done everything wrong at least once, sad thing is when I realize I did them more than once, but I never tried that one. I've had similar behavior though once but couldn't get in because by the time I'd hit enter for name it was restarting.
I had enabled two boot modules at once, one time, thought I disabled one but wasn't careful enough to read the message that I didn't due to a typo, and enabled a 2nd one. That was weird output at boot. :)

Powered by Obarun