http://etherboot.org/wiki/ 2026-05-07T17:06:33-07:00 http://etherboot.org/wiki/ http://etherboot.org/wiki/lib/tpl/monobook/images/favicon.ico text/html 2009-06-02T09:30:24-07:00 http://etherboot.org/wiki/soc/2009/dverkamp/notes/buildbot?rev=1243960224&do=diff BuildBot setup notes I am currently using a Debian stable (5.01) system, but this should work similarly on other distributions or with BuildBot installed from source. $ sudo aptitude install buildbot edit /etc/default/buildbot: BB_NUMBER[0]=0 # index for the other values; negative disables the bot BB_NAME[0]="foo" # short name printed on startup / stop BB_USER[0]="buildbot" # user to run as BB_BASEDIR[0]="/var/lib/buildmaster" # basedir argum… text/html 2009-06-19T06:51:08-07:00 http://etherboot.org/wiki/soc/2009/dverkamp/notes/linux_mkbootfs?rev=1245419468&do=diff Linux bzImage boot Test Boot into a minimal Linux/busybox system created using mkbootfs via HTTP. DUT configuration No physical disks present. System configured to boot from NIC equipped with gPXE ROM. Environment configuration Apache HTTP server providing gPXE script, kernel, initrd, and modules as separate files. gPXE script set to instruct client to download kernel, initrd and relevant modules. DHCP server providing network configuration and path to gPXE script on HTTP server. text/html 2009-06-06T10:53:30-07:00 http://etherboot.org/wiki/soc/2009/dverkamp/notes/linux_tftp?rev=1244310810&do=diff Linux bzImage boot over TFTP Test Boot into a minimal Linux/busybox system created using mkbootfs via TFTP. DUT configuration No physical disks present. System configured to boot from NIC equipped with gPXE ROM. Environment configuration tftpd-hpa server providing gPXE script, kernel, initrd, and modules as separate files. gPXE script set to instruct client to download kernel, initrd and relevant modules. DHCP server providing network configuration and path to gPXE script on TFTP server… text/html 2009-06-19T06:37:40-07:00 http://etherboot.org/wiki/soc/2009/dverkamp/notes/start?rev=1245418660&do=diff Daniel Verkamp: Automated regression testing Notes Detailed test cases * Windows XP iSCSI * Windows PE * Linux mkbootfs Unfinished * Windows iSCSI forward authentication * Windows 7 install to iSCSI * Linux TFTP Potential test cases NOTE: brainstorming; not final * Protocol tests: download image, verify integrity * HTTP * HTTPS * text/html 2009-06-16T09:49:55-07:00 http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_7_install_to_iscsi?rev=1245170995&do=diff Windows 7 install to iSCSI Test Install a Windows 7 operating system on an iSCSI target. DUT configuration No physical disks present. System configured to boot from NIC equipped with gPXE ROM. Environment configuration iSCSI target running IETD. DHCP server providing network configuration and iSCSI root-path. text/html 2009-06-05T08:05:11-07:00 http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_iscsi_forward_authentication?rev=1244214311&do=diff Windows iSCSI forward authentication Test Boot into a Windows Server 2003 operating system stored on an iSCSI target that requires forward CHAP authentication. DUT configuration No physical disks present. System configured to boot from NIC equipped with gPXE ROM. NIC non-volatile storage configured with iSCSI username and password. text/html 2009-06-09T14:51:28-07:00 http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_pe?rev=1244584288&do=diff Windows PE boot Test Boot into a Windows PE operating system generated according to these instructions via TFTP. DUT configuration No physical disks present. System configured to boot from NIC equipped with gPXE ROM. Environment configuration TFTP server hosting WinPE files. DHCP server providing network configuration and path to WinPE's text/html 2009-06-12T15:46:57-07:00 http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_xp_iscsi?rev=1244846817&do=diff Windows iSCSI forward authentication Test Boot into a Windows XP operating system stored on an iSCSI target. DUT configuration No physical disks present. System configured to boot from NIC equipped with gPXE ROM. Environment configuration iSCSI target running IETD set up to require forward CHAP authentication. DHCP server providing network configuration and iSCSI root-path.