Re: 2.6.11-rc1-mm1

[Kasper Sandberg <lkml@metanurb.dk>]

On Fri, 2005-01-14 at 00:23 -0800, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc1/2.6.11-rc1-mm1/
> 
> 
> - Added bk-xfs to the -mm "external trees" lineup.
> 
> - Added the Linux Trace Toolkit (and hence relayfs).  Mainly because I
>   haven't yet taken as close a look at LTT as I should have.  Probably neither
>   have you.
> 
>   It needs a bit of work on the kernel<->user periphery, which is not a big
>   deal.
> 
>   As does relayfs, IMO.  It seems to need some regularised way in which a
>   userspace relayfs client can tell relayfs what file(s) to use.  LTT is
>   currently using some ghastly stick-a-pathname-in-/proc thing.  Relayfs
>   should provide this service.
> 
>   relayfs needs a closer look too.  A lot of advanced instrumentation
>   projects seem to require it, but none of them have been merged.  Lots of
>   people say "use netlink instead" and lots of other people say "err, we think
>   relayfs is better".  This is a discussion which needs to be had.
> 
> - The 2.6.10-mm3 announcement was munched by the vger filters, sorry.  One of
>   the uml patches had an inopportune substring in its name (oh pee tee hyphen
>   oh you tee).  Nice trick if you meant it ;)
> 
> - Big update to the ext3 extended attribute support.  agruen, tridge and sct
>   have been cooking this up for a while.  samba4 proved to be a good
>   stress test.
> 
> - davej's "2.6 post-Halloween features" document has been added to -mm as
>   Documentation/feature-list-2.6.txt in the hope that someone will review it
>   and help keep it up-to-date.
> 
> - Added FUSE (filesystem in userspace) for people to play with.  Am agnostic
>   as to whether it should be merged (haven't read it at all closely yet,
>   either), but I am impressed by the amount of care which has obviously gone
>   into it.  Opinions sought.

i really believe fuse is a good thing to have merged, i use it, and it
works really really good. my vote is to get it in

<snip>