grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] Support OpenIndiana in GRUB2
Date: Tue, 08 Nov 2011 20:17:34 +0100	[thread overview]
Message-ID: <4EB9804E.2070706@gmail.com> (raw)
In-Reply-To: <alpine.GSO.2.00.1111081013230.965@oretfbsg>

[-- Attachment #1: Type: text/plain, Size: 2202 bytes --]

On 08.11.2011 19:16, Seth Goldberg wrote:
>
>
> 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
>
bootfs is an annoying one since on-disk AFAIK only its objnum is stored
so we need to scan to determine its name. But for me it's only
backward-compatibility issue. This property shouldn't be necessary with
new or autodetected config.
>>> 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).
>
You can have a small disk locally holding only GRUB2, kernel and boot
archive and rpool in a SAN, boot_archive taking care of mounting rpool.
>>> 2) What's the best way to handle "local" keyword?
>
>   Remove it ;) ?
>
I have a patch for it few lines down in this ML.
>>> 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.
Could you explain better what's boot environment is? Is it separate
subvolume? How do we discover them. Should it be on runtime or config time?
>
>  --S
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2011-11-08 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4EB8839C.2000701@gmail.com>
2011-11-08  1:24 ` [PATCH] Support OpenIndiana in GRUB2 Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-08 18:16   ` Seth Goldberg
2011-11-08 19:17     ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-11-08 19:37       ` Seth Goldberg
2011-11-08 20:01         ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-08 19:53       ` Seth Goldberg
     [not found]   ` <4EB99F38.7020303@alum.mit.edu>
2011-11-08 21:38     ` [oi-dev] " Vladimir 'φ-coder/phcoder' Serbinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EB9804E.2070706@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).