From owner-freebsd-hackers Sun Dec 1 13:23: 1 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7EE237B401 for ; Sun, 1 Dec 2002 13:22:59 -0800 (PST) Received: from clover.kientzle.com (user-112uh9a.biz.mindspring.com [66.47.69.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBABF43EA9 for ; Sun, 1 Dec 2002 13:22:57 -0800 (PST) (envelope-from kientzle@acm.org) Received: from acm.org (c43 [66.47.69.43]) by clover.kientzle.com (8.11.3/8.11.3) with ESMTP id gB1LMnE26459; Sun, 1 Dec 2002 13:22:49 -0800 (PST) (envelope-from kientzle@acm.org) Message-ID: <3DEA7DA9.2050801@acm.org> Date: Sun, 01 Dec 2002 13:22:49 -0800 From: Tim Kientzle Reply-To: kientzle@acm.org User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.6) Gecko/20011206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: lm Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: file handle References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG lm wrote: > I have some FreeBSD diskless machines, 4.7 ones, working fine. > Now, because i know what variables to set, i do not want bootp anymore. Why not? DHCP (I prefer DHCP to bootp): * Does not load the network very much * Allows you to change boot information from a single central server (if your NFS server changes, you change one entry on your DHCP server; you don't need to change something on every machine) * Is stable and well-supported. > I guess that freebsd do not think in this situation. Today, HD is not so > expansive, and a misc solution is fine! It is quite common to use a local HD together with network booting: * Local swap makes things much faster * Local /tmp removes the need to have per-client directories on the server for that purpose * Many people even copy certain applications from the server to the local HD at boot time. For example, you might copy /usr/local and /usr/lib from the server on every boot. This makes boot much slower, but can dramatically speed up regular operations, especially if you have a very large number of machines. (Some Beowulf-style systems do this.) * Loading a kernel from local disk is usually a bad idea; keeping the kernel on the server simplifies future updates. Remember: systems do not boot very often; maintenance is more important than speed. Most people find DHCP very helpful and don't want to eliminate it. It keeps your network information in a single place which simplifies management of your network. Tim Kientzle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message