public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
	LKML <linux-kernel@vger.kernel.org>,
	Jeff Dike <jdike@addtoit.com>
Subject: Re: [PATCH] um/configs: don't use devtmpfs in defconfig
Date: Tue, 16 Jul 2013 18:47:09 +0100	[thread overview]
Message-ID: <20130716174708.GN4165@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CALkWK0nrDsZiHe2==DQZuHV7id=6gc4UHUj1xXu9jN5cr3SUcQ@mail.gmail.com>

On Tue, Jul 16, 2013 at 10:36:25PM +0530, Ramkumar Ramachandra wrote:
> Richard Weinberger wrote:
> > If you don't want devtmpfs, just disable it in your config.
> 
> I don't understand: is this not a good default?  Why is creating bogus
> devices, confusing systemd, and making um Linux hard to boot
> desirable?

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...

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.

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.  One
practical issue is the lack of VT102 emulation; 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.)

  parent reply	other threads:[~2013-07-16 17:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 16:52 [PATCH] um/configs: don't use devtmpfs in defconfig Ramkumar Ramachandra
2013-07-16 16:58 ` Richard Weinberger
2013-07-16 17:06   ` Ramkumar Ramachandra
2013-07-16 17:08     ` Richard Weinberger
2013-07-16 17:15       ` Ramkumar Ramachandra
2013-07-16 17:20         ` Ramkumar Ramachandra
2013-07-16 17:23           ` Richard Weinberger
2013-07-16 17:36             ` Ramkumar Ramachandra
2013-07-16 17:39               ` Richard Weinberger
2013-07-16 17:31           ` Ramkumar Ramachandra
2013-07-16 17:34             ` Richard Weinberger
2013-07-16 17:47     ` Al Viro [this message]
2013-07-16 18:12       ` Ramkumar Ramachandra
2013-07-16 18:20         ` Richard Weinberger
2013-07-16 19:29           ` Ramkumar Ramachandra
2013-07-16 19:32             ` Richard Weinberger
2013-07-16 19:03         ` Al Viro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130716174708.GN4165@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=artagnon@gmail.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox