From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 18 03:05:30 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D8AA106566C; Mon, 18 Jul 2011 03:05:30 +0000 (UTC) (envelope-from prvs=41809205dd=devin.teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 02EE68FC1C; Mon, 18 Jul 2011 03:05:29 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa02 [127.0.0.1]) by ltcfislmsgpa02.fnfis.com (8.14.4/8.14.4) with SMTP id p6I2m7hQ023963; Sun, 17 Jul 2011 21:49:45 -0500 Received: from sbhfisltcgw01.fnfis.com ([10.132.248.121]) by ltcfislmsgpa02.fnfis.com with ESMTP id xjs5e03f3-10; Sun, 17 Jul 2011 21:49:45 -0500 Received: from sbhfisltcgw01.FNFIS.COM ([10.132.248.121]) by sbhfisltcgw01.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Sun, 17 Jul 2011 21:44:21 -0500 Received: from [10.0.0.104] ([10.132.254.136]) by sbhfisltcgw01.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Sun, 17 Jul 2011 21:41:10 -0500 Mime-Version: 1.0 (Apple Message framework v1084) From: Devin Teske In-Reply-To: <4E23797A.8060209@FreeBSD.org> Date: Sun, 17 Jul 2011 19:41:08 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <4966ACA5-DA61-445D-8C22-C337D032E756@vicor.com> References: <4E23797A.8060209@FreeBSD.org> To: Doug Barton X-Mailer: Apple Mail (2.1084) X-OriginalArrivalTime: 18 Jul 2011 02:41:10.0274 (UTC) FILETIME=[26EDF620:01CC44F4] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813, 1.0.211, 0.0.0000 definitions=2011-07-17_05:2011-07-16, 2011-07-17, 1970-01-01 signatures=0 Content-Type: text/plain; charset="ISO-8859-1" Cc: freebsd-hackers@freebsd.org, f0andrey@gmail.com, "Teske, Devin" Subject: Re: [RELEASE] New Boot-Loader Menu bugs? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2011 03:05:30 -0000 On Jul 17, 2011, at 5:08 PM, Doug Barton wrote: > There also seems to be a bug with the new boot loader that if you bounce > out to the prompt and do 'boot kernel.other' Hmmm... The last change to the FICL word "boot" was 10 years, 9 months ago, by dcs = in version 1.19 of sys/boot/forth/loader.4th. I know that I haven't touched that word, but I'll have to double-check to s= ee if I'm overriding it in any way. I can see by the code in loader.4th that "boot" will automatically call "un= load" for you if/when an argument is present (e.g., "boot kernel.other"). I personally have never used that syntax (I've always said "unload" before-= hand), but I will take it from the code that this is supposed to work. > the kern.module_path sysctl > is not updated. If you want to change module_path for loader(8), you should set it in loade= r.conf(5). The FICL word "start" (as seen in /boot/loader.rc) will: (a) read loader.conf(5) and then (b) take your customized module_path and (c) search for a suitable kernel in those directories NOTE: that is, if "kernel" was not already set -- which it is, by default, = to "/boot/kernel" sysctl(8) is not (and, IIRC, cannot be) influenced by loader environment va= riables. However, you can retrieve the loader(8) variables via kenv(1). If you wanted to, you could create an rc.d or RCNG script to use kenv(1) to= do things with the loader(8) variables (such as drop them into loader.conf= (5) or sysctl.conf(5)). Be careful though. > It still lists /boot/kernel first; but that should be > replaced by /boot/kernel.other. I'm not familiar with the latter behavior. -- Devin ______________________________________________________________________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.