Re: gpg errors

2010-11-10 Thread Andreas Heinlein
Am 09.11.2010 21:45, schrieb Martin Konrad: > It seems the keys are not available if I chroot to the NFSROOT. Correct. These keys need to be in $NFSROOT/etc/apt/trusted.gpg > Maybe that's > why the script failes? > Like Thomas said, no? From what you wrote, it looks like yo haven't installed a

Re: gpg errors

2010-11-10 Thread Andreas Heinlein
Am 10.11.2010 11:15, schrieb Martin Konrad: > Hi, > >>> It seems the keys are not available if I chroot to the NFSROOT. >>> >> Correct. These keys need to be in $NFSROOT/etc/apt/trusted.gpg >> > Are they added automatically to this file? > > chroot $NFSROOT apt-key list > > does not

Re: gpg errors

2010-11-10 Thread Thomas Lange
> On Wed, 10 Nov 2010 09:47:00 +0100, Andreas Heinlein > said: > installed any kernels in the nfsroot. It just means the script tries to > copy kernels from the nfsroot to your tftp-dir and cannot find one. > Actually, even that is no real failure, as you could as well provid

Re: gpg errors

2010-11-10 Thread Martin Konrad
Hi, > Which FAI version are you using? Sorry, I forgot: 3.4.4 on squeeze. I'm using FAI_ALLOW_UNSIGNED=0 to avoid installation of untrusted packages. > > It seems the keys are not available if I chroot to the NFSROOT. Maybe > > that's why the script failes? > > No, the script does not fa

Re: gpg errors

2010-11-10 Thread Thomas Lange
> On Tue, 9 Nov 2010 21:45:05 +0100, Martin Konrad > said: > cp: cannot stat `/srv/fai/nfsroot/live/filesystem.dir/boot/vmlinu?-*': No such > file or directory > cp: cannot stat `/srv/fai/nfsroot/live/filesystem.dir/boot/initrd.img-*': No > such file or directory Wh

Re: gpg errors

2010-11-10 Thread Martin Konrad
Hi, > > It seems the keys are not available if I chroot to the NFSROOT. > > Correct. These keys need to be in $NFSROOT/etc/apt/trusted.gpg Are they added automatically to this file? chroot $NFSROOT apt-key list does not report any keys of third party repositories. Do I need to use a hook to add

algorithm of setting BOOT_DEVICE

2010-11-10 Thread Toomas Tamm
Hello all! Is there a human-language description of how the value of BOOT_DEVICE gets determined in setup-storage? I tried to read the sources (/usr/share/fai/setup-storage/Fstab.pm) but there are several pieces of code dealing with assignment of this variable and tracking the necessary conditions

Re: algorithm of setting BOOT_DEVICE

2010-11-10 Thread Toomas Tamm
> I'll try to fix this soon, but one of the core problems is that AFAIK the > version in trunk and the experimental one differ in this regard. Which version > would you be interested in? I am using experimental. > Would you mind explaining why you'd need to override this? The reason I'm > askin

Re: gpg errors

2010-11-10 Thread Andreas Heinlein
Am 10.11.2010 09:59, schrieb Thomas Lange: >> On Wed, 10 Nov 2010 09:47:00 +0100, Andreas Heinlein >> said: >> > > installed any kernels in the nfsroot. It just means the script tries to > > copy kernels from the nfsroot to your tftp-dir and cannot find one. >

Re: algorithm of setting BOOT_DEVICE

2010-11-10 Thread Michael Tautschnig
> Hello all! > > Is there a human-language description of how the value of BOOT_DEVICE > gets determined in setup-storage? I tried to read the sources > (/usr/share/fai/setup-storage/Fstab.pm) but there are several pieces of > code dealing with assignment of this variable and tracking the necessar

Re: gpg errors

2010-11-10 Thread Thomas Lange
> On Wed, 10 Nov 2010 11:09:05 +0100, Martin Konrad > said: >> Which FAI version are you using? > Sorry, I forgot: 3.4.4 on squeeze. I'm using FAI_ALLOW_UNSIGNED=0 to avoid > installation of untrusted packages. FAI_ALLOW_UNSIGNED=0 does not work when calling make-fai-nfsroo

install system hangs during boot up

2010-11-10 Thread Martin Konrad
Hi, I'm experiencing problems during boot up of my install system. On a VMware ESX server the installation works perfectly but on my Intel S3200SH the system stops during boot up. According to the output on the screen the problem seems to be connected somehow to the networking system (see [1]).