From owner-freebsd-questions@FreeBSD.ORG Thu Dec 26 22:40:40 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E4125427 for ; Thu, 26 Dec 2013 22:40:39 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A407F1840 for ; Thu, 26 Dec 2013 22:40:39 +0000 (UTC) Received: from r56.edvax.de (port-92-195-127-162.dynamic.qsc.de [92.195.127.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id D3E90276FE; Thu, 26 Dec 2013 23:40:30 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id rBQMe8oC001977; Thu, 26 Dec 2013 23:40:09 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Thu, 26 Dec 2013 23:40:08 +0100 From: Polytropon To: g8kbvdave@googlemail.com Subject: Re: No System sources? (update) Message-Id: <20131226234008.0777c00e.freebsd@edvax.de> In-Reply-To: <52BC3261.31622.35C3BC@g8kbvdave.gmail.com> References: <52AF4D2A.13679.1A7A5A9@g8kbvdave.gmail.com> <52B7135F.16024.96D587C@g8kbvdave.gmail.com> <52BC3261.31622.35C3BC@g8kbvdave.gmail.com> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 22:40:40 -0000 On Thu, 26 Dec 2013 13:42:57 -0000, g8kbvdave@googlemail.com wrote: > > On Sun, 22 Dec 2013, g8kbvdave@googlemail.com wrote: > > > > > Update: > > > > > > I've found (after a LOT of reading...) I can do what I need (enable pps support > > > in the kernel) without recompiling, by creating:- > > > > > > /boot/loader.conf.local > > > > > > with an entry:- > > > > > > pps_load="YES" > > > > > > Then, kldstat shows that module (pps.ko) is loaded after boot. > > > > That line can be added be added to /boot/loader.conf, no need for a > > separate .local file. > > Hi Warren. > > Only used /boot/loader.conf.local, as from what I read, it is more "machine > specific", so applies for all users regardless. But otherwise OK. The .local separation can be applied to certain files in the FreeBSD system, however this is mostly for organisational aspects of system administration, there is, as far as I know, no functional aspect as those files are sourced the same way as the "normal" ones. If you compare to OpenBSD, there you'll find a comparable approach, even though there's a stronger emphasize on keeping things separated (for example system settings go to /etc/rc.conf and should probably not be altered, local settings go to /etc/rc.conf.local). In FreeBSD, there's also /etc/rc.local to "extend" /etc/rc, as well as /etc/rc.shutdown.local respectively, even though those can be considered "present for historical reasons" (rc.conf.local content to rc.conf, rc.(shutdown.)local content to rc.d-style scripts), but they still work. >From "man loader.conf", the FILES section: /boot/defaults/loader.conf default settings -- do not change this file. /boot/loader.4th defines the commands used by loader to read and process loader.conf. /boot/loader.conf user defined settings. /boot/loader.conf.local machine-specific settings for sites with a common loader.conf. In comparison, from "man rc.conf": The /etc/rc.conf file is included from the file /etc/defaults/rc.conf, which specifies the default settings for all the available options. Options need only be specified in /etc/rc.conf when the system adminis- trator wishes to override these defaults. The file /etc/rc.conf.local is used to override settings in /etc/rc.conf for historical reasons. [...] Also see the rc_conf_files variable below. Summary: There's nothing wrong in using the .local files, as long as you remember what you've done. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...