- Ursprüngliche Mail -
> Von: "Dan McDonald"
> An: "Stephan Budach"
> CC: "omnios-discuss" , "Dan McDonald"
>
> Gesendet: Mittwoch, 1. März 2017 19:56:42
> Betreff: Re: [OmniOS-discuss] CALL
Please refresh your copy by downloading here:
http://kebe.com/~danmcd/webrevs/r151021-kayak.iso
Here are the checksums:
md5 (r151021-kayak.iso) = f4a726113e74dd84e3c74d9f5cfe7c95
sha1 (r151021-kayak.iso) = d9c6381e7d7c792610b5f19c1c3a546b168d495a
sha256
Shoot, the pkgrecv isn't done yet. Stay tuned...
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
Because I'm experimenting with Kayak-for-ISO, I want to have fresh
illumos-omnios bits (esp. Loader itself) on the public server. I've just
pushed new packages (full build) out to the bloody repo. Update highlights
include:
- AIO improvements in LX
- Some loader bugfixes
- blkdev fixes for
In 45 days, OmniOS r151018 (old-Stable) will reach end-of-service-life. Users
should update to current-stable, r151020, if they haven't already.
Unlike prior releases, the next Stable, and next LTS, r151022, will not be
ready until approximately June, due to the sheer number of upstream
If you are user of LTS (r151014) or Stable (r151020), please "pkg update" and
be ready for a new BE and a reboot.
Included in this update are:
- bge fixes on HP Gen9 systems
- MSI-X for NVMe is disable on VMware (where MSI-X is a problem)
- mmap() now properly modifies a
> On Mar 1, 2017, at 1:02 PM, Stephan Budach wrote:
>
> Hi Dan
>
> Well, I just got it a shot on my Oracle VM cluster and after the iso loaded,
> it threw this on the screen:
>
> BTX loader 1.00 Starting in protected mode (base mem=9d400)
> .
> .
> .
> BIOS CD is cd0
>
Hi Dan
- Ursprüngliche Mail -
> It MIGHT, and you're the sort of person I need to confirm/deny it.
>
> Watch for a kebe.com link later today.
>
> Dan
>
>
Well, I just got it a shot on my Oracle VM cluster and after the iso loaded, it
threw this on the screen:
BTX loader 1.00
On Wed, 1 Mar 2017 12:16:14 -0500
Dan McDonald wrote:
>
> This is on Xen? There's a fix coming for this:
>
No, qemu.
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael rasmussen cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir datanom
> On Mar 1, 2017, at 11:00 AM, Michael Rasmussen wrote:
>
> I have digged deeper into this problem and have discovered that it is
> actually a very critical problem since the low-level disk tools
> recognizes the disk but the kernel has mapped the disk to another disk
> so that
> On Mar 1, 2017, at 8:56 AM, N. Nadine Miller wrote:
>
> I installed pkgsrc some time ago and attempted to upgrade this
> morning. When I attempted to update the pkg tools, it gave me an error
What exactly do you mean when you says "update the pkg tools"?
> regarding
I installed pkgsrc some time ago and attempted to upgrade this
morning. When I attempted to update the pkg tools, it gave me an error
regarding 32-bit vs 64-bit, so reflexively I checked 'uname' output to
verify I hadn't broken my recent update to r151020.
I discovered that 'uname' incorrectly
On Tue, Feb 28, 2017 at 10:35 PM, Dan McDonald wrote:
>
> > On Feb 28, 2017, at 5:22 PM, Peter Tribble
> wrote:
> >
> > Dan,
>
>
>
> > Ok, some comments (I'm wearing 2 hats here, one as an omnios
> > customer, the other as someone who's
Okay. Not even seeing the loader screen then... shoot. Good news is that
there are some new fixes in loader from upstream that I'm building now. A new
test ISO will get spun from them.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Feb 28, 2017, at 10:37 PM, Doug Hughes
14 matches
Mail list logo