From grzemba at contac-dt.de  Mon Jun  3 14:44:26 2019
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Mon, 03 Jun 2019 16:44:26 +0200
Subject: [oi-dev] Openindiana on Laptop: touchpad not working
In-Reply-To: <bd3e8f4829c5.5ce65b00@contac-dt.de>
References: <be86e6074ec1.5ce41f99@contac-dt.de>
	<alpine.GSO.2.20.1905211010220.7749@scrappy.simplesystems.org>
	<bd3e8f4829c5.5ce65b00@contac-dt.de>
Message-ID: <bd3d30256aff.5cf54e6a@contac-dt.de>


<signaturebeforequotedtext></signaturebeforequotedtext>
On 23.05.19 08:34, Carsten Grzemba via oi-dev  <oi-dev at openindiana.org> wrote: 
> 
> I compared the Xorg log:
> 
> in the working log the mouse driver is loaded on PS/s mouse on /dev/mouse:
> 
> [ 38.008] (II) LoadModule: "mouse"
> [ 38.008] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> [ 38.012] (II) Module mouse: vendor="X.Org Foundation"
> [ 38.012] compiled for 1.19.5, module version = 1.9.2
> [ 38.012] Module class: X.Org XInput Driver
> [ 38.012] ABI class: X.Org XInput driver, version 24.1
> [ 38.012] (II) Using input driver 'mouse' for 'PS/2 Port for PS/2-style Mice'
> [ 38.012] (**) PS/2 Port for PS/2-style Mice: always reports core events
> [ 38.012] (**) Option "Device" "/dev/mouse"
> [ 38.012] (II) PS/2 Port for PS/2-style Mice: Setting Device option to "/dev/mouse"
> [ 38.014] (==) PS/2 Port for PS/2-style Mice: Protocol: "VUID"
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: always reports core events
> [ 38.014] (**) Option "Device" "/dev/mouse"
> [ 38.014] (==) PS/2 Port for PS/2-style Mice: Emulate3Buttons, Emulate3Timeout: 50
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: ZAxisMapping: buttons 4 and 5
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: Buttons: 9
> [ 38.014] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/isa_1f/i8042_1_60/mouse_1_0_logicaldev_input"
> [ 38.014] (II) XINPUT: Adding extended input device "PS/2 Port for PS/2-style Mice" (type: MOUSE, id 6)
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) keeping acceleration scheme 1
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration profile 0
> [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration factor: 2.000
> [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration threshold: 4
> 
> and the not working on the generic USB device /dev/usb/hid1:
> 
> [ 523.036] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> [ 523.036] (II) Module mouse: vendor="X.Org Foundation"
> [ 523.036] compiled for 1.19.5, module version = 1.9.2
> [ 523.036] Module class: X.Org XInput Driver
> [ 523.037] ABI class: X.Org XInput driver, version 24.1
> [ 523.037] (II) Using input driver 'mouse' for 'mouse'
> [ 523.037] (**) mouse: always reports core events
> [ 523.037] (**) Option "Protocol" "VUID"
> [ 523.037] (**) Option "Device" "/dev/usb/hid1"
> [ 523.037] (**) Option "StreamsModule" "usbms"
> [ 523.039] (**) mouse: Protocol: "VUID"
> [ 523.039] (**) mouse: always reports core events
> [ 523.039] (==) mouse: Emulate3Buttons, Emulate3Timeout: 50
> [ 523.039] (**) mouse: ZAxisMapping: buttons 4 and 5
> [ 523.039] (**) mouse: Buttons: 9
> [ 523.039] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1025_1019_14/device_4/mouse_1_if1_4_logicaldev_input"
> [ 523.039] (II) XINPUT: Adding extended input device "mouse" (type: MOUSE, id 6)
> [ 523.039] (**) mouse: (accel) keeping acceleration scheme 1
> [ 523.039] (**) mouse: (accel) acceleration profile 0
> [ 523.039] (**) mouse: (accel) acceleration factor: 2.000
> [ 523.039] (**) mouse: (accel) acceleration threshold: 4
> [ 523.045] (II) config/hal: Adding input device hotkey
> 
> 
> in both cases is the the touchpad avail and a extern USB mouse connected. the /dev/mouse dev link is in both BE targeted to /devices/pseudo/cons at 0:mouse
> 
> 
Still no luck with the latest hipster on my laptop:

scanpci:
pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1604
?Intel Corporation Broadwell-U Host Bridge -OPI

pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1616
?Intel Corporation HD Graphics 5500

pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x160c
?Intel Corporation Broadwell-U Audio Controller

pci bus 0x0000 cardnum 0x14 function 0x00: vendor 0x8086 device 0x9cb1
?Intel Corporation Wildcat Point-LP USB xHCI Controller

pci bus 0x0000 cardnum 0x16 function 0x00: vendor 0x8086 device 0x9cba
?Intel Corporation Wildcat Point-LP MEI Controller #1

pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x9ca0
?Intel Corporation Wildcat Point-LP High Definition Audio Controller

pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x9c90
?Intel Corporation Wildcat Point-LP PCI Express Root Port #1

pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device 0x9c94
?Intel Corporation Wildcat Point-LP PCI Express Root Port #3

pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
?Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device 0x9c96
?Intel Corporation Wildcat Point-LP PCI Express Root Port #4

pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x8086 device 0x095a
?Intel Corporation Wireless 7265

pci bus 0x0000 cardnum 0x1c function 0x04: vendor 0x8086 device 0x9c98
?Intel Corporation Wildcat Point-LP PCI Express Root Port #5

pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10de device 0x1299
?NVIDIA Corporation GK208BM [GeForce 920M]

pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x9ca6
?Intel Corporation Wildcat Point-LP USB EHCI Controller

pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x9cc3
?Intel Corporation Wildcat Point-LP LPC ControllerX.Org X Server 1.19.6

pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x9c83
?Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode]

pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x9ca2
?Intel Corporation Wildcat Point-LP SMBus Controller

I boot from latest USB image there X session dont start, only the mouse pointer is seen. If I kill the Xorg via SSH I get no text console.
So I reboot in text console and tried to test Xorg configuration with my current working settings (of Xorg 1.19.6 vesa for the Intel, Nvidia was never usable with the old i915 driver). There I get only a black screen and after kill Xorg no text console again. 
Activating vtdaemon and vt-console also not working.

What is the change here, so that Xorg 1.19.7 isn't working anymore? In Xorg.0.log I dont see any errors.

Thanks



























 <signatureafterquotedtext></signatureafterquotedtext>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190603/0736b268/attachment.html>

From grzemba at contac-dt.de  Tue Jun  4 08:27:09 2019
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Tue, 04 Jun 2019 10:27:09 +0200
Subject: [oi-dev] Openindiana on Laptop: touchpad not working
In-Reply-To: <bd3d30256aff.5cf54e6a@contac-dt.de>
References: <be86e6074ec1.5ce41f99@contac-dt.de>
	<alpine.GSO.2.20.1905211010220.7749@scrappy.simplesystems.org>
	<bd3e8f4829c5.5ce65b00@contac-dt.de>
	<bd3d30256aff.5cf54e6a@contac-dt.de>
Message-ID: <bf5f8a435076.5cf6477d@contac-dt.de>


<signaturebeforequotedtext></signaturebeforequotedtext>
On 03.06.19 16:44, "Carsten Grzemba"  <grzemba at contac-dt.de> wrote: 
> 
> 
> 
> On 23.05.19 08:34, Carsten Grzemba via oi-dev  <oi-dev at openindiana.org> wrote: 
> > 
> > I compared the Xorg log:
> > 
> > in the working log the mouse driver is loaded on PS/s mouse on /dev/mouse:
> > 
> > [ 38.008] (II) LoadModule: "mouse"
> > [ 38.008] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> > [ 38.012] (II) Module mouse: vendor="X.Org Foundation"
> > [ 38.012] compiled for 1.19.5, module version = 1.9.2
> > [ 38.012] Module class: X.Org XInput Driver
> > [ 38.012] ABI class: X.Org XInput driver, version 24.1
> > [ 38.012] (II) Using input driver 'mouse' for 'PS/2 Port for PS/2-style Mice'
> > [ 38.012] (**) PS/2 Port for PS/2-style Mice: always reports core events
> > [ 38.012] (**) Option "Device" "/dev/mouse"
> > [ 38.012] (II) PS/2 Port for PS/2-style Mice: Setting Device option to "/dev/mouse"
> > [ 38.014] (==) PS/2 Port for PS/2-style Mice: Protocol: "VUID"
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: always reports core events
> > [ 38.014] (**) Option "Device" "/dev/mouse"
> > [ 38.014] (==) PS/2 Port for PS/2-style Mice: Emulate3Buttons, Emulate3Timeout: 50
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: ZAxisMapping: buttons 4 and 5
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: Buttons: 9
> > [ 38.014] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/isa_1f/i8042_1_60/mouse_1_0_logicaldev_input"
> > [ 38.014] (II) XINPUT: Adding extended input device "PS/2 Port for PS/2-style Mice" (type: MOUSE, id 6)
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) keeping acceleration scheme 1
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration profile 0
> > [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration factor: 2.000
> > [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration threshold: 4
> > 
> > and the not working on the generic USB device /dev/usb/hid1:
> > 
> > [ 523.036] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> > [ 523.036] (II) Module mouse: vendor="X.Org Foundation"
> > [ 523.036] compiled for 1.19.5, module version = 1.9.2
> > [ 523.036] Module class: X.Org XInput Driver
> > [ 523.037] ABI class: X.Org XInput driver, version 24.1
> > [ 523.037] (II) Using input driver 'mouse' for 'mouse'
> > [ 523.037] (**) mouse: always reports core events
> > [ 523.037] (**) Option "Protocol" "VUID"
> > [ 523.037] (**) Option "Device" "/dev/usb/hid1"
> > [ 523.037] (**) Option "StreamsModule" "usbms"
> > [ 523.039] (**) mouse: Protocol: "VUID"
> > [ 523.039] (**) mouse: always reports core events
> > [ 523.039] (==) mouse: Emulate3Buttons, Emulate3Timeout: 50
> > [ 523.039] (**) mouse: ZAxisMapping: buttons 4 and 5
> > [ 523.039] (**) mouse: Buttons: 9
> > [ 523.039] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1025_1019_14/device_4/mouse_1_if1_4_logicaldev_input"
> > [ 523.039] (II) XINPUT: Adding extended input device "mouse" (type: MOUSE, id 6)
> > [ 523.039] (**) mouse: (accel) keeping acceleration scheme 1
> > [ 523.039] (**) mouse: (accel) acceleration profile 0
> > [ 523.039] (**) mouse: (accel) acceleration factor: 2.000
> > [ 523.039] (**) mouse: (accel) acceleration threshold: 4
> > [ 523.045] (II) config/hal: Adding input device hotkey
> > 
> > 
> > in both cases is the the touchpad avail and a extern USB mouse connected. the /dev/mouse dev link is in both BE targeted to /devices/pseudo/cons at 0:mouse
> > 
> > 
> Still no luck with the latest hipster on my laptop:
> 
> scanpci:
> pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1604
> ?Intel Corporation Broadwell-U Host Bridge -OPI
> 
> pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1616
> ?Intel Corporation HD Graphics 5500
> 
> pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x160c
> ?Intel Corporation Broadwell-U Audio Controller
> 
> pci bus 0x0000 cardnum 0x14 function 0x00: vendor 0x8086 device 0x9cb1
> ?Intel Corporation Wildcat Point-LP USB xHCI Controller
> 
> pci bus 0x0000 cardnum 0x16 function 0x00: vendor 0x8086 device 0x9cba
> ?Intel Corporation Wildcat Point-LP MEI Controller #1
> 
> pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x9ca0
> ?Intel Corporation Wildcat Point-LP High Definition Audio Controller
> 
> pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x9c90
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #1
> 
> pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device 0x9c94
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #3
> 
> pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
> ?Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
> 
> pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device 0x9c96
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #4
> 
> pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x8086 device 0x095a
> ?Intel Corporation Wireless 7265
> 
> pci bus 0x0000 cardnum 0x1c function 0x04: vendor 0x8086 device 0x9c98
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #5
> 
> pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10de device 0x1299
> ?NVIDIA Corporation GK208BM [GeForce 920M]
> 
> pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x9ca6
> ?Intel Corporation Wildcat Point-LP USB EHCI Controller
> 
> pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x9cc3
> ?Intel Corporation Wildcat Point-LP LPC ControllerX.Org X Server 1.19.6
> 
> pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x9c83
> ?Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode]
> 
> pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x9ca2
> ?Intel Corporation Wildcat Point-LP SMBus Controller
> 
> I boot from latest USB image there X session dont start, only the mouse pointer is seen. If I kill the Xorg via SSH I get no text console.
> So I reboot in text console and tried to test Xorg configuration with my current working settings (of Xorg 1.19.6 vesa for the Intel, Nvidia was never usable with the old i915 driver). There I get only a black screen and after kill Xorg no text console again. 
> Activating vtdaemon and vt-console also not working.
> 
> What is the change here, so that Xorg 1.19.7 isn't working anymore? In Xorg.0.log I dont see any errors.
> 
> Thanks 
> 
Because the Xorg config is not changed and the touchpad not working on newer hipster, it looks for me like the touchpad is disabled what can normaly toggled by Fn F7.
But Fn keys do not work at all on newer hipster. Something to do with ACPI ?

 <signatureafterquotedtext></signatureafterquotedtext>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190604/1b76e6e2/attachment-0001.html>

From randyf at sibernet.com  Tue Jun 11 18:07:21 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 11:07:21 -0700 (PDT)
Subject: [oi-dev] suspend/resume in Illumos
Message-ID: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>



I have a question for developers here:

    How important is suspend/resume for OI/Illumos (including S4)?


One of the incomplete projects left behind was S4 (lack of need, and a 
hard to identify bug stifled it's integration).  It is non-trivial, and 
needs updated s/r core code (added configuration and significant 
restructuring, as well as likely assistance from developers knowlegable in 
other Illumos internals), but if this is an uninteresting feature, it is 
likey not worth the effort (recent bugs suggest that few if anyone use 
it); however, it wouldn't be too hard to resurect (though would still take 
several months of work).


   Cheers!

 	---- Randy


From gary_mills at fastmail.fm  Tue Jun 11 18:10:11 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 11 Jun 2019 13:10:11 -0500
Subject: [oi-dev] Toward a SPARC distro of OI
Message-ID: <20190611181011.GA18869@mail.messagingengine.com>

I'm part way through this long project now.  I began with v9os
installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
packages.  I've been building IPS packages from oi-userland source.
This process has gotten easier now that all the build tools I need are
in IPS packages.  I've been replacing v9os packages with oi-userland
packages.  My goal is to replace all of them, and finally to produce a
text ISO and package repository for SPARC that's entirely based on
oi-userland.

So far, I've built and packaged versions 5, 6, and 7 of the gcc
compiler.  The commands for IPS packages are all packaged for python
2.7.  My system now has 106 packages installed from oi-userland,
versus 343 packages from v9os.  Most of the oi-userland products
required very few or no changes to build and package for SPARC.

For perl, I've removed the 5.16.1 version from v9os and installed
versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
packaged for 5.22.  Python libraries are all packaged for 2.7.

I'm submitting this message to the mailing list mostly as a progress
report.  I would, of course, appreciate a bit of help with this
project.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-


From garrett at damore.org  Tue Jun 11 19:58:08 2019
From: garrett at damore.org (Garrett D'Amore)
Date: Tue, 11 Jun 2019 12:58:08 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
Message-ID: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>

My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where suspend/resume has little if any applicability.

While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from other more pressing work, without any clear use cases for it.

That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any other reason we would reject a suitably formed RTI.

Sent from Mail for Windows 10

From: randyf at sibernet.com
Sent: Tuesday, June 11, 2019 11:10 AM
To: oi-dev at openindiana.org; developer at lists.illumos.org
Subject: [developer] suspend/resume in Illumos



I have a question for developers here:

    How important is suspend/resume for OI/Illumos (including S4)?


One of the incomplete projects left behind was S4 (lack of need, and a 
hard to identify bug stifled it's integration).  It is non-trivial, and 
needs updated s/r core code (added configuration and significant 
restructuring, as well as likely assistance from developers knowlegable in 
other Illumos internals), but if this is an uninteresting feature, it is 
likey not worth the effort (recent bugs suggest that few if anyone use 
it); however, it wouldn't be too hard to resurect (though would still take 
several months of work).


   Cheers!

        ---- Randy

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190611/347dae6d/attachment.html>

From tsoome at me.com  Tue Jun 11 20:31:18 2019
From: tsoome at me.com (Toomas Soome)
Date: Tue, 11 Jun 2019 23:31:18 +0300
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
Message-ID: <DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>

I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be bonus.

Sent from my iPhone

> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
> 
> My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where suspend/resume has little if any applicability.
>  
> While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from other more pressing work, without any clear use cases for it.
>  
> That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any other reason we would reject a suitably formed RTI.
>  
> Sent from Mail for Windows 10
>  
> From: randyf at sibernet.com
> Sent: Tuesday, June 11, 2019 11:10 AM
> To: oi-dev at openindiana.org; developer at lists.illumos.org
> Subject: [developer] suspend/resume in Illumos
>  
>  
>  
> I have a question for developers here:
>  
>     How important is suspend/resume for OI/Illumos (including S4)?
>  
>  
> One of the incomplete projects left behind was S4 (lack of need, and a
> hard to identify bug stifled it's integration).  It is non-trivial, and
> needs updated s/r core code (added configuration and significant
> restructuring, as well as likely assistance from developers knowlegable in
> other Illumos internals), but if this is an uninteresting feature, it is
> likey not worth the effort (recent bugs suggest that few if anyone use
> it); however, it wouldn't be too hard to resurect (though would still take
> several months of work).
>  
>  
>    Cheers!
>  
>         ---- Randy
>  
> ------------------------------------------
> illumos: illumos-developer
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
>  
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190611/1b0c9592/attachment.html>

From randyf at sibernet.com  Tue Jun 11 21:28:34 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 14:28:34 -0700 (PDT)
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
Message-ID: <alpine.SOC.2.00.1906111420090.15467@sibernet.com>



On Tue, 11 Jun 2019, Garrett D'Amore wrote:

> 
> My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where
> suspend/resume has little if any applicability.
> 
> ?
> 
> While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from
> other more pressing work, without any clear use cases for it.
>

   I should point out that s/r isn't just for laptop bare-metal.  It allows 
for a running instance of an OS to be frozen in an orderly manner (rather 
than a VM just pausing a guest, the guest suspends first).  S4 opens a 
different world of allowing said image to be more easily migrated, or 
(since it has roots in CPR) opens quick-boot images (imagine getting an 
OS fully booted in under 10 seconds).

> ?
> 
> That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m
> fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any
> other reason we would reject a suitably formed RTI.
>

   Doubt I'll fully drop it, but without sufficient interest, it's is 
unlikely I'll give it much priority (certainly, my other 'dropped' project 
should have a higer priority).

   Cheers!

 	---- Randy

> ?
> 
> Sent from Mail for Windows 10
> 
> ?
> 
> From: randyf at sibernet.com
> Sent: Tuesday, June 11, 2019 11:10 AM
> To: oi-dev at openindiana.org; developer at lists.illumos.org
> Subject: [developer] suspend/resume in Illumos
> 
> ?
> 
> ?
> 
> ?
> 
> I have a question for developers here:
> 
> ?
> 
> ??? How important is suspend/resume for OI/Illumos (including S4)?
> 
> ?
> 
> ?
> 
> One of the incomplete projects left behind was S4 (lack of need, and a
> 
> hard to identify bug stifled it's integration).? It is non-trivial, and
> 
> needs updated s/r core code (added configuration and significant
> 
> restructuring, as well as likely assistance from developers knowlegable in
> 
> other Illumos internals), but if this is an uninteresting feature, it is
> 
> likey not worth the effort (recent bugs suggest that few if anyone use
> 
> it); however, it wouldn't be too hard to resurect (though would still take
> 
> several months of work).
> 
> ?
> 
> ?
> 
> ?? Cheers!
> 
> ?
> 
> ??????? ---- Randy
> 
> ?
> 
> ------------------------------------------
> 
> illumos: illumos-developer
> 
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> 
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
> 
> ?
> 
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
> 
>

From randyf at sibernet.com  Tue Jun 11 21:29:23 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 14:29:23 -0700 (PDT)
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
Message-ID: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>



On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:

> I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be
> bonus.

   Betting better graphics support would be higher on the list (yea, the 
other 'dropped' project).

   Cheers!

 	---- Randy

> 
> Sent from my iPhone
> 
> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>
>       My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter
>       applications where suspend/resume has little if any applicability.
>
>       ?
>
>       While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be
>       detraction from other more pressing work, without any clear use cases for it.
>
>       ?
>
>       That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it,
>       and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for
>       example), I can?t see any other reason we would reject a suitably formed RTI.
>
>       ?
>
>       Sent from Mail for Windows 10
>
>       ?
>
>       From: randyf at sibernet.com
>       Sent: Tuesday, June 11, 2019 11:10 AM
>       To: oi-dev at openindiana.org; developer at lists.illumos.org
>       Subject: [developer] suspend/resume in Illumos
> 
> ?
> 
> ?
> 
> ?
> 
> I have a question for developers here:
> 
> ?
> 
> ??? How important is suspend/resume for OI/Illumos (including S4)?
> 
> ?
> 
> ?
> 
> One of the incomplete projects left behind was S4 (lack of need, and a
> 
> hard to identify bug stifled it's integration).? It is non-trivial, and
> 
> needs updated s/r core code (added configuration and significant
> 
> restructuring, as well as likely assistance from developers knowlegable in
> 
> other Illumos internals), but if this is an uninteresting feature, it is
> 
> likey not worth the effort (recent bugs suggest that few if anyone use
> 
> it); however, it wouldn't be too hard to resurect (though would still take
> 
> several months of work).
> 
> ?
> 
> ?
> 
> ?? Cheers!
> 
> ?
> 
> ??????? ---- Randy
> 
> ?
> 
> ------------------------------------------
> 
> illumos: illumos-developer
> 
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> 
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
> 
> ?
> 
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
> 
>

From josh at sysmgr.org  Tue Jun 11 21:32:28 2019
From: josh at sysmgr.org (Joshua M. Clulow)
Date: Tue, 11 Jun 2019 14:32:28 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <CAEwA5nJHmR+Md2hh2HGj5770+-x=uanePOwqTrYRBe4W0GxPoQ@mail.gmail.com>

On Tue, 11 Jun 2019 at 14:29, <randyf at sibernet.com> wrote:
> On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
> > I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be
> > bonus.
>
>    Betting better graphics support would be higher on the list (yea, the
> other 'dropped' project).

I think there are a fair few people who would appreciate some serious
elbow grease being applied to the graphics bits!


Cheers.

-- 
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org


From jimklimov at cos.ru  Wed Jun 12 08:01:25 2019
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 12 Jun 2019 08:01:25 +0000
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>

On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>
>
>On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>
>> I?d say, anything to encourage people to try, use and join to develop
>[illumos] is very welcome. Better laptop support will definitely be
>> bonus.
>
> Betting better graphics support would be higher on the list (yea, the 
>other 'dropped' project).
>
>   Cheers!
>
>        ---- Randy
>
>> 
>> Sent from my iPhone
>> 
>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> My gut instinct is that this isn?t that interesting ? most everyone
>is running illumos in either VMs, or in datacenter
>> applications where suspend/resume has little if any applicability.
>> 
>> While the work itself is probably interesting, and it may enable new
>applications for illumos, the concern I?d have would be
>> detraction from other more pressing work, without any clear use cases
>for it.
>> 
>> That said, if someone (you?) wanted to spend cycles on this for
>personal satisfaction, I hardly see any reason to discourage it,
>> and I?m fairly certain if the risks of the new code being introduced
>are small (or well managed by sufficient testing for
>> example), I can?t see any other reason we would reject a suitably
>formed RTI.
>> 
>> Sent from Mail for Windows 10
>> 
>> From: randyf at sibernet.com
>> Sent: Tuesday, June 11, 2019 11:10 AM
>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>> Subject: [developer] suspend/resume in Illumos
>> 
>> I have a question for developers here:
>> 
>> ??? How important is suspend/resume for OI/Illumos (including S4)?
>> 
>> One of the incomplete projects left behind was S4 (lack of need, and
>a
>> 
>> hard to identify bug stifled it's integration).? It is non-trivial,
>and
>> 
>> needs updated s/r core code (added configuration and significant
>> 
>> restructuring, as well as likely assistance from developers
>knowlegable in
>> 
>> other Illumos internals), but if this is an uninteresting feature, it
>is
>> 
>> likey not worth the effort (recent bugs suggest that few if anyone
>use
>> 
>> it); however, it wouldn't be too hard to resurect (though would still
>take
>> 
>> several months of work).
>> 
>> ?? Cheers!
>> 
>> ??????? ---- Randy
>> 
>> illumos / illumos-developer / see discussions + participants +
>delivery options Permalink
>> 
>------------------------------------------
>illumos: illumos-developer
>Permalink:
>https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>Delivery options:
>https://illumos.topicbox.com/groups/developer/subscription

For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.

My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.

Jim

--
Typos courtesy of K-9 Mail on my Android


From jimklimov at cos.ru  Wed Jun 12 08:01:25 2019
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 12 Jun 2019 08:01:25 +0000
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>

On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>
>
>On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>
>> I?d say, anything to encourage people to try, use and join to develop
>[illumos] is very welcome. Better laptop support will definitely be
>> bonus.
>
> Betting better graphics support would be higher on the list (yea, the 
>other 'dropped' project).
>
>   Cheers!
>
>        ---- Randy
>
>> 
>> Sent from my iPhone
>> 
>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> My gut instinct is that this isn?t that interesting ? most everyone
>is running illumos in either VMs, or in datacenter
>> applications where suspend/resume has little if any applicability.
>> 
>> While the work itself is probably interesting, and it may enable new
>applications for illumos, the concern I?d have would be
>> detraction from other more pressing work, without any clear use cases
>for it.
>> 
>> That said, if someone (you?) wanted to spend cycles on this for
>personal satisfaction, I hardly see any reason to discourage it,
>> and I?m fairly certain if the risks of the new code being introduced
>are small (or well managed by sufficient testing for
>> example), I can?t see any other reason we would reject a suitably
>formed RTI.
>> 
>> Sent from Mail for Windows 10
>> 
>> From: randyf at sibernet.com
>> Sent: Tuesday, June 11, 2019 11:10 AM
>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>> Subject: [developer] suspend/resume in Illumos
>> 
>> I have a question for developers here:
>> 
>> ??? How important is suspend/resume for OI/Illumos (including S4)?
>> 
>> One of the incomplete projects left behind was S4 (lack of need, and
>a
>> 
>> hard to identify bug stifled it's integration).? It is non-trivial,
>and
>> 
>> needs updated s/r core code (added configuration and significant
>> 
>> restructuring, as well as likely assistance from developers
>knowlegable in
>> 
>> other Illumos internals), but if this is an uninteresting feature, it
>is
>> 
>> likey not worth the effort (recent bugs suggest that few if anyone
>use
>> 
>> it); however, it wouldn't be too hard to resurect (though would still
>take
>> 
>> several months of work).
>> 
>> ?? Cheers!
>> 
>> ??????? ---- Randy
>> 
>> illumos / illumos-developer / see discussions + participants +
>delivery options Permalink
>> 
>------------------------------------------
>illumos: illumos-developer
>Permalink:
>https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>Delivery options:
>https://illumos.topicbox.com/groups/developer/subscription

For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.

My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.

Jim

--
Typos courtesy of K-9 Mail on my Android


From aurelien.larcher at gmail.com  Mon Jun 17 11:26:59 2019
From: aurelien.larcher at gmail.com (=?UTF-8?Q?Aur=C3=A9lien_Larcher?=)
Date: Mon, 17 Jun 2019 13:26:59 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <20190611181011.GA18869@mail.messagingengine.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
Message-ID: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>

On Mon, Jun 17, 2019 at 11:59 AM Gary Mills <gary_mills at fastmail.fm> wrote:

> I'm part way through this long project now.  I began with v9os
> installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
> packages.  I've been building IPS packages from oi-userland source.
> This process has gotten easier now that all the build tools I need are
> in IPS packages.  I've been replacing v9os packages with oi-userland
> packages.  My goal is to replace all of them, and finally to produce a
> text ISO and package repository for SPARC that's entirely based on
> oi-userland.
>
> So far, I've built and packaged versions 5, 6, and 7 of the gcc
> compiler.  The commands for IPS packages are all packaged for python
> 2.7.  My system now has 106 packages installed from oi-userland,
> versus 343 packages from v9os.  Most of the oi-userland products
> required very few or no changes to build and package for SPARC.
>
> For perl, I've removed the 5.16.1 version from v9os and installed
> versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
> removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
> packaged for 5.22.  Python libraries are all packaged for 2.7.
>
> I'm submitting this message to the mailing list mostly as a progress
> report.  I would, of course, appreciate a bit of help with this
> project.
>

Congratulations Gary this is great :)
If we get to the point that we can setup a build machine this would secure
your work.
Kind regards

Aur?lien



>
>
> --
> -Gary Mills-            -refurb-                -Winnipeg, Manitoba,
> Canada-
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


-- 
---
Praise the Caffeine embeddings
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190617/a222a8e2/attachment.html>

From toasterson at gmail.com  Mon Jun 17 15:33:53 2019
From: toasterson at gmail.com (=?UTF-8?Q?Till_Wegm=c3=bcller?=)
Date: Mon, 17 Jun 2019 17:33:53 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
Message-ID: <63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com>

Hi Gary

Thank you so much for this Work. I don't personaly use sparc but ir is
good to see people doing this kinds of projects.

Do you know about Agnar's Project to get OI building on SPARC? I can't
remember if I ever pointed you towards him and his OI on Sparc work. His
angle was to jump from an existing OI distro to current packages and
later looking in V9OS.

Greetings
Till

On 17.06.19 13:26, Aur?lien Larcher wrote:
> 
> 
> On Mon, Jun 17, 2019 at 11:59 AM Gary Mills <gary_mills at fastmail.fm
> <mailto:gary_mills at fastmail.fm>> wrote:
> 
>     I'm part way through this long project now.? I began with v9os
>     installed on a Sun T2000.? v9os is a SPARC distribution that uses IPS
>     packages.? I've been building IPS packages from oi-userland source.
>     This process has gotten easier now that all the build tools I need are
>     in IPS packages.? I've been replacing v9os packages with oi-userland
>     packages.? My goal is to replace all of them, and finally to produce a
>     text ISO and package repository for SPARC that's entirely based on
>     oi-userland.
> 
>     So far, I've built and packaged versions 5, 6, and 7 of the gcc
>     compiler.? The commands for IPS packages are all packaged for python
>     2.7.? My system now has 106 packages installed from oi-userland,
>     versus 343 packages from v9os.? Most of the oi-userland products
>     required very few or no changes to build and package for SPARC.
> 
>     For perl, I've removed the 5.16.1 version from v9os and installed
>     versions 5.22 and 5.24 from oi-userland.? Likewise, for python, I've
>     removed 2.6 and installed 2.7 and 3.4.? Perl libraries are all
>     packaged for 5.22.? Python libraries are all packaged for 2.7.
> 
>     I'm submitting this message to the mailing list mostly as a progress
>     report.? I would, of course, appreciate a bit of help with this
>     project.
> 
> 
> Congratulations Gary this is great :)
> If we get to the point that we can setup a build machine this would
> secure your work.
> Kind regards
> 
> Aur?lien
> 
> ?
> 
> 
> 
>     -- 
>     -Gary Mills-? ? ? ? ? ? -refurb-? ? ? ? ? ? ? ? -Winnipeg, Manitoba,
>     Canada-
> 
>     _______________________________________________
>     oi-dev mailing list
>     oi-dev at openindiana.org <mailto:oi-dev at openindiana.org>
>     https://openindiana.org/mailman/listinfo/oi-dev
> 
> 
> 
> -- 
> ---
> Praise the Caffeine embeddings
> 
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
> 


From olbohlen at eenfach.de  Tue Jun 18 19:25:07 2019
From: olbohlen at eenfach.de (Olaf Bohlen)
Date: Tue, 18 Jun 2019 21:25:07 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com> ("Till
	=?utf-8?Q?Wegm=C3=BCller=22's?= message of "Mon, 17 Jun 2019 17:33:53
	+0200")
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
	<63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com>
Message-ID: <x6pnnavgq4.fsf@eenfach.de>

Till Wegm?ller <toasterson at gmail.com> writes:

Hi Till,
hi Gary,

> Do you know about Agnar's Project to get OI building on SPARC? I can't
> remember if I ever pointed you towards him and his OI on Sparc work. His
> angle was to jump from an existing OI distro to current packages and
> later looking in V9OS.

First: Gary, this is phantastic news, congrats to it! I'm looking
forward to hear more from you.

Second: Till, yes Gary and I have been in contact but since I have
not enough time, my progress is probably somewhat slower. I also
have newer bits running, but my approach is - as you mentioned -
doing bootstrapping a system to be able to build recent bits in
the correct way.

I'd be happy to hear once someone has built a bootable OI media
for sparc and would take up of these also.

Best regards,

-- 
      ~       Olaf Bohlen - olbohlen at eenfach.de
      |~~     Het
     /|  \    Bruine
 ___/_|___\   Leven
   \__n____/# DGCN2


From Tim.Mooney at ndsu.edu  Mon Jun 24 02:24:33 2019
From: Tim.Mooney at ndsu.edu (Tim Mooney)
Date: Sun, 23 Jun 2019 21:24:33 -0500 (CDT)
Subject: [oi-dev] component TODO list for perl components?
Message-ID: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,

 	https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164


From alp at sfedu.ru  Mon Jun 24 06:05:50 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 06:05:50 +0000
Subject: [oi-dev] component TODO list for perl components?
In-Reply-To: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
References: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
Message-ID: <AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.

I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/ some time ago. There are mostly tasks which I'm interested in.

Now I'm looking at removing binary blobs from DDU. Later I'll likely look at switching it to Python 3.5.

If you can propose any tasks which you can take (or pehaps, someone else), feel  free to update this page. I just don't want it to become a list of never-done tasks.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Tim Mooney <Tim.Mooney at ndsu.edu>
??????????: 24 ???? 2019 ?. 5:24:33
????: oi-dev at openindiana.org
????: [oi-dev] component TODO list for perl components?


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,

        https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
--
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev


From garrett at damore.org  Mon Jun 24 14:42:34 2019
From: garrett at damore.org (Garrett D'Amore)
Date: Mon, 24 Jun 2019 07:42:34 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <DE25905A-0071-4339-B00A-9EB1D62CC5AB@gmail.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
	<699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>
	<DE25905A-0071-4339-B00A-9EB1D62CC5AB@gmail.com>
Message-ID: <5d10e157.1c69fb81.48b1c.91f9@mx.google.com>

That?s only true if you?re running on  a hypervisor that uses suspend / resume for live migration.  I?m not sure how widespread running illumos on VMware is ? the absence of suspend/resume support means that nobody is benefiting from this particular capability today (at least with illumos).

Sent from Mail for Windows 10

From: DavidHalko
Sent: Monday, June 24, 2019 5:18 AM
To: illumos-developer
Cc: randyf at sibernet.com; oi-dev at openindiana.org
Subject: Re: [developer] suspend/resume in Illumos

Suspend and Resume is critical for live migration in a data center with external storage to reduce schedules downtime incurred with firmware updates to maintain a secure platform.

Thanks, David Halko
http://netmgt.blogspot.com/

Sent from my iPhone

> On Jun 12, 2019, at 4:01 AM, Jim Klimov <jimklimov at cos.ru> wrote:
> 
>> On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>> 
>> 
>>> On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>>> 
>>> I?d say, anything to encourage people to try, use and join to develop
>> [illumos] is very welcome. Better laptop support will definitely be
>>> bonus.
>> 
>> Betting better graphics support would be higher on the list (yea, the 
>> other 'dropped' project).
>> 
>>  Cheers!
>> 
>>       ---- Randy
>> 
>>> 
>>> Sent from my iPhone
>>> 
>>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>>> 
>>> My gut instinct is that this isn?t that interesting ? most everyone
>> is running illumos in either VMs, or in datacenter
>>> applications where suspend/resume has little if any applicability.
>>> 
>>> While the work itself is probably interesting, and it may enable new
>> applications for illumos, the concern I?d have would be
>>> detraction from other more pressing work, without any clear use cases
>> for it.
>>> 
>>> That said, if someone (you?) wanted to spend cycles on this for
>> personal satisfaction, I hardly see any reason to discourage it,
>>> and I?m fairly certain if the risks of the new code being introduced
>> are small (or well managed by sufficient testing for
>>> example), I can?t see any other reason we would reject a suitably
>> formed RTI.
>>> 
>>> Sent from Mail for Windows 10
>>> 
>>> From: randyf at sibernet.com
>>> Sent: Tuesday, June 11, 2019 11:10 AM
>>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>>> Subject: [developer] suspend/resume in Illumos
>>> 
>>> I have a question for developers here:
>>> 
>>>     How important is suspend/resume for OI/Illumos (including S4)?
>>> 
>>> One of the incomplete projects left behind was S4 (lack of need, and
>> a
>>> 
>>> hard to identify bug stifled it's integration).  It is non-trivial,
>> and
>>> 
>>> needs updated s/r core code (added configuration and significant
>>> 
>>> restructuring, as well as likely assistance from developers
>> knowlegable in
>>> 
>>> other Illumos internals), but if this is an uninteresting feature, it
>> is
>>> 
>>> likey not worth the effort (recent bugs suggest that few if anyone
>> use
>>> 
>>> it); however, it wouldn't be too hard to resurect (though would still
>> take
>>> 
>>> several months of work).
>>> 
>>>    Cheers!
>>> 
>>>         ---- Randy
>>> 
>>> illumos / illumos-developer / see discussions + participants +
>> delivery options Permalink
>> ------------------------------------------
>> illumos: illumos-developer
>> Permalink:
>> https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>> Delivery options:
>> https://illumos.topicbox.com/groups/developer/subscription
> 
> For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.
> 
> My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.
> 
> Jim
> 
> --
> Typos courtesy of K-9 Mail on my Android

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M87936b070d0aa9c1490f0794
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190624/7192fbe4/attachment.html>

From alp at sfedu.ru  Mon Jun 24 15:12:45 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 15:12:45 +0000
Subject: [oi-dev] DDU testing
Message-ID: <AM6PR05MB6198AE59E0359DD5E878CCAFCFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.

I've finished replacing DDU binaries with binaries from DDU 1.2 and rewriting missing parts. 
Result is here: https://github.com/OpenIndiana/ddu/ .
I suggest it can get wider testing.
You can use openindiana/ddu component  from https://github.com/OpenIndiana/oi-userland/pull/5103 to build and test it. 

I'm waiting for test results and reviews.

Changes from current DDU (shipped with OI now).
1) pt_BR localization files removed as msgunfmt couldn't unparse them;
2) Database of third-party drivers was removed (it was obsolete  with it seems one working link from dozen). I suppose nobody volunteers to support it in actual state.
3) I hope finally I've made DDU help behave - now it shows help in user locale, images are not removed.
4) I've regenerated database of existing OI drivers shipped with DDU, updated pci.ids and usb.ids files.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???



From gary_mills at fastmail.fm  Mon Jun 24 15:33:31 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Mon, 24 Jun 2019 10:33:31 -0500
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
Message-ID: <20190624153331.GA28009@mail.messagingengine.com>

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aur?lien Larcher wrote:
> 
>    Congratulations Gary this is great :)
>    If we get to the point that we can setup a build machine this would
>    secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-


