fai uses /etc/init.d/rcS for starting the installation. Probably this has to be changed for jessie with systemd to be a systemd-job with lowest priority and dependcy of network...
Am 12.05.2015 um 19:32 schrieb Nat Sincheler: > I upgraded the FAI build server to jessie and things are looking much > better. I still have some build issues, but at least I get to the FAI > portion of the build process now. > > The use of systemd-sysv seems to cause problems. Can anyone explain > why sysvinit-core works while systemd-sysv does not, even though those > two packages are supposed to provide the same functionality? > > > > > On 5/11/2015 9:11 AM, Adam Lewenberg wrote: >> >> >> On 5/10/2015 11:00 AM, Thomas Lange wrote: >>>>>>>> On Sun, 10 May 2015 08:55:49 -0700, fai1...@macrotex.net said: >>> >>> > The main fai-make-nfsroot log: http://paste.debian.net/174450 >>> I found the problem. You do not install the package sysvinit-core into >>> the NFSROOT. Please add sysvinit-core to /etc/fai/NFSROOT and rebuild >>> the nfsroot. This should fix hopyfully all of your problems. >> >> Unfortunately, this does not seem to be the issue. Using chroot, I see >> that sysvinit-core is, in fact, installed: >> >> % chroot /srv/fai/jessie-amd64 dpkg -l | grep sysvinit-core >> ii sysvinit-core 2.88dsf-59 amd64 >> System-V-like init utilities >> >> However, I am seeing the same pxeboot problems from my original e-mail; >> see http://paste.debian.net/174459 >> >> >> >>> >>> I think I will add a test to fai-make-nfsroot. >>> >> > -- Sven Schumacher - Systemadministrator Tel: (0511)762-2753 Leibniz Universitaet Hannover Institut für Turbomaschinen und Fluid-Dynamik - TFD Appelstraße 9 - 30167 Hannover Institut für Kraftwerkstechnik und Wärmeübertragung - IKW Callinstraße 36 - 30167 Hannover
