Boomer Updates

Just a quick note: no Boomer beta release this week. Due to a bug which we fixed in ON, but which we are dependent upon, there won't be any formal beta release until after SXCE b107 ships. And it will depend on SXCE b107. (And likewise, when the OpenSolaris package repos are updated to use b107, you'll be able to use OpenSolaris and Boomer together.)

I probably will post an updated code review, and possibly BFU archives, for the folks that want to play with these bits earlier and are willing to deal with BFU. (Hmmm.. does BFU work correctly on OpenSolaris? I've only used it on SXCE.) That posting will probably occur on Monday or Tuesday of next week. Stay tuned.

(Is there any interest in an external Mercurial repo for this stuff? I hadn't been planning on one, but if folks want one and will use it, I'll look into it.)

Comments

Binary Crusader said…
BFU does work correctly on OpenSolaris 200x.x. However, once you've used BFU you can't upgrade the boot environment you used BFU in, so it's not something you should do without careful consideration.

With that said, you could use the boot environment manager to create a copy of the 107 boot environment, activate that copy, reboot, then apply the BFU to that copy and experiment with it.

Once you were done experimenting, you could then reactivate the original 107 boot environment, reboot, and then destroy the copy and continue to be able to update your system.

Anyway, this is great news to hear; I'm looking forward to OpenSolaris being the 2nd UNIX vendor to have a real audio subsystem (Apple being the 1st).
Cyril Plisko said…
(Is there any interest in an external Mercurial repo for this stuff? I hadn't been planning on one, but if folks want one and will use it, I'll look into it.)
On the other hand - if there will be no external Mercurial repo - there will be exactly zero interest. I think public repo should be a default (like open PSARC case).
Unknown said…
The problem with this is that an open repo doesn't come for free. It takes time and effort to transition the internal repo to the outside, and there may be legal requirements to ensure that the code is properly vetted.

This project had the start of its life as a closed project, and it still has changes to the closed tree (mostly in the form of *removing* closed bits and replacing them with open ones!)

Hence, we can't use a public hg repo as our "main" tree; we have to use an internal rep that includes the closed bits for our work.

So, again, if there is someone that has an interest in accessing the hg tree *before* we putback, I'll look into it. But I'm not going to waste my time if there is no real interest. The code should be going into the open ON repository in the next month or so anyway.
vermaden said…
QUOTE:Binary Crusader

I'm looking forward to OpenSolaris being the 2nd UNIX vendor to have a real audio subsystem (Apple being the 1st).

OpenSolaris being the 3RD UNIX, while Apple being 2ND ... and FreeBSD being 1ST which has full in-kernel OSS channel mixing long before all the rest ...

Popular posts from this blog

SP (nanomsg) in Pure Go

An important milestone

GNU grep - A Cautionary Tale About GPLv3