On Thu, Jul 22, 2010 at 03:04:40PM +0200, Goswin von Brederlow wrote:
> Mark Brown 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. Virtu
Mark Brown 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 virtualiza
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
> virt
Mark Brown writes:
> severity 589821 important
> kthxbye
>
> On Wed, Jul 21, 2010 at 02:07:45PM +0200, Goswin von Brederlow wrote:
>> Package: nis
>> Version: 3.17-17
>> Severity: critical
>
> Please be realistic in the severity of your reports; this is a fairly
> obscure use case (it's been pres
severity 589821 important
kthxbye
On Wed, Jul 21, 2010 at 02:07:45PM +0200, Goswin von Brederlow wrote:
> Package: nis
> Version: 3.17-17
> Severity: critical
Please be realistic in the severity of your reports; this is a fairly
obscure use case (it's been present for something in the region of t
Package: nis
Version: 3.17-17
Severity: critical
Hi,
installing nis in a chroot with
chroot $DIR apt-get install nis
causes nis to break down on the main system. E.g. sudo says:
YPBINDPROC_DOMAIN: Domain not bound
YPBINDPROC_DOMAIN: Domain not bound
sudo: unknown uid: 1009
Restarting
6 matches
Mail list logo
