On 04/19/10 13:13, Alexander Eremin wrote:
My experience from working with Solaris media: It is
useful to be able
to identify the build number by just mounting the
image. If one has to
try booting off of the image just to see that it's
build X instead of
build Y, that can be frustrating. If there were a
plain text file with
the build number that they can access, that could be
one solution. We
hadn't used build numbers for Solaris volids, but
people could find the
/etc/release file buried in the image and use that to
identify the
build. But since the LiveCD files are mostly
compressed into a
microroot, there isn't much visible that can give the
build number.
Is there a file that currently exists or can be
created that would have
the build ID easily found?
-- Alan
On 04/19/10 12:38 PM, Alexander Eremin wrote:
On 04/19/10 06:17, Alexander Eremin wrote:
Please review the fixes for:
15571 long volume IDs break x86 ISO image builds
if
customized grub menu
is long
Bug:
http://defect.opensolaris.org/bz/show_bug.cgi?id=15571
Webrev:
http://cr.opensolaris.org/~alhazred/15571/
Hi Alex,
Thank you for working on this bug.
You need to update the "distribution name" value
for
usr/src/cmd/distro_const/slim_cd/all_lang_slim_cd_x86.
xml. That's the
manifest
for the Live CD image that includes all the
languages. The distribution
name
there currently shows "OpenSolaris".
I want to clarify one thing. From reading the
code,
the volume id will now
just be whatever string we specified for
"distribution name" in the
manifest.
It will not be appended with snv_xxx, right? I
want
to make sure that's
the case, because in your email interchange with
Alan
Steinberg, you
keep using the example of:
OpenSolaris_X86_snv_134
OpenSolaris_AI_X86_snv_134
OpenSolaris_Text_X86_snv_134
In this case, in order to get those strings as the
volume id, we would have
to specify the build number ourselves, right?
Thanks,
--Karen
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-di
scuss
Hi Karen,
thanks for point about "all_lang_slim_cd_x86", I'll
fix this.
Alan told about volumeids which DC generates at
this time. I used the build number for identification
in 13276 fix, now as the UUID is used for the
identification, I am not sure that the build number
must be used with the distro_name for volumeid (it
may be appear in the Grub title?). Otherwise, need
to somehow indicate to the user that the volumeid
will consist of the distro_name + build number, and
length should be no more than 32 characters.
This time build number can be used with default
distro names in manifests but every time if the user
decides to change the distro name, he will have to
calculate the volumeid length. I can revert to this,
but experience has shown that it confuses users.
What you think?
Thanks,
Alex
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-di
scuss
Yes, I agree that it is very well to know the build number after iso mounting and possible solution
- just create a ".release" or ".build" file in CD root directory which will
contain the distro name and build number.
--
Alex
If you just mount the CD, and not boot it, you can take a look at the
/boot/grub/menu.lst file, which contains
entries of what would be displayed on the grub menu.
Unless the user customize the grub menu to not show the build number, by
default, DC uses the
build number from /etc/release.
The text that goes with the CD icon on the desktop displays what's
specified as the .volumeid. Not having
the build number or release string associated with the .volumeid means
that media from different
build will have the same string. Is it important to have a more user
friendly string displayed on the desktop?
--Karen
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
