Am 19.07.2013 20:20, schrieb Ramkumar Ramachandra: > The default configuration dictates that um Linux will launch xterms > connected to various tty devices on the host. It makes more sense to > connect to /dev/pts/N, so that the host can: > > $ screen /dev/pts/N > > or > > $ minicom /dev/pts/N > > to start talking to the guest session. Note that > con0 (CONFIG_CON_ZERO_CHAN) still defaults to "fd:0,fd:1", printing boot > messages on the same terminal.
Makes sense. Queued for 3.12. Thanks, //richard > Cc: Al Viro <[email protected]> > Cc: Richard Weinberger <[email protected]> > Signed-off-by: Ramkumar Ramachandra <[email protected]> > --- > Further, I will patch systemd to getty on con0 when um Linux is > detected. Thanks for all the help, and sorry I took so long to > figure it out. > > Applies on top of the patch I sent earlier. > > arch/um/configs/i386_defconfig | 2 +- > arch/um/configs/x86_64_defconfig | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/um/configs/i386_defconfig b/arch/um/configs/i386_defconfig > index 995aecd..74d8823 100644 > --- a/arch/um/configs/i386_defconfig > +++ b/arch/um/configs/i386_defconfig > @@ -278,7 +278,7 @@ CONFIG_TTY_CHAN=y > CONFIG_XTERM_CHAN=y > # CONFIG_NOCONFIG_CHAN is not set > CONFIG_CON_ZERO_CHAN="fd:0,fd:1" > -CONFIG_CON_CHAN="xterm" > +CONFIG_CON_CHAN="pts" > CONFIG_SSL_CHAN="pts" > CONFIG_UML_SOUND=m > CONFIG_SOUND=m > diff --git a/arch/um/configs/x86_64_defconfig > b/arch/um/configs/x86_64_defconfig > index f2c6123..7d4cbbf 100644 > --- a/arch/um/configs/x86_64_defconfig > +++ b/arch/um/configs/x86_64_defconfig > @@ -270,7 +270,7 @@ CONFIG_TTY_CHAN=y > CONFIG_XTERM_CHAN=y > # CONFIG_NOCONFIG_CHAN is not set > CONFIG_CON_ZERO_CHAN="fd:0,fd:1" > -CONFIG_CON_CHAN="xterm" > +CONFIG_CON_CHAN="pts" > CONFIG_SSL_CHAN="pts" > CONFIG_UML_SOUND=m > CONFIG_SOUND=m > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
