Categories

• Announcements

  Get the latest news on what's happening.
  168
  Topics
  706
  Posts

  T

  @Tom-Elliott said in Ubuntu is FOG's enemy: apt-get -y remove unattended-upgrades This saved my bacon, thank you very much, first command failed but second one worked, i have also run the unattended-upgrades command, once again thank you.
• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  1981
  Topics
  15981
  Posts

  

  Ubuntu 1910 Desktop Under development 17-Jan-2020 First we’ll create the required directories: mkdir -p /images/os/ubuntu/Desk19.10 mkdir -p /tftpboot/os/ubuntu/Desk19.10 Now we’ll mount the Ubuntu 19.10 installer over the loop directory. Then we’ll copy the contents of the DVD to the directory we built above. mount -o loop -t iso9660 /{full path where you have the iso stored}/ubuntu-19.10-desktop-amd64.iso /mnt/loop cp -R /mnt/loop/* /images/os/ubuntu/Desk19.10 umount /mnt/loop Finally we’ll copy the pxe boot kernel and intfs to the tftpboot directory. We’ll need to download the netboot version from here: http://archive.ubuntu.com/ubuntu/dists/eoan/main/installer-amd64/current/images/netboot/netboot.tar.gz This version of bzlinuz.efi and initrd.lz support booting over an NFS share instead of the local DVD Drive. wget http://archive.ubuntu.com/ubuntu/dists/eoan/main/installer-amd64/current/images/netboot/netboot.tar.gz tar -zxf netboot.tar.gz cp ./netboot/vmlinuz.efi /tftpboot/os/ubuntu/Desk19.10 cp ./netboot/initrd.lz /tftpboot/os/ubuntu/Desk19.10 The last bit of magic we need to do is setup a new FOG iPXE boot menu entry for this OS. In the fog WebGUI go to FOG Configuration->iPXE New Menu Entry Set the following fields Menu Item: os.Ubuntu.Desktop.19.10 Description: Ubuntu Desktop 19.10 Parameters: kernel tftp://${fog-ip}/os/ubuntu/Desk19.10/vmlinuz.efi initrd tftp://${fog-ip}/os/ubuntu/Desk19.10/initrd.lz imgargs vmlinuz.efi root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:/images/os/ubuntu/Desk19.10/ locale=en_US.UTF-8 keyboard-configuration/layoutcode=us quiet splash ip=dhcp rw boot || goto MENU Menu Show with: All Hosts That’s it, just pxe boot your target system and pick Ubuntu Desktop 19.10 from the FOG iPXE boot menu. References:
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  9551
  Topics
  94376
  Posts

  P

  @Lee-Rowlett That is a sound route, I’ll keep it in mind while I dig into it. Yeah, I was hoping it was some other reason than permissions, but somehow over the last week permissions changed on the server, so it is probably how I’ve got it setup. The main system is installed on a 512 GB M.2 Nvme, and the images are stored on a 2TB HDD that I have mounted to the images folder. The permissions didn’t have a date last changed, so I’m guessing something happened with that mount at some point, maybe a power outage or brownout and maybe it reset the mount long enough to fubar the permissions? Pure conjecture… but it was a permissions issue…
• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  2059
  Topics
  19377
  Posts

  

  I’ve removed Arch Linux from the automated tests due to complications within Terraform. These issues were sort of the final straw in my Arch testing efforts. The Arch community doesn’t supply an official AWS AMI. I had been relying on a privately built AMI that isn’t 1:1 with a manual Arch installation. For perhaps the last half year, my Arch tests were failing but the installer worked if you tested it against a manually setup Arch installation. This can only be due to differences between the AMI I was using and a manual installation. The Arch community is vehement about only providing help if you follow their installation instructions on their wiki exactly. Because of this, when I asked for some help sorting out the issues, they were not willing to help. Until someone with some Arch prowess can put some time into helping with this, Arch Linux will not be included in the automated tests.