[OmniOS-discuss] Installer Crashes While 'Probing for DeviceNodes'

[Theo Schlossnagle]

That uname hash will match a commit in our illumos-omnios tree:

http://omnios.omniti.com/browse.php/core/illumos-omnios

http://omnios.omniti.com/changeset.php/core/illumos-omnios/eae537bad35e09fb6be6db8ea368cd25c07ef77e

If you work backward from there you'll find that
eb36692e8e3d1add7a4530a507a828476656941b is the version of
illumos-gate we branched from.  You are running release.  My bloody
box is  bit easier:

; uname -a
SunOS vitrial 5.11 omnios-33fdde4 i86pc i386 i86pc

commit 33fdde4db8344e316d03e0582b73cdc5608c8f1e
Merge: 1568459 989f280
Author: Theo Schlossnagle <jesus at omniti.com>
Date:   Thu Oct 4 18:11:52 2012 +0000

    Merge branch 'upstream'

So we pulled in from [989f280] on illumos-gate.. which happens to be
the latest commit as of this email. :-)

Hope that helps.


On Thu, Oct 4, 2012 at 8:51 PM, Paul B. Henson <henson at acm.org> wrote:
> On 10/4/2012 3:54 PM, Eric Sproul wrote:
>
>> Unfortunately there isn't an easy way.
>
>
> Aw, well...
>
>
>> It might be possible to include that in our /etc/release but I think
>> that would require tracking the illumos-gate IDs separately from
>> illumos-omnios ones. It's the latter that get encoded in various
>> places (uname -v, /etc/motd) depending on when they are built.
>
>
> So would the non-easy way then be to clone your git repo, find the commit
> corresponding to the OmniOS release in use, and see if the commit of
> interest from upstream was merged before that?
>
> How do you tell which commit in your git repo a given release is from? The
> one I have installed reports "eae537b" but that doesn't seem to be a
> substring of any commit in your repo?
>
> Thanks...
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss



-- 
Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle