Hi,
did anybody think about the reason we did simpler no-curses text mode in the first place? It seems to me that tmux just violated all that...
I understand what we gained by using it, but will it work on dumb consoles or s390?
If I missed the discussion because of my PTO, then consider this email as just ranting :)
Martin
----- Original Message -----
> So now that we have tmux handling consoles for us, the rules for
> console
> stuff have changed a little. Basically, anything in anaconda that
> deals
> directly with VTs or /dev/tty* should be considered deprecated.
>
> tmux has a fairly robust command set that will let you manipulate its
> state (and thus what's shown on the user's console). For example,
> here
> are some common tasks and possible replacements:
>
> Old and busted: Sending log output to tty{3,4,5...}
> New hotness: Send log output to log files; tail log in tmux window
>
> Old: Run debugger in a new VT (e.g. tty6)
> New: Run debugger in a new window:
> `tmux new-window -n pdb "[debugger-command]"`
>
> Old: Activate (switch to) debugger on tty6
> New: Not needed (new-window automatically switches)
>
> Old: Switch back to tty1 using isys.vtActivate
> New: Switch back to first window:
> `tmux select-window -t anaconda:1`
>
> (Note that when you're specifying a window by hand, you can probably
> get
> away with just `tmux selectw -t 1`, but in scripts inside anaconda we
> probably want to specify the full [session-name]:[index])
>
> For more details, consult the man page. Here's a link to it on the
> web:
> http://www.openbsd.org/cgi-bin/man.cgi?query=tmux&sektion=1
>
> -w
>
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list
>
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
