From owner-freebsd-hackers Fri Feb 14 18:49:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA22355 for hackers-outgoing; Fri, 14 Feb 1997 18:49:26 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA22259; Fri, 14 Feb 1997 18:48:41 -0800 (PST) Message-Id: <199702150248.SAA22259@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA148424740; Sat, 15 Feb 1997 13:45:40 +1100 From: Darren Reed Subject: Re: undocumented kernel options... To: thorpej@nas.nasa.gov Date: Sat, 15 Feb 1997 13:45:40 +1100 (EDT) Cc: msmith@atrad.adelaide.edu.au, phk@critter.dk.tfs.com, leisner@sdsp.mc.xerox.com, bsdcur@shadows.aeon.net, freebsd-current@freebsd.org, freebsd-hackers@freebsd.org In-Reply-To: <199702140807.AAA14402@lestat.nas.nasa.gov> from "Jason Thorpe" at Feb 14, 97 00:07:58 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Jason Thorpe, sie said: [...] > Documentation on how to edit a kernel configuration file is loads better > IMO than having a rigid GUI (so, you update config to deal with new syntax, > and how you have to update the GUI, as well...) (So, if you've ever used > HP's SAM, you'll understand just how frustrating using a GUI to configure > your kernel can be, if you've previously used "vi CONFIGNAME".) > > ...plus, the user can insert arbitrary, random options.... major win. If anyone was ever tempted to do anything like SAM, I'd make them use it for every system admin. task first and see of that changed their mind. (Yes, we edit the config files rather than use SAM).