Date: Mon, 14 Jun 2021 15:42:09 +0100 From: tech-lists <tech-lists@zyxst.net> To: freebsd-questions@freebsd.org Subject: Re: freebsd tftp server for hetrogenous diskless clients Message-ID: <YMdqwfr4edCEEnDI@ceres.zyxst.net> In-Reply-To: <17986d52-bbf3-96a7-e1bb-4ecdee69962c@nber.org> References: <YMYVIi3p/SHY9cby@ceres.zyxst.net> <17986d52-bbf3-96a7-e1bb-4ecdee69962c@nber.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--pG3BIwHX3XejJ6n4 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 13, 2021 at 12:02:49PM -0400, Daniel Feenberg wrote: >We have more than 30 Linux clients PXE booting from a FreeBSD server. This >is not a network install, /bin /sbin etc are NFS mounts. > >We have been doing this for many years, currently the Linux clients are >all CentOS, they have been Ubuntu at times in the past. Both FreeBSD and >Linux have been kept up to current supported releases. > >We like PXE booting with system files on read-only server because it makes >updates quick and easy, ensures uniformity across clients and is in >general convenient. We don't do it to save disk space. Network bandwidth >is not really a problem - 1GBE is fine for this, although we upgraded to >10GBE some years ago because the applications do a lot of network I/O. If >you lose the network connection the client will hang till the network is >restored, and jobs will continue from where they left off. Hi Daniel, Thanks for confirming this. Can you recommend any guides/how-tos as https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-dis= kless and man 8 diskless seem to only address freebsd clients and servers? I'm looking for an example with say ubuntu as client. or briefly describe how= =20 you did it? The clients need to always get the same IP address. I guess this would be tied to the MAC in some way. One issue is that there is already a dhcp server active on the router. If the freebsd tftp/pxe/nfs server is another dhcp server on the same network, they'll clash. How can this be avoided? thanks, --=20 J. --pG3BIwHX3XejJ6n4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAmDHarcACgkQs8o7QhFz NAVxPw/+MUs0iuiC8Q8mYFVKKhC2vD5MBIljnBf1xGLvXHmdaSm6cxUUyt0OmMqF HFTPbfNkwFz0dvuCmGGQPodXII/OkaTtbbZ9J8rpnF48Gt/nn9JjNgNxtVyJVCnr ciEn2QbmDnSmlzr5+G0jZPRCNBrqZuvleWuPgmUfEIWL/sjUFZ0OCPr2OskQsOGw bDnssHWAuB+jPlzYkL51TLvrnp1VF3F6F+WkYEoFd78OzSYYZSMbGSsBltZ7IEUo cyBk94NdgLeKPyviid17VU1IMW2LIlVpkuPQIfRZldhRLwLZCzhqGe2WrD8YVLcC 9wVwaDbVTHk+JmduDDvwSWCpa2WMBesyXL9ZLsX83DlndgwhxFK3j7ZmxnfQkHMo dT7COCKSaoBO82GuDA3tKOw2KlT+C0l2qamRGfEpSvP9SmmB8r9zoKJu9xkqSYXZ 0eYmPKtOMqXLOBImSHLHKBfvecuezckrbBf/0de1zQE7leYoR2Np6jt1Dfcv3TCg g2qyUXfUJTv6EkUENsj1N4lJrA4Klfp4DwMmNs4rWXohue/ZP/LQ14mOp5ycS5v4 ka/mL8Z6LdLsZ+4cDnpVcXF0gBaJMggUrxD0qMK1T6TTp0SJzkG7ypFIgqb5ITvI nnnR8g5d/FfpcD3/iNnFpjKw4fFYhsAg4BdhQTgKeeii7NsolCc= =JJI5 -----END PGP SIGNATURE----- --pG3BIwHX3XejJ6n4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YMdqwfr4edCEEnDI>