Re: [OpenIndiana-discuss] Sun Management Centre

[Alan Coopersmith via openindiana-discuss]

On 5/14/24 11:13, Rainer Heilke wrote:
I think that before I start asking questions, I need to wrap my head around the 
general structure of RBAC. What comes first, that sort of thing. Then my 
questions will at least make sense, and I won't be wasting everyone's time.


I think the Solaris rbac(7) man page is a good start for that:
https://docs.oracle.com/cd/E88353_01/html/E37853/esc-rbac-7.html
though it does refer to some things that aren't in OI/illumos.

Unfortunately, the illumos one is still oriented more towards the application 
developer.


Till: funny how you mention just dealing with openindiana.org pages. Oracle's 
pages all still reference SMC as well. :b Not much help, are they? ;-)


Only the Solaris 10 docs should still reference SMC - the ones for Solaris 11
and later should have all that removed now.  For instance, I don't see any SMC
references in https://docs.oracle.com/cd/E37838_01/html/E61023/index.html .

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] Selecting wrong video driver

[Alan Coopersmith via openindiana-discuss]

On 5/7/24 12:15, Rainer Heilke wrote:

I'm getting the feeling this isn't possible.  To wit:
Xorg.0.log doesn't exist (which seems odd...)


That suggests nothing is even trying to run X11, which could be because it
wasn't installed, as Till suggested.


dmesg shows:
May  7 04:22:25 omar nvidia_modeset: [ID 107833 kern.notice] Loading NVIDIA 
Kernel Mode Setting Driver for UNIX platforms  470.239.06  Sat Feb  3 05:55:09 
UTC 2024

May  7 04:22:25 omar pseudo: [ID 129642 kern.info] pseudo-device: profile0
May  7 04:22:25 omar genunix: [ID 936769 kern.info] profile0 is 
/pseudo/profile@0

Watching it boot, it loads the NVidia and nvidia_modeset drivers, and then 
unloads them again.

root@omar:~# dmesg | grep -i load
May  7 04:20:53 omar nvidia_modeset: [ID 107833 kern.notice] Loading NVIDIA 
Kernel Mode Setting Driver for UNIX platforms  470.239.06  Sat Feb  3 05:55:09 
UTC 2024

May  7 04:20:56 omar nvidia_modeset: [ID 107833 kern.notice] Unloading


That's the kernel, not Xorg, and it's normal for it to load the driver,
let the driver search for hardware it can support, and then unload when
it doesn't find any.

-alan-

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

Re: [OpenIndiana-discuss] Selecting wrong video driver

[Alan Coopersmith via openindiana-discuss]

/var/log/Xorg.0.log should have information on what config files the X server
read, what devices it actually found, and what decisions it made on which
driver to use for them.

It would have to be a very old motherboard to have an Intel graphics chip
that's not part of an Intel CPU - they merged them into a single unit years
ago.  But X won't assume an nvidia card based on the CPU, only on the PCI
device ids it finds that match nvidia's vendor id.

-alan-

On 5/6/24 18:59, Rainer Heilke wrote:

Hi.
xrandr called it an Intel graphics card. The intel_drv.so driver worked solidly 
under FreeBSD. I think X keeps thinking it's an NVidia card because it's an AMD 
CPU. But Gigabyte seems to have used an intel chip on the motherboard. The 
NVideo driver hasn't worked under any flavour of Unix/Linux I've tried.

Rainer


-- Original Message --
 From "Rainer Heilke" 
To "Alan Coopersmith" ; "Discussion list for 
OpenIndiana" 

Date 2024-05-06 6:29:09 PM
Subject Re: [OpenIndiana-discuss] Selecting wrong video driver


-- Original Message --
From "Alan Coopersmith" 
To "Discussion list for OpenIndiana" ; 
"Rainer Heilke" 

Date 2024-05-06 6:17:15 PM
Subject Re: [OpenIndiana-discuss] Selecting wrong video driver


On 5/6/24 18:10, Rainer Heilke wrote:

Greetings.
Which file is Hipster using to define the video driver to use? X is trying 
to use the NVidia driver, which fails. Under FreeBSD, the Intel driver 
worked, so I'm hoping it will here as well. But none  of the files I've 
found that mention the NVidia driver seem to actually be an Xorg config file.


Like Xorg on all other platforms, it will use /etc/X11/xorg.conf if it exists,
or config snippets in /etc/X11/xorg.conf.d/ but the default configuration
doesn't use a config file, but lets Xorg check for available video devices
and uses its internal mapping of PCI vendor ids to drivers to decide which
drivers to use for those.

-- -Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


Hi.
That make sense, thanks. It also explains why I can't find a config file to 
edit.
So, is there an "official" way to override the driver X is using? Do I need to 
hack together a config file to do this?

Thanks again,
Rainer





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


--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] Selecting wrong video driver

[Alan Coopersmith via openindiana-discuss]

On 5/6/24 18:29, Rainer Heilke wrote:

On 5/6/24 18:10, Rainer Heilke wrote:

Greetings.
Which file is Hipster using to define the video driver to use? X is trying to 
use the NVidia driver, which fails. Under FreeBSD, the Intel driver worked, 
so I'm hoping it will here as well. But none  of the files I've found that 
mention the NVidia driver seem to actually be an Xorg config file.


Like Xorg on all other platforms, it will use /etc/X11/xorg.conf if it exists,
or config snippets in /etc/X11/xorg.conf.d/ but the default configuration
doesn't use a config file, but lets Xorg check for available video devices
and uses its internal mapping of PCI vendor ids to drivers to decide which
drivers to use for those.


Hi.
That make sense, thanks. It also explains why I can't find a config file to 
edit.
So, is there an "official" way to override the driver X is using? Do I need to 
hack together a config file to do this?


You should just ba able to create a file named
  /etc/X11/xorg.conf.d/50-driver.conf
that contains:

Section "Device"
Identifier  "Card0"
Driver  "vesa"
EndSection

(change "vesa" to the name of the driver module you want to use)

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] Selecting wrong video driver

[Alan Coopersmith via openindiana-discuss]

On 5/6/24 18:10, Rainer Heilke wrote:

Greetings.
Which file is Hipster using to define the video driver to use? X is trying to 
use the NVidia driver, which fails. Under FreeBSD, the Intel driver worked, so 
I'm hoping it will here as well. But none  of the files I've found that mention 
the NVidia driver seem to actually be an Xorg config file.


Like Xorg on all other platforms, it will use /etc/X11/xorg.conf if it exists,
or config snippets in /etc/X11/xorg.conf.d/ but the default configuration
doesn't use a config file, but lets Xorg check for available video devices
and uses its internal mapping of PCI vendor ids to drivers to decide which
drivers to use for those.

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] Screen locking with XScreenSaver disabled

[Alan Coopersmith]

On 1/14/24 15:17, hput wrote:

Till Wegmueller  writes:


Hi

Check all other system settings if you have another Screensaver. Mate
has it's own AFAIK.


The thing is, as you see in the small image of what I see on screen:



It is the very Xscreensaver installed in my OS:
  pkg list |grep xscreen
  desktop/xscreensaver6.8-2023.0.0.0i--

And is disabled in gui:


"Disable Screen Saver" as shown in that gui only disables the display of
animations when the screen is idle, locking is a separate preference/setting.

--
    -Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] Questions about /var/pkg

[Alan Coopersmith]

On 1/13/24 08:41, Goetz T. Fischer wrote:

the first and foremost problem of ips is speed.


Someone looking to improve that might want to check out the recent performance
improving commits to https://github.com/oracle/solaris-ips/commits/master/ and
see if they cherry-pick to OI's fork.

-alan-


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

Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages

[Alan Coopersmith]

On 1/10/24 15:26, Matthew R. Trower wrote:
I wonder why we don't have source in our build system.  Sun didn't publish 
sources for some components because they couldn't get licenses, but that 
shouldn't have been the case here.  It's just idle speculation on my part, don't 
worry about it.


For things like jedit, it may just be that no one ever translated the build
recipe from the old OpenSolaris Desktop rpm-style spec file to the Userland
Makefile used by OI.  I think hg.openindiana.org used to have a mirror of the
spec files from opensolaris.org, but all those sites are offline now, and I
don't know if or where a public mirror would still exist.  When OI started,
it first built all the sources in the formats OpenSolaris published, but over
time it simplified the build process from a mish-mash of a dozen different
build systems into the oi-userland combined repo for all of them, but that
required people who cared about each package to do the translation to the
common build system.

-alan-


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

Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages

[Alan Coopersmith]

On 1/10/24 01:33, Marcel Telka wrote:

On Tue, Jan 09, 2024 at 04:08:13PM -0600, Matthew R. Trower wrote:

For the CDE packages, we don't ship an entire CDE, right? So all they can do


We do ship this:

$ pkg list -a | grep '\'
cde/calendar-manager-server   0.5.11-2013.0.0.0  ---
cde/cde-runtime   0.5.11-2013.0.0.0  ---
cde/cde-utilities 0.5.11-2013.0.0.0  ---
cde/help-viewer   0.5.11-2013.0.0.0  ---
consolidation/cde/cde-incorporation   0.5.11-2013.0.0.0  i--
$

I do not know how complete it is.


It is very much incomplete - that's the set we kept for Solaris 11/OpenSolaris
after removing the bulk of CDE. The CDE desktop & GUI applications are all gone.
What's left is a few binary compatibility packages for 3rd party applications
that used the CDE libraries, shipped their help docs in the CDE helpviewer
format, or called a small handful of CDE helper utilities.  The calendar server
was also retained so that servers could move to OpenSolaris/Solaris 11 and still
support calendars for CDE desktop users running on Solaris 10 still.

The versions you have are known to have a number of security bugs, as has been
reported via Oracle's security bulletins over the past 13 years.

--
    -Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] running sunpro binaries

[Alan Coopersmith]

On 1/9/24 14:50, Goetz T. Fischer wrote:

yes okay, compatibility reasons. but my question was: "does it still make sense 
to use sunpro
performance wise?"


For SPARC?  Probably.  Much more effort went into SPARC performance for
the Studio compilers than for gcc or llvm.

For x86? Maybe not.  Studio only knows about x86 CPUs up to the Skylake
generation, while Intel has contributed code to gcc & llvm for newer processors,
and both of those compilers have continued to improve their optimizers in other
ways as well.

But really, the only way to tell for your code is to compile & measure your
code with the compilers in question.

-alan-


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

Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages

[Alan Coopersmith]

On 1/9/24 14:08, Matthew R. Trower wrote:
Motif itself (while not on this list) is a curious situation.  It was open 
sourced along with CDE, so we could actually update to a source release.  From 
what I recall however, there was at a breaking change in the open source 
codebase which prevents backwards/forwards compatibility between the two.  This 
really sucked when I had a mix of applications depending on both the closed and 
open releases.  However...


Yes, I believe the open source OpenMotif 2.3 is not binary compatible with the
Solaris closed source Motif 2.1.  That shouldn't be a problem for the packages
in OI, if OI rebuilt all the packages to use OpenMotif, just for running 
programs built against the Solaris libraries.


Am I correct in observing, that the only remaining packages depending on our 
Motif will be developer/opensolaris/X and x11/keyboard/accessx?


developer/opensolaris/X was the set of package dependencies needed to build the
OpenSolaris X consolidation, and doesn't make sense for OI to maintain now that
all the X packages are folded into oi-userland instead.  There is no actual
software built in developer/opensolaris/X - it's solely a set of package
dependencies.  x11/keyboard/accessx is mainly interesting for running CDE or
other setups without the accessibility controls provided in the desktop
environment - it's not necessary for GNOME which has accessibility controls
in it's settings apps, and I suspect is not needed for MATE either.

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] [oi-dev] Heads-Up: Obsoletion of 39 old packages

[Alan Coopersmith]

On 1/9/24 09:07, Marcel Telka wrote:

On Tue, Jan 09, 2024 at 08:41:14AM -0800, Alan Coopersmith wrote:

A few are open source - for instance, I could point you to the sources for
x11/network/x11-network-proxies - but no one uses that in a world where
ssh X11-Forwarding is prevalent, which is why I removed that package from
Solaris and declared the upstream sources unmaintained and suggested that
distros remove them.


Thanks for insights.  This caused I looked closer at x11/network/rstart
which is still required by mate_install and I noticed it is deprecated
too, so I created https://github.com/OpenIndiana/oi-userland/pull/15571 .


I don't know why it ever would have depended on rstart - an obscure method
to start X apps remotely in the days before ssh, but it shouldn't any more.

https://lore.kernel.org/distributions/1ea25603-171c-062e-bc02-bcdfc3acd...@oracle.com/T/#u
is the advice I gave distros last year on unmaintained packages from X.Org.

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] [oi-dev] Heads-Up: Obsoletion of 39 old packages

[Alan Coopersmith]

On 1/9/24 07:24, Marcel Telka wrote:

All of them are:
- very old - they are more than 10 years old
- not maintained - we have no knowledge how to build them (there are no
   build recipes for them in oi-userland)


A fair number of them are actually impossible for you to maintain as we
never released the sources for them (things like the Solaris CDE & Motif
packages), and are likely just repackaging of the redistributable binaries
from OpenSolaris, complete with the bugs and security holes they had back
in 2010.

A few are open source - for instance, I could point you to the sources for
x11/network/x11-network-proxies - but no one uses that in a world where
ssh X11-Forwarding is prevalent, which is why I removed that package from
Solaris and declared the upstream sources unmaintained and suggested that
distros remove them.

--
    -Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] running sunpro binaries

[Alan Coopersmith]

On 1/8/24 17:55, Goetz T. Fischer wrote:

hi again,

i tried to run something compiled with sunpro on solaris 11 on indiana and it 
almost worked. i put the
additional libs in place and everything looked fine. however, running the 
program in question failed
with:

ld.so.1: prog: fatal: prog: hardware capability (CA_SUNW_HW_2) unsupported: 
0x80  [ RDSEED ]

of course the first impression is that the cpu simply doesn't support RDSEED 
but that's not the case. it
does support it and the program in question runs fine on the same machine under 
solaris 11.
so it seems like something sunpro produces gets misinterpreted.

maybe someone else ran into the same problem and found a solution?


Unfortunately, illumos & Solaris diverged on the id's used for hardware
capabilities added after the fork.

On illumos, AV_386_2_RDSEED is 0x0080 and AV_386_2_BMI2 is 0x0008,
but on Solaris, AV2_386_BMI2 is 0x0080 and AV2_386_RDSEED is 0x0800.
(You can see this in the /usr/include/sys/auxv_386.h file on each system.)

You might be able to use "env LD_DEBUG=cap" to see what capabilities the OS
thinks your hardware supports and "env LD_HWCAP=+RDSEED" to override that
detection.

More info about this is documented in
https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/11.4/linkers-libraries/capability-processing.html
and on the illumos side in https://illumos.org/man/1/ld.so.1 .

-alan-

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

Re: [OpenIndiana-discuss] Thunderbird 115.3.1

[Alan Coopersmith]

On 10/13/23 12:26, Udo Grabowski (IMK) wrote:

Don't expect too much in
these days from reporting bugs at mozilla, they most likely will
be closed by a bot after a while...


Sometimes someone new comes along to fix them much much later:

https://arstechnica.com/gadgets/2023/10/22-year-old-firefox-tooltip-bug-fixed-in-a-few-lines-offering-hope-to-us-all/

-alan-

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

Re: [OpenIndiana-discuss] warning: new thunberbird crashes nvidia and nvidia-470 (works with nvidia-390)

[Alan Coopersmith]

On 10/5/23 09:53, Bob Friesenhahn wrote:
If a mere client application can cause the display server to crash, might this 
appear to be a severe security issue?


We only saw application crashes here, not the display server.  (Remember
that the nvidia packages include not just the kernel & Xorg drivers, but
also the OpenGL libraries loaded into applications on the X client side.)

--
    -Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] warning: new thunberbird crashes nvidia and nvidia-470 (works with nvidia-390)

[Alan Coopersmith]

On 10/3/23 23:19, Andreas Wacknitz wrote:

After updating thunderbird to the latest version 115.3.1 I have
experienced instant crashes using either nvidia(-535) or nvidia-470 drivers.
Going back to -390 makes thunderbird usable again. Thus, the problem
seems to be located at the newer NVIDIA drivers.


When our nvidia expert looked into it, he found the 115.x version of Firefox
& Thunderbird were mixing OpenGL & EGL calls in a way that works with Mesa
but not the Nvidia drivers, and applied a workaround to stop it from using
EGL for now to avoid that:

https://github.com/oracle/solaris-userland/blob/master/components/desktop/firefox/patches/firefox-115-glx-only.patch

-alan-

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

Re: [OpenIndiana-discuss] pkg folder size escalated

[Alan Coopersmith]

On 5/18/23 02:39, Goetz T. Fischer wrote:

i know what illumos is and where it came from and i didn't imply it had to be 
the same either. my
question was about the size of the pkg folder and that i think it's too big. 
which then turned out to be
right considering the solution with flush-content-cache-on-success and its 
result. the latter should be
True by default if i may suggest that.


Solaris changed the default to True before 11.0 shipped:
https://github.com/oracle/solaris-ips/commit/528306cd9b19b442f56ebad250d3caf15420d077
but I believe the full change also required changes to the
distro-const manifests which are not openly published.

-alan-

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

Re: [OpenIndiana-discuss] Cups problems

[Alan Coopersmith]

On 5/16/23 09:37, Udo Grabowski (IMK) wrote:

I've found a few problems with cups

1) it wants system/volatile/cups, but /system/volatile doesn't exist.
    Works if created manually and restart cups/in-lpd and /scheduler.
    Either system/volatile should be created somehow after boot before
    cups starts, or cups should be patched to put that into /var/run/cups;
    but...


On Solaris, /etc/svc/volatile and /var/run were combined & renamed into
/system/volatile and a symlink made from /var/run to /system/volatile for
backwards compatibility, but I didn't think illumos/OI had made that change.
(While Solaris made the change in the 11.0 release, it happened in snv_159,
after the ON source releases ended.)

The OI makefile seems to have copied the --with-rundir=/system/volatile/cups
from the Solaris makefile though, which may be a mistake:

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/print/cups/Makefile#L66

https://github.com/oracle/solaris-userland/blob/master/components/cups/Makefile#L59


2) ... it wants /var/run/cups/, but that doesn't exist. Should be created
    when it installs.


Both /var/run & /system/volatile are tmpfs filesystems, so are recreated
empty from scratch on every boot and services using them need to create
any subdirectories they need (whether in the daemon code or the service
method startup script) - packages can't install files or directories there
since they'll disappear on reboot.

--
    -Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] what do pkg install phases mean?

[Alan Coopersmith]

On 3/5/23 07:41, Richard L. Hamilton wrote:

And what drives the decision whether to create a new boot environment, or a 
backup boot environment (or maybe neither)?


You can control those decisions with options such as --require-new-be and
--require-backup-be and with properties such as be-policy & create-backup
- all of which are described in the pkg(1) man page.

By default, a new BE is created any time a pkg update sees "reboot-needed"
on an update it is applying to the currently running BE - for instance, you
can see it on the lines for the driver module files in:
https://pkg.openindiana.org/hipster/manifest/0/driver%2Fnetwork%2Fe1000g%400.5.11%2C5.11-2023.0.0.21520%3A20230305T011413Z

You can see the documentation of "reboot-needed" on the pkg(7) man page.

--
    -Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris


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

Re: [OpenIndiana-discuss] OI Installer offers to visit wiki.openindiana.org

[Alan Coopersmith]

On 2/25/23 03:18, James Madgwick wrote:

Hello,

