Talk:Install Server: Difference between revisions

From Free Geek Seattle
No edit summary
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
I'm going to post a really basic shell script here to replicate the setup I have on headwaiter (the install on which this article is based).
Having had more than one install server disappear, [[koanhead]] is working on automating the setup process. Results posted to github.
I will also place the file in the [[Special:Files]] section so it will be wget-able. Later there will be a more refined, general-purpose script on our github.
 
==pxelinux.cfg/default==
<pre>
include mybootmenu.cfg
default ubuntu-installer/i386/boot-screens/vesamenu.c32
prompt 0
timeout 100
</pre>
 
==mybootmenu.cfg==
<pre>
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
</pre>


== install-server-setup.sh ==


!#/bin/bash


# run this as root, but READ IT FIRST.
== Computer with bad mobo ==
# BEFORE you run this, edit the ./interface-changes.txt file.
# if you don't see that file, don't run this script, it won't work without that file present. But it WILL break things.


apt-get install isc-dhcp-server tftpd-hpa nfs-kernel-server
I came across a computer that had a bad motherboard...  (memory errors occurred with any ram that i tried)


cp /etc/network/interfaces /etc/network/interfaces.old


cat ./interface-changes > /etc/network/interfaces
I'm wondering if that was it.


== interface-change.sh ==
I'll be there on Saturday towards the end of the session [[User:AaronPeterson|AaronPeterson]] ([[User talk:AaronPeterson|talk]]) 14:56, 31 October 2014 (PDT)
<pre>
 
#wired - services listen on this iface
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.
allow-hotplug eth0
 
iface eth0 inet static
[[User:Koanhead|Koanhead]] ([[User talk:Koanhead|talk]])
  address 192.168.0.1
  netmask 255.255.255.0
#radio - connected to internets
allow-hotplug wlan0
iface wlan0 inet dhcp
  wpa-ssid "Network-essid"
  wpa-psk "wpa-password"
</pre>

Latest revision as of 02:00, 29 November 2014

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

pxelinux.cfg/default[edit]

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

mybootmenu.cfg[edit]

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


Computer with bad mobo[edit]

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)