`<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 2, 2013 at 9:12 AM, Jim Klimov <span dir="ltr"><<a href="mailto:jimklimov@cos.ru" target="_blank">jimklimov@cos.ru</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hello Theo, thanks for the prompt reply!<div class="im"><br>
<br>
On 2013-08-02 17:20, Theo Schlossnagle wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">
On Fri, Aug 2, 2013 at 7:44 AM, Jim Klimov <<a href="mailto:jimklimov@cos.ru" target="_blank">jimklimov@cos.ru</a><br></div><div class="im">
<mailto:<a href="mailto:jimklimov@cos.ru" target="_blank">jimklimov@cos.ru</a>>> wrote:<br>
That's a subjective question. I'd imagine it looks quite similar to<br>
some and starkly different to others.<br>
</div></blockquote>
<br>
Right... well, to put it another way: I have rehearsed the procedure<br>
to update older OpenSolaris SXCE servers to OpenIndiana before that<br>
project stalled (and then became too experimental), and while some<br>
servers can wait a few years more, others would quite benefit from<br>
an OS upgrade. If I've figured out the needed procedure for OI, would<br>
I likely easily adapt and reuse it for OmniOS, or should I expect to<br>
learn a lot of new stuff and restart rehearsing from scratch? :^)</blockquote><div><br></div><div>We don't use incorporations and consolidations the same way. So, the procedure will most certainly be different.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
No shipped X at all, not enough to run X stuff in anyway. You can,<br>
however, get X pkgs from pkgsrc.<br>
</blockquote>
<br></div>
Uh-huh... and is there an install-ready IPS repo of pkgsrc provided<br>
by OmniTI (or at least recommended, even if maintained by some other<br>
team), along with occasional updates of software in the repo?<br>
<br>
Sorry for this particular lame question, I guess I just did not get<br>
too far through the docs yet :\</blockquote><div><br></div><div><a href="http://comments.gmane.org/gmane.os.omnios.general/640">http://comments.gmane.org/gmane.os.omnios.general/640</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
If I build my own ZFS-root image for the networked installer, can it<br>
involve a hierarchy of several datasets or just one root FS dataset?<br>
<br>
<br>
Not as a baked in feature, but there is post-install scripting available<br>
and you could easily make that happen without modifying kayak. (just zfs<br>
recv the extra data sets over the network after the rpool is recv'd). I<br>
think you'll be pleasantly surprised by the simplicity and power of kayak.<br>
</blockquote>
<br></div>
And is that all received as a "zfs-send" stream packed into a file?<br>
I mean, are there any limitations in Kayak today that would limit an<br>
ability to receive a "replication" stream which already includes a<br>
hierarchy of datasets? In a simple case - a hierarchy rooted under<br>
one common root filesystem dataset - for example, rpool/ROOT/rootfs<br>
and rpool/ROOT/rootfs/var (and maybe some split usr/ and opt/)?..<br>
I would likely need scripted receiving for my other half of the<br>
general setup - the rpool/SHARED/var/* datasets (logs, mail, etc.)<br>
to be common across different BEs.</blockquote><div><br></div><div>I've never tried. I see no reason it couldn't work.</div><div> </div></div>-- <br>
<p>Theo Schlossnagle</p>
<p><a href="http://omniti.com/is/theo-schlossnagle" target="_blank">http://omniti.com/is/theo-schlossnagle</a></p>
</div></div>
`