Re: FreeBSD 9.X network installation using PXE+TFTP (not NFS) !
Hi!,
Take a look,
http://postfixquotareject.ramattack.net/freebsdpxehowto.pdf
Now by default all is built with BSD installer although you could always bu=
ild 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:
> =
> =
>> -----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) !
>> =
>> Hi everyone,
> =
> Hello.
> =
>> 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.
>> =
> =
> You're correct that utilizing the root-path identifier of dhcpd.conf limi=
ts
> your
> abilities. However, that does not mean that you can't use NFS.
> =
> Before you say anything else, look at these images that I created for my
> setup:
> http://druidbsd.sf.net/download/pxe-config.png
> =
> 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
> =
> =
>> 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
>> =
> =
> Make sure you choose your TFTP server software carefully if you're going =
to
> go
> the route of loading any files >32MB over TFTP.
> =
> 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:
> =
> tftpd_enable=3D"YES"
> tftpd_flags=3D"-p4B 1024 -s /tftpboot -a 192.168.1.1"
> =
> =
>> 1st question is : Is this modification going to allow the install of
> differents
>> freebsd images?
>> =
>> 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.
>> =
> =
> 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.
> =
> pxelinux ( which comes from the sysutils/syslinux port -- of which I
> submitted
> an update recently, bringing the latest version to 6.02 *fixing* broken H=
TTP
> based loading of ISO files; http://www.freshports.org/sysutils/syslinux/
> )...
> =
> ... provides 2 functionalities that help you. First, it can actually do t=
he
> same
> thing as your dhcp MAC binding and choose a specialized config to be load=
ed
> over TFTP based on the MAC address. =
> =
> ... and second, but more importantly, it can provide an interactive menu
> with
> a list of options.
> =
> However, integrating syslinux's pxelinux, gpxelinux, or lpxelinux modules
> into
> the FreeBSD workflow can be challenging. That's why I'm providing the abo=
ve-
> mentioned "pxe-config" tool to simplify the process of integrating a menu=
of
> multiple FreeBSD choices.
> =
> The requirements of which are (as shown in the Workflow GIF above):
> =
> 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)
> =
> I wanted the system to work from a jail, so hence the SMB support.
> =
> If you have questions, don't hesitate to ask.
> -- =
> Cheers,
> Devin
> =
> _____________
> The information contained in this message is proprietary and/or confident=
ial. 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 awa=
re that any message addressed to our domain is subject to archiving and rev=
iew 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"
_______________________________________________
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"
討論串 (同標題文章)
完整討論串 (本文為第 6 之 6 篇)：