Date: Wed, 4 May 2011 08:57:32 -0700 From: Devin Teske <dteske@vicor.com> To: Jason Hellenthal <jhell@DataIX.net> Cc: freebsd-hackers@freebsd.org, 'Dieter BSD' <dieterbsd@engineer.com> Subject: Re: [RELEASE] New Boot-Loader Menu Message-ID: <5536F45D-82C1-44EE-8BF2-E1C081FAC095@vicor.com> In-Reply-To: <20110504040621.GC78390@DataIX.net> References: <20110430192737.287270@gmx.com> <DD1F639830154CDF9EFF3DF790795293@shxd.ath.cx> <20110501031105.GA16357@DataIX.net> <CE451F5A-1D05-455C-9081-41585245AEF3@vicor.com> <20110504040621.GC78390@DataIX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 3, 2011, at 9:06 PM, Jason Hellenthal wrote: >=20 > Devin, >=20 >=20 > On Sat, Apr 30, 2011 at 08:45:14PM -0700, Devin Teske wrote: >>=20 >> On Apr 30, 2011, at 8:11 PM, Jason Hellenthal wrote: >>=20 >>>=20 >>> Devin, >>>=20 >>>=20 >>> On Sat, Apr 30, 2011 at 04:00:47PM -0700, Devin Teske wrote: >>>>=20 >>>>> Would be nice: "uname -v" of the kernel it will boot. >>>>=20 >>>> That's a bit more technically challenging. I'll have another look at t= he >>>> FICL words available, but I don't recall if there was a way to crawl t= he >>>> object space of the items loaded with ``load'' (looking for the uname)= . I'm >>>> open to suggestions if you had an idea of how to do this in Forth -- e= lse >>>> I'd think this would need to be a loader(8) modification. >>>=20 >>> How about forgetting a mention of unmae & ... instead look into if we >>> can support some sort of bootcode versioning to be displayed on the >>> screen. This would serve to be very helpful in the future when for say a >>> new version of bootcode for ZFS has to be installed then it would be >>> easy for announce@ to simply say "A new version of ZFS has been MFCd and >>> requires boot version >=3D X. To find out your version please see the >>> bottom right hand corner of your boot screen." >>>=20 >>> I would place a pretty good bet that loader(8) could be modified to >>> export some sort of versioning of the bootcode to make this a easier >>> stance for the user to gather information before a upgrade. >>=20 >> Piece of cake! If you give me a loader(8) that exports a "version" envir= onment variable, I'll give the Forth functionality in mere seconds. It's al= ready been developed (but was not packaged). >>=20 >> I have a module named "version.4th" which prints the value of the "versi= on" environment variable at the bottom-right of the screen underneath the b= eastie logo. >>=20 >> Since you mention this, I'll add the code to the next package and if/whe= n loader(8) ever exports a "version" environment variable, it will just mag= ically appear. How's that sound? >>=20 >=20 > Sounds perfect! One minor adjustment... can we make that environment variable "loader_versi= on" instead of "version"? The code is already in for "loader_version". Whatever string you export int= o that environment variable will be displayed on-screen at bottom-right, ri= ght-justified. --=20 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. _____________
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5536F45D-82C1-44EE-8BF2-E1C081FAC095>