Difference between revisions of "Talk:Install Arch from network via PXE"

From ArchWiki
Jump to: navigation, search
(Netboot ?)
m
Line 31: Line 31:
  
 
== Confirm : instructions are outdated ==
 
== Confirm : instructions are outdated ==
What I wrote as workaround in bash to do the trick ( none solutions on aur, wiki works with archlinux-2011.08.19-core-i686.iso !) :
+
What I wrote as workaround in bash to do the trick ( none solutions on aur, wiki or bbs works as-is with archlinux-2011.08.19-core-i686.iso !) :
  
 
<pre>
 
<pre>
Line 51: Line 51:
 
netboot $broadcats $serverip $range $clientmac
 
netboot $broadcats $serverip $range $clientmac
 
</pre>
 
</pre>
 +
 +
Quick & dirty, but that works, I can boot my EEEPC 1005HA with PXE (no cdrom)
 +
 +
--[[User:Sputnick|Sputnick]] 19:08, 3 September 2011 (EDT)

Revision as of 23:08, 3 September 2011

Use of mkpxelinux script is overkill

The entirety of the "mkpxelinux" sections of this guide can be summed up as using the "mkpxelinux" package to install the package "syslinux" as a dependency and copy the /usr/lib/syslinux/pxelinux.0 to /var/tftpboot. Nothing else provided by the "mkpxelinux" script is used since all of the files that it installs are wiped out by copying the contents of the archboot isolinux folder over /var/tftpboot.

In the situation where you already have a working pxeboot environment setup, you may not want to blindly copy all of the files from the iso over the /var/tftpboot directory. This guide should be expanded to explain PXE booting on a more general level so as to encourage users to understand PXE booting

--Daschu 18:43, 12 August 2009 (EDT)

No doubt you are correct, me having no clue about the general level of PXE booting. I was forced to use it, however, by mean circumstances. After fiddling around long enough to get it working, I fixed the heavily outdated wiki page to merely get some working instructions up again.
Please, everyone more familiar with PXE, go ahead and edit! Cheers, Hokasch 19:06, 22 September 2009 (EDT)

Is a USB-drive required..?

Isn't the thing with PXE boot that you only need a network connection? That you don't need a CD/DVD or USB-drive? If I understand this guide correctly, you set up dhcpd and tftpd, only to *boot* Arch, and then Arch mounts the install image/USB-drive. I might be wrong, but is it not possible to get the install-image over tftp? I think this would be a much better solution. --Bjoernfan 03:57, 4 December 2008 (EST)

Article out of date?

Well it seems this got a bit out of date... "mkpxelinux -a" is not a valid command, it doesn't accept the "-a", furthermore there is no pxelinux.0 file in /usr/share/mkpxelinux

Out of date

Article seems out of date:

  1. - Their is no such file boot/archlive.img after mounting the Arch.2009.02.img
  2. - Also pxelinux.0 does not exist in /usr/share/mkpxelinux/pxelinux.0

Netboot ?

I just packaged netboot on AUR, which is a minimal implementation of DHCP + BOOTP for easy PXE boot. Using it instead of dhcpd+tftpd is easier and requires less configuration, so I think it would be interesting to modify the instructions on this page to use it. Delroth 12:40, 9 March 2010 (EST)

Confirm : instructions are outdated

What I wrote as workaround in bash to do the trick ( none solutions on aur, wiki or bbs works as-is with archlinux-2011.08.19-core-i686.iso !) :

#!/bin/bash

broadcast=192.168.0.255
serverip=192.168.0.1
range=192.168.0.201,192.168.0.253
clientmac=00:22:33:44:55:aa:ee

[[ $1 ]] || { echo >&2 "Usage: $0 /path/to/iso; exit 1; }

trap '\rm -f /arch /nbd-server.conf' 0 1 2 3 15

archiso-pxe-server -s "$1"
pkill dnsmasq
cd /tmp/archiso-pxe-server/syslinux
cp -a ../nbd-server.conf arch /
netboot $broadcats $serverip $range $clientmac

Quick & dirty, but that works, I can boot my EEEPC 1005HA with PXE (no cdrom)

--Sputnick 19:08, 3 September 2011 (EDT)