Mark Brown <[email protected]> writes:
> On Thu, Jul 22, 2010 at 10:16:25AM +0200, Goswin von Brederlow wrote:
>
>> As to the obscurity of this scenario: I was creating a chroot to be used
>> as filesystem for a kvm instance. While nis is not widely used, those
>> that do use it probably want to use it in virtualization too, if they do
>> virtualization. So this might crop up more often in the future. 10 years
>> ago virtualization wasn't a buzz-word.
>
> 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.
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.
MfG
Goswin
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
