Andrew Morton <[email protected]> writes:
> Given that a lot of this development will hopefully happen over the next
> two months, ...
A lot. Various pieces are a major effort in their own right.
Improving the kthread API so it can be used universally and
allow removal all of the kernel_thread users.
Reducing to an absolute minimum usage of pid_t.
I know several of the things with signal handling had Oleg
scratching his head.
There is enough development there I question if the code will even be
canidates for merging into 2.6.24.
I can imagine an -mm tree that has everything ready to go in
the next two months.
>> It hurts me to even ponder what thinking makes it that
>> CONFIG_EXPERIMENTAL isn't enough to keep a stable distro
>> from shipping the code in their stable kernel, and locking us into
>> trouble.
>>
>> With that said. I think I should just respin the patchset now and add
>> the "depends on BROKEN".
>
> it doesn't make sense to make it all dependent upon BROKEN now. Better
> would be to make it dependant upon CONFIG_SOMETHING_ELSE now, which depends
> upon EXPERIMENTAL and which will, around -rc6, be changed to depend upon
> BROKEN.
So we now have my patch which makes it depend on CONFIG_PID_NS.
Which is what started this thread.
> If that makes sense.
Yes.
> It's all a bit unusual and complex, but this is an exceptional set of
> features - let's hang in there.
Sure. One small step at a time.
- Step One add a config option.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
