From owner-freebsd-current Fri Feb 5 14:56:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15901 for freebsd-current-outgoing; Fri, 5 Feb 1999 14:56:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15896 for ; Fri, 5 Feb 1999 14:56:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.2) with ESMTP id OAA00510 for ; Fri, 5 Feb 1999 14:56:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: current@FreeBSD.ORG Subject: Heads up on new sysinstall changes. Date: Fri, 05 Feb 1999 14:56:45 -0800 Message-ID: <506.918255405@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1. Userconfig parameter saving should work again, albeit somewhat differently than before. Rather than having a program (dset) pound bits directly into your kernel, a /boot/kernel.conf file is written out by sysinstall, along with a set of /boot/loader.rc file entries to make use of it. If you've already got a loader.rc file, sysinstall won't touch it but will instead instruct you on what to add. This is not to say that you can boot -c any time and have your parameters saved entirely like in the old days. This is (for the time being) solely a feature of sysinstall, not the rc scripts, and good only for initial install/upgrade time. 2. Sysinstall no longer writes customizations into /etc/rc.conf, reserving that file as a "template" of config data. Sysinstall's customizations are written into /etc/rc.conf.site, the /etc/rc.conf.local file remaining free for site-specific use as always. This makes the task of keeping /etc up to date that much easier since you can just copy over a new rc.conf at any time if your /etc starts getting stale. The Feb 6th snapshot (for both 4.0 and 3.0S) should contain these changes. Please test them out as they do represent some fairly sweeping internal changes to sysinstall. Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message