From alp at sfedu.ru  Mon Jun 24 16:02:51 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 16:02:51 +0000
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <20190624153331.GA28009@mail.messagingengine.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>,
	<20190624153331.GA28009@mail.messagingengine.com>
Message-ID: <AM6PR05MB619883D7A53C05872643155DCFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

BTW, while working on DDU I've removed SPARC parts I've encountered ;)
Anyway I had no way (or desire) to test them.
Most interesting is likely dmi_info.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Gary Mills <gary_mills at fastmail.fm>
??????????: 24 ???? 2019 ?. 18:33
????: OpenIndiana Developer mailing list
????: Re: [oi-dev] Toward a SPARC distro of OI

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aur?lien Larcher wrote:
>
>    Congratulations Gary this is great :)
>    If we get to the point that we can setup a build machine this would
>    secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


--
-Gary Mills-            -refurb-                -Winnipeg, Manitoba, Canada-

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

From Tim.Mooney at ndsu.edu  Mon Jun 24 18:24:09 2019
From: Tim.Mooney at ndsu.edu (Tim Mooney)
Date: Mon, 24 Jun 2019 13:24:09 -0500 (CDT)
Subject: [oi-dev] component TODO list for perl components?
In-Reply-To: <AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>
References: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
	<AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>
Message-ID: <alpine.SOC.2.20.1906241317080.14673@dogbert.cc.ndsu.NoDak.edu>

In regard to: Re: [oi-dev] component TODO list for perl components?,...:

> I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/
> some time ago. There are mostly tasks which I'm interested in.
>
> Now I'm looking at removing binary blobs from DDU. Later I'll likely
> look at switching it to Python 3.5.
>
> If you can propose any tasks which you can take (or pehaps, someone
> else), feel  free to update this page. I just don't want it to become a
> list of never-done tasks.

Thanks Alexander, and I understand completely about a list of never-done
tasks.

I'll open a pull request with some proposed updates, and you and others
can comment on whether they're a good idea or not.

Tim

> ________________________________________
> ??: Tim Mooney <Tim.Mooney at ndsu.edu>
> ??????????: 24 ???? 2019 ?. 5:24:33
> ????: oi-dev at openindiana.org
> ????: [oi-dev] component TODO list for perl components?
>
>
> I've been considering packaging the latest stable perl5, 5.30.0, as
> perl-530 and then packaging (and in some cases, updating) the perl
> modules that are part of hipster, but I want to make certain I'm not
> working at cross-purposes to any planned updates for OI and that this
> type of update is actually useful.
>
> There's a checklist of small/easy changes to make when updating a
> component,
>
>        https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md
>
> but is there a list of the bigger packaging tasks, perhaps prioritized by
> need?  Obviously people volunteering their time are going to work on
> things that interest them, benefit them, and are within their ability,
> but at times it would be helpful to know what the most pressing packaging
> needs are.
>
> I'm happy to continue choosing components kind of at random to update, but
> if I have a list of easy (but perhaps tedious) packaging tasks that are
> priorities for update in OI, I would probably attempt some of them as I
> have time, especially if it frees up more time for core contributors to
> work on the more difficult tasks.
>
> Does a list like that exist?  Those types of things tend to go stale fast,
> so I understand if there isn't one.
>
> Tim
> --
> Tim Mooney                                             Tim.Mooney at ndsu.edu
> Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
> Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>

-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

From gary_mills at fastmail.fm  Tue Jun 25 20:47:20 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 25 Jun 2019 15:47:20 -0500
Subject: [oi-dev] Am I stuck?
Message-ID: <20190625204720.GA8601@mail.messagingengine.com>

These are my publishers:

    # pkg publisher                      
    PUBLISHER                   TYPE     STATUS P LOCATION
    oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
    v9os           (non-sticky) origin   online F file:///data/ips/

I just published all of illumos-gate to the oi-userland repository.
There are now two copies of the
consolidation/osnet/osnet-incorporation package.  This is the
installed one:

    # pkg info consolidation/osnet/osnet-incorporation
              Name: consolidation/osnet/osnet-incorporation
           Summary: OS/Net consolidation incorporation
       Description: This incorporation constrains packages from the OS/Net
                    consolidation.
             State: Installed
         Publisher: v9os
           Version: 0.5.11
            Branch: 0.151100
    Packaging Date: Wed Jul 27 07:12:37 2016
              Size: 0.00 B
              FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
    
This is the new one:

    # pkg info -r consolidation/osnet/osnet-incorporation
              Name: consolidation/osnet/osnet-incorporation
           Summary: OS/Net consolidation incorporation
       Description: This incorporation constrains packages from the OS/Net
                    consolidation.
             State: Not installed
         Publisher: oi-userland
           Version: 0.5.11
            Branch: 2018.0.0.0
    Packaging Date: Sun Jun 23 22:35:19 2019
              Size: 0.00 B
              FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z

I expected that `pkg update -nv' would offer to remove the installed
incorporation and replace all of the old illumos-gate packages, over
200 of them, with the new illumos-gate packages.  It didn't do that.
It did report that it would replace ten packages from the v9os
publisher with newer versions from the oi-userland publisher, but this
list didn't include any of the illumos-gate packages.

When I tried to remove the incorporation with pkg, I got this result:

    # pkg uninstall -nv consolidation/osnet/osnet-incorporation
    Creating Plan (Solver setup): -
    pkg uninstall: Unable to remove 'consolidation/osnet/osnet-incorporation at 0.5.11-0.151100' due to the following packages that depend on it:
      SUNWcs at 0.5.11-0.151100
      SUNWcsd at 0.5.11-0.151100
      compatibility/ucb at 0.5.11-0.151100
      developer/astdev at 0.5.11-0.151100
    ...
      system/zones at 0.5.11-0.151100
      system/zones/internal at 0.5.11-0.151100
      text/doctools at 0.5.11-0.151100
      text/locale at 0.5.11-0.151100

Have I run into a dead end, or is there a way out of this dilemma?


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-


From vab at bb-c.de  Tue Jun 25 21:01:31 2019
From: vab at bb-c.de (Volker A. Brandt)
Date: Tue, 25 Jun 2019 23:01:31 +0200
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190625204720.GA8601@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
Message-ID: <23826.35755.98828.321659@shelob.bb-c.de>

Hi Gary!


> These are my publishers:
> 
>     # pkg publisher                      
>     PUBLISHER                   TYPE     STATUS P LOCATION
>     oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
>     v9os           (non-sticky) origin   online F file:///data/ips/
> 
> I just published all of illumos-gate to the oi-userland repository.
> There are now two copies of the
> consolidation/osnet/osnet-incorporation package.  This is the
> installed one:
> 
>     # pkg info consolidation/osnet/osnet-incorporation
>               Name: consolidation/osnet/osnet-incorporation
>            Summary: OS/Net consolidation incorporation
>        Description: This incorporation constrains packages from the OS/Net
>                     consolidation.
>              State: Installed
>          Publisher: v9os
>            Version: 0.5.11
>             Branch: 0.151100
>     Packaging Date: Wed Jul 27 07:12:37 2016
>               Size: 0.00 B
>               FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
>     
> This is the new one:
> 
>     # pkg info -r consolidation/osnet/osnet-incorporation
>               Name: consolidation/osnet/osnet-incorporation
>            Summary: OS/Net consolidation incorporation
>        Description: This incorporation constrains packages from the OS/Net
>                     consolidation.
>              State: Not installed
>          Publisher: oi-userland
>            Version: 0.5.11
>             Branch: 2018.0.0.0
>     Packaging Date: Sun Jun 23 22:35:19 2019
>               Size: 0.00 B
>               FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z
> 
> I expected that `pkg update -nv' would offer to remove the installed
> incorporation and replace all of the old illumos-gate packages, over
> 200 of them, with the new illumos-gate packages.  It didn't do that.
> It did report that it would replace ten packages from the v9os
> publisher with newer versions from the oi-userland publisher, but this
> list didn't include any of the illumos-gate packages.

So it appears that pkg does not recognize the fact that version
0.5.11-2018.0.0.0:20190623T223519Z is newer than version
0.5.11-0.151100:20160727T071237Z -- correct?

> When I tried to remove the incorporation with pkg, I got this result:
[...]

I don't think that you are supposed to be able to remove the package
altogether.  You should, hovewer, be able to update it.

Do you also have an "entire" package?  If so, what version does it
have?


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt        Consulting and Support for Solaris-based Systems
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"


From gary_mills at fastmail.fm  Wed Jun 26 00:31:04 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 25 Jun 2019 19:31:04 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <23826.35755.98828.321659@shelob.bb-c.de>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
Message-ID: <20190626003104.GA10000@mail.messagingengine.com>

On Tue, Jun 25, 2019 at 11:01:31PM +0200, Volker A. Brandt wrote:
> 
> So it appears that pkg does not recognize the fact that version
> 0.5.11-2018.0.0.0:20190623T223519Z is newer than version
> 0.5.11-0.151100:20160727T071237Z -- correct?

I don't think that that is the problem.  Consider this transcript:

    # pkg update -nv
    ...
    Changed packages:
    ...
    v9os -> oi-userland
      archiver/gnu-tar
        1.28-0.151100 -> 1.29-2018.0.0.0
      compress/bzip2
        1.0.6-0.151100 -> 1.0.6-2018.0.0.3
      compress/gzip
        1.6-0.151100 -> 1.9-2018.0.0.0

The version numbers were the same for the last two packages.

> > When I tried to remove the incorporation with pkg, I got this result:
> [...]
> 
> I don't think that you are supposed to be able to remove the package
> altogether.  You should, hovewer, be able to update it.

That's close to working.  I should be able to make it work.
Here's this one:

    # pkg update -nv pkg://oi-userland/consolidation/osnet/osnet-inco...
    Creating Plan (Solver setup): \
    pkg update: No matching version of consolidation/osnet/osnet-incorporation can be installed:
      Reject:  pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0
      Reason:  No version matching 'incorporate' dependency SUNWcs at 0.5.11-2018.0.0.0 can be installed
        ----------------------------------------
        Reject:  pkg://oi-userland/SUNWcs at 0.5.11-2018.0.0.0
        Reason:  No version matching 'require' dependency system/network/mailwrapper can be installed
          ----------------------------------------
          Reject:  pkg://oi-userland/system/network/mailwrapper at 0.5.11-2018.0.0.0
          Reason:  No version for 'require' dependency on system/mta can be found
          Reject:  pkg://v9os/system/network/mailwrapper at 0.5.11-0.151100
          Reason:  Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation'
          ----------------------------------------
        ----------------------------------------

> Do you also have an "entire" package?  If so, what version does it
> have?

No, I don't have that package.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-


From naj at snapcon.com  Wed Jun 26 00:28:12 2019
From: naj at snapcon.com (Norm Jacobs)
Date: Tue, 25 Jun 2019 19:28:12 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190625204720.GA8601@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
Message-ID: <1bba6380-a729-e329-a326-0fd1aa7572fb@snapcon.com>

You might look at the 'entire' package and see if it constrains the 
'osnet-incorporation to the older version.? That is most likely the 
cause of your trouble.? You can probably remove the 'entire' package and 
then update.? You might also be able to unlock the incorporation before 
upgrading instead.

 ??? -Norm


On 6/25/19 3:47 PM, Gary Mills wrote:
> These are my publishers:
>
>      # pkg publisher
>      PUBLISHER                   TYPE     STATUS P LOCATION
>      oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
>      v9os           (non-sticky) origin   online F file:///data/ips/
>
> I just published all of illumos-gate to the oi-userland repository.
> There are now two copies of the
> consolidation/osnet/osnet-incorporation package.  This is the
> installed one:
>
>      # pkg info consolidation/osnet/osnet-incorporation
>                Name: consolidation/osnet/osnet-incorporation
>             Summary: OS/Net consolidation incorporation
>         Description: This incorporation constrains packages from the OS/Net
>                      consolidation.
>               State: Installed
>           Publisher: v9os
>             Version: 0.5.11
>              Branch: 0.151100
>      Packaging Date: Wed Jul 27 07:12:37 2016
>                Size: 0.00 B
>                FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
>      
> This is the new one:
>
>      # pkg info -r consolidation/osnet/osnet-incorporation
>                Name: consolidation/osnet/osnet-incorporation
>             Summary: OS/Net consolidation incorporation
>         Description: This incorporation constrains packages from the OS/Net
>                      consolidation.
>               State: Not installed
>           Publisher: oi-userland
>             Version: 0.5.11
>              Branch: 2018.0.0.0
>      Packaging Date: Sun Jun 23 22:35:19 2019
>                Size: 0.00 B
>                FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z
>
> I expected that `pkg update -nv' would offer to remove the installed
> incorporation and replace all of the old illumos-gate packages, over
> 200 of them, with the new illumos-gate packages.  It didn't do that.
> It did report that it would replace ten packages from the v9os
> publisher with newer versions from the oi-userland publisher, but this
> list didn't include any of the illumos-gate packages.
>
> When I tried to remove the incorporation with pkg, I got this result:
>
>      # pkg uninstall -nv consolidation/osnet/osnet-incorporation
>      Creating Plan (Solver setup): -
>      pkg uninstall: Unable to remove 'consolidation/osnet/osnet-incorporation at 0.5.11-0.151100' due to the following packages that depend on it:
>        SUNWcs at 0.5.11-0.151100
>        SUNWcsd at 0.5.11-0.151100
>        compatibility/ucb at 0.5.11-0.151100
>        developer/astdev at 0.5.11-0.151100
>      ...
>        system/zones at 0.5.11-0.151100
>        system/zones/internal at 0.5.11-0.151100
>        text/doctools at 0.5.11-0.151100
>        text/locale at 0.5.11-0.151100
>
> Have I run into a dead end, or is there a way out of this dilemma?
>
>


From richlowe at richlowe.net  Wed Jun 26 00:42:41 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Tue, 25 Jun 2019 20:42:41 -0400
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190626003104.GA10000@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
	<20190626003104.GA10000@mail.messagingengine.com>
Message-ID: <CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>

Reason:  No version for 'require' dependency on system/mta can be found

Seems a leaf failure, does one really not exist?


From gary_mills at fastmail.fm  Wed Jun 26 12:52:41 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Wed, 26 Jun 2019 07:52:41 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
	<20190626003104.GA10000@mail.messagingengine.com>
	<CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>
Message-ID: <20190626125240.GA12540@mail.messagingengine.com>

On Tue, Jun 25, 2019 at 08:42:41PM -0400, Richard Lowe wrote:
> Reason:  No version for 'require' dependency on system/mta can be found
> 
> Seems a leaf failure, does one really not exist?

Indeed, the package system/mta does not exist in either publisher.  I
just published it to oi-userland and installed it.  My next task is to
see if that missing package was preventing the update.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-


From gordon.w.ross at gmail.com  Fri Jun 28 04:25:37 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 27 Jun 2019 21:25:37 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
Message-ID: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>

Any ideas what I should do to fix this?

root at oi-dev:/home/gwr# pkg -R /mnt image-update -v
Creating Plan (Running solver): /
pkg update: No solution was found to satisfy constraints
No solution found to update to latest available versions.
This may indicate an overly constrained set of packages are installed.

latest incorporations:

  pkg://openindiana.org/consolidation/install/install-incorporation at 0.5.11,5.11-2018.0.0.1041:20190516T142943Z
  pkg://openindiana.org/consolidation/l10n/l10n-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014527Z
  pkg://openindiana.org/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014529Z
  pkg://openindiana.org/consolidation/userland/userland-incorporation at 0.5.11,5.11-2018.0.0.11903:20190627T091450Z

Dependency analysis is unable to determine the cause.
Try specifying expected versions to obtain more detailed error messages.

On Sun, May 12, 2019 at 12:33 AM Alexander Pyhalov via oi-dev
<oi-dev at openindiana.org> wrote:
>
> Sorry, missed dot in
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso link.
>
> ? ?????????,
> ????????? ???????,
> ??????????? ?????? ???????????????????? ??????????????
> ?????????? ?????????????-???????????????? ?????????????? ???
>
>
> ________________________________________
> ??: Alexander Pyhalov via oi-dev <oi-dev at openindiana.org>
> ??????????: 12 ??? 2019 ?. 10:11:57
> ????: OpenIndiana Developer mailing list
> ?????: Alexander Pyhalov
> ????: [oi-dev] OI Hipster 2019.04
>
> Hi.
>
> OI Hipster 2019.04 snapshot is ready.
>
> Images:
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb
>
>
> SHA 256 checksums are available at ${link}.sha256sum
> Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
> https://sks-keyservers.net/pks/lookup?op=get&search=0x3A021AFADBE31887 ).
>
> Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes
>
> Note, we have an issue with Firefox on live image - it can fail to start correctly when launched for the first time in memory-constrained  environment. After being killed and restarted it behaves more sane.
>
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev


From gordon.w.ross at gmail.com  Fri Jun 28 04:26:44 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 27 Jun 2019 21:26:44 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
Message-ID: <CAD0Ztp2nrGdb3t2sKjUdR9HNNwdSJ_t=eJs=6UBesB2Uo=+wtA@mail.gmail.com>

I'm guessing people will want to see:

root at oi-dev:/home/gwr# pkg -R /mnt publisher
PUBLISHER                   TYPE     STATUS P LOCATION
openindiana.org              origin   online F
http://pkg.openindiana.org/hipster/
root at oi-dev:/home/gwr# pkg -R /mnt info entire
          Name: entire
       Summary: incorporation to lock all system packages to same build (empty
                package)
   Description: incorporation to lock all system packages to same build (empty
                package)
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
        Branch: 2018.0.0.0
Packaging Date: February 11, 2018 at 01:10:12 PM
          Size: 0.00 B
          FMRI: pkg://openindiana.org/entire at 0.5.11-2018.0.0.0:20180211T131012Z

On Thu, Jun 27, 2019 at 9:25 PM Gordon Ross <gordon.w.ross at gmail.com> wrote:
>
> Any ideas what I should do to fix this?
>
> root at oi-dev:/home/gwr# pkg -R /mnt image-update -v
> Creating Plan (Running solver): /
> pkg update: No solution was found to satisfy constraints
> No solution found to update to latest available versions.
> This may indicate an overly constrained set of packages are installed.
>
> latest incorporations:
>
>   pkg://openindiana.org/consolidation/install/install-incorporation at 0.5.11,5.11-2018.0.0.1041:20190516T142943Z
>   pkg://openindiana.org/consolidation/l10n/l10n-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014527Z
>   pkg://openindiana.org/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014529Z
>   pkg://openindiana.org/consolidation/userland/userland-incorporation at 0.5.11,5.11-2018.0.0.11903:20190627T091450Z
>
> Dependency analysis is unable to determine the cause.
> Try specifying expected versions to obtain more detailed error messages.
>
> On Sun, May 12, 2019 at 12:33 AM Alexander Pyhalov via oi-dev
> <oi-dev at openindiana.org> wrote:
> >
> > Sorry, missed dot in
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso link.
> >
> > ? ?????????,
> > ????????? ???????,
> > ??????????? ?????? ???????????????????? ??????????????
> > ?????????? ?????????????-???????????????? ?????????????? ???
> >
> >
> > ________________________________________
> > ??: Alexander Pyhalov via oi-dev <oi-dev at openindiana.org>
> > ??????????: 12 ??? 2019 ?. 10:11:57
> > ????: OpenIndiana Developer mailing list
> > ?????: Alexander Pyhalov
> > ????: [oi-dev] OI Hipster 2019.04
> >
> > Hi.
> >
> > OI Hipster 2019.04 snapshot is ready.
> >
> > Images:
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb
> >
> >
> > SHA 256 checksums are available at ${link}.sha256sum
> > Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> > The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
> > https://sks-keyservers.net/pks/lookup?op=get&search=0x3A021AFADBE31887 ).
> >
> > Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes
> >
> > Note, we have an issue with Firefox on live image - it can fail to start correctly when launched for the first time in memory-constrained  environment. After being killed and restarted it behaves more sane.
> >
> > Best regards,
> > Alexander Pyhalov,
> > system administrator of Southern Federal University IT department
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev


From richlowe at richlowe.net  Fri Jun 28 05:28:15 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Fri, 28 Jun 2019 01:28:15 -0400
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
Message-ID: <CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>

> Dependency analysis is unable to determine the cause.
> Try specifying expected versions to obtain more detailed error messages.
>

Do what it says there,

Specify the verisons of those 'latest incorporations', and probably
also entire, including the versions.

You may be able to just do 'pkg install -nv entire at latest' but I can
never remember whether only specifying 'entire' does the right thing.


From gordon.w.ross at gmail.com  Fri Jun 28 17:32:25 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Fri, 28 Jun 2019 10:32:25 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
Message-ID: <CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>

OK, but I can't seem to find the latest version of entire.
Can anyone tell me what that should be?

root at oi-dev:/home/gwr# pkg -R /mnt refresh --full
root at oi-dev:/home/gwr# pkg -R /mnt update -nv entire at latest
No updates available for this image.
root at oi-dev:/home/gwr# pkg -R /mnt install -nv entire at latest
No updates necessary for this image.
root at oi-dev:/home/gwr# pkg -R /mnt info entire
          Name: entire
       Summary: incorporation to lock all system packages to same build (empty
                package)
   Description: incorporation to lock all system packages to same build (empty
                package)
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
        Branch: 2018.0.0.0
Packaging Date: February 11, 2018 at 01:10:12 PM
          Size: 0.00 B
          FMRI: pkg://openindiana.org/entire at 0.5.11-2018.0.0.0:20180211T131012Z

On Thu, Jun 27, 2019 at 10:28 PM Richard Lowe <richlowe at richlowe.net> wrote:
>
> > Dependency analysis is unable to determine the cause.
> > Try specifying expected versions to obtain more detailed error messages.
> >
>
> Do what it says there,
>
> Specify the verisons of those 'latest incorporations', and probably
> also entire, including the versions.
>
> You may be able to just do 'pkg install -nv entire at latest' but I can
> never remember whether only specifying 'entire' does the right thing.
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev


From richlowe at richlowe.net  Fri Jun 28 17:43:23 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Fri, 28 Jun 2019 13:43:23 -0400
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
	<CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>
Message-ID: <CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?


From alp at sfedu.ru  Sat Jun 29 05:37:26 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Sat, 29 Jun 2019 05:37:26 +0000
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
	<CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>,
	<CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>
Message-ID: <AM6PR05MB6198F5838BDA1D994F326236CFFF0@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.
entire is a package which depends on userland-incorporation. That's all. You are interested in latest osnet-incorporation and userland-incorporation.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Richard Lowe <richlowe at richlowe.net>
??????????: 28 ???? 2019 ?. 20:43
????: OpenIndiana Developer mailing list
????: Re: [oi-dev] OI Hipster 2019.04

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev


From grzemba at contac-dt.de  Mon Jun  3 14:44:26 2019
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Mon, 03 Jun 2019 16:44:26 +0200
Subject: [oi-dev] Openindiana on Laptop: touchpad not working
In-Reply-To: <bd3e8f4829c5.5ce65b00@contac-dt.de>
References: <be86e6074ec1.5ce41f99@contac-dt.de>
	<alpine.GSO.2.20.1905211010220.7749@scrappy.simplesystems.org>
	<bd3e8f4829c5.5ce65b00@contac-dt.de>
Message-ID: <bd3d30256aff.5cf54e6a@contac-dt.de>


<signaturebeforequotedtext></signaturebeforequotedtext>
On 23.05.19 08:34, Carsten Grzemba via oi-dev  <oi-dev at openindiana.org> wrote: 
> 
> I compared the Xorg log:
> 
> in the working log the mouse driver is loaded on PS/s mouse on /dev/mouse:
> 
> [ 38.008] (II) LoadModule: "mouse"
> [ 38.008] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> [ 38.012] (II) Module mouse: vendor="X.Org Foundation"
> [ 38.012] compiled for 1.19.5, module version = 1.9.2
> [ 38.012] Module class: X.Org XInput Driver
> [ 38.012] ABI class: X.Org XInput driver, version 24.1
> [ 38.012] (II) Using input driver 'mouse' for 'PS/2 Port for PS/2-style Mice'
> [ 38.012] (**) PS/2 Port for PS/2-style Mice: always reports core events
> [ 38.012] (**) Option "Device" "/dev/mouse"
> [ 38.012] (II) PS/2 Port for PS/2-style Mice: Setting Device option to "/dev/mouse"
> [ 38.014] (==) PS/2 Port for PS/2-style Mice: Protocol: "VUID"
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: always reports core events
> [ 38.014] (**) Option "Device" "/dev/mouse"
> [ 38.014] (==) PS/2 Port for PS/2-style Mice: Emulate3Buttons, Emulate3Timeout: 50
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: ZAxisMapping: buttons 4 and 5
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: Buttons: 9
> [ 38.014] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/isa_1f/i8042_1_60/mouse_1_0_logicaldev_input"
> [ 38.014] (II) XINPUT: Adding extended input device "PS/2 Port for PS/2-style Mice" (type: MOUSE, id 6)
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) keeping acceleration scheme 1
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration profile 0
> [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration factor: 2.000
> [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration threshold: 4
> 
> and the not working on the generic USB device /dev/usb/hid1:
> 
> [ 523.036] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> [ 523.036] (II) Module mouse: vendor="X.Org Foundation"
> [ 523.036] compiled for 1.19.5, module version = 1.9.2
> [ 523.036] Module class: X.Org XInput Driver
> [ 523.037] ABI class: X.Org XInput driver, version 24.1
> [ 523.037] (II) Using input driver 'mouse' for 'mouse'
> [ 523.037] (**) mouse: always reports core events
> [ 523.037] (**) Option "Protocol" "VUID"
> [ 523.037] (**) Option "Device" "/dev/usb/hid1"
> [ 523.037] (**) Option "StreamsModule" "usbms"
> [ 523.039] (**) mouse: Protocol: "VUID"
> [ 523.039] (**) mouse: always reports core events
> [ 523.039] (==) mouse: Emulate3Buttons, Emulate3Timeout: 50
> [ 523.039] (**) mouse: ZAxisMapping: buttons 4 and 5
> [ 523.039] (**) mouse: Buttons: 9
> [ 523.039] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1025_1019_14/device_4/mouse_1_if1_4_logicaldev_input"
> [ 523.039] (II) XINPUT: Adding extended input device "mouse" (type: MOUSE, id 6)
> [ 523.039] (**) mouse: (accel) keeping acceleration scheme 1
> [ 523.039] (**) mouse: (accel) acceleration profile 0
> [ 523.039] (**) mouse: (accel) acceleration factor: 2.000
> [ 523.039] (**) mouse: (accel) acceleration threshold: 4
> [ 523.045] (II) config/hal: Adding input device hotkey
> 
> 
> in both cases is the the touchpad avail and a extern USB mouse connected. the /dev/mouse dev link is in both BE targeted to /devices/pseudo/cons at 0:mouse
> 
> 
Still no luck with the latest hipster on my laptop:

scanpci:
pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1604
?Intel Corporation Broadwell-U Host Bridge -OPI

pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1616
?Intel Corporation HD Graphics 5500

pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x160c
?Intel Corporation Broadwell-U Audio Controller

pci bus 0x0000 cardnum 0x14 function 0x00: vendor 0x8086 device 0x9cb1
?Intel Corporation Wildcat Point-LP USB xHCI Controller

pci bus 0x0000 cardnum 0x16 function 0x00: vendor 0x8086 device 0x9cba
?Intel Corporation Wildcat Point-LP MEI Controller #1

pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x9ca0
?Intel Corporation Wildcat Point-LP High Definition Audio Controller

pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x9c90
?Intel Corporation Wildcat Point-LP PCI Express Root Port #1

pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device 0x9c94
?Intel Corporation Wildcat Point-LP PCI Express Root Port #3

pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
?Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device 0x9c96
?Intel Corporation Wildcat Point-LP PCI Express Root Port #4

pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x8086 device 0x095a
?Intel Corporation Wireless 7265

pci bus 0x0000 cardnum 0x1c function 0x04: vendor 0x8086 device 0x9c98
?Intel Corporation Wildcat Point-LP PCI Express Root Port #5

pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10de device 0x1299
?NVIDIA Corporation GK208BM [GeForce 920M]

pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x9ca6
?Intel Corporation Wildcat Point-LP USB EHCI Controller

pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x9cc3
?Intel Corporation Wildcat Point-LP LPC ControllerX.Org X Server 1.19.6

pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x9c83
?Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode]

pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x9ca2
?Intel Corporation Wildcat Point-LP SMBus Controller

I boot from latest USB image there X session dont start, only the mouse pointer is seen. If I kill the Xorg via SSH I get no text console.
So I reboot in text console and tried to test Xorg configuration with my current working settings (of Xorg 1.19.6 vesa for the Intel, Nvidia was never usable with the old i915 driver). There I get only a black screen and after kill Xorg no text console again. 
Activating vtdaemon and vt-console also not working.

What is the change here, so that Xorg 1.19.7 isn't working anymore? In Xorg.0.log I dont see any errors.

Thanks



























 <signatureafterquotedtext></signatureafterquotedtext>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190603/0736b268/attachment-0002.html>

From grzemba at contac-dt.de  Tue Jun  4 08:27:09 2019
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Tue, 04 Jun 2019 10:27:09 +0200
Subject: [oi-dev] Openindiana on Laptop: touchpad not working
In-Reply-To: <bd3d30256aff.5cf54e6a@contac-dt.de>
References: <be86e6074ec1.5ce41f99@contac-dt.de>
	<alpine.GSO.2.20.1905211010220.7749@scrappy.simplesystems.org>
	<bd3e8f4829c5.5ce65b00@contac-dt.de>
	<bd3d30256aff.5cf54e6a@contac-dt.de>
Message-ID: <bf5f8a435076.5cf6477d@contac-dt.de>


<signaturebeforequotedtext></signaturebeforequotedtext>
On 03.06.19 16:44, "Carsten Grzemba"  <grzemba at contac-dt.de> wrote: 
> 
> 
> 
> On 23.05.19 08:34, Carsten Grzemba via oi-dev  <oi-dev at openindiana.org> wrote: 
> > 
> > I compared the Xorg log:
> > 
> > in the working log the mouse driver is loaded on PS/s mouse on /dev/mouse:
> > 
> > [ 38.008] (II) LoadModule: "mouse"
> > [ 38.008] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> > [ 38.012] (II) Module mouse: vendor="X.Org Foundation"
> > [ 38.012] compiled for 1.19.5, module version = 1.9.2
> > [ 38.012] Module class: X.Org XInput Driver
> > [ 38.012] ABI class: X.Org XInput driver, version 24.1
> > [ 38.012] (II) Using input driver 'mouse' for 'PS/2 Port for PS/2-style Mice'
> > [ 38.012] (**) PS/2 Port for PS/2-style Mice: always reports core events
> > [ 38.012] (**) Option "Device" "/dev/mouse"
> > [ 38.012] (II) PS/2 Port for PS/2-style Mice: Setting Device option to "/dev/mouse"
> > [ 38.014] (==) PS/2 Port for PS/2-style Mice: Protocol: "VUID"
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: always reports core events
> > [ 38.014] (**) Option "Device" "/dev/mouse"
> > [ 38.014] (==) PS/2 Port for PS/2-style Mice: Emulate3Buttons, Emulate3Timeout: 50
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: ZAxisMapping: buttons 4 and 5
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: Buttons: 9
> > [ 38.014] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/isa_1f/i8042_1_60/mouse_1_0_logicaldev_input"
> > [ 38.014] (II) XINPUT: Adding extended input device "PS/2 Port for PS/2-style Mice" (type: MOUSE, id 6)
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) keeping acceleration scheme 1
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration profile 0
> > [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration factor: 2.000
> > [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration threshold: 4
> > 
> > and the not working on the generic USB device /dev/usb/hid1:
> > 
> > [ 523.036] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> > [ 523.036] (II) Module mouse: vendor="X.Org Foundation"
> > [ 523.036] compiled for 1.19.5, module version = 1.9.2
> > [ 523.036] Module class: X.Org XInput Driver
> > [ 523.037] ABI class: X.Org XInput driver, version 24.1
> > [ 523.037] (II) Using input driver 'mouse' for 'mouse'
> > [ 523.037] (**) mouse: always reports core events
> > [ 523.037] (**) Option "Protocol" "VUID"
> > [ 523.037] (**) Option "Device" "/dev/usb/hid1"
> > [ 523.037] (**) Option "StreamsModule" "usbms"
> > [ 523.039] (**) mouse: Protocol: "VUID"
> > [ 523.039] (**) mouse: always reports core events
> > [ 523.039] (==) mouse: Emulate3Buttons, Emulate3Timeout: 50
> > [ 523.039] (**) mouse: ZAxisMapping: buttons 4 and 5
> > [ 523.039] (**) mouse: Buttons: 9
> > [ 523.039] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1025_1019_14/device_4/mouse_1_if1_4_logicaldev_input"
> > [ 523.039] (II) XINPUT: Adding extended input device "mouse" (type: MOUSE, id 6)
> > [ 523.039] (**) mouse: (accel) keeping acceleration scheme 1
> > [ 523.039] (**) mouse: (accel) acceleration profile 0
> > [ 523.039] (**) mouse: (accel) acceleration factor: 2.000
> > [ 523.039] (**) mouse: (accel) acceleration threshold: 4
> > [ 523.045] (II) config/hal: Adding input device hotkey
> > 
> > 
> > in both cases is the the touchpad avail and a extern USB mouse connected. the /dev/mouse dev link is in both BE targeted to /devices/pseudo/cons at 0:mouse
> > 
> > 
> Still no luck with the latest hipster on my laptop:
> 
> scanpci:
> pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1604
> ?Intel Corporation Broadwell-U Host Bridge -OPI
> 
> pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1616
> ?Intel Corporation HD Graphics 5500
> 
> pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x160c
> ?Intel Corporation Broadwell-U Audio Controller
> 
> pci bus 0x0000 cardnum 0x14 function 0x00: vendor 0x8086 device 0x9cb1
> ?Intel Corporation Wildcat Point-LP USB xHCI Controller
> 
> pci bus 0x0000 cardnum 0x16 function 0x00: vendor 0x8086 device 0x9cba
> ?Intel Corporation Wildcat Point-LP MEI Controller #1
> 
> pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x9ca0
> ?Intel Corporation Wildcat Point-LP High Definition Audio Controller
> 
> pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x9c90
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #1
> 
> pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device 0x9c94
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #3
> 
> pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
> ?Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
> 
> pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device 0x9c96
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #4
> 
> pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x8086 device 0x095a
> ?Intel Corporation Wireless 7265
> 
> pci bus 0x0000 cardnum 0x1c function 0x04: vendor 0x8086 device 0x9c98
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #5
> 
> pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10de device 0x1299
> ?NVIDIA Corporation GK208BM [GeForce 920M]
> 
> pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x9ca6
> ?Intel Corporation Wildcat Point-LP USB EHCI Controller
> 
> pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x9cc3
> ?Intel Corporation Wildcat Point-LP LPC ControllerX.Org X Server 1.19.6
> 
> pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x9c83
> ?Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode]
> 
> pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x9ca2
> ?Intel Corporation Wildcat Point-LP SMBus Controller
> 
> I boot from latest USB image there X session dont start, only the mouse pointer is seen. If I kill the Xorg via SSH I get no text console.
> So I reboot in text console and tried to test Xorg configuration with my current working settings (of Xorg 1.19.6 vesa for the Intel, Nvidia was never usable with the old i915 driver). There I get only a black screen and after kill Xorg no text console again. 
> Activating vtdaemon and vt-console also not working.
> 
> What is the change here, so that Xorg 1.19.7 isn't working anymore? In Xorg.0.log I dont see any errors.
> 
> Thanks 
> 
Because the Xorg config is not changed and the touchpad not working on newer hipster, it looks for me like the touchpad is disabled what can normaly toggled by Fn F7.
But Fn keys do not work at all on newer hipster. Something to do with ACPI ?

 <signatureafterquotedtext></signatureafterquotedtext>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190604/1b76e6e2/attachment-0002.html>

From randyf at sibernet.com  Tue Jun 11 18:07:21 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 11:07:21 -0700 (PDT)
Subject: [oi-dev] suspend/resume in Illumos
Message-ID: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>



I have a question for developers here:

    How important is suspend/resume for OI/Illumos (including S4)?


One of the incomplete projects left behind was S4 (lack of need, and a 
hard to identify bug stifled it's integration).  It is non-trivial, and 
needs updated s/r core code (added configuration and significant 
restructuring, as well as likely assistance from developers knowlegable in 
other Illumos internals), but if this is an uninteresting feature, it is 
likey not worth the effort (recent bugs suggest that few if anyone use 
it); however, it wouldn't be too hard to resurect (though would still take 
several months of work).


   Cheers!

 	---- Randy



From gary_mills at fastmail.fm  Tue Jun 11 18:10:11 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 11 Jun 2019 13:10:11 -0500
Subject: [oi-dev] Toward a SPARC distro of OI
Message-ID: <20190611181011.GA18869@mail.messagingengine.com>

I'm part way through this long project now.  I began with v9os
installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
packages.  I've been building IPS packages from oi-userland source.
This process has gotten easier now that all the build tools I need are
in IPS packages.  I've been replacing v9os packages with oi-userland
packages.  My goal is to replace all of them, and finally to produce a
text ISO and package repository for SPARC that's entirely based on
oi-userland.

So far, I've built and packaged versions 5, 6, and 7 of the gcc
compiler.  The commands for IPS packages are all packaged for python
2.7.  My system now has 106 packages installed from oi-userland,
versus 343 packages from v9os.  Most of the oi-userland products
required very few or no changes to build and package for SPARC.

For perl, I've removed the 5.16.1 version from v9os and installed
versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
packaged for 5.22.  Python libraries are all packaged for 2.7.

I'm submitting this message to the mailing list mostly as a progress
report.  I would, of course, appreciate a bit of help with this
project.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From garrett at damore.org  Tue Jun 11 19:58:08 2019
From: garrett at damore.org (Garrett D'Amore)
Date: Tue, 11 Jun 2019 12:58:08 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
Message-ID: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>

My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where suspend/resume has little if any applicability.

While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from other more pressing work, without any clear use cases for it.

That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any other reason we would reject a suitably formed RTI.

Sent from Mail for Windows 10

From: randyf at sibernet.com
Sent: Tuesday, June 11, 2019 11:10 AM
To: oi-dev at openindiana.org; developer at lists.illumos.org
Subject: [developer] suspend/resume in Illumos



I have a question for developers here:

    How important is suspend/resume for OI/Illumos (including S4)?


One of the incomplete projects left behind was S4 (lack of need, and a 
hard to identify bug stifled it's integration).  It is non-trivial, and 
needs updated s/r core code (added configuration and significant 
restructuring, as well as likely assistance from developers knowlegable in 
other Illumos internals), but if this is an uninteresting feature, it is 
likey not worth the effort (recent bugs suggest that few if anyone use 
it); however, it wouldn't be too hard to resurect (though would still take 
several months of work).


   Cheers!

        ---- Randy

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190611/347dae6d/attachment-0002.html>

From tsoome at me.com  Tue Jun 11 20:31:18 2019
From: tsoome at me.com (Toomas Soome)
Date: Tue, 11 Jun 2019 23:31:18 +0300
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
Message-ID: <DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>

I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be bonus.

Sent from my iPhone

> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
> 
> My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where suspend/resume has little if any applicability.
>  
> While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from other more pressing work, without any clear use cases for it.
>  
> That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any other reason we would reject a suitably formed RTI.
>  
> Sent from Mail for Windows 10
>  
> From: randyf at sibernet.com
> Sent: Tuesday, June 11, 2019 11:10 AM
> To: oi-dev at openindiana.org; developer at lists.illumos.org
> Subject: [developer] suspend/resume in Illumos
>  
>  
>  
> I have a question for developers here:
>  
>     How important is suspend/resume for OI/Illumos (including S4)?
>  
>  
> One of the incomplete projects left behind was S4 (lack of need, and a
> hard to identify bug stifled it's integration).  It is non-trivial, and
> needs updated s/r core code (added configuration and significant
> restructuring, as well as likely assistance from developers knowlegable in
> other Illumos internals), but if this is an uninteresting feature, it is
> likey not worth the effort (recent bugs suggest that few if anyone use
> it); however, it wouldn't be too hard to resurect (though would still take
> several months of work).
>  
>  
>    Cheers!
>  
>         ---- Randy
>  
> ------------------------------------------
> illumos: illumos-developer
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
>  
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190611/1b0c9592/attachment-0002.html>

From randyf at sibernet.com  Tue Jun 11 21:28:34 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 14:28:34 -0700 (PDT)
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
Message-ID: <alpine.SOC.2.00.1906111420090.15467@sibernet.com>



On Tue, 11 Jun 2019, Garrett D'Amore wrote:

> 
> My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where
> suspend/resume has little if any applicability.
> 
> ?
> 
> While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from
> other more pressing work, without any clear use cases for it.
>

   I should point out that s/r isn't just for laptop bare-metal.  It allows 
for a running instance of an OS to be frozen in an orderly manner (rather 
than a VM just pausing a guest, the guest suspends first).  S4 opens a 
different world of allowing said image to be more easily migrated, or 
(since it has roots in CPR) opens quick-boot images (imagine getting an 
OS fully booted in under 10 seconds).

> ?
> 
> That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m
> fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any
> other reason we would reject a suitably formed RTI.
>

   Doubt I'll fully drop it, but without sufficient interest, it's is 
unlikely I'll give it much priority (certainly, my other 'dropped' project 
should have a higer priority).

   Cheers!

 	---- Randy

> ?
> 
> Sent from Mail for Windows 10
> 
> ?
> 
> From: randyf at sibernet.com
> Sent: Tuesday, June 11, 2019 11:10 AM
> To: oi-dev at openindiana.org; developer at lists.illumos.org
> Subject: [developer] suspend/resume in Illumos
> 
> ?
> 
> ?
> 
> ?
> 
> I have a question for developers here:
> 
> ?
> 
> ??? How important is suspend/resume for OI/Illumos (including S4)?
> 
> ?
> 
> ?
> 
> One of the incomplete projects left behind was S4 (lack of need, and a
> 
> hard to identify bug stifled it's integration).? It is non-trivial, and
> 
> needs updated s/r core code (added configuration and significant
> 
> restructuring, as well as likely assistance from developers knowlegable in
> 
> other Illumos internals), but if this is an uninteresting feature, it is
> 
> likey not worth the effort (recent bugs suggest that few if anyone use
> 
> it); however, it wouldn't be too hard to resurect (though would still take
> 
> several months of work).
> 
> ?
> 
> ?
> 
> ?? Cheers!
> 
> ?
> 
> ??????? ---- Randy
> 
> ?
> 
> ------------------------------------------
> 
> illumos: illumos-developer
> 
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> 
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
> 
> ?
> 
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
> 
>

From randyf at sibernet.com  Tue Jun 11 21:29:23 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 14:29:23 -0700 (PDT)
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
Message-ID: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>



On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:

> I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be
> bonus.

   Betting better graphics support would be higher on the list (yea, the 
other 'dropped' project).

   Cheers!

 	---- Randy

> 
> Sent from my iPhone
> 
> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>
>       My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter
>       applications where suspend/resume has little if any applicability.
>
>       ?
>
>       While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be
>       detraction from other more pressing work, without any clear use cases for it.
>
>       ?
>
>       That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it,
>       and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for
>       example), I can?t see any other reason we would reject a suitably formed RTI.
>
>       ?
>
>       Sent from Mail for Windows 10
>
>       ?
>
>       From: randyf at sibernet.com
>       Sent: Tuesday, June 11, 2019 11:10 AM
>       To: oi-dev at openindiana.org; developer at lists.illumos.org
>       Subject: [developer] suspend/resume in Illumos
> 
> ?
> 
> ?
> 
> ?
> 
> I have a question for developers here:
> 
> ?
> 
> ??? How important is suspend/resume for OI/Illumos (including S4)?
> 
> ?
> 
> ?
> 
> One of the incomplete projects left behind was S4 (lack of need, and a
> 
> hard to identify bug stifled it's integration).? It is non-trivial, and
> 
> needs updated s/r core code (added configuration and significant
> 
> restructuring, as well as likely assistance from developers knowlegable in
> 
> other Illumos internals), but if this is an uninteresting feature, it is
> 
> likey not worth the effort (recent bugs suggest that few if anyone use
> 
> it); however, it wouldn't be too hard to resurect (though would still take
> 
> several months of work).
> 
> ?
> 
> ?
> 
> ?? Cheers!
> 
> ?
> 
> ??????? ---- Randy
> 
> ?
> 
> ------------------------------------------
> 
> illumos: illumos-developer
> 
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> 
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
> 
> ?
> 
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
> 
>

From josh at sysmgr.org  Tue Jun 11 21:32:28 2019
From: josh at sysmgr.org (Joshua M. Clulow)
Date: Tue, 11 Jun 2019 14:32:28 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <CAEwA5nJHmR+Md2hh2HGj5770+-x=uanePOwqTrYRBe4W0GxPoQ@mail.gmail.com>

On Tue, 11 Jun 2019 at 14:29, <randyf at sibernet.com> wrote:
> On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
> > I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be
> > bonus.
>
>    Betting better graphics support would be higher on the list (yea, the
> other 'dropped' project).

I think there are a fair few people who would appreciate some serious
elbow grease being applied to the graphics bits!


Cheers.

-- 
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org



From jimklimov at cos.ru  Wed Jun 12 08:01:25 2019
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 12 Jun 2019 08:01:25 +0000
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>

On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>
>
>On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>
>> I?d say, anything to encourage people to try, use and join to develop
>[illumos] is very welcome. Better laptop support will definitely be
>> bonus.
>
> Betting better graphics support would be higher on the list (yea, the 
>other 'dropped' project).
>
>   Cheers!
>
>        ---- Randy
>
>> 
>> Sent from my iPhone
>> 
>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> My gut instinct is that this isn?t that interesting ? most everyone
>is running illumos in either VMs, or in datacenter
>> applications where suspend/resume has little if any applicability.
>> 
>> While the work itself is probably interesting, and it may enable new
>applications for illumos, the concern I?d have would be
>> detraction from other more pressing work, without any clear use cases
>for it.
>> 
>> That said, if someone (you?) wanted to spend cycles on this for
>personal satisfaction, I hardly see any reason to discourage it,
>> and I?m fairly certain if the risks of the new code being introduced
>are small (or well managed by sufficient testing for
>> example), I can?t see any other reason we would reject a suitably
>formed RTI.
>> 
>> Sent from Mail for Windows 10
>> 
>> From: randyf at sibernet.com
>> Sent: Tuesday, June 11, 2019 11:10 AM
>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>> Subject: [developer] suspend/resume in Illumos
>> 
>> I have a question for developers here:
>> 
>> ??? How important is suspend/resume for OI/Illumos (including S4)?
>> 
>> One of the incomplete projects left behind was S4 (lack of need, and
>a
>> 
>> hard to identify bug stifled it's integration).? It is non-trivial,
>and
>> 
>> needs updated s/r core code (added configuration and significant
>> 
>> restructuring, as well as likely assistance from developers
>knowlegable in
>> 
>> other Illumos internals), but if this is an uninteresting feature, it
>is
>> 
>> likey not worth the effort (recent bugs suggest that few if anyone
>use
>> 
>> it); however, it wouldn't be too hard to resurect (though would still
>take
>> 
>> several months of work).
>> 
>> ?? Cheers!
>> 
>> ??????? ---- Randy
>> 
>> illumos / illumos-developer / see discussions + participants +
>delivery options Permalink
>> 
>------------------------------------------
>illumos: illumos-developer
>Permalink:
>https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>Delivery options:
>https://illumos.topicbox.com/groups/developer/subscription

For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.

My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.

Jim

--
Typos courtesy of K-9 Mail on my Android



From jimklimov at cos.ru  Wed Jun 12 08:01:25 2019
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 12 Jun 2019 08:01:25 +0000
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>

On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>
>
>On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>
>> I?d say, anything to encourage people to try, use and join to develop
>[illumos] is very welcome. Better laptop support will definitely be
>> bonus.
>
> Betting better graphics support would be higher on the list (yea, the 
>other 'dropped' project).
>
>   Cheers!
>
>        ---- Randy
>
>> 
>> Sent from my iPhone
>> 
>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> My gut instinct is that this isn?t that interesting ? most everyone
>is running illumos in either VMs, or in datacenter
>> applications where suspend/resume has little if any applicability.
>> 
>> While the work itself is probably interesting, and it may enable new
>applications for illumos, the concern I?d have would be
>> detraction from other more pressing work, without any clear use cases
>for it.
>> 
>> That said, if someone (you?) wanted to spend cycles on this for
>personal satisfaction, I hardly see any reason to discourage it,
>> and I?m fairly certain if the risks of the new code being introduced
>are small (or well managed by sufficient testing for
>> example), I can?t see any other reason we would reject a suitably
>formed RTI.
>> 
>> Sent from Mail for Windows 10
>> 
>> From: randyf at sibernet.com
>> Sent: Tuesday, June 11, 2019 11:10 AM
>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>> Subject: [developer] suspend/resume in Illumos
>> 
>> I have a question for developers here:
>> 
>> ??? How important is suspend/resume for OI/Illumos (including S4)?
>> 
>> One of the incomplete projects left behind was S4 (lack of need, and
>a
>> 
>> hard to identify bug stifled it's integration).? It is non-trivial,
>and
>> 
>> needs updated s/r core code (added configuration and significant
>> 
>> restructuring, as well as likely assistance from developers
>knowlegable in
>> 
>> other Illumos internals), but if this is an uninteresting feature, it
>is
>> 
>> likey not worth the effort (recent bugs suggest that few if anyone
>use
>> 
>> it); however, it wouldn't be too hard to resurect (though would still
>take
>> 
>> several months of work).
>> 
>> ?? Cheers!
>> 
>> ??????? ---- Randy
>> 
>> illumos / illumos-developer / see discussions + participants +
>delivery options Permalink
>> 
>------------------------------------------
>illumos: illumos-developer
>Permalink:
>https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>Delivery options:
>https://illumos.topicbox.com/groups/developer/subscription

For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.

My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.

Jim

--
Typos courtesy of K-9 Mail on my Android



From aurelien.larcher at gmail.com  Mon Jun 17 11:26:59 2019
From: aurelien.larcher at gmail.com (=?UTF-8?Q?Aur=C3=A9lien_Larcher?=)
Date: Mon, 17 Jun 2019 13:26:59 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <20190611181011.GA18869@mail.messagingengine.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
Message-ID: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>

On Mon, Jun 17, 2019 at 11:59 AM Gary Mills <gary_mills at fastmail.fm> wrote:

> I'm part way through this long project now.  I began with v9os
> installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
> packages.  I've been building IPS packages from oi-userland source.
> This process has gotten easier now that all the build tools I need are
> in IPS packages.  I've been replacing v9os packages with oi-userland
> packages.  My goal is to replace all of them, and finally to produce a
> text ISO and package repository for SPARC that's entirely based on
> oi-userland.
>
> So far, I've built and packaged versions 5, 6, and 7 of the gcc
> compiler.  The commands for IPS packages are all packaged for python
> 2.7.  My system now has 106 packages installed from oi-userland,
> versus 343 packages from v9os.  Most of the oi-userland products
> required very few or no changes to build and package for SPARC.
>
> For perl, I've removed the 5.16.1 version from v9os and installed
> versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
> removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
> packaged for 5.22.  Python libraries are all packaged for 2.7.
>
> I'm submitting this message to the mailing list mostly as a progress
> report.  I would, of course, appreciate a bit of help with this
> project.
>

Congratulations Gary this is great :)
If we get to the point that we can setup a build machine this would secure
your work.
Kind regards

Aur?lien



>
>
> --
> -Gary Mills-            -refurb-                -Winnipeg, Manitoba,
> Canada-
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


-- 
---
Praise the Caffeine embeddings
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190617/a222a8e2/attachment-0002.html>

From toasterson at gmail.com  Mon Jun 17 15:33:53 2019
From: toasterson at gmail.com (=?UTF-8?Q?Till_Wegm=c3=bcller?=)
Date: Mon, 17 Jun 2019 17:33:53 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
Message-ID: <63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com>

Hi Gary

Thank you so much for this Work. I don't personaly use sparc but ir is
good to see people doing this kinds of projects.

Do you know about Agnar's Project to get OI building on SPARC? I can't
remember if I ever pointed you towards him and his OI on Sparc work. His
angle was to jump from an existing OI distro to current packages and
later looking in V9OS.

Greetings
Till

On 17.06.19 13:26, Aur?lien Larcher wrote:
> 
> 
> On Mon, Jun 17, 2019 at 11:59 AM Gary Mills <gary_mills at fastmail.fm
> <mailto:gary_mills at fastmail.fm>> wrote:
> 
>     I'm part way through this long project now.? I began with v9os
>     installed on a Sun T2000.? v9os is a SPARC distribution that uses IPS
>     packages.? I've been building IPS packages from oi-userland source.
>     This process has gotten easier now that all the build tools I need are
>     in IPS packages.? I've been replacing v9os packages with oi-userland
>     packages.? My goal is to replace all of them, and finally to produce a
>     text ISO and package repository for SPARC that's entirely based on
>     oi-userland.
> 
>     So far, I've built and packaged versions 5, 6, and 7 of the gcc
>     compiler.? The commands for IPS packages are all packaged for python
>     2.7.? My system now has 106 packages installed from oi-userland,
>     versus 343 packages from v9os.? Most of the oi-userland products
>     required very few or no changes to build and package for SPARC.
> 
>     For perl, I've removed the 5.16.1 version from v9os and installed
>     versions 5.22 and 5.24 from oi-userland.? Likewise, for python, I've
>     removed 2.6 and installed 2.7 and 3.4.? Perl libraries are all
>     packaged for 5.22.? Python libraries are all packaged for 2.7.
> 
>     I'm submitting this message to the mailing list mostly as a progress
>     report.? I would, of course, appreciate a bit of help with this
>     project.
> 
> 
> Congratulations Gary this is great :)
> If we get to the point that we can setup a build machine this would
> secure your work.
> Kind regards
> 
> Aur?lien
> 
> ?
> 
> 
> 
>     -- 
>     -Gary Mills-? ? ? ? ? ? -refurb-? ? ? ? ? ? ? ? -Winnipeg, Manitoba,
>     Canada-
> 
>     _______________________________________________
>     oi-dev mailing list
>     oi-dev at openindiana.org <mailto:oi-dev at openindiana.org>
>     https://openindiana.org/mailman/listinfo/oi-dev
> 
> 
> 
> -- 
> ---
> Praise the Caffeine embeddings
> 
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
> 



From olbohlen at eenfach.de  Tue Jun 18 19:25:07 2019
From: olbohlen at eenfach.de (Olaf Bohlen)
Date: Tue, 18 Jun 2019 21:25:07 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com> ("Till
	=?utf-8?Q?Wegm=C3=BCller=22's?= message of "Mon, 17 Jun 2019 17:33:53
	+0200")
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
	<63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com>
Message-ID: <x6pnnavgq4.fsf@eenfach.de>

Till Wegm?ller <toasterson at gmail.com> writes:

Hi Till,
hi Gary,

> Do you know about Agnar's Project to get OI building on SPARC? I can't
> remember if I ever pointed you towards him and his OI on Sparc work. His
> angle was to jump from an existing OI distro to current packages and
> later looking in V9OS.

First: Gary, this is phantastic news, congrats to it! I'm looking
forward to hear more from you.

Second: Till, yes Gary and I have been in contact but since I have
not enough time, my progress is probably somewhat slower. I also
have newer bits running, but my approach is - as you mentioned -
doing bootstrapping a system to be able to build recent bits in
the correct way.

I'd be happy to hear once someone has built a bootable OI media
for sparc and would take up of these also.

Best regards,

-- 
      ~       Olaf Bohlen - olbohlen at eenfach.de
      |~~     Het
     /|  \    Bruine
 ___/_|___\   Leven
   \__n____/# DGCN2



From Tim.Mooney at ndsu.edu  Mon Jun 24 02:24:33 2019
From: Tim.Mooney at ndsu.edu (Tim Mooney)
Date: Sun, 23 Jun 2019 21:24:33 -0500 (CDT)
Subject: [oi-dev] component TODO list for perl components?
Message-ID: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,

 	https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164



From alp at sfedu.ru  Mon Jun 24 06:05:50 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 06:05:50 +0000
Subject: [oi-dev] component TODO list for perl components?
In-Reply-To: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
References: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
Message-ID: <AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.

I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/ some time ago. There are mostly tasks which I'm interested in.

Now I'm looking at removing binary blobs from DDU. Later I'll likely look at switching it to Python 3.5.

If you can propose any tasks which you can take (or pehaps, someone else), feel  free to update this page. I just don't want it to become a list of never-done tasks.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Tim Mooney <Tim.Mooney at ndsu.edu>
??????????: 24 ???? 2019 ?. 5:24:33
????: oi-dev at openindiana.org
????: [oi-dev] component TODO list for perl components?


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,

        https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
--
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



From garrett at damore.org  Mon Jun 24 14:42:34 2019
From: garrett at damore.org (Garrett D'Amore)
Date: Mon, 24 Jun 2019 07:42:34 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <DE25905A-0071-4339-B00A-9EB1D62CC5AB@gmail.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
	<699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>
	<DE25905A-0071-4339-B00A-9EB1D62CC5AB@gmail.com>
Message-ID: <5d10e157.1c69fb81.48b1c.91f9@mx.google.com>

That?s only true if you?re running on  a hypervisor that uses suspend / resume for live migration.  I?m not sure how widespread running illumos on VMware is ? the absence of suspend/resume support means that nobody is benefiting from this particular capability today (at least with illumos).

Sent from Mail for Windows 10

From: DavidHalko
Sent: Monday, June 24, 2019 5:18 AM
To: illumos-developer
Cc: randyf at sibernet.com; oi-dev at openindiana.org
Subject: Re: [developer] suspend/resume in Illumos

Suspend and Resume is critical for live migration in a data center with external storage to reduce schedules downtime incurred with firmware updates to maintain a secure platform.

Thanks, David Halko
http://netmgt.blogspot.com/

Sent from my iPhone

> On Jun 12, 2019, at 4:01 AM, Jim Klimov <jimklimov at cos.ru> wrote:
> 
>> On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>> 
>> 
>>> On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>>> 
>>> I?d say, anything to encourage people to try, use and join to develop
>> [illumos] is very welcome. Better laptop support will definitely be
>>> bonus.
>> 
>> Betting better graphics support would be higher on the list (yea, the 
>> other 'dropped' project).
>> 
>>  Cheers!
>> 
>>       ---- Randy
>> 
>>> 
>>> Sent from my iPhone
>>> 
>>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>>> 
>>> My gut instinct is that this isn?t that interesting ? most everyone
>> is running illumos in either VMs, or in datacenter
>>> applications where suspend/resume has little if any applicability.
>>> 
>>> While the work itself is probably interesting, and it may enable new
>> applications for illumos, the concern I?d have would be
>>> detraction from other more pressing work, without any clear use cases
>> for it.
>>> 
>>> That said, if someone (you?) wanted to spend cycles on this for
>> personal satisfaction, I hardly see any reason to discourage it,
>>> and I?m fairly certain if the risks of the new code being introduced
>> are small (or well managed by sufficient testing for
>>> example), I can?t see any other reason we would reject a suitably
>> formed RTI.
>>> 
>>> Sent from Mail for Windows 10
>>> 
>>> From: randyf at sibernet.com
>>> Sent: Tuesday, June 11, 2019 11:10 AM
>>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>>> Subject: [developer] suspend/resume in Illumos
>>> 
>>> I have a question for developers here:
>>> 
>>>     How important is suspend/resume for OI/Illumos (including S4)?
>>> 
>>> One of the incomplete projects left behind was S4 (lack of need, and
>> a
>>> 
>>> hard to identify bug stifled it's integration).  It is non-trivial,
>> and
>>> 
>>> needs updated s/r core code (added configuration and significant
>>> 
>>> restructuring, as well as likely assistance from developers
>> knowlegable in
>>> 
>>> other Illumos internals), but if this is an uninteresting feature, it
>> is
>>> 
>>> likey not worth the effort (recent bugs suggest that few if anyone
>> use
>>> 
>>> it); however, it wouldn't be too hard to resurect (though would still
>> take
>>> 
>>> several months of work).
>>> 
>>>    Cheers!
>>> 
>>>         ---- Randy
>>> 
>>> illumos / illumos-developer / see discussions + participants +
>> delivery options Permalink
>> ------------------------------------------
>> illumos: illumos-developer
>> Permalink:
>> https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>> Delivery options:
>> https://illumos.topicbox.com/groups/developer/subscription
> 
> For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.
> 
> My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.
> 
> Jim
> 
> --
> Typos courtesy of K-9 Mail on my Android

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M87936b070d0aa9c1490f0794
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190624/7192fbe4/attachment-0002.html>

From alp at sfedu.ru  Mon Jun 24 15:12:45 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 15:12:45 +0000
Subject: [oi-dev] DDU testing
Message-ID: <AM6PR05MB6198AE59E0359DD5E878CCAFCFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.

I've finished replacing DDU binaries with binaries from DDU 1.2 and rewriting missing parts. 
Result is here: https://github.com/OpenIndiana/ddu/ .
I suggest it can get wider testing.
You can use openindiana/ddu component  from https://github.com/OpenIndiana/oi-userland/pull/5103 to build and test it. 

I'm waiting for test results and reviews.

Changes from current DDU (shipped with OI now).
1) pt_BR localization files removed as msgunfmt couldn't unparse them;
2) Database of third-party drivers was removed (it was obsolete  with it seems one working link from dozen). I suppose nobody volunteers to support it in actual state.
3) I hope finally I've made DDU help behave - now it shows help in user locale, images are not removed.
4) I've regenerated database of existing OI drivers shipped with DDU, updated pci.ids and usb.ids files.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???




From gary_mills at fastmail.fm  Mon Jun 24 15:33:31 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Mon, 24 Jun 2019 10:33:31 -0500
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
Message-ID: <20190624153331.GA28009@mail.messagingengine.com>

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aur?lien Larcher wrote:
> 
>    Congratulations Gary this is great :)
>    If we get to the point that we can setup a build machine this would
>    secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From alp at sfedu.ru  Mon Jun 24 16:02:51 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 16:02:51 +0000
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <20190624153331.GA28009@mail.messagingengine.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>,
	<20190624153331.GA28009@mail.messagingengine.com>
Message-ID: <AM6PR05MB619883D7A53C05872643155DCFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

BTW, while working on DDU I've removed SPARC parts I've encountered ;)
Anyway I had no way (or desire) to test them.
Most interesting is likely dmi_info.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Gary Mills <gary_mills at fastmail.fm>
??????????: 24 ???? 2019 ?. 18:33
????: OpenIndiana Developer mailing list
????: Re: [oi-dev] Toward a SPARC distro of OI

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aur?lien Larcher wrote:
>
>    Congratulations Gary this is great :)
>    If we get to the point that we can setup a build machine this would
>    secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


--
-Gary Mills-            -refurb-                -Winnipeg, Manitoba, Canada-

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

From Tim.Mooney at ndsu.edu  Mon Jun 24 18:24:09 2019
From: Tim.Mooney at ndsu.edu (Tim Mooney)
Date: Mon, 24 Jun 2019 13:24:09 -0500 (CDT)
Subject: [oi-dev] component TODO list for perl components?
In-Reply-To: <AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>
References: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
	<AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>
Message-ID: <alpine.SOC.2.20.1906241317080.14673@dogbert.cc.ndsu.NoDak.edu>

In regard to: Re: [oi-dev] component TODO list for perl components?,...:

> I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/
> some time ago. There are mostly tasks which I'm interested in.
>
> Now I'm looking at removing binary blobs from DDU. Later I'll likely
> look at switching it to Python 3.5.
>
> If you can propose any tasks which you can take (or pehaps, someone
> else), feel  free to update this page. I just don't want it to become a
> list of never-done tasks.

Thanks Alexander, and I understand completely about a list of never-done
tasks.

I'll open a pull request with some proposed updates, and you and others
can comment on whether they're a good idea or not.

Tim

> ________________________________________
> ??: Tim Mooney <Tim.Mooney at ndsu.edu>
> ??????????: 24 ???? 2019 ?. 5:24:33
> ????: oi-dev at openindiana.org
> ????: [oi-dev] component TODO list for perl components?
>
>
> I've been considering packaging the latest stable perl5, 5.30.0, as
> perl-530 and then packaging (and in some cases, updating) the perl
> modules that are part of hipster, but I want to make certain I'm not
> working at cross-purposes to any planned updates for OI and that this
> type of update is actually useful.
>
> There's a checklist of small/easy changes to make when updating a
> component,
>
>        https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md
>
> but is there a list of the bigger packaging tasks, perhaps prioritized by
> need?  Obviously people volunteering their time are going to work on
> things that interest them, benefit them, and are within their ability,
> but at times it would be helpful to know what the most pressing packaging
> needs are.
>
> I'm happy to continue choosing components kind of at random to update, but
> if I have a list of easy (but perhaps tedious) packaging tasks that are
> priorities for update in OI, I would probably attempt some of them as I
> have time, especially if it frees up more time for core contributors to
> work on the more difficult tasks.
>
> Does a list like that exist?  Those types of things tend to go stale fast,
> so I understand if there isn't one.
>
> Tim
> --
> Tim Mooney                                             Tim.Mooney at ndsu.edu
> Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
> Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>

-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

From gary_mills at fastmail.fm  Tue Jun 25 20:47:20 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 25 Jun 2019 15:47:20 -0500
Subject: [oi-dev] Am I stuck?
Message-ID: <20190625204720.GA8601@mail.messagingengine.com>

These are my publishers:

    # pkg publisher                      
    PUBLISHER                   TYPE     STATUS P LOCATION
    oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
    v9os           (non-sticky) origin   online F file:///data/ips/

I just published all of illumos-gate to the oi-userland repository.
There are now two copies of the
consolidation/osnet/osnet-incorporation package.  This is the
installed one:

    # pkg info consolidation/osnet/osnet-incorporation
              Name: consolidation/osnet/osnet-incorporation
           Summary: OS/Net consolidation incorporation
       Description: This incorporation constrains packages from the OS/Net
                    consolidation.
             State: Installed
         Publisher: v9os
           Version: 0.5.11
            Branch: 0.151100
    Packaging Date: Wed Jul 27 07:12:37 2016
              Size: 0.00 B
              FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
    
This is the new one:

    # pkg info -r consolidation/osnet/osnet-incorporation
              Name: consolidation/osnet/osnet-incorporation
           Summary: OS/Net consolidation incorporation
       Description: This incorporation constrains packages from the OS/Net
                    consolidation.
             State: Not installed
         Publisher: oi-userland
           Version: 0.5.11
            Branch: 2018.0.0.0
    Packaging Date: Sun Jun 23 22:35:19 2019
              Size: 0.00 B
              FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z

I expected that `pkg update -nv' would offer to remove the installed
incorporation and replace all of the old illumos-gate packages, over
200 of them, with the new illumos-gate packages.  It didn't do that.
It did report that it would replace ten packages from the v9os
publisher with newer versions from the oi-userland publisher, but this
list didn't include any of the illumos-gate packages.

When I tried to remove the incorporation with pkg, I got this result:

    # pkg uninstall -nv consolidation/osnet/osnet-incorporation
    Creating Plan (Solver setup): -
    pkg uninstall: Unable to remove 'consolidation/osnet/osnet-incorporation at 0.5.11-0.151100' due to the following packages that depend on it:
      SUNWcs at 0.5.11-0.151100
      SUNWcsd at 0.5.11-0.151100
      compatibility/ucb at 0.5.11-0.151100
      developer/astdev at 0.5.11-0.151100
    ...
      system/zones at 0.5.11-0.151100
      system/zones/internal at 0.5.11-0.151100
      text/doctools at 0.5.11-0.151100
      text/locale at 0.5.11-0.151100

Have I run into a dead end, or is there a way out of this dilemma?


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From vab at bb-c.de  Tue Jun 25 21:01:31 2019
From: vab at bb-c.de (Volker A. Brandt)
Date: Tue, 25 Jun 2019 23:01:31 +0200
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190625204720.GA8601@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
Message-ID: <23826.35755.98828.321659@shelob.bb-c.de>

Hi Gary!


> These are my publishers:
> 
>     # pkg publisher                      
>     PUBLISHER                   TYPE     STATUS P LOCATION
>     oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
>     v9os           (non-sticky) origin   online F file:///data/ips/
> 
> I just published all of illumos-gate to the oi-userland repository.
> There are now two copies of the
> consolidation/osnet/osnet-incorporation package.  This is the
> installed one:
> 
>     # pkg info consolidation/osnet/osnet-incorporation
>               Name: consolidation/osnet/osnet-incorporation
>            Summary: OS/Net consolidation incorporation
>        Description: This incorporation constrains packages from the OS/Net
>                     consolidation.
>              State: Installed
>          Publisher: v9os
>            Version: 0.5.11
>             Branch: 0.151100
>     Packaging Date: Wed Jul 27 07:12:37 2016
>               Size: 0.00 B
>               FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
>     
> This is the new one:
> 
>     # pkg info -r consolidation/osnet/osnet-incorporation
>               Name: consolidation/osnet/osnet-incorporation
>            Summary: OS/Net consolidation incorporation
>        Description: This incorporation constrains packages from the OS/Net
>                     consolidation.
>              State: Not installed
>          Publisher: oi-userland
>            Version: 0.5.11
>             Branch: 2018.0.0.0
>     Packaging Date: Sun Jun 23 22:35:19 2019
>               Size: 0.00 B
>               FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z
> 
> I expected that `pkg update -nv' would offer to remove the installed
> incorporation and replace all of the old illumos-gate packages, over
> 200 of them, with the new illumos-gate packages.  It didn't do that.
> It did report that it would replace ten packages from the v9os
> publisher with newer versions from the oi-userland publisher, but this
> list didn't include any of the illumos-gate packages.

So it appears that pkg does not recognize the fact that version
0.5.11-2018.0.0.0:20190623T223519Z is newer than version
0.5.11-0.151100:20160727T071237Z -- correct?

> When I tried to remove the incorporation with pkg, I got this result:
[...]

I don't think that you are supposed to be able to remove the package
altogether.  You should, hovewer, be able to update it.

Do you also have an "entire" package?  If so, what version does it
have?


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt        Consulting and Support for Solaris-based Systems
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"



From gary_mills at fastmail.fm  Wed Jun 26 00:31:04 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 25 Jun 2019 19:31:04 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <23826.35755.98828.321659@shelob.bb-c.de>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
Message-ID: <20190626003104.GA10000@mail.messagingengine.com>

On Tue, Jun 25, 2019 at 11:01:31PM +0200, Volker A. Brandt wrote:
> 
> So it appears that pkg does not recognize the fact that version
> 0.5.11-2018.0.0.0:20190623T223519Z is newer than version
> 0.5.11-0.151100:20160727T071237Z -- correct?

I don't think that that is the problem.  Consider this transcript:

    # pkg update -nv
    ...
    Changed packages:
    ...
    v9os -> oi-userland
      archiver/gnu-tar
        1.28-0.151100 -> 1.29-2018.0.0.0
      compress/bzip2
        1.0.6-0.151100 -> 1.0.6-2018.0.0.3
      compress/gzip
        1.6-0.151100 -> 1.9-2018.0.0.0

The version numbers were the same for the last two packages.

> > When I tried to remove the incorporation with pkg, I got this result:
> [...]
> 
> I don't think that you are supposed to be able to remove the package
> altogether.  You should, hovewer, be able to update it.

That's close to working.  I should be able to make it work.
Here's this one:

    # pkg update -nv pkg://oi-userland/consolidation/osnet/osnet-inco...
    Creating Plan (Solver setup): \
    pkg update: No matching version of consolidation/osnet/osnet-incorporation can be installed:
      Reject:  pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0
      Reason:  No version matching 'incorporate' dependency SUNWcs at 0.5.11-2018.0.0.0 can be installed
        ----------------------------------------
        Reject:  pkg://oi-userland/SUNWcs at 0.5.11-2018.0.0.0
        Reason:  No version matching 'require' dependency system/network/mailwrapper can be installed
          ----------------------------------------
          Reject:  pkg://oi-userland/system/network/mailwrapper at 0.5.11-2018.0.0.0
          Reason:  No version for 'require' dependency on system/mta can be found
          Reject:  pkg://v9os/system/network/mailwrapper at 0.5.11-0.151100
          Reason:  Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation'
          ----------------------------------------
        ----------------------------------------

> Do you also have an "entire" package?  If so, what version does it
> have?

No, I don't have that package.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From naj at snapcon.com  Wed Jun 26 00:28:12 2019
From: naj at snapcon.com (Norm Jacobs)
Date: Tue, 25 Jun 2019 19:28:12 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190625204720.GA8601@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
Message-ID: <1bba6380-a729-e329-a326-0fd1aa7572fb@snapcon.com>

You might look at the 'entire' package and see if it constrains the 
'osnet-incorporation to the older version.? That is most likely the 
cause of your trouble.? You can probably remove the 'entire' package and 
then update.? You might also be able to unlock the incorporation before 
upgrading instead.

 ??? -Norm


On 6/25/19 3:47 PM, Gary Mills wrote:
> These are my publishers:
>
>      # pkg publisher
>      PUBLISHER                   TYPE     STATUS P LOCATION
>      oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
>      v9os           (non-sticky) origin   online F file:///data/ips/
>
> I just published all of illumos-gate to the oi-userland repository.
> There are now two copies of the
> consolidation/osnet/osnet-incorporation package.  This is the
> installed one:
>
>      # pkg info consolidation/osnet/osnet-incorporation
>                Name: consolidation/osnet/osnet-incorporation
>             Summary: OS/Net consolidation incorporation
>         Description: This incorporation constrains packages from the OS/Net
>                      consolidation.
>               State: Installed
>           Publisher: v9os
>             Version: 0.5.11
>              Branch: 0.151100
>      Packaging Date: Wed Jul 27 07:12:37 2016
>                Size: 0.00 B
>                FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
>      
> This is the new one:
>
>      # pkg info -r consolidation/osnet/osnet-incorporation
>                Name: consolidation/osnet/osnet-incorporation
>             Summary: OS/Net consolidation incorporation
>         Description: This incorporation constrains packages from the OS/Net
>                      consolidation.
>               State: Not installed
>           Publisher: oi-userland
>             Version: 0.5.11
>              Branch: 2018.0.0.0
>      Packaging Date: Sun Jun 23 22:35:19 2019
>                Size: 0.00 B
>                FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z
>
> I expected that `pkg update -nv' would offer to remove the installed
> incorporation and replace all of the old illumos-gate packages, over
> 200 of them, with the new illumos-gate packages.  It didn't do that.
> It did report that it would replace ten packages from the v9os
> publisher with newer versions from the oi-userland publisher, but this
> list didn't include any of the illumos-gate packages.
>
> When I tried to remove the incorporation with pkg, I got this result:
>
>      # pkg uninstall -nv consolidation/osnet/osnet-incorporation
>      Creating Plan (Solver setup): -
>      pkg uninstall: Unable to remove 'consolidation/osnet/osnet-incorporation at 0.5.11-0.151100' due to the following packages that depend on it:
>        SUNWcs at 0.5.11-0.151100
>        SUNWcsd at 0.5.11-0.151100
>        compatibility/ucb at 0.5.11-0.151100
>        developer/astdev at 0.5.11-0.151100
>      ...
>        system/zones at 0.5.11-0.151100
>        system/zones/internal at 0.5.11-0.151100
>        text/doctools at 0.5.11-0.151100
>        text/locale at 0.5.11-0.151100
>
> Have I run into a dead end, or is there a way out of this dilemma?
>
>



From richlowe at richlowe.net  Wed Jun 26 00:42:41 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Tue, 25 Jun 2019 20:42:41 -0400
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190626003104.GA10000@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
	<20190626003104.GA10000@mail.messagingengine.com>
Message-ID: <CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>

Reason:  No version for 'require' dependency on system/mta can be found

Seems a leaf failure, does one really not exist?



From gary_mills at fastmail.fm  Wed Jun 26 12:52:41 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Wed, 26 Jun 2019 07:52:41 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
	<20190626003104.GA10000@mail.messagingengine.com>
	<CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>
Message-ID: <20190626125240.GA12540@mail.messagingengine.com>

On Tue, Jun 25, 2019 at 08:42:41PM -0400, Richard Lowe wrote:
> Reason:  No version for 'require' dependency on system/mta can be found
> 
> Seems a leaf failure, does one really not exist?

Indeed, the package system/mta does not exist in either publisher.  I
just published it to oi-userland and installed it.  My next task is to
see if that missing package was preventing the update.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From gordon.w.ross at gmail.com  Fri Jun 28 04:25:37 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 27 Jun 2019 21:25:37 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
Message-ID: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>

Any ideas what I should do to fix this?

root at oi-dev:/home/gwr# pkg -R /mnt image-update -v
Creating Plan (Running solver): /
pkg update: No solution was found to satisfy constraints
No solution found to update to latest available versions.
This may indicate an overly constrained set of packages are installed.

latest incorporations:

  pkg://openindiana.org/consolidation/install/install-incorporation at 0.5.11,5.11-2018.0.0.1041:20190516T142943Z
  pkg://openindiana.org/consolidation/l10n/l10n-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014527Z
  pkg://openindiana.org/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014529Z
  pkg://openindiana.org/consolidation/userland/userland-incorporation at 0.5.11,5.11-2018.0.0.11903:20190627T091450Z

Dependency analysis is unable to determine the cause.
Try specifying expected versions to obtain more detailed error messages.

On Sun, May 12, 2019 at 12:33 AM Alexander Pyhalov via oi-dev
<oi-dev at openindiana.org> wrote:
>
> Sorry, missed dot in
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso link.
>
> ? ?????????,
> ????????? ???????,
> ??????????? ?????? ???????????????????? ??????????????
> ?????????? ?????????????-???????????????? ?????????????? ???
>
>
> ________________________________________
> ??: Alexander Pyhalov via oi-dev <oi-dev at openindiana.org>
> ??????????: 12 ??? 2019 ?. 10:11:57
> ????: OpenIndiana Developer mailing list
> ?????: Alexander Pyhalov
> ????: [oi-dev] OI Hipster 2019.04
>
> Hi.
>
> OI Hipster 2019.04 snapshot is ready.
>
> Images:
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb
>
>
> SHA 256 checksums are available at ${link}.sha256sum
> Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
> https://sks-keyservers.net/pks/lookup?op=get&search=0x3A021AFADBE31887 ).
>
> Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes
>
> Note, we have an issue with Firefox on live image - it can fail to start correctly when launched for the first time in memory-constrained  environment. After being killed and restarted it behaves more sane.
>
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



From gordon.w.ross at gmail.com  Fri Jun 28 04:26:44 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 27 Jun 2019 21:26:44 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
Message-ID: <CAD0Ztp2nrGdb3t2sKjUdR9HNNwdSJ_t=eJs=6UBesB2Uo=+wtA@mail.gmail.com>

I'm guessing people will want to see:

root at oi-dev:/home/gwr# pkg -R /mnt publisher
PUBLISHER                   TYPE     STATUS P LOCATION
openindiana.org              origin   online F
http://pkg.openindiana.org/hipster/
root at oi-dev:/home/gwr# pkg -R /mnt info entire
          Name: entire
       Summary: incorporation to lock all system packages to same build (empty
                package)
   Description: incorporation to lock all system packages to same build (empty
                package)
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
        Branch: 2018.0.0.0
Packaging Date: February 11, 2018 at 01:10:12 PM
          Size: 0.00 B
          FMRI: pkg://openindiana.org/entire at 0.5.11-2018.0.0.0:20180211T131012Z

On Thu, Jun 27, 2019 at 9:25 PM Gordon Ross <gordon.w.ross at gmail.com> wrote:
>
> Any ideas what I should do to fix this?
>
> root at oi-dev:/home/gwr# pkg -R /mnt image-update -v
> Creating Plan (Running solver): /
> pkg update: No solution was found to satisfy constraints
> No solution found to update to latest available versions.
> This may indicate an overly constrained set of packages are installed.
>
> latest incorporations:
>
>   pkg://openindiana.org/consolidation/install/install-incorporation at 0.5.11,5.11-2018.0.0.1041:20190516T142943Z
>   pkg://openindiana.org/consolidation/l10n/l10n-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014527Z
>   pkg://openindiana.org/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014529Z
>   pkg://openindiana.org/consolidation/userland/userland-incorporation at 0.5.11,5.11-2018.0.0.11903:20190627T091450Z
>
> Dependency analysis is unable to determine the cause.
> Try specifying expected versions to obtain more detailed error messages.
>
> On Sun, May 12, 2019 at 12:33 AM Alexander Pyhalov via oi-dev
> <oi-dev at openindiana.org> wrote:
> >
> > Sorry, missed dot in
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso link.
> >
> > ? ?????????,
> > ????????? ???????,
> > ??????????? ?????? ???????????????????? ??????????????
> > ?????????? ?????????????-???????????????? ?????????????? ???
> >
> >
> > ________________________________________
> > ??: Alexander Pyhalov via oi-dev <oi-dev at openindiana.org>
> > ??????????: 12 ??? 2019 ?. 10:11:57
> > ????: OpenIndiana Developer mailing list
> > ?????: Alexander Pyhalov
> > ????: [oi-dev] OI Hipster 2019.04
> >
> > Hi.
> >
> > OI Hipster 2019.04 snapshot is ready.
> >
> > Images:
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb
> >
> >
> > SHA 256 checksums are available at ${link}.sha256sum
> > Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> > The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
> > https://sks-keyservers.net/pks/lookup?op=get&search=0x3A021AFADBE31887 ).
> >
> > Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes
> >
> > Note, we have an issue with Firefox on live image - it can fail to start correctly when launched for the first time in memory-constrained  environment. After being killed and restarted it behaves more sane.
> >
> > Best regards,
> > Alexander Pyhalov,
> > system administrator of Southern Federal University IT department
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev



From richlowe at richlowe.net  Fri Jun 28 05:28:15 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Fri, 28 Jun 2019 01:28:15 -0400
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
Message-ID: <CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>

> Dependency analysis is unable to determine the cause.
> Try specifying expected versions to obtain more detailed error messages.
>

Do what it says there,

Specify the verisons of those 'latest incorporations', and probably
also entire, including the versions.

You may be able to just do 'pkg install -nv entire at latest' but I can
never remember whether only specifying 'entire' does the right thing.



From gordon.w.ross at gmail.com  Fri Jun 28 17:32:25 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Fri, 28 Jun 2019 10:32:25 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
Message-ID: <CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>

OK, but I can't seem to find the latest version of entire.
Can anyone tell me what that should be?

root at oi-dev:/home/gwr# pkg -R /mnt refresh --full
root at oi-dev:/home/gwr# pkg -R /mnt update -nv entire at latest
No updates available for this image.
root at oi-dev:/home/gwr# pkg -R /mnt install -nv entire at latest
No updates necessary for this image.
root at oi-dev:/home/gwr# pkg -R /mnt info entire
          Name: entire
       Summary: incorporation to lock all system packages to same build (empty
                package)
   Description: incorporation to lock all system packages to same build (empty
                package)
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
        Branch: 2018.0.0.0
Packaging Date: February 11, 2018 at 01:10:12 PM
          Size: 0.00 B
          FMRI: pkg://openindiana.org/entire at 0.5.11-2018.0.0.0:20180211T131012Z

On Thu, Jun 27, 2019 at 10:28 PM Richard Lowe <richlowe at richlowe.net> wrote:
>
> > Dependency analysis is unable to determine the cause.
> > Try specifying expected versions to obtain more detailed error messages.
> >
>
> Do what it says there,
>
> Specify the verisons of those 'latest incorporations', and probably
> also entire, including the versions.
>
> You may be able to just do 'pkg install -nv entire at latest' but I can
> never remember whether only specifying 'entire' does the right thing.
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



From richlowe at richlowe.net  Fri Jun 28 17:43:23 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Fri, 28 Jun 2019 13:43:23 -0400
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
	<CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>
Message-ID: <CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?



From alp at sfedu.ru  Sat Jun 29 05:37:26 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Sat, 29 Jun 2019 05:37:26 +0000
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
	<CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>,
	<CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>
Message-ID: <AM6PR05MB6198F5838BDA1D994F326236CFFF0@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.
entire is a package which depends on userland-incorporation. That's all. You are interested in latest osnet-incorporation and userland-incorporation.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Richard Lowe <richlowe at richlowe.net>
??????????: 28 ???? 2019 ?. 20:43
????: OpenIndiana Developer mailing list
????: Re: [oi-dev] OI Hipster 2019.04

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



From grzemba at contac-dt.de  Mon Jun  3 14:44:26 2019
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Mon, 03 Jun 2019 16:44:26 +0200
Subject: [oi-dev] Openindiana on Laptop: touchpad not working
In-Reply-To: <bd3e8f4829c5.5ce65b00@contac-dt.de>
References: <be86e6074ec1.5ce41f99@contac-dt.de>
	<alpine.GSO.2.20.1905211010220.7749@scrappy.simplesystems.org>
	<bd3e8f4829c5.5ce65b00@contac-dt.de>
Message-ID: <bd3d30256aff.5cf54e6a@contac-dt.de>


<signaturebeforequotedtext></signaturebeforequotedtext>
On 23.05.19 08:34, Carsten Grzemba via oi-dev  <oi-dev at openindiana.org> wrote: 
> 
> I compared the Xorg log:
> 
> in the working log the mouse driver is loaded on PS/s mouse on /dev/mouse:
> 
> [ 38.008] (II) LoadModule: "mouse"
> [ 38.008] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> [ 38.012] (II) Module mouse: vendor="X.Org Foundation"
> [ 38.012] compiled for 1.19.5, module version = 1.9.2
> [ 38.012] Module class: X.Org XInput Driver
> [ 38.012] ABI class: X.Org XInput driver, version 24.1
> [ 38.012] (II) Using input driver 'mouse' for 'PS/2 Port for PS/2-style Mice'
> [ 38.012] (**) PS/2 Port for PS/2-style Mice: always reports core events
> [ 38.012] (**) Option "Device" "/dev/mouse"
> [ 38.012] (II) PS/2 Port for PS/2-style Mice: Setting Device option to "/dev/mouse"
> [ 38.014] (==) PS/2 Port for PS/2-style Mice: Protocol: "VUID"
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: always reports core events
> [ 38.014] (**) Option "Device" "/dev/mouse"
> [ 38.014] (==) PS/2 Port for PS/2-style Mice: Emulate3Buttons, Emulate3Timeout: 50
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: ZAxisMapping: buttons 4 and 5
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: Buttons: 9
> [ 38.014] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/isa_1f/i8042_1_60/mouse_1_0_logicaldev_input"
> [ 38.014] (II) XINPUT: Adding extended input device "PS/2 Port for PS/2-style Mice" (type: MOUSE, id 6)
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) keeping acceleration scheme 1
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration profile 0
> [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration factor: 2.000
> [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration threshold: 4
> 
> and the not working on the generic USB device /dev/usb/hid1:
> 
> [ 523.036] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> [ 523.036] (II) Module mouse: vendor="X.Org Foundation"
> [ 523.036] compiled for 1.19.5, module version = 1.9.2
> [ 523.036] Module class: X.Org XInput Driver
> [ 523.037] ABI class: X.Org XInput driver, version 24.1
> [ 523.037] (II) Using input driver 'mouse' for 'mouse'
> [ 523.037] (**) mouse: always reports core events
> [ 523.037] (**) Option "Protocol" "VUID"
> [ 523.037] (**) Option "Device" "/dev/usb/hid1"
> [ 523.037] (**) Option "StreamsModule" "usbms"
> [ 523.039] (**) mouse: Protocol: "VUID"
> [ 523.039] (**) mouse: always reports core events
> [ 523.039] (==) mouse: Emulate3Buttons, Emulate3Timeout: 50
> [ 523.039] (**) mouse: ZAxisMapping: buttons 4 and 5
> [ 523.039] (**) mouse: Buttons: 9
> [ 523.039] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1025_1019_14/device_4/mouse_1_if1_4_logicaldev_input"
> [ 523.039] (II) XINPUT: Adding extended input device "mouse" (type: MOUSE, id 6)
> [ 523.039] (**) mouse: (accel) keeping acceleration scheme 1
> [ 523.039] (**) mouse: (accel) acceleration profile 0
> [ 523.039] (**) mouse: (accel) acceleration factor: 2.000
> [ 523.039] (**) mouse: (accel) acceleration threshold: 4
> [ 523.045] (II) config/hal: Adding input device hotkey
> 
> 
> in both cases is the the touchpad avail and a extern USB mouse connected. the /dev/mouse dev link is in both BE targeted to /devices/pseudo/cons at 0:mouse
> 
> 
Still no luck with the latest hipster on my laptop:

scanpci:
pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1604
?Intel Corporation Broadwell-U Host Bridge -OPI

pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1616
?Intel Corporation HD Graphics 5500

pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x160c
?Intel Corporation Broadwell-U Audio Controller

pci bus 0x0000 cardnum 0x14 function 0x00: vendor 0x8086 device 0x9cb1
?Intel Corporation Wildcat Point-LP USB xHCI Controller

pci bus 0x0000 cardnum 0x16 function 0x00: vendor 0x8086 device 0x9cba
?Intel Corporation Wildcat Point-LP MEI Controller #1

pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x9ca0
?Intel Corporation Wildcat Point-LP High Definition Audio Controller

pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x9c90
?Intel Corporation Wildcat Point-LP PCI Express Root Port #1

pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device 0x9c94
?Intel Corporation Wildcat Point-LP PCI Express Root Port #3

pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
?Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device 0x9c96
?Intel Corporation Wildcat Point-LP PCI Express Root Port #4

pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x8086 device 0x095a
?Intel Corporation Wireless 7265

pci bus 0x0000 cardnum 0x1c function 0x04: vendor 0x8086 device 0x9c98
?Intel Corporation Wildcat Point-LP PCI Express Root Port #5

pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10de device 0x1299
?NVIDIA Corporation GK208BM [GeForce 920M]

pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x9ca6
?Intel Corporation Wildcat Point-LP USB EHCI Controller

pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x9cc3
?Intel Corporation Wildcat Point-LP LPC ControllerX.Org X Server 1.19.6

pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x9c83
?Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode]

pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x9ca2
?Intel Corporation Wildcat Point-LP SMBus Controller

I boot from latest USB image there X session dont start, only the mouse pointer is seen. If I kill the Xorg via SSH I get no text console.
So I reboot in text console and tried to test Xorg configuration with my current working settings (of Xorg 1.19.6 vesa for the Intel, Nvidia was never usable with the old i915 driver). There I get only a black screen and after kill Xorg no text console again. 
Activating vtdaemon and vt-console also not working.

What is the change here, so that Xorg 1.19.7 isn't working anymore? In Xorg.0.log I dont see any errors.

Thanks



























 <signatureafterquotedtext></signatureafterquotedtext>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190603/0736b268/attachment-0003.html>

From grzemba at contac-dt.de  Tue Jun  4 08:27:09 2019
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Tue, 04 Jun 2019 10:27:09 +0200
Subject: [oi-dev] Openindiana on Laptop: touchpad not working
In-Reply-To: <bd3d30256aff.5cf54e6a@contac-dt.de>
References: <be86e6074ec1.5ce41f99@contac-dt.de>
	<alpine.GSO.2.20.1905211010220.7749@scrappy.simplesystems.org>
	<bd3e8f4829c5.5ce65b00@contac-dt.de>
	<bd3d30256aff.5cf54e6a@contac-dt.de>
Message-ID: <bf5f8a435076.5cf6477d@contac-dt.de>


<signaturebeforequotedtext></signaturebeforequotedtext>
On 03.06.19 16:44, "Carsten Grzemba"  <grzemba at contac-dt.de> wrote: 
> 
> 
> 
> On 23.05.19 08:34, Carsten Grzemba via oi-dev  <oi-dev at openindiana.org> wrote: 
> > 
> > I compared the Xorg log:
> > 
> > in the working log the mouse driver is loaded on PS/s mouse on /dev/mouse:
> > 
> > [ 38.008] (II) LoadModule: "mouse"
> > [ 38.008] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> > [ 38.012] (II) Module mouse: vendor="X.Org Foundation"
> > [ 38.012] compiled for 1.19.5, module version = 1.9.2
> > [ 38.012] Module class: X.Org XInput Driver
> > [ 38.012] ABI class: X.Org XInput driver, version 24.1
> > [ 38.012] (II) Using input driver 'mouse' for 'PS/2 Port for PS/2-style Mice'
> > [ 38.012] (**) PS/2 Port for PS/2-style Mice: always reports core events
> > [ 38.012] (**) Option "Device" "/dev/mouse"
> > [ 38.012] (II) PS/2 Port for PS/2-style Mice: Setting Device option to "/dev/mouse"
> > [ 38.014] (==) PS/2 Port for PS/2-style Mice: Protocol: "VUID"
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: always reports core events
> > [ 38.014] (**) Option "Device" "/dev/mouse"
> > [ 38.014] (==) PS/2 Port for PS/2-style Mice: Emulate3Buttons, Emulate3Timeout: 50
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: ZAxisMapping: buttons 4 and 5
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: Buttons: 9
> > [ 38.014] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/isa_1f/i8042_1_60/mouse_1_0_logicaldev_input"
> > [ 38.014] (II) XINPUT: Adding extended input device "PS/2 Port for PS/2-style Mice" (type: MOUSE, id 6)
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) keeping acceleration scheme 1
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration profile 0
> > [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration factor: 2.000
> > [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration threshold: 4
> > 
> > and the not working on the generic USB device /dev/usb/hid1:
> > 
> > [ 523.036] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> > [ 523.036] (II) Module mouse: vendor="X.Org Foundation"
> > [ 523.036] compiled for 1.19.5, module version = 1.9.2
> > [ 523.036] Module class: X.Org XInput Driver
> > [ 523.037] ABI class: X.Org XInput driver, version 24.1
> > [ 523.037] (II) Using input driver 'mouse' for 'mouse'
> > [ 523.037] (**) mouse: always reports core events
> > [ 523.037] (**) Option "Protocol" "VUID"
> > [ 523.037] (**) Option "Device" "/dev/usb/hid1"
> > [ 523.037] (**) Option "StreamsModule" "usbms"
> > [ 523.039] (**) mouse: Protocol: "VUID"
> > [ 523.039] (**) mouse: always reports core events
> > [ 523.039] (==) mouse: Emulate3Buttons, Emulate3Timeout: 50
> > [ 523.039] (**) mouse: ZAxisMapping: buttons 4 and 5
> > [ 523.039] (**) mouse: Buttons: 9
> > [ 523.039] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1025_1019_14/device_4/mouse_1_if1_4_logicaldev_input"
> > [ 523.039] (II) XINPUT: Adding extended input device "mouse" (type: MOUSE, id 6)
> > [ 523.039] (**) mouse: (accel) keeping acceleration scheme 1
> > [ 523.039] (**) mouse: (accel) acceleration profile 0
> > [ 523.039] (**) mouse: (accel) acceleration factor: 2.000
> > [ 523.039] (**) mouse: (accel) acceleration threshold: 4
> > [ 523.045] (II) config/hal: Adding input device hotkey
> > 
> > 
> > in both cases is the the touchpad avail and a extern USB mouse connected. the /dev/mouse dev link is in both BE targeted to /devices/pseudo/cons at 0:mouse
> > 
> > 
> Still no luck with the latest hipster on my laptop:
> 
> scanpci:
> pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1604
> ?Intel Corporation Broadwell-U Host Bridge -OPI
> 
> pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1616
> ?Intel Corporation HD Graphics 5500
> 
> pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x160c
> ?Intel Corporation Broadwell-U Audio Controller
> 
> pci bus 0x0000 cardnum 0x14 function 0x00: vendor 0x8086 device 0x9cb1
> ?Intel Corporation Wildcat Point-LP USB xHCI Controller
> 
> pci bus 0x0000 cardnum 0x16 function 0x00: vendor 0x8086 device 0x9cba
> ?Intel Corporation Wildcat Point-LP MEI Controller #1
> 
> pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x9ca0
> ?Intel Corporation Wildcat Point-LP High Definition Audio Controller
> 
> pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x9c90
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #1
> 
> pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device 0x9c94
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #3
> 
> pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
> ?Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
> 
> pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device 0x9c96
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #4
> 
> pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x8086 device 0x095a
> ?Intel Corporation Wireless 7265
> 
> pci bus 0x0000 cardnum 0x1c function 0x04: vendor 0x8086 device 0x9c98
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #5
> 
> pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10de device 0x1299
> ?NVIDIA Corporation GK208BM [GeForce 920M]
> 
> pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x9ca6
> ?Intel Corporation Wildcat Point-LP USB EHCI Controller
> 
> pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x9cc3
> ?Intel Corporation Wildcat Point-LP LPC ControllerX.Org X Server 1.19.6
> 
> pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x9c83
> ?Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode]
> 
> pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x9ca2
> ?Intel Corporation Wildcat Point-LP SMBus Controller
> 
> I boot from latest USB image there X session dont start, only the mouse pointer is seen. If I kill the Xorg via SSH I get no text console.
> So I reboot in text console and tried to test Xorg configuration with my current working settings (of Xorg 1.19.6 vesa for the Intel, Nvidia was never usable with the old i915 driver). There I get only a black screen and after kill Xorg no text console again. 
> Activating vtdaemon and vt-console also not working.
> 
> What is the change here, so that Xorg 1.19.7 isn't working anymore? In Xorg.0.log I dont see any errors.
> 
> Thanks 
> 
Because the Xorg config is not changed and the touchpad not working on newer hipster, it looks for me like the touchpad is disabled what can normaly toggled by Fn F7.
But Fn keys do not work at all on newer hipster. Something to do with ACPI ?

 <signatureafterquotedtext></signatureafterquotedtext>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190604/1b76e6e2/attachment-0003.html>

From randyf at sibernet.com  Tue Jun 11 18:07:21 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 11:07:21 -0700 (PDT)
Subject: [oi-dev] suspend/resume in Illumos
Message-ID: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>



I have a question for developers here:

    How important is suspend/resume for OI/Illumos (including S4)?


One of the incomplete projects left behind was S4 (lack of need, and a 
hard to identify bug stifled it's integration).  It is non-trivial, and 
needs updated s/r core code (added configuration and significant 
restructuring, as well as likely assistance from developers knowlegable in 
other Illumos internals), but if this is an uninteresting feature, it is 
likey not worth the effort (recent bugs suggest that few if anyone use 
it); however, it wouldn't be too hard to resurect (though would still take 
several months of work).


   Cheers!

 	---- Randy



From gary_mills at fastmail.fm  Tue Jun 11 18:10:11 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 11 Jun 2019 13:10:11 -0500
Subject: [oi-dev] Toward a SPARC distro of OI
Message-ID: <20190611181011.GA18869@mail.messagingengine.com>

I'm part way through this long project now.  I began with v9os
installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
packages.  I've been building IPS packages from oi-userland source.
This process has gotten easier now that all the build tools I need are
in IPS packages.  I've been replacing v9os packages with oi-userland
packages.  My goal is to replace all of them, and finally to produce a
text ISO and package repository for SPARC that's entirely based on
oi-userland.

So far, I've built and packaged versions 5, 6, and 7 of the gcc
compiler.  The commands for IPS packages are all packaged for python
2.7.  My system now has 106 packages installed from oi-userland,
versus 343 packages from v9os.  Most of the oi-userland products
required very few or no changes to build and package for SPARC.

For perl, I've removed the 5.16.1 version from v9os and installed
versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
packaged for 5.22.  Python libraries are all packaged for 2.7.

I'm submitting this message to the mailing list mostly as a progress
report.  I would, of course, appreciate a bit of help with this
project.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From garrett at damore.org  Tue Jun 11 19:58:08 2019
From: garrett at damore.org (Garrett D'Amore)
Date: Tue, 11 Jun 2019 12:58:08 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
Message-ID: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>

My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where suspend/resume has little if any applicability.

While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from other more pressing work, without any clear use cases for it.

That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any other reason we would reject a suitably formed RTI.

Sent from Mail for Windows 10

From: randyf at sibernet.com
Sent: Tuesday, June 11, 2019 11:10 AM
To: oi-dev at openindiana.org; developer at lists.illumos.org
Subject: [developer] suspend/resume in Illumos



I have a question for developers here:

    How important is suspend/resume for OI/Illumos (including S4)?


One of the incomplete projects left behind was S4 (lack of need, and a 
hard to identify bug stifled it's integration).  It is non-trivial, and 
needs updated s/r core code (added configuration and significant 
restructuring, as well as likely assistance from developers knowlegable in 
other Illumos internals), but if this is an uninteresting feature, it is 
likey not worth the effort (recent bugs suggest that few if anyone use 
it); however, it wouldn't be too hard to resurect (though would still take 
several months of work).


   Cheers!

        ---- Randy

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190611/347dae6d/attachment-0003.html>

From tsoome at me.com  Tue Jun 11 20:31:18 2019
From: tsoome at me.com (Toomas Soome)
Date: Tue, 11 Jun 2019 23:31:18 +0300
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
Message-ID: <DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>

I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be bonus.

Sent from my iPhone

> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
> 
> My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where suspend/resume has little if any applicability.
>  
> While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from other more pressing work, without any clear use cases for it.
>  
> That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any other reason we would reject a suitably formed RTI.
>  
> Sent from Mail for Windows 10
>  
> From: randyf at sibernet.com
> Sent: Tuesday, June 11, 2019 11:10 AM
> To: oi-dev at openindiana.org; developer at lists.illumos.org
> Subject: [developer] suspend/resume in Illumos
>  
>  
>  
> I have a question for developers here:
>  
>     How important is suspend/resume for OI/Illumos (including S4)?
>  
>  
> One of the incomplete projects left behind was S4 (lack of need, and a
> hard to identify bug stifled it's integration).  It is non-trivial, and
> needs updated s/r core code (added configuration and significant
> restructuring, as well as likely assistance from developers knowlegable in
> other Illumos internals), but if this is an uninteresting feature, it is
> likey not worth the effort (recent bugs suggest that few if anyone use
> it); however, it wouldn't be too hard to resurect (though would still take
> several months of work).
>  
>  
>    Cheers!
>  
>         ---- Randy
>  
> ------------------------------------------
> illumos: illumos-developer
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
>  
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190611/1b0c9592/attachment-0003.html>

From randyf at sibernet.com  Tue Jun 11 21:28:34 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 14:28:34 -0700 (PDT)
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
Message-ID: <alpine.SOC.2.00.1906111420090.15467@sibernet.com>



On Tue, 11 Jun 2019, Garrett D'Amore wrote:

> 
> My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where
> suspend/resume has little if any applicability.
> 
> ?
> 
> While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from
> other more pressing work, without any clear use cases for it.
>

   I should point out that s/r isn't just for laptop bare-metal.  It allows 
for a running instance of an OS to be frozen in an orderly manner (rather 
than a VM just pausing a guest, the guest suspends first).  S4 opens a 
different world of allowing said image to be more easily migrated, or 
(since it has roots in CPR) opens quick-boot images (imagine getting an 
OS fully booted in under 10 seconds).

> ?
> 
> That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m
> fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any
> other reason we would reject a suitably formed RTI.
>

   Doubt I'll fully drop it, but without sufficient interest, it's is 
unlikely I'll give it much priority (certainly, my other 'dropped' project 
should have a higer priority).

   Cheers!

 	---- Randy

> ?
> 
> Sent from Mail for Windows 10
> 
> ?
> 
> From: randyf at sibernet.com
> Sent: Tuesday, June 11, 2019 11:10 AM
> To: oi-dev at openindiana.org; developer at lists.illumos.org
> Subject: [developer] suspend/resume in Illumos
> 
> ?
> 
> ?
> 
> ?
> 
> I have a question for developers here:
> 
> ?
> 
> ??? How important is suspend/resume for OI/Illumos (including S4)?
> 
> ?
> 
> ?
> 
> One of the incomplete projects left behind was S4 (lack of need, and a
> 
> hard to identify bug stifled it's integration).? It is non-trivial, and
> 
> needs updated s/r core code (added configuration and significant
> 
> restructuring, as well as likely assistance from developers knowlegable in
> 
> other Illumos internals), but if this is an uninteresting feature, it is
> 
> likey not worth the effort (recent bugs suggest that few if anyone use
> 
> it); however, it wouldn't be too hard to resurect (though would still take
> 
> several months of work).
> 
> ?
> 
> ?
> 
> ?? Cheers!
> 
> ?
> 
> ??????? ---- Randy
> 
> ?
> 
> ------------------------------------------
> 
> illumos: illumos-developer
> 
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> 
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
> 
> ?
> 
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
> 
>

From randyf at sibernet.com  Tue Jun 11 21:29:23 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 14:29:23 -0700 (PDT)
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
Message-ID: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>



On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:

> I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be
> bonus.

   Betting better graphics support would be higher on the list (yea, the 
other 'dropped' project).

   Cheers!

 	---- Randy

> 
> Sent from my iPhone
> 
> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>
>       My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter
>       applications where suspend/resume has little if any applicability.
>
>       ?
>
>       While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be
>       detraction from other more pressing work, without any clear use cases for it.
>
>       ?
>
>       That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it,
>       and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for
>       example), I can?t see any other reason we would reject a suitably formed RTI.
>
>       ?
>
>       Sent from Mail for Windows 10
>
>       ?
>
>       From: randyf at sibernet.com
>       Sent: Tuesday, June 11, 2019 11:10 AM
>       To: oi-dev at openindiana.org; developer at lists.illumos.org
>       Subject: [developer] suspend/resume in Illumos
> 
> ?
> 
> ?
> 
> ?
> 
> I have a question for developers here:
> 
> ?
> 
> ??? How important is suspend/resume for OI/Illumos (including S4)?
> 
> ?
> 
> ?
> 
> One of the incomplete projects left behind was S4 (lack of need, and a
> 
> hard to identify bug stifled it's integration).? It is non-trivial, and
> 
> needs updated s/r core code (added configuration and significant
> 
> restructuring, as well as likely assistance from developers knowlegable in
> 
> other Illumos internals), but if this is an uninteresting feature, it is
> 
> likey not worth the effort (recent bugs suggest that few if anyone use
> 
> it); however, it wouldn't be too hard to resurect (though would still take
> 
> several months of work).
> 
> ?
> 
> ?
> 
> ?? Cheers!
> 
> ?
> 
> ??????? ---- Randy
> 
> ?
> 
> ------------------------------------------
> 
> illumos: illumos-developer
> 
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> 
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
> 
> ?
> 
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
> 
>

From josh at sysmgr.org  Tue Jun 11 21:32:28 2019
From: josh at sysmgr.org (Joshua M. Clulow)
Date: Tue, 11 Jun 2019 14:32:28 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <CAEwA5nJHmR+Md2hh2HGj5770+-x=uanePOwqTrYRBe4W0GxPoQ@mail.gmail.com>

On Tue, 11 Jun 2019 at 14:29, <randyf at sibernet.com> wrote:
> On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
> > I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be
> > bonus.
>
>    Betting better graphics support would be higher on the list (yea, the
> other 'dropped' project).

I think there are a fair few people who would appreciate some serious
elbow grease being applied to the graphics bits!


Cheers.

-- 
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org



From jimklimov at cos.ru  Wed Jun 12 08:01:25 2019
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 12 Jun 2019 08:01:25 +0000
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>

On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>
>
>On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>
>> I?d say, anything to encourage people to try, use and join to develop
>[illumos] is very welcome. Better laptop support will definitely be
>> bonus.
>
> Betting better graphics support would be higher on the list (yea, the 
>other 'dropped' project).
>
>   Cheers!
>
>        ---- Randy
>
>> 
>> Sent from my iPhone
>> 
>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> My gut instinct is that this isn?t that interesting ? most everyone
>is running illumos in either VMs, or in datacenter
>> applications where suspend/resume has little if any applicability.
>> 
>> While the work itself is probably interesting, and it may enable new
>applications for illumos, the concern I?d have would be
>> detraction from other more pressing work, without any clear use cases
>for it.
>> 
>> That said, if someone (you?) wanted to spend cycles on this for
>personal satisfaction, I hardly see any reason to discourage it,
>> and I?m fairly certain if the risks of the new code being introduced
>are small (or well managed by sufficient testing for
>> example), I can?t see any other reason we would reject a suitably
>formed RTI.
>> 
>> Sent from Mail for Windows 10
>> 
>> From: randyf at sibernet.com
>> Sent: Tuesday, June 11, 2019 11:10 AM
>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>> Subject: [developer] suspend/resume in Illumos
>> 
>> I have a question for developers here:
>> 
>> ??? How important is suspend/resume for OI/Illumos (including S4)?
>> 
>> One of the incomplete projects left behind was S4 (lack of need, and
>a
>> 
>> hard to identify bug stifled it's integration).? It is non-trivial,
>and
>> 
>> needs updated s/r core code (added configuration and significant
>> 
>> restructuring, as well as likely assistance from developers
>knowlegable in
>> 
>> other Illumos internals), but if this is an uninteresting feature, it
>is
>> 
>> likey not worth the effort (recent bugs suggest that few if anyone
>use
>> 
>> it); however, it wouldn't be too hard to resurect (though would still
>take
>> 
>> several months of work).
>> 
>> ?? Cheers!
>> 
>> ??????? ---- Randy
>> 
>> illumos / illumos-developer / see discussions + participants +
>delivery options Permalink
>> 
>------------------------------------------
>illumos: illumos-developer
>Permalink:
>https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>Delivery options:
>https://illumos.topicbox.com/groups/developer/subscription

For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.

My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.

Jim

--
Typos courtesy of K-9 Mail on my Android



From jimklimov at cos.ru  Wed Jun 12 08:01:25 2019
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 12 Jun 2019 08:01:25 +0000
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>

On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>
>
>On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>
>> I?d say, anything to encourage people to try, use and join to develop
>[illumos] is very welcome. Better laptop support will definitely be
>> bonus.
>
> Betting better graphics support would be higher on the list (yea, the 
>other 'dropped' project).
>
>   Cheers!
>
>        ---- Randy
>
>> 
>> Sent from my iPhone
>> 
>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> My gut instinct is that this isn?t that interesting ? most everyone
>is running illumos in either VMs, or in datacenter
>> applications where suspend/resume has little if any applicability.
>> 
>> While the work itself is probably interesting, and it may enable new
>applications for illumos, the concern I?d have would be
>> detraction from other more pressing work, without any clear use cases
>for it.
>> 
>> That said, if someone (you?) wanted to spend cycles on this for
>personal satisfaction, I hardly see any reason to discourage it,
>> and I?m fairly certain if the risks of the new code being introduced
>are small (or well managed by sufficient testing for
>> example), I can?t see any other reason we would reject a suitably
>formed RTI.
>> 
>> Sent from Mail for Windows 10
>> 
>> From: randyf at sibernet.com
>> Sent: Tuesday, June 11, 2019 11:10 AM
>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>> Subject: [developer] suspend/resume in Illumos
>> 
>> I have a question for developers here:
>> 
>> ??? How important is suspend/resume for OI/Illumos (including S4)?
>> 
>> One of the incomplete projects left behind was S4 (lack of need, and
>a
>> 
>> hard to identify bug stifled it's integration).? It is non-trivial,
>and
>> 
>> needs updated s/r core code (added configuration and significant
>> 
>> restructuring, as well as likely assistance from developers
>knowlegable in
>> 
>> other Illumos internals), but if this is an uninteresting feature, it
>is
>> 
>> likey not worth the effort (recent bugs suggest that few if anyone
>use
>> 
>> it); however, it wouldn't be too hard to resurect (though would still
>take
>> 
>> several months of work).
>> 
>> ?? Cheers!
>> 
>> ??????? ---- Randy
>> 
>> illumos / illumos-developer / see discussions + participants +
>delivery options Permalink
>> 
>------------------------------------------
>illumos: illumos-developer
>Permalink:
>https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>Delivery options:
>https://illumos.topicbox.com/groups/developer/subscription

For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.

My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.

Jim

--
Typos courtesy of K-9 Mail on my Android



From aurelien.larcher at gmail.com  Mon Jun 17 11:26:59 2019
From: aurelien.larcher at gmail.com (=?UTF-8?Q?Aur=C3=A9lien_Larcher?=)
Date: Mon, 17 Jun 2019 13:26:59 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <20190611181011.GA18869@mail.messagingengine.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
Message-ID: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>

On Mon, Jun 17, 2019 at 11:59 AM Gary Mills <gary_mills at fastmail.fm> wrote:

> I'm part way through this long project now.  I began with v9os
> installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
> packages.  I've been building IPS packages from oi-userland source.
> This process has gotten easier now that all the build tools I need are
> in IPS packages.  I've been replacing v9os packages with oi-userland
> packages.  My goal is to replace all of them, and finally to produce a
> text ISO and package repository for SPARC that's entirely based on
> oi-userland.
>
> So far, I've built and packaged versions 5, 6, and 7 of the gcc
> compiler.  The commands for IPS packages are all packaged for python
> 2.7.  My system now has 106 packages installed from oi-userland,
> versus 343 packages from v9os.  Most of the oi-userland products
> required very few or no changes to build and package for SPARC.
>
> For perl, I've removed the 5.16.1 version from v9os and installed
> versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
> removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
> packaged for 5.22.  Python libraries are all packaged for 2.7.
>
> I'm submitting this message to the mailing list mostly as a progress
> report.  I would, of course, appreciate a bit of help with this
> project.
>

Congratulations Gary this is great :)
If we get to the point that we can setup a build machine this would secure
your work.
Kind regards

Aur?lien



>
>
> --
> -Gary Mills-            -refurb-                -Winnipeg, Manitoba,
> Canada-
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


-- 
---
Praise the Caffeine embeddings
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190617/a222a8e2/attachment-0003.html>

From toasterson at gmail.com  Mon Jun 17 15:33:53 2019
From: toasterson at gmail.com (=?UTF-8?Q?Till_Wegm=c3=bcller?=)
Date: Mon, 17 Jun 2019 17:33:53 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
Message-ID: <63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com>

Hi Gary

Thank you so much for this Work. I don't personaly use sparc but ir is
good to see people doing this kinds of projects.

Do you know about Agnar's Project to get OI building on SPARC? I can't
remember if I ever pointed you towards him and his OI on Sparc work. His
angle was to jump from an existing OI distro to current packages and
later looking in V9OS.

Greetings
Till

On 17.06.19 13:26, Aur?lien Larcher wrote:
> 
> 
> On Mon, Jun 17, 2019 at 11:59 AM Gary Mills <gary_mills at fastmail.fm
> <mailto:gary_mills at fastmail.fm>> wrote:
> 
>     I'm part way through this long project now.? I began with v9os
>     installed on a Sun T2000.? v9os is a SPARC distribution that uses IPS
>     packages.? I've been building IPS packages from oi-userland source.
>     This process has gotten easier now that all the build tools I need are
>     in IPS packages.? I've been replacing v9os packages with oi-userland
>     packages.? My goal is to replace all of them, and finally to produce a
>     text ISO and package repository for SPARC that's entirely based on
>     oi-userland.
> 
>     So far, I've built and packaged versions 5, 6, and 7 of the gcc
>     compiler.? The commands for IPS packages are all packaged for python
>     2.7.? My system now has 106 packages installed from oi-userland,
>     versus 343 packages from v9os.? Most of the oi-userland products
>     required very few or no changes to build and package for SPARC.
> 
>     For perl, I've removed the 5.16.1 version from v9os and installed
>     versions 5.22 and 5.24 from oi-userland.? Likewise, for python, I've
>     removed 2.6 and installed 2.7 and 3.4.? Perl libraries are all
>     packaged for 5.22.? Python libraries are all packaged for 2.7.
> 
>     I'm submitting this message to the mailing list mostly as a progress
>     report.? I would, of course, appreciate a bit of help with this
>     project.
> 
> 
> Congratulations Gary this is great :)
> If we get to the point that we can setup a build machine this would
> secure your work.
> Kind regards
> 
> Aur?lien
> 
> ?
> 
> 
> 
>     -- 
>     -Gary Mills-? ? ? ? ? ? -refurb-? ? ? ? ? ? ? ? -Winnipeg, Manitoba,
>     Canada-
> 
>     _______________________________________________
>     oi-dev mailing list
>     oi-dev at openindiana.org <mailto:oi-dev at openindiana.org>
>     https://openindiana.org/mailman/listinfo/oi-dev
> 
> 
> 
> -- 
> ---
> Praise the Caffeine embeddings
> 
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
> 



