linux-kernel - Re: [PATCH] um/configs: don't use devtmpfs in defconfig

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Jul 2013 23:42:55 +0530
From:	Ramkumar Ramachandra <artagnon@...il.com>
To:	Al Viro <viro@...iv.linux.org.uk>
Cc:	Richard Weinberger <richard@....at>,
	LKML <linux-kernel@...r.kernel.org>,
	Jeff Dike <jdike@...toit.com>
Subject: Re: [PATCH] um/configs: don't use devtmpfs in defconfig

Al Viro wrote:
> As for the devices, they are *not* bogus.  RTFM, already.
> Documentation/virtual/uml/UserModeLinux-HOWTO.txt, if you can't be bothered
> to say git grep UML Documentation/ and find where it on your own.  The
> relevant section is called "Setting up serial lines and consoles".
> Seriously, it's not as if the documentation didn't exist or had been
> hard to find...

Yes; I've been trying to decipher the con thing for some time now.

> FWIW, default config is rather annoying - 6 xterms spawned and associated
> with /dev/tty[1-6].  con0=fd:0,fd:1 con=pts mentioned in the HOWTO would,
> IMO, make for much saner default.

Leave aside the fact that I could not find the uml-utils upstream [1],
and didn't have a /uml/port-helper to connect the xterms for a second;
I didn't even understand what was supposed to happen.  Why do we spawn
xterms, and attach to the host's /dev/tty*?  So far, I just used
/dev/console inside my existing tmux session in urxvt, and it seems to
work fine.

> No comments on systemd behaviour - take that with LP and his crowd.  They
> may or may not be confused by /dev/tty1 not being a virtual console.

>From my brief discussion with Lennart, he's just following what
Documentation/devices.txt says: /dev/tty* are virtual consoles.  If um
is making some sort of exception for good reason, I'm sure systemd can
accommodate it.

> One
> practical issue is the lack of VT102 emulation;

This detail is not at all clear from the Documentation.  I spent a lot
of time trying to figure out why systemd wasn't able to getty on
/dev/tty1.

> TERM=linux when logged
> in on those is not right - you want either TERM=xterm (for xterms) or
> TERM=screen (when accessing pts-associated ones with screen /dev/pts/n),
> etc.  In any case, it's a dumb serial line as far as the guest kernel
> is concerned - all terminal emulation is going to happen elsewhere (xterms
> running on host and interpreting escape sequences from guest userland,
> etc.)

Hm, what does $TERM have to do with all this?

[1]: A fabulously empty git repository here:
sourceforge.net/p/user-mode-linux/git/ref/master/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/