From: Richard Weinberger <richard@nod.at>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: 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 19:39:56 +0200 [thread overview]
Message-ID: <51E5856C.3020504@nod.at> (raw)
In-Reply-To: <CALkWK0mDtxNPRnU480k8wiNt+i7gpVHLz8Za4+368_L8bU9Teg@mail.gmail.com>
Am 16.07.2013 19:36, schrieb Ramkumar Ramachandra:
> Richard Weinberger wrote:
>> BTW: I'll not apply any patch to the kernel if the issue can easily
>> fixed in user space, that's the major reason for my NAK.
>
> I was just asking for good defaults; I want um Linux to work
> out-of-the-box. There's really no point in creating bogus devices in
> /dev, and make life unnecessarily hard for user-space applications:
> instead of checking for existence, they'd have to check that all the
> devices work. I doubt systemd will accept such a patch, just to bend
> over backwards and support um.
Out of the box wont work in all cases.
But you can easily adjust some systemd units.
Like any visualization technology UML comes with some trade-offs.
Thanks,
//richard
next prev parent reply other threads:[~2013-07-16 17:40 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 [this message]
2013-07-16 17:31 ` Ramkumar Ramachandra
2013-07-16 17:34 ` Richard Weinberger
2013-07-16 17:47 ` Al Viro
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=51E5856C.3020504@nod.at \
--to=richard@nod.at \
--cc=artagnon@gmail.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
/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