Yes the Wiki has been replaced. It's interesting that the installer
is not up to date. There's no mention of the Wiki in the repo for it
(https://github.com/OpenIndiana/slim_source)?
It has also been removed from the welcome pages -
(https://github.com/OpenIndiana/openindiana-welcome/pull/14).

It's in a png, so text search won't find it:
https://github.com/OpenIndiana/slim_source/blob/oi/hipster/usr/src/cmd/gui-aux/install-03.png

Also, these images need to be updated to stop sending people to freenode IRC:
https://github.com/OpenIndiana/slim_source/blob/oi/hipster/usr/src/cmd/gui-aux/install-02.png
https://github.com/OpenIndiana/slim_source/blob/oi/hipster/usr/src/cmd/gui-aux/install-04.png

And this could probably use some updates as well:
https://github.com/OpenIndiana/slim_source/blob/oi/hipster/usr/src/cmd/gui-aux/install-05.png

-alan-

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

Re: [OpenIndiana-discuss] warning - libtiif will be updated and will damage many packages until they have been rebuild - update process finished

[Alan Coopersmith]

On 1/30/23 12:59, Andreas Wacknitz wrote:

Alas, during the process I found out that binutils-2.40 is broken for
us. The problem was visible in a newly created qt5 version where all
binaries were broken.
The culprit seems to be gstrip. I have downgraded to binutils-2.39 with
fake 2.40 version information (because our version numbers cannot decrease).
After that it was needed to rebuild qt5 again to get working binaries.


jperkins found similar problems with gstrip:
https://federate.me.uk/@jperkin/109771972347227241

-alan-

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

Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

[Alan Coopersmith]

On 4/11/22 07:49, Bob Friesenhahn wrote:
The above only applies to how the client gets its name.  At one time I used a 
Solaris DHCP server (and it was great) but I think that server has been 
deprecated in Solaris and likely removed since then. 


Yes, Solaris 11.4 only ships the ISC DHCP server, and no longer includes the old
Sun DHCP server.

-alan-

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

Re: [OpenIndiana-discuss] wiki.openindiana.org needs to be re/started and fixed

[Alan Coopersmith]

On 11/2/21 8:58 PM, Nikola M. wrote:
Wikis do not need "appointed censor" to decide only by itself without any 
discussion or process what is to stay on Wiki and what is not,


If you have a publicly writable wiki on the internet you absolutely need
this or your wiki soon becomes full of spam and completely unusable.

It's not the ideal situation, or what anyone wants, but it is reality.

Wikis require someone to do work, not just someone to demand others do it.

-alan-

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

Re: [OpenIndiana-discuss] NVIDIA-470 driver problem

[Alan Coopersmith]

On 9/29/21 6:44 AM, Predrag Zecevic wrote:
However, IF I remove those packages (NVDAgraphics, NVDAgraphicsr), and install 
*pkg:/driver/graphics/nvidia-470@0.470.74-2020.0.1.0* (e.g. same one), that 
process refuses to start...

There may be some more clues in /var/log/Xorg.0.log and /var/log/lightdm/.

-alan-

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

Re: [OpenIndiana-discuss] [oi-dev] I've given up on gnome-doc-utils

[Alan Coopersmith]

On 7/5/21 2:58 PM, Jason Martin wrote:

https://wiki.gnome.org/Projects/GnomeDocUtils/MigrationHowTo

yelp-tools


Yes, we dropped gnome-doc-utils from Solaris after migrating to GNOME 3
as all our upstream packages had moved to yelp-tools and we EOL'ed the
few things on our end that had used it, like the IPS Package Manager GUI.

-alan-

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

Re: [OpenIndiana-discuss] automount does not work!

[Alan Coopersmith]

On 6/18/21 11:34 AM, Gary Mills wrote:

There does appear
to be some interaction between hal (supplied by illumos) and X11
(supplied by OI).


On Solaris & OI, the Xorg server relies on hal to let it know when USB
input devices have been hotplugged so it can attach to mice, keyboards,
tablets, etc.  It should not interfere with the mounting of USB storage
devices.

-alan-

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

Re: [OpenIndiana-discuss] Which OI service cleans up hidden NFS files?

[Alan Coopersmith]

On 5/4/21 3:38 PM, Judah Richardson wrote:

I did some searching about the error message and found this Solaris
documentation page
 about
removing hidden NFS files. It says that the above error is due to something
called nfsfind, but that nfsfind should be superseded by a service called
svc:/network/nfs/cleanup.


It also says that the nfs cleanup service was added in Solaris 11.4, which is
much newer than the pre-Solaris-11.0 base that OpenIndiana/illumos is based on.

Don't you still have the nfsfind command in your root crontab?

https://github.com/illumos/illumos-gate/blob/9ecd05bdc59e4a1091c51ce68cce2028d5ba6fd1/usr/src/cmd/Adm/root#L30

-alan-

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

Re: [OpenIndiana-discuss] Recommended way to migrate to a new release?

[Alan Coopersmith]

On 5/2/21 6:35 AM, Bob Friesenhahn wrote:

On Sun, 2 May 2021, Reginald Beardsley via openindiana-discuss wrote:


My personal preference is for "all known bugs fixed" release points. If 
someone wants to track changes more often then the "pkg update" mechanism 
provides that.


The "all known bugs fixed" release points are not even remotely possible given 
the rolling build/release model.  The release is just a snapshot in time.  Even 
major Linux distributions and FreeBSD are not able to accomplish what you 
describe.  The internal processes that Sun used to internally test and "bake" a 
release for a couple of years are not possible.


Even those never produced a "all known bugs fixed" release - just a "all bugs
considered to be showstoppers for the release" fixed.  I doubt there has been
any "all known bugs fixed" release of a significant operating system in many
decades - there's just so many things that can break that you have to have a
cutoff point to determine what's truly going to hold up your release and what
you can accept and leave until later.  (And later may never come - there are
some bugs that lingered for decades in Sun's bug tracker, never getting fixed
or closed, and I'm sure the same is true in Linux & BSD distros as well.)

--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] Recommended way to migrate to a new release?

[Alan Coopersmith]

On 5/1/21 3:31 PM, Reginald Beardsley via openindiana-discuss wrote:

I tried a text-install of 2021.04.30  into an existing 2020.10.31 pool, but the 
user information didn't propagate to the new BE.  Is this a bug, install 
mistake or the wrong way to update?


The wrong way to update.  Install media is for fresh installs only.
Updates are done via "pkg update".

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] Some internals questions

[Alan Coopersmith]

On 4/22/21 6:40 AM, Reginald Beardsley via openindiana-discuss wrote:

Where is the code that creates the symlinks in /var/run, when is it supposed to 
run and what determines the timing?


If you mean the OpenGL symlinks for graphics cards:

https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/x11/ogl-select/files

The timing is determined by when SMF runs the ogl-select service, depending
on it's position in the SMF service dependency graph.

--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] 2021.04_rc1 on Z840 crashes after install

[Alan Coopersmith]

On 4/21/21 2:31 PM, Reginald Beardsley wrote:
The Xorg server is loading both the nvidia driver and the vesa driver. Is that 
likely to cause a crash? I don't understand what is causing it to load the vesa 
driver as it doesn't seem to find an xorg.conf file and uses a builtin.


When there is no xorg.conf, it's normal for Xorg to load multiple drivers 
(usually including vesa) as part of the probe routines, and then once it's

found a driver to use, to unload the rest.  This shouldn't cause a crash.

--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] 2021.04_rc1 on Z840 crashes after install

[Alan Coopersmith]

On 4/21/21 12:51 PM, Reginald Beardsley via openindiana-discuss wrote:

  A bit more information.

There are symlinks in /usr/lib/xorg that point to symlinks in /var/run which 
point back to /usr/X11 on the Desktop Live Image. The /var/run links are not 
present on the installed system.


They are created at boot when the system detects what graphics devices are
in use, via the ogl-select SMF service - make sure it is enabled & running.

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] Replacing Solaris 10 u8

[Alan Coopersmith]

On 3/24/21 11:13 AM, Reginald Beardsley via openindiana-discuss wrote:

I've still not found the Oracle EULA for 11.4.


It depends on whether you're paying for it or not.

If you're not paying, then:
https://www.oracle.com/downloads/licenses/solaris-cluster-express-license.html

If you're paying, I believe the license terms are included with the support
contract terms, but I don't have a handy URL for those.

--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Alan Coopersmith]

On 3/17/21 6:24 AM, Stephan Althaus wrote:

On 03/17/21 02:09 PM, Gary Mills wrote:
On Tue, Mar 16, 2021 at 04:27:31PM +0100, Carsten Grzemba via 
openindiana-discuss wrote:

I made available a firefox package 68esr for testing

Unfortunately for the moment there is a restriction!
There is a setting in /etc/system necessary:

set _userlimit=0x7fffc000

whithout this, FF will raise a assertion in JS code.

It sounds as if we need the illumos developers to make the appropriate
change to the illumos kernel or to the linker so that this setting
will not be necessary.  An illumos bug report would be a good starting
point.



Hm..

How is this handled with Solaris and solaris-userland ?


Solaris 11.4 on x86 defaults to the userlimit setting shown above.

Solaris 11.4 on SPARC uses a linker mapfile to "reserve" all the
memory above that point, making it effectively use that userlimit
for the Firefox process.

See https://openindiana.org/pipermail/oi-dev/2021-March/032536.html

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] Updated NVIDIA drivers

[Alan Coopersmith]

On 3/14/21 9:33 AM, Alan Coopersmith wrote:

On 3/13/21 4:32 PM, John D Groenveld wrote:
In message , Alan Coopersmith 
writes:

There is no way to script this inside IPS packages - instead your script
would have to be outside the packaging system and run pkg commands to
install/uninstall the packages as neto.


Did Oracle consider using a mediator to set the system's nVidia version
branch?
http://pkg.oracle.com/solaris/release/manifest/0/driver%2Fgraphics%2FnvidiaR304@0.304.137.0%2C5.11-11.4.0.0.1.1.0%3A20180226T183047Z> 

http://pkg.oracle.com/solaris/release/manifest/0/driver%2Fgraphics%2FnvidiaR340@0.340.104.0%2C5.11-11.4.0.0.1.1.0%3A20180226T183049Z> 



Considered and rejected as nvidia's design doesn't allow multiple versions to be
installed on the system at the same time to mediate between.


Also, IPS mediator support is limited to changing symlinks - it doesn't support
changing the /etc/driver_aliases entries needed when switching between versions
of the nvidia driver to reflect the different subsets of hardware devices they
support.

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] Updated NVIDIA drivers

[Alan Coopersmith]

On 3/13/21 4:32 PM, John D Groenveld wrote:

In message , Alan Coopersmith 
writes:

There is no way to script this inside IPS packages - instead your script
would have to be outside the packaging system and run pkg commands to
install/uninstall the packages as neto.


Did Oracle consider using a mediator to set the system's nVidia version
branch?
http://pkg.oracle.com/solaris/release/manifest/0/driver%2Fgraphics%2FnvidiaR304@0.304.137.0%2C5.11-11.4.0.0.1.1.0%3A20180226T183047Z>
http://pkg.oracle.com/solaris/release/manifest/0/driver%2Fgraphics%2FnvidiaR340@0.340.104.0%2C5.11-11.4.0.0.1.1.0%3A20180226T183049Z>


Considered and rejected as nvidia's design doesn't allow multiple versions to be
installed on the system at the same time to mediate between.

-alan-

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

Re: [OpenIndiana-discuss] Updated NVIDIA drivers

[Alan Coopersmith]

On 3/13/21 4:27 AM, Stephan Althaus wrote:
But i don't know how to integrate this into the build system nor at packaging 
level.


There is no way to script this inside IPS packages - instead your script
would have to be outside the packaging system and run pkg commands to
install/uninstall the packages as needed.

-alan-

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

Re: [OpenIndiana-discuss] Why OpenIndiana online package search still query something from opensolaris.org?

[Alan Coopersmith]

I don't see it waiting, but I do see in the page source, at the bottom
of https://pkg.openindiana.org/hipster/en/index.shtml :

Re: [OpenIndiana-discuss] SMF and X11 startup problem

[Alan Coopersmith]

On 2/23/21 4:26 PM, Reginald Beardsley via openindiana-discuss wrote:

Does anyone know what the missing environment variable is or where the 
reference to

/usr/X11/lib/modules/extensions//libglx.so

is located?


The ogl-select SMF service should create the right links - make sure it is 
enabled.

--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] How to install MATE or Gnome Desktop?

[Alan Coopersmith]

On 2/15/21 3:34 AM, Jason Long via openindiana-discuss wrote:

Why nobody fixed it and why VirtualBox doesn't have any "illumos" and 
"OpenIndiana" in its list?


I believe this is because no one has done the work to contribute that to the
open source project, and no one has paid Oracle's VirtualBox team to do the
work themselves.  OS'es with tiny user bases don't get support added by just
wishing for it, and having an already listed OS be close enough for most
purposes pushes it even further down the priority list.

-alan-

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

Re: [OpenIndiana-discuss] Porting an application to OpenIndiana.

[Alan Coopersmith]

On 2/11/21 1:14 PM, Jason Long wrote:

Thank you so much.
Excuse me, can I send email to you?


Sorry - I don't do private consulting.  I answer questions on the mailing list
when my time allows and I know the answer, but often times one or the other of
those won't apply, and others on the list can help instead, so mailing the list
is usually best, since you'll have no way of knowing which list members have
the right combination of knowledge and time at any given point.

-alan-

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

Re: [OpenIndiana-discuss] Porting an application to OpenIndiana.

[Alan Coopersmith]

On 2/11/21 8:59 AM, Jason Long via openindiana-discuss wrote:

Hello,
If someone wants to porting an application from an operating system to another 
operating system, then he\she must rewrite that program from scratch?


No - most applications have a large amount of code that's specific to the
application itself which is operating system independent - for instance a
stock market application is going to have code for tracking changes in
stock prices or figuring out gains and losses that doesn't depend on the
OS in use; while a database is going to have things like SQL handling code
that doesn't change between platforms.

But applications also have a fair amount of code to interact with platform
interfaces to do things like network communications, read & write to disk
or other storage, display output, etc.  If they're written in something
like Java or Python that provides it's own platform routines for that, to
hide the underlying OS details, then there may be very little work to port
to a new OS, unless they need functionality not provided by the platform.

If they're written in something else, without those platform routines,
such as C or C++, then the work may increase and how much depends on
the OS'es you are porting between.  Porting from another platform in
the Unix family - Linux, BSD, AIX, etc. - will be much easier than
porting from Windows or MacOS, since a large amount of the OS
interfaces are the same between the Unixes - especially for the subset
defined in the POSIX standard.  You can see this in the large amount of
open source software shipping already in OpenIndiana, where the same
source code for things such as vim, emacs, nano, Firefox, perl, python,
etc. is used on OpenIndiana as on BSD & Linux, with just some small
sections of the code which check for the OS and call the OS-specific
interfaces for that.

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] What is the Solaris ld linker's equivalent to GNU's -dynamic-linker?

[Alan Coopersmith]

On 2/11/21 8:03 AM, cretin1997 via openindiana-discuss wrote:

I have a linker script which uses many of:

-dynamic-linker /lib64/ld-linux-x86-64.so.2

I tried to use it on OpenIndiana by changed it to:

-dynamic-linker /lib/64/ld.so.1

but the Solaris ld linker doesn't happy with it:

ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1763 (illumos)
ld: fatal: option -d has illegal argument 'ynamic-linker'
ld: fatal: flags processing errors

Please help.


https://illumos.org/man/1/ld documents --dynamic-linker as an alias for -I
- is the problem the lack of the double-dash in your script?

I'd be tempted to just delete it altogether, since the linker will pick the
right value on its own, but if you needed something non-default, try adding
the second dash or switching to -I.

-alan-

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

Re: [OpenIndiana-discuss] What is the equivalent packages on OI?

[Alan Coopersmith]

On 2/6/21 11:46 PM, cretin1997 via openindiana-discuss wrote:

They are Ubuntu packages:

gcc libncurses5-dev libtinfo5 libffi-dev libgl1-mesa-dev
libx11-dev libxext-dev libxrender-dev libxrandr-dev libxpm-dev


With the IPS package system, there usually aren't separate -dev packages,
but the dev files are part of the main package, with the "devel" facet
used to control whether or not they are installed, so the OI equivalent
to most of those is the same name with "-dev" removed.  (For libgl1-mesa-dev,
you'll also need to remove "libgl1-" - it's just "mesa" here, and libncurses5
is just "ncurses".)

For gcc, pick a version:
https://pkg.openindiana.org/hipster/en/search.shtml?token=gcc=Search

-alan-

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

Re: [OpenIndiana-discuss] ~6 minutes to OI banner/boot options in text install

[Alan Coopersmith]

On 1/30/21 9:54 AM, John D Groenveld wrote:

Is anyone here free to explain why nVidia still provides its binaries
for OpenSolaris and how much longer its obligated to provide that
support?


Do they actually claim to support OpenSolaris or OpenIndiana?  I thought
they just provided binaries for Solaris 10 & 11 that happened to work on
systems that maintain a high enough level of binary compatibility with
Oracle's releases.

-alan-

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

Re: [OpenIndiana-discuss] python-gi in OI?

[Alan Coopersmith]

On 1/25/21 10:59 PM, Tony Brian Albers wrote:

On 01/25/21 04:45 PM, Alan Coopersmith wrote:

On 1/25/21 4:24 AM, Tony Brian Albers wrote:

Hi guys,

I'm trying to get virt-manager to work. But it complains about not being
able to load gi:

tba@emu:/opt$ virt-manager
Traceback (most recent call last):
     File "/usr/bin/virt-manager", line 6, in 
   from virtManager import virtmanager
     File "/usr/share/virt-manager/virtManager/virtmanager.py", line 15,
in 
   import gi
ModuleNotFoundError: No module named 'gi'
tba@emu:/opt$


Does anyone know if we have gi somewhere?


The gi python module comes from the pygobject-* packages:

https://pkg.openindiana.org/hipster/en/search.shtml?token=pygobject=Search


  -alan-


Thanks Alan,

I tried using python3.5, but now I just get a "Namespace LibvirtGLib not
available" so it seems that more stuff is missing.


The gi module is used to load gobject-introspection files, which projects based
on glib (like GTK & gnome, but also some non-GUI software) uses to provide
Python bindings to their API's without having to hand craft the bindings
themselves, instead scanning their C or C++ API's, recording that in the gi
files, and autogenerating Python APIs from the gi files.

So I think you'd need to pkg search for "LibvirtGLib.typelib" to see if there's
a matching gobject-introspection file for this library already packaged - there
may not be if the package wasn't built with gobject-introspection to generate
the files.  (They usually end up in /usr/lib/amd64/girepository-1.0/ or
/usr/lib/girepository-1.0/ for 32-bit versions.)

-alan-

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

Re: [OpenIndiana-discuss] python-gi in OI?

[Alan Coopersmith]

On 1/25/21 4:24 AM, Tony Brian Albers wrote:

Hi guys,

I'm trying to get virt-manager to work. But it complains about not being
able to load gi:

tba@emu:/opt$ virt-manager
Traceback (most recent call last):
File "/usr/bin/virt-manager", line 6, in 
  from virtManager import virtmanager
File "/usr/share/virt-manager/virtManager/virtmanager.py", line 15,
in 
  import gi
ModuleNotFoundError: No module named 'gi'
tba@emu:/opt$


Does anyone know if we have gi somewhere?


The gi python module comes from the pygobject-* packages:

https://pkg.openindiana.org/hipster/en/search.shtml?token=pygobject=Search

-alan-

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

Re: [OpenIndiana-discuss] [External] : How many file systems supported by OI?

[Alan Coopersmith]

On 1/22/21 11:05 PM, Hung Nguyen Gia via openindiana-discuss wrote:

If you could, please give me an accurate list.


https://illumos.org/man/7fs/all

Though many of those are special purpose like devfs and objfs.

The ones you can use to format a disk and store data on are:
 - zfs
 - ufs
 - udfs
 - pcfs

-alan-

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

Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)

[Alan Coopersmith]

On 1/4/21 2:11 PM, Apostolos Syropoulos via openindiana-discuss wrote:

OK I got it but still the question is: Why tkinteris a separate package? IMHO, 
it makes nosense to have as a separate package. Afterall it is part of the core 
python distribution.


Because some people want to install systems without all the X libraries
that Tk brings in, so having Tkinter packaged separately allows that.

-alan-

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

Re: [OpenIndiana-discuss] Wayland on OpenIndiana

[Alan Coopersmith]

On 8/2/20 3:55 PM, Lonnie Cumberland wrote:

Hi All,

I am not sure if I have asked this since I cannot find a record of it, but
can Openindiana run Wayland instead of Xorg?


No, it requires too much in the kernel that Solaris & illumos do not have.

-alan-

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

Re: [OpenIndiana-discuss] Which Oracle Solaris version('s documentation) is closest to OI Hipster's current state?

[Alan Coopersmith]

On 7/19/20 5:05 PM, Judah Richardson wrote:

Hi All,

I'd been using Solaris 11.4's docs for OI but after realizing OI's zfs
share functionality is closer to the "legacy" implementation described
there than Solaris 11.4's, I'm trying to figure out which Solaris version
is closest to OI's current state. That way I can use that version's docs
instead.

Any idea?


Probably Solaris 11.0 from 2011, since that would only have ~1.5 years
divergence from the last open source release of the core OpenSolaris code
that OpenIndiana is based on - but then you don't get coverage of any
of the changes OpenIndiana/illumos have made over the past decade.

-alan-

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

Re: [OpenIndiana-discuss] X apps in lx zone?

[Alan Coopersmith]

On 2/18/20 12:46 PM, PÁSZTOR György wrote:

Hi,

"Alan Coopersmith"  írta 2020-02-05 09:11-kor:

Right - applications expecting DRI/KMS interfaces are going to be sorely
disappointed, and limited to what the underlying illumos kernel provides.


Are you 100% sure about this?
If apps would have direct access to those devices at the same time
X11server does, that could lead to serious deadlock issues, or one writes
over parts in the graphic card's memory what is under the control of the
other one.


Which is why X has the DRI extension to coordinate access with applications
that directly access the graphics hardware (like OpenGL).

https://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure


If you would say, that the Xserver mmap-s or does some other magic to
access the card's memory, than shares the memory area using some X11
extenson and the client (wm/de) could access that like some sysv ipc-way
(eg. shmem), I could understand if that would not work.
Or like fdpassing.


Different generations use mmap, fd passing, or other IPC techniques.


Btw.: In X11 the partys can negotiate who supports which feature.


Thanks, but you really don't need to explain X11 to me, since I've been
working on it for 20 years now.  A much more complete explanation of what
you describe is available in the chapters I wrote of
https://www.x.org/wiki/guide/ .


I would think if the Xserver doesn't support some linux-specific drm/kms
interface (which can be easily the point here) than it would just fallback
to some legacy solution.


Some applications will, some won't - it depends on whether the authors
wanted to put in the effort to code a fallback or not.

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] X apps in lx zone?

