On Mon, Mar 18, 2013 at 2:36 PM, harryxiyou <harryxi...@gmail.com> wrote: > On Mon, Mar 18, 2013 at 7:10 PM, Stefan Hajnoczi <stefa...@gmail.com> wrote: > Hi Stefan, > >> Is HLFS making releases that distros can package? I don't see packages >> in Debian or Fedora. > > We will make packages for Debian and Fedora. > >> >> Block drivers in qemu.git should have active and sustainable communities >> behind them. > > Cloudxy is an active and sustainable community, which HLFS is just a > sub-project of it. > >> For example, if this is a research project where the team >> will move on within a year, then it may not be appropriate to merge the >> code into QEMU. > > HLFS have been developed for two years. > >> Can you share some background on the HLFS community and >> where the project is heading? > > See http://code.google.com/p/cloudxy/ (Our Main Website) for > details (in Chinese). > See http://code.google.com/p/cloudxy/wiki/WHAT_IS_CLOUDXY for > details.(in English)
I looked at the Google Code project before, it looks like a repo that a few people are hacking on. The site is developer-focussed and there is no evidence of users. This is why I asked about the background of the community. There are references to "workshop3" and "linux lab" in the source code. Xiyou and XUPT is http://www.xiyou.edu.cn/. What I'm concerned about is that there are no users and the developers leave when they graduate. In that case integrating the patches into QEMU is wasted effort. So what *is* the background of cloudxy (HLFS)? > >> >>> --- >>> block/Makefile.objs | 2 +- >>> block/hlfs.c | 515 >>> +++++++++++++++++++++++++++++++++++++++++++++++++++ >>> configure | 51 +++++ >>> 3 files changed, 567 insertions(+), 1 deletion(-) >>> create mode 100644 block/hlfs.c >>> >>> diff --git a/block/Makefile.objs b/block/Makefile.objs >>> index c067f38..723c7a5 100644 >>> --- a/block/Makefile.objs >>> +++ b/block/Makefile.objs >>> @@ -8,7 +8,7 @@ block-obj-$(CONFIG_POSIX) += raw-posix.o >>> block-obj-$(CONFIG_LINUX_AIO) += linux-aio.o >>> >>> ifeq ($(CONFIG_POSIX),y) >>> -block-obj-y += nbd.o sheepdog.o >>> +block-obj-y += nbd.o sheepdog.o hlfs.o >> >> Missing CONFIG_HLFS to compile out hlfs.o. > > I changed this according to sheepdog. I cannot see any CONFIG_SHEEPDOG. Sheepdog has no dependencies, it can always be built. Stefan