Ok, so here's the rethink from another perspective, inpired by the "user in rumpuser-xen doesn't mean anything" comment from a few days ago. The names of the repos we currently have are a bit of a mess, so which layers of repos do we have, and can we name them consistently?
I think we have 3 classes of repos: hypercall, appstack, driver. In addition, we have (or should have) repos which are a class on their own: wiki, book, tools, src (and buildrump.sh, which I'll get to shortly). The distinction between hypercall and appstack is that hypercalls enable running the rump kernel, while appstacks enable running "userspace" applications on the given platform. So the current repos on http://repo.rumpkernel.org/ would be: rumpfiber -> hypercall-userspace-fibers rumpuser-xen -> appstack-xen rumprun -> appstack-userspace pci-userspace -> driver-pci netmap-rumptcpip -> driver-netmap dpdk-rumptcpip -> driver-dpdk rump-pktgenif -> driver-pktgenif rumpuser-linuxkernel -> hypercall-linuxkernel wiki -> wiki book -> book In addition, netbsd-userspace-src and rumpkernel-netbsd-src would be merged to src-netbsd (per earlier discussion in this thread). If we'd some day want to make the pthreads librumpuser hosted on repo.rumpkernel.org, we'd call it hypercall-userspace-pthreads. Tools would contain tools, i.e. mostly take over the role of buildrump.sh. I want to keep the "./buildrump.sh" use case because I've both advertised "just run buildrump.sh to get a working userspace build" quite a lot, and also because it's a neat way to introduce someone unfamiliar with rump kernels to the concept. IOW, we'd have a buildrump.sh implemented on top of the previous repos. I'm not sure if we'd want to have a separate hypercall-xen-minios and appstack-xen. One could build a Xen hypercall implementation which isn't based on MiniOS, but is that likely to happen in reality? Also, if it were to happen, would it screw us if we don't put the extra abstraction level there up front? MiniOS probably will permeate "appstack-xen" quite a lot too, so maybe we'll just not worry about it. Not sure if "driver" needs some extra qualifiers, like "driver-netif-netmap" or "driver-userspace-pci". Makes sense, or "absolute rubbish, laddie" and I should get on with my work? ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
