On Thu, Jul 22, 2010 at 03:04:40PM +0200, Goswin von Brederlow wrote: > Mark Brown <broo...@debian.org> writes:
> > Most people do virtualisation rather than chroots (as you yourself were > > actually going to do) and with virtualisation you don't get the problem > > since the virtual system is a separate one. Virtualisation has pretty > > much removed the reason people used to do this by providing a superior > > alternative. > You still have to create the filesystem for it first. d-i sounds like a good candidate here, you are essentially installing a new system. > I looked into writing a patch for this and looked into policy for what > the right thing to do is. According to policy on a fresh install dpkg > passes the Null argument as second argument but the "killall ypbind" is > already portected with an "$2" != "". So on a fresh install the killall > should not be triggered, right? > But then what did kill the systems ypbind? I'm afraid of running the > "create FS for kvm" script again because I'm not on site currently. So > I can't make a strace of what happens just now. I suspect it may be getting triggered by the debconf interaction, I'll try to check at some point. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
