Talk:Install Server

Having had more than one install server disappear, koanhead is working on automating the setup process. Results posted to github.

pxelinux.cfg/default

include mybootmenu.cfg
default ubuntu-installer/i386/boot-screens/vesamenu.c32
prompt 0
timeout 100

mybootmenu.cfg

menu hshift 13
menu width 49
menu margin 8
menu title Trusty NetBoot Menu
include ubuntu-installer/i386/boot-screens/stdmenu.cfg
menu begin Cool options
    default livei386
    label livei386
        menu label Xubuntu 14.04 Live 32bit
        kernel ubuntu-livecd-boot/i386/vmlinuz
        append boot=casper netboot=nfs nfsroot=192.168.0.1:/srv/nfs/live-files/i386 initrd=ubuntu-livecd-boot/i386/initrd.lz -- splash quiet
    label liveamd64
        menu label Xubuntu 14.04 Live 64bit
        kernel ubuntu-livecd-boot/amd64/vmlinuz
    append boot=casper netboot=nfs nfsroot=192.168.0.1:/srv/nfs/live-files/amd64 initrd=ubuntu-livecd-boot/amd64/initrd.lz -- splash quiet
menu end

interface-change.sh

#wired - services listen on this iface
auto allow-hotplug eth0
iface eth0 inet static
   address 192.168.0.1
   netmask 255.255.255.0
up /etc/init.d/tftpd-hpa start
up /etc/init.d/isc-dhcp-server start
up exportfs -a

#radio - connected to internets
allow-hotplug wlan0
iface wlan0 inet dhcp
   wpa-ssid "Network-essid"
   wpa-psk "wpa-password"

Computer with bad mobo

I came across a computer that had a bad motherboard... (memory errors occurred with any ram that i tried)

I'm wondering if that was it.

I'll be there on Saturday towards the end of the session AaronPeterson (talk) 14:56, 31 October 2014 (PDT)

I'm not sure what you mean by 'if that was it'... the server that refuses to PXE boot has OK ram as far as I can tell, the netboot issue is due to protocol mismatch between old client / new server I think. Details on page. Of the servers I set up before, one physically went missing and one got wiped by someone else.

Koanhead (talk)