[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: [RELEASE] New Boot-Loader Menu
From:       Devin Teske <dteske () vicor ! com>
Date:       2011-05-30 2:26:30
Message-ID: 8C5F02EB-E700-453F-988A-0DEEB8BB263B () vicor ! com
[Download RAW message or body]


On May 29, 2011, at 6:08 PM, Julian Elischer wrote:

> On 5/29/11 2:53 PM, Devin Teske wrote:
> > On May 4, 2011, at 8:57 AM, Devin Teske wrote:
> > 
> > > On May 3, 2011, at 9:06 PM, Jason Hellenthal wrote:
> > > 
> > > > Devin,
> > > > 
> > > > 
> > > > On Sat, Apr 30, 2011 at 08:45:14PM -0700, Devin Teske wrote:
> > > > > On Apr 30, 2011, at 8:11 PM, Jason Hellenthal wrote:
> > > > > 
> > > > > > Devin,
> > > > > > 
> > > > > > 
> > > > > > On Sat, Apr 30, 2011 at 04:00:47PM -0700, Devin Teske wrote:
> > > > > > > > Would be nice: "uname -v" of the kernel it will boot.
> > > > > > > That's a bit more technically challenging. I'll have another look at \
> > > > > > > the FICL words available, but I don't recall if there was a way to \
> > > > > > > crawl the 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 -- else I'd think this would need to be a loader(8) \
> > > > > > > modification.
> > > > > > 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>= X. To find out your version please see the
> > > > > > bottom right hand corner of your boot screen."
> > > > > > 
> > > > > > 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.
> > > > > Piece of cake! If you give me a loader(8) that exports a "version" \
> > > > > environment variable, I'll give the Forth functionality in mere seconds. \
> > > > > It's already been developed (but was not packaged). 
> > > > > I have a module named "version.4th" which prints the value of the "version" \
> > > > > environment variable at the bottom-right of the screen underneath the \
> > > > > beastie logo. 
> > > > > Since you mention this, I'll add the code to the next package and if/when \
> > > > > loader(8) ever exports a "version" environment variable, it will just \
> > > > > magically appear. How's that sound? 
> > > > Sounds perfect!
> > > One minor adjustment... can we make that environment variable "loader_version" \
> > > instead of "version"? 
> > > The code is already in for "loader_version". Whatever string you export into \
> > > that environment variable will be displayed on-screen at bottom-right, \
> > > right-justified.
> > The code for thew new menu has been committed to HEAD.
> > 
> > http://svnweb.freebsd.org/base?view=revision&revision=222417
> > 
> > Now...
> > 
> > Who wants to make the necessary patch to loader(8) to export $loader_version \
> > text? 
> > Or maybe a suggestion on another list worth including on this?
> I suggest this move to -current since it is checked on there,
> and a port be kept for 8.x/7.x
> 
> Devin, a fix was made at 222450 as it was broken for ppc.
> 

Regarding fix 222450:

Oops. Slight oversight. Thanks for the one-liner fix.

Looks like we'll have to do the same thing for the following:

	sys/boot/ia64/common/Makefile
	sys/boot/powerpc/ps3/Makefile
	sys/boot/sparc64/loader/Makefile

Here's a patch that can be applied by anyone willing:

http://druidbsd.sourceforge.net/download/loader_menu-1.6.1-HEAD20110521092952-fixup.patch


-- 
Devin

_____________

The information contained in this message is proprietary and/or confidential. If you \
are not the intended recipient, please: (i) delete the message and all copies; (ii) \
do not disclose, distribute or use the message in any manner; and (iii) notify the \
sender immediately. In addition, please be aware that any message addressed to our \
domain is subject to archiving and review by persons other than the intended \
recipient. Thank you. _____________
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"


[prev in list] [next in list] [prev in thread] [next in thread]