Hi Karen.
On 03/24/09 15:20, Karen Tung wrote:
> I am working on bug 5416
>
> 5416 GRUB shouldn't track nevada build numbers on official releases
> http://defect.opensolaris.org/bz/show_bug.cgi?id=5416
>
> My proposed solution to the bug is in the comment #12 field.
>
> This email discussion on how I plan to implement the solution.
> Your comments/suggestions are welcomed in one or both items below.
>
> 1) As discussed in the proposed solution,
> I plan to introduce a new field in the DC manifest for specifying
> an alternate title for entries in the grub menu.
> I am trying to decide where to put this field.
> The logical place is in the <grub_menu_modification> section
> of the DC manifest. Currently, this section contains additional
> entries to the grub menu. Here's an example of what is there today:
>
> <grub_menu_modifications>
> <entry>
> <title_suffix>with
> magnifier</title_suffix>
> <line>kernel$
> /platform/i86pc/kernel/$ISADIR/unix -B assistive_tech=magnifier</line>
> <line>module /boot/boot_archive</line>
> </entry>
>
> .....
> <grub_menu_modifications>
>
> I plan to add the entry as follows:
>
> <grub_menu_modifications>
> <title>My special title for the grub menu</title>
>
> <entry>
> <title_suffix>with
> magnifier</title_suffix>
> <line>kernel$
> /platform/i86pc/kernel/$ISADIR/unix -B assistive_tech=magnifier</line>
> <line>module /boot/boot_archive</line>
> </entry>
>
> .....
> <grub_menu_modifications>
Sounds good.
>
> Even though "title" sounds very general, the fact that it is
> within the <grub_menu_modification> block means that it
> is only applicable to grub_menu_modifications.
There are currently three entries (excluding the hard disk entry) which
appear in menu.lst when the <grub_menu_modification> section is blank or
missing. These are:
OpenSolaris 2009.06 snv_xxx X86
OpenSolaris 2009.06 snv_xxx X86 VESA driver
OpenSolaris 2009.06 snv_xxx X86 text console
Are you suggesting to exclude these from the new title? I think that
would be a mistake. The title should affect all entries (except hard
disk) whether placed in menu.lst automatically or specified by the manifest.
> 2) Another problem to solve is how to pass this special string into
> the grub menu of the installed system. I was planning to parse out
> the special string from the Live CD's
> menu.lst. However, I realized that there are many
> entries in the Live CD's menu.lst and many of them have suffix.
> So, which one should I use as the title.
>
> At this time, the DC creates the Live CD's grub menu entries
> and I know for a fact that the first entry does not have the suffixes.
> I remember discussion about future improvement and the possibility of
> moving the accessibility entries to the top or something.
> So, perhaps it is not a good idea for me to rely on the order of
> the Live CD's grub menu entries.
>
> To solve this problem, I propose putting the special string for
> the grub menu(if any) into the .image_info file on the Live CD.
> This entry to .image_info will only be added if there's a special title.
> The ICT can look up the info from the .image_info and modify the
> entries in menu.lst as needed. This won't rely on the ordering of
> the grub menu entries, and avoids all the parsing of Live CD's menu.lst.
> Your thoughts?
DC (grub_setup.py specifically) already gets the "base" title from
/etc/release, so you already have it at your disposal. I would imagine
that the proposed changes would be implemented in this same file, which
would make it really convenient for you. If the manifest had something
specified for the title, it could override the /etc/release value. This
should handle it for liveCD.
I'm not sure what ICT does at hard-disk install time, but by the time it
would run, it could just interrogate the liveCD's menu.lst for the
release string. If you are worried about which menu.lst string it would
parse, then how about adding a commented, keyed line in menu.lst which
would have a magic string ICT can look for, followed by the release
string it should use.
Thanks,
Jack
>
> Thanks,
>
> --Karen
>
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
