Moinak Ghosh wrote: > jan damborsky wrote: > >> Sanjay Nadkarni wrote: >> >> >>> I built the a version of the live CD using the slim prototype approach >>> and pieces are coming togther. >>> The system booted up and installed on the target disk without a >>> problem. However a couple of issues after install still >>> exist. >>> >>> 1. Solaris2 fdisk partition should be set as active. >>> >>> >>> >> If "whole disk" path is chosen, "active" flag is set automatically by >> "fdisk -B" command >> in TI when partition is being created. >> I think, it might not be the problem to have it set so early, because >> Solaris2 partition is >> the only one which will exist on the selected disk. >> >> For "existing Solaris2 partition" case, I was curious and tried what >> happens, if other partition >> is set active. I have found out that if stage1 of Solaris GRUB is >> installed in MBR, stage2 GRUB >> is always booted from Solaris2 partition regardless of which one is set >> as active. >> >> I have taken a look an installgrub(1M) man page which says: >> >> "WARNINGS >> Installing GRUB on the master boot sector (-m option) over- >> rides any boot manager currently installed on the machine. >> The system will always boot the GRUB in the Solaris parti- >> tion regardless of which fdisk partition is active." >> >> It seems that unlike GNU GRUB Solaris version of GRUB stage1 doesn't honor >> "active" flag. >> >> It might be subject of discussion, if it is safe to rely on this GRUB >> behavior for >> October release. >> >> > > GRUB stage1 does not use active flag. Rather it directly > loads stage2 from the partition that was patched into > the stage1 binary by installgrub. This happens even if the > Solaris partition is not active. > > Using installgrub without "-m" put mboot instead of GRUB > stage1 into the MBR that does honor the active flag. This > is what happens with Solaris installation I believe. >
Yes. You are right. I have taken a look at the code and that install doesn't put GRUB stage1 into MBR (installgrub is being used without "-m" option). Then mboot is present in MBR and it boots from partition marked as "active". Thank you very much for clarifying this ! Jan > Regards, > Moinak. > > >> Jan >> >> >> >>> 2. NWAM service was not enabled. >>> 3. generic.xml->generic_open.xml - Dave M addressing this. >>> >>> I also tried using the hiddenmenu option in GRUB. This worked fine. >>> However I am not sure I liked the effect. What I saw a black screen. >>> At the top of the screen was a line with the count down to boot. The >>> background/foreground for this line was blue on white. So the visual >>> effect was not pleasing to me. I would be interested in feedback from >>> others especially Frank and the JDS folks. >>> >>> -Sanjay >>> >>> >>> _______________________________________________ >>> caiman-discuss mailing list >>> caiman-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>> >>> >>> >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >> >> > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >
