Date: Wed, 7 May 2014 12:14:55 +0200 From: Egoitz Aurrekoetxea <egoitz@ramattack.net> To: dteske@FreeBSD.org Cc: freebsd-hackers@freebsd.org, amine tay <amine.tay91@gmail.com> Subject: Re: FreeBSD 9.X network installation using PXE+TFTP (not NFS) ! Message-ID: <A74E3EDC-6081-4503-A347-915495729142@ramattack.net> In-Reply-To: <1a6901cf3a30$7b7b8ed0$7272ac70$@FreeBSD.org> References: <CAMMGsZ%2BBOpLowveVLOoGZqTNva1o%2BiHXwu28dW1X-Uf%2BnG476w@mail.gmail.com> <1a6901cf3a30$7b7b8ed0$7272ac70$@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi!, Take a look, http://postfixquotareject.ramattack.net/freebsdpxehowto.pdf Now by default all is built with BSD installer although you could always = build you=92re own disks with Makefile.sysinstall=85.. Tell us if you have more questions=85 Regards! El 07/03/2014, a las 19:10, dteske@FreeBSD.org escribi=F3: >=20 >=20 >> -----Original Message----- >> From: amine tay [mailto:amine.tay91@gmail.com] >> Sent: Friday, March 7, 2014 2:36 AM >> To: freebsd-hackers@freebsd.org >> Subject: FreeBSD 9.X network installation using PXE+TFTP (not NFS) ! >>=20 >> Hi everyone, >=20 > Hello. >=20 >> I'm trying to perform a FreeBSD 9.X network installation using = PXE+TFTP > (not >> NFS) ! >> The problem using NFS is the need to specify the root-path in the = dhcp > conf, >> therefore we can't deploy multiple releases or different images of > freebsd. >>=20 >=20 > You're correct that utilizing the root-path identifier of dhcpd.conf = limits > your > abilities. However, that does not mean that you can't use NFS. >=20 > Before you say anything else, look at these images that I created for = my > setup: > http://druidbsd.sf.net/download/pxe-config.png > http://druidbsd.sf.net/download/FreeBSD_PXE_Install_Workflow_alt.gif >=20 > The later "workflow" image shows a comparison against iPXE based = cobbler > and my latest setup that I created last week: > http://druidbsd.cvs.sf.net/druidbsd/pxe-config/ > http://druidbsd.sf.net/download/tftpboot.txz >=20 >=20 >> So to enable the tftp instead of NFS we have to edit make.conf with = these > lines >> LOADER_TFTP_SUPPORT=3DYES LOADER_NFS_SUPPORT=3DNO and rebuild the >> pxeboot file >>=20 >=20 > Make sure you choose your TFTP server software carefully if you're = going to > go > the route of loading any files >32MB over TFTP. >=20 > To support >32MB single file over TFTP make sure you use tftp-hpa > (ftp/tftp-hpa) > which I have enabled on my server with the following rc.conf entries: >=20 > tftpd_enable=3D"YES" > tftpd_flags=3D"-p4B 1024 -s /tftpboot -a 192.168.1.1" >=20 >=20 >> 1st question is : Is this modification going to allow the install of > differents >> freebsd images? >>=20 >> Note that I'm using an automated os deployement solution , and I am = using >> mac-adresses to deploy freebsd depending on policies, so for exemple = two >> clients with different mac-adresses will have two diffrents freebsd > images. >>=20 >=20 > If you don't add pxelinux to the mix and rely on dhcpd for the = solution of > using the MAC address to change the identifiers handed to the PXE boot > client, that may work but may also limit you. >=20 > pxelinux ( which comes from the sysutils/syslinux port -- of which I > submitted > an update recently, bringing the latest version to 6.02 *fixing* = broken HTTP > based loading of ISO files; = http://www.freshports.org/sysutils/syslinux/ > )... >=20 > ... provides 2 functionalities that help you. First, it can actually = do the > same > thing as your dhcp MAC binding and choose a specialized config to be = loaded > over TFTP based on the MAC address.=20 >=20 > ... and second, but more importantly, it can provide an interactive = menu > with > a list of options. >=20 > However, integrating syslinux's pxelinux, gpxelinux, or lpxelinux = modules > into > the FreeBSD workflow can be challenging. That's why I'm providing the = above- > mentioned "pxe-config" tool to simplify the process of integrating a = menu of > multiple FreeBSD choices. >=20 > The requirements of which are (as shown in the Workflow GIF above): >=20 > DHCP (net/isc-dhcp43-server) > TFTP (either freebsd-tftp or tftp-hpa will do fine; files >32M loaded = over > HTTP) > HTTP (e.g., www/apache22) > SMB *or* NFS (nfs is built-in, for SMB e.g. net/samba36) >=20 > I wanted the system to work from a jail, so hence the SMB support. >=20 > If you have questions, don't hesitate to ask. > --=20 > Cheers, > Devin >=20 > _____________ > The information contained in this message is proprietary and/or = confidential. If you are not the intended recipient, please: (i) delete = the message and all copies; (ii) do not disclose, distribute or use the = message in any manner; and (iii) notify the sender immediately. In = addition, please be aware that any message addressed to our domain is = subject to archiving and review by persons other than the intended = recipient. Thank you. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A74E3EDC-6081-4503-A347-915495729142>