From olbohlen at eenfach.de  Tue Jun 18 19:25:07 2019
From: olbohlen at eenfach.de (Olaf Bohlen)
Date: Tue, 18 Jun 2019 21:25:07 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com> ("Till
	=?utf-8?Q?Wegm=C3=BCller=22's?= message of "Mon, 17 Jun 2019 17:33:53
	+0200")
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
	<63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com>
Message-ID: <x6pnnavgq4.fsf@eenfach.de>

Till Wegm?ller <toasterson at gmail.com> writes:

Hi Till,
hi Gary,

> Do you know about Agnar's Project to get OI building on SPARC? I can't
> remember if I ever pointed you towards him and his OI on Sparc work. His
> angle was to jump from an existing OI distro to current packages and
> later looking in V9OS.

First: Gary, this is phantastic news, congrats to it! I'm looking
forward to hear more from you.

Second: Till, yes Gary and I have been in contact but since I have
not enough time, my progress is probably somewhat slower. I also
have newer bits running, but my approach is - as you mentioned -
doing bootstrapping a system to be able to build recent bits in
the correct way.

I'd be happy to hear once someone has built a bootable OI media
for sparc and would take up of these also.

Best regards,

-- 
      ~       Olaf Bohlen - olbohlen at eenfach.de
      |~~     Het
     /|  \    Bruine
 ___/_|___\   Leven
   \__n____/# DGCN2



From Tim.Mooney at ndsu.edu  Mon Jun 24 02:24:33 2019
From: Tim.Mooney at ndsu.edu (Tim Mooney)
Date: Sun, 23 Jun 2019 21:24:33 -0500 (CDT)
Subject: [oi-dev] component TODO list for perl components?
Message-ID: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,

 	https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164



From alp at sfedu.ru  Mon Jun 24 06:05:50 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 06:05:50 +0000
Subject: [oi-dev] component TODO list for perl components?
In-Reply-To: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
References: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
Message-ID: <AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.

I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/ some time ago. There are mostly tasks which I'm interested in.

Now I'm looking at removing binary blobs from DDU. Later I'll likely look at switching it to Python 3.5.

If you can propose any tasks which you can take (or pehaps, someone else), feel  free to update this page. I just don't want it to become a list of never-done tasks.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Tim Mooney <Tim.Mooney at ndsu.edu>
??????????: 24 ???? 2019 ?. 5:24:33
????: oi-dev at openindiana.org
????: [oi-dev] component TODO list for perl components?


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,

        https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
--
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



From garrett at damore.org  Mon Jun 24 14:42:34 2019
From: garrett at damore.org (Garrett D'Amore)
Date: Mon, 24 Jun 2019 07:42:34 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <DE25905A-0071-4339-B00A-9EB1D62CC5AB@gmail.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
	<699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>
	<DE25905A-0071-4339-B00A-9EB1D62CC5AB@gmail.com>
Message-ID: <5d10e157.1c69fb81.48b1c.91f9@mx.google.com>

That?s only true if you?re running on  a hypervisor that uses suspend / resume for live migration.  I?m not sure how widespread running illumos on VMware is ? the absence of suspend/resume support means that nobody is benefiting from this particular capability today (at least with illumos).

Sent from Mail for Windows 10

From: DavidHalko
Sent: Monday, June 24, 2019 5:18 AM
To: illumos-developer
Cc: randyf at sibernet.com; oi-dev at openindiana.org
Subject: Re: [developer] suspend/resume in Illumos

Suspend and Resume is critical for live migration in a data center with external storage to reduce schedules downtime incurred with firmware updates to maintain a secure platform.

Thanks, David Halko
http://netmgt.blogspot.com/

Sent from my iPhone

> On Jun 12, 2019, at 4:01 AM, Jim Klimov <jimklimov at cos.ru> wrote:
> 
>> On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>> 
>> 
>>> On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>>> 
>>> I?d say, anything to encourage people to try, use and join to develop
>> [illumos] is very welcome. Better laptop support will definitely be
>>> bonus.
>> 
>> Betting better graphics support would be higher on the list (yea, the 
>> other 'dropped' project).
>> 
>>  Cheers!
>> 
>>       ---- Randy
>> 
>>> 
>>> Sent from my iPhone
>>> 
>>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>>> 
>>> My gut instinct is that this isn?t that interesting ? most everyone
>> is running illumos in either VMs, or in datacenter
>>> applications where suspend/resume has little if any applicability.
>>> 
>>> While the work itself is probably interesting, and it may enable new
>> applications for illumos, the concern I?d have would be
>>> detraction from other more pressing work, without any clear use cases
>> for it.
>>> 
>>> That said, if someone (you?) wanted to spend cycles on this for
>> personal satisfaction, I hardly see any reason to discourage it,
>>> and I?m fairly certain if the risks of the new code being introduced
>> are small (or well managed by sufficient testing for
>>> example), I can?t see any other reason we would reject a suitably
>> formed RTI.
>>> 
>>> Sent from Mail for Windows 10
>>> 
>>> From: randyf at sibernet.com
>>> Sent: Tuesday, June 11, 2019 11:10 AM
>>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>>> Subject: [developer] suspend/resume in Illumos
>>> 
>>> I have a question for developers here:
>>> 
>>>     How important is suspend/resume for OI/Illumos (including S4)?
>>> 
>>> One of the incomplete projects left behind was S4 (lack of need, and
>> a
>>> 
>>> hard to identify bug stifled it's integration).  It is non-trivial,
>> and
>>> 
>>> needs updated s/r core code (added configuration and significant
>>> 
>>> restructuring, as well as likely assistance from developers
>> knowlegable in
>>> 
>>> other Illumos internals), but if this is an uninteresting feature, it
>> is
>>> 
>>> likey not worth the effort (recent bugs suggest that few if anyone
>> use
>>> 
>>> it); however, it wouldn't be too hard to resurect (though would still
>> take
>>> 
>>> several months of work).
>>> 
>>>    Cheers!
>>> 
>>>         ---- Randy
>>> 
>>> illumos / illumos-developer / see discussions + participants +
>> delivery options Permalink
>> ------------------------------------------
>> illumos: illumos-developer
>> Permalink:
>> https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>> Delivery options:
>> https://illumos.topicbox.com/groups/developer/subscription
> 
> For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.
> 
> My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.
> 
> Jim
> 
> --
> Typos courtesy of K-9 Mail on my Android

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M87936b070d0aa9c1490f0794
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190624/7192fbe4/attachment-0003.html>

From alp at sfedu.ru  Mon Jun 24 15:12:45 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 15:12:45 +0000
Subject: [oi-dev] DDU testing
Message-ID: <AM6PR05MB6198AE59E0359DD5E878CCAFCFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.

I've finished replacing DDU binaries with binaries from DDU 1.2 and rewriting missing parts. 
Result is here: https://github.com/OpenIndiana/ddu/ .
I suggest it can get wider testing.
You can use openindiana/ddu component  from https://github.com/OpenIndiana/oi-userland/pull/5103 to build and test it. 

I'm waiting for test results and reviews.

Changes from current DDU (shipped with OI now).
1) pt_BR localization files removed as msgunfmt couldn't unparse them;
2) Database of third-party drivers was removed (it was obsolete  with it seems one working link from dozen). I suppose nobody volunteers to support it in actual state.
3) I hope finally I've made DDU help behave - now it shows help in user locale, images are not removed.
4) I've regenerated database of existing OI drivers shipped with DDU, updated pci.ids and usb.ids files.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???




From gary_mills at fastmail.fm  Mon Jun 24 15:33:31 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Mon, 24 Jun 2019 10:33:31 -0500
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
Message-ID: <20190624153331.GA28009@mail.messagingengine.com>

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aur?lien Larcher wrote:
> 
>    Congratulations Gary this is great :)
>    If we get to the point that we can setup a build machine this would
>    secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From alp at sfedu.ru  Mon Jun 24 16:02:51 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 16:02:51 +0000
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <20190624153331.GA28009@mail.messagingengine.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>,
	<20190624153331.GA28009@mail.messagingengine.com>
Message-ID: <AM6PR05MB619883D7A53C05872643155DCFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

BTW, while working on DDU I've removed SPARC parts I've encountered ;)
Anyway I had no way (or desire) to test them.
Most interesting is likely dmi_info.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Gary Mills <gary_mills at fastmail.fm>
??????????: 24 ???? 2019 ?. 18:33
????: OpenIndiana Developer mailing list
????: Re: [oi-dev] Toward a SPARC distro of OI

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aur?lien Larcher wrote:
>
>    Congratulations Gary this is great :)
>    If we get to the point that we can setup a build machine this would
>    secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


--
-Gary Mills-            -refurb-                -Winnipeg, Manitoba, Canada-

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

From Tim.Mooney at ndsu.edu  Mon Jun 24 18:24:09 2019
From: Tim.Mooney at ndsu.edu (Tim Mooney)
Date: Mon, 24 Jun 2019 13:24:09 -0500 (CDT)
Subject: [oi-dev] component TODO list for perl components?
In-Reply-To: <AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>
References: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
	<AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>
Message-ID: <alpine.SOC.2.20.1906241317080.14673@dogbert.cc.ndsu.NoDak.edu>

In regard to: Re: [oi-dev] component TODO list for perl components?,...:

> I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/
> some time ago. There are mostly tasks which I'm interested in.
>
> Now I'm looking at removing binary blobs from DDU. Later I'll likely
> look at switching it to Python 3.5.
>
> If you can propose any tasks which you can take (or pehaps, someone
> else), feel  free to update this page. I just don't want it to become a
> list of never-done tasks.

Thanks Alexander, and I understand completely about a list of never-done
tasks.

I'll open a pull request with some proposed updates, and you and others
can comment on whether they're a good idea or not.

Tim

> ________________________________________
> ??: Tim Mooney <Tim.Mooney at ndsu.edu>
> ??????????: 24 ???? 2019 ?. 5:24:33
> ????: oi-dev at openindiana.org
> ????: [oi-dev] component TODO list for perl components?
>
>
> I've been considering packaging the latest stable perl5, 5.30.0, as
> perl-530 and then packaging (and in some cases, updating) the perl
> modules that are part of hipster, but I want to make certain I'm not
> working at cross-purposes to any planned updates for OI and that this
> type of update is actually useful.
>
> There's a checklist of small/easy changes to make when updating a
> component,
>
>        https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md
>
> but is there a list of the bigger packaging tasks, perhaps prioritized by
> need?  Obviously people volunteering their time are going to work on
> things that interest them, benefit them, and are within their ability,
> but at times it would be helpful to know what the most pressing packaging
> needs are.
>
> I'm happy to continue choosing components kind of at random to update, but
> if I have a list of easy (but perhaps tedious) packaging tasks that are
> priorities for update in OI, I would probably attempt some of them as I
> have time, especially if it frees up more time for core contributors to
> work on the more difficult tasks.
>
> Does a list like that exist?  Those types of things tend to go stale fast,
> so I understand if there isn't one.
>
> Tim
> --
> Tim Mooney                                             Tim.Mooney at ndsu.edu
> Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
> Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>

-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

From gary_mills at fastmail.fm  Tue Jun 25 20:47:20 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 25 Jun 2019 15:47:20 -0500
Subject: [oi-dev] Am I stuck?
Message-ID: <20190625204720.GA8601@mail.messagingengine.com>

These are my publishers:

    # pkg publisher                      
    PUBLISHER                   TYPE     STATUS P LOCATION
    oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
    v9os           (non-sticky) origin   online F file:///data/ips/

I just published all of illumos-gate to the oi-userland repository.
There are now two copies of the
consolidation/osnet/osnet-incorporation package.  This is the
installed one:

    # pkg info consolidation/osnet/osnet-incorporation
              Name: consolidation/osnet/osnet-incorporation
           Summary: OS/Net consolidation incorporation
       Description: This incorporation constrains packages from the OS/Net
                    consolidation.
             State: Installed
         Publisher: v9os
           Version: 0.5.11
            Branch: 0.151100
    Packaging Date: Wed Jul 27 07:12:37 2016
              Size: 0.00 B
              FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
    
This is the new one:

    # pkg info -r consolidation/osnet/osnet-incorporation
              Name: consolidation/osnet/osnet-incorporation
           Summary: OS/Net consolidation incorporation
       Description: This incorporation constrains packages from the OS/Net
                    consolidation.
             State: Not installed
         Publisher: oi-userland
           Version: 0.5.11
            Branch: 2018.0.0.0
    Packaging Date: Sun Jun 23 22:35:19 2019
              Size: 0.00 B
              FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z

I expected that `pkg update -nv' would offer to remove the installed
incorporation and replace all of the old illumos-gate packages, over
200 of them, with the new illumos-gate packages.  It didn't do that.
It did report that it would replace ten packages from the v9os
publisher with newer versions from the oi-userland publisher, but this
list didn't include any of the illumos-gate packages.

When I tried to remove the incorporation with pkg, I got this result:

    # pkg uninstall -nv consolidation/osnet/osnet-incorporation
    Creating Plan (Solver setup): -
    pkg uninstall: Unable to remove 'consolidation/osnet/osnet-incorporation at 0.5.11-0.151100' due to the following packages that depend on it:
      SUNWcs at 0.5.11-0.151100
      SUNWcsd at 0.5.11-0.151100
      compatibility/ucb at 0.5.11-0.151100
      developer/astdev at 0.5.11-0.151100
    ...
      system/zones at 0.5.11-0.151100
      system/zones/internal at 0.5.11-0.151100
      text/doctools at 0.5.11-0.151100
      text/locale at 0.5.11-0.151100

Have I run into a dead end, or is there a way out of this dilemma?


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From vab at bb-c.de  Tue Jun 25 21:01:31 2019
From: vab at bb-c.de (Volker A. Brandt)
Date: Tue, 25 Jun 2019 23:01:31 +0200
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190625204720.GA8601@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
Message-ID: <23826.35755.98828.321659@shelob.bb-c.de>

Hi Gary!


> These are my publishers:
> 
>     # pkg publisher                      
>     PUBLISHER                   TYPE     STATUS P LOCATION
>     oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
>     v9os           (non-sticky) origin   online F file:///data/ips/
> 
> I just published all of illumos-gate to the oi-userland repository.
> There are now two copies of the
> consolidation/osnet/osnet-incorporation package.  This is the
> installed one:
> 
>     # pkg info consolidation/osnet/osnet-incorporation
>               Name: consolidation/osnet/osnet-incorporation
>            Summary: OS/Net consolidation incorporation
>        Description: This incorporation constrains packages from the OS/Net
>                     consolidation.
>              State: Installed
>          Publisher: v9os
>            Version: 0.5.11
>             Branch: 0.151100
>     Packaging Date: Wed Jul 27 07:12:37 2016
>               Size: 0.00 B
>               FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
>     
> This is the new one:
> 
>     # pkg info -r consolidation/osnet/osnet-incorporation
>               Name: consolidation/osnet/osnet-incorporation
>            Summary: OS/Net consolidation incorporation
>        Description: This incorporation constrains packages from the OS/Net
>                     consolidation.
>              State: Not installed
>          Publisher: oi-userland
>            Version: 0.5.11
>             Branch: 2018.0.0.0
>     Packaging Date: Sun Jun 23 22:35:19 2019
>               Size: 0.00 B
>               FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z
> 
> I expected that `pkg update -nv' would offer to remove the installed
> incorporation and replace all of the old illumos-gate packages, over
> 200 of them, with the new illumos-gate packages.  It didn't do that.
> It did report that it would replace ten packages from the v9os
> publisher with newer versions from the oi-userland publisher, but this
> list didn't include any of the illumos-gate packages.

So it appears that pkg does not recognize the fact that version
0.5.11-2018.0.0.0:20190623T223519Z is newer than version
0.5.11-0.151100:20160727T071237Z -- correct?

> When I tried to remove the incorporation with pkg, I got this result:
[...]

I don't think that you are supposed to be able to remove the package
altogether.  You should, hovewer, be able to update it.

Do you also have an "entire" package?  If so, what version does it
have?


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt        Consulting and Support for Solaris-based Systems
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"



From gary_mills at fastmail.fm  Wed Jun 26 00:31:04 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 25 Jun 2019 19:31:04 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <23826.35755.98828.321659@shelob.bb-c.de>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
Message-ID: <20190626003104.GA10000@mail.messagingengine.com>

On Tue, Jun 25, 2019 at 11:01:31PM +0200, Volker A. Brandt wrote:
> 
> So it appears that pkg does not recognize the fact that version
> 0.5.11-2018.0.0.0:20190623T223519Z is newer than version
> 0.5.11-0.151100:20160727T071237Z -- correct?

I don't think that that is the problem.  Consider this transcript:

    # pkg update -nv
    ...
    Changed packages:
    ...
    v9os -> oi-userland
      archiver/gnu-tar
        1.28-0.151100 -> 1.29-2018.0.0.0
      compress/bzip2
        1.0.6-0.151100 -> 1.0.6-2018.0.0.3
      compress/gzip
        1.6-0.151100 -> 1.9-2018.0.0.0

The version numbers were the same for the last two packages.

> > When I tried to remove the incorporation with pkg, I got this result:
> [...]
> 
> I don't think that you are supposed to be able to remove the package
> altogether.  You should, hovewer, be able to update it.

That's close to working.  I should be able to make it work.
Here's this one:

    # pkg update -nv pkg://oi-userland/consolidation/osnet/osnet-inco...
    Creating Plan (Solver setup): \
    pkg update: No matching version of consolidation/osnet/osnet-incorporation can be installed:
      Reject:  pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0
      Reason:  No version matching 'incorporate' dependency SUNWcs at 0.5.11-2018.0.0.0 can be installed
        ----------------------------------------
        Reject:  pkg://oi-userland/SUNWcs at 0.5.11-2018.0.0.0
        Reason:  No version matching 'require' dependency system/network/mailwrapper can be installed
          ----------------------------------------
          Reject:  pkg://oi-userland/system/network/mailwrapper at 0.5.11-2018.0.0.0
          Reason:  No version for 'require' dependency on system/mta can be found
          Reject:  pkg://v9os/system/network/mailwrapper at 0.5.11-0.151100
          Reason:  Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation'
          ----------------------------------------
        ----------------------------------------

> Do you also have an "entire" package?  If so, what version does it
> have?

No, I don't have that package.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From naj at snapcon.com  Wed Jun 26 00:28:12 2019
From: naj at snapcon.com (Norm Jacobs)
Date: Tue, 25 Jun 2019 19:28:12 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190625204720.GA8601@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
Message-ID: <1bba6380-a729-e329-a326-0fd1aa7572fb@snapcon.com>

You might look at the 'entire' package and see if it constrains the 
'osnet-incorporation to the older version.? That is most likely the 
cause of your trouble.? You can probably remove the 'entire' package and 
then update.? You might also be able to unlock the incorporation before 
upgrading instead.

 ??? -Norm


