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 any
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 report any keys
On Wed, 10 Nov 2010 09:47:00 +0100, Andreas Heinlein aheinl...@gmx.com
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
On Tue, 9 Nov 2010 21:45:05 +0100, Martin Konrad
kon...@ikp.tu-darmstadt.de 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
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
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
On Wed, 10 Nov 2010 11:09:05 +0100, Martin Konrad
kon...@ikp.tu-darmstadt.de 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
