From owner-freebsd-current@freebsd.org Thu Oct 22 20:16:13 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B95D8A1CEE4 for ; Thu, 22 Oct 2015 20:16:13 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9C5431627 for ; Thu, 22 Oct 2015 20:16:13 +0000 (UTC) (envelope-from lars@netapp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 99DA3A1CEE3; Thu, 22 Oct 2015 20:16:13 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 996DFA1CEE2 for ; Thu, 22 Oct 2015 20:16:13 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx143.netapp.com (mx143.netapp.com [216.240.21.24]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mx143.netapp.com", Issuer "Symantec Class 3 Secure Server CA - G4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6998C1626; Thu, 22 Oct 2015 20:16:12 +0000 (UTC) (envelope-from lars@netapp.com) X-IronPort-AV: E=Sophos;i="5.20,184,1444719600"; d="scan'208";a="73906536" Received: from hioexcmbx05-prd.hq.netapp.com ([10.122.105.38]) by mx143-out.netapp.com with ESMTP; 22 Oct 2015 13:15:42 -0700 Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx05-prd.hq.netapp.com (10.122.105.38) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 22 Oct 2015 13:15:42 -0700 Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::e1d9:911e:3048:d510%21]) with mapi id 15.00.1104.000; Thu, 22 Oct 2015 13:15:42 -0700 From: "Eggert, Lars" To: Ian Lepore CC: "current@freebsd.org" Subject: Re: env functionality of config(5) has no effect? Thread-Topic: env functionality of config(5) has no effect? Thread-Index: AQHRC9fHKfB6BJNlVEazj7PKhw5wOJ54V6cA//+dg5I= Date: Thu, 22 Oct 2015 20:15:42 +0000 Message-ID: <641BBA24-447D-453C-B2E2-47503559A517@netapp.com> References: <0F998D21-682B-4B41-8248-B072F468184B@netapp.com>, <1445540892.14963.22.camel@freebsd.org> In-Reply-To: <1445540892.14963.22.camel@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2015 20:16:13 -0000 amd64 --=20 Sent from a mobile device; please excuse typos. +49 151 120 55791 > On Oct 22, 2015, at 21:08, Ian Lepore wrote: >=20 >> On Wed, 2015-10-21 at 08:09 +0000, Eggert, Lars wrote: >> Hi, >>=20 >> I'm trying to include some loader tunables in the kernel, via the >> "env" functionality described in config(5). >>=20 >> When I look at the compiled kernel binary with strings(1), I see that >> the tunables are compiled in. >>=20 >> However, they don't seem to take any effect when booting the kernel, >> and they also don't show up when running kenv(1) after boot. >>=20 >> Any ideas? >>=20 >> Thanks, >> Lars >=20 > I finally found a few minutes to look into this today. You didn't say > what platform you're working with. It appears that this has only ever > worked on i386 and a handful of old arm and mips platforms. >=20 > -- Ian