On 6/25/19 3:47 PM, Gary Mills wrote:
> These are my publishers:
>
>      # pkg publisher
>      PUBLISHER                   TYPE     STATUS P LOCATION
>      oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
>      v9os           (non-sticky) origin   online F file:///data/ips/
>
> I just published all of illumos-gate to the oi-userland repository.
> There are now two copies of the
> consolidation/osnet/osnet-incorporation package.  This is the
> installed one:
>
>      # pkg info consolidation/osnet/osnet-incorporation
>                Name: consolidation/osnet/osnet-incorporation
>             Summary: OS/Net consolidation incorporation
>         Description: This incorporation constrains packages from the OS/Net
>                      consolidation.
>               State: Installed
>           Publisher: v9os
>             Version: 0.5.11
>              Branch: 0.151100
>      Packaging Date: Wed Jul 27 07:12:37 2016
>                Size: 0.00 B
>                FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
>      
> This is the new one:
>
>      # pkg info -r consolidation/osnet/osnet-incorporation
>                Name: consolidation/osnet/osnet-incorporation
>             Summary: OS/Net consolidation incorporation
>         Description: This incorporation constrains packages from the OS/Net
>                      consolidation.
>               State: Not installed
>           Publisher: oi-userland
>             Version: 0.5.11
>              Branch: 2018.0.0.0
>      Packaging Date: Sun Jun 23 22:35:19 2019
>                Size: 0.00 B
>                FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z
>
> I expected that `pkg update -nv' would offer to remove the installed
> incorporation and replace all of the old illumos-gate packages, over
> 200 of them, with the new illumos-gate packages.  It didn't do that.
> It did report that it would replace ten packages from the v9os
> publisher with newer versions from the oi-userland publisher, but this
> list didn't include any of the illumos-gate packages.
>
> When I tried to remove the incorporation with pkg, I got this result:
>
>      # pkg uninstall -nv consolidation/osnet/osnet-incorporation
>      Creating Plan (Solver setup): -
>      pkg uninstall: Unable to remove 'consolidation/osnet/osnet-incorporation at 0.5.11-0.151100' due to the following packages that depend on it:
>        SUNWcs at 0.5.11-0.151100
>        SUNWcsd at 0.5.11-0.151100
>        compatibility/ucb at 0.5.11-0.151100
>        developer/astdev at 0.5.11-0.151100
>      ...
>        system/zones at 0.5.11-0.151100
>        system/zones/internal at 0.5.11-0.151100
>        text/doctools at 0.5.11-0.151100
>        text/locale at 0.5.11-0.151100
>
> Have I run into a dead end, or is there a way out of this dilemma?
>
>



From richlowe at richlowe.net  Wed Jun 26 00:42:41 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Tue, 25 Jun 2019 20:42:41 -0400
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190626003104.GA10000@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
	<20190626003104.GA10000@mail.messagingengine.com>
Message-ID: <CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>

Reason:  No version for 'require' dependency on system/mta can be found

Seems a leaf failure, does one really not exist?



From gary_mills at fastmail.fm  Wed Jun 26 12:52:41 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Wed, 26 Jun 2019 07:52:41 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
	<20190626003104.GA10000@mail.messagingengine.com>
	<CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>
Message-ID: <20190626125240.GA12540@mail.messagingengine.com>

On Tue, Jun 25, 2019 at 08:42:41PM -0400, Richard Lowe wrote:
> Reason:  No version for 'require' dependency on system/mta can be found
> 
> Seems a leaf failure, does one really not exist?

Indeed, the package system/mta does not exist in either publisher.  I
just published it to oi-userland and installed it.  My next task is to
see if that missing package was preventing the update.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From gordon.w.ross at gmail.com  Fri Jun 28 04:25:37 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 27 Jun 2019 21:25:37 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
Message-ID: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>

Any ideas what I should do to fix this?

root at oi-dev:/home/gwr# pkg -R /mnt image-update -v
Creating Plan (Running solver): /
pkg update: No solution was found to satisfy constraints
No solution found to update to latest available versions.
This may indicate an overly constrained set of packages are installed.

latest incorporations:

  pkg://openindiana.org/consolidation/install/install-incorporation at 0.5.11,5.11-2018.0.0.1041:20190516T142943Z
  pkg://openindiana.org/consolidation/l10n/l10n-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014527Z
  pkg://openindiana.org/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014529Z
  pkg://openindiana.org/consolidation/userland/userland-incorporation at 0.5.11,5.11-2018.0.0.11903:20190627T091450Z

Dependency analysis is unable to determine the cause.
Try specifying expected versions to obtain more detailed error messages.

On Sun, May 12, 2019 at 12:33 AM Alexander Pyhalov via oi-dev
<oi-dev at openindiana.org> wrote:
>
> Sorry, missed dot in
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso link.
>
> ? ?????????,
> ????????? ???????,
> ??????????? ?????? ???????????????????? ??????????????
> ?????????? ?????????????-???????????????? ?????????????? ???
>
>
> ________________________________________
> ??: Alexander Pyhalov via oi-dev <oi-dev at openindiana.org>
> ??????????: 12 ??? 2019 ?. 10:11:57
> ????: OpenIndiana Developer mailing list
> ?????: Alexander Pyhalov
> ????: [oi-dev] OI Hipster 2019.04
>
> Hi.
>
> OI Hipster 2019.04 snapshot is ready.
>
> Images:
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb
>
>
> SHA 256 checksums are available at ${link}.sha256sum
> Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
> https://sks-keyservers.net/pks/lookup?op=get&search=0x3A021AFADBE31887 ).
>
> Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes
>
> Note, we have an issue with Firefox on live image - it can fail to start correctly when launched for the first time in memory-constrained  environment. After being killed and restarted it behaves more sane.
>
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



From gordon.w.ross at gmail.com  Fri Jun 28 04:26:44 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 27 Jun 2019 21:26:44 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
Message-ID: <CAD0Ztp2nrGdb3t2sKjUdR9HNNwdSJ_t=eJs=6UBesB2Uo=+wtA@mail.gmail.com>

I'm guessing people will want to see:

root at oi-dev:/home/gwr# pkg -R /mnt publisher
PUBLISHER                   TYPE     STATUS P LOCATION
openindiana.org              origin   online F
http://pkg.openindiana.org/hipster/
root at oi-dev:/home/gwr# pkg -R /mnt info entire
          Name: entire
       Summary: incorporation to lock all system packages to same build (empty
                package)
   Description: incorporation to lock all system packages to same build (empty
                package)
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
        Branch: 2018.0.0.0
Packaging Date: February 11, 2018 at 01:10:12 PM
          Size: 0.00 B
          FMRI: pkg://openindiana.org/entire at 0.5.11-2018.0.0.0:20180211T131012Z

On Thu, Jun 27, 2019 at 9:25 PM Gordon Ross <gordon.w.ross at gmail.com> wrote:
>
> Any ideas what I should do to fix this?
>
> root at oi-dev:/home/gwr# pkg -R /mnt image-update -v
> Creating Plan (Running solver): /
> pkg update: No solution was found to satisfy constraints
> No solution found to update to latest available versions.
> This may indicate an overly constrained set of packages are installed.
>
> latest incorporations:
>
>   pkg://openindiana.org/consolidation/install/install-incorporation at 0.5.11,5.11-2018.0.0.1041:20190516T142943Z
>   pkg://openindiana.org/consolidation/l10n/l10n-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014527Z
>   pkg://openindiana.org/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014529Z
>   pkg://openindiana.org/consolidation/userland/userland-incorporation at 0.5.11,5.11-2018.0.0.11903:20190627T091450Z
>
> Dependency analysis is unable to determine the cause.
> Try specifying expected versions to obtain more detailed error messages.
>
> On Sun, May 12, 2019 at 12:33 AM Alexander Pyhalov via oi-dev
> <oi-dev at openindiana.org> wrote:
> >
> > Sorry, missed dot in
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso link.
> >
> > ? ?????????,
> > ????????? ???????,
> > ??????????? ?????? ???????????????????? ??????????????
> > ?????????? ?????????????-???????????????? ?????????????? ???
> >
> >
> > ________________________________________
> > ??: Alexander Pyhalov via oi-dev <oi-dev at openindiana.org>
> > ??????????: 12 ??? 2019 ?. 10:11:57
> > ????: OpenIndiana Developer mailing list
> > ?????: Alexander Pyhalov
> > ????: [oi-dev] OI Hipster 2019.04
> >
> > Hi.
> >
> > OI Hipster 2019.04 snapshot is ready.
> >
> > Images:
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb
> >
> >
> > SHA 256 checksums are available at ${link}.sha256sum
> > Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> > The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
> > https://sks-keyservers.net/pks/lookup?op=get&search=0x3A021AFADBE31887 ).
> >
> > Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes
> >
> > Note, we have an issue with Firefox on live image - it can fail to start correctly when launched for the first time in memory-constrained  environment. After being killed and restarted it behaves more sane.
> >
> > Best regards,
> > Alexander Pyhalov,
> > system administrator of Southern Federal University IT department
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev



From richlowe at richlowe.net  Fri Jun 28 05:28:15 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Fri, 28 Jun 2019 01:28:15 -0400
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
Message-ID: <CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>

> Dependency analysis is unable to determine the cause.
> Try specifying expected versions to obtain more detailed error messages.
>

Do what it says there,

Specify the verisons of those 'latest incorporations', and probably
also entire, including the versions.

You may be able to just do 'pkg install -nv entire at latest' but I can
never remember whether only specifying 'entire' does the right thing.



From gordon.w.ross at gmail.com  Fri Jun 28 17:32:25 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Fri, 28 Jun 2019 10:32:25 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
Message-ID: <CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>

OK, but I can't seem to find the latest version of entire.
Can anyone tell me what that should be?

root at oi-dev:/home/gwr# pkg -R /mnt refresh --full
root at oi-dev:/home/gwr# pkg -R /mnt update -nv entire at latest
No updates available for this image.
root at oi-dev:/home/gwr# pkg -R /mnt install -nv entire at latest
No updates necessary for this image.
root at oi-dev:/home/gwr# pkg -R /mnt info entire
          Name: entire
       Summary: incorporation to lock all system packages to same build (empty
                package)
   Description: incorporation to lock all system packages to same build (empty
                package)
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
        Branch: 2018.0.0.0
Packaging Date: February 11, 2018 at 01:10:12 PM
          Size: 0.00 B
          FMRI: pkg://openindiana.org/entire at 0.5.11-2018.0.0.0:20180211T131012Z

On Thu, Jun 27, 2019 at 10:28 PM Richard Lowe <richlowe at richlowe.net> wrote:
>
> > Dependency analysis is unable to determine the cause.
> > Try specifying expected versions to obtain more detailed error messages.
> >
>
> Do what it says there,
>
> Specify the verisons of those 'latest incorporations', and probably
> also entire, including the versions.
>
> You may be able to just do 'pkg install -nv entire at latest' but I can
> never remember whether only specifying 'entire' does the right thing.
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



From richlowe at richlowe.net  Fri Jun 28 17:43:23 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Fri, 28 Jun 2019 13:43:23 -0400
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
	<CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>
Message-ID: <CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?



From alp at sfedu.ru  Sat Jun 29 05:37:26 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Sat, 29 Jun 2019 05:37:26 +0000
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
	<CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>,
	<CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>
Message-ID: <AM6PR05MB6198F5838BDA1D994F326236CFFF0@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.
entire is a package which depends on userland-incorporation. That's all. You are interested in latest osnet-incorporation and userland-incorporation.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Richard Lowe <richlowe at richlowe.net>
??????????: 28 ???? 2019 ?. 20:43
????: OpenIndiana Developer mailing list
????: Re: [oi-dev] OI Hipster 2019.04

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



From grzemba at contac-dt.de  Mon Jun  3 14:44:26 2019
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Mon, 03 Jun 2019 16:44:26 +0200
Subject: [oi-dev] Openindiana on Laptop: touchpad not working
In-Reply-To: <bd3e8f4829c5.5ce65b00@contac-dt.de>
References: <be86e6074ec1.5ce41f99@contac-dt.de>
	<alpine.GSO.2.20.1905211010220.7749@scrappy.simplesystems.org>
	<bd3e8f4829c5.5ce65b00@contac-dt.de>
Message-ID: <bd3d30256aff.5cf54e6a@contac-dt.de>


<signaturebeforequotedtext></signaturebeforequotedtext>
On 23.05.19 08:34, Carsten Grzemba via oi-dev  <oi-dev at openindiana.org> wrote: 
> 
> I compared the Xorg log:
> 
> in the working log the mouse driver is loaded on PS/s mouse on /dev/mouse:
> 
> [ 38.008] (II) LoadModule: "mouse"
> [ 38.008] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> [ 38.012] (II) Module mouse: vendor="X.Org Foundation"
> [ 38.012] compiled for 1.19.5, module version = 1.9.2
> [ 38.012] Module class: X.Org XInput Driver
> [ 38.012] ABI class: X.Org XInput driver, version 24.1
> [ 38.012] (II) Using input driver 'mouse' for 'PS/2 Port for PS/2-style Mice'
> [ 38.012] (**) PS/2 Port for PS/2-style Mice: always reports core events
> [ 38.012] (**) Option "Device" "/dev/mouse"
> [ 38.012] (II) PS/2 Port for PS/2-style Mice: Setting Device option to "/dev/mouse"
> [ 38.014] (==) PS/2 Port for PS/2-style Mice: Protocol: "VUID"
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: always reports core events
> [ 38.014] (**) Option "Device" "/dev/mouse"
> [ 38.014] (==) PS/2 Port for PS/2-style Mice: Emulate3Buttons, Emulate3Timeout: 50
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: ZAxisMapping: buttons 4 and 5
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: Buttons: 9
> [ 38.014] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/isa_1f/i8042_1_60/mouse_1_0_logicaldev_input"
> [ 38.014] (II) XINPUT: Adding extended input device "PS/2 Port for PS/2-style Mice" (type: MOUSE, id 6)
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) keeping acceleration scheme 1
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration profile 0
> [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration factor: 2.000
> [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration threshold: 4
> 
> and the not working on the generic USB device /dev/usb/hid1:
> 
> [ 523.036] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> [ 523.036] (II) Module mouse: vendor="X.Org Foundation"
> [ 523.036] compiled for 1.19.5, module version = 1.9.2
> [ 523.036] Module class: X.Org XInput Driver
> [ 523.037] ABI class: X.Org XInput driver, version 24.1
> [ 523.037] (II) Using input driver 'mouse' for 'mouse'
> [ 523.037] (**) mouse: always reports core events
> [ 523.037] (**) Option "Protocol" "VUID"
> [ 523.037] (**) Option "Device" "/dev/usb/hid1"
> [ 523.037] (**) Option "StreamsModule" "usbms"
> [ 523.039] (**) mouse: Protocol: "VUID"
> [ 523.039] (**) mouse: always reports core events
> [ 523.039] (==) mouse: Emulate3Buttons, Emulate3Timeout: 50
> [ 523.039] (**) mouse: ZAxisMapping: buttons 4 and 5
> [ 523.039] (**) mouse: Buttons: 9
> [ 523.039] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1025_1019_14/device_4/mouse_1_if1_4_logicaldev_input"
> [ 523.039] (II) XINPUT: Adding extended input device "mouse" (type: MOUSE, id 6)
> [ 523.039] (**) mouse: (accel) keeping acceleration scheme 1
> [ 523.039] (**) mouse: (accel) acceleration profile 0
> [ 523.039] (**) mouse: (accel) acceleration factor: 2.000
> [ 523.039] (**) mouse: (accel) acceleration threshold: 4
> [ 523.045] (II) config/hal: Adding input device hotkey
> 
> 
> in both cases is the the touchpad avail and a extern USB mouse connected. the /dev/mouse dev link is in both BE targeted to /devices/pseudo/cons at 0:mouse
> 
> 
Still no luck with the latest hipster on my laptop:

scanpci:
pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1604
?Intel Corporation Broadwell-U Host Bridge -OPI

pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1616
?Intel Corporation HD Graphics 5500

pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x160c
?Intel Corporation Broadwell-U Audio Controller

pci bus 0x0000 cardnum 0x14 function 0x00: vendor 0x8086 device 0x9cb1
?Intel Corporation Wildcat Point-LP USB xHCI Controller

pci bus 0x0000 cardnum 0x16 function 0x00: vendor 0x8086 device 0x9cba
?Intel Corporation Wildcat Point-LP MEI Controller #1

pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x9ca0
?Intel Corporation Wildcat Point-LP High Definition Audio Controller

pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x9c90
?Intel Corporation Wildcat Point-LP PCI Express Root Port #1

pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device 0x9c94
?Intel Corporation Wildcat Point-LP PCI Express Root Port #3

pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
?Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device 0x9c96
?Intel Corporation Wildcat Point-LP PCI Express Root Port #4

pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x8086 device 0x095a
?Intel Corporation Wireless 7265

pci bus 0x0000 cardnum 0x1c function 0x04: vendor 0x8086 device 0x9c98
?Intel Corporation Wildcat Point-LP PCI Express Root Port #5

pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10de device 0x1299
?NVIDIA Corporation GK208BM [GeForce 920M]

pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x9ca6
?Intel Corporation Wildcat Point-LP USB EHCI Controller

pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x9cc3
?Intel Corporation Wildcat Point-LP LPC ControllerX.Org X Server 1.19.6

pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x9c83
?Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode]

pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x9ca2
?Intel Corporation Wildcat Point-LP SMBus Controller

I boot from latest USB image there X session dont start, only the mouse pointer is seen. If I kill the Xorg via SSH I get no text console.
So I reboot in text console and tried to test Xorg configuration with my current working settings (of Xorg 1.19.6 vesa for the Intel, Nvidia was never usable with the old i915 driver). There I get only a black screen and after kill Xorg no text console again. 
Activating vtdaemon and vt-console also not working.

What is the change here, so that Xorg 1.19.7 isn't working anymore? In Xorg.0.log I dont see any errors.

Thanks



























 <signatureafterquotedtext></signatureafterquotedtext>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190603/0736b268/attachment-0004.html>

From grzemba at contac-dt.de  Tue Jun  4 08:27:09 2019
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Tue, 04 Jun 2019 10:27:09 +0200
Subject: [oi-dev] Openindiana on Laptop: touchpad not working
In-Reply-To: <bd3d30256aff.5cf54e6a@contac-dt.de>
References: <be86e6074ec1.5ce41f99@contac-dt.de>
	<alpine.GSO.2.20.1905211010220.7749@scrappy.simplesystems.org>
	<bd3e8f4829c5.5ce65b00@contac-dt.de>
	<bd3d30256aff.5cf54e6a@contac-dt.de>
Message-ID: <bf5f8a435076.5cf6477d@contac-dt.de>


<signaturebeforequotedtext></signaturebeforequotedtext>
On 03.06.19 16:44, "Carsten Grzemba"  <grzemba at contac-dt.de> wrote: 
> 
> 
> 
> On 23.05.19 08:34, Carsten Grzemba via oi-dev  <oi-dev at openindiana.org> wrote: 
> > 
> > I compared the Xorg log:
> > 
> > in the working log the mouse driver is loaded on PS/s mouse on /dev/mouse:
> > 
> > [ 38.008] (II) LoadModule: "mouse"
> > [ 38.008] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> > [ 38.012] (II) Module mouse: vendor="X.Org Foundation"
> > [ 38.012] compiled for 1.19.5, module version = 1.9.2
> > [ 38.012] Module class: X.Org XInput Driver
> > [ 38.012] ABI class: X.Org XInput driver, version 24.1
> > [ 38.012] (II) Using input driver 'mouse' for 'PS/2 Port for PS/2-style Mice'
> > [ 38.012] (**) PS/2 Port for PS/2-style Mice: always reports core events
> > [ 38.012] (**) Option "Device" "/dev/mouse"
> > [ 38.012] (II) PS/2 Port for PS/2-style Mice: Setting Device option to "/dev/mouse"
> > [ 38.014] (==) PS/2 Port for PS/2-style Mice: Protocol: "VUID"
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: always reports core events
> > [ 38.014] (**) Option "Device" "/dev/mouse"
> > [ 38.014] (==) PS/2 Port for PS/2-style Mice: Emulate3Buttons, Emulate3Timeout: 50
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: ZAxisMapping: buttons 4 and 5
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: Buttons: 9
> > [ 38.014] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/isa_1f/i8042_1_60/mouse_1_0_logicaldev_input"
> > [ 38.014] (II) XINPUT: Adding extended input device "PS/2 Port for PS/2-style Mice" (type: MOUSE, id 6)
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) keeping acceleration scheme 1
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration profile 0
> > [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration factor: 2.000
> > [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration threshold: 4
> > 
> > and the not working on the generic USB device /dev/usb/hid1:
> > 
> > [ 523.036] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> > [ 523.036] (II) Module mouse: vendor="X.Org Foundation"
> > [ 523.036] compiled for 1.19.5, module version = 1.9.2
> > [ 523.036] Module class: X.Org XInput Driver
> > [ 523.037] ABI class: X.Org XInput driver, version 24.1
> > [ 523.037] (II) Using input driver 'mouse' for 'mouse'
> > [ 523.037] (**) mouse: always reports core events
> > [ 523.037] (**) Option "Protocol" "VUID"
> > [ 523.037] (**) Option "Device" "/dev/usb/hid1"
> > [ 523.037] (**) Option "StreamsModule" "usbms"
> > [ 523.039] (**) mouse: Protocol: "VUID"
> > [ 523.039] (**) mouse: always reports core events
> > [ 523.039] (==) mouse: Emulate3Buttons, Emulate3Timeout: 50
> > [ 523.039] (**) mouse: ZAxisMapping: buttons 4 and 5
> > [ 523.039] (**) mouse: Buttons: 9
> > [ 523.039] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1025_1019_14/device_4/mouse_1_if1_4_logicaldev_input"
> > [ 523.039] (II) XINPUT: Adding extended input device "mouse" (type: MOUSE, id 6)
> > [ 523.039] (**) mouse: (accel) keeping acceleration scheme 1
> > [ 523.039] (**) mouse: (accel) acceleration profile 0
> > [ 523.039] (**) mouse: (accel) acceleration factor: 2.000
> > [ 523.039] (**) mouse: (accel) acceleration threshold: 4
> > [ 523.045] (II) config/hal: Adding input device hotkey
> > 
> > 
> > in both cases is the the touchpad avail and a extern USB mouse connected. the /dev/mouse dev link is in both BE targeted to /devices/pseudo/cons at 0:mouse
> > 
> > 
> Still no luck with the latest hipster on my laptop:
> 
> scanpci:
> pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1604
> ?Intel Corporation Broadwell-U Host Bridge -OPI
> 
> pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1616
> ?Intel Corporation HD Graphics 5500
> 
> pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x160c
> ?Intel Corporation Broadwell-U Audio Controller
> 
> pci bus 0x0000 cardnum 0x14 function 0x00: vendor 0x8086 device 0x9cb1
> ?Intel Corporation Wildcat Point-LP USB xHCI Controller
> 
> pci bus 0x0000 cardnum 0x16 function 0x00: vendor 0x8086 device 0x9cba
> ?Intel Corporation Wildcat Point-LP MEI Controller #1
> 
> pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x9ca0
> ?Intel Corporation Wildcat Point-LP High Definition Audio Controller
> 
> pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x9c90
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #1
> 
> pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device 0x9c94
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #3
> 
> pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
> ?Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
> 
> pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device 0x9c96
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #4
> 
> pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x8086 device 0x095a
> ?Intel Corporation Wireless 7265
> 
> pci bus 0x0000 cardnum 0x1c function 0x04: vendor 0x8086 device 0x9c98
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #5
> 
> pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10de device 0x1299
> ?NVIDIA Corporation GK208BM [GeForce 920M]
> 
> pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x9ca6
> ?Intel Corporation Wildcat Point-LP USB EHCI Controller
> 
> pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x9cc3
> ?Intel Corporation Wildcat Point-LP LPC ControllerX.Org X Server 1.19.6
> 
> pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x9c83
> ?Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode]
> 
> pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x9ca2
> ?Intel Corporation Wildcat Point-LP SMBus Controller
> 
> I boot from latest USB image there X session dont start, only the mouse pointer is seen. If I kill the Xorg via SSH I get no text console.
> So I reboot in text console and tried to test Xorg configuration with my current working settings (of Xorg 1.19.6 vesa for the Intel, Nvidia was never usable with the old i915 driver). There I get only a black screen and after kill Xorg no text console again. 
> Activating vtdaemon and vt-console also not working.
> 
> What is the change here, so that Xorg 1.19.7 isn't working anymore? In Xorg.0.log I dont see any errors.
> 
> Thanks 
> 
Because the Xorg config is not changed and the touchpad not working on newer hipster, it looks for me like the touchpad is disabled what can normaly toggled by Fn F7.
But Fn keys do not work at all on newer hipster. Something to do with ACPI ?

 <signatureafterquotedtext></signatureafterquotedtext>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190604/1b76e6e2/attachment-0004.html>

From randyf at sibernet.com  Tue Jun 11 18:07:21 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 11:07:21 -0700 (PDT)
Subject: [oi-dev] suspend/resume in Illumos
Message-ID: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>



I have a question for developers here:

    How important is suspend/resume for OI/Illumos (including S4)?


One of the incomplete projects left behind was S4 (lack of need, and a 
hard to identify bug stifled it's integration).  It is non-trivial, and 
needs updated s/r core code (added configuration and significant 
restructuring, as well as likely assistance from developers knowlegable in 
other Illumos internals), but if this is an uninteresting feature, it is 
likey not worth the effort (recent bugs suggest that few if anyone use 
it); however, it wouldn't be too hard to resurect (though would still take 
several months of work).


   Cheers!

 	---- Randy



From gary_mills at fastmail.fm  Tue Jun 11 18:10:11 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 11 Jun 2019 13:10:11 -0500
Subject: [oi-dev] Toward a SPARC distro of OI
Message-ID: <20190611181011.GA18869@mail.messagingengine.com>

I'm part way through this long project now.  I began with v9os
installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
packages.  I've been building IPS packages from oi-userland source.
This process has gotten easier now that all the build tools I need are
in IPS packages.  I've been replacing v9os packages with oi-userland
packages.  My goal is to replace all of them, and finally to produce a
text ISO and package repository for SPARC that's entirely based on
oi-userland.

So far, I've built and packaged versions 5, 6, and 7 of the gcc
compiler.  The commands for IPS packages are all packaged for python
2.7.  My system now has 106 packages installed from oi-userland,
versus 343 packages from v9os.  Most of the oi-userland products
required very few or no changes to build and package for SPARC.

For perl, I've removed the 5.16.1 version from v9os and installed
versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
packaged for 5.22.  Python libraries are all packaged for 2.7.

I'm submitting this message to the mailing list mostly as a progress
report.  I would, of course, appreciate a bit of help with this
project.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From garrett at damore.org  Tue Jun 11 19:58:08 2019
From: garrett at damore.org (Garrett D'Amore)
Date: Tue, 11 Jun 2019 12:58:08 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
Message-ID: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>

My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where suspend/resume has little if any applicability.

While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from other more pressing work, without any clear use cases for it.

That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any other reason we would reject a suitably formed RTI.

Sent from Mail for Windows 10

From: randyf at sibernet.com
Sent: Tuesday, June 11, 2019 11:10 AM
To: oi-dev at openindiana.org; developer at lists.illumos.org
Subject: [developer] suspend/resume in Illumos



I have a question for developers here:

    How important is suspend/resume for OI/Illumos (including S4)?


One of the incomplete projects left behind was S4 (lack of need, and a 
hard to identify bug stifled it's integration).  It is non-trivial, and 
needs updated s/r core code (added configuration and significant 
restructuring, as well as likely assistance from developers knowlegable in 
other Illumos internals), but if this is an uninteresting feature, it is 
likey not worth the effort (recent bugs suggest that few if anyone use 
it); however, it wouldn't be too hard to resurect (though would still take 
several months of work).


   Cheers!

        ---- Randy

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190611/347dae6d/attachment-0004.html>

From tsoome at me.com  Tue Jun 11 20:31:18 2019
From: tsoome at me.com (Toomas Soome)
Date: Tue, 11 Jun 2019 23:31:18 +0300
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
Message-ID: <DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>

I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be bonus.

Sent from my iPhone

> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
> 
> My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where suspend/resume has little if any applicability.
>  
> While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from other more pressing work, without any clear use cases for it.
>  
> That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any other reason we would reject a suitably formed RTI.
>  
> Sent from Mail for Windows 10
>  
> From: randyf at sibernet.com
> Sent: Tuesday, June 11, 2019 11:10 AM
> To: oi-dev at openindiana.org; developer at lists.illumos.org
> Subject: [developer] suspend/resume in Illumos
>  
>  
>  
> I have a question for developers here:
>  
>     How important is suspend/resume for OI/Illumos (including S4)?
>  
>  
> One of the incomplete projects left behind was S4 (lack of need, and a
> hard to identify bug stifled it's integration).  It is non-trivial, and
> needs updated s/r core code (added configuration and significant
> restructuring, as well as likely assistance from developers knowlegable in
> other Illumos internals), but if this is an uninteresting feature, it is
> likey not worth the effort (recent bugs suggest that few if anyone use
> it); however, it wouldn't be too hard to resurect (though would still take
> several months of work).
>  
>  
>    Cheers!
>  
>         ---- Randy
>  
> ------------------------------------------
> illumos: illumos-developer
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
>  
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190611/1b0c9592/attachment-0004.html>

From randyf at sibernet.com  Tue Jun 11 21:28:34 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 14:28:34 -0700 (PDT)
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
Message-ID: <alpine.SOC.2.00.1906111420090.15467@sibernet.com>



On Tue, 11 Jun 2019, Garrett D'Amore wrote:

> 
> My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where
> suspend/resume has little if any applicability.
> 
> ?
> 
> While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from
> other more pressing work, without any clear use cases for it.
>

   I should point out that s/r isn't just for laptop bare-metal.  It allows 
for a running instance of an OS to be frozen in an orderly manner (rather 
than a VM just pausing a guest, the guest suspends first).  S4 opens a 
different world of allowing said image to be more easily migrated, or 
(since it has roots in CPR) opens quick-boot images (imagine getting an 
OS fully booted in under 10 seconds).

> ?
> 
> That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m
> fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any
> other reason we would reject a suitably formed RTI.
>

   Doubt I'll fully drop it, but without sufficient interest, it's is 
unlikely I'll give it much priority (certainly, my other 'dropped' project 
should have a higer priority).

   Cheers!

 	---- Randy

> ?
> 
> Sent from Mail for Windows 10
> 
> ?
> 
> From: randyf at sibernet.com
> Sent: Tuesday, June 11, 2019 11:10 AM
> To: oi-dev at openindiana.org; developer at lists.illumos.org
> Subject: [developer] suspend/resume in Illumos
> 
> ?
> 
> ?
> 
> ?
> 
> I have a question for developers here:
> 
> ?
> 
> ??? How important is suspend/resume for OI/Illumos (including S4)?
> 
> ?
> 
> ?
> 
> One of the incomplete projects left behind was S4 (lack of need, and a
> 
> hard to identify bug stifled it's integration).? It is non-trivial, and
> 
> needs updated s/r core code (added configuration and significant
> 
> restructuring, as well as likely assistance from developers knowlegable in
> 
> other Illumos internals), but if this is an uninteresting feature, it is
> 
> likey not worth the effort (recent bugs suggest that few if anyone use
> 
> it); however, it wouldn't be too hard to resurect (though would still take
> 
> several months of work).
> 
> ?
> 
> ?
> 
> ?? Cheers!
> 
> ?
> 
> ??????? ---- Randy
> 
> ?
> 
> ------------------------------------------
> 
> illumos: illumos-developer
> 
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> 
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
> 
> ?
> 
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
> 
>

From randyf at sibernet.com  Tue Jun 11 21:29:23 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 14:29:23 -0700 (PDT)
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
Message-ID: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>



On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:

> I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be
> bonus.

   Betting better graphics support would be higher on the list (yea, the 
other 'dropped' project).

   Cheers!

 	---- Randy

> 
> Sent from my iPhone
> 
> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>
>       My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter
>       applications where suspend/resume has little if any applicability.
>
>       ?
>
>       While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be
>       detraction from other more pressing work, without any clear use cases for it.
>
>       ?
>
>       That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it,
>       and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for
>       example), I can?t see any other reason we would reject a suitably formed RTI.
>
>       ?
>
>       Sent from Mail for Windows 10
>
>       ?
>
>       From: randyf at sibernet.com
>       Sent: Tuesday, June 11, 2019 11:10 AM
>       To: oi-dev at openindiana.org; developer at lists.illumos.org
>       Subject: [developer] suspend/resume in Illumos
> 
> ?
> 
> ?
> 
> ?
> 
> I have a question for developers here:
> 
> ?
> 
> ??? How important is suspend/resume for OI/Illumos (including S4)?
> 
> ?
> 
> ?
> 
> One of the incomplete projects left behind was S4 (lack of need, and a
> 
> hard to identify bug stifled it's integration).? It is non-trivial, and
> 
> needs updated s/r core code (added configuration and significant
> 
> restructuring, as well as likely assistance from developers knowlegable in
> 
> other Illumos internals), but if this is an uninteresting feature, it is
> 
> likey not worth the effort (recent bugs suggest that few if anyone use
> 
> it); however, it wouldn't be too hard to resurect (though would still take
> 
> several months of work).
> 
> ?
> 
> ?
> 
> ?? Cheers!
> 
> ?
> 
> ??????? ---- Randy
> 
> ?
> 
> ------------------------------------------
> 
> illumos: illumos-developer
> 
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> 
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
> 
> ?
> 
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
> 
>

From josh at sysmgr.org  Tue Jun 11 21:32:28 2019
From: josh at sysmgr.org (Joshua M. Clulow)
Date: Tue, 11 Jun 2019 14:32:28 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <CAEwA5nJHmR+Md2hh2HGj5770+-x=uanePOwqTrYRBe4W0GxPoQ@mail.gmail.com>

On Tue, 11 Jun 2019 at 14:29, <randyf at sibernet.com> wrote:
> On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
> > I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be
> > bonus.
>
>    Betting better graphics support would be higher on the list (yea, the
> other 'dropped' project).

I think there are a fair few people who would appreciate some serious
elbow grease being applied to the graphics bits!


Cheers.

-- 
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org



From jimklimov at cos.ru  Wed Jun 12 08:01:25 2019
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 12 Jun 2019 08:01:25 +0000
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>

On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>
>
>On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>
>> I?d say, anything to encourage people to try, use and join to develop
>[illumos] is very welcome. Better laptop support will definitely be
>> bonus.
>
> Betting better graphics support would be higher on the list (yea, the 
>other 'dropped' project).
>
>   Cheers!
>
>        ---- Randy
>
>> 
>> Sent from my iPhone
>> 
>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> My gut instinct is that this isn?t that interesting ? most everyone
>is running illumos in either VMs, or in datacenter
>> applications where suspend/resume has little if any applicability.
>> 
>> While the work itself is probably interesting, and it may enable new
>applications for illumos, the concern I?d have would be
>> detraction from other more pressing work, without any clear use cases
>for it.
>> 
>> That said, if someone (you?) wanted to spend cycles on this for
>personal satisfaction, I hardly see any reason to discourage it,
>> and I?m fairly certain if the risks of the new code being introduced
>are small (or well managed by sufficient testing for
>> example), I can?t see any other reason we would reject a suitably
>formed RTI.
>> 
>> Sent from Mail for Windows 10
>> 
>> From: randyf at sibernet.com
>> Sent: Tuesday, June 11, 2019 11:10 AM
>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>> Subject: [developer] suspend/resume in Illumos
>> 
>> I have a question for developers here:
>> 
>> ??? How important is suspend/resume for OI/Illumos (including S4)?
>> 
>> One of the incomplete projects left behind was S4 (lack of need, and
>a
>> 
>> hard to identify bug stifled it's integration).? It is non-trivial,
>and
>> 
>> needs updated s/r core code (added configuration and significant
>> 
>> restructuring, as well as likely assistance from developers
>knowlegable in
>> 
>> other Illumos internals), but if this is an uninteresting feature, it
>is
>> 
>> likey not worth the effort (recent bugs suggest that few if anyone
>use
>> 
>> it); however, it wouldn't be too hard to resurect (though would still
>take
>> 
>> several months of work).
>> 
>> ?? Cheers!
>> 
>> ??????? ---- Randy
>> 
>> illumos / illumos-developer / see discussions + participants +
>delivery options Permalink
>> 
>------------------------------------------
>illumos: illumos-developer
>Permalink:
>https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>Delivery options:
>https://illumos.topicbox.com/groups/developer/subscription

For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.

My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.

Jim

--
Typos courtesy of K-9 Mail on my Android



From jimklimov at cos.ru  Wed Jun 12 08:01:25 2019
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 12 Jun 2019 08:01:25 +0000
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>

On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>
>
>On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>
>> I?d say, anything to encourage people to try, use and join to develop
>[illumos] is very welcome. Better laptop support will definitely be
>> bonus.
>
> Betting better graphics support would be higher on the list (yea, the 
>other 'dropped' project).
>
>   Cheers!
>
>        ---- Randy
>
>> 
>> Sent from my iPhone
>> 
>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> My gut instinct is that this isn?t that interesting ? most everyone
>is running illumos in either VMs, or in datacenter
>> applications where suspend/resume has little if any applicability.
>> 
>> While the work itself is probably interesting, and it may enable new
>applications for illumos, the concern I?d have would be
>> detraction from other more pressing work, without any clear use cases
>for it.
>> 
>> That said, if someone (you?) wanted to spend cycles on this for
>personal satisfaction, I hardly see any reason to discourage it,
>> and I?m fairly certain if the risks of the new code being introduced
>are small (or well managed by sufficient testing for
>> example), I can?t see any other reason we would reject a suitably
>formed RTI.
>> 
>> Sent from Mail for Windows 10
>> 
>> From: randyf at sibernet.com
>> Sent: Tuesday, June 11, 2019 11:10 AM
>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>> Subject: [developer] suspend/resume in Illumos
>> 
>> I have a question for developers here:
>> 
>> ??? How important is suspend/resume for OI/Illumos (including S4)?
>> 
>> One of the incomplete projects left behind was S4 (lack of need, and
>a
>> 
>> hard to identify bug stifled it's integration).? It is non-trivial,
>and
>> 
>> needs updated s/r core code (added configuration and significant
>> 
>> restructuring, as well as likely assistance from developers
>knowlegable in
>> 
>> other Illumos internals), but if this is an uninteresting feature, it
>is
>> 
>> likey not worth the effort (recent bugs suggest that few if anyone
>use
>> 
>> it); however, it wouldn't be too hard to resurect (though would still
>take
>> 
>> several months of work).
>> 
>> ?? Cheers!
>> 
>> ??????? ---- Randy
>> 
>> illumos / illumos-developer / see discussions + participants +
>delivery options Permalink
>> 
>------------------------------------------
>illumos: illumos-developer
>Permalink:
>https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>Delivery options:
>https://illumos.topicbox.com/groups/developer/subscription

For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.

My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.

Jim

--
Typos courtesy of K-9 Mail on my Android



From aurelien.larcher at gmail.com  Mon Jun 17 11:26:59 2019
From: aurelien.larcher at gmail.com (=?UTF-8?Q?Aur=C3=A9lien_Larcher?=)
Date: Mon, 17 Jun 2019 13:26:59 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <20190611181011.GA18869@mail.messagingengine.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
Message-ID: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>

On Mon, Jun 17, 2019 at 11:59 AM Gary Mills <gary_mills at fastmail.fm> wrote:

> I'm part way through this long project now.  I began with v9os
> installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
> packages.  I've been building IPS packages from oi-userland source.
> This process has gotten easier now that all the build tools I need are
> in IPS packages.  I've been replacing v9os packages with oi-userland
> packages.  My goal is to replace all of them, and finally to produce a
> text ISO and package repository for SPARC that's entirely based on
> oi-userland.
>
> So far, I've built and packaged versions 5, 6, and 7 of the gcc
> compiler.  The commands for IPS packages are all packaged for python
> 2.7.  My system now has 106 packages installed from oi-userland,
> versus 343 packages from v9os.  Most of the oi-userland products
> required very few or no changes to build and package for SPARC.
>
> For perl, I've removed the 5.16.1 version from v9os and installed
> versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
> removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
> packaged for 5.22.  Python libraries are all packaged for 2.7.
>
> I'm submitting this message to the mailing list mostly as a progress
> report.  I would, of course, appreciate a bit of help with this
> project.
>

Congratulations Gary this is great :)
If we get to the point that we can setup a build machine this would secure
your work.
Kind regards

Aur?lien



>
>
> --
> -Gary Mills-            -refurb-                -Winnipeg, Manitoba,
> Canada-
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


-- 
---
Praise the Caffeine embeddings
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190617/a222a8e2/attachment-0004.html>

From toasterson at gmail.com  Mon Jun 17 15:33:53 2019
From: toasterson at gmail.com (=?UTF-8?Q?Till_Wegm=c3=bcller?=)
Date: Mon, 17 Jun 2019 17:33:53 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
Message-ID: <63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com>

Hi Gary

Thank you so much for this Work. I don't personaly use sparc but ir is
good to see people doing this kinds of projects.

Do you know about Agnar's Project to get OI building on SPARC? I can't
remember if I ever pointed you towards him and his OI on Sparc work. His
angle was to jump from an existing OI distro to current packages and
later looking in V9OS.

Greetings
Till

On 17.06.19 13:26, Aur?lien Larcher wrote:
> 
> 
> On Mon, Jun 17, 2019 at 11:59 AM Gary Mills <gary_mills at fastmail.fm
> <mailto:gary_mills at fastmail.fm>> wrote:
> 
>     I'm part way through this long project now.? I began with v9os
>     installed on a Sun T2000.? v9os is a SPARC distribution that uses IPS
>     packages.? I've been building IPS packages from oi-userland source.
>     This process has gotten easier now that all the build tools I need are
>     in IPS packages.? I've been replacing v9os packages with oi-userland
>     packages.? My goal is to replace all of them, and finally to produce a
>     text ISO and package repository for SPARC that's entirely based on
>     oi-userland.
> 
>     So far, I've built and packaged versions 5, 6, and 7 of the gcc
>     compiler.? The commands for IPS packages are all packaged for python
>     2.7.? My system now has 106 packages installed from oi-userland,
>     versus 343 packages from v9os.? Most of the oi-userland products
>     required very few or no changes to build and package for SPARC.
> 
>     For perl, I've removed the 5.16.1 version from v9os and installed
>     versions 5.22 and 5.24 from oi-userland.? Likewise, for python, I've
>     removed 2.6 and installed 2.7 and 3.4.? Perl libraries are all
>     packaged for 5.22.? Python libraries are all packaged for 2.7.
> 
>     I'm submitting this message to the mailing list mostly as a progress
>     report.? I would, of course, appreciate a bit of help with this
>     project.
> 
> 
> Congratulations Gary this is great :)
> If we get to the point that we can setup a build machine this would
> secure your work.
> Kind regards
> 
> Aur?lien
> 
> ?
> 
> 
> 
>     -- 
>     -Gary Mills-? ? ? ? ? ? -refurb-? ? ? ? ? ? ? ? -Winnipeg, Manitoba,
>     Canada-
> 
>     _______________________________________________
>     oi-dev mailing list
>     oi-dev at openindiana.org <mailto:oi-dev at openindiana.org>
>     https://openindiana.org/mailman/listinfo/oi-dev
> 
> 
> 
> -- 
> ---
> Praise the Caffeine embeddings
> 
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
> 



From olbohlen at eenfach.de  Tue Jun 18 19:25:07 2019
From: olbohlen at eenfach.de (Olaf Bohlen)
Date: Tue, 18 Jun 2019 21:25:07 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com> ("Till
	=?utf-8?Q?Wegm=C3=BCller=22's?= message of "Mon, 17 Jun 2019 17:33:53
	+0200")
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
	<63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com>
Message-ID: <x6pnnavgq4.fsf@eenfach.de>

Till Wegm?ller <toasterson at gmail.com> writes:

Hi Till,
hi Gary,

> Do you know about Agnar's Project to get OI building on SPARC? I can't
> remember if I ever pointed you towards him and his OI on Sparc work. His
> angle was to jump from an existing OI distro to current packages and
> later looking in V9OS.

First: Gary, this is phantastic news, congrats to it! I'm looking
forward to hear more from you.

Second: Till, yes Gary and I have been in contact but since I have
not enough time, my progress is probably somewhat slower. I also
have newer bits running, but my approach is - as you mentioned -
doing bootstrapping a system to be able to build recent bits in
the correct way.

I'd be happy to hear once someone has built a bootable OI media
for sparc and would take up of these also.

Best regards,

-- 
      ~       Olaf Bohlen - olbohlen at eenfach.de
      |~~     Het
     /|  \    Bruine
 ___/_|___\   Leven
   \__n____/# DGCN2



From Tim.Mooney at ndsu.edu  Mon Jun 24 02:24:33 2019
From: Tim.Mooney at ndsu.edu (Tim Mooney)
Date: Sun, 23 Jun 2019 21:24:33 -0500 (CDT)
Subject: [oi-dev] component TODO list for perl components?
Message-ID: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,

 	https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164



From alp at sfedu.ru  Mon Jun 24 06:05:50 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 06:05:50 +0000
Subject: [oi-dev] component TODO list for perl components?
In-Reply-To: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
References: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
Message-ID: <AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.

I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/ some time ago. There are mostly tasks which I'm interested in.

Now I'm looking at removing binary blobs from DDU. Later I'll likely look at switching it to Python 3.5.

If you can propose any tasks which you can take (or pehaps, someone else), feel  free to update this page. I just don't want it to become a list of never-done tasks.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Tim Mooney <Tim.Mooney at ndsu.edu>
??????????: 24 ???? 2019 ?. 5:24:33
????: oi-dev at openindiana.org
????: [oi-dev] component TODO list for perl components?


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,

        https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
--
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



From garrett at damore.org  Mon Jun 24 14:42:34 2019
From: garrett at damore.org (Garrett D'Amore)
Date: Mon, 24 Jun 2019 07:42:34 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <DE25905A-0071-4339-B00A-9EB1D62CC5AB@gmail.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
	<699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>
	<DE25905A-0071-4339-B00A-9EB1D62CC5AB@gmail.com>
Message-ID: <5d10e157.1c69fb81.48b1c.91f9@mx.google.com>

That?s only true if you?re running on  a hypervisor that uses suspend / resume for live migration.  I?m not sure how widespread running illumos on VMware is ? the absence of suspend/resume support means that nobody is benefiting from this particular capability today (at least with illumos).

Sent from Mail for Windows 10

From: DavidHalko
Sent: Monday, June 24, 2019 5:18 AM
To: illumos-developer
Cc: randyf at sibernet.com; oi-dev at openindiana.org
Subject: Re: [developer] suspend/resume in Illumos

Suspend and Resume is critical for live migration in a data center with external storage to reduce schedules downtime incurred with firmware updates to maintain a secure platform.

Thanks, David Halko
http://netmgt.blogspot.com/

Sent from my iPhone

> On Jun 12, 2019, at 4:01 AM, Jim Klimov <jimklimov at cos.ru> wrote:
> 
>> On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>> 
>> 
>>> On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>>> 
>>> I?d say, anything to encourage people to try, use and join to develop
>> [illumos] is very welcome. Better laptop support will definitely be
>>> bonus.
>> 
>> Betting better graphics support would be higher on the list (yea, the 
>> other 'dropped' project).
>> 
>>  Cheers!
>> 
>>       ---- Randy
>> 
>>> 
>>> Sent from my iPhone
>>> 
>>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>>> 
>>> My gut instinct is that this isn?t that interesting ? most everyone
>> is running illumos in either VMs, or in datacenter
>>> applications where suspend/resume has little if any applicability.
>>> 
>>> While the work itself is probably interesting, and it may enable new
>> applications for illumos, the concern I?d have would be
>>> detraction from other more pressing work, without any clear use cases
>> for it.
>>> 
>>> That said, if someone (you?) wanted to spend cycles on this for
>> personal satisfaction, I hardly see any reason to discourage it,
>>> and I?m fairly certain if the risks of the new code being introduced
>> are small (or well managed by sufficient testing for
>>> example), I can?t see any other reason we would reject a suitably
>> formed RTI.
>>> 
>>> Sent from Mail for Windows 10
>>> 
>>> From: randyf at sibernet.com
>>> Sent: Tuesday, June 11, 2019 11:10 AM
>>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>>> Subject: [developer] suspend/resume in Illumos
>>> 
>>> I have a question for developers here:
>>> 
>>>     How important is suspend/resume for OI/Illumos (including S4)?
>>> 
>>> One of the incomplete projects left behind was S4 (lack of need, and
>> a
>>> 
>>> hard to identify bug stifled it's integration).  It is non-trivial,
>> and
>>> 
>>> needs updated s/r core code (added configuration and significant
>>> 
>>> restructuring, as well as likely assistance from developers
>> knowlegable in
>>> 
>>> other Illumos internals), but if this is an uninteresting feature, it
>> is
>>> 
>>> likey not worth the effort (recent bugs suggest that few if anyone
>> use
>>> 
>>> it); however, it wouldn't be too hard to resurect (though would still
>> take
>>> 
>>> several months of work).
>>> 
>>>    Cheers!
>>> 
>>>         ---- Randy
>>> 
>>> illumos / illumos-developer / see discussions + participants +
>> delivery options Permalink
>> ------------------------------------------
>> illumos: illumos-developer
>> Permalink:
>> https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>> Delivery options:
>> https://illumos.topicbox.com/groups/developer/subscription
> 
> For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.
> 
> My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.
> 
> Jim
> 
> --
> Typos courtesy of K-9 Mail on my Android

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M87936b070d0aa9c1490f0794
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190624/7192fbe4/attachment-0004.html>

From alp at sfedu.ru  Mon Jun 24 15:12:45 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 15:12:45 +0000
Subject: [oi-dev] DDU testing
Message-ID: <AM6PR05MB6198AE59E0359DD5E878CCAFCFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.

I've finished replacing DDU binaries with binaries from DDU 1.2 and rewriting missing parts. 
Result is here: https://github.com/OpenIndiana/ddu/ .
I suggest it can get wider testing.
You can use openindiana/ddu component  from https://github.com/OpenIndiana/oi-userland/pull/5103 to build and test it. 

I'm waiting for test results and reviews.

Changes from current DDU (shipped with OI now).
1) pt_BR localization files removed as msgunfmt couldn't unparse them;
2) Database of third-party drivers was removed (it was obsolete  with it seems one working link from dozen). I suppose nobody volunteers to support it in actual state.
3) I hope finally I've made DDU help behave - now it shows help in user locale, images are not removed.
4) I've regenerated database of existing OI drivers shipped with DDU, updated pci.ids and usb.ids files.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???




From gary_mills at fastmail.fm  Mon Jun 24 15:33:31 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Mon, 24 Jun 2019 10:33:31 -0500
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
Message-ID: <20190624153331.GA28009@mail.messagingengine.com>

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aur?lien Larcher wrote:
> 
>    Congratulations Gary this is great :)
>    If we get to the point that we can setup a build machine this would
>    secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From alp at sfedu.ru  Mon Jun 24 16:02:51 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 16:02:51 +0000
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <20190624153331.GA28009@mail.messagingengine.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>,
	<20190624153331.GA28009@mail.messagingengine.com>
Message-ID: <AM6PR05MB619883D7A53C05872643155DCFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

BTW, while working on DDU I've removed SPARC parts I've encountered ;)
Anyway I had no way (or desire) to test them.
Most interesting is likely dmi_info.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Gary Mills <gary_mills at fastmail.fm>
??????????: 24 ???? 2019 ?. 18:33
????: OpenIndiana Developer mailing list
????: Re: [oi-dev] Toward a SPARC distro of OI

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aur?lien Larcher wrote:
>
>    Congratulations Gary this is great :)
>    If we get to the point that we can setup a build machine this would
>    secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


--
-Gary Mills-            -refurb-                -Winnipeg, Manitoba, Canada-

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

From Tim.Mooney at ndsu.edu  Mon Jun 24 18:24:09 2019
From: Tim.Mooney at ndsu.edu (Tim Mooney)
Date: Mon, 24 Jun 2019 13:24:09 -0500 (CDT)
Subject: [oi-dev] component TODO list for perl components?
In-Reply-To: <AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>
References: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
	<AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>
Message-ID: <alpine.SOC.2.20.1906241317080.14673@dogbert.cc.ndsu.NoDak.edu>

In regard to: Re: [oi-dev] component TODO list for perl components?,...:

> I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/
> some time ago. There are mostly tasks which I'm interested in.
>
> Now I'm looking at removing binary blobs from DDU. Later I'll likely
> look at switching it to Python 3.5.
>
> If you can propose any tasks which you can take (or pehaps, someone
> else), feel  free to update this page. I just don't want it to become a
> list of never-done tasks.

Thanks Alexander, and I understand completely about a list of never-done
tasks.

I'll open a pull request with some proposed updates, and you and others
can comment on whether they're a good idea or not.

Tim

> ________________________________________
> ??: Tim Mooney <Tim.Mooney at ndsu.edu>
> ??????????: 24 ???? 2019 ?. 5:24:33
> ????: oi-dev at openindiana.org
> ????: [oi-dev] component TODO list for perl components?
>
>
> I've been considering packaging the latest stable perl5, 5.30.0, as
> perl-530 and then packaging (and in some cases, updating) the perl
> modules that are part of hipster, but I want to make certain I'm not
> working at cross-purposes to any planned updates for OI and that this
> type of update is actually useful.
>
> There's a checklist of small/easy changes to make when updating a
> component,
>
>        https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md
>
> but is there a list of the bigger packaging tasks, perhaps prioritized by
> need?  Obviously people volunteering their time are going to work on
> things that interest them, benefit them, and are within their ability,
> but at times it would be helpful to know what the most pressing packaging
> needs are.
>
> I'm happy to continue choosing components kind of at random to update, but
> if I have a list of easy (but perhaps tedious) packaging tasks that are
> priorities for update in OI, I would probably attempt some of them as I
> have time, especially if it frees up more time for core contributors to
> work on the more difficult tasks.
>
> Does a list like that exist?  Those types of things tend to go stale fast,
> so I understand if there isn't one.
>
> Tim
> --
> Tim Mooney                                             Tim.Mooney at ndsu.edu
> Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
> Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>

-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

From gary_mills at fastmail.fm  Tue Jun 25 20:47:20 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 25 Jun 2019 15:47:20 -0500
Subject: [oi-dev] Am I stuck?
Message-ID: <20190625204720.GA8601@mail.messagingengine.com>

These are my publishers:

    # pkg publisher                      
    PUBLISHER                   TYPE     STATUS P LOCATION
    oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
    v9os           (non-sticky) origin   online F file:///data/ips/

I just published all of illumos-gate to the oi-userland repository.
There are now two copies of the
consolidation/osnet/osnet-incorporation package.  This is the
installed one:

    # pkg info consolidation/osnet/osnet-incorporation
              Name: consolidation/osnet/osnet-incorporation
           Summary: OS/Net consolidation incorporation
       Description: This incorporation constrains packages from the OS/Net
                    consolidation.
             State: Installed
         Publisher: v9os
           Version: 0.5.11
            Branch: 0.151100
    Packaging Date: Wed Jul 27 07:12:37 2016
              Size: 0.00 B
              FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
    
This is the new one:

    # pkg info -r consolidation/osnet/osnet-incorporation
              Name: consolidation/osnet/osnet-incorporation
           Summary: OS/Net consolidation incorporation
       Description: This incorporation constrains packages from the OS/Net
                    consolidation.
             State: Not installed
         Publisher: oi-userland
           Version: 0.5.11
            Branch: 2018.0.0.0
    Packaging Date: Sun Jun 23 22:35:19 2019
              Size: 0.00 B
              FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z

I expected that `pkg update -nv' would offer to remove the installed
incorporation and replace all of the old illumos-gate packages, over
200 of them, with the new illumos-gate packages.  It didn't do that.
It did report that it would replace ten packages from the v9os
publisher with newer versions from the oi-userland publisher, but this
list didn't include any of the illumos-gate packages.

When I tried to remove the incorporation with pkg, I got this result:

    # pkg uninstall -nv consolidation/osnet/osnet-incorporation
    Creating Plan (Solver setup): -
    pkg uninstall: Unable to remove 'consolidation/osnet/osnet-incorporation at 0.5.11-0.151100' due to the following packages that depend on it:
      SUNWcs at 0.5.11-0.151100
      SUNWcsd at 0.5.11-0.151100
      compatibility/ucb at 0.5.11-0.151100
      developer/astdev at 0.5.11-0.151100
    ...
      system/zones at 0.5.11-0.151100
      system/zones/internal at 0.5.11-0.151100
      text/doctools at 0.5.11-0.151100
      text/locale at 0.5.11-0.151100

Have I run into a dead end, or is there a way out of this dilemma?


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From vab at bb-c.de  Tue Jun 25 21:01:31 2019
From: vab at bb-c.de (Volker A. Brandt)
Date: Tue, 25 Jun 2019 23:01:31 +0200
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190625204720.GA8601@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
Message-ID: <23826.35755.98828.321659@shelob.bb-c.de>

Hi Gary!


> These are my publishers:
> 
>     # pkg publisher                      
>     PUBLISHER                   TYPE     STATUS P LOCATION
>     oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
>     v9os           (non-sticky) origin   online F file:///data/ips/
> 
> I just published all of illumos-gate to the oi-userland repository.
> There are now two copies of the
> consolidation/osnet/osnet-incorporation package.  This is the
> installed one:
> 
>     # pkg info consolidation/osnet/osnet-incorporation
>               Name: consolidation/osnet/osnet-incorporation
>            Summary: OS/Net consolidation incorporation
>        Description: This incorporation constrains packages from the OS/Net
>                     consolidation.
>              State: Installed
>          Publisher: v9os
>            Version: 0.5.11
>             Branch: 0.151100
>     Packaging Date: Wed Jul 27 07:12:37 2016
>               Size: 0.00 B
>               FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
>     
> This is the new one:
> 
>     # pkg info -r consolidation/osnet/osnet-incorporation
>               Name: consolidation/osnet/osnet-incorporation
>            Summary: OS/Net consolidation incorporation
>        Description: This incorporation constrains packages from the OS/Net
>                     consolidation.
>              State: Not installed
>          Publisher: oi-userland
>            Version: 0.5.11
>             Branch: 2018.0.0.0
>     Packaging Date: Sun Jun 23 22:35:19 2019
>               Size: 0.00 B
>               FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z
> 
> I expected that `pkg update -nv' would offer to remove the installed
> incorporation and replace all of the old illumos-gate packages, over
> 200 of them, with the new illumos-gate packages.  It didn't do that.
> It did report that it would replace ten packages from the v9os
> publisher with newer versions from the oi-userland publisher, but this
> list didn't include any of the illumos-gate packages.

So it appears that pkg does not recognize the fact that version
0.5.11-2018.0.0.0:20190623T223519Z is newer than version
0.5.11-0.151100:20160727T071237Z -- correct?

> When I tried to remove the incorporation with pkg, I got this result:
[...]

I don't think that you are supposed to be able to remove the package
altogether.  You should, hovewer, be able to update it.

Do you also have an "entire" package?  If so, what version does it
have?


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt        Consulting and Support for Solaris-based Systems
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"



From gary_mills at fastmail.fm  Wed Jun 26 00:31:04 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 25 Jun 2019 19:31:04 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <23826.35755.98828.321659@shelob.bb-c.de>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
Message-ID: <20190626003104.GA10000@mail.messagingengine.com>

On Tue, Jun 25, 2019 at 11:01:31PM +0200, Volker A. Brandt wrote:
> 
> So it appears that pkg does not recognize the fact that version
> 0.5.11-2018.0.0.0:20190623T223519Z is newer than version
> 0.5.11-0.151100:20160727T071237Z -- correct?

I don't think that that is the problem.  Consider this transcript:

    # pkg update -nv
    ...
    Changed packages:
    ...
    v9os -> oi-userland
      archiver/gnu-tar
        1.28-0.151100 -> 1.29-2018.0.0.0
      compress/bzip2
        1.0.6-0.151100 -> 1.0.6-2018.0.0.3
      compress/gzip
        1.6-0.151100 -> 1.9-2018.0.0.0

The version numbers were the same for the last two packages.

> > When I tried to remove the incorporation with pkg, I got this result:
> [...]
> 
> I don't think that you are supposed to be able to remove the package
> altogether.  You should, hovewer, be able to update it.

That's close to working.  I should be able to make it work.
Here's this one:

    # pkg update -nv pkg://oi-userland/consolidation/osnet/osnet-inco...
    Creating Plan (Solver setup): \
    pkg update: No matching version of consolidation/osnet/osnet-incorporation can be installed:
      Reject:  pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0
      Reason:  No version matching 'incorporate' dependency SUNWcs at 0.5.11-2018.0.0.0 can be installed
        ----------------------------------------
        Reject:  pkg://oi-userland/SUNWcs at 0.5.11-2018.0.0.0
        Reason:  No version matching 'require' dependency system/network/mailwrapper can be installed
          ----------------------------------------
          Reject:  pkg://oi-userland/system/network/mailwrapper at 0.5.11-2018.0.0.0
          Reason:  No version for 'require' dependency on system/mta can be found
          Reject:  pkg://v9os/system/network/mailwrapper at 0.5.11-0.151100
          Reason:  Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation'
          ----------------------------------------
        ----------------------------------------

> Do you also have an "entire" package?  If so, what version does it
> have?

No, I don't have that package.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From naj at snapcon.com  Wed Jun 26 00:28:12 2019
From: naj at snapcon.com (Norm Jacobs)
Date: Tue, 25 Jun 2019 19:28:12 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190625204720.GA8601@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
Message-ID: <1bba6380-a729-e329-a326-0fd1aa7572fb@snapcon.com>

You might look at the 'entire' package and see if it constrains the 
'osnet-incorporation to the older version.? That is most likely the 
cause of your trouble.? You can probably remove the 'entire' package and 
then update.? You might also be able to unlock the incorporation before 
upgrading instead.

 ??? -Norm


On 6/25/19 3:47 PM, Gary Mills wrote:
> These are my publishers:
>
>      # pkg publisher
>      PUBLISHER                   TYPE     STATUS P LOCATION
>      oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
>      v9os           (non-sticky) origin   online F file:///data/ips/
>
> I just published all of illumos-gate to the oi-userland repository.
> There are now two copies of the
> consolidation/osnet/osnet-incorporation package.  This is the
> installed one:
>
>      # pkg info consolidation/osnet/osnet-incorporation
>                Name: consolidation/osnet/osnet-incorporation
>             Summary: OS/Net consolidation incorporation
>         Description: This incorporation constrains packages from the OS/Net
>                      consolidation.
>               State: Installed
>           Publisher: v9os
>             Version: 0.5.11
>              Branch: 0.151100
>      Packaging Date: Wed Jul 27 07:12:37 2016
>                Size: 0.00 B
>                FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
>      
> This is the new one:
>
>      # pkg info -r consolidation/osnet/osnet-incorporation
>                Name: consolidation/osnet/osnet-incorporation
>             Summary: OS/Net consolidation incorporation
>         Description: This incorporation constrains packages from the OS/Net
>                      consolidation.
>               State: Not installed
>           Publisher: oi-userland
>             Version: 0.5.11
>              Branch: 2018.0.0.0
>      Packaging Date: Sun Jun 23 22:35:19 2019
>                Size: 0.00 B
>                FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z
>
> I expected that `pkg update -nv' would offer to remove the installed
> incorporation and replace all of the old illumos-gate packages, over
> 200 of them, with the new illumos-gate packages.  It didn't do that.
> It did report that it would replace ten packages from the v9os
> publisher with newer versions from the oi-userland publisher, but this
> list didn't include any of the illumos-gate packages.
>
> When I tried to remove the incorporation with pkg, I got this result:
>
>      # pkg uninstall -nv consolidation/osnet/osnet-incorporation
>      Creating Plan (Solver setup): -
>      pkg uninstall: Unable to remove 'consolidation/osnet/osnet-incorporation at 0.5.11-0.151100' due to the following packages that depend on it:
>        SUNWcs at 0.5.11-0.151100
>        SUNWcsd at 0.5.11-0.151100
>        compatibility/ucb at 0.5.11-0.151100
>        developer/astdev at 0.5.11-0.151100
>      ...
>        system/zones at 0.5.11-0.151100
>        system/zones/internal at 0.5.11-0.151100
>        text/doctools at 0.5.11-0.151100
>        text/locale at 0.5.11-0.151100
>
> Have I run into a dead end, or is there a way out of this dilemma?
>
>



From richlowe at richlowe.net  Wed Jun 26 00:42:41 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Tue, 25 Jun 2019 20:42:41 -0400
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190626003104.GA10000@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
	<20190626003104.GA10000@mail.messagingengine.com>
Message-ID: <CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>

Reason:  No version for 'require' dependency on system/mta can be found

Seems a leaf failure, does one really not exist?



From gary_mills at fastmail.fm  Wed Jun 26 12:52:41 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Wed, 26 Jun 2019 07:52:41 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
	<20190626003104.GA10000@mail.messagingengine.com>
	<CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>
Message-ID: <20190626125240.GA12540@mail.messagingengine.com>

On Tue, Jun 25, 2019 at 08:42:41PM -0400, Richard Lowe wrote:
> Reason:  No version for 'require' dependency on system/mta can be found
> 
> Seems a leaf failure, does one really not exist?

Indeed, the package system/mta does not exist in either publisher.  I
just published it to oi-userland and installed it.  My next task is to
see if that missing package was preventing the update.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From gordon.w.ross at gmail.com  Fri Jun 28 04:25:37 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 27 Jun 2019 21:25:37 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
Message-ID: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>

Any ideas what I should do to fix this?

root at oi-dev:/home/gwr# pkg -R /mnt image-update -v
Creating Plan (Running solver): /
pkg update: No solution was found to satisfy constraints
No solution found to update to latest available versions.
This may indicate an overly constrained set of packages are installed.

latest incorporations:

  pkg://openindiana.org/consolidation/install/install-incorporation at 0.5.11,5.11-2018.0.0.1041:20190516T142943Z
  pkg://openindiana.org/consolidation/l10n/l10n-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014527Z
  pkg://openindiana.org/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014529Z
  pkg://openindiana.org/consolidation/userland/userland-incorporation at 0.5.11,5.11-2018.0.0.11903:20190627T091450Z

Dependency analysis is unable to determine the cause.
Try specifying expected versions to obtain more detailed error messages.

On Sun, May 12, 2019 at 12:33 AM Alexander Pyhalov via oi-dev
<oi-dev at openindiana.org> wrote:
>
> Sorry, missed dot in
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso link.
>
> ? ?????????,
> ????????? ???????,
> ??????????? ?????? ???????????????????? ??????????????
> ?????????? ?????????????-???????????????? ?????????????? ???
>
>
> ________________________________________
> ??: Alexander Pyhalov via oi-dev <oi-dev at openindiana.org>
> ??????????: 12 ??? 2019 ?. 10:11:57
> ????: OpenIndiana Developer mailing list
> ?????: Alexander Pyhalov
> ????: [oi-dev] OI Hipster 2019.04
>
> Hi.
>
> OI Hipster 2019.04 snapshot is ready.
>
> Images:
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb
>
>
> SHA 256 checksums are available at ${link}.sha256sum
> Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
> https://sks-keyservers.net/pks/lookup?op=get&search=0x3A021AFADBE31887 ).
>
> Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes
>
> Note, we have an issue with Firefox on live image - it can fail to start correctly when launched for the first time in memory-constrained  environment. After being killed and restarted it behaves more sane.
>
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



From gordon.w.ross at gmail.com  Fri Jun 28 04:26:44 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 27 Jun 2019 21:26:44 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
Message-ID: <CAD0Ztp2nrGdb3t2sKjUdR9HNNwdSJ_t=eJs=6UBesB2Uo=+wtA@mail.gmail.com>

I'm guessing people will want to see:

root at oi-dev:/home/gwr# pkg -R /mnt publisher
PUBLISHER                   TYPE     STATUS P LOCATION
openindiana.org              origin   online F
http://pkg.openindiana.org/hipster/
root at oi-dev:/home/gwr# pkg -R /mnt info entire
          Name: entire
       Summary: incorporation to lock all system packages to same build (empty
                package)
   Description: incorporation to lock all system packages to same build (empty
                package)
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
        Branch: 2018.0.0.0
Packaging Date: February 11, 2018 at 01:10:12 PM
          Size: 0.00 B
          FMRI: pkg://openindiana.org/entire at 0.5.11-2018.0.0.0:20180211T131012Z

On Thu, Jun 27, 2019 at 9:25 PM Gordon Ross <gordon.w.ross at gmail.com> wrote:
>
> Any ideas what I should do to fix this?
>
> root at oi-dev:/home/gwr# pkg -R /mnt image-update -v
> Creating Plan (Running solver): /
> pkg update: No solution was found to satisfy constraints
> No solution found to update to latest available versions.
> This may indicate an overly constrained set of packages are installed.
>
> latest incorporations:
>
>   pkg://openindiana.org/consolidation/install/install-incorporation at 0.5.11,5.11-2018.0.0.1041:20190516T142943Z
>   pkg://openindiana.org/consolidation/l10n/l10n-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014527Z
>   pkg://openindiana.org/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014529Z
>   pkg://openindiana.org/consolidation/userland/userland-incorporation at 0.5.11,5.11-2018.0.0.11903:20190627T091450Z
>
> Dependency analysis is unable to determine the cause.
> Try specifying expected versions to obtain more detailed error messages.
>
> On Sun, May 12, 2019 at 12:33 AM Alexander Pyhalov via oi-dev
> <oi-dev at openindiana.org> wrote:
> >
> > Sorry, missed dot in
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso link.
> >
> > ? ?????????,
> > ????????? ???????,
> > ??????????? ?????? ???????????????????? ??????????????
> > ?????????? ?????????????-???????????????? ?????????????? ???
> >
> >
> > ________________________________________
> > ??: Alexander Pyhalov via oi-dev <oi-dev at openindiana.org>
> > ??????????: 12 ??? 2019 ?. 10:11:57
> > ????: OpenIndiana Developer mailing list
> > ?????: Alexander Pyhalov
> > ????: [oi-dev] OI Hipster 2019.04
> >
> > Hi.
> >
> > OI Hipster 2019.04 snapshot is ready.
> >
> > Images:
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb
> >
> >
> > SHA 256 checksums are available at ${link}.sha256sum
> > Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> > The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
> > https://sks-keyservers.net/pks/lookup?op=get&search=0x3A021AFADBE31887 ).
> >
> > Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes
> >
> > Note, we have an issue with Firefox on live image - it can fail to start correctly when launched for the first time in memory-constrained  environment. After being killed and restarted it behaves more sane.
> >
> > Best regards,
> > Alexander Pyhalov,
> > system administrator of Southern Federal University IT department
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev



From richlowe at richlowe.net  Fri Jun 28 05:28:15 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Fri, 28 Jun 2019 01:28:15 -0400
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
Message-ID: <CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>

> Dependency analysis is unable to determine the cause.
> Try specifying expected versions to obtain more detailed error messages.
>

Do what it says there,

Specify the verisons of those 'latest incorporations', and probably
also entire, including the versions.

You may be able to just do 'pkg install -nv entire at latest' but I can
never remember whether only specifying 'entire' does the right thing.



From gordon.w.ross at gmail.com  Fri Jun 28 17:32:25 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Fri, 28 Jun 2019 10:32:25 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
Message-ID: <CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>

OK, but I can't seem to find the latest version of entire.
Can anyone tell me what that should be?

root at oi-dev:/home/gwr# pkg -R /mnt refresh --full
root at oi-dev:/home/gwr# pkg -R /mnt update -nv entire at latest
No updates available for this image.
root at oi-dev:/home/gwr# pkg -R /mnt install -nv entire at latest
No updates necessary for this image.
root at oi-dev:/home/gwr# pkg -R /mnt info entire
          Name: entire
       Summary: incorporation to lock all system packages to same build (empty
                package)
   Description: incorporation to lock all system packages to same build (empty
                package)
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
        Branch: 2018.0.0.0
Packaging Date: February 11, 2018 at 01:10:12 PM
          Size: 0.00 B
          FMRI: pkg://openindiana.org/entire at 0.5.11-2018.0.0.0:20180211T131012Z

On Thu, Jun 27, 2019 at 10:28 PM Richard Lowe <richlowe at richlowe.net> wrote:
>
> > Dependency analysis is unable to determine the cause.
> > Try specifying expected versions to obtain more detailed error messages.
> >
>
> Do what it says there,
>
> Specify the verisons of those 'latest incorporations', and probably
> also entire, including the versions.
>
> You may be able to just do 'pkg install -nv entire at latest' but I can
> never remember whether only specifying 'entire' does the right thing.
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



From richlowe at richlowe.net  Fri Jun 28 17:43:23 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Fri, 28 Jun 2019 13:43:23 -0400
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
	<CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>
Message-ID: <CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?



From alp at sfedu.ru  Sat Jun 29 05:37:26 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Sat, 29 Jun 2019 05:37:26 +0000
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
	<CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>,
	<CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>
Message-ID: <AM6PR05MB6198F5838BDA1D994F326236CFFF0@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.
entire is a package which depends on userland-incorporation. That's all. You are interested in latest osnet-incorporation and userland-incorporation.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Richard Lowe <richlowe at richlowe.net>
??????????: 28 ???? 2019 ?. 20:43
????: OpenIndiana Developer mailing list
????: Re: [oi-dev] OI Hipster 2019.04

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



From grzemba at contac-dt.de  Mon Jun  3 14:44:26 2019
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Mon, 03 Jun 2019 16:44:26 +0200
Subject: [oi-dev] Openindiana on Laptop: touchpad not working
In-Reply-To: <bd3e8f4829c5.5ce65b00@contac-dt.de>
References: <be86e6074ec1.5ce41f99@contac-dt.de>
	<alpine.GSO.2.20.1905211010220.7749@scrappy.simplesystems.org>
	<bd3e8f4829c5.5ce65b00@contac-dt.de>
Message-ID: <bd3d30256aff.5cf54e6a@contac-dt.de>


<signaturebeforequotedtext></signaturebeforequotedtext>
On 23.05.19 08:34, Carsten Grzemba via oi-dev  <oi-dev at openindiana.org> wrote: 
> 
> I compared the Xorg log:
> 
> in the working log the mouse driver is loaded on PS/s mouse on /dev/mouse:
> 
> [ 38.008] (II) LoadModule: "mouse"
> [ 38.008] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> [ 38.012] (II) Module mouse: vendor="X.Org Foundation"
> [ 38.012] compiled for 1.19.5, module version = 1.9.2
> [ 38.012] Module class: X.Org XInput Driver
> [ 38.012] ABI class: X.Org XInput driver, version 24.1
> [ 38.012] (II) Using input driver 'mouse' for 'PS/2 Port for PS/2-style Mice'
> [ 38.012] (**) PS/2 Port for PS/2-style Mice: always reports core events
> [ 38.012] (**) Option "Device" "/dev/mouse"
> [ 38.012] (II) PS/2 Port for PS/2-style Mice: Setting Device option to "/dev/mouse"
> [ 38.014] (==) PS/2 Port for PS/2-style Mice: Protocol: "VUID"
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: always reports core events
> [ 38.014] (**) Option "Device" "/dev/mouse"
> [ 38.014] (==) PS/2 Port for PS/2-style Mice: Emulate3Buttons, Emulate3Timeout: 50
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: ZAxisMapping: buttons 4 and 5
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: Buttons: 9
> [ 38.014] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/isa_1f/i8042_1_60/mouse_1_0_logicaldev_input"
> [ 38.014] (II) XINPUT: Adding extended input device "PS/2 Port for PS/2-style Mice" (type: MOUSE, id 6)
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) keeping acceleration scheme 1
> [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration profile 0
> [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration factor: 2.000
> [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration threshold: 4
> 
> and the not working on the generic USB device /dev/usb/hid1:
> 
> [ 523.036] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> [ 523.036] (II) Module mouse: vendor="X.Org Foundation"
> [ 523.036] compiled for 1.19.5, module version = 1.9.2
> [ 523.036] Module class: X.Org XInput Driver
> [ 523.037] ABI class: X.Org XInput driver, version 24.1
> [ 523.037] (II) Using input driver 'mouse' for 'mouse'
> [ 523.037] (**) mouse: always reports core events
> [ 523.037] (**) Option "Protocol" "VUID"
> [ 523.037] (**) Option "Device" "/dev/usb/hid1"
> [ 523.037] (**) Option "StreamsModule" "usbms"
> [ 523.039] (**) mouse: Protocol: "VUID"
> [ 523.039] (**) mouse: always reports core events
> [ 523.039] (==) mouse: Emulate3Buttons, Emulate3Timeout: 50
> [ 523.039] (**) mouse: ZAxisMapping: buttons 4 and 5
> [ 523.039] (**) mouse: Buttons: 9
> [ 523.039] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1025_1019_14/device_4/mouse_1_if1_4_logicaldev_input"
> [ 523.039] (II) XINPUT: Adding extended input device "mouse" (type: MOUSE, id 6)
> [ 523.039] (**) mouse: (accel) keeping acceleration scheme 1
> [ 523.039] (**) mouse: (accel) acceleration profile 0
> [ 523.039] (**) mouse: (accel) acceleration factor: 2.000
> [ 523.039] (**) mouse: (accel) acceleration threshold: 4
> [ 523.045] (II) config/hal: Adding input device hotkey
> 
> 
> in both cases is the the touchpad avail and a extern USB mouse connected. the /dev/mouse dev link is in both BE targeted to /devices/pseudo/cons at 0:mouse
> 
> 
Still no luck with the latest hipster on my laptop:

scanpci:
pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1604
?Intel Corporation Broadwell-U Host Bridge -OPI

pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1616
?Intel Corporation HD Graphics 5500

pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x160c
?Intel Corporation Broadwell-U Audio Controller

pci bus 0x0000 cardnum 0x14 function 0x00: vendor 0x8086 device 0x9cb1
?Intel Corporation Wildcat Point-LP USB xHCI Controller

pci bus 0x0000 cardnum 0x16 function 0x00: vendor 0x8086 device 0x9cba
?Intel Corporation Wildcat Point-LP MEI Controller #1

pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x9ca0
?Intel Corporation Wildcat Point-LP High Definition Audio Controller

pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x9c90
?Intel Corporation Wildcat Point-LP PCI Express Root Port #1

pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device 0x9c94
?Intel Corporation Wildcat Point-LP PCI Express Root Port #3

pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
?Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device 0x9c96
?Intel Corporation Wildcat Point-LP PCI Express Root Port #4

pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x8086 device 0x095a
?Intel Corporation Wireless 7265

pci bus 0x0000 cardnum 0x1c function 0x04: vendor 0x8086 device 0x9c98
?Intel Corporation Wildcat Point-LP PCI Express Root Port #5

pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10de device 0x1299
?NVIDIA Corporation GK208BM [GeForce 920M]

pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x9ca6
?Intel Corporation Wildcat Point-LP USB EHCI Controller

pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x9cc3
?Intel Corporation Wildcat Point-LP LPC ControllerX.Org X Server 1.19.6

pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x9c83
?Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode]

pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x9ca2
?Intel Corporation Wildcat Point-LP SMBus Controller

I boot from latest USB image there X session dont start, only the mouse pointer is seen. If I kill the Xorg via SSH I get no text console.
So I reboot in text console and tried to test Xorg configuration with my current working settings (of Xorg 1.19.6 vesa for the Intel, Nvidia was never usable with the old i915 driver). There I get only a black screen and after kill Xorg no text console again. 
Activating vtdaemon and vt-console also not working.

What is the change here, so that Xorg 1.19.7 isn't working anymore? In Xorg.0.log I dont see any errors.

Thanks



























 <signatureafterquotedtext></signatureafterquotedtext>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190603/0736b268/attachment-0005.html>

From grzemba at contac-dt.de  Tue Jun  4 08:27:09 2019
From: grzemba at contac-dt.de (Carsten Grzemba)
Date: Tue, 04 Jun 2019 10:27:09 +0200
Subject: [oi-dev] Openindiana on Laptop: touchpad not working
In-Reply-To: <bd3d30256aff.5cf54e6a@contac-dt.de>
References: <be86e6074ec1.5ce41f99@contac-dt.de>
	<alpine.GSO.2.20.1905211010220.7749@scrappy.simplesystems.org>
	<bd3e8f4829c5.5ce65b00@contac-dt.de>
	<bd3d30256aff.5cf54e6a@contac-dt.de>
Message-ID: <bf5f8a435076.5cf6477d@contac-dt.de>


<signaturebeforequotedtext></signaturebeforequotedtext>
On 03.06.19 16:44, "Carsten Grzemba"  <grzemba at contac-dt.de> wrote: 
> 
> 
> 
> On 23.05.19 08:34, Carsten Grzemba via oi-dev  <oi-dev at openindiana.org> wrote: 
> > 
> > I compared the Xorg log:
> > 
> > in the working log the mouse driver is loaded on PS/s mouse on /dev/mouse:
> > 
> > [ 38.008] (II) LoadModule: "mouse"
> > [ 38.008] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> > [ 38.012] (II) Module mouse: vendor="X.Org Foundation"
> > [ 38.012] compiled for 1.19.5, module version = 1.9.2
> > [ 38.012] Module class: X.Org XInput Driver
> > [ 38.012] ABI class: X.Org XInput driver, version 24.1
> > [ 38.012] (II) Using input driver 'mouse' for 'PS/2 Port for PS/2-style Mice'
> > [ 38.012] (**) PS/2 Port for PS/2-style Mice: always reports core events
> > [ 38.012] (**) Option "Device" "/dev/mouse"
> > [ 38.012] (II) PS/2 Port for PS/2-style Mice: Setting Device option to "/dev/mouse"
> > [ 38.014] (==) PS/2 Port for PS/2-style Mice: Protocol: "VUID"
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: always reports core events
> > [ 38.014] (**) Option "Device" "/dev/mouse"
> > [ 38.014] (==) PS/2 Port for PS/2-style Mice: Emulate3Buttons, Emulate3Timeout: 50
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: ZAxisMapping: buttons 4 and 5
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: Buttons: 9
> > [ 38.014] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/isa_1f/i8042_1_60/mouse_1_0_logicaldev_input"
> > [ 38.014] (II) XINPUT: Adding extended input device "PS/2 Port for PS/2-style Mice" (type: MOUSE, id 6)
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) keeping acceleration scheme 1
> > [ 38.014] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration profile 0
> > [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration factor: 2.000
> > [ 38.015] (**) PS/2 Port for PS/2-style Mice: (accel) acceleration threshold: 4
> > 
> > and the not working on the generic USB device /dev/usb/hid1:
> > 
> > [ 523.036] (II) Loading /usr/lib/xorg/modules/input/amd64/mouse_drv.so
> > [ 523.036] (II) Module mouse: vendor="X.Org Foundation"
> > [ 523.036] compiled for 1.19.5, module version = 1.9.2
> > [ 523.036] Module class: X.Org XInput Driver
> > [ 523.037] ABI class: X.Org XInput driver, version 24.1
> > [ 523.037] (II) Using input driver 'mouse' for 'mouse'
> > [ 523.037] (**) mouse: always reports core events
> > [ 523.037] (**) Option "Protocol" "VUID"
> > [ 523.037] (**) Option "Device" "/dev/usb/hid1"
> > [ 523.037] (**) Option "StreamsModule" "usbms"
> > [ 523.039] (**) mouse: Protocol: "VUID"
> > [ 523.039] (**) mouse: always reports core events
> > [ 523.039] (==) mouse: Emulate3Buttons, Emulate3Timeout: 50
> > [ 523.039] (**) mouse: ZAxisMapping: buttons 4 and 5
> > [ 523.039] (**) mouse: Buttons: 9
> > [ 523.039] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1025_1019_14/device_4/mouse_1_if1_4_logicaldev_input"
> > [ 523.039] (II) XINPUT: Adding extended input device "mouse" (type: MOUSE, id 6)
> > [ 523.039] (**) mouse: (accel) keeping acceleration scheme 1
> > [ 523.039] (**) mouse: (accel) acceleration profile 0
> > [ 523.039] (**) mouse: (accel) acceleration factor: 2.000
> > [ 523.039] (**) mouse: (accel) acceleration threshold: 4
> > [ 523.045] (II) config/hal: Adding input device hotkey
> > 
> > 
> > in both cases is the the touchpad avail and a extern USB mouse connected. the /dev/mouse dev link is in both BE targeted to /devices/pseudo/cons at 0:mouse
> > 
> > 
> Still no luck with the latest hipster on my laptop:
> 
> scanpci:
> pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1604
> ?Intel Corporation Broadwell-U Host Bridge -OPI
> 
> pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1616
> ?Intel Corporation HD Graphics 5500
> 
> pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x160c
> ?Intel Corporation Broadwell-U Audio Controller
> 
> pci bus 0x0000 cardnum 0x14 function 0x00: vendor 0x8086 device 0x9cb1
> ?Intel Corporation Wildcat Point-LP USB xHCI Controller
> 
> pci bus 0x0000 cardnum 0x16 function 0x00: vendor 0x8086 device 0x9cba
> ?Intel Corporation Wildcat Point-LP MEI Controller #1
> 
> pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x9ca0
> ?Intel Corporation Wildcat Point-LP High Definition Audio Controller
> 
> pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x9c90
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #1
> 
> pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device 0x9c94
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #3
> 
> pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
> ?Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
> 
> pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device 0x9c96
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #4
> 
> pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x8086 device 0x095a
> ?Intel Corporation Wireless 7265
> 
> pci bus 0x0000 cardnum 0x1c function 0x04: vendor 0x8086 device 0x9c98
> ?Intel Corporation Wildcat Point-LP PCI Express Root Port #5
> 
> pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10de device 0x1299
> ?NVIDIA Corporation GK208BM [GeForce 920M]
> 
> pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x9ca6
> ?Intel Corporation Wildcat Point-LP USB EHCI Controller
> 
> pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x9cc3
> ?Intel Corporation Wildcat Point-LP LPC ControllerX.Org X Server 1.19.6
> 
> pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x9c83
> ?Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode]
> 
> pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x9ca2
> ?Intel Corporation Wildcat Point-LP SMBus Controller
> 
> I boot from latest USB image there X session dont start, only the mouse pointer is seen. If I kill the Xorg via SSH I get no text console.
> So I reboot in text console and tried to test Xorg configuration with my current working settings (of Xorg 1.19.6 vesa for the Intel, Nvidia was never usable with the old i915 driver). There I get only a black screen and after kill Xorg no text console again. 
> Activating vtdaemon and vt-console also not working.
> 
> What is the change here, so that Xorg 1.19.7 isn't working anymore? In Xorg.0.log I dont see any errors.
> 
> Thanks 
> 
Because the Xorg config is not changed and the touchpad not working on newer hipster, it looks for me like the touchpad is disabled what can normaly toggled by Fn F7.
But Fn keys do not work at all on newer hipster. Something to do with ACPI ?

 <signatureafterquotedtext></signatureafterquotedtext>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190604/1b76e6e2/attachment-0005.html>

From randyf at sibernet.com  Tue Jun 11 18:07:21 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 11:07:21 -0700 (PDT)
Subject: [oi-dev] suspend/resume in Illumos
Message-ID: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>



I have a question for developers here:

    How important is suspend/resume for OI/Illumos (including S4)?


One of the incomplete projects left behind was S4 (lack of need, and a 
hard to identify bug stifled it's integration).  It is non-trivial, and 
needs updated s/r core code (added configuration and significant 
restructuring, as well as likely assistance from developers knowlegable in 
other Illumos internals), but if this is an uninteresting feature, it is 
likey not worth the effort (recent bugs suggest that few if anyone use 
it); however, it wouldn't be too hard to resurect (though would still take 
several months of work).


   Cheers!

 	---- Randy



From gary_mills at fastmail.fm  Tue Jun 11 18:10:11 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 11 Jun 2019 13:10:11 -0500
Subject: [oi-dev] Toward a SPARC distro of OI
Message-ID: <20190611181011.GA18869@mail.messagingengine.com>

I'm part way through this long project now.  I began with v9os
installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
packages.  I've been building IPS packages from oi-userland source.
This process has gotten easier now that all the build tools I need are
in IPS packages.  I've been replacing v9os packages with oi-userland
packages.  My goal is to replace all of them, and finally to produce a
text ISO and package repository for SPARC that's entirely based on
oi-userland.

So far, I've built and packaged versions 5, 6, and 7 of the gcc
compiler.  The commands for IPS packages are all packaged for python
2.7.  My system now has 106 packages installed from oi-userland,
versus 343 packages from v9os.  Most of the oi-userland products
required very few or no changes to build and package for SPARC.

For perl, I've removed the 5.16.1 version from v9os and installed
versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
packaged for 5.22.  Python libraries are all packaged for 2.7.

I'm submitting this message to the mailing list mostly as a progress
report.  I would, of course, appreciate a bit of help with this
project.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From garrett at damore.org  Tue Jun 11 19:58:08 2019
From: garrett at damore.org (Garrett D'Amore)
Date: Tue, 11 Jun 2019 12:58:08 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
Message-ID: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>

My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where suspend/resume has little if any applicability.

While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from other more pressing work, without any clear use cases for it.

That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any other reason we would reject a suitably formed RTI.

Sent from Mail for Windows 10

From: randyf at sibernet.com
Sent: Tuesday, June 11, 2019 11:10 AM
To: oi-dev at openindiana.org; developer at lists.illumos.org
Subject: [developer] suspend/resume in Illumos



I have a question for developers here:

    How important is suspend/resume for OI/Illumos (including S4)?


One of the incomplete projects left behind was S4 (lack of need, and a 
hard to identify bug stifled it's integration).  It is non-trivial, and 
needs updated s/r core code (added configuration and significant 
restructuring, as well as likely assistance from developers knowlegable in 
other Illumos internals), but if this is an uninteresting feature, it is 
likey not worth the effort (recent bugs suggest that few if anyone use 
it); however, it wouldn't be too hard to resurect (though would still take 
several months of work).


   Cheers!

        ---- Randy

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190611/347dae6d/attachment-0005.html>

From tsoome at me.com  Tue Jun 11 20:31:18 2019
From: tsoome at me.com (Toomas Soome)
Date: Tue, 11 Jun 2019 23:31:18 +0300
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
Message-ID: <DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>

I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be bonus.

Sent from my iPhone

> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
> 
> My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where suspend/resume has little if any applicability.
>  
> While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from other more pressing work, without any clear use cases for it.
>  
> That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any other reason we would reject a suitably formed RTI.
>  
> Sent from Mail for Windows 10
>  
> From: randyf at sibernet.com
> Sent: Tuesday, June 11, 2019 11:10 AM
> To: oi-dev at openindiana.org; developer at lists.illumos.org
> Subject: [developer] suspend/resume in Illumos
>  
>  
>  
> I have a question for developers here:
>  
>     How important is suspend/resume for OI/Illumos (including S4)?
>  
>  
> One of the incomplete projects left behind was S4 (lack of need, and a
> hard to identify bug stifled it's integration).  It is non-trivial, and
> needs updated s/r core code (added configuration and significant
> restructuring, as well as likely assistance from developers knowlegable in
> other Illumos internals), but if this is an uninteresting feature, it is
> likey not worth the effort (recent bugs suggest that few if anyone use
> it); however, it wouldn't be too hard to resurect (though would still take
> several months of work).
>  
>  
>    Cheers!
>  
>         ---- Randy
>  
> ------------------------------------------
> illumos: illumos-developer
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
>  
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190611/1b0c9592/attachment-0005.html>

From randyf at sibernet.com  Tue Jun 11 21:28:34 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 14:28:34 -0700 (PDT)
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
Message-ID: <alpine.SOC.2.00.1906111420090.15467@sibernet.com>



On Tue, 11 Jun 2019, Garrett D'Amore wrote:

> 
> My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter applications where
> suspend/resume has little if any applicability.
> 
> ?
> 
> While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be detraction from
> other more pressing work, without any clear use cases for it.
>

   I should point out that s/r isn't just for laptop bare-metal.  It allows 
for a running instance of an OS to be frozen in an orderly manner (rather 
than a VM just pausing a guest, the guest suspends first).  S4 opens a 
different world of allowing said image to be more easily migrated, or 
(since it has roots in CPR) opens quick-boot images (imagine getting an 
OS fully booted in under 10 seconds).

> ?
> 
> That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it, and I?m
> fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for example), I can?t see any
> other reason we would reject a suitably formed RTI.
>

   Doubt I'll fully drop it, but without sufficient interest, it's is 
unlikely I'll give it much priority (certainly, my other 'dropped' project 
should have a higer priority).

   Cheers!

 	---- Randy

> ?
> 
> Sent from Mail for Windows 10
> 
> ?
> 
> From: randyf at sibernet.com
> Sent: Tuesday, June 11, 2019 11:10 AM
> To: oi-dev at openindiana.org; developer at lists.illumos.org
> Subject: [developer] suspend/resume in Illumos
> 
> ?
> 
> ?
> 
> ?
> 
> I have a question for developers here:
> 
> ?
> 
> ??? How important is suspend/resume for OI/Illumos (including S4)?
> 
> ?
> 
> ?
> 
> One of the incomplete projects left behind was S4 (lack of need, and a
> 
> hard to identify bug stifled it's integration).? It is non-trivial, and
> 
> needs updated s/r core code (added configuration and significant
> 
> restructuring, as well as likely assistance from developers knowlegable in
> 
> other Illumos internals), but if this is an uninteresting feature, it is
> 
> likey not worth the effort (recent bugs suggest that few if anyone use
> 
> it); however, it wouldn't be too hard to resurect (though would still take
> 
> several months of work).
> 
> ?
> 
> ?
> 
> ?? Cheers!
> 
> ?
> 
> ??????? ---- Randy
> 
> ?
> 
> ------------------------------------------
> 
> illumos: illumos-developer
> 
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> 
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
> 
> ?
> 
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
> 
>

From randyf at sibernet.com  Tue Jun 11 21:29:23 2019
From: randyf at sibernet.com (randyf at sibernet.com)
Date: Tue, 11 Jun 2019 14:29:23 -0700 (PDT)
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
Message-ID: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>



On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:

> I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be
> bonus.

   Betting better graphics support would be higher on the list (yea, the 
other 'dropped' project).

   Cheers!

 	---- Randy

> 
> Sent from my iPhone
> 
> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>
>       My gut instinct is that this isn?t that interesting ? most everyone is running illumos in either VMs, or in datacenter
>       applications where suspend/resume has little if any applicability.
>
>       ?
>
>       While the work itself is probably interesting, and it may enable new applications for illumos, the concern I?d have would be
>       detraction from other more pressing work, without any clear use cases for it.
>
>       ?
>
>       That said, if someone (you?) wanted to spend cycles on this for personal satisfaction, I hardly see any reason to discourage it,
>       and I?m fairly certain if the risks of the new code being introduced are small (or well managed by sufficient testing for
>       example), I can?t see any other reason we would reject a suitably formed RTI.
>
>       ?
>
>       Sent from Mail for Windows 10
>
>       ?
>
>       From: randyf at sibernet.com
>       Sent: Tuesday, June 11, 2019 11:10 AM
>       To: oi-dev at openindiana.org; developer at lists.illumos.org
>       Subject: [developer] suspend/resume in Illumos
> 
> ?
> 
> ?
> 
> ?
> 
> I have a question for developers here:
> 
> ?
> 
> ??? How important is suspend/resume for OI/Illumos (including S4)?
> 
> ?
> 
> ?
> 
> One of the incomplete projects left behind was S4 (lack of need, and a
> 
> hard to identify bug stifled it's integration).? It is non-trivial, and
> 
> needs updated s/r core code (added configuration and significant
> 
> restructuring, as well as likely assistance from developers knowlegable in
> 
> other Illumos internals), but if this is an uninteresting feature, it is
> 
> likey not worth the effort (recent bugs suggest that few if anyone use
> 
> it); however, it wouldn't be too hard to resurect (though would still take
> 
> several months of work).
> 
> ?
> 
> ?
> 
> ?? Cheers!
> 
> ?
> 
> ??????? ---- Randy
> 
> ?
> 
> ------------------------------------------
> 
> illumos: illumos-developer
> 
> Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M221586bbcf19e81e63ecf58f
> 
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription
> 
> ?
> 
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
> 
>

From josh at sysmgr.org  Tue Jun 11 21:32:28 2019
From: josh at sysmgr.org (Joshua M. Clulow)
Date: Tue, 11 Jun 2019 14:32:28 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <CAEwA5nJHmR+Md2hh2HGj5770+-x=uanePOwqTrYRBe4W0GxPoQ@mail.gmail.com>

On Tue, 11 Jun 2019 at 14:29, <randyf at sibernet.com> wrote:
> On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
> > I?d say, anything to encourage people to try, use and join to develop [illumos] is very welcome. Better laptop support will definitely be
> > bonus.
>
>    Betting better graphics support would be higher on the list (yea, the
> other 'dropped' project).

I think there are a fair few people who would appreciate some serious
elbow grease being applied to the graphics bits!


Cheers.

-- 
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org



From jimklimov at cos.ru  Wed Jun 12 08:01:25 2019
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 12 Jun 2019 08:01:25 +0000
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>

On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>
>
>On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>
>> I?d say, anything to encourage people to try, use and join to develop
>[illumos] is very welcome. Better laptop support will definitely be
>> bonus.
>
> Betting better graphics support would be higher on the list (yea, the 
>other 'dropped' project).
>
>   Cheers!
>
>        ---- Randy
>
>> 
>> Sent from my iPhone
>> 
>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> My gut instinct is that this isn?t that interesting ? most everyone
>is running illumos in either VMs, or in datacenter
>> applications where suspend/resume has little if any applicability.
>> 
>> While the work itself is probably interesting, and it may enable new
>applications for illumos, the concern I?d have would be
>> detraction from other more pressing work, without any clear use cases
>for it.
>> 
>> That said, if someone (you?) wanted to spend cycles on this for
>personal satisfaction, I hardly see any reason to discourage it,
>> and I?m fairly certain if the risks of the new code being introduced
>are small (or well managed by sufficient testing for
>> example), I can?t see any other reason we would reject a suitably
>formed RTI.
>> 
>> Sent from Mail for Windows 10
>> 
>> From: randyf at sibernet.com
>> Sent: Tuesday, June 11, 2019 11:10 AM
>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>> Subject: [developer] suspend/resume in Illumos
>> 
>> I have a question for developers here:
>> 
>> ??? How important is suspend/resume for OI/Illumos (including S4)?
>> 
>> One of the incomplete projects left behind was S4 (lack of need, and
>a
>> 
>> hard to identify bug stifled it's integration).? It is non-trivial,
>and
>> 
>> needs updated s/r core code (added configuration and significant
>> 
>> restructuring, as well as likely assistance from developers
>knowlegable in
>> 
>> other Illumos internals), but if this is an uninteresting feature, it
>is
>> 
>> likey not worth the effort (recent bugs suggest that few if anyone
>use
>> 
>> it); however, it wouldn't be too hard to resurect (though would still
>take
>> 
>> several months of work).
>> 
>> ?? Cheers!
>> 
>> ??????? ---- Randy
>> 
>> illumos / illumos-developer / see discussions + participants +
>delivery options Permalink
>> 
>------------------------------------------
>illumos: illumos-developer
>Permalink:
>https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>Delivery options:
>https://illumos.topicbox.com/groups/developer/subscription

For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.

My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.

Jim

--
Typos courtesy of K-9 Mail on my Android



From jimklimov at cos.ru  Wed Jun 12 08:01:25 2019
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 12 Jun 2019 08:01:25 +0000
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <alpine.SOC.2.00.1906111428490.15467@sibernet.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
Message-ID: <699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>

On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>
>
>On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>
>> I?d say, anything to encourage people to try, use and join to develop
>[illumos] is very welcome. Better laptop support will definitely be
>> bonus.
>
> Betting better graphics support would be higher on the list (yea, the 
>other 'dropped' project).
>
>   Cheers!
>
>        ---- Randy
>
>> 
>> Sent from my iPhone
>> 
>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> My gut instinct is that this isn?t that interesting ? most everyone
>is running illumos in either VMs, or in datacenter
>> applications where suspend/resume has little if any applicability.
>> 
>> While the work itself is probably interesting, and it may enable new
>applications for illumos, the concern I?d have would be
>> detraction from other more pressing work, without any clear use cases
>for it.
>> 
>> That said, if someone (you?) wanted to spend cycles on this for
>personal satisfaction, I hardly see any reason to discourage it,
>> and I?m fairly certain if the risks of the new code being introduced
>are small (or well managed by sufficient testing for
>> example), I can?t see any other reason we would reject a suitably
>formed RTI.
>> 
>> Sent from Mail for Windows 10
>> 
>> From: randyf at sibernet.com
>> Sent: Tuesday, June 11, 2019 11:10 AM
>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>> Subject: [developer] suspend/resume in Illumos
>> 
>> I have a question for developers here:
>> 
>> ??? How important is suspend/resume for OI/Illumos (including S4)?
>> 
>> One of the incomplete projects left behind was S4 (lack of need, and
>a
>> 
>> hard to identify bug stifled it's integration).? It is non-trivial,
>and
>> 
>> needs updated s/r core code (added configuration and significant
>> 
>> restructuring, as well as likely assistance from developers
>knowlegable in
>> 
>> other Illumos internals), but if this is an uninteresting feature, it
>is
>> 
>> likey not worth the effort (recent bugs suggest that few if anyone
>use
>> 
>> it); however, it wouldn't be too hard to resurect (though would still
>take
>> 
>> several months of work).
>> 
>> ?? Cheers!
>> 
>> ??????? ---- Randy
>> 
>> illumos / illumos-developer / see discussions + participants +
>delivery options Permalink
>> 
>------------------------------------------
>illumos: illumos-developer
>Permalink:
>https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>Delivery options:
>https://illumos.topicbox.com/groups/developer/subscription

For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.

My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.

Jim

--
Typos courtesy of K-9 Mail on my Android



