[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081125055744.c3377164.akpm@linux-foundation.org>
Date: Tue, 25 Nov 2008 05:57:44 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Christoph Hellwig <hch@...radead.org>,
ltt-dev@...ts.casi.polymtl.ca, Zhaolei <zhaolei@...fujitsu.com>,
Lai Jiangshan <laijs@...fujitsu.com>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Sam Ravnborg <sam@...nborg.org>
Subject: Re: LTTng kernel integration roadmap, update
On Mon, 24 Nov 2008 11:58:40 -0500 (EST) Steven Rostedt <rostedt@...dmis.org> wrote:
> > The question that prevails is therefore : should we ship userspace
> > binary with the kernel tree at all ? And if yes, how should the resuting
> > executables be packaged and deployed ? Should it be installed in the
> > system along with kernel modules or should it be populated into a
> > filesystem populated by kernelspace ?
> >
> > Or is it better to do as we have always done and keep the userspace
> > tools separated from the kernel tree ?
>
> I say keep the user space tools separate as much as possible.
So... we're now planning to build even more userspace tools into the
kernel merely because we don't know how to deliver userspace tools in
userspace?
Worse, those kernel-based userspace tools will simply be presenting a
textual form of something which the kernel already makes available in a
binary form?
This is so lame.
Any proposal to fix all this will result in vast amounts of
inconclusive chin-scratching again. Last time this came up, we ended
up with the old impractical put-it-in-util-linux chestnut. I think the
time has come for us to admit that this isn't working out.
Mathieu, if you're feeling keen I'd suggest that you just type `mkdir
-p userspace/lttng' and build your userspace tools in there. One they
are there and real, the issues around versioning, installation and
delivery will still need tobe sorted out, but we need to start
somewhere.
--
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/
Powered by blists - more mailing lists