(I realize this is not strictly speaking an FAI issue, but I am hoping
that one you FAI users has a solution.)
We are trying to install the old Debian wheezy on a Dell PE 620 using
FAI. The first step is the PXE boot where the wheezy bootstrap image is
downloaded from our tftp server. The boot
In doing an FAI build of stretch we are seeing several messages of the form
Running in chroot, ignoring request.
invoke-rc.d: policy-rc.d denied execution of restart.
For example:
...
Setting up libmagic1:amd64 (1:5.30-1) ...
Setting up rsync (3.1.2-1) ...
Running in ch
On 6/28/2017 5:24 PM, Bill MacAllister wrote:
On Wednesday, June 28, 2017 3:21:58 PM PDT, Nat Sincheler wrote:
We are able to PXE boot and do an NFS mount, but we are getting a
"Read-only file system" error when FAI is trying to make the directory
/tmp/fai.
We get to the point wh
We are able to PXE boot and do an NFS mount, but we are getting a
"Read-only file system" error when FAI is trying to make the directory
/tmp/fai.
We get to the point where we see this at the console:
INIT: version 2.88 booting
cat: /sys/class/net/eth0/name_assign_type: Invalid argument
cat: /
Thanks to Juri Grabowski and Justin Cattle for the suggestion to include
curl: that took care of the issue.
On 6/23/2017 1:37 PM, Nat Sincheler wrote:
We are trying to build a stretch NFS root. We keep getting this error:
#
Setting up
We are trying to build a stretch NFS root. We keep getting this error:
#
Setting up dracut (044+241-3) ...
dracut: Generating /boot/initrd.img-4.9.0-3-amd64
dracut: dracut module 'livenet' depends on 'url-lib', which can't be
installed
dracut:
My disk_config is this:
disk_config disk1 align-at:4k fstabkey:uuid
primary / 2048- ext4
rw,acl,async,noatime,errors=remount-ro
primary swap 4096 swap sw
primary /var/cache/openafs 1024 ext2 rw,noatime
I would like the swap partition to be encrypted. How do I
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,