From aurelien.larcher at gmail.com  Mon Jun 17 11:26:59 2019
From: aurelien.larcher at gmail.com (=?UTF-8?Q?Aur=C3=A9lien_Larcher?=)
Date: Mon, 17 Jun 2019 13:26:59 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <20190611181011.GA18869@mail.messagingengine.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
Message-ID: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>

On Mon, Jun 17, 2019 at 11:59 AM Gary Mills <gary_mills at fastmail.fm> wrote:

> I'm part way through this long project now.  I began with v9os
> installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
> packages.  I've been building IPS packages from oi-userland source.
> This process has gotten easier now that all the build tools I need are
> in IPS packages.  I've been replacing v9os packages with oi-userland
> packages.  My goal is to replace all of them, and finally to produce a
> text ISO and package repository for SPARC that's entirely based on
> oi-userland.
>
> So far, I've built and packaged versions 5, 6, and 7 of the gcc
> compiler.  The commands for IPS packages are all packaged for python
> 2.7.  My system now has 106 packages installed from oi-userland,
> versus 343 packages from v9os.  Most of the oi-userland products
> required very few or no changes to build and package for SPARC.
>
> For perl, I've removed the 5.16.1 version from v9os and installed
> versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
> removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
> packaged for 5.22.  Python libraries are all packaged for 2.7.
>
> I'm submitting this message to the mailing list mostly as a progress
> report.  I would, of course, appreciate a bit of help with this
> project.
>

Congratulations Gary this is great :)
If we get to the point that we can setup a build machine this would secure
your work.
Kind regards

Aur?lien



>
>
> --
> -Gary Mills-            -refurb-                -Winnipeg, Manitoba,
> Canada-
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


-- 
---
Praise the Caffeine embeddings
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190617/a222a8e2/attachment-0005.html>

From toasterson at gmail.com  Mon Jun 17 15:33:53 2019
From: toasterson at gmail.com (=?UTF-8?Q?Till_Wegm=c3=bcller?=)
Date: Mon, 17 Jun 2019 17:33:53 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
Message-ID: <63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com>

Hi Gary

Thank you so much for this Work. I don't personaly use sparc but ir is
good to see people doing this kinds of projects.

Do you know about Agnar's Project to get OI building on SPARC? I can't
remember if I ever pointed you towards him and his OI on Sparc work. His
angle was to jump from an existing OI distro to current packages and
later looking in V9OS.

Greetings
Till

On 17.06.19 13:26, Aur?lien Larcher wrote:
> 
> 
> On Mon, Jun 17, 2019 at 11:59 AM Gary Mills <gary_mills at fastmail.fm
> <mailto:gary_mills at fastmail.fm>> wrote:
> 
>     I'm part way through this long project now.? I began with v9os
>     installed on a Sun T2000.? v9os is a SPARC distribution that uses IPS
>     packages.? I've been building IPS packages from oi-userland source.
>     This process has gotten easier now that all the build tools I need are
>     in IPS packages.? I've been replacing v9os packages with oi-userland
>     packages.? My goal is to replace all of them, and finally to produce a
>     text ISO and package repository for SPARC that's entirely based on
>     oi-userland.
> 
>     So far, I've built and packaged versions 5, 6, and 7 of the gcc
>     compiler.? The commands for IPS packages are all packaged for python
>     2.7.? My system now has 106 packages installed from oi-userland,
>     versus 343 packages from v9os.? Most of the oi-userland products
>     required very few or no changes to build and package for SPARC.
> 
>     For perl, I've removed the 5.16.1 version from v9os and installed
>     versions 5.22 and 5.24 from oi-userland.? Likewise, for python, I've
>     removed 2.6 and installed 2.7 and 3.4.? Perl libraries are all
>     packaged for 5.22.? Python libraries are all packaged for 2.7.
> 
>     I'm submitting this message to the mailing list mostly as a progress
>     report.? I would, of course, appreciate a bit of help with this
>     project.
> 
> 
> Congratulations Gary this is great :)
> If we get to the point that we can setup a build machine this would
> secure your work.
> Kind regards
> 
> Aur?lien
> 
> ?
> 
> 
> 
>     -- 
>     -Gary Mills-? ? ? ? ? ? -refurb-? ? ? ? ? ? ? ? -Winnipeg, Manitoba,
>     Canada-
> 
>     _______________________________________________
>     oi-dev mailing list
>     oi-dev at openindiana.org <mailto:oi-dev at openindiana.org>
>     https://openindiana.org/mailman/listinfo/oi-dev
> 
> 
> 
> -- 
> ---
> Praise the Caffeine embeddings
> 
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
> 



From olbohlen at eenfach.de  Tue Jun 18 19:25:07 2019
From: olbohlen at eenfach.de (Olaf Bohlen)
Date: Tue, 18 Jun 2019 21:25:07 +0200
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com> ("Till
	=?utf-8?Q?Wegm=C3=BCller=22's?= message of "Mon, 17 Jun 2019 17:33:53
	+0200")
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
	<63736dfc-e8f2-6bb0-0fd9-dad8fc0cdd0b@gmail.com>
Message-ID: <x6pnnavgq4.fsf@eenfach.de>

Till Wegm?ller <toasterson at gmail.com> writes:

Hi Till,
hi Gary,

> Do you know about Agnar's Project to get OI building on SPARC? I can't
> remember if I ever pointed you towards him and his OI on Sparc work. His
> angle was to jump from an existing OI distro to current packages and
> later looking in V9OS.

First: Gary, this is phantastic news, congrats to it! I'm looking
forward to hear more from you.

Second: Till, yes Gary and I have been in contact but since I have
not enough time, my progress is probably somewhat slower. I also
have newer bits running, but my approach is - as you mentioned -
doing bootstrapping a system to be able to build recent bits in
the correct way.

I'd be happy to hear once someone has built a bootable OI media
for sparc and would take up of these also.

Best regards,

-- 
      ~       Olaf Bohlen - olbohlen at eenfach.de
      |~~     Het
     /|  \    Bruine
 ___/_|___\   Leven
   \__n____/# DGCN2



From Tim.Mooney at ndsu.edu  Mon Jun 24 02:24:33 2019
From: Tim.Mooney at ndsu.edu (Tim Mooney)
Date: Sun, 23 Jun 2019 21:24:33 -0500 (CDT)
Subject: [oi-dev] component TODO list for perl components?
Message-ID: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,

 	https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164



From alp at sfedu.ru  Mon Jun 24 06:05:50 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 06:05:50 +0000
Subject: [oi-dev] component TODO list for perl components?
In-Reply-To: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
References: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
Message-ID: <AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.

I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/ some time ago. There are mostly tasks which I'm interested in.

Now I'm looking at removing binary blobs from DDU. Later I'll likely look at switching it to Python 3.5.

If you can propose any tasks which you can take (or pehaps, someone else), feel  free to update this page. I just don't want it to become a list of never-done tasks.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Tim Mooney <Tim.Mooney at ndsu.edu>
??????????: 24 ???? 2019 ?. 5:24:33
????: oi-dev at openindiana.org
????: [oi-dev] component TODO list for perl components?


I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.

There's a checklist of small/easy changes to make when updating a
component,

        https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md

but is there a list of the bigger packaging tasks, perhaps prioritized by
need?  Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.

I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.

Does a list like that exist?  Those types of things tend to go stale fast,
so I understand if there isn't one.

Tim
--
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



From garrett at damore.org  Mon Jun 24 14:42:34 2019
From: garrett at damore.org (Garrett D'Amore)
Date: Mon, 24 Jun 2019 07:42:34 -0700
Subject: [oi-dev] [developer] suspend/resume in Illumos
In-Reply-To: <DE25905A-0071-4339-B00A-9EB1D62CC5AB@gmail.com>
References: <alpine.SOC.2.00.1905231023430.18660@sibernet.com>
	<5d0007cf.1c69fb81.c767c.c58c@mx.google.com>
	<DE3E9799-BAFC-43E5-A0C0-3BC88A2565C2@me.com>
	<alpine.SOC.2.00.1906111428490.15467@sibernet.com>
	<699A1A3D-460A-466E-AF03-5475D7402BB6@cos.ru>
	<DE25905A-0071-4339-B00A-9EB1D62CC5AB@gmail.com>
Message-ID: <5d10e157.1c69fb81.48b1c.91f9@mx.google.com>

That?s only true if you?re running on  a hypervisor that uses suspend / resume for live migration.  I?m not sure how widespread running illumos on VMware is ? the absence of suspend/resume support means that nobody is benefiting from this particular capability today (at least with illumos).

Sent from Mail for Windows 10

From: DavidHalko
Sent: Monday, June 24, 2019 5:18 AM
To: illumos-developer
Cc: randyf at sibernet.com; oi-dev at openindiana.org
Subject: Re: [developer] suspend/resume in Illumos

Suspend and Resume is critical for live migration in a data center with external storage to reduce schedules downtime incurred with firmware updates to maintain a secure platform.

Thanks, David Halko
http://netmgt.blogspot.com/

Sent from my iPhone

> On Jun 12, 2019, at 4:01 AM, Jim Klimov <jimklimov at cos.ru> wrote:
> 
>> On June 11, 2019 9:29:23 PM UTC, randyf at sibernet.com wrote:
>> 
>> 
>>> On Tue, 11 Jun 2019, Toomas Soome via illumos-developer wrote:
>>> 
>>> I?d say, anything to encourage people to try, use and join to develop
>> [illumos] is very welcome. Better laptop support will definitely be
>>> bonus.
>> 
>> Betting better graphics support would be higher on the list (yea, the 
>> other 'dropped' project).
>> 
>>  Cheers!
>> 
>>       ---- Randy
>> 
>>> 
>>> Sent from my iPhone
>>> 
>>> On 11 Jun 2019, at 22:58, Garrett D'Amore <garrett at damore.org> wrote:
>>> 
>>> My gut instinct is that this isn?t that interesting ? most everyone
>> is running illumos in either VMs, or in datacenter
>>> applications where suspend/resume has little if any applicability.
>>> 
>>> While the work itself is probably interesting, and it may enable new
>> applications for illumos, the concern I?d have would be
>>> detraction from other more pressing work, without any clear use cases
>> for it.
>>> 
>>> That said, if someone (you?) wanted to spend cycles on this for
>> personal satisfaction, I hardly see any reason to discourage it,
>>> and I?m fairly certain if the risks of the new code being introduced
>> are small (or well managed by sufficient testing for
>>> example), I can?t see any other reason we would reject a suitably
>> formed RTI.
>>> 
>>> Sent from Mail for Windows 10
>>> 
>>> From: randyf at sibernet.com
>>> Sent: Tuesday, June 11, 2019 11:10 AM
>>> To: oi-dev at openindiana.org; developer at lists.illumos.org
>>> Subject: [developer] suspend/resume in Illumos
>>> 
>>> I have a question for developers here:
>>> 
>>>     How important is suspend/resume for OI/Illumos (including S4)?
>>> 
>>> One of the incomplete projects left behind was S4 (lack of need, and
>> a
>>> 
>>> hard to identify bug stifled it's integration).  It is non-trivial,
>> and
>>> 
>>> needs updated s/r core code (added configuration and significant
>>> 
>>> restructuring, as well as likely assistance from developers
>> knowlegable in
>>> 
>>> other Illumos internals), but if this is an uninteresting feature, it
>> is
>>> 
>>> likey not worth the effort (recent bugs suggest that few if anyone
>> use
>>> 
>>> it); however, it wouldn't be too hard to resurect (though would still
>> take
>>> 
>>> several months of work).
>>> 
>>>    Cheers!
>>> 
>>>         ---- Randy
>>> 
>>> illumos / illumos-developer / see discussions + participants +
>> delivery options Permalink
>> ------------------------------------------
>> illumos: illumos-developer
>> Permalink:
>> https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-Ma4a7672659b46c13f040eb9e
>> Delivery options:
>> https://illumos.topicbox.com/groups/developer/subscription
> 
> For my 2c, I have to use OI in a VM rather than baremetal on my laptop (would love to some day; it is part of my daily desktop for years now) because of a mix of these issues. While graphics and wifi drivers might be worked around by careful choice of hardware for a new rig, effective lack of sleep/hibernate is a big problem.
> 
> My sessions of desktop OS uptime tend to be weeks and months long, many apps and tabs open... so rebooting every morning is not quite an option.
> 
> Jim
> 
> --
> Typos courtesy of K-9 Mail on my Android

------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tb3e65f5ac470e30c-M87936b070d0aa9c1490f0794
Delivery options: https://illumos.topicbox.com/groups/developer/subscription

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20190624/7192fbe4/attachment-0005.html>

From alp at sfedu.ru  Mon Jun 24 15:12:45 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 15:12:45 +0000
Subject: [oi-dev] DDU testing
Message-ID: <AM6PR05MB6198AE59E0359DD5E878CCAFCFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.

I've finished replacing DDU binaries with binaries from DDU 1.2 and rewriting missing parts. 
Result is here: https://github.com/OpenIndiana/ddu/ .
I suggest it can get wider testing.
You can use openindiana/ddu component  from https://github.com/OpenIndiana/oi-userland/pull/5103 to build and test it. 

I'm waiting for test results and reviews.

Changes from current DDU (shipped with OI now).
1) pt_BR localization files removed as msgunfmt couldn't unparse them;
2) Database of third-party drivers was removed (it was obsolete  with it seems one working link from dozen). I suppose nobody volunteers to support it in actual state.
3) I hope finally I've made DDU help behave - now it shows help in user locale, images are not removed.
4) I've regenerated database of existing OI drivers shipped with DDU, updated pci.ids and usb.ids files.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???




From gary_mills at fastmail.fm  Mon Jun 24 15:33:31 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Mon, 24 Jun 2019 10:33:31 -0500
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>
Message-ID: <20190624153331.GA28009@mail.messagingengine.com>

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aur?lien Larcher wrote:
> 
>    Congratulations Gary this is great :)
>    If we get to the point that we can setup a build machine this would
>    secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From alp at sfedu.ru  Mon Jun 24 16:02:51 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Mon, 24 Jun 2019 16:02:51 +0000
Subject: [oi-dev] Toward a SPARC distro of OI
In-Reply-To: <20190624153331.GA28009@mail.messagingengine.com>
References: <20190611181011.GA18869@mail.messagingengine.com>
	<CAHMq6q2_x=1eh9aWB+C=ocaVp4tC0n2K9KJB+i=M_ChHngXusQ@mail.gmail.com>,
	<20190624153331.GA28009@mail.messagingengine.com>
Message-ID: <AM6PR05MB619883D7A53C05872643155DCFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>

BTW, while working on DDU I've removed SPARC parts I've encountered ;)
Anyway I had no way (or desire) to test them.
Most interesting is likely dmi_info.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Gary Mills <gary_mills at fastmail.fm>
??????????: 24 ???? 2019 ?. 18:33
????: OpenIndiana Developer mailing list
????: Re: [oi-dev] Toward a SPARC distro of OI

On Mon, Jun 17, 2019 at 01:26:59PM +0200, Aur?lien Larcher wrote:
>
>    Congratulations Gary this is great :)
>    If we get to the point that we can setup a build machine this would
>    secure your work.

Thanks.  That will be a big help.  I'd recommend weekly builds, rather
than daily builds.  I'm sure that will be adequate.  My build, when
it's completed, will be at least a year behind the current state of
OI.


--
-Gary Mills-            -refurb-                -Winnipeg, Manitoba, Canada-

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

From Tim.Mooney at ndsu.edu  Mon Jun 24 18:24:09 2019
From: Tim.Mooney at ndsu.edu (Tim Mooney)
Date: Mon, 24 Jun 2019 13:24:09 -0500 (CDT)
Subject: [oi-dev] component TODO list for perl components?
In-Reply-To: <AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>
References: <alpine.SOC.2.20.1906232020480.10941@dogbert.cc.ndsu.NoDak.edu>
	<AM6PR05MB619835DBC5E4E96EA3600465CFE00@AM6PR05MB6198.eurprd05.prod.outlook.com>
Message-ID: <alpine.SOC.2.20.1906241317080.14673@dogbert.cc.ndsu.NoDak.edu>

In regard to: Re: [oi-dev] component TODO list for perl components?,...:

> I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/
> some time ago. There are mostly tasks which I'm interested in.
>
> Now I'm looking at removing binary blobs from DDU. Later I'll likely
> look at switching it to Python 3.5.
>
> If you can propose any tasks which you can take (or pehaps, someone
> else), feel  free to update this page. I just don't want it to become a
> list of never-done tasks.

Thanks Alexander, and I understand completely about a list of never-done
tasks.

I'll open a pull request with some proposed updates, and you and others
can comment on whether they're a good idea or not.

Tim

> ________________________________________
> ??: Tim Mooney <Tim.Mooney at ndsu.edu>
> ??????????: 24 ???? 2019 ?. 5:24:33
> ????: oi-dev at openindiana.org
> ????: [oi-dev] component TODO list for perl components?
>
>
> I've been considering packaging the latest stable perl5, 5.30.0, as
> perl-530 and then packaging (and in some cases, updating) the perl
> modules that are part of hipster, but I want to make certain I'm not
> working at cross-purposes to any planned updates for OI and that this
> type of update is actually useful.
>
> There's a checklist of small/easy changes to make when updating a
> component,
>
>        https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md
>
> but is there a list of the bigger packaging tasks, perhaps prioritized by
> need?  Obviously people volunteering their time are going to work on
> things that interest them, benefit them, and are within their ability,
> but at times it would be helpful to know what the most pressing packaging
> needs are.
>
> I'm happy to continue choosing components kind of at random to update, but
> if I have a list of easy (but perhaps tedious) packaging tasks that are
> priorities for update in OI, I would probably attempt some of them as I
> have time, especially if it frees up more time for core contributors to
> work on the more difficult tasks.
>
> Does a list like that exist?  Those types of things tend to go stale fast,
> so I understand if there isn't one.
>
> Tim
> --
> Tim Mooney                                             Tim.Mooney at ndsu.edu
> Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
> Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>

-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

From gary_mills at fastmail.fm  Tue Jun 25 20:47:20 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 25 Jun 2019 15:47:20 -0500
Subject: [oi-dev] Am I stuck?
Message-ID: <20190625204720.GA8601@mail.messagingengine.com>

These are my publishers:

    # pkg publisher                      
    PUBLISHER                   TYPE     STATUS P LOCATION
    oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
    v9os           (non-sticky) origin   online F file:///data/ips/

I just published all of illumos-gate to the oi-userland repository.
There are now two copies of the
consolidation/osnet/osnet-incorporation package.  This is the
installed one:

    # pkg info consolidation/osnet/osnet-incorporation
              Name: consolidation/osnet/osnet-incorporation
           Summary: OS/Net consolidation incorporation
       Description: This incorporation constrains packages from the OS/Net
                    consolidation.
             State: Installed
         Publisher: v9os
           Version: 0.5.11
            Branch: 0.151100
    Packaging Date: Wed Jul 27 07:12:37 2016
              Size: 0.00 B
              FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
    
This is the new one:

    # pkg info -r consolidation/osnet/osnet-incorporation
              Name: consolidation/osnet/osnet-incorporation
           Summary: OS/Net consolidation incorporation
       Description: This incorporation constrains packages from the OS/Net
                    consolidation.
             State: Not installed
         Publisher: oi-userland
           Version: 0.5.11
            Branch: 2018.0.0.0
    Packaging Date: Sun Jun 23 22:35:19 2019
              Size: 0.00 B
              FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z

I expected that `pkg update -nv' would offer to remove the installed
incorporation and replace all of the old illumos-gate packages, over
200 of them, with the new illumos-gate packages.  It didn't do that.
It did report that it would replace ten packages from the v9os
publisher with newer versions from the oi-userland publisher, but this
list didn't include any of the illumos-gate packages.

When I tried to remove the incorporation with pkg, I got this result:

    # pkg uninstall -nv consolidation/osnet/osnet-incorporation
    Creating Plan (Solver setup): -
    pkg uninstall: Unable to remove 'consolidation/osnet/osnet-incorporation at 0.5.11-0.151100' due to the following packages that depend on it:
      SUNWcs at 0.5.11-0.151100
      SUNWcsd at 0.5.11-0.151100
      compatibility/ucb at 0.5.11-0.151100
      developer/astdev at 0.5.11-0.151100
    ...
      system/zones at 0.5.11-0.151100
      system/zones/internal at 0.5.11-0.151100
      text/doctools at 0.5.11-0.151100
      text/locale at 0.5.11-0.151100

Have I run into a dead end, or is there a way out of this dilemma?


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From vab at bb-c.de  Tue Jun 25 21:01:31 2019
From: vab at bb-c.de (Volker A. Brandt)
Date: Tue, 25 Jun 2019 23:01:31 +0200
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190625204720.GA8601@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
Message-ID: <23826.35755.98828.321659@shelob.bb-c.de>

Hi Gary!


> These are my publishers:
> 
>     # pkg publisher                      
>     PUBLISHER                   TYPE     STATUS P LOCATION
>     oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
>     v9os           (non-sticky) origin   online F file:///data/ips/
> 
> I just published all of illumos-gate to the oi-userland repository.
> There are now two copies of the
> consolidation/osnet/osnet-incorporation package.  This is the
> installed one:
> 
>     # pkg info consolidation/osnet/osnet-incorporation
>               Name: consolidation/osnet/osnet-incorporation
>            Summary: OS/Net consolidation incorporation
>        Description: This incorporation constrains packages from the OS/Net
>                     consolidation.
>              State: Installed
>          Publisher: v9os
>            Version: 0.5.11
>             Branch: 0.151100
>     Packaging Date: Wed Jul 27 07:12:37 2016
>               Size: 0.00 B
>               FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
>     
> This is the new one:
> 
>     # pkg info -r consolidation/osnet/osnet-incorporation
>               Name: consolidation/osnet/osnet-incorporation
>            Summary: OS/Net consolidation incorporation
>        Description: This incorporation constrains packages from the OS/Net
>                     consolidation.
>              State: Not installed
>          Publisher: oi-userland
>            Version: 0.5.11
>             Branch: 2018.0.0.0
>     Packaging Date: Sun Jun 23 22:35:19 2019
>               Size: 0.00 B
>               FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z
> 
> I expected that `pkg update -nv' would offer to remove the installed
> incorporation and replace all of the old illumos-gate packages, over
> 200 of them, with the new illumos-gate packages.  It didn't do that.
> It did report that it would replace ten packages from the v9os
> publisher with newer versions from the oi-userland publisher, but this
> list didn't include any of the illumos-gate packages.

So it appears that pkg does not recognize the fact that version
0.5.11-2018.0.0.0:20190623T223519Z is newer than version
0.5.11-0.151100:20160727T071237Z -- correct?

> When I tried to remove the incorporation with pkg, I got this result:
[...]

I don't think that you are supposed to be able to remove the package
altogether.  You should, hovewer, be able to update it.

Do you also have an "entire" package?  If so, what version does it
have?


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt        Consulting and Support for Solaris-based Systems
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"



From gary_mills at fastmail.fm  Wed Jun 26 00:31:04 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Tue, 25 Jun 2019 19:31:04 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <23826.35755.98828.321659@shelob.bb-c.de>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
Message-ID: <20190626003104.GA10000@mail.messagingengine.com>

On Tue, Jun 25, 2019 at 11:01:31PM +0200, Volker A. Brandt wrote:
> 
> So it appears that pkg does not recognize the fact that version
> 0.5.11-2018.0.0.0:20190623T223519Z is newer than version
> 0.5.11-0.151100:20160727T071237Z -- correct?

I don't think that that is the problem.  Consider this transcript:

    # pkg update -nv
    ...
    Changed packages:
    ...
    v9os -> oi-userland
      archiver/gnu-tar
        1.28-0.151100 -> 1.29-2018.0.0.0
      compress/bzip2
        1.0.6-0.151100 -> 1.0.6-2018.0.0.3
      compress/gzip
        1.6-0.151100 -> 1.9-2018.0.0.0

The version numbers were the same for the last two packages.

> > When I tried to remove the incorporation with pkg, I got this result:
> [...]
> 
> I don't think that you are supposed to be able to remove the package
> altogether.  You should, hovewer, be able to update it.

That's close to working.  I should be able to make it work.
Here's this one:

    # pkg update -nv pkg://oi-userland/consolidation/osnet/osnet-inco...
    Creating Plan (Solver setup): \
    pkg update: No matching version of consolidation/osnet/osnet-incorporation can be installed:
      Reject:  pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0
      Reason:  No version matching 'incorporate' dependency SUNWcs at 0.5.11-2018.0.0.0 can be installed
        ----------------------------------------
        Reject:  pkg://oi-userland/SUNWcs at 0.5.11-2018.0.0.0
        Reason:  No version matching 'require' dependency system/network/mailwrapper can be installed
          ----------------------------------------
          Reject:  pkg://oi-userland/system/network/mailwrapper at 0.5.11-2018.0.0.0
          Reason:  No version for 'require' dependency on system/mta can be found
          Reject:  pkg://v9os/system/network/mailwrapper at 0.5.11-0.151100
          Reason:  Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation'
          ----------------------------------------
        ----------------------------------------

> Do you also have an "entire" package?  If so, what version does it
> have?

No, I don't have that package.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From naj at snapcon.com  Wed Jun 26 00:28:12 2019
From: naj at snapcon.com (Norm Jacobs)
Date: Tue, 25 Jun 2019 19:28:12 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190625204720.GA8601@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
Message-ID: <1bba6380-a729-e329-a326-0fd1aa7572fb@snapcon.com>

You might look at the 'entire' package and see if it constrains the 
'osnet-incorporation to the older version.? That is most likely the 
cause of your trouble.? You can probably remove the 'entire' package and 
then update.? You might also be able to unlock the incorporation before 
upgrading instead.

 ??? -Norm


On 6/25/19 3:47 PM, Gary Mills wrote:
> These are my publishers:
>
>      # pkg publisher
>      PUBLISHER                   TYPE     STATUS P LOCATION
>      oi-userland                 origin   online F file:///export/home/mills/Downloads/code/oi-userland/sparc/repo/
>      v9os           (non-sticky) origin   online F file:///data/ips/
>
> I just published all of illumos-gate to the oi-userland repository.
> There are now two copies of the
> consolidation/osnet/osnet-incorporation package.  This is the
> installed one:
>
>      # pkg info consolidation/osnet/osnet-incorporation
>                Name: consolidation/osnet/osnet-incorporation
>             Summary: OS/Net consolidation incorporation
>         Description: This incorporation constrains packages from the OS/Net
>                      consolidation.
>               State: Installed
>           Publisher: v9os
>             Version: 0.5.11
>              Branch: 0.151100
>      Packaging Date: Wed Jul 27 07:12:37 2016
>                Size: 0.00 B
>                FMRI: pkg://v9os/consolidation/osnet/osnet-incorporation at 0.5.11-0.151100:20160727T071237Z
>      
> This is the new one:
>
>      # pkg info -r consolidation/osnet/osnet-incorporation
>                Name: consolidation/osnet/osnet-incorporation
>             Summary: OS/Net consolidation incorporation
>         Description: This incorporation constrains packages from the OS/Net
>                      consolidation.
>               State: Not installed
>           Publisher: oi-userland
>             Version: 0.5.11
>              Branch: 2018.0.0.0
>      Packaging Date: Sun Jun 23 22:35:19 2019
>                Size: 0.00 B
>                FMRI: pkg://oi-userland/consolidation/osnet/osnet-incorporation at 0.5.11-2018.0.0.0:20190623T223519Z
>
> I expected that `pkg update -nv' would offer to remove the installed
> incorporation and replace all of the old illumos-gate packages, over
> 200 of them, with the new illumos-gate packages.  It didn't do that.
> It did report that it would replace ten packages from the v9os
> publisher with newer versions from the oi-userland publisher, but this
> list didn't include any of the illumos-gate packages.
>
> When I tried to remove the incorporation with pkg, I got this result:
>
>      # pkg uninstall -nv consolidation/osnet/osnet-incorporation
>      Creating Plan (Solver setup): -
>      pkg uninstall: Unable to remove 'consolidation/osnet/osnet-incorporation at 0.5.11-0.151100' due to the following packages that depend on it:
>        SUNWcs at 0.5.11-0.151100
>        SUNWcsd at 0.5.11-0.151100
>        compatibility/ucb at 0.5.11-0.151100
>        developer/astdev at 0.5.11-0.151100
>      ...
>        system/zones at 0.5.11-0.151100
>        system/zones/internal at 0.5.11-0.151100
>        text/doctools at 0.5.11-0.151100
>        text/locale at 0.5.11-0.151100
>
> Have I run into a dead end, or is there a way out of this dilemma?
>
>



From richlowe at richlowe.net  Wed Jun 26 00:42:41 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Tue, 25 Jun 2019 20:42:41 -0400
Subject: [oi-dev] Am I stuck?
In-Reply-To: <20190626003104.GA10000@mail.messagingengine.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
	<20190626003104.GA10000@mail.messagingengine.com>
Message-ID: <CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>

Reason:  No version for 'require' dependency on system/mta can be found

Seems a leaf failure, does one really not exist?



From gary_mills at fastmail.fm  Wed Jun 26 12:52:41 2019
From: gary_mills at fastmail.fm (Gary Mills)
Date: Wed, 26 Jun 2019 07:52:41 -0500
Subject: [oi-dev] Am I stuck?
In-Reply-To: <CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>
References: <20190625204720.GA8601@mail.messagingengine.com>
	<23826.35755.98828.321659@shelob.bb-c.de>
	<20190626003104.GA10000@mail.messagingengine.com>
	<CAA7J0x8Cf3OETXy9_XAqxyxHYVi9eijwa5aqhqi6HDhMiG5jDg@mail.gmail.com>
Message-ID: <20190626125240.GA12540@mail.messagingengine.com>

On Tue, Jun 25, 2019 at 08:42:41PM -0400, Richard Lowe wrote:
> Reason:  No version for 'require' dependency on system/mta can be found
> 
> Seems a leaf failure, does one really not exist?

Indeed, the package system/mta does not exist in either publisher.  I
just published it to oi-userland and installed it.  My next task is to
see if that missing package was preventing the update.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-



From gordon.w.ross at gmail.com  Fri Jun 28 04:25:37 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 27 Jun 2019 21:25:37 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
Message-ID: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>

Any ideas what I should do to fix this?

root at oi-dev:/home/gwr# pkg -R /mnt image-update -v
Creating Plan (Running solver): /
pkg update: No solution was found to satisfy constraints
No solution found to update to latest available versions.
This may indicate an overly constrained set of packages are installed.

latest incorporations:

  pkg://openindiana.org/consolidation/install/install-incorporation at 0.5.11,5.11-2018.0.0.1041:20190516T142943Z
  pkg://openindiana.org/consolidation/l10n/l10n-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014527Z
  pkg://openindiana.org/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014529Z
  pkg://openindiana.org/consolidation/userland/userland-incorporation at 0.5.11,5.11-2018.0.0.11903:20190627T091450Z

Dependency analysis is unable to determine the cause.
Try specifying expected versions to obtain more detailed error messages.

On Sun, May 12, 2019 at 12:33 AM Alexander Pyhalov via oi-dev
<oi-dev at openindiana.org> wrote:
>
> Sorry, missed dot in
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso link.
>
> ? ?????????,
> ????????? ???????,
> ??????????? ?????? ???????????????????? ??????????????
> ?????????? ?????????????-???????????????? ?????????????? ???
>
>
> ________________________________________
> ??: Alexander Pyhalov via oi-dev <oi-dev at openindiana.org>
> ??????????: 12 ??? 2019 ?. 10:11:57
> ????: OpenIndiana Developer mailing list
> ?????: Alexander Pyhalov
> ????: [oi-dev] OI Hipster 2019.04
>
> Hi.
>
> OI Hipster 2019.04 snapshot is ready.
>
> Images:
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb
>
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
> http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb
>
>
> SHA 256 checksums are available at ${link}.sha256sum
> Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
> https://sks-keyservers.net/pks/lookup?op=get&search=0x3A021AFADBE31887 ).
>
> Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes
>
> Note, we have an issue with Firefox on live image - it can fail to start correctly when launched for the first time in memory-constrained  environment. After being killed and restarted it behaves more sane.
>
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



From gordon.w.ross at gmail.com  Fri Jun 28 04:26:44 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 27 Jun 2019 21:26:44 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
Message-ID: <CAD0Ztp2nrGdb3t2sKjUdR9HNNwdSJ_t=eJs=6UBesB2Uo=+wtA@mail.gmail.com>

I'm guessing people will want to see:

root at oi-dev:/home/gwr# pkg -R /mnt publisher
PUBLISHER                   TYPE     STATUS P LOCATION
openindiana.org              origin   online F
http://pkg.openindiana.org/hipster/
root at oi-dev:/home/gwr# pkg -R /mnt info entire
          Name: entire
       Summary: incorporation to lock all system packages to same build (empty
                package)
   Description: incorporation to lock all system packages to same build (empty
                package)
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
        Branch: 2018.0.0.0
Packaging Date: February 11, 2018 at 01:10:12 PM
          Size: 0.00 B
          FMRI: pkg://openindiana.org/entire at 0.5.11-2018.0.0.0:20180211T131012Z

On Thu, Jun 27, 2019 at 9:25 PM Gordon Ross <gordon.w.ross at gmail.com> wrote:
>
> Any ideas what I should do to fix this?
>
> root at oi-dev:/home/gwr# pkg -R /mnt image-update -v
> Creating Plan (Running solver): /
> pkg update: No solution was found to satisfy constraints
> No solution found to update to latest available versions.
> This may indicate an overly constrained set of packages are installed.
>
> latest incorporations:
>
>   pkg://openindiana.org/consolidation/install/install-incorporation at 0.5.11,5.11-2018.0.0.1041:20190516T142943Z
>   pkg://openindiana.org/consolidation/l10n/l10n-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014527Z
>   pkg://openindiana.org/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-2018.0.0.18662:20190628T014529Z
>   pkg://openindiana.org/consolidation/userland/userland-incorporation at 0.5.11,5.11-2018.0.0.11903:20190627T091450Z
>
> Dependency analysis is unable to determine the cause.
> Try specifying expected versions to obtain more detailed error messages.
>
> On Sun, May 12, 2019 at 12:33 AM Alexander Pyhalov via oi-dev
> <oi-dev at openindiana.org> wrote:
> >
> > Sorry, missed dot in
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.iso link.
> >
> > ? ?????????,
> > ????????? ???????,
> > ??????????? ?????? ???????????????????? ??????????????
> > ?????????? ?????????????-???????????????? ?????????????? ???
> >
> >
> > ________________________________________
> > ??: Alexander Pyhalov via oi-dev <oi-dev at openindiana.org>
> > ??????????: 12 ??? 2019 ?. 10:11:57
> > ????: OpenIndiana Developer mailing list
> > ?????: Alexander Pyhalov
> > ????: [oi-dev] OI Hipster 2019.04
> >
> > Hi.
> >
> > OI Hipster 2019.04 snapshot is ready.
> >
> > Images:
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-gui-20190511.usb
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-text-20190511.usb
> >
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.iso
> > http://dlc.openindiana.org/isos/hipster/20190511/OI-hipster-minimal-20190511.usb
> >
> >
> > SHA 256 checksums are available at ${link}.sha256sum
> > Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> > The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887 (
> > https://sks-keyservers.net/pks/lookup?op=get&search=0x3A021AFADBE31887 ).
> >
> > Release notes: http://wiki.openindiana.org/oi/2019.04+Release+notes
> >
> > Note, we have an issue with Firefox on live image - it can fail to start correctly when launched for the first time in memory-constrained  environment. After being killed and restarted it behaves more sane.
> >
> > Best regards,
> > Alexander Pyhalov,
> > system administrator of Southern Federal University IT department
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev



From richlowe at richlowe.net  Fri Jun 28 05:28:15 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Fri, 28 Jun 2019 01:28:15 -0400
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
Message-ID: <CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>

> Dependency analysis is unable to determine the cause.
> Try specifying expected versions to obtain more detailed error messages.
>

Do what it says there,

Specify the verisons of those 'latest incorporations', and probably
also entire, including the versions.

You may be able to just do 'pkg install -nv entire at latest' but I can
never remember whether only specifying 'entire' does the right thing.



From gordon.w.ross at gmail.com  Fri Jun 28 17:32:25 2019
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Fri, 28 Jun 2019 10:32:25 -0700
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
Message-ID: <CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>

OK, but I can't seem to find the latest version of entire.
Can anyone tell me what that should be?

root at oi-dev:/home/gwr# pkg -R /mnt refresh --full
root at oi-dev:/home/gwr# pkg -R /mnt update -nv entire at latest
No updates available for this image.
root at oi-dev:/home/gwr# pkg -R /mnt install -nv entire at latest
No updates necessary for this image.
root at oi-dev:/home/gwr# pkg -R /mnt info entire
          Name: entire
       Summary: incorporation to lock all system packages to same build (empty
                package)
   Description: incorporation to lock all system packages to same build (empty
                package)
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
        Branch: 2018.0.0.0
Packaging Date: February 11, 2018 at 01:10:12 PM
          Size: 0.00 B
          FMRI: pkg://openindiana.org/entire at 0.5.11-2018.0.0.0:20180211T131012Z

On Thu, Jun 27, 2019 at 10:28 PM Richard Lowe <richlowe at richlowe.net> wrote:
>
> > Dependency analysis is unable to determine the cause.
> > Try specifying expected versions to obtain more detailed error messages.
> >
>
> Do what it says there,
>
> Specify the verisons of those 'latest incorporations', and probably
> also entire, including the versions.
>
> You may be able to just do 'pkg install -nv entire at latest' but I can
> never remember whether only specifying 'entire' does the right thing.
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



From richlowe at richlowe.net  Fri Jun 28 17:43:23 2019
From: richlowe at richlowe.net (Richard Lowe)
Date: Fri, 28 Jun 2019 13:43:23 -0400
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
	<CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>
Message-ID: <CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?



From alp at sfedu.ru  Sat Jun 29 05:37:26 2019
From: alp at sfedu.ru (Alexander Pyhalov)
Date: Sat, 29 Jun 2019 05:37:26 +0000
Subject: [oi-dev] OI Hipster 2019.04
In-Reply-To: <CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>
References: <AM6PR05MB61983C720AADAF0A884EFA68CF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<AM6PR05MB61981562DA296AB8E74F64ACCF0E0@AM6PR05MB6198.eurprd05.prod.outlook.com>
	<CAD0Ztp325P1HRtkZVUPzKiLBmfuUEP6Kvci69Q6S3N17SBvbKw@mail.gmail.com>
	<CAA7J0x87LoeS8ZcayHYz0+suHEY1FDC8BtYMEFG1DqkONKC_DQ@mail.gmail.com>
	<CAD0Ztp1tUCvh+Lf7UOTk4OQ78SCW3DRhuXbCGQVy6qkgY6Nh4A@mail.gmail.com>,
	<CAA7J0x_nQ9f2xVORagNianuUqFxZFnEsm+z7oVj4taRyX7H47g@mail.gmail.com>
Message-ID: <AM6PR05MB6198F5838BDA1D994F326236CFFF0@AM6PR05MB6198.eurprd05.prod.outlook.com>

Hi.
entire is a package which depends on userland-incorporation. That's all. You are interested in latest osnet-incorporation and userland-incorporation.

? ?????????,
????????? ???????,
??????????? ?????? ???????????????????? ??????????????
?????????? ?????????????-???????????????? ?????????????? ???


________________________________________
??: Richard Lowe <richlowe at richlowe.net>
??????????: 28 ???? 2019 ?. 20:43
????: OpenIndiana Developer mailing list
????: Re: [oi-dev] OI Hipster 2019.04

I think that's me not-remembering whether doing that with entire would
do the right thing, did you try specifying @latest for all the
incorporations in the original error?

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev