From owner-freebsd-questions Sun Oct 31 18:46:47 1999 Delivered-To: freebsd-questions@freebsd.org Received: from proxy4.ba.best.com (proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (Postfix) with ESMTP id 2BC6715032 for ; Sun, 31 Oct 1999 18:46:44 -0800 (PST) (envelope-from mda@discerning.com) Received: from mdaxke (cm-24-142-61-115.cableco-op.ispchannel.com [24.142.61.115]) by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id SAA15433 for ; Sun, 31 Oct 1999 18:45:53 -0800 (PST) Message-ID: <004301bf2413$4d6a64a0$0200a8c0@mdaxke> From: "Mark D. Anderson" To: Subject: how to replicate a kernel config and binaries across heterogenous hw? Date: Sun, 31 Oct 1999 18:46:00 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this must be a FAQ, but i can't find it. i suppose that is what this list is for.... supposing i have chosen my desired kernel build parameters, concerning whether i want quota enabled, promiscuous ethernet, blah, blah, as well as other options. i'd now like to use those decisions on all freebsd machines i manage -- or at least, the ones with like purpose (such as all web server or all db servers or all firewall machines). i'd also like to just sync binaries to other machines -- i'm ok if this means building in support for all devices, and not have to make world on each one. some machines have multiple scsi disks, some have just one IDE disk, etc. of course, there is still some per-host config that has to be preserved (devices, hostname, etc.). when i decide to fetch new kernel sources, i'd like to just build it once and install multiple places. i don't need to hear about dd and rsync and scp and other replication mechanisms. i can do that. i'm worried about traps in what might happen if i replicate the wrong thing: about freebsd-specific issues, such as files i need to worry about, what config decisions are really determined at kernel compile time and not runtime, and other recipes from people who have done this. on a related note, for certain production machines, i'd like to be able to minimize as much as possible the downtime due to a kernel upgrade. are there general tips on that? note that i run my firewall machine with an init security level that effectively forbids writes. -mda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message