seems good to me, although I am not overly familiar with p5m's I usually
let build.sh deal with those.
On 2014-09-04 22:14, Dan McDonald wrote:
On Sep 4, 2014, at 4:12 PM, Dan McDonald wrote:
On Sep 4, 2014, at 4:04 PM, Jorge Schrauwen
wrote:
lotheac said on IRC virtio is just pulls in
On Sep 4, 2014, at 4:12 PM, Dan McDonald wrote:
>
> On Sep 4, 2014, at 4:04 PM, Jorge Schrauwen wrote:
>
>> lotheac said on IRC virtio is just pulls in vioblk as there is no virtio-net
>> driver.
>> But the vioblk is the important one for installs.
>>
>> But getting it in entire would be ni
On Sep 4, 2014, at 4:04 PM, Jorge Schrauwen wrote:
> lotheac said on IRC virtio is just pulls in vioblk as there is no virtio-net
> driver.
> But the vioblk is the important one for installs.
>
> But getting it in entire would be nice, that would mean kayak images will
> have it too :)
osde
lotheac said on IRC virtio is just pulls in vioblk as there is no
virtio-net driver.
But the vioblk is the important one for installs.
But getting it in entire would be nice, that would mean kayak images
will have it too :)
On 2014-09-04 22:00, Theo Schlossnagle wrote:
We should just stick
We should just stick those in entire... so... +1.
On Thu, Sep 4, 2014 at 3:16 PM, Jorge Schrauwen
wrote:
> Hey Dan,
>
> As mentioned on IRC, maybe we should bundle vioblk in the ISO/USB/Kayak
> images.
> It's in the following package:
> pkg:/driver/storage/vioblk
> And we might also include the
Hey Dan,
As mentioned on IRC, maybe we should bundle vioblk in the ISO/USB/Kayak
images.
It's in the following package:
pkg:/driver/storage/vioblk
And we might also include the network drivers
pkg:/driver/misc/virtio
Thanks
Jorge
On 2014-09-02 20:22, Dan McDonald wrote:
Hello folks!
I'm n
On Aug 25, 2014, at 8:38 PM, Keith Paskett wrote:
> Just a note, that I have had the same issue with r151010 hanging after the
> copyright notice.
> I have the issue when booting from CD on several different SunFIre servers.
> They are X4150s and X4250s.
> I have not yet tried on other systems
On Sep 4, 2014, at 3:04 AM, Dan Vatca wrote:
> The thing that I find odd is that dependencies are gathered from the build
> system and not from the set of packages OmniOS is currently building.
> If we could find a way to do that, couldn't we have a way to build any
> version of OmniOS on any
The thing that I find odd is that dependencies are gathered from the build
system and not from the set of packages OmniOS is currently building.
If we could find a way to do that, couldn't we have a way to build any
version of OmniOS on any other version?
___