[Alan Coopersmith]

Right - applications expecting DRI/KMS interfaces are going to be sorely
disappointed, and limited to what the underlying illumos kernel provides.

-alan-

On 2/5/20 1:38 AM, Till Wegmüller wrote:

Hi Mark


Not exactly. You would be able to pass the X11 Unix socket to the Zone
or use X11 via Network to achieve this. But KDE and others require the
Graphics card to be present for rendering speedup. You can forward the
device to the Zone. But I have absolutely no idea if that works with LX.
Considering they have different userland libraries to access the Card.

Greetings
Till

On 05.02.20 05:57, Mark Kosmowski wrote:

Is it possible to run X applications from within an lx zone?

If so, would it work for the global zone to run the X server and the lx
zone to provide plasma/KDE?
___
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 mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] What pkgs for building gnu stuff

[Alan Coopersmith]

On 1/21/20 8:22 AM, Harry Putnam wrote:

Michal Nowak via openindiana-discuss
 writes:


On 01/19/20 05:55 AM, Harry Putnam wrote:

Does openindian have a package cluster or something similar for
working gnu software building?

If not what are the packages I would need for building emacs?


I don't know what is "package cluster", but we provide the latest GNU
Emacs and thus also it's build dependencies, see
https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/editor/emacs/Makefile#L186
for the list.


Thanks for your response.. by `package cluster' I just meant the
groups of tools and libraries required to build some gnu stuff from
source.

When I build emacs from source on linux I always seem to need to
install a few more libraries or tools so thought someone here might
have some sort of list.


IPS calls them group packages, and it sounds like you're asking for the one
named developer/gnu:

http://pkg.openindiana.org/hipster/manifest/0/developer%2Fgnu%400.5.11%2C5.11-2018.0.0.0%3A20180211T131009Z

You may need more than that to build emacs, and probably want a newer gcc
version than is listed there, but it should be a good start.

If you'd like to suggest updates (like switching to gcc-9 or adding git or
automake-116), you can submit a pull request against:

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/meta-packages/developer-gnu/developer-gnu.p5m

-alan-

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

Re: [OpenIndiana-discuss] OpenIndiana Hipster 2019.10

[Alan Coopersmith]

On 11/10/19 1:12 PM, Till Wegmüller wrote:

You always need to reboot.

IPS never updates the live system but clones it and updates the clone.
This feature is known as Boot Environments. You can manage them with the
beadm utility.


It can update the live system if you're only updating packages not marked
as "need=reboot" - but all kernel & driver packages are marked like that
so any update that includes those will create a new BE and require booting
into it.


image-update and update are the same command. At least they map to the
exact same action. Why we documented image-update i do not know. The
manpage only lists update.


image-update was the original name in IPS, but it's been more than a
decade since it was renamed to just "update", so all the docs should
have been fixed long ago.

-alan-

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

Re: [OpenIndiana-discuss] emacs problems

[Alan Coopersmith]

On 10/28/19 1:13 PM, Andreas Wacknitz wrote:

╭─andreas@saturn ~  ‹master*›
╰─➤  ldd /usr/bin/emacs-gtk-26.3 2>&1 | ggrep libgcc
     libgcc_s.so.1 =>     (file not found)


ldd -v will help show which file has the dependency and then you can
run elfdump -d on that file to see where it is looking for libgcc_s.

-alan-

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

Re: [OpenIndiana-discuss] Survey: What nvidia card you use?

[Alan Coopersmith]

On 10/2/19 12:41 PM, Andreas Wacknitz wrote:

Am 02.10.19 um 21:16 schrieb Michal Nowak:

Hi,

which nvidia graphics card type you use with OpenIndiana?

Currently we ship the version 340 of nvidia Solaris driver, which
supports following cards:
https://www.nvidia.com/Download/driverResults.aspx/135163/en-us.
However, newer devices are not supported in this driver version.

I was wondering if users are fine with a newer version like 390? It
adds new cards but drops old ones. List of supported cards in this
version: https://www.nvidia.com/Download/driverResults.aspx/149144/en-us.

Anyone knows might be affected? (I don't have a plan, just wondering.)


What happened to the GeForce family of cards? The newer driver seem only
to support Quadro and NVS variants, which are NVIDIA's professional lines.


The Solaris README has always only documented the professional lines as
officially supported, since the Solaris driver was intended for use in a
technical workstation, not a consumer rig.

Since the driver is built from the same core source code as the Linux & Windows
drivers, it also supports the GeForce cards, you just have to look at the
README for the corresponding version of the Linux driver to get the model list.

-alan-

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

Re: [OpenIndiana-discuss] Virtualbox is core dumping

[Alan Coopersmith]

On 9/4/19 10:20 AM, Geoff Nordli wrote:

Hi.

I posted this a couple of days on the omnios list, but haven't gotten much 
feedback. I am hoping someone here might have some clues as OI and Omnios share 
the same vbox code.  Posted below is some crash dump information.


I have several machines running vbox without issue.  The only thing I can think 
of here is that this machine has a "newer" Intel Xeon Silver 4110 Processor.


Any other thoughts?



That looks like the crashes we see on Solaris when SMAP is enabled on a CPU
new enough to support it.  The VirtualBox drivers try to access memory that
SMAP blocks access to from kernel space.

https://wiki.openindiana.org/oi/7.2+VirtualBox suggests "Workaround is to put:
set disable_smap=1 in /etc/system and reboot, before starting VirtualBox"

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] apache-mellon package broken

[Alan Coopersmith]

On 8/27/19 7:58 AM, Predrag Zečević - Technical Support Analyst wrote:

:; pkg contents apache-mellon
PATH
$(ETCDIR)/apache2/2.4/samples-conf.d/mellon.conf
$(USRDIR)/apache2/2.4/bin/mellon_create_metadata.sh
$(USRDIR)/apache2/2.4/libexec/mod_auth_mellon.so
$(USRSHAREDIR)/doc/mellon/README.md

e.g:
:; ls -al /etc//apache2/2.4/samples-conf.d/mellon.conf
ls: cannot access '/etc//apache2/2.4/samples-conf.d/mellon.conf': No such file 
or directory


pkg does not expand $(...) variables, so if you "ls /" you'll probably see
several directory names starting with a $ there.

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] SunRay on OI/Hipster

[Alan Coopersmith]

On 8/19/19 9:16 AM, Jonathan Adams wrote:

any chance you can get them to open source the SunRay software? ;-)


Nope - no business reason to justify spending the required amount of
time/effort to open source it.   Open sourcing existing software is
not just flipping a switch - as anyone who lived through the early
days of OpenSolaris can tell you.  It's a lot of human effort to
dig through ancient records to determine if you have all the rights
to do so, and to ensure you're not releasing anything that may
violate NDA's or require a patent license to use.

Doing that for a product you've killed off and aren't making any more
money from is not very likely unless you've got some big partner or
customer willing to make it worth the expense.

-alan-

*Obviously speaking only for myself, not my employer, as always*

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

Re: [OpenIndiana-discuss] SunRay on OI/Hipster

[Alan Coopersmith]

I don't think upstream GDM can work - if I remember correctly it removed the
multi-seat support that Sun Ray needs.   It also dropped ConsoleKit to force
users to systemd, and doesn't have the patches from Solaris to make Sun Ray
work better.

The Solaris-Userland repo has the consolekit support patched in, but not the
rest of the Sun Ray support, so I think using the OI-Userland sources from
before the switch to mate is your best bet.

-alan-

On 8/19/19 3:34 AM, Jonathan Adams wrote:

GDM from here? :

https://github.com/GNOME/gdm

might be worth the pet project to check if it will work.  thanks

Jon

On Mon, 19 Aug 2019 at 10:48, Carsten Grzemba  wrote:




On 19.08.19 11:29, *Jonathan Adams *  wrote:

so a standard install + Mate desktop could possibly work?

no
disable lightdm and build and install the GDM packages with newer versions
than in hipster repo. There is some work, because hipster-repo has set this
packages to '--o' (obsolete)


It'd be a complete shame to have to dispose of 300+ Sunrays (including a
dozen SunRay 3+ boxes)

Jon

P.S. we might be closing some offices in a couple of months, and will
probably be losing the SunRays if that is the case, is anyone interested in
taking possession of any of them? (contact me off list)

On Mon, 19 Aug 2019 at 10:26, Carsten Grzemba via openindiana-discuss <
openindiana-discuss@openindiana.org> wrote:


You can use SunRay on latest Hipster if you review GDM. Mate desktop can
be used. But the Firefox 60 is a little bit slow on filling textareas or
forms.
It is like it refresh the whole page an every keystroke.

On 19.08.19 11:03, Jonathan Adams   wrote:


Hi everyone,

we used to run our SunRays on Solaris 10, back in the day, and then

moved

to Centos in order to get access to updated desktop apps (firefox,

chrome,

wine, xrdp mostly).

We obviously now have issues in that the gtk+ on Centos is ancient and
causes the latest Firefox to crash for some windows (print, "save as"

...).


I'd really like to move back to running them in the Solaris/OI world.

Do you know if it is still possible to run the SunRays on the latest
version of OI/Hipster, and if so does anyone have a guide/walkthrough?

Thanks

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


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


--
Carsten

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




--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] Firefox 60 ESR available

[Alan Coopersmith]

On 5/6/19 9:06 AM, Udo Grabowski (IMK) wrote:

After the addons certificate desaster, a followup hotfix build of the
fixed ESR 60.x should be released in the repo. It's yet to be awaited,
they just pushed the 66.0.4 regular version.


Mozilla has released ESR 60.6.2 upstream:
https://www.mozilla.org/en-US/firefox/60.6.2/releasenotes/

but:
https://bugzilla.mozilla.org/show_bug.cgi?id=1549310

--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] installing pthreads for compiling

[Alan Coopersmith]

On 3/26/19 10:50 AM, Lonnie Cumberland wrote:

Hello Andreas.

Thanks for your response.

Unfortunately, although I just installed the "system/header" and
"build-essential" packages, when I tried a clean "cmake" on the code, it > still says 
that it cannot find "pthread.h" for some reason.


Check the output of "pkg facet" to make sure you have not set the "devel"
facet to False, as that will prevent installing headers and other files
needed to build software.

--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] IPS idiom for local packages with no dependencies

[Alan Coopersmith]

On 02/11/19 04:19 PM, Tim Mooney wrote:

However, most packages that I would have guessed would be "leaves" are
actually required by userland-incorporation or some other incorporation,
so they are effectively "required". 


depend type=incorporate does not mark a package required, it just sets a
constraint on what version can be installed.   When you're looking at what
packages are actually required, you need to look carefully at the type
of the depend action, and see what each type actually does in the list
in the pkg(5) man page.

-alan-


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

Re: [OpenIndiana-discuss] MATE 1.20 and updated GTK+3 for hipster

[Alan Coopersmith]

On 10/23/18 06:44 AM, Predrag Zečević - Technical Support Analyst wrote:

$ for dir in /var/cache/fontconfig
/export/home/predrag_zecevic/.cache/fontconfig /etc/X11/fontpath.d; do
printf "%50s:" $dir; find ${dir} -type f | wc -l; done
  /var/cache/fontconfig:408
 /export/home/predrag_zecevic/.cache/fontconfig:199
/etc/X11/fontpath.d:0


[Latest one contains just links to some fonts, presumably created by
fc-cache service].


/etc/X11/fontpath.d links are created by the packages that install fonts
to put the fonts into the X server font path, for legacy applications
that use the old X11 font system instead of fontconfig.

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] SOLVED: MATE 1.20 and updated GTK+3 for hipster

[Alan Coopersmith]

On 10/23/18 07:38 AM, Predrag Zečević - Technical Support Analyst wrote:

What I wanted to say is, if desktop relies heavily of ownership (???) of
directory /var/cache/fontconfig, maybe that package has to check it (pkg
verify?)


IPS packages are just data, they can't run commands like pkg verify - unlike
other package systems, there is no scripting.

The closest that could happen would be adding it to the fc-cache service -
packages that deliver fonts trigger a refresh of this service to update the
caches.

--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] MATE 1.20 and updated GTK+3 for hipster

[Alan Coopersmith]

On 10/18/18 05:55 AM, Udo Grabowski (IMK) wrote:

This is strange, why in the world should the settings-daemon
read the fontpathes in an infinite loop ? Looks like its constantly
thinking the mate font configuration has changed.


I don't know about infinite loop, but you'll see libfontconfig iterating
through all the fonts in all the directories when it thinks its font
caches are out of date.   On Solarish systems, we have an SMF service
svc:/application/font/fc-cache to ensure the caches are up-to-date at
system boot and when IPS packages with fonts are installed, so it would
be good to check that's running and not reporting any errors in the SMF
logs for it.

--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] Σχετ: Re: mounting an existing system on a b

[Alan Coopersmith]

On 09/10/18 08:45 AM, Apostolos Syropoulos via openindiana-discuss wrote:

It is openindiana. This is not Oracle Solaris.


Sorry, thought I was responding to the solarisx86@yahoo list.  Must drink
more caffiene before answering mail on Monday morning...

-alan-


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

Re: [OpenIndiana-discuss] mounting an existing system on a boot image

[Alan Coopersmith]

On 09/10/18 02:55 AM, Marc Lobelle wrote:

Thanks Udo and Jean Pierre: a small detail:I must be root to do this: where can 
I find the root pwd of the live image ?


On the live cd, root's password should be "solaris".

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] gmake REQUIRED_PACKAGES and depends path

[Alan Coopersmith]

On 05/25/18 05:23 AM, Jason Martin wrote:
> What do I need to do in my build so that depend path includes
> 
> usr/lib/svn/amd64 and usr/apr/lib/amd64
> 
> 
> /export/home/agrellum/oi-userland/components/desktop/gnome3/anjuta/build/manifest-i386-anjuta.depend
> has unresolved dependency '
>     depend type=require fmri=__TBD pkg.debug.depend.file=libsvn_client-1.so.0 
> \
> pkg.debug.depend.reason=usr/lib/amd64/anjuta/libanjuta-subversion.so \
>     pkg.debug.depend.type=elf \
>     pkg.debug.depend.path=lib/64 \
>     pkg.debug.depend.path=usr/gcc/6/lib/amd64 \
>     pkg.debug.depend.path=usr/lib/64'.

You need to ensure that -R /usr/lib/svn/amd64 -R /usr/apr/lib/amd64 are passed
to the linker when building those components.

Some examples that may or may not work depending on the build tool in use are:

https://github.com/OpenIndiana/oi-userland/blob/1522ea203f807319de8eb760adc0580cff3d7f7c/components/sysutils/fsvs/Makefile#L44
https://github.com/OpenIndiana/oi-userland/blob/f66857d190658752d5992bea2ea2680756e42184/components/developer/subversion/Makefile#L117-L125
https://github.com/OpenIndiana/oi-userland/blob/8370eb10ecdd7fa558b996353eab56822ca17201/components/sysutils/rsyslog/Makefile#L43-L45

-alan-

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

Re: [OpenIndiana-discuss] mkvmerge fails

[Alan Coopersmith]

On 05/23/18 08:28 AM, Apostolos Syropoulos via openindiana-discuss wrote:
> I have no idea what this KTPI thing does but it certainly has
> made my life more difficult. How can I deactivate it?

KPTI protects you from Meltdown attacks, which could be run as Javascript
in your web browser if you visit a site that embeds ads from an ad network
that doesn't have a thorough security review process for all Javascript
that they serve (i.e. basically any ad network out there, because that sort
of security costs lots of money and provides them no benefit).

https://en.wikipedia.org/wiki/Kernel_page-table_isolation and
https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability)
have more in-depth explanations.

https://omniosce.org/info/kpti documents how to disable for OmniOS - I'd
guess OpenIndiana is very similar.

-alan-

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

Re: [OpenIndiana-discuss] Does anyone else have Emacs issue?

[Alan Coopersmith]

On 04/24/18 09:35 PM, srvr_mnk wrote:
> Greetings all,
> 
> When ever I use emacs and paste a line of text or code into my buffer, I get
> 'Mark set' at the bottom of it and am locked from the session.
> 
> I went on the emacs channel to find a way to break out of the lock, but there 
> is
> nothing.
> 
> The emacs sessions then greys-out and then have to 'pkill' the emacs session.
> 
> Other text editors like Pluma work okay though. Anyone else has issues in 
> Emacs
> in OI?

I've had a similar problem in emacs on Solaris for a while if I just right-click
in the emacs window to paste, instead of clicking on the window to give it focus
first.  I've mostly trained myself to avoid it, but still screw up every now and
then and end up cursing it.

-- 
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] Building Filezilla 3.17 and later

[Alan Coopersmith]

On 03/ 4/18 11:11 AM, russell wrote:
> Both Gnutls v3.5.18 and v3.6.2 both can almost be successfuly built using
> 
> $ CC=gcc-6  CXX=g++-6 CFLAGS="-I/usr/include/idn -I/usr/include/idn2"
> LDFLAGS="-L/opt/gnu/lib -L/usr/lib" NETTLE_CFLAGS="-I/opt/gnu/include/nettle"
> HOGWEED_CFLAGS="-I/opt/gnu/include/nettle" NETTLE_LIBS=-L/opt/gnu/lib
> HOGWEED_LIBS=-L/opt/gnu/lib ./configure --prefix=/opt/gnu
> --enable-openssl-compatibility --disable-ssl2-support --enable-tests
>

When you're using *_LIBS to override the pkg-config provided flags you need
to include the -l flags that pkg-config would give you, not just the -L ones,
so for instance, the above should probably be:
   NETTLE_LIBS="-L/opt/gnu/lib -R/opt/gnu/lib -lnettle"
(including the -R to find the library at runtime outside the normal library
 path).

Or if the nettle.pc file is installed under /opt/gnu/lib/pkgconfig, then you
may just be able to replace much of the above with:
   PKG_CONFIG_PATH=/opt/gnu/lib/pkgconfig

-alan-

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

Re: [OpenIndiana-discuss] Firefox 32bit future

[Alan Coopersmith]

On 01/25/18 10:40 AM, russell wrote:
> Is there any immediate danger of Mozilla retiring the 32bit version of 
> Firefox?

I believe the most immediate item of concern is that Firefox now uses code
written in Rust, so you'll be limited to platforms that the Rust compiler
generates code for, and I don't know if anyone is bothering to do 32-bit code
generation for Solaris/illumos in Rust.

Of course, with the elimination of Netscape plugin support, there's little
reason to still use a 32-bit version of Firefox.

-alan-

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

Re: [OpenIndiana-discuss] Intel hardware

[Alan Coopersmith]

On 01/ 4/18 01:32 PM, Tim Mooney wrote:
> Intel's "Newsroom" response page is pretty terrible, in that regard.
> 
> 
> https://newsroom.intel.com/news/intel-responds-to-security-research-findings/

Intel posted statements with a little more detail after the embargo broke:

https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088=en-fr

https://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html

-alan-

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

Re: [OpenIndiana-discuss] OpenIndiana or OpenSolaris version with PowerPC support?

[Alan Coopersmith]

On 12/ 3/17 12:36 PM, ardi wrote:

By reading the Wikipedia page about Solaris
(https://en.wikipedia.org/wiki/Solaris_(operating_system) ), I somehow
get the conclusion that PowerPC was added into OpenSolaris at some
point, and not only through Polaris, but merging it into OpenSolaris
actually. However, the paragraph explaining it seems a bit unclear, so
maybe I'm not reading it correctly.


It was never merged into the main OpenSolaris repositories, it was only
ever available as a separate project.  (The wording on Wikipedia is a
bit confusing there - perhaps it should say "which re-integrated the
relevant parts from Solaris 2.5.1 into their OpenSolaris project" and
add a note that it was abandoned before completion.)

-alan-

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

Re: [OpenIndiana-discuss] system-config-printer-applet not found

[Alan Coopersmith]

On 11/12/17 12:10 PM, Gary Mills wrote:

When I upgraded hipster yesterday, I got this errors in the message
log:

 Nov 11 14:55:01 ryzen mate-session[2839]: [ID 702911 daemon.warning] WARNING: Could 
not launch application 'print-applet.desktop': Unable to start application: Failed to 
execute child process 
"/usr/lib/system-config-printer/system-config-printer-applet" (No such file or 
directory)

The file in question is here:

 /usr/share/system-config-printer/system-config-printer-applet


Check to see if it's a script with a #! line pointing to an invalid interpreter
(like an old version of python or perl that's no longer installed) - the "No
such file or directory" can refer to either the program or its interpreter.

-alan-

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

Re: [OpenIndiana-discuss] OI 2017/10 lightdm under VBox 5.1.28

[Alan Coopersmith]

On 11/ 2/17 10:51 AM, Tim Mooney wrote:

In regard to: Re: [OpenIndiana-discuss] OI 2017/10 lightdm under VBox...:

Or if you don't have an /etc/X11/xorg.conf yet:
 cp /usr/lib/X11/xorg.conf.vesa /etc/X11/xorg.conf


The OI guest that I updated from 2017.04 to 2017.10 does not have any
example files in /usr/lib/X11.  Perhaps I neglected to install some
package?


Sorry, I didn't realize hipster has it in a different place than Solaris does
& OpenSolaris did - it appears to be in /jack/xorg.conf.vesa on the install
media, but I don't see it in a package for a normal installation.

Adding to the confusion, OI carries our man page patch documenting this file:
https://github.com/OpenIndiana/oi-userland/blob/c95cbd986fe0d263b84fa8385b39d380246f894b/components/x11/xorg-server/patches/04-sun-manpage.patch#L176

You can grab the file itself from:
https://raw.githubusercontent.com/oracle/solaris-xorg/master/open-src/driver/xf86-video-vesa/xorg.conf.vesa

(Really the last 4 lines is all you need.)

-alan-

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

Re: [OpenIndiana-discuss] OI 2017/10 lightdm under VBox 5.1.28

[Alan Coopersmith]

On 11/ 2/17 09:10 AM, John D Groenveld wrote:

In message <87d150elb7@local.lan>, Harry Putnam writes:

Sorry about dumbo question, but can you mention briefly how this
switching is done?


Change vboxvideo to vesa in /etc/X11/xorg.conf.


Or if you don't have an /etc/X11/xorg.conf yet:
  cp /usr/lib/X11/xorg.conf.vesa /etc/X11/xorg.conf

--
    -Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] OpenIndiana Intro questions

[Alan Coopersmith]

On 10/23/17 12:13 PM, Lonnie Cumberland wrote:

I did find that VNC has DirectVNC for working with the framebuffer (
http://drinkmilk.github.io/directvnc/) and am exploring it more now.


I would be surprised if code written for the Linux DirectFB API's worked with
the Solaris framebuffer devices, but as those are only really found on SPARC
systems, not x86, it's really not likely to help here.

-alan-

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

Re: [OpenIndiana-discuss] /hipster: question about /proc

[Alan Coopersmith]

On 09/29/17 06:55 AM, Predrag Zečević - Technical Support Analyst wrote:

Hi all,

I got today alert (actually blinking TimeSlider icon) that root FS is more than 
70% in use (that is my setup).


Went to check what occupies so much space, and found:
$ pfexec du -sch /*
...
76G /proc


/proc is a virtual file system of its own and doesn't use space in your ZFS
pool, so you'll need to look somewhere else to find out what's filling your
root FS.

-alan-


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

Re: [OpenIndiana-discuss] So is Solaris officially supported till 2034?

[Alan Coopersmith]

On 09/ 4/17 02:11 PM, Nikola M wrote:

On 09/ 4/17 08:18 PM, Apostolos Syropoulos wrote:
I would expect exactly that, to be able to run it on compatible but newer 
hardware, and at least on Oracle hardware,

but yes, you are right - over time new hardware requires new support, drivers 
etc.

There helps the thing, that same (even binary) drivers work for decades because 
Solaris driver model was established long time ago and doesn't need to change 
much. Even today most of drivers are shared between illumos and Oracle Solaris.


While the core Device Driver Interfaces (DDI) don't need to change much, many of
the higher level frameworks, such as the storage & network interfaces, do as the
hardware evolves - interfaces designed for spinning SCSI disks aren't quite the
same as using gobs of NVRAM as storage.   While I'm not surprised you can share
drivers written for Solaris 11.0, I'd be more surprised if drivers written for
the latest hardware & Solaris releases just work out of the box with no effort
on OI/illumos forevermore.

-alan-

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

Re: [OpenIndiana-discuss] /hipster: MATE + NVIDIA + 2 monitors :: full screen problem

[Alan Coopersmith]

On 09/ 5/17 12:59 AM, Predrag Zečević - Technical Support Analyst wrote:

Hi all,

I have strange problem on my /hipster installation (since I have moved
to Mate from Gnome).

There were no changes on hardware in mean time:

pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x10de device 0x0605
  NVIDIA Corporation G92 [GeForce 9800 GT]

In Gnome, I was able to use Xinerama and to have separate workspaces on 2 
screens.. E.G. If I wanted to watch video on full screen, only that monitor was 
used.


Are you sure Xinerama was turned on then?  Xinerama combines screens into a
single logical screen, so what you want sounds like the opposite of Xinerama.

Have you tried turning Xinerama off?

-alan-

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

Re: [OpenIndiana-discuss] So is Solaris officially dead?

[Alan Coopersmith]

No.

--
-Alan Coopersmith-   alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/alanc

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

Re: [OpenIndiana-discuss] How to tell for sure what bit your OS is?

[Alan Coopersmith]

On 05/31/17 10:30 AM, Richard L. Hamilton wrote:



On May 31, 2017, at 13:01, Alan Coopersmith <alan.coopersm...@oracle.com> wrote:

On 05/31/17 09:43 AM, Richard L. Hamilton wrote:

The alternative would be a large times analog of large file support; why that 
wasn't done when 64-bit began, I don't understand. :-)


It was considered at Sun in the late 90's but discarded as going full LP64
already provided a solution without combinatorial explosion of test matrices
for large files x large times.  The large files API was created before LP64
was an option on most Unixes, including Solaris.



Testing, yes; that makes sense.

How are the time conversion functions doing with regard to time_t past 
INT32_MAX?  I see that (with a 64-bit executable) at least ctime() seems to 
work enough beyond for usual life and commercial purposes (aside from 
radioactive waste :-) ):

13:15:32[13]monster:/home/rlhamil> ./maxtime
time overflow after Tue Jan 19 03:14:07 2038
 in 32-bit signed two's complement
timestamp 9223372036854775807 (INT64_MAX) cannot be processed by ctime()
t=2147483647: Tue Jan 19 03:14:07 2038

t=4294967294: Sun Feb  7 06:28:14 2106

t=8589934588: Wed Mar 16 12:56:28 2242

t=17179869176: Wed May 30 01:52:56 2514

t=34359738352: Tue Oct 26 03:45:52 3058

t=68719476704: Sun Aug 20 07:31:44 4147

t=137438953408: Wed Apr  8 15:03:28 6325

t=274877906816: (null)


On Solaris, ctime() is defined as returning a string of exactly 26 characters,
so it gives up when the year requires a 5th digit and doesn't fit.

Converting to strftime and compiling with -std=c99 -m64 -D_XOPEN_SOURCE=700
gets a bit further here:

for (t=INT32_MAX;t<=INT64_MAX && t>=0L;t<<=1) {
char s[100] = "";
struct tm *l = localtime();
if (l != NULL)
strftime(s, sizeof(s), "%a %b %e %H:%M:%S %Y", l);
else
snprintf(s, sizeof(s), "localtime(%ld) == NULL", t);
printf("t=%ld: %s\n", t, s);
}

time overflow after Tue Jan 19 03:14:07 2038
 in 32-bit signed two's complement
timestamp 9223372036854775807 (INT64_MAX) cannot be processed by ctime()
t=2147483647: Tue Jan 19 03:14:07 2038
t=4294967294: Sun Feb  7 06:28:14 2106
t=8589934588: Wed Mar 16 12:56:28 2242
t=17179869176: Wed May 30 01:52:56 2514
t=34359738352: Tue Oct 26 03:45:52 3058
t=68719476704: Sun Aug 20 07:31:44 4147
t=137438953408: Wed Apr  8 15:03:28 6325
t=274877906816: Wed Jul 14 06:06:56 10680
t=549755813632: Tue Jan 25 12:13:52 19391
t=1099511627264: Mon Feb 20 00:27:44 36812
t=2199023254528: Fri Apr 10 00:55:28 71654
t=4398046509056: Sat Jul 19 01:50:56 141338
t=8796093018112: Mon Feb  4 03:41:52 280707
t=17592186036224: Fri Mar  8 07:23:44 559444
t=35184372072448: Sat May 14 14:47:28 1116918
t=70368744144896: Tue Sep 25 05:34:56 2231866
t=140737488289792: Sun Jun 19 11:09:52 4461763
t=281474976579584: Wed Dec  5 22:19:44 8921556
t=562949953159168: Wed Nov 10 20:39:28 17841143
t=1125899906318336: Wed Sep 19 17:18:56 35680317
t=2251799812636672: Wed Jun  7 10:37:52 71358665
t=4503599625273344: Tue Nov 11 21:15:44 142715360
t=9007199250546688: Mon Sep 24 18:31:28 285428751
t=18014398501093376: Sat Jun 17 13:02:56 570855533
t=36028797002186752: Tue Dec  1 02:05:52 1141709096
t=72057594004373504: localtime(72057594004373504) == NULL
t=144115188008747008: localtime(144115188008747008) == NULL
t=288230376017494016: localtime(288230376017494016) == NULL
t=576460752034988032: localtime(576460752034988032) == NULL
t=1152921504069976064: localtime(1152921504069976064) == NULL
t=2305843008139952128: localtime(2305843008139952128) == NULL
t=4611686016279904256: localtime(4611686016279904256) == NULL
t=9223372032559808512: localtime(9223372032559808512) == NULL

I suggest anyone working with such precise timestamps more than a billion years
in the future use a system more oriented towards such scientific calculations
than the C standard library.  I'm sure it's timezone code does not account for
the changes in the Earth's rotation nor the tectonic plate migration that will
have occurred over that timespan.

-alan-

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

Re: [OpenIndiana-discuss] How to tell for sure what bit your OS is?

[Alan Coopersmith]

On 05/31/17 09:43 AM, Richard L. Hamilton wrote:

The alternative would be a large times analog of large file support; why that 
wasn't done when 64-bit began, I don't understand. :-)


It was considered at Sun in the late 90's but discarded as going full LP64
already provided a solution without combinatorial explosion of test matrices
for large files x large times.  The large files API was created before LP64
was an option on most Unixes, including Solaris.

-alan-

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

Re: [OpenIndiana-discuss] How to tell for sure what bit your OS is?

[Alan Coopersmith]

On 05/31/17 09:19 AM, Richard L. Hamilton wrote:

Aside from executables that reference timestamps (given that a signed 
twos-complement will overflow after Tue Jan 19 03:14:07 2038 GMT), and for 
programs that will never need to manipulate files larger than 2GiB-1 (unless  
they use large file support), is it necessarily desirable to upgrade user-space 
binaries at all?  On x86, ok you get more registers and such; but on SPARC, 
I've heard you may be better off with V8 (or V8+), given smaller binaries, 
better use of cache, etc.


Remember that any program that calls stat() on a file references timestamps
and can get stat() failures with an out-of range timestamp.

Also as noted in the blogs various newer features either work better with 64-bit
pointers (like ASLR) or can only work with 64-bit pointers (like ADI on SPARC).


Ok, thinking about it, now that static libc is gone, with the time issues, a 
32-bit libc would be an invitation to forget that it wouldn't work with 
something that used timestamps, not to mention whatever complications follow 
from maintaining support for 32-bit executables.


All very true too - at some point there's going to be little benefit in
maintaining a second copy of every single shared library for all those
32-bit programs, plus all the translation layers in the kernel for 32-bit
syscalls.   That point is probably years in the future, but certainly
less than 20 years from now.

-alan-

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

Re: [OpenIndiana-discuss] How to tell for sure what bit your OS is?

[Alan Coopersmith]

On 05/26/17 11:34 AM, Harry Putnam wrote:

Alan Coopersmith <alan.coopersm...@oracle.com> writes:


For the one I work on (not OI, but "Big Red"), we've been making
this conversion across 5+ years now, and are >90% done in our
development trunk, though much less done in what's been released so
far.  I've written far more about the topic for the terminally
curious at:


I guess it might be inappropriate here... but I'm not finding anything
with google on the terms Alan Coopersmith and Big Red.

Is this slang or an insider name for an OS ... or what?


It's a slang term referring to the color of my employer's logo/branding,
much as IBM has long been "Big Blue"...

https://www.google.com/#q=Big+Red+Oracle

-alan-

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

Re: [OpenIndiana-discuss] Solaris github repositories

[Alan Coopersmith]

On 05/26/17 05:48 AM, Harry Putnam wrote:

Predrag Zečević - Technical Support Analyst
<predrag.zece...@2e-systems.com> writes:


Sorry if you already know for this, I though it might be worth
sharing:
https://blogs.oracle.com/observatory/github-repos-with-software-for-solaris


Thanks for that link...

And thanks to Alan Coopersmith.

I wondered how one adds the `userland' mentioned at url to publishers


It's a github source repository, not an IPS pkg repository.  (Same word,
but very different usage.)

-alan-

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

Re: [OpenIndiana-discuss] How to tell for sure what bit your OS is?

[Alan Coopersmith]

On 05/26/17 04:26 AM, Harry Putnam wrote:

Jonathan Adams  writes:


Much better than the Linux "file 'which file'" (with back ticks) ...



sudo  file `which file`
/usr/bin/file:  ELF 32-bit LSB executable 80386 Version 1, dynamically
linked, not stripped, no debugging information available

Er... looks like one of the techniques has got it wrong

Or does something else explain this?


That works on Linux distros which have separate 32-bit & 64-bit versions
and compile every binary in the OS to match.

That doesn't work on Solaris-derived distros which have a unified 32/64 bit
version that supports binaries of either flavor, and which many programs are
32-bit so they can run on either 32-bit or 64-bit kernels.

As distros drop 32-bit kernel support, they'll likely convert more and more
of their programs to 64-bit, but it can be a gradual process, not a flag day.

For the one I work on (not OI, but "Big Red"), we've been making this conversion
across 5+ years now, and are >90% done in our development trunk, though much
less done in what's been released so far.  I've written far more about the
topic for the terminally curious at:

https://blogs.oracle.com/alanc/moving-oracle-solaris-to-lp64-bit-by-bit
https://blogs.oracle.com/observatory/oracle-solaris-113-progress-on-lp64-conversion

-alan-

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

Re: [OpenIndiana-discuss] How to tell for sure what bit your OS is?

[Alan Coopersmith]

On 05/25/17 02:13 PM, Will Brokenbourgh wrote:

On 05/25/17 14:10, Harry Putnam wrote:

How can quickly tell what bit my Hipster 2017.04 is?


Have you tried:

uname -a


The Solaris/openSolaris/illumos kernel doesn't change any of the values
in uname between 32 & 64-bit kernels, much to the confusion of users of
kernels which do.

-alan-


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

Re: [OpenIndiana-discuss] How to tell for sure what bit your OS is?

[Alan Coopersmith]

On 05/25/17 02:10 PM, Harry Putnam wrote:

How can quickly tell what bit my Hipster 2017.04 is?


"isainfo -kv" will tell you which kernel is running.

-alan-

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

Re: [OpenIndiana-discuss] Hijacking of Shift-F5

[Alan Coopersmith]

On 05/18/17 12:37 PM, Harry Putnam wrote:

Jean-Pierre André <jean-pierre.an...@wanadoo.fr> writes:

I have a similar problem with Shift-F5 which is hijacked
by some code I cannot locate. Apparently this does not
reach Xorg (xev does not see the KeyPress event), so I
cannot redefine it.

I thought it was hijacked by the nvidia driver, as I got
the normal behavior on a computer with Intel graphics, but
this was with vesa emulation. The Intel graphics driver
can now be used, and the hijacking now also shows up on
this computer.

So this must be an OI/illumos thing (or at least something
common to nvidia and intel drivers but not the vesa one).
How can I locate and un-hijack it ?

Note : Shift-F5 causes a screen blink. Is it taken for
a screen copy or a screen print ?


Oops - I missed the original message, but saw it quoted here - check to
see if you have a process called "dispswitch" running - it grabs
Shift-F5 to try to do display probe/switch for when you plug in an external
monitor to your laptop.

It was an OpenSolaris custom creation which I assume OI inherited, and
isn't used on other OS'es that I know of.

It's started by /etc/xdg/autostart/gnome-dispswitch.desktop as part of
desktop session startup.  The man page lists the args to change which
key it steals.

--
-Alan Coopersmith-  alan.coopersm...@oracle.com
 Oracle Solaris Engineering - http://blogs.oracle.com/alanc

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

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

Re: [OpenIndiana-discuss] nonblocking i/o problem

[Alan Coopersmith]

On 04/ 9/17 02:08 AM, Peter Tribble wrote:

As an aside, there are limitations. The conditions were always pretty
strict,
so that compatibility only applies to (a) Solaris itself, and (b) only those
interfaces explictly marked as being compatible.


Specifically those whose man pages have an attributes section listing them
as "Committed" or "Uncommitted" - anything that's "External", "Volatile",
"Private" or undocumented may break even between Solaris releases, as well
as between Solaris and illumos.


In particular, link with the system openssl and you're in trouble.


Especially as the original S10 openssl was 0.9.8 which is no longer supported
or receiving security fixes, which is why Oracle's patching everything in S10
to use the not-completely-compatible 1.0.1 instead.


What I've found in general is that older (pre-S10)
applications tend to be fine, S10-native applications can be problematic.


Drivers that stick to the documented DDI interfaces should also be good, but
other kernel modules, such as filesystems, that rely on undocumented or private
kernel interfaces may really break your system.

-alan-

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

Re: [OpenIndiana-discuss] glxgears

[Alan Coopersmith]

On 03/ 7/17 06:10 AM, Apostolos Syropoulos via openindiana-discuss wrote:

apostolo@adalind>> ls -l /usr/X11/include/NVIDIA/GL/gl.h
/usr/X11/include/NVIDIA/GL/gl.h: No such file or directory
This can be solved by downloading the Linux NVIDIA driver which includes this 
file
and glext.h, glx.h, and glxext.h


New versions of the Nvidia driver are relying on the platform to provide
these files defined by the Khronos standards instead of delivering their
own copies - that means we're going to have to adjust the ogl-select setup
to point to the copies from the Mesa packages for these new drivers.
(Unfortunately, while I know this is happening, I don't have a working
 solution to point to just yet.)

-alan-


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

Re: [OpenIndiana-discuss] Newly installed VirtualBox gives COM object error when launched

[Alan Coopersmith]

On 03/ 6/17 08:13 AM, Aurélien Larcher wrote:

So I guess there is still something weird with the GL libraries :)

There will always be something weird with the GL libraries due to historical
mistakes and lack of cross-vendor cooperation which led to requiring a
completely different libGL for different hardware.

Eventually the libglvnd proposal should help here, but it's not widespread yet.

-alan-

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

Re: [OpenIndiana-discuss] The end is near

[Alan Coopersmith]

On 01/25/17 11:15 AM, Tim Mooney wrote:

In regard to: Re: [OpenIndiana-discuss] The end is near, Udo Grabowski said...:


You need reliable sources:
<http://www.theregister.co.uk/2017/01/23/oracle_layoffs_in_hardware_div/>


I haven't seen any posts to the list from Alan Coopersmith since this
thread started; here's hoping Alan escaped this unscathed.


Then you must have deleted all the e-mails I sent:
https://openindiana.org/pipermail/openindiana-discuss/2017-January/020100.html
https://openindiana.org/pipermail/openindiana-discuss/2017-January/020102.html
https://openindiana.org/pipermail/openindiana-discuss/2017-January/020110.html
https://openindiana.org/pipermail/openindiana-discuss/2017-January/020113.html
https://openindiana.org/pipermail/openindiana-discuss/2017-January/020131.html

As long as we're cluttering the OI list with off-topic noise, some further
reading material on what we're doing with Solaris:
https://blogs.oracle.com/solaris/entry/oracle_solaris_moving_to_a
https://www.linkedin.com/pulse/approachable-innovation-bill-nesheim

https://twitter.com/ORCL_Solaris & https://twitter.com/opensolaris have both
been sharing various links as well (though obviously with different biases).
https://twitter.com/alanc on the other hand is completely off-topic.  8-)

-alan-

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

Re: [OpenIndiana-discuss] The end is near

[Alan Coopersmith]

On 01/19/17 12:38 AM, Fred Liu wrote:

From that roadmap, my understanding is there is no on-premise and standalone 
Solaris and SPARC releases after 2017 and everything goes into cloud.


Then you're misunderstanding the roadmap, which shows both on-premise & cloud
releases going forward until at least 2021.


So data-machine and fishwork-storage are some kinds of variations from Solaris 
and SPARC, if users want to touch by hand.


ZFS Storage Appliances ("fishworks") use x86 CPUs and their own OS versions,
with their own release schedules.   You can't make any assumptions about
them based on the roadmap for CPU's they don't use or OS versions they don't
use.

-alan-

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