Quoting Vladimir 'φ-coder/phcoder' Serbinenko, who wrote the following on...:
Resending because of wrong oi-dev address at first try which caused it
to be rejected from other 2 lists as well
On 08.11.2011 02:19, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
With this patch on top of trunk I was able to compile (using GCC+GAS+GNU
LD), install, generate config and boot OpenIndiana. Some areas are grey
to me. As like:
1) Is it better to determine zfs-bootfs parameter on boot or on config.
(These opinions are based on Oracle Solaris):
Some grub entries may not specify a bootfs, in which case, GRUB should
derive it from the bootfs property in the pool
GRUB-Legacy does former but it has the problem that rpool may be
inaccessible to GRUB (it may be that only /boot/grub is accessible to it)
If the rpool is in accessible, then the top-level dataset should also be
inaccessible (unless I'm misunderstanding what you mean).
2) What's the best way to handle "local" keyword?
Remove it ;) ?
3) Does Illumos support* multiple kernels?
(For O.S.) This is something that developers would use, IMHO, but not
something for production, because the boot environment construct is used to
isolate different bootable instances.
--S
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
