Binu Jose Philip wrote:
>Moinak Ghosh <Moinak...@Sun.COM> writes:
>> OpenSolaris as of today is not yet self-hosting. Which means
>>that you cannot yet have a "pure" bootable OpenSolaris
>>environment. As yet some of the critical components (including
>>libm.so.1) are closed source.
>>So you need to first install the Solaris Express (Nevada)
>>community edition and then build OpenSolaris and do a BFU. It
>>should be possible to have an OpenSolaris setup with the
>>missing parts filled up with GNU components.
>Does this mean, Nevada can/will live in my existing grub config
>if asked? In other words, I install nevada to some partition
>(formatted as ufs which linux understands?) and do some magic on
>my existing grub conf, my Sun built neavada can be booted. Then I
>go in there and build+install whatever opensolaris components,
>including the kernel, that I want.
>Is it better to let nevada live on whole disk or will it
>co-operate with existing grub?
>Does the current Linux fs-drivers r & w nevada ufs - atleast
You will need to use the Grub that comes with Nevada since Grub
has been modified to read UFS partitions so that it can load the
Solaris kernel and boot archive(miniroot). This patch is in the
process of being contributed back to the Grub project.
Nevada Grub will be able to boot your Linux, Windoze and Nevada
partitions. So dedicate one primary partition to Solaris where
you create all the slices and install Nevada and allow Nevada
to put Grub in MBR. Then boot into Nevada and do some magic
with grub.conf to boot the other OSes. Then you can build and
upgrade to OpenSolaris.
Linux UFS support is not yet safe for RW access. RO access is
recommended. BTW I believe there is an old ext2 module for
Solaris 9. It might be interesting to make it work properly on