As I've mentioned in the past to Dan, it's worth noting that Crossbow is
not the only project that has significant impact here -- e.g., Clearview
UV and Clearview IPMP (among other projects) also made significant changes
to both kernel and userland that are presumed to be in lockstep.
Part 2: solaris10 Brand
The solaris10 brand is conceptually similar to the existing solaris8
and solaris9 brands and builds directly on the BrandZ infrastructure
that was created to support the lx brand. Familiarity with BrandZ
and the solaris8 and
Hi Jerry,
This document provides a lot of useful information.
The section solaris10 Brand: What's Not Emulated
you repeat some old information that is no longer correct.
One point to note is that TX will continue to
be incompatible with branded zones.
That statement probably dates to the
Ellard Roush wrote:
Hi Jerry,
This document provides a lot of useful information.
The section solaris10 Brand: What's Not Emulated
you repeat some old information that is no longer correct.
One point to note is that TX will continue to
be incompatible with branded zones.
That statement
Enclosed is a first draft of a spec. for the S10
brand which we plan to submit for a PSARC
inception review. Please send us any comments
or questions.
Thanks,
Jerry
---
S10C: A Solaris 10 Branded Zone for Solaris.Next
Gerald Jelinek, Jordan Vaughan
On 05/12/09 13:28, Jerry Jelinek wrote:
Enclosed is a first draft of a spec. for the S10
brand which we plan to submit for a PSARC
inception review. Please send us any comments
or questions.
Thanks,
Jerry
Hi Jerry,
Cool stuff!
A couple of questions:
- it is stated that the minimum
Hi!
Will there be an adoption toolkit, to let the people use the S10 brand while
testing it, and starting the migration process?
Thanks a lot, and best regards,
HeCSa.
On Tue, May 12, 2009 at 8:28 AM, Jerry Jelinek gerald.jeli...@sun.comwrote:
Enclosed is a first draft of a spec. for the S10
Hernan Saltiel wrote:
Hi!
Will there be an adoption toolkit, to let the people use the S10 brand while
testing it, and starting the migration process?
I'm not sure I understand the question. Are you asking
if the source code will be available before S.next is
released? If so, then yes, we're
No, I'm talking about the Solaris migration toolkit, available in the past
to certify pre-Solaris 10 binaries against the new versions.
They were a couple of Perl scripts (solcat, for example). They were a binary
interface certification set of scripts.
They were a good point to start thinking in a
On 05/12/09 14:20, Jerry Jelinek wrote:
It wouldn't really be multiple versions of the brand. The idea is that
any enhancements to the brand module will need to continue to support
all versions of S10 that are supported in the zone (i.e. S10u8 and beyond).
So, there may be conditional code in
Hernan Saltiel wrote:
No, I'm talking about the Solaris migration toolkit, available in the past
to certify pre-Solaris 10 binaries against the new versions.
They were a couple of Perl scripts (solcat, for example). They were a binary
interface certification set of scripts.
They were a good
Menno Lageman wrote:
Thanks, that clears it up. Adding some text at the start of the
Versioning section that newer versions of the brand will provide
compatibility for older versions of the brand would help I think.
Thanks, I'll add that clarification.
Jerry
On Tue, May 12, 2009 at 6:28 AM, Jerry Jelinek gerald.jeli...@sun.com wrote:
[snip]
Zones have been part of S10 since its FCS, so in general S10 is
already zone-aware and does the right thing in most cases. Commands
that are zone-aware will continue to work as they do today in
S10 native
Jerry,
I am not sure if that was described in the proposal.
Would it be possible to run s10 brands ontop of future s10 global zones ?
-Ursprüngliche Nachricht-
Von: Jerry Jelinek gerald.jeli...@sun.com
Gesendet: 12.5.'09, 13:28
Enclosed is a first draft of a spec. for the S10
brand
Mike Gerdts wrote:
Any thoughts on supporting live upgrade? That is, I would like live
upgrade within the branded zone to work as it does for a S10 global
zone. I don't care about it from the upgrade standpoint, but it is a
very helpful tool for patching. Having a zfs zonepath is an
On Tue, May 12, 2009 at 8:02 AM, Jerry Jelinek gerald.jeli...@sun.com wrote:
Mike Gerdts wrote:
Any thoughts on supporting live upgrade? That is, I would like live
upgrade within the branded zone to work as it does for a S10 global
zone. I don't care about it from the upgrade standpoint,
Mike Gerdts wrote:
I suspect that making live upgrade work within a zone would be
significantly easier if ZFS was a prerequisite. It looks as though
the ipkg brand already has support for mounting the appropriate
dataset on boot and attach. Delegated datasets can be snapshotted and
cloned
17 matches
Mail list logo
