On Sep 15, 2014, at 11:46 PM, Doug Hughes wrote:
>
> I can confirm that miniroot is available in r151012! That's good. Also the
> zfs build image builds cleanly. However, something appears to be wrong with
> either the miniroot. I'm pretty sure it's the mintroot based upon the fact
> that th
On 9/15/2014 8:28 PM, Dan McDonald wrote:
On Sep 15, 2014, at 8:24 PM, Dan McDonald wrote:
Actually... I'd fixed these in the bloody branch, and have fixed them as well
in the r151012 branch. If you checkout either of those branches, you should
see the mods (and a comment reminding future
On Sep 15, 2014, at 8:24 PM, Dan McDonald wrote:
>
> Actually... I'd fixed these in the bloody branch, and have fixed them as well
> in the r151012 branch. If you checkout either of those branches, you should
> see the mods (and a comment reminding future folks to keep 'em up to date).
To b
On Sep 15, 2014, at 8:18 PM, Doug Hughes wrote:
>
> I figured out how to build the miniroot after skulking around the utils a bit.
>
> I had to make the same edits to ./build_image.sh that I did to the
> build_zfs_send.sh (http://pkg.omniti.com/omnios/release =>
> http://pkg.omniti.com/omnio
I figured out how to build the miniroot after skulking around the utils
a bit.
I had to make the same edits to ./build_image.sh that I did to the
build_zfs_send.sh (http://pkg.omniti.com/omnios/release =>
http://pkg.omniti.com/omnios/r151010)
after that running gmake with tftp-install made
On 9/15/2014 4:00 PM, Dan McDonald wrote:
On Sep 15, 2014, at 3:26 PM, Doug Hughes wrote:
I had some problems with 006 also, but these appear to be different so far. I
took an omniOS 008 machine and upgraded to 010 using the standard upgrade
mechanism. Totally successul. My /etc/release is
On Sep 15, 2014, at 3:26 PM, Doug Hughes wrote:
>
> I had some problems with 006 also, but these appear to be different so far. I
> took an omniOS 008 machine and upgraded to 010 using the standard upgrade
> mechanism. Totally successul. My /etc/release is updated and everything is
> fine. T
I had some problems with 006 also, but these appear to be different so
far. I took an omniOS 008 machine and upgraded to 010 using the standard
upgrade mechanism. Totally successul. My /etc/release is updated and
everything is fine. Then I made sure that the kayak and kayak-server
packages we
Mark,
Each LU in Comstar has a "writeback cache" property. Maybe you had that enabled
instead?
Kyle
Message: 1
Date: Sun, 14 Sep 2014 21:30:50 +1200
From: Mark
To: omnios-discuss@lists.omniti.com
Subject: Re: [OmniOS-discuss] Fibre Target problems
Message-ID: <5415604a.7030...@gmail.com>
Conte
15 сентября 2014 г. 4:05:52 CEST, Dan McDonald пишет:
>Saw this retweeted on twitter. Anyone here care about Jenkins running
>on OmniOS? (His calling out of OI is likely just improper conflation.)
>
>Dan
>
>Begin forwarded message:
>
>> From: "Dan McDonald (via Twitter)"
>> Subject: Dan McDonal
I had same error some time ago for full build. It seems if some of required
build dependencies for component are missed, then this line in buildctl fails:
PATH=$PATH:. $SCRIPT -r $PKGSRVR $batch_flag $lint_flag || \
May be passing some flag for build deps autoinstall could solve this.
Alex
>
Hi Jim,
I am building on a local zfs filesystem with atime=on and sync=disabled.
I'veI also had problems with NFS mountpoints, so I avoid building on it.
On Sun, Sep 14, 2014 at 3:53 PM, Jim Klimov wrote:
> 14 сентября 2014 г. 3:41:36 CEST, Dan Vatca пишет:
> >Yes, it does it sometimes even wh
12 matches
Mail list logo
