From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>,
developer@lists.illumos.org, oi-dev@openindiana.org
Subject: Re: [PATCH] Support OpenIndiana in GRUB2
Date: Tue, 08 Nov 2011 02:24:29 +0100 [thread overview]
Message-ID: <4EB884CD.2050106@gmail.com> (raw)
In-Reply-To: <4EB8839C.2000701@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
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.
> 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)
> 2) What's the best way to handle "local" keyword?
> 3) Does Illumos support* multiple kernels?
> 4) Does Illumos support* snapshot or subvolume booting
>
> *=support=kernel is capable of handling it, we can do whatever we want
> on bootloader level.
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next parent reply other threads:[~2011-11-08 1:24 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 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-11-08 18:16 ` [PATCH] Support OpenIndiana in GRUB2 Seth Goldberg
2011-11-08 19:17 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4EB884CD.2050106@gmail.com \
--to=phcoder@gmail.com \
--cc=developer@lists.illumos.org \
--cc=grub-devel@gnu.org \
--cc=oi-dev@openindiana.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).