Messages in this thread | | | From | Al Boldi <> | Subject | Re: [PATCH 0/9] namespaces: Introduction | Date | Fri, 19 May 2006 20:17:32 +0300 |
| |
Andrey Savochkin wrote: > I have a practical proposal. > We can start with presenting and merging the most interesting part, > network containers. We discuss details, possible approaches, and related > subsystems, until networking is finished to its utmost detail. > This will create an example of virtualization of a non-trivial subsystem, > and we will have to agree on basic principles of virtualization of related > subsystems like proc. > > Virtualization of networking presents a lot of challenges and > decision-making points with respect to user-visible interfaces: proc, > sysctl, netlink events (and netlink sockets themselves), and so on. This > code will also become immediately useful as an improvement over chroot. > I am sure that when we come to a mutually acceptable solution with respect > to networking, virtualization of all other subsystems can be implemented > and merged without many questions. > > What do people think about this plan?
Exactly what I thought too, and in general always the best way to move forward, i.e: "slowly but surely" instead of "big bang".
This would of course imply, that even this subsystem should be kept as minimalistic as possible, to avoid any side-effects and to just concentrate on the crux of the problem.
Thanks!
-- Al
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |