[OpenIndiana-discuss] Σχετ: Re: many duplicates - Re: OpenIndiana Hipster at Servethehome (call for a regular minimal stable)

[Apostolos Syropoulos via openindiana-discuss]

I have receive one message 4 times and asecond one 5 times...
AS

Στάλθηκε από το Ταχυδρομείο Yahoo σε Android
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] I Installed OpenIndiana -- Now How Do I Boot It?

[Jay F. Shachter]

Esteemed Colleagues:

I have seen occasional references here and there on this mailing list
to the fact that OpenIndiana now uses the FreeBSD boot loader and no
longer uses GRUB, although I must have missed the discussion that
explained why this was in any way desirable.

However, even the FreeBSD boot loader would be better than no boot
loader at all, which is what I got yesterday after installing
OpenIndiana on my laptop (from the newest image on the website,
OI-hipster-gui-20161030.usb).

The context: I had to get a new laptop a few weeks ago, and because I
work with many different operating systems, I installed many different
operating systems on it.  Presently it has 3 dialects of Linux,
FreeBSD, and, as of yesterday, OpenIndiana, and soon it will have
Haiku (although I have never been able to install either SkyOS or
IcAros on any computer I have ever owned, but I digress).  The idea is
that when you turn on the computer you select the OS that you want to
run.

Actually I installed OpenIndiana for variety, my old laptop had
Solaris 11.3 (and I have more clients who demand knowledge of Solaris
11 than who demand knowledge of OpenIndiana, but my mind craves
variety, which is why I installed Springdale this time for my
RHEL-flavored Linux system, where my old laptop had Oracle Linux).  I
figured it was close enough, and I was prepared for the differences,
like OpenIndiana has none of the new ZFS stuff that Oracle has done on
Solaris (I'm sorry, I know everyone hates Oracle here, but what can I
do, I really like the new zfs share stuff) and like OpenIndiana uses
the FreeBSD boot loader instead of GRUB.  After that it would be a
simple matter of configuring the FreeBSD boot loader to offer my other
operating systems as boot-time options, a technique that, I think, was
in fact discussed on this mailing list a couple months ago or
thereabouts.

Or so I thought.  The USB key from which I booted the laptop in order
to perform the installation, definitely and recognizably uses the
FreeBSD boot loader.  I then happily installed OpenIndiana on Slice 7
of my disk (partitioned in the old msdos manner, meaning that Slice 7
is a "logical" slice inside of extended slice 4).  But the
installation procedure did not put any boot loader whatsoever on the
disk.  When I next booted my laptop from powerup I saw the exact same
GRUB2 menu as before, offering me the same 3 Linux systems and
FreeBSD.

That shouldn't be a problem, though.  Surely there should be some way
of getting GRUB2 to find and boot the OpenIndiana system.  Like, for
example, "chainloader (hd0,7)+1" would a good way of doing that.
Except that it didn't work.  I think it doesn't work in Solaris any
more either, although it once did, you would get a whole other GRUB
menu when you did that.  Similarly, you used to be able to do a
chainloader +1 on a FreeBSD installation, but I think that's stopped
working also, now you have to do kfreebsd /boot/loader (and I can't
get "kfreebsd /boot/kernel/kernel" to work either like it used to,
even after setting all the variables like I'm supposed to, but I
digress).

There does not seem to be any area on the disk from which one can do a
chainloader +1, except the MBR itself, which as I stated just gives me
the same GRUB2 menu as before.  What I need to do is instruct GRUB2
how to boot the OpenIndiana system on (hd0,7).  This is a procedure
that would surely start with "insmod zfs" but I'll be washed and
starched and ironed if I know what I'm supposed to do after that.
At the moment, the only way I know how to boot that system that I
installed yesterday (and subsequently spent hours configuring and
adding software to) is to boot from the installation medium and then
do a "reboot -f -- rpool/ROOT/openindiana".  That works, but it's
bogus; it is not, of course, a long-term solution.

I did it, though, because I refuse to be defeated, and then I found
that OpenIndiana, FreeBSD boot loader or not, still has an
"installgrub" program.  So I ran it:

   installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c3t0d0s0

and it installed GRUB, not where I asked it to -- i.e., (hd0,7),
because that's where all the disk devices are if there's no "p" in
their names -- or not only where I asked it to, but in the MBR, or
also in the MBR.  My old GRUB2 menu was blown away, and when I
rebooted the laptop from powerup I saw the results of my
"installgrub".

Whoa!  Has anyone on this mailing list ever done that?  First of all,
it is not GRUB2, it is GRUB 0.97, and that is problematic, because my
Linux kernels are all on logical volumes, which GRUB2 can boot from
(you may need to do "insmod lvm" first) but GRUB 0.97 cannot.  Solaris
11.3 has moved to GRUB2, but OpenIndiana apparently never did.

That is hardly the most memorable part of the story, though.  I
actually recommend that you do this yourselves, just to experience the
weirdness of it.  The GRUB menu offers you one option -- OS/2.  I
swear I am not making this up.  I selected it, 

Re: [OpenIndiana-discuss] many duplicates - Re: OpenIndiana Hipster at Servethehome (call for a regular minimal stable)

[Alan Coopersmith]

On 04/27/17 05:05 PM, Jerry Kemp wrote:

Guenther,

I don't know if it is just me, or the whole list, but I have received a couple
dozen copies of this email.

is anyone else seeing lots of duplicates?


I am too (and not just this mail, but others from the OI lists as well) - I was
starting to wonder if it was just me.

-alan-


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] many duplicates - Re: OpenIndiana Hipster at Servethehome (call for a regular minimal stable)

[Jerry Kemp]

Guenther,

I don't know if it is just me, or the whole list, but I have received a couple 
dozen copies of this email.


is anyone else seeing lots of duplicates?

Jerry



On 04/26/17 04:50 AM, Guenther Alka wrote:

I have started a thread on a popular forum with many Illumos users about OI
Hipster and would appreciate comments especially about the possibility of future
developments ex a regular minimal stable edition with a dedicated repository
additionally to the rolling updates. Like the OmniOS development model.

https://forums.servethehome.com/index.php?threads/openindiana-2016-10.14499/#post-138978


Gea/Guenther Alka
napp-it.org

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] I Installed OpenIndiana -- Now How Do I Boot It?

[Jay F. Shachter]

Esteemed Colleagues:

I have seen occasional references here and there on this mailing list
to the fact that OpenIndiana now uses the FreeBSD boot loader and no
longer uses GRUB, although I must have missed the discussion that
explained why this was in any way desirable.

However, even the FreeBSD boot loader would be better than no boot
loader at all, which is what I got yesterday after installing
OpenIndiana on my laptop (from the newest image on the website,
OI-hipster-gui-20161030.usb).

The context: I had to get a new laptop a few weeks ago, and because I
work with many different operating systems, I installed many different
operating systems on it.  Presently it has 3 dialects of Linux,
FreeBSD, and, as of yesterday, OpenIndiana, and soon it will have
Haiku (although I have never been able to install either SkyOS or
IcAros on any computer I have ever owned, but I digress).  The idea is
that when you turn on the computer you select the OS that you want to
run.

Actually I installed OpenIndiana for variety, my old laptop had
Solaris 11.3 (and I have more clients who demand knowledge of Solaris
11 than who demand knowledge of OpenIndiana, but my mind craves
variety, which is why I installed Springdale this time for my
RHEL-flavored Linux system, where my old laptop had Oracle Linux).  I
figured it was close enough, and I was prepared for the differences,
like OpenIndiana has none of the new ZFS stuff that Oracle has done on
Solaris (I'm sorry, I know everyone hates Oracle here, but what can I
do, I really like the new zfs share stuff) and like OpenIndiana uses
the FreeBSD boot loader instead of GRUB.  After that it would be a
simple matter of configuring the FreeBSD boot loader to offer my other
operating systems as boot-time options, a technique that, I think, was
in fact discussed on this mailing list a couple months ago or
thereabouts.

Or so I thought.  The USB key from which I booted the laptop in order
to perform the installation, definitely and recognizably uses the
FreeBSD boot loader.  I then happily installed OpenIndiana on Slice 7
of my disk (partitioned in the old msdos manner, meaning that Slice 7
is a "logical" slice inside of extended slice 4).  But the
installation procedure did not put any boot loader whatsoever on the
disk.  When I next booted my laptop from powerup I saw the exact same
GRUB2 menu as before, offering me the same 3 Linux systems and
FreeBSD.

That shouldn't be a problem, though.  Surely there should be some way
of getting GRUB2 to find and boot the OpenIndiana system.  Like, for
example, "chainloader (hd0,7)+1" would a good way of doing that.
Except that it didn't work.  I think it doesn't work in Solaris any
more either, although it once did, you would get a whole other GRUB
menu when you did that.  Similarly, you used to be able to do a
chainloader +1 on a FreeBSD installation, but I think that's stopped
working also, now you have to do kfreebsd /boot/loader (and I can't
get "kfreebsd /boot/kernel/kernel" to work either like it used to,
even after setting all the variables like I'm supposed to, but I
digress).

There does not seem to be any area on the disk from which one can do a
chainloader +1, except the MBR itself, which as I stated just gives me
the same GRUB2 menu as before.  What I need to do is instruct GRUB2
how to boot the OpenIndiana system on (hd0,7).  This is a procedure
that would surely start with "insmod zfs" but I'll be washed and
starched and ironed if I know what I'm supposed to do after that.
At the moment, the only way I know how to boot that system that I
installed yesterday (and subsequently spent hours configuring and
adding software to) is to boot from the installation medium and then
do a "reboot -f -- rpool/ROOT/openindiana".  That works, but it's
bogus; it is not, of course, a long-term solution.

I did it, though, because I refuse to be defeated, and then I found
that OpenIndiana, FreeBSD boot loader or not, still has an
"installgrub" program.  So I ran it:

   installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c3t0d0s0

and it installed GRUB, not where I asked it to -- i.e., (hd0,7),
because that's where all the disk devices are if there's no "p" in
their names -- or not only where I asked it to, but in the MBR, or
also in the MBR.  My old GRUB2 menu was blown away, and when I
rebooted the laptop from powerup I saw the results of my
"installgrub".

Whoa!  Has anyone on this mailing list ever done that?  First of all,
it is not GRUB2, it is GRUB 0.97, and that is problematic, because my
Linux kernels are all on logical volumes, which GRUB2 can boot from
(you may need to do "insmod lvm" first) but GRUB 0.97 cannot.  Solaris
11.3 has moved to GRUB2, but OpenIndiana apparently never did.

That is hardly the most memorable part of the story, though.  I
actually recommend that you do this yourselves, just to experience the
weirdness of it.  The GRUB menu offers you one option -- OS/2.  I
swear I am not making this up.  I selected it, 

Re: [OpenIndiana-discuss] ZFS on Openindiana vs ZFS on oracle linux

[Harry Putnam]

David Johnson  writes:

> Does anyone have any editorial comments on how well ZFS is handled on
> Openindiana
> vs. Oracle Linux? It looks like these may be my only two choices if I
> want to
> have an OS that has native ZFS support, and allow me to get updated
> security patches.

Two points:

1) You might be hard pressed to find a busy open group like this to
   help you with oracle linux... but maybe I'm just thinking of Oracle   
   solaris.

2) You will find some of the best help possible on this group if you
   should chose openindiana.  There is a high number of experts here
   that do willingly share there expertise.

Speaking aa a semi no-nothing on the technical and even practicle
aspects of oi, I have been able to run oi for several years now
primarily due to the help I have received here.

Mind you that mine is strictly a homeboy usage nothing commercial or
even terribly important.  Just a home server to store certain of my
data on like 300 GB of images collected over a number of years of
amatuer photography.



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] I Installed OpenIndiana -- Now How Do I Boot It?

[Jay F. Shachter]

Esteemed Colleagues:

I have seen occasional references here and there on this mailing list
to the fact that OpenIndiana now uses the FreeBSD boot loader and no
longer uses GRUB, although I must have missed the discussion that
explained why this was in any way desirable.

However, even the FreeBSD boot loader would be better than no boot
loader at all, which is what I got yesterday after installing
OpenIndiana on my laptop (from the newest image on the website,
OI-hipster-gui-20161030.usb).

The context: I had to get a new laptop a few weeks ago, and because I
work with many different operating systems, I installed many different
operating systems on it.  Presently it has 3 dialects of Linux,
FreeBSD, and, as of yesterday, OpenIndiana, and soon it will have
Haiku (although I have never been able to install either SkyOS or
IcAros on any computer I have ever owned, but I digress).  The idea is
that when you turn on the computer you select the OS that you want to
run.

Actually I installed OpenIndiana for variety, my old laptop had
Solaris 11.3 (and I have more clients who demand knowledge of Solaris
11 than who demand knowledge of OpenIndiana, but my mind craves
variety, which is why I installed Springdale this time for my
RHEL-flavored Linux system, where my old laptop had Oracle Linux).  I
figured it was close enough, and I was prepared for the differences,
like OpenIndiana has none of the new ZFS stuff that Oracle has done on
Solaris (I'm sorry, I know everyone hates Oracle here, but what can I
do, I really like the new zfs share stuff) and like OpenIndiana uses
the FreeBSD boot loader instead of GRUB.  After that it would be a
simple matter of configuring the FreeBSD boot loader to offer my other
operating systems as boot-time options, a technique that, I think, was
in fact discussed on this mailing list a couple months ago or
thereabouts.

Or so I thought.  The USB key from which I booted the laptop in order
to perform the installation, definitely and recognizably uses the
FreeBSD boot loader.  I then happily installed OpenIndiana on Slice 7
of my disk (partitioned in the old msdos manner, meaning that Slice 7
is a "logical" slice inside of extended slice 4).  But the
installation procedure did not put any boot loader whatsoever on the
disk.  When I next booted my laptop from powerup I saw the exact same
GRUB2 menu as before, offering me the same 3 Linux systems and
FreeBSD.

That shouldn't be a problem, though.  Surely there should be some way
of getting GRUB2 to find and boot the OpenIndiana system.  Like, for
example, "chainloader (hd0,7)+1" would a good way of doing that.
Except that it didn't work.  I think it doesn't work in Solaris any
more either, although it once did, you would get a whole other GRUB
menu when you did that.  Similarly, you used to be able to do a
chainloader +1 on a FreeBSD installation, but I think that's stopped
working also, now you have to do kfreebsd /boot/loader (and I can't
get "kfreebsd /boot/kernel/kernel" to work either like it used to,
even after setting all the variables like I'm supposed to, but I
digress).

There does not seem to be any area on the disk from which one can do a
chainloader +1, except the MBR itself, which as I stated just gives me
the same GRUB2 menu as before.  What I need to do is instruct GRUB2
how to boot the OpenIndiana system on (hd0,7).  This is a procedure
that would surely start with "insmod zfs" but I'll be washed and
starched and ironed if I know what I'm supposed to do after that.
At the moment, the only way I know how to boot that system that I
installed yesterday (and subsequently spent hours configuring and
adding software to) is to boot from the installation medium and then
do a "reboot -f -- rpool/ROOT/openindiana".  That works, but it's
bogus; it is not, of course, a long-term solution.

I did it, though, because I refuse to be defeated, and then I found
that OpenIndiana, FreeBSD boot loader or not, still has an
"installgrub" program.  So I ran it:

   installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c3t0d0s0

and it installed GRUB, not where I asked it to -- i.e., (hd0,7),
because that's where all the disk devices are if there's no "p" in
their names -- or not only where I asked it to, but in the MBR, or
also in the MBR.  My old GRUB2 menu was blown away, and when I
rebooted the laptop from powerup I saw the results of my
"installgrub".

Whoa!  Has anyone on this mailing list ever done that?  First of all,
it is not GRUB2, it is GRUB 0.97, and that is problematic, because my
Linux kernels are all on logical volumes, which GRUB2 can boot from
(you may need to do "insmod lvm" first) but GRUB 0.97 cannot.  Solaris
11.3 has moved to GRUB2, but OpenIndiana apparently never did.

That is hardly the most memorable part of the story, though.  I
actually recommend that you do this yourselves, just to experience the
weirdness of it.  The GRUB menu offers you one option -- OS/2.  I
swear I am not making this up.  I selected it, 

Re: [OpenIndiana-discuss] Avoton based motherboards known tout Work with recent hipster versions?

[Hans J Albertsson]

I realize I should never have said "sunray server".. that was just a side
remark..

I want to know if anyone runs late hipster successfully on some avoton
motherboard, with or without sunrays.

Hans J. Albertsson
>From my Nexus 5

Den 27 apr. 2017 4:14 em skrev "Alexander Pyhalov" :

On 04/27/17 09:29 AM, Carsten Grzemba wrote:

I took a look at the gdm patches and found only gdm-10-sol-notty.patch is
> SRSS related.
> Are there any other patches related SRSS?
>

gdm-10-sol-notty.patch seems to be imported as  lightdm patches
10-set-console.patch and 16-create-device.patch.


At least gdm-01-dynamic-display.patch (together with files/gdmdynamic can
be actual (don't know if something similar is required for lightdm), as
well as gdm-12-setfacl.patch.

If you can create some manual and check which patches are required to run
SRSS with ligthdm, it would be great.

-- 
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Avoton based motherboards known tout Work with recent hipster versions?

[Alexander Pyhalov]

On 04/27/17 09:29 AM, Carsten Grzemba wrote:


I took a look at the gdm patches and found only gdm-10-sol-notty.patch is SRSS 
related.
Are there any other patches related SRSS?


gdm-10-sol-notty.patch seems to be imported as  lightdm patches 
10-set-console.patch and 16-create-device.patch.



At least gdm-01-dynamic-display.patch (together with files/gdmdynamic 
can be actual (don't know if something similar is required for lightdm), 
as well as gdm-12-setfacl.patch.


If you can create some manual and check which patches are required to 
run SRSS with ligthdm, it would be great.

--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [CFT] Xorg 1.18.4 update repository

[Apostolos Syropoulos via openindiana-discuss]

>
> In recent weeks we have fixed several issues with Intel drm driver and
> Xorg server 1.18. So we are ready for second round of testing.
> Kudos go to Aurélien and Gordon for their hard work and, of course,
> to Alan for his help and consulting.
>
Excellent!

> Instructions available here
> https://www.openindiana.org/2016/10/04/call-for-testing-repository-with-xorg-1-18-4-now-available/
> are still relevant.
>
"Still relevant"? I have tried this recipe and I ended up with 2 broken systems!
The original system was installed from the OI + KMS + MATE experimental 
ISOs.Although the login screen appears sometime after boot, the mouse and the 
keyboard do not work. Also, I got many messages about something called 
metainit. Since this receipe does not work, would be possible to have ISOs that 
can be tested without destroying anything?
A.S.

--
Apostolos Syropoulos
Xanthi, Greece




___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Avoton based motherboards known tout Work with recent hipster versions?

[Carsten Grzemba]

On 07.04.17 11:30, Alexander Pyhalov   wrote: 
> 
> On 04/ 7/17 12:02 PM, Hans J Albertsson wrote:
> >At last, after years of fretting, I will build a new zfs+sunray server, and
> >my first take on this is an avoton setup.
> >
> 
> 
> Hello.
> I don't know about Avoton, but I know a bit about SRSS (and its EOL in 
> November 2017). One thing I'd like to note - it depends heavily on GDM (at 
> least versions which I used), which we want to drop in N+1 snapshot. Do you 
> have a desire to create lightdm patches to emulate GDM behavior (look through 
> SRSS-specific gdm patches at 
> https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/desktop/gnome2/gdm/patches/
>  and port them to lightdm + patch SRSS scripts to work with lightdm ?
> -- 
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
> 

I took a look at the gdm patches and found only gdm-10-sol-notty.patch is SRSS 
related.
Are there any other patches related SRSS?

Thanks
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] OpenIndiana Hipster at Servethehome (call for a regular minimal stable)

[Guenther Alka]

I have started a thread on a popular forum with many Illumos users about 
OI Hipster and would appreciate comments especially about the 
possibility of future developments ex a regular minimal stable edition 
with a dedicated repository additionally to the rolling updates. Like 
the OmniOS development model.


https://forums.servethehome.com/index.php?threads/openindiana-2016-10.14499/#post-138978 



Gea/Guenther Alka
napp-it.org

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [CFT] Xorg 1.18.4 update repository

[Alexander Pyhalov]

On 04/26/17 10:01 AM, Predrag Zečević - Technical Support Analyst wrote:


Invalid child image publisher configuration.  Child image publisher
configuration must be a superset of the parent image publisher
configuration.
Please update the child publisher configuration to match the parent.  If
the
child image is a zone this can be done automatically by detaching and
attaching the zone.

The parent image has the following enabled publishers:
PUBLISHER 0: userland
PUBLISHER 1: openindiana.org (non-sticky)
PUBLISHER 2: hipster-encumbered
PUBLISHER 3: localhostoih

The child image has the following enabled publishers:
PUBLISHER 0: openindiana.org
PUBLISHER 1: hipster-encumbered
PUBLISHER 2: localhostoih


pkg: This is an internal error in pkg(5) version 0769bc89.  Please log a
Service Request about this issue including the information above and this
message.
--

Is there any easier way to pass this step, beside booting both zones and
adding userland there (and making openindiana.org non-stiky)?


Well, if you feel that ipkg brand is too restricting, you can try 
switching zones to nlipkg - http://alp-notes.blogspot.ru/2016/03/


--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [CFT] Xorg 1.18.4 update repository

[Predrag Zečević - Technical Support Analyst]

On 04/25/17 17:59, Alexander Pyhalov wrote:

Hi, all.

In recent weeks we have fixed several issues with Intel drm driver and
Xorg server 1.18. So we are ready for second round of testing.
Kudos go to Aurélien and Gordon for their hard work and, of course,
to Alan for his help and consulting.

Lower is original Aurélien's message.
Please, test packages from updated
http://pkg.openindiana.org/xorg-testing/ repository.
Instructions available here
https://www.openindiana.org/2016/10/04/call-for-testing-repository-with-xorg-1-18-4-now-available/
are still relevant.


On 10/ 4/16 11:11 PM, Aurélien Larcher wrote:

Hi,
I am happy to announce that we have prepared a repository with updated
X11 bits:

http://pkg.openindiana.org/xorg-testing/

On the menu:

... a handful of libraries and apps updated,
... Xorg 1.18.4, TurboVNC refreshed with Xorg 1.18,
... some drivers bumps,
... and CVEs picked fresh from the market today.

Find below a short article about the repository and instructions to
install the packages:

https://www.openindiana.org/2016/10/04/call-for-testing-repository-with-xorg-1-18-4-now-available/


Many thanks to Martin for his hard work on drm/i915, of course to
Alexander, Ken, Adam, and also to Alan and the Solaris team with whom
I have been playing catch up in the past months in order to
migrate/update the X11 gate in oi-userland.

Thank you in advance for your feedback.
Kind regards

Aurélien






Hi all,

I wanted to give it a try, and stuck at step 4:

$ sudo pkg -R /mnt update

because I have 2 zones and update complains:
--
A 'pubcheck-linked' operation failed for child 'zone:builder' with an 
unexpected

return value of 99 and generated the following output:
Traceback (most recent call last):
  File "/usr/bin/pkg", line 5444, in handle_errors
__ret = func(*args, **kwargs)
  File "/usr/bin/pkg", line 1816, in __dispatch
rv = op_func(op, _api_inst, **pwargs)
  File "/usr/bin/pkg", line 4047, in pubcheck_linked
api_inst.linked_publisher_check()
  File "/usr/lib/python2.7/vendor-packages/pkg/client/api.py", line 
206, in wrapper

return f(instance, *fargs, **f_kwargs)
  File "/usr/lib/python2.7/vendor-packages/pkg/client/api.py", line 
1628, in linked_publisher_check

self.__linked_pubcheck()
  File "/usr/lib/python2.7/vendor-packages/pkg/client/api.py", line 
1607, in __linked_pubcheck

self._img.linked.pubcheck()
  File 
"/usr/lib/python2.7/vendor-packages/pkg/client/linkedimage/common.py", 
line 1043, in pubcheck

linked_pub_error=(pubs, ppubs))
PlanCreationException:
Invalid child image publisher configuration.  Child image publisher
configuration must be a superset of the parent image publisher 
configuration.

Please update the child publisher configuration to match the parent.  If the
child image is a zone this can be done automatically by detaching and
attaching the zone.

The parent image has the following enabled publishers:
PUBLISHER 0: userland
PUBLISHER 1: openindiana.org (non-sticky)
PUBLISHER 2: hipster-encumbered
PUBLISHER 3: localhostoih

The child image has the following enabled publishers:
PUBLISHER 0: openindiana.org
PUBLISHER 1: hipster-encumbered
PUBLISHER 2: localhostoih


pkg: This is an internal error in pkg(5) version 0769bc89.  Please log a
Service Request about this issue including the information above and this
message.
--

Is there any easier way to pass this step, beside booting both zones and 
adding userland there (and making openindiana.org non-stiky)?


With best regards.
Predrag Zečević
--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com

Headquarter:  2e Systems GmbH, Königsteiner Str. 87,
  65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas

http://www.2e-systems.com/ - Making your business fly!

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss