Anyone done an "onu"-style ON gate install on OmniOS 151044?

I want to build just illumos gate and overlay that in a test BE.

See my email (if it got approved). make sure ONNV_BUILDNUM in your env matches your current set (e.g. export ONNV_BUILDNUM=151044 )

gwr - just sent an email to your thread too. This definitely should work (I do it most days).

Thanks. I was starting to wonder what was actually _meant_ to work, as attempts using /opt/onbld/env/omnios-illumos-gate were not going smoothly for me, and I didn't see anything about this procedure on omnios.org/dev/build_instructions. Thanks.

I'll try it again and follow up with some details about what I see.

Thanks, and we can get any documentation updated and things fixed if necessary.

I did an onu to gate bits this morning (on bloody, but that should not matter) so it works in principle at least!

I also might on occasion want to do an illumos build on my OmniOS server to be installed on an OI system.

As long as the VERSION that ends up in the packages is "newer" somehow than the existing OI packages, that should work

I know some people just use 9999.99.99.9 or whatever

The template under /opt/onbld/env picks it up from /etc/release IIRC

That _almost_ works for me but complained about lixml2 version (2.10.3 vs 2.10 IIRC). I guess for that to work properly I'd need an adjunct proto for OI, right?

but you might want to modify that anyway to adjust things like multi proto, debug/non-debug etc.

Every time I try to do anything clever, the pkg stuff says "no" to me :)

Yes, I'd guess so in that case, until they upgrade their package

I don't know enough about pkg to tell it "go ahead anyway, I consider those two versions close enough"?

If something has a dependency on libxml >= 2.10.3, then 2.10 is not going to satisfy it

you can use a package transform to rewrite the dependencies..

it's actually not too difficult to do that to adjust a package or two in the nightly repo

It's actually not an adjunct you need here, come to think of it

cool, but that's beyond my abilities. A read through the pkg man pages did not reveal to me the magic :)

you need to persuade the pacakge dependency resolver to require a lower version

Happy to gist it if you get to needing it

It would be helpful. At least one of the VMs I use a lot is OI (so I can use the full X stuff)

and I'd rather not bother with a zone.

(on the build server)

I'll write something up and drop a link here

Thanks for looking into illumos 14306 (fenix) btw

BUG 14306: Can't get SID for ID=0 type=0, status=-9977 (New)

↳ illumos.org/issues/14306 | code.illumos.org/c/illumos-gate/+/2630

Yeah, I have some more work to fix the reporting (so it can actually tell you what ID caused the problem)

Then we really should have a 2nd bug to fix up the cases where this complains.

So looking at OmniOS onu, it's a lot different from the old Sun one.

We don't use an on-nightly publisher?

Instead redirecting the omnios publisher, and turning off the signed requirement etc?

I think most of the important changes got upstreamed (in terms of functionality anyway).

Some people use on-nightly and make sure that omnios is non-sticky etc.

gwr: gist.github.com/citrus-it/d4f4479436cb7fcfe819ec4a07bf7d8f

you can also adjust publisher name, or the -151045 bit and so on in the same mog file

to massage things as needed to make OI happier

Thanks. Will try when I'm next ready to do things to an OI VM.

The example for this is example 10 in man.omnios.org/pkgrecv#EXAMPLES which is.. not the most obvious place to look

How is the publisher name specified for the build? I don't see it.

It should be in the Makefile.master

1162:PKGPUBLISHER_REDIST= on-nightly

and optionally overidden in the environment or .env file

that might be a reason you have to use the `onu` from gate, actually

andyf, danmcd, can one of you poke illumos.org/issues/15302 for me, please? While it isn't urgent now, I expect it to come up again with future server purchases.

→ BUG 15302: broadcom 3108 kernel driver update (New)

nomad: You may wish to make sure #illumos knows about this. I don't think I'm going to have cycles for this unless one of our paying customers is asking.

And there might be folks in places like Nexenta/Tintri that have interest in getting this done.

Thing is, we're paying omniosce, not illumos

I'll mention it there but was hoping for some big names to push it.

For things like device drivers, they need to go in upstream illumos first anyway, so it's best to alert the wider community.

I had hoped opening the ticket would count as alerting them.

Last time a lift was done here, danmcd, I think you got code from the vendor.

Somebody like Nexenta might have more luck doing that again

Yeah, via Joyent. Joyent got the code via the vendor, and passed it off to me@nexenta.

Otherwise the option is most likely to consider porting the driver over from somewhere like FreeBSD

There were some nontrivial updates from other people, and from what I can tell we won't need new code but updated code, which we probably can lift from FreeBSD.