Re: [OpenIndiana-discuss] Sun Management Centre

[Udo Grabowski (IMK)]

On 21/05/2024 09:28, Rainer Heilke wrote:

Just a quick update:
I'll still try to see if I can find any OpenIndiana.org references to 
smc (not having found them yet, I suspect they were third party pages), 
but I don't think I'll get to play with RBAC. It seems my test system 
likes to lose any USB drives on reboot, and when/if I get them back, all 
data is gone. zpool is even telling me that one zpool has a property 
that has never existed on this box:

This pool uses the following feature(s) not supported by this system:
     com.klarasystems:vdev_zaps_v2
cannot import 'Work': unsupported version or feature


That cannot be handled on OI, see:



It's even losing the internal SSD.
I'm loath to play around with RBAC, or anything else, on my OmniOS 
backup server. And I doubt I can get any OpenSolaris flavour running on 
a Raspberry Pi. :/   I even got a pair of 4TB drives for this (they were 
surprisingly inexpensive).
To quote Gary Olman's character in 5th Element, "I'm getting very 
disappointed!"

Rainer
I wonder if there's something in the BIOS...


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


Date 2024-05-14 11:13:24 AM
Subject Re: [OpenIndiana-discuss] Sun Management Centre





-- Original Message --
From "Rolf M. Dietze" 
To "Discussion list for OpenIndiana" 


Date 2024-05-14 12:43:55 AM
Subject Re: [OpenIndiana-discuss] Sun Management Centre



Quoting Rainer Heilke :


On 5/13/24 22:50, Toomas Soome via openindiana-discuss wrote:


On 14. May 2024, at 08:12, Rainer Heilke 
 wrote:


Hi.
I keep running into documentation that tells me to do a task by  
firing up the Sun Management Centre, but OI doesn't seem to have  
it, nor can I find any way of getting/installing it. Is it  
available for OpenIndiana? Is it maybe in a different repository?
The documentation needs to either explain how to get it, or any  
reference to it needs to be purged, IMNSH opinion. If the former,  
I may be able to help a bit, as energy levels allow.

??
Rainer
I’m afraid, it is long dead. So yes, if you see the references,  
please do file the issue (and patches are also very welcome!).


thanks,
toomas


I'll look into how to file issues, and make a note of the pages 
I've  already found.


Unfortunately, that means a number of documents need to be fleshed  
out with the proper chain of commands to perform the functions, and  
I don't know how much I can help. Aside from limited energy, I 
never  had to deal with RBAC, etc. This is new-ish territory for me, 
having  always used sudo when I was working. (I want to learn the 
"proper"  RBAC way of doing things, even if only for kicks and 
giggles, which  is why I was looking into this in the first place.)


Rainer

Hi Rainer,

I use RBAC quite often, on Solaris as well as on OpenIndiana since I
am running Sunray desktops for class on Solaris in kiosk mode to have
the students connect to OpenIndiana machines for their tasks to do.
The students have to do admin stuff on the target systems but are all
homed on one OpenIndiana machine to start from. So RBAC and resource
management are needed. If you reference to the old Solaris 10 
documentation,

both run smoothly. I do not use any GUI but xterm for that as for most
tasks on theses boxes. Have a look in the old documentation. Resource
management works quite the same as on solaris 11, also have a look there

By the way, I do have an issue with resource management on OpenIndiana,
that is, if a student runs against certain limitations mostly in number
of lwps, the resource management terminates the X server. That it does
for all sessions. Haven't had the time to dig into this and I am not
sure if it is of any interest since my setup is not so commonly used.

The Sun Management Center was a long and not so enthusiastic story as
since Solaris never had consistent admin GUIs as example smit on AIX 
oder

sam on HP-UX

Rolf


Thanks, to everyone.
I'll try to file issues in the next few days -- I have other 
(non-computer) issues to deal with today.
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.
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? ;-)

Rainer






___
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] Xorg crashes on reboot

[Udo Grabowski (IMK)]

Since a while I see core files from Xorg, which are seemingly generated
on 'init 6' while going down:

> ::status
debugging core file of Xorg (64-bit) from imksunts
initial argv: /usr/bin/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -

threading model: native threads
status: process terminated by SIGABRT (Abort), pid=1215 uid=0 code=-1
> $C
7fffb100 libc.so.1`_lwp_kill+0xa()
7fffb130 libc.so.1`raise+0x22(6)
7fffb180 libc.so.1`abort+0x58()
7fffb190 System()
7fffb1c0 ddxGiveUp+0xa5()
7fffb1f0 AbortDDX+0x126()
7fffb200 AbortServer+0x22()
7fffb300 FatalError+0x143()
7fffb350 OsSigHandler+0x10c()
7fffb360 libc.so.1`__sighndlr+6()
7fffb400 libc.so.1`call_user_handler+0x1d1(b, 7fffb7e0, 
7fffb480)
7fffb460 libc.so.1`sigacthandler+0xee(b, 7fffb7e0, 7fffb480)
7fffb960 PointerWin+0xc()
7fffb9a0 CoreFocusInNotifyPointerEvents+0x34()
7fffb9e0 CoreFocusToAncestor+0x107()
7fffba10 CoreFocusEvents+0x11e()
7fffba40 DoFocusEvents+0x48()
7fffba80 DeleteDeviceFromAnyExtEvents+0x1a0()
7fffbac0 DeleteWindowFromAnyExtEvents+0x6a()
7fffbb20 DeleteWindowFromAnyEvents+0x3ef()
7fffbb70 UnrealizeTree+0xf1()
7fffbbb0 UnmapWindow+0x186()
7fffbc00 DeleteWindow+0x28()
7fffbc20 doFreeResource+0x61()
7fffbc80 FreeResource+0x17b()
7fffbcf0 dixSaveScreens+0x1c8()
7fffbd60 dix_main+0x6a8()
7fffbd90 main+0x28()
7fffbdc0 _start_crt+0x87()
7fffbdd0 _start+0x18()

--
Dr.Udo Grabowski  Inst.of Meteorology & Climate Research IMK-ASF-SAT
https://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology  https://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] Firefox 123.0.1 has changed UA (User-Agent) value?

[Udo Grabowski (IMK)]

On 21/03/2024 16:11, Predrag Zečević via openindiana-discuss wrote:

For example, previous version UA was:

"Mozilla/5.0 (X11; SunOS i86pc; rv:122.0) Gecko/20100101 Firefox/122.0"

Now is:

"Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0"

Why? How?

Just spend 30 minutes searching log files for *SunOS* (no one else uses it, so
it is nice :-))


P.S: I have removed UA switcher before writing this, and bounced FF



I also see this, and it has a nice side effect: You can now join
Zoom meetings via the browser (since there's no zoom client for SunOS)
without being rejected by Zoom per default at the entrance page ...
--
Dr.Udo Grabowski  Inst.of Meteorology & Climate Research IMK-ASF-SAT
https://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology  https://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,

[Udo Grabowski (IMK)]

On 12/02/2024 17:32, Stephan Althaus wrote:

...
That is the nvidia audio device, i can select it in vlc and hear nothing, my
monitor speakers should do it - i have no clue at the moment..

i tried USB-C and HDMI connection the the monitor just right now with no luck..

# cat /dev/random > /dev/dsp1

gives no sound output..



mate-volume-control may helps.


--
Dr.Udo Grabowski  Inst.of Meteorology & Climate Research IMK-ASF-SAT
https://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology  https://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,

[Udo Grabowski (IMK)]

On 10/02/2024 09:16, Carsten Grzemba via openindiana-discuss wrote:

For do some preliminary  testing   on update Pulseaudio I am interested in a 
small contribution.

If anyone has more then one audio device, I am interested in the output of:

$ ls -l /dev/audio*

$ ls -l /dev/sound*


$ ls -l /dev/dsp*

Many thanks!



Dell Precision 3500 + NVIDIA Quadro 2000:


ro sunts ~ # prtconf -v | grep -i aud
name='audiohd_beep' type=int items=1
value='High Definition Audio 1.0'
value='GF106 High Definition Audio Controller'
dev_link=/dev/sound/audiohd:1mixer
dev_link=/dev/sound/audiohd:1dsp

dev_path=/pci@0,0/pci8086,340a@3/pci10de,84a@0,1:sound,audio1
dev_link=/dev/sound/audiohd:1

dev_path=/pci@0,0/pci8086,340a@3/pci10de,84a@0,1:sound,audioctl1
dev_link=/dev/sound/audiohd:1ctl
name='audiohd_beep' type=int items=1
value='High Definition Audio 1.0'
value='82801JI (ICH10 Family) HD Audio Controller'
dev_link=/dev/sound/audiohd:0mixer
dev_link=/dev/sound/audiohd:0dsp
dev_path=/pci@0,0/pci1028,293@1b:sound,audio0
dev_link=/dev/sound/audiohd:0
dev_path=/pci@0,0/pci1028,293@1b:sound,audioctl0
dev_link=/dev/sound/audiohd:0ctl

ro sunts ~ # pkg info pulseaudio
 Name: library/audio/pulseaudio
  Summary: Sample Rate Converter for audio
 Category: System/Multimedia Libraries
State: Installed
Publisher: openindiana.org
  Version: 13.0
   Branch: 2024.0.0.5
   Packaging Date: 13 January 2024 at 19:35:31
Last Install Time: 31 October 2021 at 19:39:21
 Last Update Time: 15 January 2024 at 09:13:37
 Size: 8.40 MB
 FMRI: 
pkg://openindiana.org/library/audio/pulseaudio@13.0-2024.0.0.5:20240113T193531Z

  Project URL: https://www.freedesktop.org/wiki/Software/PulseAudio/
   Source URL: 
https://freedesktop.org/software/pulseaudio/releases/pulseaudio-13.0.tar.xz



ro sunts ~ # ls -l /dev/*audio* ; ls -l /dev/sound* ; ls -l /dev/*dsp*
lrwxrwxrwx   1 root root   7 Sep 22  2022 /dev/audio -> sound/0
lrwxrwxrwx   1 root root  10 Sep 22  2022 /dev/audioctl -> 
sound/0ctl
total 12
lrwxrwxrwx   1 root root   9 Sep 22  2022 0 -> audiohd:0
lrwxrwxrwx   1 root root  12 Sep 22  2022 0ctl -> audiohd:0ctl
lrwxrwxrwx   1 root root   9 Sep 22  2022 1 -> audiohd:1
lrwxrwxrwx   1 root root  12 Sep 22  2022 1ctl -> audiohd:1ctl
lrwxrwxrwx   1 root root  49 Sep 22  2022 audiohd:0 -> 
../../devices/pci@0,0/pci1028,293@1b:sound,audio0
lrwxrwxrwx   1 root root  52 Sep 22  2022 audiohd:0ctl -> 
../../devices/pci@0,0/pci1028,293@1b:sound,audioctl0
lrwxrwxrwx   1 root root  47 Sep 22  2022 audiohd:0dsp -> 
../../devices/pci@0,0/pci1028,293@1b:sound,dsp0
lrwxrwxrwx   1 root root  49 Sep 22  2022 audiohd:0mixer -> 
../../devices/pci@0,0/pci1028,293@1b:sound,mixer0
lrwxrwxrwx   1 root root  65 Sep 22  2022 audiohd:1 -> 
../../devices/pci@0,0/pci8086,340a@3/pci10de,84a@0,1:sound,audio1
lrwxrwxrwx   1 root root  68 Sep 22  2022 audiohd:1ctl -> 
../../devices/pci@0,0/pci8086,340a@3/pci10de,84a@0,1:sound,audioctl1
lrwxrwxrwx   1 root root  63 Sep 22  2022 audiohd:1dsp -> 
../../devices/pci@0,0/pci8086,340a@3/pci10de,84a@0,1:sound,dsp1
lrwxrwxrwx   1 root root  65 Sep 22  2022 audiohd:1mixer -> 
../../devices/pci@0,0/pci8086,340a@3/pci10de,84a@0,1:sound,mixer1

lrwxrwxrwx   1 root root   4 Sep 22  2022 /dev/dsp -> dsp0
lrwxrwxrwx   1 root root  18 Sep 22  2022 /dev/dsp0 -> 
sound/audiohd:0dsp
lrwxrwxrwx   1 root root  18 Sep 22  2022 /dev/dsp1 -> 
sound/audiohd:1dsp


--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] running sunpro binaries

[Udo Grabowski (IMK)]

On 09/01/2024 23:50, Goetz T. Fischer wrote:

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



For Fortran, a clear YES, it's comparable to INTEL ifort performance,
which doesn't exist for illumos, but for C/C++, I don't know
(you typically don't use C/C++ for performance critical numerical
projects in science ...). But even there, it already misses
Fortran 2003/2017/2023 standards, so having gfortran fixed for
basic language conformance would be preferable.


On Tue, 9 Jan 2024 23:43:19 +0100, Udo Grabowski (IMK) wrote:

On 09/01/2024 22:37, Goetz T. Fischer wrote:

On Tue, 9 Jan 2024 11:40:53 +0100, Udo Grabowski (IMK) wrote:

For C/C++, I would absolutely prefer gcc/g++


why?


As said. the old sunpro doesn't support modern standards,
and the newer ones that do are not binary compatible anymore;
and for C++, it causes issues with lousily written packages
to not compile without nontrivial patches, while gcc just
happily let them through, see:


<https://www.oracle.com/application-development/te>chnologies/developerstudio-cplusplus-faq.html#Coding10>


The other culprit is the standards-required name-mangling
uniqueness for each compiler, which don't let you mix
C++ libraries from different brands to be called from one
program (which was dropped from later C++ standards),
which then requires you to have more than one C++ brand
of libraries at hand to link (this was one of the obstacles
to solve to get python scipy/numpy linked when using the Sun
F90 compiler for the LAPACK/BLAS libraries, which took a lot
of tinkering with the python toolchain on an old oi151a9).

So if you don't have specific requirements forced on you
by already existing libraries using the sunpro stuff,
I would recommend to always go with the gcc/g++ tools.

Didn't use clang/llvm, so can't say much about 
that.___
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] Heads-Up: Obsoletion of 39 old packages

[Udo Grabowski (IMK)]

On 09/01/2024 23:35, Matthew R. Trower wrote:



On 1/9/24 16:25, Alan Coopersmith wrote:
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,


It's not fully source compatible, either --- there was a function 
signature change.  Nothing that would be terrible to adjust for IIRC, 
just tedious in large projects (or across numerous small projects).  But 
it seems like maybe we don't have much (if anything) left to worry about 
in OI, anyway.


 > just for running programs built against the Solaris libraries.

Yeah, that's the sticking point.  I wonder if there are people out there 
still running things like that.


One major software package using motif is the GUI for Sun SGE,
which we still have in production. No problem to obsolete the
runtime library, I can just copy the required libraries over
to /usr/local/lib.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] running sunpro binaries

[Udo Grabowski (IMK)]

On 09/01/2024 22:37, Goetz T. Fischer wrote:

On Tue, 9 Jan 2024 11:40:53 +0100, Udo Grabowski (IMK) wrote:

elfedit -e 'cap:hw2 -and -cmp rdseed' 


much thanks to you as well. both, this or setting LD_HWCAP, work like a charm!


For C/C++, I would absolutely prefer gcc/g++


why?


As said. the old sunpro doesn't support modern standards,
and the newer ones that do are not binary compatible anymore;
and for C++, it causes issues with lousily written packages
to not compile without nontrivial patches, while gcc just
happily let them through, see:
<https://www.oracle.com/application-development/te>chnologies/developerstudio-cplusplus-faq.html#Coding10>

The other culprit is the standards-required name-mangling
uniqueness for each compiler, which don't let you mix
C++ libraries from different brands to be called from one
program (which was dropped from later C++ standards),
which then requires you to have more than one C++ brand
of libraries at hand to link (this was one of the obstacles
to solve to get python scipy/numpy linked when using the Sun
F90 compiler for the LAPACK/BLAS libraries, which took a lot
of tinkering with the python toolchain on an old oi151a9).

So if you don't have specific requirements forced on you
by already existing libraries using the sunpro stuff,
I would recommend to always go with the gcc/g++ tools.

Didn't use clang/llvm, so can't say much about that.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] running sunpro binaries

[Udo Grabowski (IMK)]

On 09/01/2024 03:40, Goetz T. Fischer wrote:

On Mon, 8 Jan 2024 18:17:17 -0800, Alan Coopersmith wrote:

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-


ah, i see, much thanks for the info!

i always liked the way sunpro binaries expose these cpu features by just using "file" or 
"ldd". that can
save a lot of time investigating why something doesn't run.



There's a way to repair binaries and libraries:

isainfo -v
elfdump -H 

will show you the capabilities of the machine and the requirements
of your binary.

With

elfedit -e 'cap:hw2 -and -cmp rdseed' 

you can delete that requirement from the binary if rdseed is not
seen on the CPU.

You can also specify a mapfile during linking to explicitly
set the hw caps:

$ cat mapfile
$mapfile_version 2
  CAPABILITY {
HW = SSE SSE2;
};


btw given its age, does it still make sense to use sunpro performance wise? 
maybe gcc and/or clang did
catch up in the meantime or maybe got even better?


We still use the sunpro compiler for Fortran 90/95, where gfortran is
still inferior in language conformity, and the Intel compiler is too
slow in compiling our project on Linux environments (...and non-existent
for illumos), and the binaries are farely compatible to the Intel ifort.
For C/C++, I would absolutely prefer gcc/g++. Also note that licensing
and binary compatibility would restrict us using anything above sunpro
12.1u1, so it's also getting outdated in terms of supported standards.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Cannot delete an ADDROBJ in ipadm?

[Udo Grabowski (IMK)]

On 30/11/2023 14:33, Philip Kime wrote:

I was trying to switch from fixed IP to DHCP and finally managed to get it to 
work but in the process, I created a dhcp addr on the interface with ipadm and 
now I can't get rid of it:

root@park:~# ipadm
ADDROBJ   TYPE STATEADDR
lo0/v4static   ok   127.0.0.1/8
rge0/_a   dhcp ok   192.168.0.50/24
lo0/v6static   ok   ::1/128
rge0/?static   ok   fe80::baae:edff:fedb:1e5c%rge0/10
rge0/?addrconf ok   
2a02:1210:14dd:3100:baae:edff:fedb:1e5c/64
rge0/addr dhcp disabled ?
root@park:~# ipadm delete-addr rge0/addr
ipadm: could not delete address: Object not found
root@park:~#

The underlined can't be removed any way I've tried. Does anyone know how to 
delete it? Network is working fine with DHCP using the /_a ADDROBJ but I want 
to clean this up.
On Hipster 2023.05
...


You can try to fix /etc/ipadm/ipadm.conf in your favourite editor.
But be careful, ipadm is very picky on the format of that file,
apparent inconsistencies and oddities are intended, don't "fix"
them ...

Then reboot.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

[OpenIndiana-discuss] dlc.openindiana.org down

[Udo Grabowski (IMK)]

 doesn't answer, but server seems
alive on pings.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] Thunderbird 115.3.1

[Udo Grabowski (IMK)]

On 13/10/2023 18:45, russell wrote:

Good Afternoon

I have noticed since upgrading to Thunderbird 115.3.1 the window decoration
which allows me to switch to different Workspaces is not available.
If I login using a different user, run xhost +local:, then su - as myself and
then run thunderbird the workspace switcher option in the upper left hand corner
of the window is available. So in order to have thunderbird appear on a
particular workspace, I have to switch to that workspace and start it there.

As anyone else notice this behaviour?



Click the right mouse button TWO times. This helps at least on
Ubuntu, but the middle click "window to background" is also not
working. Started to happen a while ago for firefox too (before
thunderbird was updated to the same new core); I filed a bug for
it, but people there "can't reproduce". 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...
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] SMB NFS not sure where to go

[Udo Grabowski (IMK)]

On 25/09/2023 11:36, Michelle wrote:

...

I'll have to look up snoop and how to use it. ...



snoop -d 

-v for detailed package content.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] zpool status rpool not consistent with diskinfo

[Udo Grabowski (IMK)]

On 20/09/2023 14:57, Stephan Althaus wrote:

On 9/20/23 13:59, Toomas Soome via openindiana-discuss wrote:

You can try 'zpool reopen’, if that will not help, remove
/etc/zfs/zpool.cache. There is some issue that information in zpool.cache is
not updated…

rgds,
toomas


On 20. Sep 2023, at 14:14, Stephan Althaus 
wrote:

Hello!

I swapped 2 of 3 root-pool drives (after power off)
to different controllers, (with power-off-saving battery pack)
and now the device names are inconsistent - the device names in the pool
context have not been not updated.

Boot message was shown: "NOTICE: Performing full ZFS device scan!"

Messages regarding the move where also in the logs:

messages:923126:Sep 20 09:24:21 oi genunix: [ID 176336 kern.notice] devid
register: devid for
/pci@0,0/pci8086,c05@1,1/pci1028,1f1c@0/iport@20/disk@p5,0 does not match.
stored:
id1,sd@TATA_Patriot_P220_1TBP220HBCB230710002657,
new:
id1,sd@TATA_EMTEC_X150_480GB511200729140001240__.
messages:923339:Sep 20 09:24:32 oi zfs: [ID 101897 kern.notice] NOTICE:
vdev_disk_open /dev/dsk/c3t2d0s0: update devid from
'id1,sd@SATA_EMTEC_X150_480GB__511200729140001240/a' to
'id1,sd@TATA_EMTEC_X150_480GB511200729140001240__/a'

... but not for the "SCSI" ones (sata disks on SAS controller LSI JOBD,
driver mpt_sas i believe)

Pool status is ok.

Is there a command to update this info?

Reboot did not change the drive info.

Importing/exporting the rpool via OI-USB-live-boot-stick would help, do i
really have to do so ?


# diskinfo
TYPEDISKVID  PID SIZE  RMV SSD
SCSIc7t5d0  EMTECX150 480GB447.13 GiB   no  yes
SCSIc8t4d0  Patriot  P220 1TB  953.87 GiB   no  yes
SATAc3t3d0  EMTECX150 480GB447.13 GiB   no  yes

$ zpool status
   pool: rpool1
  state: ONLINE
   scan: resilvered 381G in 0 days 00:51:40 with 0 errors on Tue Sep 12
16:36:55 2023
config:

 NAME  STATE READ WRITE CKSUM
 rpool1ONLINE   0 0 0
   mirror-0ONLINE   0 0 0
 c3t2d0s0  ONLINE   0 0 0
 c3t3d0s0  ONLINE   0 0 0
 c7t5d0s0  ONLINE   0 0 0


Regards,

Stephan



___
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


Hello!

Thanks for the hints, but no change with

touch /reconfigure

zpool reopen

rm /etc/zfs/zpool.cache


should i try to "zpool offline -t c3t2d0s0" one device and reboot?



It could also be that the label entry is not updated.
zdb -l /dev/dsk/cxtyd0s0 should show the correct one
at least in the first label. I once had such a case,
and had to boot into an older openindiana version to
get that fixed, but that depends of course on the
available and activated pool features.

--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] zpool status rpool not consistent with diskinfo

[Udo Grabowski (IMK)]

You forgot to touch /reconfigure before booting ?

On 20/09/2023 13:14, Stephan Althaus wrote:

Hello!

I swapped 2 of 3 root-pool drives (after power off)
to different controllers, (with power-off-saving battery pack)
and now the device names are inconsistent - the device names in the pool context
have not been not updated.

Boot message was shown: "NOTICE: Performing full ZFS device scan!"

Messages regarding the move where also in the logs:

messages:923126:Sep 20 09:24:21 oi genunix: [ID 176336 kern.notice] devid
register: devid for /pci@0,0/pci8086,c05@1,1/pci1028,1f1c@0/iport@20/disk@p5,0
does not match. stored:
id1,sd@TATA_Patriot_P220_1TBP220HBCB230710002657,
new: 
id1,sd@TATA_EMTEC_X150_480GB511200729140001240__.
messages:923339:Sep 20 09:24:32 oi zfs: [ID 101897 kern.notice] NOTICE:
vdev_disk_open /dev/dsk/c3t2d0s0: update devid from
'id1,sd@SATA_EMTEC_X150_480GB__511200729140001240/a' to
'id1,sd@TATA_EMTEC_X150_480GB511200729140001240__/a'

... but not for the "SCSI" ones (sata disks on SAS controller LSI JOBD,
driver mpt_sas i believe)

Pool status is ok.

Is there a command to update this info?

Reboot did not change the drive info.

Importing/exporting the rpool via OI-USB-live-boot-stick would help, do i really
have to do so ?


# diskinfo
TYPEDISKVID  PID SIZE  RMV SSD
SCSIc7t5d0  EMTECX150 480GB447.13 GiB   no  yes
SCSIc8t4d0  Patriot  P220 1TB  953.87 GiB   no  yes
SATAc3t3d0  EMTECX150 480GB447.13 GiB   no  yes

$ zpool status
  pool: rpool1
 state: ONLINE
  scan: resilvered 381G in 0 days 00:51:40 with 0 errors on Tue Sep 12 16:36:55
2023
config:

NAME  STATE READ WRITE CKSUM
rpool1ONLINE   0 0 0
  mirror-0ONLINE   0 0 0
c3t2d0s0  ONLINE   0 0 0
c3t3d0s0  ONLINE   0 0 0
c7t5d0s0  ONLINE   0 0 0


Regards,

Stephan



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



--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] No sound output - no rights ?

[Udo Grabowski (IMK)]

On 24/08/2023 22:20, Stephan Althaus wrote:

Hello!

I have no audio output - anyone else, too ?

$ prtconf -d | grep -i audio
     pci1028,17b1 (pciex10de,fbc) [NVIDIA Corporation GM107 High 
Definition Audio Controller [GeForce 940MX]], instance #6
     pci1028,7b1 (pciex8086,a171) [Intel Corporation CM238 HD Audio 
Controller], instance #5


$ sudo audioctl list-devices
Password:
audiohd#5
audiohd#6

$ audiotest
Sound subsystem and version: SunOS Audio 4.0 (0x00040003)
Platform: SunOS 5.11 illumos-a98a962ff1 i86pc
/dev/sound/audiohd:5dsp: Permission denied
/dev/sound/audiohd:6dsp: Permission denied

*** Errors were detected ***

$ ls -l /dev/sound/audiohd:5dsp
lrwxrwxrwx   1 root root  49 Apr 11  2019 
/dev/sound/audiohd:5dsp -> 
../../devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5


$ ls -l /devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5
crw---   1 root root  30, 81 Apr 11  2019 
/devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5



There's no group having rights to access the device, nor "others" - is 
this normal ?




This is regulated in /etc/logindevperm:
#
# console   modedevices
#
/dev/vt/console_user0600/dev/mouse:/dev/kbd
/dev/vt/console_user0600/dev/sound/*# audio devices
/dev/vt/console_user0666/dev/fbs/*  # frame buffers
/dev/vt/console_user0600/dev/dri/*  # dri devices
/dev/vt/console_user0400/dev/removable-media/dsk/*  # 
removable media
/dev/vt/console_user0400/dev/removable-media/rdsk/* # 
removable media
/dev/vt/console_user0400/dev/hotpluggable/dsk/* # 
hotpluggable storage
/dev/vt/console_user0400/dev/hotpluggable/rdsk/*# 
hotpluggable storage

/dev/vt/console_user0600/dev/video[0-9]+# video devices
/dev/vt/console_user0600/dev/usb/hid[0-9]+  # hid devices 
should have the same permission with conskbd and consms
/dev/vt/console_user0600/dev/usb/[0-9a-f]+[.][0-9a-f]+/[0-9]+/* 
driver=scsa2usb,usb_mid,usbprn,ugen #libusb/ugen devices

/dev/vt/console_user0666/dev/nvidia[0-9a-f]+# Nvidia
/dev/vt/console_user0666/dev/console# workaround for 
defect.opensolaris.org 12133


You can try to change the mode of /dev/sound/* to 666.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Readahead Batch error

[Udo Grabowski (IMK)]

On 21/07/2023 20:55, Michelle wrote:

In case it helps, this is what's reported by mount...

//192.168.0.2/jaguar on /mnt/jaguar type cifs
(rw,relatime,vers=3.0,cache=none,username=michelle,.. > ..,soft,...

There's your problem: NEVER EVER mount anything
SOFT, but always HARD ! SOFT means YOU have to deal with
every error the channel delivers !

This option should gnererally be hidden from users in
the documentation, it should never be used normally.



Michelle.

On Fri, 2023-07-21 at 19:37 +0200, Till Wegmüller wrote:

Hey Michelle

The Internet tells me this might be related to linuxes client
caching.
Try cache=none if you are having locking problems. And experiment a
bit
with the cache variable.

-Till
On 21.07.23 13:41, Michelle wrote:

Can't work out why I'm getting this, which is causing problems
accessing/renaming/moving files, more specifically if they're in
use by
another process, which used to be no problem under vers=1.0

...but obviously I'm not going to shift back to vers=1.0. I did try
connecting at 2.0 and also leaving the vers off the command
(detailed
later) but no change in behaviour.

Looking the error up on the internet has not given anything that I
can
believe is relevant to this particular combination of client and
server, etc.

OI server is at...
   OpenIndiana Hipster 2022.10 (powered by illumos)
  OpenIndiana Project, part of The Illumos Foundation (C)
2010-
2022
  Use is subject to license terms.
     Assembled 01 November 2022

Client is Linux Mint...
Distributor ID: Linuxmint
Description:Linux Mint 21
Release:21
Codename:   vanessa

Mount version is...
mount from util-linux 2.37.2 (libmount 2.37.2: selinux, smack,
btrfs,
verity, namespaces, assert, debug)

Mounting command is...
sudo mount //192.168.0.2/jaguar /mnt/jaguar -o
user=username,password=password,file_mode=0777,dir_mode=0777,vers=3
.0

Errors received in syslog are...

Jul 21 12:34:04 main-desktop kernel: [1487413.251478] CIFS:
__readahead_batch() returned 9/16
Jul 21 12:34:04 main-desktop kernel: [1487413.260788] CIFS:
__readahead_batch() returned 13/16
Jul 21 12:34:04 main-desktop kernel: [1487413.668432] CIFS:
__readahead_batch() returned 9/16
Jul 21 12:34:05 main-desktop kernel: [1487413.873347] CIFS:
__readahead_batch() returned 3/16
Jul 21 12:34:05 main-desktop kernel: [1487413.877899] CIFS:
__readahead_batch() returned 7/16
Jul 21 12:34:05 main-desktop kernel: [1487413.882006] CIFS:
__readahead_batch() returned 9/16
Jul 21 12:34:05 main-desktop kernel: [1487413.887425] CIFS:
__readahead_batch() returned 4/16
Jul 21 12:34:05 main-desktop kernel: [1487414.095730] CIFS:
__readahead_batch() returned 12/16
Jul 21 12:34:05 main-desktop kernel: [1487414.303237] CIFS:
__readahead_batch() returned 3/16

___
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
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] INFO: thunderbird 102.11.0 doesn't like network problems (?)

[Udo Grabowski (IMK)]

On 23/05/2023 08:04, Stephan Althaus wrote:

Hello!

Just for the records.

Today i observed thunderbird being unresponsible and the cause for 
garbage on the screen, using 1 cpu whith 100%,

whilst my home mail server was not responding.

I would have expected that one network thread in the background in 
waiting state, but not these symptoms.


Starting thunderbird from the console i got these last lines of output:

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci 
missing (t=0.480759) [GFX1-]: glxtest: libpci missing
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci 
missing (t=0.480759) |[1][GFX1-]: glxtest: libEGL missing 
eglGetDisplayDriverName (t=0.480808) [GFX1-]: glxtest: libEGL missing 
eglGetDisplayDriverName
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci 
missing (t=0.480759) |[1][GFX1-]: glxtest: libEGL missing 
eglGetDisplayDriverName (t=0.480808) |[2][GFX1-]: glxtest: libEGL 
missing eglGetDisplayDriverName (t=0.48082) [GFX1-]: glxtest: libEGL 
missing eglGetDisplayDriverName


That's "Wayland" fallout littering Sun-lit spaces... totally unrelated,
but really annoying. Fighting that on firefox, too.

[Parent 2895, Main Thread] WARNING: Failed to connect to proxy: 'glib 
warning', file 
/jenkins/jobs/oi-userland/workspace/components/mail/thunderbird/thunderbird-102.11.0/toolkit/xre/nsSigHandlers.cpp:167


(thunderbird-default:2895): libnotify-WARNING **: 07:52:23.705: Failed 
to connect to proxy


That seems to be an expectable message. The only worrysome here
is that it takes 100% of one CPU; I've not seen that on Linux,
where I regularily have outages due to an unreliable mail provider...
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Cups problems

[Udo Grabowski (IMK)]

On 17/05/2023 09:55, Stephan Althaus wrote:

On 5/16/23 18:45, Udo Grabowski (IMK) wrote:

On 16/05/2023 18: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...

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

3) It complains about a missing ColorManager:
   "The name org.freedesktop.ColorManager was not provided by any .service
   files" which relates to a missing gnome-colord manager (because it's
   mate here...), so it can't read icc-Profiles for the printer. Don't know
   if that affects color-printing somehow.


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




4) it opens network connections like hell (on a simple client):

ro sunts ~ # netstat -afinet | grep \.ipp | wc -l
 105

don't see any messages in regard to this problem, neither in messages,
syslog, cups/access_log or error_log

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


Hello!

I dont't see this problem here:

$ netstat -afinet | grep \.ipp | wc -l
   2

$ svcs -a|grep cup
legacy_run  9:40:33 lrc:/etc/rc3_d/S99cups-browsed
online  9:40:19 svc:/application/cups/scheduler:default
online  9:51:42 svc:/application/cups/in-lpd:default


$ pkg list|grep cups
library/desktop/gtk2/gtk-backend-cups 2.24.32-2023.0.0.5 i--
library/desktop/gtk3/gtk-backend-cups 3.24.34-2023.0.0.2 i--
library/print/cups-libs 2.4.2-2023.0.0.2   i--
library/python/pycups-39 2.0.1-2023.0.0.0   i--
print/cups 2.4.2-2023.0.0.2   i--
print/cups-filters 1.28.17-2023.0.0.1 i--
print/cups/system-config-printer 2.30.0-2023.0.0.7  i--

$ uname -a
SunOS dell7720 5.11 illumos-864a8d6953 i86pc i386 i86pc

I did a pkg update a few minutes ago..



Problem 4 is generated by cups-browsed (avahi,dns/multicast active).
Found this:

/etc/init.d/cups-browsed is linked from several rc*.d/ directories
with S* and K* entries (as specified in package contents).
The script does not set pid for SunOS, so more than one cups-browsed is
started and not killed in run level transitions.
Adding SunOS to the pid discovery in the script leaves one cups-browsed.

This one still generates a loop of connections. The printing server is an
older cups, which is accomodated by setting

ServerName  myserver/version=1.1

in /etc/cups/client.conf. The server is spammed with these log entries:

access_log: hundreds of entries
imksunts - - [17/May/2023:11:05:40 -0100] "POST /admin/ HTTP/1.1" 403 0 - -

error_log: hundreds of corresponding entries
I [17/May/2023:11:05:48 -0100] cupsdAcceptClient: label=(null)

So I suspect that the connection to the old cups printing server
does not function totally correct anymore. Nevertheless, all
advertised printers are found and can be used.

The problems 1 and 2 have been fixed by the latest update.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] Cups problems

[Udo Grabowski (IMK)]

On 16/05/2023 18: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...

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

3) It complains about a missing ColorManager:
   "The name org.freedesktop.ColorManager was not provided by any .service
   files" which relates to a missing gnome-colord manager (because it's
   mate here...), so it can't read icc-Profiles for the printer. Don't know
   if that affects color-printing somehow.


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




4) it opens network connections like hell (on a simple client):

ro sunts ~ # netstat -afinet | grep \.ipp | wc -l
 105

don't see any messages in regard to this problem, neither in messages,
syslog, cups/access_log or error_log
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

[OpenIndiana-discuss] Cups problems

[Udo Grabowski (IMK)]

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...

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

3) It complains about a missing ColorManager:
   "The name org.freedesktop.ColorManager was not provided by any .service
   files" which relates to a missing gnome-colord manager (because it's
   mate here...), so it can't read icc-Profiles for the printer. Don't know
   if that affects color-printing somehow.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] Fwd: Add inotify support to illumos-gate

[Udo Grabowski (IMK)]

On 09/05/2023 07:41, Stephan Althaus wrote:

On 5/8/23 16:10, Udo Grabowski (IMK) wrote:

On 08/05/2023 11:13, Udo Grabowski (IMK) wrote:

On 05/05/2023 09:14, Stephan Althaus wrote:

Hello!

The hint to use inotify support in glib was from you, can you please 
shed a

light on this?

I am lacking all sorts of background on this stuff :-{

To test this, we would have to patch and build inotify support in 
illumos-gate,
install it, then compile glib2 with a check if inotify was found and 
install,
and then mate-system-monitor... to see if this approach does indeed 
help.. Is

there some easier way?

Regards,
Stephan

 Forwarded Message 
Subject: Re: [OpenIndiana-discuss] Add inotify support to 
illumos-gate

Date: Tue, 2 May 2023 20:25:49 +0200
From: Till Wegmüller 
Reply-To: Discussion list for OpenIndiana

To: openindiana-discuss@openindiana.org



Hi Stephan

inotify has stubbed headers that work roughly decently. Any software 
should use
FEN or the Native API. We add it to every programming language we 
can and should
also add it to mate-system-monitor or rather make it use kstat if it 
tries to

poll things under /proc which it should not for us.

What does mate-system-monitor use inotify for?
...


The parts that use Gio for monitoring in mate-system-monitor are located
in prettytable.cpp, where it monitors its apps-cache, and in 
procman-app.cpp,
where it monitors mounts and somehow uses it to process a 
commandline; that's

also the place it crashes (after complaining about the missing monitor
facility):

...



And still, even with LD_LIBRARY_PATH set to gcc 10, libgtkmm-3 again
loads itself libstdc++.so.6 from gcc 7 AND 10, as well as libgcc_s.so.1
from gcc 7 AND 10.

And the same problem for libgdkmm-3, and libpangomm-1.4. Probably because
software that is still compiled with gcc 7 depends on them.

This mixup should be cleared first.

All libraries loaded from mate-system-monitor that depend on gcc:

 /usr/lib/64/libgtkmm-3.0.so.1 ###
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libgdkmm-3.0.so.1 ###
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libxml2.so.2 ###
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/librsvg-2.so.2 ###
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libgiomm-2.4.so.1 ###
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libglibmm-2.4.so.1 ###
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libsigc-2.0.so.0 ###
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/gcc/10/lib/amd64/libstdc++.so.6 ###
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libatkmm-1.6.so.1 ###
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libpangomm-1.4.so.1 ###
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libcairomm-1.0.so.1 ###
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libicuuc.so.68 ###
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libcroco-0.6.so.3 ###
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1



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


Hello!

The linkage seems to be clean now:

$ ldd `which 

Re: [OpenIndiana-discuss] Fwd: Add inotify support to illumos-gate

[Udo Grabowski (IMK)]

On 08/05/2023 20:59, Andreas Wacknitz wrote:

Am 08.05.23 um 16:10 schrieb Udo Grabowski (IMK):

On 08/05/2023 11:13, Udo Grabowski (IMK) wrote:

,,,


And still, even with LD_LIBRARY_PATH set to gcc 10, libgtkmm-3 again
loads itself libstdc++.so.6 from gcc 7 AND 10, as well as libgcc_s.so.1
from gcc 7 AND 10.

And the same problem for libgdkmm-3, and libpangomm-1.4. Probably because
software that is still compiled with gcc 7 depends on them.

This mixup should be cleared first.

All libraries loaded from mate-system-monitor that depend on gcc:

 /usr/lib/64/libgtkmm-3.0.so.1 ###
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

>>

 /usr/lib/64/libgdkmm-3.0.so.1 ###
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
...
 /usr/lib/64/libpangomm-1.4.so.1 ###
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

>> ...




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

I have upgraded pangomm and rebuilt its dependend packages gtkmm, gtkmm3
and gparted.
So all are using the correct libraries now.


libgdkmm-3.0 is also in the list and should be corrected as well.
Unfortunately, my Dell T3500 (where I installed the rolling Hipster)
doesn't boot anymore after update from today (serial 21623) and
I'm unfortunately in HOME-Office...), so I can't check anything
today.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Fwd: Add inotify support to illumos-gate

[Udo Grabowski (IMK)]

On 08/05/2023 11:13, Udo Grabowski (IMK) wrote:

On 05/05/2023 09:14, Stephan Althaus wrote:

Hello!

The hint to use inotify support in glib was from you, can you please shed a
light on this?

I am lacking all sorts of background on this stuff :-{

To test this, we would have to patch and build inotify support in illumos-gate,
install it, then compile glib2 with a check if inotify was found and install,
and then mate-system-monitor... to see if this approach does indeed help.. Is
there some easier way?

Regards,
Stephan

 Forwarded Message 
Subject: Re: [OpenIndiana-discuss] Add inotify support to illumos-gate
Date: Tue, 2 May 2023 20:25:49 +0200
From: Till Wegmüller 
Reply-To: Discussion list for OpenIndiana

To: openindiana-discuss@openindiana.org



Hi Stephan

inotify has stubbed headers that work roughly decently. Any software should use
FEN or the Native API. We add it to every programming language we can and should
also add it to mate-system-monitor or rather make it use kstat if it tries to
poll things under /proc which it should not for us.

What does mate-system-monitor use inotify for?
...


The parts that use Gio for monitoring in mate-system-monitor are located
in prettytable.cpp, where it monitors its apps-cache, and in procman-app.cpp,
where it monitors mounts and somehow uses it to process a commandline; that's
also the place it crashes (after complaining about the missing monitor
facility):

...



And still, even with LD_LIBRARY_PATH set to gcc 10, libgtkmm-3 again
loads itself libstdc++.so.6 from gcc 7 AND 10, as well as libgcc_s.so.1
from gcc 7 AND 10.

And the same problem for libgdkmm-3, and libpangomm-1.4. Probably because
software that is still compiled with gcc 7 depends on them.

This mixup should be cleared first.

All libraries loaded from mate-system-monitor that depend on gcc:

 /usr/lib/64/libgtkmm-3.0.so.1 ###
libstdc++.so.6 =>/usr/gcc/7/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libgdkmm-3.0.so.1 ###
libstdc++.so.6 =>/usr/gcc/7/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libxml2.so.2 ###
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/librsvg-2.so.2 ###
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libgiomm-2.4.so.1 ###
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libglibmm-2.4.so.1 ###
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libsigc-2.0.so.0 ###
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/gcc/10/lib/amd64/libstdc++.so.6 ###
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libatkmm-1.6.so.1 ###
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libpangomm-1.4.so.1 ###
libstdc++.so.6 =>/usr/gcc/7/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libcairomm-1.0.so.1 ###
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libicuuc.so.68 ###
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
 /usr/lib/64/libcroco-0.6.so.3 ###
libstdc++.so.6 =>/usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1


--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english

Re: [OpenIndiana-discuss] Fwd: Add inotify support to illumos-gate

[Udo Grabowski (IMK)]

On 05/05/2023 09:14, Stephan Althaus wrote:

Hello!

The hint to use inotify support in glib was from you, can you please shed a
light on this?

I am lacking all sorts of background on this stuff :-{

To test this, we would have to patch and build inotify support in illumos-gate,
install it, then compile glib2 with a check if inotify was found and install,
and then mate-system-monitor... to see if this approach does indeed help.. Is
there some easier way?

Regards,
Stephan

 Forwarded Message 
Subject:Re: [OpenIndiana-discuss] Add inotify support to illumos-gate
Date:   Tue, 2 May 2023 20:25:49 +0200
From:   Till Wegmüller 
Reply-To:   Discussion list for OpenIndiana 

To: openindiana-discuss@openindiana.org



Hi Stephan

inotify has stubbed headers that work roughly decently. Any software should use
FEN or the Native API. We add it to every programming language we can and should
also add it to mate-system-monitor or rather make it use kstat if it tries to
poll things under /proc which it should not for us.

What does mate-system-monitor use inotify for?
...


The parts that use Gio for monitoring in mate-system-monitor are located
in prettytable.cpp, where it monitors its apps-cache, and in procman-app.cpp,
where it monitors mounts and somehow uses it to process a commandline; that's
also the place it crashes (after complaining about the missing monitor
facility):

ts(~) env LD_LIBRARY_PATH=/usr/gcc/10/lib dbx `which mate-system-monitor`
For information about new features see `help changes'
To remove this message, put `dbxenv suppress_startup_message 7.7' in your .dbxrc
Reading mate-system-monitor
Reading ld.so.1
Reading libc.so.1
Reading libgtkmm-3.0.so.1.1.0
Reading libgiomm-2.4.so.1.3.0
Reading libglibmm-2.4.so.1.3.0
Reading libstdc++.so.6.0.28
Reading libm.so.2
Reading libgcc_s.so.1
Reading libgdkmm-3.0.so.1.1.0
Reading libstdc++.so.6.0.24
Reading libgcc_s.so.1
Reading libatkmm-1.6.so.1.1.0
Reading libsigc-2.0.so.0.0.0
Reading libgtk-3.so.0.2404.30
Reading libgdk-3.so.0.2404.30
Reading libgobject-2.0.so.0.7400.7
Reading libglib-2.0.so.0.7400.7
Reading libffi.so.6.0.4
Reading libepoxy.so.0.0.0
Reading libcairo.so.2.11600.0
Reading libEGL.so.1
Reading libpthread.so.1
Reading librt.so.1
Reading libsocket.so.1
Reading libnvidia-glsi.so.1
Reading libnsl.so.1
Reading libxcb.so.1.1.0
Reading libxcb-render.so.0.0.0
Reading libGL.so.1
Reading libnvidia-tls.so.1
Reading libnvidia-glcore.so.1
Reading libX11.so.4.0.0
Reading libXext.so.0.0.0
Reading libatk-1.0.so.0.23809.1
Reading libgio-2.0.so.0.7400.7
Reading libpango-1.0.so.0.5000.14
(dbx) run
Running: mate-system-monitor
(process id 7317)
Reading libgtop-2.0.so.11.0.1
Reading libxml2.so.2.10.4
Reading libicuuc.so.68.2
Reading libicudata.so.68.2
Reading librsvg-2.so.2.40.21
Reading libgmodule-2.0.so.0.7400.7
Reading libwnck-3.so.0.3.0
Reading libpangocairo-1.0.so.0.5000.14
Reading libgdk_pixbuf-2.0.so.0.3612.0
Reading libcairo-gobject.so.2.11600.0
Reading libXau.so.6.0.0
Reading libkstat.so.1
Reading libcairomm-1.0.so.1.4.0
Reading libz.so.1.2.13
Reading liblzma.so.5.4.2
Reading libpangoft2-1.0.so.0.5000.14
Reading libfontconfig.so.1.12.0
Reading libcroco-0.6.so.3.0.1
Reading libXrender.so.1.3.0
Reading libstartup-notification-1.so.0.0.0
Reading libXRes.so.1.0.0
Reading libXinerama.so.1.0.0
Reading libXrandr.so.2.2.0
Reading libXcursor.so.1.0.2
Reading libXi.so.5.0.0
Reading libXcomposite.so.1.0.0
Reading libXdamage.so.1.1.0
Reading libXfixes.so.1.0.0
Reading libatk-bridge-2.0.so.0.0.0
Reading libfribidi.so.0.4.0
Reading libharfbuzz.so.0.60720.0
Reading libfreetype.so.6.19.0
Reading libresolv.so.2
Reading libthai.so.0.3.1
Reading libpixman-1.so.0.42.2
Reading libdl.so.1
Reading libpng16.so.16.39.0
Reading libX11-xcb.so.1.0.0
Reading libpcre2-8.so.0.11.2
Reading libmp.so.2
Reading libmd.so.1
Reading libexpat.so.1.8.10
Reading libxcb-util.so.1.0.0
Reading libatspi.so.0.0.1
Reading libdbus-1.so.3.19.15
Reading libgraphite2.so.3.2.1
Reading libbz2.so.1
Reading libbrotlidec.so.1.0.9
Reading libbrotlicommon.so.1.0.9
Reading libdatrie.so.1.4.0
Reading libXdmcp.so.6.0.0
Reading libbsm.so.1
Reading libsecdb.so.1
Reading libtsol.so.2
Reading libinetutil.so.1
Reading libscf.so.1
Reading libuutil.so.1
Reading libgen.so.1
Reading libnvpair.so.1
Reading libsmbios.so.1
Reading libdevinfo.so.1
Reading libsec.so.1
Reading libavl.so.1
Reading libidmap.so.1
Reading libpangomm-1.4.so.1.0.30
Reading libgvfsdbus.so
Reading libcanberra-gtk3-module.so
Reading xlcUTF8Load.so.2.0.0
Reading libdconfsettings.so
Reading libgsettingsgconfbackend.so
Reading libgconf-2.so.4.1.5
Reading libORBit-2.so.0.1.0

(:7317): glibmm-CRITICAL **: 10:56:52.629:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

t@1 (l@1) signal SEGV (no mapping at the fault address) in 
ProcmanApp::on_command_line at 0x44b0a1

0x0044b0a1: on_command_line+0x0111: movq 

Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

[Udo Grabowski (IMK)]

On 02/05/2023 11:06, Stephan Althaus wrote:

On 5/2/23 11:01, Udo Grabowski (IMK) wrote:

On 02/05/2023 10:55, Udo Grabowski (IMK) wrote:

On 01/05/2023 22:02, Stephan Althaus wrote:

On 4/19/23 15:59, Udo Grabowski (IMK) wrote:

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and 
found that like
the non working screensavers see 
(https://www.illumos.org/issues/15138) which

abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to gcc 
10 I believe

it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 
mate-system-monitor


(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd 
`which mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1



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


Hello!

Info:

This error persists even after upgrade glib2 to 2.74.7 as build on 
the official build server on 30.04.2023 (pkg update some minutes ago)..
On a fast search i did not find any 'easy' configure option to add 
"inotify/fam support" as suggested by Udo Grabowski


Regards,

Stephan Althaus

_

$ pkg info glib2
  Name: library/glib2
   Summary: GNOME core libraries
  Category: Desktop (GNOME)/Libraries
 State: Installed
 Publisher: openindiana.org
   Version: 2.74.7
    Branch: 2023.0.0.0
    Packaging Date: April 30, 2023 at 08:34:29 PM
Last Install Time: September  7, 2019 at 07:43:17 PM
  Last Update Time: May  1, 2023 at 05:59:29 PM
  Size: 21.65 MB
  FMRI: 
pkg://openindiana.org/library/glib2@2.74.7-2023.0.0.0:20230430T203429Z


$ env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:4045): Gtk-WARNING **: 21:53:22.206: Theme parsing error: 
gtk-widgets.css:6:28: The style property GtkRange:slider-width is 
deprecated and shouldn't be used anymore. It will be removed in a 
future version

..
(:4045): glibmm-CRITICAL **: 21:53:22.275:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 4045:    mate-system-monitor
- thread# 1 / lwp# 1 -
  7fffac7c6ca7 g_type_check_instance_cast () + 17
  0044977a 
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 11a
  7fff9e799ab0 
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 160

  7fffac4ace5f _g_cclosure_marshal_INT__OBJECTv () + 6f
  7fffac79aa08 _g_closure_invoke_va () + 188
  7fffac7baf92 g_signal_emit_valist () + 332
  7fffac7bc17d g_signal_emit () + 7d
  7fffac509933 g_application_call_command_line () + a3
  7fffac50bd71 g_application_real_local_command_line () + 211
  7fff9e798722 
_ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 52
  7fff9e79939b 
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + fb

  7fffac50bef3 g_application_run () + 133
  00422b4e main () + 5e
  00421e07 _start_crt () + 87
  00421d68 _start () + 18



Yes, it's also still ingesting both gcc-7 and 10 libraries.
The configure script for glib2 seems to check for the presence of
libfam and inotify by default, but fam support could be switched
off by an explicitly set option. The fam library is installed by
package library/file-monitor/gamin .



Has fam-support been removed from glib2 ?

<https://src.fedoraproject.org/rpms/glib2/blob/rawhide/f/glib2.spec>
...
# Remove gamin dependency
Obsoletes: glib2-fam < 2.67.1-3

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


Found this:

https://github.com/AOS

Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

[Udo Grabowski (IMK)]

On 02/05/2023 10:55, Udo Grabowski (IMK) wrote:

On 01/05/2023 22:02, Stephan Althaus wrote:

On 4/19/23 15:59, Udo Grabowski (IMK) wrote:

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and found 
that like
the non working screensavers see 
(https://www.illumos.org/issues/15138) which

abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to gcc 10 
I believe

it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 
mate-system-monitor


(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd `which 
mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1



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


Hello!

Info:

This error persists even after upgrade glib2 to 2.74.7 as build on the 
official build server on 30.04.2023 (pkg update some minutes ago)..
On a fast search i did not find any 'easy' configure option to add 
"inotify/fam support" as suggested by Udo Grabowski


Regards,

Stephan Althaus

_

$ pkg info glib2
  Name: library/glib2
   Summary: GNOME core libraries
  Category: Desktop (GNOME)/Libraries
 State: Installed
 Publisher: openindiana.org
   Version: 2.74.7
    Branch: 2023.0.0.0
    Packaging Date: April 30, 2023 at 08:34:29 PM
Last Install Time: September  7, 2019 at 07:43:17 PM
  Last Update Time: May  1, 2023 at 05:59:29 PM
  Size: 21.65 MB
  FMRI: 
pkg://openindiana.org/library/glib2@2.74.7-2023.0.0.0:20230430T203429Z


$ env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:4045): Gtk-WARNING **: 21:53:22.206: Theme parsing error: 
gtk-widgets.css:6:28: The style property GtkRange:slider-width is 
deprecated and shouldn't be used anymore. It will be removed in a 
future version

..
(:4045): glibmm-CRITICAL **: 21:53:22.275:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 4045:    mate-system-monitor
- thread# 1 / lwp# 1 -
  7fffac7c6ca7 g_type_check_instance_cast () + 17
  0044977a 
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 11a
  7fff9e799ab0 
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 160

  7fffac4ace5f _g_cclosure_marshal_INT__OBJECTv () + 6f
  7fffac79aa08 _g_closure_invoke_va () + 188
  7fffac7baf92 g_signal_emit_valist () + 332
  7fffac7bc17d g_signal_emit () + 7d
  7fffac509933 g_application_call_command_line () + a3
  7fffac50bd71 g_application_real_local_command_line () + 211
  7fff9e798722 
_ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 52
  7fff9e79939b 
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + fb

  7fffac50bef3 g_application_run () + 133
  00422b4e main () + 5e
  00421e07 _start_crt () + 87
  00421d68 _start () + 18



Yes, it's also still ingesting both gcc-7 and 10 libraries.
The configure script for glib2 seems to check for the presence of
libfam and inotify by default, but fam support could be switched
off by an explicitly set option. The fam library is installed by
package library/file-monitor/gamin .
 


Has fam-support been removed from glib2 ?

<https://src.fedoraproject.org/rpms/glib2/blob/rawhide/f/glib2.spec>
...
# Remove gamin dependency   
Obsoletes: glib2-fam < 2.67.1-3
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

[Udo Grabowski (IMK)]

On 01/05/2023 22:02, Stephan Althaus wrote:

On 4/19/23 15:59, Udo Grabowski (IMK) wrote:

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and found 
that like
the non working screensavers see 
(https://www.illumos.org/issues/15138) which

abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to gcc 10 
I believe

it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd `which 
mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1



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


Hello!

Info:

This error persists even after upgrade glib2 to 2.74.7 as build on the 
official build server on 30.04.2023 (pkg update some minutes ago)..
On a fast search i did not find any 'easy' configure option to add 
"inotify/fam support" as suggested by Udo Grabowski


Regards,

Stephan Althaus

_

$ pkg info glib2
  Name: library/glib2
   Summary: GNOME core libraries
  Category: Desktop (GNOME)/Libraries
     State: Installed
     Publisher: openindiana.org
   Version: 2.74.7
    Branch: 2023.0.0.0
    Packaging Date: April 30, 2023 at 08:34:29 PM
Last Install Time: September  7, 2019 at 07:43:17 PM
  Last Update Time: May  1, 2023 at 05:59:29 PM
  Size: 21.65 MB
  FMRI: 
pkg://openindiana.org/library/glib2@2.74.7-2023.0.0.0:20230430T203429Z


$ env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:4045): Gtk-WARNING **: 21:53:22.206: Theme parsing error: 
gtk-widgets.css:6:28: The style property GtkRange:slider-width is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version

..
(:4045): glibmm-CRITICAL **: 21:53:22.275:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 4045:    mate-system-monitor
- thread# 1 / lwp# 1 -
  7fffac7c6ca7 g_type_check_instance_cast () + 17
  0044977a 
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 11a
  7fff9e799ab0 
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 160

  7fffac4ace5f _g_cclosure_marshal_INT__OBJECTv () + 6f
  7fffac79aa08 _g_closure_invoke_va () + 188
  7fffac7baf92 g_signal_emit_valist () + 332
  7fffac7bc17d g_signal_emit () + 7d
  7fffac509933 g_application_call_command_line () + a3
  7fffac50bd71 g_application_real_local_command_line () + 211
  7fff9e798722 _ZN3Gio11Application24local_command_line_vfuncERPPcRi 
() + 52
  7fff9e79939b 
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + fb

  7fffac50bef3 g_application_run () + 133
  00422b4e main () + 5e
  00421e07 _start_crt () + 87
  00421d68 _start () + 18



Yes, it's also still ingesting both gcc-7 and 10 libraries.
The configure script for glib2 seems to check for the presence of
libfam and inotify by default, but fam support could be switched
off by an explicitly set option. The fam library is installed by
package library/file-monitor/gamin .
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] overlay mounts in zfs

[Udo Grabowski (IMK)]

On 24/04/2023 15:00, Udo Grabowski (IMK) wrote:

On 24/04/2023 14:53, Marc Lobelle wrote:

Hello,

Zfs mount can be used with -O argument to allow overlay mount, but 
apparently, this argument is not known in zpool import. is there a way 
to zpool import if the mounting directory is not empty ?


zpool import [-o mntopts]


No, doesn't work, it only accepts the mount -o ... options there, not
-o '-O'
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] overlay mounts in zfs

[Udo Grabowski (IMK)]

On 24/04/2023 14:53, Marc Lobelle wrote:

Hello,

Zfs mount can be used with -O argument to allow overlay mount, but 
apparently, this argument is not known in zpool import. is there a way 
to zpool import if the mounting directory is not empty ?


zpool import [-o mntopts]
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

[Udo Grabowski (IMK)]

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and found that like
the non working screensavers see (https://www.illumos.org/issues/15138) which
abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to gcc 10 I believe
it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd `which 
mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 =>  /usr/gcc/10/lib/amd64/libgcc_s.so.1


--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] mate system monitor does not work any more on recent versions of openindiana

[Udo Grabowski (IMK)]

On 19/04/2023 15:01, Marc Lobelle wrote:

Hello Udo,

I do not really understand what to do: uninstalling the old gcc 7 ? But I do not
see the relation between fam and the system monitor program.

What exactly should I do ?



You can't do anything. mate-system-monitor has to be recompiled
so that it don't load both gcc7 and gcc10 libraries. I emulated
that by changing the binary with elfedit, linking libraries
locally and preloading. But then you trap on the root cause,
which is the missing fam support in glib that causes most of
the gio stuff to fail. This is also seen in a report on the
GNU Hurd list: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875915>



On 4/19/23 14:46, Udo Grabowski (IMK) wrote:

On 19/04/2023 13:00, Stephan Althaus wrote:

On 4/19/23 12:25, Marc Lobelle wrote:

Hello,

I updated openindiana from 2021-10 to 2022-10 on my notebook and the mate
system monitor does not start if I click on the widget: the widget is still
there and displays cpu usage, but if I click on it to get the window with full
information, I see a hourglass for a few seconds then nothing: it seems to
crash before opening the window.

Is there a workaround ?

Thanks

Marc


Hello!

This issue persists for several weeks now and is reproducible.

Alas, i can't see the root caause from the 'pstack' of the core dump, maybe
someone else is able to dig this out.

Regards,

Stephan

$ pstack core
core 'core' of 7849:mate-system-monitor
- thread# 1 / lwp# 1 -
 7fffaf40729a _lwp_kill () + a
 7fffaf39b1ee raise (6) + 1e
 7fffaf374c58 abort () + 58
 7fffab6e2b0e  ()
 7fffab8708c1 __gxx_personality_v0 () + d1
 7fffaccd5756 _Unwind_RaiseException_Phase2 () + a6
 7fffaccd6126 _Unwind_Resume () + 126
 7fff7712b9d5  ()
 0042f84b _ZN11PrettyTableC1Ev () + 1db
 004223e1 _ZN8ProcData12get_instanceEv () + 81
 0044832c _ZL16procman_data_newP10_GSettings () + 1c
 0044904d _ZN10ProcmanApp10on_startupEv () + 4d
 7fff770f9615 _ZN3Gio17Application_Class16startup_callbackEP13_GApplication
...


This boils down essentially to two problems at once: Both gcc7 and gcc10
libstdc++.so and libgcc_s.so are loaded, which breaks exception handling.
Massaging dyn:runpath and preloading then uncovers the second problem:

ro sunts /tmp # ./mate-system-monitor

(:11878): glibmm-CRITICAL **: 14:08:27.008:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault


That's what I already wrote in the thread
<https://www.mail-archive.com/openindiana-discuss@openindiana.org/msg26671.html>

The /usr/lib/gio/modules/ directory has the giomodule.cache file.
When you try to recreate it with gio-querymodules /usr/lib/gio/modules/,
it's gone!

So probably the right fixes should be: Sort out the gcc7/10 confusion,
and compile glib with inotify/fam support.

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



--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026


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

Re: [OpenIndiana-discuss] mate system monitor does not work any more on recent versions of openindiana

[Udo Grabowski (IMK)]

On 19/04/2023 13:00, Stephan Althaus wrote:

On 4/19/23 12:25, Marc Lobelle wrote:

Hello,

I updated openindiana from 2021-10 to 2022-10 on my notebook and the mate
system monitor does not start if I click on the widget: the widget is still
there and displays cpu usage, but if I click on it to get the window with full
information, I see a hourglass for a few seconds then nothing: it seems to
crash before opening the window.

Is there a workaround ?

Thanks

Marc


Hello!

This issue persists for several weeks now and is reproducible.

Alas, i can't see the root caause from the 'pstack' of the core dump, maybe
someone else is able to dig this out.

Regards,

Stephan

$ pstack core
core 'core' of 7849:mate-system-monitor
- thread# 1 / lwp# 1 -
 7fffaf40729a _lwp_kill () + a
 7fffaf39b1ee raise (6) + 1e
 7fffaf374c58 abort () + 58
 7fffab6e2b0e  ()
 7fffab8708c1 __gxx_personality_v0 () + d1
 7fffaccd5756 _Unwind_RaiseException_Phase2 () + a6
 7fffaccd6126 _Unwind_Resume () + 126
 7fff7712b9d5  ()
 0042f84b _ZN11PrettyTableC1Ev () + 1db
 004223e1 _ZN8ProcData12get_instanceEv () + 81
 0044832c _ZL16procman_data_newP10_GSettings () + 1c
 0044904d _ZN10ProcmanApp10on_startupEv () + 4d
 7fff770f9615 _ZN3Gio17Application_Class16startup_callbackEP13_GApplication
...


This boils down essentially to two problems at once: Both gcc7 and gcc10
libstdc++.so and libgcc_s.so are loaded, which breaks exception handling.
Massaging dyn:runpath and preloading then uncovers the second problem:

ro sunts /tmp # ./mate-system-monitor

(:11878): glibmm-CRITICAL **: 14:08:27.008:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault


That's what I already wrote in the thread


The /usr/lib/gio/modules/ directory has the giomodule.cache file.
When you try to recreate it with gio-querymodules /usr/lib/gio/modules/,
it's gone!

So probably the right fixes should be: Sort out the gcc7/10 confusion,
and compile glib with inotify/fam support.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

[OpenIndiana-discuss] Mail archives 404

[Udo Grabowski (IMK)]

All the links to the list archives are gone:

--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] Proper invocation for zfs sharenfs

[Udo Grabowski (IMK)]

On 12/04/2023 17:07, Till Wegmüller wrote:

On 12.04.23 16:02, Udo Grabowski (IMK) wrote:



,anon=abuild  is not a valid sharenfs option.


Hi Udo

I also simply tried rw as option with the same result. If you see the Mail from
Marcel, that was the issue. service/file-system/nfs was not installed in the
zone. With the package installed it worked.

anon is infact an option documented in 'man share_nfs' it maps all non user
accesses to the user given. In my case the common build user delivered via
developer/abuild-common and thus guaranteed to have the same UID on all systems.



On my older system the anon= option is only accepted when using a uid,
not a name.

--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] Proper invocation for zfs sharenfs

[Udo Grabowski (IMK)]

On 12/04/2023 15:19, Till Wegmüller wrote:

Hello everyone

I am currently trying to configure an NFS server but I seem to fail to correctly
invoke zfs sharenfs properly.

zfs keeps complaining with 'cannot set property for 'rpool/data/oirepo':
'sharenfs' cannot be set to invalid options'

And a manual invokation of share keeps complaining with: 'Invalid protocol
specified: nfs'

My command is:
~# zfs set
sharenfs='rw=@10.1.0.70:@10.1.0.71:@10.1.0.72,ro=@10.1.0,root=@10.1.0.70:@10.1.0.71:@10.1.0.72,anon=abuild'
rpool/data/oirepo

Does anybody know the correct invokation? Manpages etc. show that this should be
correct but I can't make it work.

Thanks
Till

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


,anon=abuild  is not a valid sharenfs option.

--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] update conflicts, what happened?

[Udo Grabowski (IMK)]

On 12/04/2023 07:16, Marcel Telka wrote:

On Tue, Apr 11, 2023 at 07:33:32PM -0400, Richard L. Hamilton wrote:

root@openindiana:~# pkg update
Creating Plan (Checking for conflicting actions): /
pkg update: The following packages all deliver driver actions to nvidia:

  
pkg://openindiana.org/driver/graphics/nvidia@525.105.17,5.11-2023.0.0.0:20230331T112122Z
  
pkg://openindiana.org/driver/graphics/nvidia-390@390.157,5.11-2022.0.0.0:20221123T085801Z

These packages cannot be installed together. Any non-conflicting subset
of the above packages can be installed.


We switched the default NVIDIA driver from nvidia-390 to nvidia
recently.  Since both nvidia-390 and nvidia packages cannot be installed
together you need to manually uninstall nvidia-390 first (possibly with
few other packages that depends on nvidia-390[*]) to get the system
updated and then install nvidia package back (together with other
packages you uninstalled previously).

[*] I think the list includes these packages: mate_install,
server_install, x11/server/xorg/driver/xorg-video.

HTH.



Since that is a real nuisance if you have an older graphics card that
depends on 390 availability: Is it possible to deliver the NVIDIA
package via a mediator ?
All of our cards are unsupported with 525.x.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] Firefox still reporting missing codecs

[Udo Grabowski (IMK)]

On 30/03/2023 17:26, russell wrote> Performed an update yesterday 
evening creating a new BE, rebooted and > checked access to youtube.> 
Some videos work without issue generating no alert but others will not > 
play because the video codec is not available

firefox delegates some video playback to ffmpeg. Since the pkgin
repository (https://pkgsrc.smartos.org) has much more plugins than
the OI one, I have installed from there:

fmpeg5-5.1.2nb4 Decoding, encoding and streaming software (v5.x)
gst-ffmpeg-0.10.13nb29 GStreamer ffmpeg plugin
gst-plugins1-libav-1.22.1 GStreamer libav/ffmpeg plugin

and redirect firefox vi a script to load ffmpeg from there:

LD_LIBRARY_PATH=/opt/local/lib/ffmpeg5:${LD_LIBRARY_PATH} 
/usr/lib/amd64/firefox/firefox $@
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices

[Udo Grabowski (IMK)]

On 24/03/2023 10:03, Toomas Soome via openindiana-discuss wrote:




On 24. Mar 2023, at 10:50, Udo Grabowski (IMK)  wrote:



On 24/03/2023 09:43, Marc Lobelle wrote:

On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote:



On 24. Mar 2023, at 07:58, Stephan Althaus  
wrote:

On 3/22/23 20:56, Richard Lowe wrote:

The challenge of answering that is you often don't know the answer
until you see it

The ::stacks command will give you asummarized view of every kernel
thread's stack
the ::cpuinfo -v command will show you what the CPUs are doing now (or
were doing, before you got into kmdb).

Both or either might have a smoking gun of some kind, but it's hard to
predict what it might look like.

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

Hello!

In one of my earlier update-tests i had a problem with the first OI-nvidia-525 
version in cooperation with Virtualbox,
so i had the idea to test this:

I uninstalled 'userland-incorporation' and 'entire' as prerequisite to  install 
nvidia version 515,
now it boots!

So, nvidia in the most recent version 525 stopped the boot process. (?)

i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is 
on the supported list for this version:
https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/


How/Why should the display driver be able to interrupt the boot process ?
How/Why should the display driver be able to interrupt the boot process without 
further notice?


That is something one can work out with debugger. But, this is binary only 
driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside 
Oracle Solaris? This means, the question is not “if” but “when” - it is only 
question of time when such drivers become unusable for us. Without gfx driver 
development, the desktop variant of illumos is dead end.

without desktop, it would unfortunately mean the dead of illumos. If Oracle 
solaris drivers become unusable shouldn't illumos move to another driver 
interface that is maintained ?


Maybe we wait until the cause for the problem is known before
declaring everything dead ?



It is a bit premature to declare everything dead, but, the fact is, we can not 
rely on binary only drivers forever. As soon as Oracle will decide to stop 
distributing Solaris, nvidia will have no reason to distribute those binary 
drivers.


Solaris is officially supported until 2030, so there's
(at least formally) time left as long as the ABI does
not become incompatible without a possible workaround.
And after that, old drivers will still work until new
graphics cards appear. So there's time to work on a
possible migration path.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices

[Udo Grabowski (IMK)]

On 24/03/2023 09:43, Marc Lobelle wrote:


On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote:


On 24. Mar 2023, at 07:58, Stephan Althaus 
 wrote:


On 3/22/23 20:56, Richard Lowe wrote:

The challenge of answering that is you often don't know the answer
until you see it

The ::stacks command will give you asummarized view of every kernel
thread's stack
the ::cpuinfo -v command will show you what the CPUs are doing now (or
were doing, before you got into kmdb).

Both or either might have a smoking gun of some kind, but it's hard to
predict what it might look like.

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

Hello!

In one of my earlier update-tests i had a problem with the first 
OI-nvidia-525 version in cooperation with Virtualbox,

so i had the idea to test this:

I uninstalled 'userland-incorporation' and 'entire' as prerequisite 
to  install nvidia version 515,

now it boots!

So, nvidia in the most recent version 525 stopped the boot process. (?)

i checked with NVidia Solaris Driver Archive that my chipset (Quadro 
M1200) is on the supported list for this version:

https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/


How/Why should the display driver be able to interrupt the boot 
process ?
How/Why should the display driver be able to interrupt the boot 
process without further notice?


That is something one can work out with debugger. But, this is binary 
only driver? Built *for Oracle Solaris 11.4*? With API interfaces 
changed inside Oracle Solaris? This means, the question is not “if” 
but “when” - it is only question of time when such drivers become 
unusable for us. Without gfx driver development, the desktop variant 
of illumos is dead end.


without desktop, it would unfortunately mean the dead of illumos. If 
Oracle solaris drivers become unusable shouldn't illumos move to another 
driver interface that is maintained ?




Maybe we wait until the cause for the problem is known before
declaring everything dead ?

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

Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices

[Udo Grabowski (IMK)]

On 21/03/2023 23:09, Stephan Althaus wrote:

On 3/21/23 20:53, Richard Lowe wrote:

A good thing to do is to get into mdb when it's hung, and see where we
are with the ::stacks command.
https://illumos.org/books/dev/debugging.html  has other tips.

I would add if you set the 1 bit of `moddebug` when you're in kmdb (I
think moddebug/W 8001 is verbose and stop on _init, but I tend to
forget), we will stop whenever a module `_init` is called, which can
be a good trick to try to narrow down where things might have gone
wrong if we don't respond to any means to get into kmdb.

More manually, an illumos version which works and one which doesn't
work will narrow down which illumos changes might have caused
problems.

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


Hello!

Thanks for your input. I tried the kmdb switched on on boot,
with ::cont i have the same situation that i can't escape the running process to
get the ::stack

Comparing the boot messages of the working BE and the not-working one, it stops
between these two pseudo-devices:


Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: 
signalfd0
*Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] signalfd0 is
/pseudo/signalfd@0*
Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: timerfd0
Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] timerfd0 is
/pseudo/timerfd@0


The line with "*signalfd0 is /pseudo/signalfd@0*" is the last output, then
nothing more happens.



You can pin that down to timerfd if you just mount the new BE and
move away /usr/kernel/drv/amd64/timerfd and see if it then boots.

Consult 'man timerfd' to convince yourself that that driver is
irrelevant to illumos...
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices

[Udo Grabowski (IMK)]

On 20/03/2023 21:45, Stephan Althaus wrote:

Hello!

On 18.03.2023 i made a pkg update, after that the Boot hangs after configuring
devices (last notice is of pseudo devices with boot option 'verbose')

Nothing happens on the prompt...

"beadm mount..." shows no fresh logfiles, so no info there, i should use some
debug options but i am not familiar to that :-/


Any hints ?


Didn't have such a failure after updating and booting today, but
didn't reboot since 14.3.

So I would recommend to revert to the previous BE and update that
again.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

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

[Udo Grabowski (IMK)]

On 05/03/2023 18:42, Richard L. Hamilton wrote:




On Mar 5, 2023, at 12:12, Peter Tribble  wrote:

On Sun, Mar 5, 2023 at 4:19 PM Till Wegmüller  wrote:


Hi

IPS works on images of the OS. And it does so in an Atomic way. Speed is
not the main goal. Stability is.



The emphasis on performance can be seen in several areas of the design -
downloading
and updating just the files you need rather than whole packages;
eliminating the overhead
of maintaining the shared contents file.

It's unfortunate that the original aim of improving performance got lost
along the way.

--
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/



Yes...I wasn't badmouthing IPS, just noting that compared to e.g. well-supported  > and maintained Linux distros (Kali Linux has impressed me recently), 

> it's slow.
>

In fact, most of the phases are really fast (as can be verified with
pkg update -v), the competition is lost when it comes to the phase
'Building new search index', which is much slower than everything
before summed up. So concentrating the effort to this phase alone
could be already sufficient to speed it up a lot.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] VIM 9: lost shell (read bash) syntax

[Udo Grabowski (IMK)]

On 20/02/2023 17:47, Udo Grabowski (IMK) wrote:

On 20/02/2023 17:17, Udo Grabowski (IMK) wrote:

On 20/02/2023 17:05, Predrag Zecevic wrote:

On 20.02.2023 16:53, Udo Grabowski (IMK) wrote:

On 20/02/2023 16:49, Udo Grabowski (IMK) wrote:

On 20/02/2023 16:20, Predrag Zecevic via openindiana-discuss wrote:

Hi all,

does anyone has nice .vimrc, which still obey syntax coloring? Especially for
bash...

Recently, vim was upgrade from version 8 to 9:

:; pkg list *editor/vim*
NAME (PUBLISHER) VERSIONIFO
editor/vim 9.0.1300-2023.0.0.0i--
editor/vim/vim-core 9.0.1300-2023.0.0.0i--

Since then, bash syntax coloring is not working with neither .vimrc (old one,
and modified one). Or w/o .vimrc.
Previously, that syntax highlighting could help a lot, when entering shell
commands to point to the syntax error.

Now, it is completely useless...

Any thoughts? Anyone still uses it?


No problem here, with .vimrc

set encoding=utf-8
set term=xterm-color
syntax enable

everything highlights fine, even bash scripts.



You may also need this (one line) :
autocmd Syntax * exec("set
dict+=".$VIMRUNTIME."/syntax/".expand('').".vim")


Thanks,

---8<--
:; cat ~/.vim/vimrc
set encoding=utf-8
set term=xterm-color


And another fix that I just learned:

set term=gnome-256color

This avoids cluttering of the commandline with t_TI and t_TE
sequences newer vims spit out everywhere...
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] VIM 9: lost shell (read bash) syntax

[Udo Grabowski (IMK)]

On 20/02/2023 17:17, Udo Grabowski (IMK) wrote:

On 20/02/2023 17:05, Predrag Zecevic wrote:

On 20.02.2023 16:53, Udo Grabowski (IMK) wrote:

On 20/02/2023 16:49, Udo Grabowski (IMK) wrote:

On 20/02/2023 16:20, Predrag Zecevic via openindiana-discuss wrote:

Hi all,

does anyone has nice .vimrc, which still obey syntax coloring? Especially for
bash...

Recently, vim was upgrade from version 8 to 9:

:; pkg list *editor/vim*
NAME (PUBLISHER) VERSIONIFO
editor/vim 9.0.1300-2023.0.0.0i--
editor/vim/vim-core 9.0.1300-2023.0.0.0i--

Since then, bash syntax coloring is not working with neither .vimrc (old one,
and modified one). Or w/o .vimrc.
Previously, that syntax highlighting could help a lot, when entering shell
commands to point to the syntax error.

Now, it is completely useless...

Any thoughts? Anyone still uses it?


No problem here, with .vimrc

set encoding=utf-8
set term=xterm-color
syntax enable

everything highlights fine, even bash scripts.



You may also need this (one line) :
autocmd Syntax * exec("set
dict+=".$VIMRUNTIME."/syntax/".expand('').".vim")


Thanks,

---8<--
:; cat ~/.vim/vimrc
set encoding=utf-8
set term=xterm-color
syntax enable

autocmd Syntax * exec("set
dict+=".$VIMRUNTIME."/syntax/".expand('').".vim")
---8<--

and still no luck (tried from within *tmux* session and from pure bash shell).
Same version from Ubuntu 22.04 (I had to install it from PPA repo) shows test
bash file properly.

So, it could be something on my machine.
The problem is I have no clue where to start.


Oh, there is definitely a problem with the bash hilighter, when
adding or deleting the 2nd line (blank) the colors change and
show the same effect you see.



Dirty workaround: Exchange the /usr/share/vim/vim90/syntax/sh.vim
with an older version from previous OI installations (e.g.,
/usr/share/vim/vim72/syntax/sh.vim). On first impression that still
works fine with vim 9.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] VIM 9: lost shell (read bash) syntax

[Udo Grabowski (IMK)]

On 20/02/2023 17:05, Predrag Zecevic wrote:

On 20.02.2023 16:53, Udo Grabowski (IMK) wrote:

On 20/02/2023 16:49, Udo Grabowski (IMK) wrote:

On 20/02/2023 16:20, Predrag Zecevic via openindiana-discuss wrote:

Hi all,

does anyone has nice .vimrc, which still obey syntax coloring? Especially for
bash...

Recently, vim was upgrade from version 8 to 9:

:; pkg list *editor/vim*
NAME (PUBLISHER) VERSIONIFO
editor/vim 9.0.1300-2023.0.0.0i--
editor/vim/vim-core 9.0.1300-2023.0.0.0i--

Since then, bash syntax coloring is not working with neither .vimrc (old one,
and modified one). Or w/o .vimrc.
Previously, that syntax highlighting could help a lot, when entering shell
commands to point to the syntax error.

Now, it is completely useless...

Any thoughts? Anyone still uses it?


No problem here, with .vimrc

set encoding=utf-8
set term=xterm-color
syntax enable

everything highlights fine, even bash scripts.



You may also need this (one line) :
autocmd Syntax * exec("set
dict+=".$VIMRUNTIME."/syntax/".expand('').".vim")


Thanks,

---8<--
:; cat ~/.vim/vimrc
set encoding=utf-8
set term=xterm-color
syntax enable

autocmd Syntax * exec("set
dict+=".$VIMRUNTIME."/syntax/".expand('').".vim")
---8<--

and still no luck (tried from within *tmux* session and from pure bash shell).
Same version from Ubuntu 22.04 (I had to install it from PPA repo) shows test
bash file properly.

So, it could be something on my machine.
The problem is I have no clue where to start.


Oh, there is definitely a problem with the bash hilighter, when
adding or deleting the 2nd line (blank) the colors change and
show the same effect you see.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] VIM 9: lost shell (read bash) syntax

[Udo Grabowski (IMK)]

On 20/02/2023 16:49, Udo Grabowski (IMK) wrote:

On 20/02/2023 16:20, Predrag Zecevic via openindiana-discuss wrote:

Hi all,

does anyone has nice .vimrc, which still obey syntax coloring? Especially for
bash...

Recently, vim was upgrade from version 8 to 9:

:; pkg list *editor/vim*
NAME (PUBLISHER) VERSIONIFO
editor/vim 9.0.1300-2023.0.0.0i--
editor/vim/vim-core 9.0.1300-2023.0.0.0i--

Since then, bash syntax coloring is not working with neither .vimrc (old one,
and modified one). Or w/o .vimrc.
Previously, that syntax highlighting could help a lot, when entering shell
commands to point to the syntax error.

Now, it is completely useless...

Any thoughts? Anyone still uses it?


No problem here, with .vimrc

set encoding=utf-8
set term=xterm-color
syntax enable

everything highlights fine, even bash scripts.



You may also need this (one line) :
autocmd Syntax * exec("set 
dict+=".$VIMRUNTIME."/syntax/".expand('').".vim")

--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] VIM 9: lost shell (read bash) syntax

[Udo Grabowski (IMK)]

On 20/02/2023 16:20, Predrag Zecevic via openindiana-discuss wrote:

Hi all,

does anyone has nice .vimrc, which still obey syntax coloring? Especially for
bash...

Recently, vim was upgrade from version 8 to 9:

:; pkg list *editor/vim*
NAME (PUBLISHER) VERSIONIFO
editor/vim 9.0.1300-2023.0.0.0i--
editor/vim/vim-core 9.0.1300-2023.0.0.0i--

Since then, bash syntax coloring is not working with neither .vimrc (old one,
and modified one). Or w/o .vimrc.
Previously, that syntax highlighting could help a lot, when entering shell
commands to point to the syntax error.

Now, it is completely useless...

Any thoughts? Anyone still uses it?


No problem here, with .vimrc

set encoding=utf-8
set term=xterm-color
syntax enable

everything highlights fine, even bash scripts.

--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] mate-system-monitor crashes

[Udo Grabowski (IMK)]

On 09/02/2023 15:06, Udo Grabowski (IMK) wrote:

On 08/02/2023 22:07, Tim Mooney via openindiana-discuss wrote:

In regard to: Re: [OpenIndiana-discuss] mate-system-monitor crashes,...:

When I web search this error:


unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type


I see hits for it for many Linux distros too, along with a similar variant
for "directory" monitor type.

I wasn't able to find any definitive fixes, most of the responses
essentially amounted to voodoo.

The Linux systems that experienced this error also had an exception and
a segfault, so segfault may not be unique to OI or Illumos.  It might just
be secondary to the "local file monitor type".


So the primary root cause may be something different.


I think you're correct.



It's possible that glib wasn't compiled with inotify/fam support.
fam is important for NFS-mounted directories. Note this:

# gio monitor -d /
gio: file:///: Unable to find default local file monitor type

# gio monitor -m /a
gio: file:///: Unable to find default local file monitor type




env GIO_USE_FILE_MONITOR=help gio monitor -d /
Supported arguments for GIO_USE_FILE_MONITOR environment variable:

>  (none)<=

gio: file:///: Unable to find default local file monitor type

--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] mate-system-monitor crashes

[Udo Grabowski (IMK)]

On 08/02/2023 22:07, Tim Mooney via openindiana-discuss wrote:

In regard to: Re: [OpenIndiana-discuss] mate-system-monitor crashes,...:

When I web search this error:


unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type


I see hits for it for many Linux distros too, along with a similar variant
for "directory" monitor type.

I wasn't able to find any definitive fixes, most of the responses
essentially amounted to voodoo.

The Linux systems that experienced this error also had an exception and
a segfault, so segfault may not be unique to OI or Illumos.  It might just
be secondary to the "local file monitor type".


So the primary root cause may be something different.


I think you're correct.



It's possible that glib wasn't compiled with inotify/fam support.
fam is important for NFS-mounted directories. Note this:

# gio monitor -d /
gio: file:///: Unable to find default local file monitor type

# gio monitor -m /a
gio: file:///: Unable to find default local file monitor type

--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] mate-system-monitor crashes

[Udo Grabowski (IMK)]

On 08/02/2023 07:02, Stephan Althaus wrote:

On 2/7/23 22:29, Stephan Althaus wrote:

On 2/7/23 22:11, Bill Sommerfeld wrote:

On 2/7/23 13:01, Matthew Yapit wrote:

I recently updated to 2022.10 and I've noticed that mate-system-monitor
causes a core instead of launching.  Has anyone else seen this?  Is there a
fix or one coming in the next update?


It happens for me, too.   Based on the traceback in exception code, it likely
needs to be rebuilt with gcc 10 given the lack of C++ ABI stability.   ldd
shows a mix of libraries:

% ldd =mate-system-monitor  | grep gcc
libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1


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


Hello!

My version of mate-system-monitor shows only the gcc 7 libs,
but maybe you're right anyway..


$ ldd `which mate-system-monitor`  | grep gcc
libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1

$ mate-system-monitor

...

(:4743): glibmm-CRITICAL **: 22:24:52.725:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 4743:mate-system-monitor
- thread# 1 / lwp# 1 -
 7fffaeb69d0b g_type_check_instance_cast () + 1b
 0044977a
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE
() + 11a
 7fff6e3c09b9
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine
() + 149
 7fffae841496 _g_cclosure_marshal_INT__OBJECTv () + 76
 7fffaeb3af95 _g_closure_invoke_va () + 185
 7fffaeb5af6d g_signal_emit_valist () + 39d
 7fffaeb5c05d g_signal_emit () + 7d
 7fffae8a032a g_application_call_command_line () + 7a
 7fffae8a26b1 g_application_real_local_command_line () + 241
 7fff6e3bf4f4 _ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 54
 7fff6e3c05cb
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi
() + 10b
 7fffae8a2845 g_application_run () + 155
 00422b4e main () + 5e
 00421e07 _start_crt () + 87
 00421d68 _start () + 18
...




When i rebuild mate-system-monitor in my environment,
i will get the dependencies to gcc-10 in the build.

The pstack of the core then contains on entry "" which i assume is a
result of the gcc-10 dependencies.

Nevertheless mate-system-monitor does crash in the version (as of my BE:
openindiana-2022:11:23) without gcc-10 deps.

So the primary root cause may be something different.


It's the same crash in the current version. The gcc 7/10 mix results
from other libraries linked, see

# ldd -v `which mate-system-monitor`

With dbx, I get this stack:

(dbx) where -h -l -v
current thread: t@1
=>[1] libc.so.1:_lwp_kill(0x1, 0x6, 0xfe116fe54400, 0x0, 0x0, 
0x5fffaeef2cf0), at 0x5fffaed8731a

  [2] libc.so.1:thr_kill(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x5fffaed7dbe0
  [3] libc.so.1:raise(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x5fffaed1b26e
  [4] libc.so.1:abort(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x5fffaecf4cd8
  [5] libgcc_s.so.1:_Unwind_SetGR(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 
0x5fffaff52b0e
  [6] libstdc++.so.6.0.24:__gxx_personality_v0(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), 
at 0x5fffaeff08c1

  [7] 0x7fffbffde8a0(0x0), at 0x7fffbffde8a0
  [8] libgcc_s.so.1:_Unwind_RaiseException_Phase2(0x0), at 0x5fffae705756
  [9] libgcc_s.so.1:_Unwind_Resume(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 
0x5fffae706126
  [10] 
libgiomm-2.4.so.1.3.0:_ZN3Gio4File17monitor_directoryENS_16FileMonitorFlagsE.cold(0x0, 
0x0, 0x0, 0x0, 0x0, 0x0), at 0x5fffaeb9b9d5
  [11] mate-system-monitor:PrettyTable::PrettyTable(0x0, 0x0, 0x0, 0x0, 0x0, 
0x0), at 0x42f84b
  [12] mate-system-monitor:ProcData::get_instance(0x0, 0x0, 0x0, 0x0, 0x0, 
0x0), at 0x4223e1


or, in mdb (on parent)
> ::stack
libc.so.1`_lwp_kill+0xa()
libc.so.1`raise+0x1e(6)
libc.so.1`abort+0x58()
0x5fffaffb2b0e()
libstdc++.so.6.0.24`__gxx_personality_v0+0xd1()
libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6()
libgcc_s.so.1`_Unwind_Resume+0x126()
0x5fffae39b9d5()
_ZN11PrettyTableC1Ev+0x1db()
_ZN8ProcData12get_instanceEv+0x81()
_ZL16procman_data_newP10_GSettings+0x1c()
_ZN10ProcmanApp10on_startupEv+0x4d()
libgiomm-2.4.so.1.3.0`_ZN3Gio17Application_Class16startup_callbackEP13_GApplication+0xc5()
libgobject-2.0.so.0.7400.5`_g_closure_invoke_va+0x188()
libgobject-2.0.so.0.7400.5`g_signal_emit_valist+0xd59()
libgobject-2.0.so.0.7400.5`g_signal_emit+0x7d()
libgio-2.0.so.0.7400.5`g_application_register+0x122()

Re: [OpenIndiana-discuss] TLS Alerts and status mail problem from OpenIndiana

[Udo Grabowski (IMK)]

On 23/01/2023 13:26, g...@napp-it.org wrote:

I send TLS alerts and status mails via the following Perl script:
(napp-it menu Jobs > TLS > Test

  use Net::SMTP;
  use Authen::SASL qw(Perl);

  my $smtp = Net::SMTP->new("$server",
  SSL => 1,
  #Port => 587,
  Debug => 1,
  Hello => "smtp.gmail.com",
  Timeout => "30",) || die("could not connect to smtp-server");

  $smtp->auth("$user","$pw");

  

  $smtp->mail($from);

  $smtp->to($to);
  $smtp->data();
  $smtp->datasend("From: $from\n");
  $smtp->datasend("To: $to\n");

  $smtp->datasend("Subject: Test Email\n");
  $smtp->datasend("\n");
  $smtp->datasend("This is a test email sent over TLS with the STARTTLS
extension.\n");
  $smtp->dataend();
  $smtp->quit;


The needed modules are installed via (accepting setup defaults))

perl -MCPAN -e shell
install CPAN
reload cpan
notest install Net::SSLeay
notest install IO::Socket::SSL
notest install Net::SMTP::TLS
notest install Authen::SASL
exit


When I try to send (ex to smtp.gmail.com) I get the following error(with newest
IO::Socket::SSL):
*To use SSL please install IO::Socket::SSL with version>=2.007 at
/usr/perl5/5.36/lib/Net/SMTP.pm line 68.*


btw
It works on OmniOS (Perl 5.36) and Solaris 11.4.
Maybe the in OI included Net::SMTP is the problem?


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


On a current, updated system it's already > 2.007:

package IO::Socket::SSL;
our $VERSION = '2.080';

# pkg list library/perl-5/io-socket-ssl-536
library/perl-5/io-socket-ssl-536  2.80-2023.0.0.0i--

And this test (which is inside Net:SMTP) does not give a message:

# perl -MIO::Socket::SSL
my $ssl_class = eval {
  require IO::Socket::SSL;
  # first version with default CA on most platforms
  no warnings 'numeric';
  IO::Socket::SSL->VERSION(2.007);
} && 'IO::Socket::SSL';

my $nossl_warn = !$ssl_class &&
  'To use SSL please install IO::Socket::SSL with version>=2.007';

--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] GIMP issues loading jpg and png

[Udo Grabowski (IMK)]

On 17/01/2023 07:32, russell wrote:

...
GIMP Message

Plug-in crashed: "file-jpeg"
(/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg)
...

GIMP Message

...
Plug-in crashed: "file-png"
(/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png)
...

Has anyone else noticed this?



Yes, same problem here. Both plugins crash with a segfault, while
a gif-file loads without problems:

ts(~) gimp
GIMP-Message: Some fonts failed to load:
- /usr/share/gimp/2.0/fonts/

Plug-in "gtkam-gimp"
(/usr/lib/amd64/gimp/2.0/plug-ins/gtkam-gimp) is installing procedure 
"gtkam-capture" with a full menu path "/File/Acquire/Capture 
from Camera..." as menu label, this deprecated and will be an error in 
GIMP 3.0

Plug-in "gtkam-gimp"
(/usr/lib/amd64/gimp/2.0/plug-ins/gtkam-gimp) is installing procedure 
"gtkam-load" with a full menu path "/File/Acquire/Load from 
Camera..." as menu label, this deprecated and will be an error in GIMP 3.0
/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error: 
Segmentation Fault
/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
Segmentation Fault
/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
Segmentation Fault
/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
Segmentation Fault
/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error: 
Segmentation Fault
/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error: 
Segmentation Fault
/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
Segmentation Fault
/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
Segmentation Fault
/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
Segmentation Fault
gimp: GEGL-WARNING: 
(../../gegl-0.4.40/gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy: 
runtime check failed: (g_queue_is_empty (_queue))

eEeek! 14 GeglBuffers leaked
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] cups does not work any more

[Udo Grabowski (IMK)]

On 11/01/2023 15:28, russell wrote:

Hi

Just activated the BE created on the 30th December 2022 and
svc:/application/cups/scheduler:default is running and CUPS is accessible on
http://127.0.0.1:631/, this is not the case on the BE created on the 1st January
2023. So from my perspective the issue is a result of the changes that took
place between

oihipster-20221203 NR /  165.18G static 2022-12-30 18:46
oihipster-20230101 -  -  886.55M static 2023-01-01 12:31

Russell



While updating currently, I see:
...
Editable files to change:
  Update:
etc/acct/holidays
etc/cups/cups-files.conf
etc/gnu/a2ps-site.cfg
etc/motd
kernel/drv/dca.conf
kernel/drv/rpcib.conf
...
So either something changed in cups-files.conf or has to be changed
there.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] Nvidia 515 problem

[Udo Grabowski (IMK)]

On 09/11/2022 13:04, Stephan Althaus wrote:

On 11/9/22 13:02, Udo Grabowski (IMK) wrote:



On 09/11/2022 12:22, Udo Grabowski (IMK) wrote:



On 09/11/2022 12:14, Udo Grabowski (IMK) wrote:



On 09/11/2022 12:08, Stephan Althaus wrote:

On 11/9/22 11:32, Marcel Telka wrote:

On Wed, Nov 09, 2022 at 11:22:01AM +0100, Udo Grabowski (IMK) wrote:


On 09/11/2022 10:21, Stephan Althaus wrote:

On 11/9/22 10:15, Marcel Telka wrote:

On Wed, Nov 09, 2022 at 08:44:58AM +0100, Stephan Althaus wrote:

Hello!

Yesterday i tried to use nvidia driver version 515 with my 
M1200M,

but got an error in the Xorg.0.log:


[   234.097] (II) Loading sub module "glxserver_nvidia"
[   234.097] (II) LoadModule: "glxserver_nvidia"
[   234.098] (WW) Warning, couldn't open module glxserver_nvidia
[   234.098] (II) UnloadModule: "glxserver_nvidia"
[   234.098] (II) Unloading glxserver_nvidia
[   234.098] (EE) NVIDIA: Failed to load module
"glxserver_nvidia" (module
does not exist, 0)
[   234.098] (EE) NVIDIA(0): Failed to initialize the GLX 
module; please

check in your X
[   234.098] (EE) NVIDIA(0): log file that the GLX module 
has been

loaded in your X
[   234.098] (EE) NVIDIA(0): server, and that the module is
the NVIDIA
GLX module.  If
[   234.098] (EE) NVIDIA(0): you continue to encounter
problems, Please
try
[   234.098] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
[   234.098] (II) NVIDIA: The X server does not support PRIME 
Render

Offload.
[   234.098] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA
graphics
device!
[   234.098] (EE) NVIDIA(0): Failing initialization of X screen
[   234.098] (II) UnloadModule: "nvidia"

i do not find glxserver_nvidia in the running version 470:

$ grep -i glx /var/log/Xorg.0.log
[    90.930] (II) LoadModule: "glx"
[    90.932] (II) Loading
/usr/lib/xorg/modules/extensions/amd64/libglx.so
[    90.986] (II) Module glx: vendor="NVIDIA Corporation"
[    90.986] (II) NVIDIA GLX Module  470.141.03 Thu Jun 30 
18:38:53 UTC

2022
[    93.742] (II) Initializing extension GLX
[    93.742] (II) Indirect GLX disabled.

Does anyone has a hint on how to solve this?
There is no '*glxserver_nvidia*' file in the Solaris driver 
distribution

https://us.download.nvidia.com/solaris/515.76/NVIDIA-Solaris-x86-515.76.run
so I'm not sure why they expect such file (module) to exist. 
Maybe this
is a bug in their package?  Either they forgot to add the 
module into
the package, or they mistakenly require it when they shouldn't? 
Maybe

you could try to contact NVIDIA.


Regards.


Hello!

Looking a bit around i think its the GLX module that is not 
"NVIDIA"


[   234.053] (II) LoadModule: "glx"
[   234.055] (II) Loading 
/usr/lib/xorg/modules/extensions/amd64/libglx.so

[   234.071] (II) Module glx: vendor="X.Org Foundation"
[   234.071]     compiled for 1.19.7, module version = 1.0.0
[   234.071]     ABI class: X.Org Server Extension, version 10.0

and the glxserver is a method within that or something similar..
...

# nm -D
NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep
-i glx

[6] |    14550384|  24|OBJT |GLOB 
|0    |22

|glxserver_nvidiaModuleData

That entrypoint is not present in , e.g., 295.40 . So probably a
packaging error by NVIDIA.

I thought initially the same, but:

$ /usr/bin/nm -D 
nvidia-470/NVIDIA-Solaris-x86-470.141.03/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx

nvidia-470/NVIDIA-Solaris-x86-470.141.03/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1:
[55]    |    10124656|  35|FUNC |GLOB |0 
|12 |__glXNvHandShake
[60]    |    14546160|  24|OBJT |GLOB |0 
|22 |glxModuleData
[7] |    14546032|  24|OBJT |GLOB |0 
|22 |glxserver_nvidiaModuleData
$ /usr/bin/nm -D 
nvidia/NVIDIA-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx

nvidia/NVIDIA-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1:
[55]    |    10128960|  35|FUNC |GLOB |0 
|12 |__glXNvHandShake
[61]    |    14550512|  24|OBJT |GLOB |0 
|22 |glxModuleData
[6] |    14550384|  24|OBJT |GLOB |0 
|22 |glxserver_nvidiaModuleData

$

and 470.141.03 seems to work okay (at least this is my 
understanding from OP).



470 works. From the running machine with 470 i follow the GLX 
module from Xorg.0.log like this:


$ grep -i glx /var/log/Xorg.0.log
[    90.930] (II) LoadModule: "glx"
[    90.932] (II) Loading 
/usr/lib/xorg/modules/extensions/amd64/libglx.so

[    90.986] (II) Module glx: vendor="NVIDIA Corporation"
[    90.986] (II) NVIDIA GLX Module  470.141.03  Thu Jun 30 
18:38:53 UTC 2022

[    93.742] (II)

Re: [OpenIndiana-discuss] Nvidia 515 problem

[Udo Grabowski (IMK)]

On 09/11/2022 12:22, Udo Grabowski (IMK) wrote:



On 09/11/2022 12:14, Udo Grabowski (IMK) wrote:



On 09/11/2022 12:08, Stephan Althaus wrote:

On 11/9/22 11:32, Marcel Telka wrote:

On Wed, Nov 09, 2022 at 11:22:01AM +0100, Udo Grabowski (IMK) wrote:


On 09/11/2022 10:21, Stephan Althaus wrote:

On 11/9/22 10:15, Marcel Telka wrote:

On Wed, Nov 09, 2022 at 08:44:58AM +0100, Stephan Althaus wrote:

Hello!

Yesterday i tried to use nvidia driver version 515 with my M1200M,
but got an error in the Xorg.0.log:


[   234.097] (II) Loading sub module "glxserver_nvidia"
[   234.097] (II) LoadModule: "glxserver_nvidia"
[   234.098] (WW) Warning, couldn't open module glxserver_nvidia
[   234.098] (II) UnloadModule: "glxserver_nvidia"
[   234.098] (II) Unloading glxserver_nvidia
[   234.098] (EE) NVIDIA: Failed to load module
"glxserver_nvidia" (module
does not exist, 0)
[   234.098] (EE) NVIDIA(0): Failed to initialize the GLX 
module; please

check in your X
[   234.098] (EE) NVIDIA(0): log file that the GLX module 
has been

loaded in your X
[   234.098] (EE) NVIDIA(0): server, and that the module is
the NVIDIA
GLX module.  If
[   234.098] (EE) NVIDIA(0): you continue to encounter
problems, Please
try
[   234.098] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
[   234.098] (II) NVIDIA: The X server does not support PRIME 
Render

Offload.
[   234.098] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA
graphics
device!
[   234.098] (EE) NVIDIA(0): Failing initialization of X screen
[   234.098] (II) UnloadModule: "nvidia"

i do not find glxserver_nvidia in the running version 470:

$ grep -i glx /var/log/Xorg.0.log
[    90.930] (II) LoadModule: "glx"
[    90.932] (II) Loading
/usr/lib/xorg/modules/extensions/amd64/libglx.so
[    90.986] (II) Module glx: vendor="NVIDIA Corporation"
[    90.986] (II) NVIDIA GLX Module  470.141.03  Thu Jun 30 
18:38:53 UTC

2022
[    93.742] (II) Initializing extension GLX
[    93.742] (II) Indirect GLX disabled.

Does anyone has a hint on how to solve this?
There is no '*glxserver_nvidia*' file in the Solaris driver 
distribution

https://us.download.nvidia.com/solaris/515.76/NVIDIA-Solaris-x86-515.76.run
so I'm not sure why they expect such file (module) to exist. 
Maybe this
is a bug in their package?  Either they forgot to add the module 
into
the package, or they mistakenly require it when they shouldn't? 
Maybe

you could try to contact NVIDIA.


Regards.


Hello!

Looking a bit around i think its the GLX module that is not "NVIDIA"

[   234.053] (II) LoadModule: "glx"
[   234.055] (II) Loading 
/usr/lib/xorg/modules/extensions/amd64/libglx.so

[   234.071] (II) Module glx: vendor="X.Org Foundation"
[   234.071]     compiled for 1.19.7, module version = 1.0.0
[   234.071]     ABI class: X.Org Server Extension, version 10.0

and the glxserver is a method within that or something similar..
...

# nm -D
NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep
-i glx

[6] |    14550384|  24|OBJT |GLOB |0
|22

|glxserver_nvidiaModuleData

That entrypoint is not present in , e.g., 295.40 . So probably a
packaging error by NVIDIA.

I thought initially the same, but:

$ /usr/bin/nm -D 
nvidia-470/NVIDIA-Solaris-x86-470.141.03/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx

nvidia-470/NVIDIA-Solaris-x86-470.141.03/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1:
[55]    |    10124656|  35|FUNC |GLOB |0 
|12 |__glXNvHandShake
[60]    |    14546160|  24|OBJT |GLOB |0 
|22 |glxModuleData
[7] |    14546032|  24|OBJT |GLOB |0 
|22 |glxserver_nvidiaModuleData
$ /usr/bin/nm -D 
nvidia/NVIDIA-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx

nvidia/NVIDIA-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1:
[55]    |    10128960|  35|FUNC |GLOB |0 
|12 |__glXNvHandShake
[61]    |    14550512|  24|OBJT |GLOB |0 
|22 |glxModuleData
[6] |    14550384|  24|OBJT |GLOB |0 
|22 |glxserver_nvidiaModuleData

$

and 470.141.03 seems to work okay (at least this is my understanding 
from OP).



470 works. From the running machine with 470 i follow the GLX module 
from Xorg.0.log like this:


$ grep -i glx /var/log/Xorg.0.log
[    90.930] (II) LoadModule: "glx"
[    90.932] (II) Loading 
/usr/lib/xorg/modules/extensions/amd64/libglx.so

[    90.986] (II) Module glx: vendor="NVIDIA Corporation"
[    90.986] (II) NVIDIA GLX Module  470.141.03  Thu Jun 30 18:38:53 
UTC 2022

[    93.742] (II) Initializing extension GLX
[    93.742] (II) Indirect GLX disabled.
,,,


Which shows the corre

Re: [OpenIndiana-discuss] Nvidia 515 problem

[Udo Grabowski (IMK)]

On 09/11/2022 12:14, Udo Grabowski (IMK) wrote:



On 09/11/2022 12:08, Stephan Althaus wrote:

On 11/9/22 11:32, Marcel Telka wrote:

On Wed, Nov 09, 2022 at 11:22:01AM +0100, Udo Grabowski (IMK) wrote:


On 09/11/2022 10:21, Stephan Althaus wrote:

On 11/9/22 10:15, Marcel Telka wrote:

On Wed, Nov 09, 2022 at 08:44:58AM +0100, Stephan Althaus wrote:

Hello!

Yesterday i tried to use nvidia driver version 515 with my M1200M,
but got an error in the Xorg.0.log:


[   234.097] (II) Loading sub module "glxserver_nvidia"
[   234.097] (II) LoadModule: "glxserver_nvidia"
[   234.098] (WW) Warning, couldn't open module glxserver_nvidia
[   234.098] (II) UnloadModule: "glxserver_nvidia"
[   234.098] (II) Unloading glxserver_nvidia
[   234.098] (EE) NVIDIA: Failed to load module
"glxserver_nvidia" (module
does not exist, 0)
[   234.098] (EE) NVIDIA(0): Failed to initialize the GLX module; 
please

check in your X
[   234.098] (EE) NVIDIA(0): log file that the GLX module has 
been

loaded in your X
[   234.098] (EE) NVIDIA(0): server, and that the module is
the NVIDIA
GLX module.  If
[   234.098] (EE) NVIDIA(0): you continue to encounter
problems, Please
try
[   234.098] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
[   234.098] (II) NVIDIA: The X server does not support PRIME Render
Offload.
[   234.098] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA
graphics
device!
[   234.098] (EE) NVIDIA(0): Failing initialization of X screen
[   234.098] (II) UnloadModule: "nvidia"

i do not find glxserver_nvidia in the running version 470:

$ grep -i glx /var/log/Xorg.0.log
[    90.930] (II) LoadModule: "glx"
[    90.932] (II) Loading
/usr/lib/xorg/modules/extensions/amd64/libglx.so
[    90.986] (II) Module glx: vendor="NVIDIA Corporation"
[    90.986] (II) NVIDIA GLX Module  470.141.03  Thu Jun 30 
18:38:53 UTC

2022
[    93.742] (II) Initializing extension GLX
[    93.742] (II) Indirect GLX disabled.

Does anyone has a hint on how to solve this?
There is no '*glxserver_nvidia*' file in the Solaris driver 
distribution

https://us.download.nvidia.com/solaris/515.76/NVIDIA-Solaris-x86-515.76.run
so I'm not sure why they expect such file (module) to exist.  
Maybe this

is a bug in their package?  Either they forgot to add the module into
the package, or they mistakenly require it when they shouldn't?  
Maybe

you could try to contact NVIDIA.


Regards.


Hello!

Looking a bit around i think its the GLX module that is not "NVIDIA"

[   234.053] (II) LoadModule: "glx"
[   234.055] (II) Loading 
/usr/lib/xorg/modules/extensions/amd64/libglx.so

[   234.071] (II) Module glx: vendor="X.Org Foundation"
[   234.071]     compiled for 1.19.7, module version = 1.0.0
[   234.071]     ABI class: X.Org Server Extension, version 10.0

and the glxserver is a method within that or something similar..
...

# nm -D
NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep
-i glx

[6] |    14550384|  24|OBJT |GLOB |0    |22
|glxserver_nvidiaModuleData

That entrypoint is not present in , e.g., 295.40 . So probably a
packaging error by NVIDIA.

I thought initially the same, but:

$ /usr/bin/nm -D 
nvidia-470/NVIDIA-Solaris-x86-470.141.03/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx

nvidia-470/NVIDIA-Solaris-x86-470.141.03/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1:
[55]    |    10124656|  35|FUNC |GLOB |0 
|12 |__glXNvHandShake
[60]    |    14546160|  24|OBJT |GLOB |0 
|22 |glxModuleData
[7] |    14546032|  24|OBJT |GLOB |0 
|22 |glxserver_nvidiaModuleData
$ /usr/bin/nm -D 
nvidia/NVIDIA-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx

nvidia/NVIDIA-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1:
[55]    |    10128960|  35|FUNC |GLOB |0 
|12 |__glXNvHandShake
[61]    |    14550512|  24|OBJT |GLOB |0 
|22 |glxModuleData
[6] |    14550384|  24|OBJT |GLOB |0 
|22 |glxserver_nvidiaModuleData

$

and 470.141.03 seems to work okay (at least this is my understanding 
from OP).



470 works. From the running machine with 470 i follow the GLX module 
from Xorg.0.log like this:


$ grep -i glx /var/log/Xorg.0.log
[    90.930] (II) LoadModule: "glx"
[    90.932] (II) Loading 
/usr/lib/xorg/modules/extensions/amd64/libglx.so

[    90.986] (II) Module glx: vendor="NVIDIA Corporation"
[    90.986] (II) NVIDIA GLX Module  470.141.03  Thu Jun 30 18:38:53 
UTC 2022

[    93.742] (II) Initializing extension GLX
[    93.742] (II) Indirect GLX disabled.
,,,


Which shows the correct vendo

Re: [OpenIndiana-discuss] Nvidia 515 problem

[Udo Grabowski (IMK)]

On 09/11/2022 12:08, Stephan Althaus wrote:

On 11/9/22 11:32, Marcel Telka wrote:

On Wed, Nov 09, 2022 at 11:22:01AM +0100, Udo Grabowski (IMK) wrote:


On 09/11/2022 10:21, Stephan Althaus wrote:

On 11/9/22 10:15, Marcel Telka wrote:

On Wed, Nov 09, 2022 at 08:44:58AM +0100, Stephan Althaus wrote:

Hello!

Yesterday i tried to use nvidia driver version 515 with my M1200M,
but got an error in the Xorg.0.log:


[   234.097] (II) Loading sub module "glxserver_nvidia"
[   234.097] (II) LoadModule: "glxserver_nvidia"
[   234.098] (WW) Warning, couldn't open module glxserver_nvidia
[   234.098] (II) UnloadModule: "glxserver_nvidia"
[   234.098] (II) Unloading glxserver_nvidia
[   234.098] (EE) NVIDIA: Failed to load module
"glxserver_nvidia" (module
does not exist, 0)
[   234.098] (EE) NVIDIA(0): Failed to initialize the GLX module; 
please

check in your X
[   234.098] (EE) NVIDIA(0): log file that the GLX module has 
been

loaded in your X
[   234.098] (EE) NVIDIA(0): server, and that the module is
the NVIDIA
GLX module.  If
[   234.098] (EE) NVIDIA(0): you continue to encounter
problems, Please
try
[   234.098] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
[   234.098] (II) NVIDIA: The X server does not support PRIME Render
Offload.
[   234.098] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA
graphics
device!
[   234.098] (EE) NVIDIA(0): Failing initialization of X screen
[   234.098] (II) UnloadModule: "nvidia"

i do not find glxserver_nvidia in the running version 470:

$ grep -i glx /var/log/Xorg.0.log
[    90.930] (II) LoadModule: "glx"
[    90.932] (II) Loading
/usr/lib/xorg/modules/extensions/amd64/libglx.so
[    90.986] (II) Module glx: vendor="NVIDIA Corporation"
[    90.986] (II) NVIDIA GLX Module  470.141.03  Thu Jun 30 
18:38:53 UTC

2022
[    93.742] (II) Initializing extension GLX
[    93.742] (II) Indirect GLX disabled.

Does anyone has a hint on how to solve this?
There is no '*glxserver_nvidia*' file in the Solaris driver 
distribution

https://us.download.nvidia.com/solaris/515.76/NVIDIA-Solaris-x86-515.76.run
so I'm not sure why they expect such file (module) to exist.  Maybe 
this

is a bug in their package?  Either they forgot to add the module into
the package, or they mistakenly require it when they shouldn't?  Maybe
you could try to contact NVIDIA.


Regards.


Hello!

Looking a bit around i think its the GLX module that is not "NVIDIA"

[   234.053] (II) LoadModule: "glx"
[   234.055] (II) Loading 
/usr/lib/xorg/modules/extensions/amd64/libglx.so

[   234.071] (II) Module glx: vendor="X.Org Foundation"
[   234.071]     compiled for 1.19.7, module version = 1.0.0
[   234.071]     ABI class: X.Org Server Extension, version 10.0

and the glxserver is a method within that or something similar..
...

# nm -D
NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep
-i glx

[6] |    14550384|  24|OBJT |GLOB |0    |22
|glxserver_nvidiaModuleData

That entrypoint is not present in , e.g., 295.40 . So probably a
packaging error by NVIDIA.

I thought initially the same, but:

$ /usr/bin/nm -D 
nvidia-470/NVIDIA-Solaris-x86-470.141.03/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx

nvidia-470/NVIDIA-Solaris-x86-470.141.03/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1:
[55]    |    10124656|  35|FUNC |GLOB |0
|12 |__glXNvHandShake
[60]    |    14546160|  24|OBJT |GLOB |0
|22 |glxModuleData
[7] |    14546032|  24|OBJT |GLOB |0
|22 |glxserver_nvidiaModuleData
$ /usr/bin/nm -D 
nvidia/NVIDIA-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep -i glx

nvidia/NVIDIA-Solaris-x86-515.76/NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1:
[55]    |    10128960|  35|FUNC |GLOB |0
|12 |__glXNvHandShake
[61]    |    14550512|  24|OBJT |GLOB |0
|22 |glxModuleData
[6] |    14550384|  24|OBJT |GLOB |0
|22 |glxserver_nvidiaModuleData

$

and 470.141.03 seems to work okay (at least this is my understanding 
from OP).



470 works. From the running machine with 470 i follow the GLX module 
from Xorg.0.log like this:


$ grep -i glx /var/log/Xorg.0.log
[    90.930] (II) LoadModule: "glx"
[    90.932] (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so
[    90.986] (II) Module glx: vendor="NVIDIA Corporation"
[    90.986] (II) NVIDIA GLX Module  470.141.03  Thu Jun 30 18:38:53 UTC 
2022

[    93.742] (II) Initializing extension GLX
[    93.742] (II) Indirect GLX disabled.

$ ls -l /usr/lib/xorg/modules/extensions/amd64/libglx.so
lrwxrwxrwx   1 root root  55 Apr  9  2018 
/usr/li

Re: [OpenIndiana-discuss] Nvidia 515 problem

[Udo Grabowski (IMK)]

On 09/11/2022 10:21, Stephan Althaus wrote:

On 11/9/22 10:15, Marcel Telka wrote:

On Wed, Nov 09, 2022 at 08:44:58AM +0100, Stephan Althaus wrote:

Hello!

Yesterday i tried to use nvidia driver version 515 with my M1200M,
but got an error in the Xorg.0.log:


[   234.097] (II) Loading sub module "glxserver_nvidia"
[   234.097] (II) LoadModule: "glxserver_nvidia"
[   234.098] (WW) Warning, couldn't open module glxserver_nvidia
[   234.098] (II) UnloadModule: "glxserver_nvidia"
[   234.098] (II) Unloading glxserver_nvidia
[   234.098] (EE) NVIDIA: Failed to load module "glxserver_nvidia" 
(module

does not exist, 0)
[   234.098] (EE) NVIDIA(0): Failed to initialize the GLX module; please
check in your X
[   234.098] (EE) NVIDIA(0): log file that the GLX module has been
loaded in your X
[   234.098] (EE) NVIDIA(0): server, and that the module is the 
NVIDIA

GLX module.  If
[   234.098] (EE) NVIDIA(0): you continue to encounter problems, 
Please

try
[   234.098] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
[   234.098] (II) NVIDIA: The X server does not support PRIME Render
Offload.
[   234.098] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA 
graphics

device!
[   234.098] (EE) NVIDIA(0): Failing initialization of X screen
[   234.098] (II) UnloadModule: "nvidia"

i do not find glxserver_nvidia in the running version 470:

$ grep -i glx /var/log/Xorg.0.log
[    90.930] (II) LoadModule: "glx"
[    90.932] (II) Loading 
/usr/lib/xorg/modules/extensions/amd64/libglx.so

[    90.986] (II) Module glx: vendor="NVIDIA Corporation"
[    90.986] (II) NVIDIA GLX Module  470.141.03  Thu Jun 30 18:38:53 UTC
2022
[    93.742] (II) Initializing extension GLX
[    93.742] (II) Indirect GLX disabled.

Does anyone has a hint on how to solve this?

There is no '*glxserver_nvidia*' file in the Solaris driver distribution
https://us.download.nvidia.com/solaris/515.76/NVIDIA-Solaris-x86-515.76.run
so I'm not sure why they expect such file (module) to exist.  Maybe this
is a bug in their package?  Either they forgot to add the module into
the package, or they mistakenly require it when they shouldn't?  Maybe
you could try to contact NVIDIA.


Regards.


Hello!

Looking a bit around i think its the GLX module that is not "NVIDIA"

[   234.053] (II) LoadModule: "glx"
[   234.055] (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so
[   234.071] (II) Module glx: vendor="X.Org Foundation"
[   234.071]     compiled for 1.19.7, module version = 1.0.0
[   234.071]     ABI class: X.Org Server Extension, version 10.0

and the glxserver is a method within that or something similar..
...


# nm -D 
NVDAgraphics/reloc/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1|fgrep 
-i glx


[6] |14550384|  24|OBJT |GLOB |0|22 
   |glxserver_nvidiaModuleData


That entrypoint is not present in , e.g., 295.40 . So probably a
packaging error by NVIDIA.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Nvidia 515 problem

[Udo Grabowski (IMK)]

On 09/11/2022 10:21, Stephan Althaus wrote:

On 11/9/22 10:15, Marcel Telka wrote:

On Wed, Nov 09, 2022 at 08:44:58AM +0100, Stephan Althaus wrote:

Hello!

Yesterday i tried to use nvidia driver version 515 with my M1200M,
but got an error in the Xorg.0.log:


[   234.097] (II) Loading sub module "glxserver_nvidia"
[   234.097] (II) LoadModule: "glxserver_nvidia"
[   234.098] (WW) Warning, couldn't open module glxserver_nvidia
[   234.098] (II) UnloadModule: "glxserver_nvidia"
[   234.098] (II) Unloading glxserver_nvidia
[   234.098] (EE) NVIDIA: Failed to load module "glxserver_nvidia" 
(module

does not exist, 0)
[   234.098] (EE) NVIDIA(0): Failed to initialize the GLX module; please
check in your X
[   234.098] (EE) NVIDIA(0): log file that the GLX module has been
loaded in your X
[   234.098] (EE) NVIDIA(0): server, and that the module is the 
NVIDIA

GLX module.  If
[   234.098] (EE) NVIDIA(0): you continue to encounter problems, 
Please

try
[   234.098] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
[   234.098] (II) NVIDIA: The X server does not support PRIME Render
Offload.
[   234.098] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA 
graphics

device!
[   234.098] (EE) NVIDIA(0): Failing initialization of X screen
[   234.098] (II) UnloadModule: "nvidia"

i do not find glxserver_nvidia in the running version 470:

$ grep -i glx /var/log/Xorg.0.log
[    90.930] (II) LoadModule: "glx"
[    90.932] (II) Loading 
/usr/lib/xorg/modules/extensions/amd64/libglx.so

[    90.986] (II) Module glx: vendor="NVIDIA Corporation"
[    90.986] (II) NVIDIA GLX Module  470.141.03  Thu Jun 30 18:38:53 UTC
2022
[    93.742] (II) Initializing extension GLX
[    93.742] (II) Indirect GLX disabled.

Does anyone has a hint on how to solve this?

There is no '*glxserver_nvidia*' file in the Solaris driver distribution
https://us.download.nvidia.com/solaris/515.76/NVIDIA-Solaris-x86-515.76.run
so I'm not sure why they expect such file (module) to exist.  Maybe this
is a bug in their package?  Either they forgot to add the module into
the package, or they mistakenly require it when they shouldn't?  Maybe
you could try to contact NVIDIA.


Regards.


Hello!

Looking a bit around i think its the GLX module that is not "NVIDIA"

[   234.053] (II) LoadModule: "glx"
[   234.055] (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so
[   234.071] (II) Module glx: vendor="X.Org Foundation"
[   234.071]     compiled for 1.19.7, module version = 1.0.0
[   234.071]     ABI class: X.Org Server Extension, version 10.0

and the glxserver is a method within that or something similar..

How to configure Xorg to use a different path for the GLX module is the 
next question to solve..


libglx.so should originate from NVIDIA.This should be the
link hierarchy:
-r-xr-xr-x   1 root bin 520K Sep 22 17:36 
/usr/lib/mesa/modules/extensions/amd64/libglx.so*
lrwxrwxrwx   1 root root  55 Sep 22 16:14 
/usr/lib/xorg/modules/extensions/amd64/libglx.so -> 
../../../../../../var/run/opengl/server/amd64/libglx.so*
lrwxrwxrwx   1 root root  46 Sep 22 16:14 
/usr/lib/xorg/modules/extensions/libglx.so -> 
../../../../../var/run/opengl/server/libglx.so*
lrwxrwxrwx   1 root root  48 Nov  9 10:08 
/var/run/opengl/server/libglx.so -> 
/usr/X11/lib/modules/extensions/NVIDIA/libglx.so*
lrwxrwxrwx   1 root root  48 Nov  9 10:08 
/var/run/opengl/server/amd64/libglx.so -> 
/usr/X11/lib/modules/extensions/NVIDIA/libglx.so*
lrwxrwxrwx   1 root root  11 Sep 22 16:14 
/usr/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so -> libglx.so.1*
-r-xr-xr-x   1 root bin14.3M Sep 22 17:36 
/usr/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so.1*
lrwxrwxrwx   1 root root  11 Sep 22 16:14 
/usr/X11/lib/modules/extensions/NVIDIA/libglx.so -> libglx.so.1*
-r-xr-xr-x   1 root bin9.23M Sep 22 17:36 
/usr/X11/lib/modules/extensions/NVIDIA/libglx.so.1*


And this service should be online (that builds that hierarchy):
# svcs -a|grep opengl
online 10:08:32 svc:/application/opengl/ogl-select:default

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

Re: [OpenIndiana-discuss] Nextcloud client?

[Udo Grabowski (IMK)]

On 18/07/2022 05:12, Leonard Sitongia wrote:

Hello,

I'm new to OpenIndiana. I probably have a few FAQs here, but I don't see the
answers.

First, about me. I was a Unix sysadmin for many years, first with 4.2BSD on a
VAX (when I also bought a Sun 2 for the Observatory where I worked), and later
with many Sun workstation models, including the SunRay thin client. At one time,
I had a deeply-discounted AT PC 7300. That was really cool to have in the
1980s. Every once in a while I try some contemporary BSD, Solaris or System V
derivative.

Back to OpenIndiana.

Is there a searchable archive for this discuss mailing list?



You can search oi-discuss and oi-dev here:




and the illumos discuss and dev lists here:





Is there a NextCloud client?


probably not.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] How to straighten out an /etc/passwd /etc/opasswd mess I've created

[Udo Grabowski (IMK)]

On 31/05/2022 17:53, hput via openindiana-discuss wrote:

Messing around beyond my capabilities I've managed to create a
situation where I cannot add a user:

 useradd  -m reader
UX: useradd: ERROR: Inconsistent password files.  See pwconv(8).

Running `pwconv' seems not to do a thing.

I've jerked around with the files  so much this morning I doubt I could really
recount all I've tried. (/etc/passwd /etc/opasswd /etc/group /etc/ogroup)

I know at one point I renamed /etc/passwd to see is pwconv would
rebuld it... no such thing.

This is oi just updated, running in a vboxvm and even though it
wouldn't be a disaster to just reinstall... I have done a fair bit of
work getting it ready before I became idiotised.

Is there some way to fix this short of reinstall?




In a standard situation, /etc/passwd and shadow should have the
same number of lines, and the same sequence of user IDs.

--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] OI server failed overnight - some help restoring it!

[Udo Grabowski (IMK)]

On 21/04/2022 06:56, Carl Brewer wrote:

...

I've got an OI box that's been running 
for 11 years, totally bombproof.


I would recommend to check the onboard battery (or batteries ?).
Maybe your just loosing the BIOS content each time the server
goes off.


___
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

[Udo Grabowski (IMK)]

On 13/04/2022 21:13, Judah Richardson wrote:

On Wed, Apr 13, 2022 at 2:03 PM Gary Mills  wrote:


On Wed, Apr 13, 2022 at 08:04:40PM +0200, s...@pandora.be wrote:


The documentation


http://docs.openindiana.org/handbook/systems-administration/#configuring-networking

writes:



"While usually server and desktop installations tend to use default
network configurations, laptop users can leverage nwam network
configuations."


That really means: "in an envionment where the network configuration
changes frequently".


Speaking as an experimental user (read: OI is not my daily driver) who
acknowledges OI inherits a lot of internal functionality from a
server/workstation distro (openSolaris): all of this strikes me as
anachronistically(?) complicated for something that should by default
expect to get an IP address lease from any DHCP server on a network to
which it's connected.

Or, put more simply: it assumes a lot of network complexity that isn't
there for most (home) networks.

I'm not necessarily advocating for it to change since I don't have the time
to do it and clearly it seems to work for many people; just making an
observation. I can't think of any other OS I've used (Android, Linux,
Windows, (Free)BSD) for which maintaining a network connection isn't
anything more than connecting an Ethernet cable.

> 

The facts are that server environments can be really involved (and
even Desktops), and NWAM isn't fit for such complications.
E.g., today I had a rather simple task: Copy a network configuration
from one wall connector to another, and our guys from the central
network messed it up... The simple task was: configure one TX wall
outlet to carry two tagged VLANs. Instead, they distributed them
untagged across two connectors. My fixed config (without NWAM)
made at least one connection visible, so that I could diagnose
and recover. NWAM would have messed that up completely as it cannot
(at least to my knowledge) cope with tagged VLANs, leaving the box
disconnected, which is not so funny when you are in home office...
We have a couple of such involved configs due to environmental/hardware
constraints which always happens if you have a larger machine park
with over 100 instances.
So you simply need all those manual knobs and switches that can be
turned to adapt to all these hassles. NWAM probably does its job
for the simple Desktop, but that isn't the right measure to decide
what a OS should provide as configuration tools. Then we could simply
drop in.routed and other seldom used stuff, since almost no one needs
that => please go away and use another OS if so... That's clearly not
the goal.
In fact, when you've worked a couple of decades in that job, you would
find out that you may at least once needed those tools and were happy
to have them.
___
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

[Udo Grabowski (IMK)]

On 13/04/2022 20:04, s...@pandora.be wrote:

- Op 12 apr 2022 om 20:00 schreef John D Groenveld groenv...@acm.org:


svc:/network/routing/route is enabled out of the box with
OI-hipster-text-20211031.iso


I can't reproduce this.

When I install from the OI-hipster-text-20211031.iso it does not enable 
routing/route.


Also my OpenIndiana system (Dell Precision 3640 with 2 NIC, 1 e1000g0 and 1 
igb0)
is not running in.routed, route:default) and is fairly up to date with recent 
OI.

I didn't have to disable in.routed or route:default , by default it was NOT 
enabled.

When I install from the OI-hipster-text-20211031.iso

$ cat OI-hipster-text-20211031.iso.sha256sum
08d938497dfb39ab51da598437cc4cadcad9c936a9371c58520fe8e99431e86d  
OI-hipster-text-20211031.iso

after the install (where I selected "Automatic" for the NIC, a single NIC), I 
login and

routeadm shows : IPV4routing disabled

Udo Grabowski will be pleased to read that :-)



Yeah, indeed !


Can you be more specific please and check the "nwadmadm list" on your server and
/var/sadm/system/logs/install_log.

Maybe there is a specific scenario where indeed route:default is enabled,
as also confirmed in https://www.illumos.org/issues/14006

In fact the bug report 14006 refers to the manpage of routeadm which describes 
some conditions where routing is ENABLED indeed, so there is something that can 
indeed enable route:default accidentally.

However the bug report 14006 does not say this is OpenIndiana specific, it is a 
Illumos bug report possibly for a different distribution ?

However when I test this , I have no /etc/defaultrouter and route:default is 
not enabled.



But what happens if you place an *empty* /etc/defaultrouter there ?


For me on my test system "nwamadm list" shows "ncp Automatic online".

in.routed is not running, routeadm shows all disabled

I mean: the command routeadm after a fresh install of 202110 shows IPv4 and 
IPv6 forwarding and routing disabled.

Note however that the installer has multiple options, so I installed using 1 
NIC here and choose network type 'Automatic'.

Finally to touch a painful issue:   the type 'Automatic' is possible NOT the 
best choice for servers.

The documentation 
http://docs.openindiana.org/handbook/systems-administration/#configuring-networking
writes:

"While usually server and desktop installations tend to use default network 
configurations, laptop users can leverage nwam network configuations."

So that doc positions NWAM as a solution for 'laptop users'.  Opinions may 
differ ...

Regards,
David Stes


___
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] OI Hipster becomes unreachable over network after a certain length of uptime

[Udo Grabowski (IMK)]

On 13/04/2022 16:32, Gary Mills wrote:

On Tue, Apr 12, 2022 at 10:42:53PM -0700, Joshua M. Clulow via 
openindiana-discuss wrote:


As suggested in the ticket, I would:

 # routeadm -d ipv4-routing -u

The "svc:/network/routing/route:default" instance should then be
disabled, unlike in your output above.


I have two different routing configurations.  The first is for a
system that acts as a NAT router using ipfilter.  /etc/defaultrouter
does not exist.  It has two ethernet interfaces.  One connects to my
cable modem.  The other goes to my private network, through a switch:

 $ routeadm
   Configuration   Current  Current
  Option   ConfigurationSystem State
 ---
IPv4 routing   disabled disabled
IPv6 routing   disabled disabled
 IPv4 forwarding   enabled  enabled
 IPv6 forwarding   disabled disabled
 ...

The "IPv4 forwarding" setting is required by ipfilter.

The other configuration is for a typical system on my private
network, using all the defaults, with a single ethernet:

 $ routeadm
   Configuration   Current  Current
  Option   ConfigurationSystem State
 ---
IPv4 routing   enabled  enabled
IPv6 routing   disabled disabled
 IPv4 forwarding   disabled disabled
 IPv6 forwarding   disabled disabled
 ...
 


This is what a typical off-the-shelf client machine should look like:

# routeadm
  Configuration   Current  Current
 Option   ConfigurationSystem State
---
   IPv4 routing   disabled disabled
   IPv6 routing   disabled disabled
IPv4 forwarding   disabled disabled
IPv6 forwarding   disabled disabled

   Routing services   "route:default ripng:default"

Routing daemons:

  STATE   FMRI
   disabled   svc:/network/routing/legacy-routing:ipv4
   disabled   svc:/network/routing/legacy-routing:ipv6
   disabled   svc:/network/routing/rdisc:default
   disabled   svc:/network/routing/route:default
   disabled   svc:/network/routing/ripng:default
 online   svc:/network/routing/ndp:default
___
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

[Udo Grabowski (IMK)]

On 12/04/2022 21:21, Udo Grabowski (IMK) wrote:



On 12/04/2022 21:12, Joshua M. Clulow via openindiana-discuss wrote:
On Tue, 12 Apr 2022 at 11:52, Udo Grabowski (IMK) 
 wrote:

On 12/04/2022 20:42, Bob Friesenhahn wrote:

On Tue, 12 Apr 2022, Judah Richardson wrote:
On Tue, Apr 12, 2022, 13:27 Udo Grabowski (IMK) 


wrote:


On 12/04/2022 20:00, John D Groenveld wrote:

In message , "Udo

Grabowski (IMK)

" writes:

No, it isn't, it's controlled by
/lib/svc/manifest/network/routing/route.xml ,
which is not enabled by default, as practically no machine
in the field is working as a router, you have to specifically
enable the route:default service.


svc:/network/routing/route is enabled out of the box with
OI-hipster-text-20211031.iso

...

...


This is indeed a bug:

 14006 ipv4-routing should not be enabled by default
 https://www.illumos.org/issues/14006

>> 

In principle, the easiest fix is to revert to

in the respective services in /lib/svc/manifest/network/routing/ .
...Hm, probably not *that* easy, routeadm interferes with that based

on the existence of an entry in /etc/defaultrouter (which we've always
set on our machines, so I've never seen this problem).
___
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

[Udo Grabowski (IMK)]

On 12/04/2022 21:12, Joshua M. Clulow via openindiana-discuss wrote:

On Tue, 12 Apr 2022 at 11:52, Udo Grabowski (IMK)  wrote:

On 12/04/2022 20:42, Bob Friesenhahn wrote:

On Tue, 12 Apr 2022, Judah Richardson wrote:

On Tue, Apr 12, 2022, 13:27 Udo Grabowski (IMK) 
wrote:


On 12/04/2022 20:00, John D Groenveld wrote:

In message , "Udo

Grabowski (IMK)

" writes:

No, it isn't, it's controlled by
/lib/svc/manifest/network/routing/route.xml ,
which is not enabled by default, as practically no machine
in the field is working as a router, you have to specifically
enable the route:default service.


svc:/network/routing/route is enabled out of the box with
OI-hipster-text-20211031.iso


Why ?? This hasn't been the case for at least two decades of
Solaris and beyond.


Probably an oversight, I'd guess. As with many such situations, things
that
aren't obviously and critically broken don't get much attention ;)


It is not really an oversight since all computers with a TCP/IP stack
need to deal with some level of routing even if they are not acting as a
gateway.  If there is ever more than one way to get "there" via the L2
network then running a higher-level routing protocol (e.g. RIP) can help
the TCP/IP stack make the right decisions if the involved routers use
the same protocol.  The host might participate in RIP or it might just
act as an observer.

In many cases one or more computers are attached to a shared L2 network
with a single upstream router. In this case, using DHCP to configure the
default route, or static configuration to provide the default route, can
be a good choice. There are other means such as ICMP Router Discovery
Protocol (https://en.wikipedia.org/wiki/ICMP_Router_Discovery_Protocol)
or even ICMP redirects.


I have a few machines with two L2 networks (a.k.a. tagged VPN), and even
those don't require the routing service. In fact, in my over 3 decades
of experience with Sun machines, I only once have seen that the routing
service had to be active. That one case was when I experimented with the
COMSTAR network simulation tools to play with virtual switches and
routers.


Goodness, what a lot of mails!

This is indeed a bug:

 14006 ipv4-routing should not be enabled by default
 https://www.illumos.org/issues/14006

I haven't had time to work on it, but I am happy to talk it through
with people who would like to pick it up and get it fixed!


In principle, the easiest fix is to revert to

in the respective services in /lib/svc/manifest/network/routing/ .
But I've not seen a 202* OI version, I'm still on 2017...
___
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

[Udo Grabowski (IMK)]

On 12/04/2022 20:52, Udo Grabowski (IMK) wrote:

... (a.k.a. tagged VPN) ...

... should be tagged VLAN.

___
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

[Udo Grabowski (IMK)]

On 12/04/2022 20:42, Bob Friesenhahn wrote:

On Tue, 12 Apr 2022, Judah Richardson wrote:


On Tue, Apr 12, 2022, 13:27 Udo Grabowski (IMK) 
wrote:


On 12/04/2022 20:00, John D Groenveld wrote:

In message , "Udo

Grabowski (IMK)

" writes:

No, it isn't, it's controlled by
/lib/svc/manifest/network/routing/route.xml ,
which is not enabled by default, as practically no machine
in the field is working as a router, you have to specifically
enable the route:default service.


svc:/network/routing/route is enabled out of the box with
OI-hipster-text-20211031.iso


Why ?? This hasn't been the case for at least two decades of
Solaris and beyond.


Probably an oversight, I'd guess. As with many such situations, things 
that

aren't obviously and critically broken don't get much attention ;)


It is not really an oversight since all computers with a TCP/IP stack 
need to deal with some level of routing even if they are not acting as a 
gateway.  If there is ever more than one way to get "there" via the L2 
network then running a higher-level routing protocol (e.g. RIP) can help 
the TCP/IP stack make the right decisions if the involved routers use 
the same protocol.  The host might participate in RIP or it might just 
act as an observer.


In many cases one or more computers are attached to a shared L2 network 
with a single upstream router. In this case, using DHCP to configure the 
default route, or static configuration to provide the default route, can 
be a good choice. There are other means such as ICMP Router Discovery 
Protocol (https://en.wikipedia.org/wiki/ICMP_Router_Discovery_Protocol) 
or even ICMP redirects.


I have a few machines with two L2 networks (a.k.a. tagged VPN), and even
those don't require the routing service. In fact, in my over 3 decades
of experience with Sun machines, I only once have seen that the routing
service had to be active. That one case was when I experimented with the
COMSTAR network simulation tools to play with virtual switches and
routers.
___
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

[Udo Grabowski (IMK)]

On 12/04/2022 20:29, Judah Richardson wrote:

On Tue, Apr 12, 2022, 13:27 Udo Grabowski (IMK) 
wrote:


On 12/04/2022 20:00, John D Groenveld wrote:

In message , "Udo

Grabowski (IMK)

" writes:

No, it isn't, it's controlled by
/lib/svc/manifest/network/routing/route.xml ,
which is not enabled by default, as practically no machine
in the field is working as a router, you have to specifically
enable the route:default service.


svc:/network/routing/route is enabled out of the box with
OI-hipster-text-20211031.iso


Why ?? This hasn't been the case for at least two decades of
Solaris and beyond.


Probably an oversight, I'd guess. As with many such situations, things that
aren't obviously and critically broken don't get much attention ;)


In fact, it is critically broken, as a routing service introduces
a whole new security context that can open critical intrusion pathes.

___
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

[Udo Grabowski (IMK)]

On 12/04/2022 20:00, John D Groenveld wrote:

In message , "Udo Grabowski (IMK)
" writes:

No, it isn't, it's controlled by
/lib/svc/manifest/network/routing/route.xml ,
which is not enabled by default, as practically no machine
in the field is working as a router, you have to specifically
enable the route:default service.


svc:/network/routing/route is enabled out of the box with
OI-hipster-text-20211031.iso


Why ?? This hasn't been the case for at least two decades of
Solaris and beyond. That's a wrong move.
___
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

[Udo Grabowski (IMK)]

On 12/04/2022 19:09, Bob Friesenhahn wrote:

On Tue, 12 Apr 2022, s...@pandora.be wrote:



- Op 11 apr 2022 om 15:47 schreef John D Groenveld groenv...@acm.org:


Does disabling in.routed with routeadm(8) prevent your default
route from being disappeared?
https://illumos.org/man/8/routeadm>


I also wonder why this system that becomes unreachable after a a 
certain uptime,

runs 'in.routed'.   And indeed whether disabling in.routed can be done,
or is it (according to the original poster) a requirement for the 
setup that route:default is enabled ?


I think it is the system default to run 'in.routed' 


No, it isn't, it's controlled by
/lib/svc/manifest/network/routing/route.xml ,
which is not enabled by default, as practically no machine
in the field is working as a router, you have to specifically
enable the route:default service.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] missing shared library ?

[Udo Grabowski (IMK)]

On 04/03/2022 14:38, Marc Lobelle wrote:

hello,

I'm trying to use the openindiana pacemaker package, but ldd tells me 
that some programs cannot find a shared library: libpcre2-posix.so.2 
=>   (file not found)


Could anyone tell me in which package I can get it ?


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

Re: [OpenIndiana-discuss] How to tell nwam to use the firewall rules in /etc/ipf/ipf.conf ?

[Udo Grabowski (IMK)]

And this part probably determines if the custom policy is preserved:

#
# IPFilter
#
# If the firewall policy is "custom", simply copy the
# custom_policy_file.  If the firewall policy is "none", "allow" or
# "deny", save the value as "/".  When reverting back to the
# Legacy location, these values will have to be treated as special.
#
# For all configuration files, copy them to the Legacy directory.
# Use the respective properties to remember the original locations
# of the files so that they can be copied back there when NWAM is
# stopped.
#
if service_is_enabled $IPFILTER_FMRI; then
FIREWALL_POLICY=`get_smf_prop $IPFILTER_FMRI \
firewall_config_default/policy`
if [ "$FIREWALL_POLICY" = "custom" ]; then
IPF_CONFIG_FILE=`get_smf_prop $IPFILTER_FMRI \
firewall_config_default/custom_policy_file`
copy_to_legacy_loc $IPF_CONFIG_FILE
else
# save value as /none, /allow, or /deny
IPF_CONFIG_FILE="/$FIREWALL_POLICY"
fi
IPF6_CONFIG_FILE=`get_smf_prop $IPFILTER_FMRI \
config/ipf6_config_file`
        copy_to_legacy_loc $IPF6_CONFIG_FILE


On 28/02/2022 14:22, Udo Grabowski (IMK) wrote:

See /lib/svc/method/net-nwam, it should take the ipfilter-config-file
from the activated IP firewall service:


     # IPFilter, IPsec, and IKE
     ipf_file=`nwam_get_loc_prop Legacy ipfilter-config-file`
     ipf6_file=`nwam_get_loc_prop Legacy ipfilter-v6-config-file`
     ipnat_file=`nwam_get_loc_prop Legacy ipnat-config-file`
     ippool_file=`nwam_get_loc_prop Legacy ippool-config-file`
     ike_file=`nwam_get_loc_prop Legacy ike-config-file`
     pol_file=`nwam_get_loc_prop Legacy ipsecpolicy-config-file`

     if [ -n "$ike_file" ]; then
     copy_from_legacy_loc $ike_file
     set_smf_prop $IPSEC_IKE_FMRI config/config_file $ike_file
     $SVCADM refresh $IPSEC_IKE_FMRI
     $SVCADM enable $IPSEC_IKE_FMRI
     else
     set_smf_prop $IPSEC_IKE_FMRI config/config_file \
     $IPSEC_IKE_DEFAULT_CONFIG_FILE
     $SVCADM disable $IPSEC_IKE_FMRI
     fi
     if [ -n "$pol_file" ]; then
     copy_from_legacy_loc $pol_file
     set_smf_prop $IPSEC_POLICY_FMRI config/config_file 
$pol_file

     $SVCADM refresh $IPSEC_POLICY_FMRI
     $SVCADM enable $IPSEC_POLICY_FMRI
     else
     set_smf_prop $IPSEC_POLICY_FMRI config/config_file \
     $IPSEC_POLICY_DEFAULT_CONFIG_FILE
     $SVCADM disable $IPSEC_POLICY_FMRI
     fi

     refresh_ipf=false
     if [ -n "$ipf_file" ]; then
     # change /none, /allow, and /deny to firewall policy
     if [ "$ipf_file" = "/none" -o "$ipf_file" = "/allow" \
     -o "$ipf_file" = "/deny" ]; then
     policy=`echo "$ipf_file" | $NAWK 'FS="/" { 
print $2 }'`

     set_smf_prop $IPFILTER_FMRI \
     firewall_config_default/policy $policy
     # no need to clear custom_policy_file as it 
isn't "custom"

     else
     copy_from_legacy_loc $ipf_file
     set_smf_prop $IPFILTER_FMRI \
     firewall_config_default/policy "custom"
     set_smf_prop $IPFILTER_FMRI \
     firewall_config_default/custom_policy_file 
$ipf_file

     fi
     refresh_ipf=true
     fi
     if [ -n "$ipf6_file" ]; then
     copy_from_legacy_loc $ipf6_file
     set_smf_prop $IPFILTER_FMRI config/ipf6_config_file 
$ipf6_file

     refresh_ipf=true
     else
     set_smf_prop $IPFILTER_FMRI config/ipf6_config_file \
     $IPF6_DEFAULT_CONFIG_FILE
     fi

On 28/02/2022 12:51, Udo Grabowski (IMK) wrote:



On 28/02/2022 12:44, Udo Grabowski (IMK) wrote:



On 28/02/2022 12:32, Marc Lobelle wrote:

Hello,

I defined firewall rules for ipfilter in /etc/ipf/ipf.conf.

However, I use nwam and, at boot time, nwam wipes out all firewall 
rules and imposes its own: block everything excpt dhcp in the NoNet 
situation and no rules at all when a network interface is active.


The NoNet rules can be replaced by my own rules by copying 
/etc/ipf/ipf.conf in /etc/nwam/loc/NoNet/ipf.conf, but thi

Re: [OpenIndiana-discuss] How to tell nwam to use the firewall rules in /etc/ipf/ipf.conf ?

[Udo Grabowski (IMK)]

See /lib/svc/method/net-nwam, it should take the ipfilter-config-file
from the activated IP firewall service:


# IPFilter, IPsec, and IKE
ipf_file=`nwam_get_loc_prop Legacy ipfilter-config-file`
ipf6_file=`nwam_get_loc_prop Legacy ipfilter-v6-config-file`
ipnat_file=`nwam_get_loc_prop Legacy ipnat-config-file`
ippool_file=`nwam_get_loc_prop Legacy ippool-config-file`
ike_file=`nwam_get_loc_prop Legacy ike-config-file`
pol_file=`nwam_get_loc_prop Legacy ipsecpolicy-config-file`

if [ -n "$ike_file" ]; then
copy_from_legacy_loc $ike_file
set_smf_prop $IPSEC_IKE_FMRI config/config_file $ike_file
$SVCADM refresh $IPSEC_IKE_FMRI
$SVCADM enable $IPSEC_IKE_FMRI
else
set_smf_prop $IPSEC_IKE_FMRI config/config_file \
$IPSEC_IKE_DEFAULT_CONFIG_FILE
$SVCADM disable $IPSEC_IKE_FMRI
fi
if [ -n "$pol_file" ]; then
copy_from_legacy_loc $pol_file
set_smf_prop $IPSEC_POLICY_FMRI config/config_file 
$pol_file

$SVCADM refresh $IPSEC_POLICY_FMRI
$SVCADM enable $IPSEC_POLICY_FMRI
else
set_smf_prop $IPSEC_POLICY_FMRI config/config_file \
$IPSEC_POLICY_DEFAULT_CONFIG_FILE
$SVCADM disable $IPSEC_POLICY_FMRI
fi

refresh_ipf=false
if [ -n "$ipf_file" ]; then
# change /none, /allow, and /deny to firewall policy
if [ "$ipf_file" = "/none" -o "$ipf_file" = "/allow" \
-o "$ipf_file" = "/deny" ]; then
policy=`echo "$ipf_file" | $NAWK 'FS="/" { 
print $2 }'`

set_smf_prop $IPFILTER_FMRI \
firewall_config_default/policy $policy
# no need to clear custom_policy_file as it 
isn't "custom"

else
copy_from_legacy_loc $ipf_file
set_smf_prop $IPFILTER_FMRI \
firewall_config_default/policy "custom"
set_smf_prop $IPFILTER_FMRI \
firewall_config_default/custom_policy_file 
$ipf_file

fi
refresh_ipf=true
fi
if [ -n "$ipf6_file" ]; then
copy_from_legacy_loc $ipf6_file
set_smf_prop $IPFILTER_FMRI config/ipf6_config_file 
$ipf6_file

refresh_ipf=true
else
        set_smf_prop $IPFILTER_FMRI config/ipf6_config_file \
        $IPF6_DEFAULT_CONFIG_FILE
fi

On 28/02/2022 12:51, Udo Grabowski (IMK) wrote:



On 28/02/2022 12:44, Udo Grabowski (IMK) wrote:



On 28/02/2022 12:32, Marc Lobelle wrote:

Hello,

I defined firewall rules for ipfilter in /etc/ipf/ipf.conf.

However, I use nwam and, at boot time, nwam wipes out all firewall 
rules and imposes its own: block everything excpt dhcp in the NoNet 
situation and no rules at all when a network interface is active.


The NoNet rules can be replaced by my own rules by copying 
/etc/ipf/ipf.conf in /etc/nwam/loc/NoNet/ipf.conf, but this is 
useless because it is replaced by nothing at all when a network 
interface is activated. Therefore I removed this change.


I tried to add to /etc/nwam/loc/create_loc_auto a line "set 
ipfilter-config-file=/etc/ipf/ipf.conf" similar to the line in 
create_loc_NoNet: "set 
ipfilter-config-file=/etc/nwam/loc/NoNet/ipf.conf"


But this does not change the behaviour.

How can I tell nwam to use ipf.conf ?

Thanks for your help.

 >  ...

In illumos-gate/usr/src/lib/libnwam/common/libnwam.h, I see
#define    NWAM_LOC_PROP_IPFILTER_CONFIG_FILE    "ipfilter-config-file"
#define    NWAM_LOC_PROP_IPFILTER_V6_CONFIG_FILE 
"ipfilter-v6-config-file"


Wild guess: These are probably defineable in the nwam_netcfg group
of the svcprop entries via svccfg.

___
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] How to tell nwam to use the firewall rules in /etc/ipf/ipf.conf ?

[Udo Grabowski (IMK)]

On 28/02/2022 12:44, Udo Grabowski (IMK) wrote:



On 28/02/2022 12:32, Marc Lobelle wrote:

Hello,

I defined firewall rules for ipfilter in /etc/ipf/ipf.conf.

However, I use nwam and, at boot time, nwam wipes out all firewall 
rules and imposes its own: block everything excpt dhcp in the NoNet 
situation and no rules at all when a network interface is active.


The NoNet rules can be replaced by my own rules by copying 
/etc/ipf/ipf.conf in /etc/nwam/loc/NoNet/ipf.conf, but this is useless 
because it is replaced by nothing at all when a network interface is 
activated. Therefore I removed this change.


I tried to add to /etc/nwam/loc/create_loc_auto a line "set 
ipfilter-config-file=/etc/ipf/ipf.conf" similar to the line in 
create_loc_NoNet: "set ipfilter-config-file=/etc/nwam/loc/NoNet/ipf.conf"


But this does not change the behaviour.

How can I tell nwam to use ipf.conf ?

Thanks for your help.

 >  ...

In illumos-gate/usr/src/lib/libnwam/common/libnwam.h, I see
#define    NWAM_LOC_PROP_IPFILTER_CONFIG_FILE    "ipfilter-config-file"
#define    NWAM_LOC_PROP_IPFILTER_V6_CONFIG_FILE
"ipfilter-v6-config-file"


Wild guess: These are probably defineable in the nwam_netcfg group
of the svcprop entries via svccfg.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] How to tell nwam to use the firewall rules in /etc/ipf/ipf.conf ?

[Udo Grabowski (IMK)]

On 28/02/2022 12:32, Marc Lobelle wrote:

Hello,

I defined firewall rules for ipfilter in /etc/ipf/ipf.conf.

However, I use nwam and, at boot time, nwam wipes out all firewall rules 
and imposes its own: block everything excpt dhcp in the NoNet situation 
and no rules at all when a network interface is active.


The NoNet rules can be replaced by my own rules by copying 
/etc/ipf/ipf.conf in /etc/nwam/loc/NoNet/ipf.conf, but this is useless 
because it is replaced by nothing at all when a network interface is 
activated. Therefore I removed this change.


I tried to add to /etc/nwam/loc/create_loc_auto a line "set 
ipfilter-config-file=/etc/ipf/ipf.conf" similar to the line in 
create_loc_NoNet: "set ipfilter-config-file=/etc/nwam/loc/NoNet/ipf.conf"


But this does not change the behaviour.

How can I tell nwam to use ipf.conf ?

Thanks for your help.

>  ...

In illumos-gate/usr/src/lib/libnwam/common/libnwam.h, I see
#define NWAM_LOC_PROP_IPFILTER_CONFIG_FILE  "ipfilter-config-file"
#define NWAM_LOC_PROP_IPFILTER_V6_CONFIG_FILE   "ipfilter-v6-config-file"

These enter pt_types and loc_prop_table structures in libnwam_loc.c,
didn't follow where that ends. Hope that helps.
___
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

[Udo Grabowski (IMK)]

On 23/11/2021 09:19, Nikola M. wrote:

On 11/22/21 17:18, Udo Grabowski (IMK) wrote:


<https://www.atlassian.com/licensing/confluence#confluence-server>
"Important changes to our server and Data Center products
 We’ve ended sales for new server licenses and will end support for
 server on February 2, 2024."


February 2, 2024 sounds just fine, till that time, things can get 
changed multiple times, things reworked, there only needs a green light 
for:
To actually see if license is attainable for fresh instance to be put 
up, ...


Read again: "W E' V E   E N D E DS A L E SF O R
 N E WS E R V E RL I C E N S E S"

___
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

[Udo Grabowski (IMK)]

On 22/11/2021 16:55, Nikola M. wrote:
> ...
Atlassian granted to the then Openindiana named project a license that 
does not need paying, maybe renewal.

It didn't bother the community to use it for ten years or so.

I think license to Confluence Wiki will be provided also for new 
install, one just needs to ask Atlassian. And do fresh install and 
migrate data.
Fresh install of Confluence providing 2 things above is I think very 
possible, it is not, only if it is not allowed to happen.

> ...


"Important changes to our server and Data Center products
 We’ve ended sales for new server licenses and will end support for
 server on February 2, 2024."


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

Re: [OpenIndiana-discuss] rpool mirror disk problems when moved to different slot

[Udo Grabowski (IMK)]

On 06/08/2021 11:19, Stephan Althaus wrote:

Hello!

i just added a new disk to my system, which i put into the slot where a
mirror disk of my rpool resided.

The mirror disk of my rpool went to a other slot, so the device name was
changed c27t1d0 -> c27t0d0

Booting into my OI system, the zpool was found as the first mirror disk
was there,
but the second partition was not found.


Is there a chance that the rpool mount procedure could try harder to
find the mirrors, even when moved ??


Yes i know this may be a rare case :-/



Not so rare, I had this problem when moving a ZFS pool from Openindiana
to Linux and then back. I'm quite sure that it has to do with the fact
that devices are recorded in the label ('zdb -l /dev/dsk/c.t..s0'), and
since somewhere around 2016 the importer seems to peek into this and
refuses to import when it's not the present device. My solution was to
import it to an older Openindiana (which seems to ignore the label
device, as it should) and reexport it to have the device entries in
the label corrected (you can't change it with a binary editor since the
checksums will be invalid).

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

Re: [OpenIndiana-discuss] More 2021.04.30 strangeness

[Udo Grabowski (IMK)]

On 21.06.21 22:17, Reginald Beardsley via openindiana-discuss wrote:

FYI  I wrapped both caja and mate-session with "truss -f -o". Neither output contains the 
"Initializing gksu extensions" string.  ...


Note that you usually don't see full strings in truss output,
those are printed usually as single character outputs. So
you cannot simply search for a string.



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

Re: [OpenIndiana-discuss] recently trouble with USB devices

[Udo Grabowski (IMK)]

On 20.05.21 10:58, Stephan Althaus wrote:

stop endpoint command (1)/slot (7) in wrong state: 19


This one ?


There's a workaround for the problem at the end of
the thread.

___
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?

[Udo Grabowski (IMK)]

On 02.05.21 23:55, Reginald Beardsley via openindiana-discuss wrote:

...
It's only 26 pages, but it's the only description of the internals of ZFS I've 
been able to find.

> ...

Some older references with a practical approach to the internals:

Leall's Blog:


Max Bruning's slides:



The Sun on-disk specification:


ZFS Under the Hood:


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

Re: [OpenIndiana-discuss] RAIDZ2 root pool install fun :-(

[Udo Grabowski (IMK)]

On 20.04.21 02:39, Reginald Beardsley via openindiana-discuss wrote:


rhb@2020-10-txt:~$ zpool status
  pool: rpool1
  state: ONLINE
  scan: none requested
config:

  NAME STATE READ WRITE CKSUM
  rpool1 ONLINE 0 0 0
  raidz2-0 ONLINE 0 0 0
  c0t539A7B78030Fd0 ONLINE 0 0 0
  c0t539A7B7002F3d0 ONLINE 0 0 0
  c0t539A7B700306d0 ONLINE 0 0 0
  c0t539A7B700305d0 ONLINE 0 0 0

...
But I *really* don't like those long winded disk names.



This provides a deeper explanation of the underlying reasoning:


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

Re: [OpenIndiana-discuss] How to mount usb devices?

[Udo Grabowski (IMK)]

On 29.03.21 13:19, Stephan Althaus wrote:

On 03/29/21 12:53 PM, Udo Grabowski (IMK) wrote:


Do you have the /etc/logindevperm file with the entries listed above ?
/dev/vt/7 is owned by you, and /dev/vt/console_user is linking to that,
so those entries should work. These are used by the login process, or
gdm. If you use lightdm, I'm not shure if that supports logindevperm
(somewhere the "light" has its origin ...).



It could also be that this depends on this gdm setting:

# cat /etc/gdm/custom.conf

[security]
CheckDirOwner=false

You have to logout and restart gdm (svcadm restart gdm)  to have this
activated


Yes, i am using lightdm as this is the default.



There seemed to be an attempt to integrate something like that into
lightdm:

<https://openindiana.org/pipermail/openindiana-discuss/2014-October/016590.html>

Unfortunately, the link therein is gone. Gabriele ?

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

Re: [OpenIndiana-discuss] How to mount usb devices?

[Udo Grabowski (IMK)]

On 29.03.21 12:45, Udo Grabowski (IMK) wrote:



On 29.03.21 12:13, Stephan Althaus wrote:

On 03/29/21 12:06 PM, Udo Grabowski (IMK) wrote:

On 29.03.21 11:59, Stephan Althaus wrote:

On 03/29/21 11:34 AM, Udo Grabowski (IMK) wrote:



On 29.03.21 11:27, Apostolos Syropoulos via openindiana-discuss wrote:
On Monday, March 29, 2021, 12:10:20 PM GMT+3, Stephan Althaus 
 wrote:


I tested this on a relatively new OI system where the user 
*should* be

standard, and i get the same:

a) The USB device gets connected ('hotplug') and is accessible via
rmformat & friends
b) The vfat partition on the USB stick is not mounted automatically
c) only the root-role is allowed to mount the partition

So the automount feature needs some additional magic to work, it 
does

not work rightoutofthebox.


I updated my system on 2021:03:18 and I reported this problem to this
list. I can mount a USB thumb disk using mount -F pcfs but the 
automagic
thing is lost. However, when I insert a DVD into the DVD driver 
the automount

thing works.


The usual way this worked was via /etc/logindevperm :

#
# Copyright (c) 1993, 2010, Oracle and/or its affiliates. All 
rights reserved.

#
# /etc/logindevperm - login-based device permissions
#
# If the user is logging in on a device specified in the "console" 
field
# of any entry in this file, the owner/group of the devices listed 
in the
# "devices" field will be set to that of the user.  Similarly, the 
mode

# will be set to the mode specified in the "mode" field.
#
# If the "console" is "/dev/vt/console_user" which is a symlink to 
the current

# active virtual console (/dev/console, or /dev/vt/#), then the first
# user to log into any virtual console will get ownership of all the
# devices until they log out.
#
# "devices" is a colon-separated list of device names.  A device name
# ending in "/*", such as "/dev/fbs/*", specifies all entries 
(except "."

# and "..") in a directory.  A '#' begins a comment and may appear
# anywhere in an entry.
# In addition, regular expressions may be used. Refer to 
logindevperm(4)

# man page.
# Note that any changes in this file should be made when logged in as
# root as devfs provides persistence on minor node attributes.
#
# console   mode    devices
#
/dev/vt/console_user    0600    /dev/mouse:/dev/kbd
/dev/vt/console_user    0600    /dev/sound/*    # audio 
devices
/dev/vt/console_user    0666    /dev/fbs/*  # frame 
buffers

/dev/vt/console_user    0600    /dev/dri/*  # dri devices
/dev/vt/console_user    0400 /dev/removable-media/dsk/*  # 
removable media
/dev/vt/console_user    0400 /dev/removable-media/rdsk/* # 
removable media
/dev/vt/console_user    0400 /dev/hotpluggable/dsk/* # 
hotpluggable storage
/dev/vt/console_user    0400 /dev/hotpluggable/rdsk/*    # 
hotpluggable storage
/dev/vt/console_user    0600    /dev/video[0-9]+    # video 
devices
/dev/vt/console_user    0600    /dev/usb/hid[0-9]+  # hid 
devices should have the same permission with conskbd and consms
/dev/vt/console_user    0600 
/dev/usb/[0-9a-f]+[.][0-9a-f]+/[0-9]+/* 
driver=scsa2usb,usb_mid,usbprn,ugen #libusb/ugen devices

/dev/vt/console_user    0666    /dev/nvidia[0-9a-f]+    # Nvidia
/dev/vt/console_user    0666    /dev/console    # 
workaround for defect.opensolaris.org 12133




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


Hm...
Whichever service should change the ownership of the devices, it 
doesn't seem to work here.


Or am i looking the 'wrong way' ?

steven@fuji:~$ ls -l /dev/vt
total 0
crw---   1 root root 245,  0 Mar 29 09:19 0
crw---   1 root root 245,  1 Mar 29 09:19 1
...
crw---   1 root root 245,  6 Mar 29 09:19 6
crw--w   1 steven   tty  245,  7 Mar 29 09:19 7
crw---   1 root root 245,  8 Mar 29 09:19 8
crw---   1 root root 245,  9 Mar 29 09:19 9
lrwxrwxrwx   1 root root   1 Mar 29 09:19 active -> 7
lrwxrwxrwx   1 root root   0 Mar 29 09:19 console_user -> 7

steven@fuji:~$ ls -l /dev/usb/mass-storage0

lrwxrwxrwx   1 root root  56 Mar 29 09:55 
/dev/usb/mass-storage0 -> 
../../devices/pci@0,0/pci1734,11f3@14/storage@2:scsa2usb


steven@fuji:~$ ls -l 
/devices/pci@0,0/pci1734,11f3@14/storage@2:scsa2usb
crw---   1 root sys  185, 512 Mar 29 09:55 
/devices/pci@0,0/pci1734,11f3@14/storage@2:scsa2usb


steven@fuji:~$ ls -l /dev/removable-media/dsk/c12t0d0
lrwxrwxrwx   1 root root  17 Mar  2 10:47 
/dev/removable-media/dsk/c12t0d0 -> ../../dsk/c12t0d0


steven@fuji:~$ ls -l /dev/hotpluggable/dsk/c12*
lrwxrwxrwx   1 root root  17 Mar  2 10:47 
/dev/h

Re: [OpenIndiana-discuss] How to mount usb devices?

[Udo Grabowski (IMK)]

On 29.03.21 12:13, Stephan Althaus wrote:

On 03/29/21 12:06 PM, Udo Grabowski (IMK) wrote:

On 29.03.21 11:59, Stephan Althaus wrote:

On 03/29/21 11:34 AM, Udo Grabowski (IMK) wrote:



On 29.03.21 11:27, Apostolos Syropoulos via openindiana-discuss wrote:
On Monday, March 29, 2021, 12:10:20 PM GMT+3, Stephan Althaus 
 wrote:


I tested this on a relatively new OI system where the user 
*should* be

standard, and i get the same:

a) The USB device gets connected ('hotplug') and is accessible via
rmformat & friends
b) The vfat partition on the USB stick is not mounted automatically
c) only the root-role is allowed to mount the partition

So the automount feature needs some additional magic to work, it does
not work rightoutofthebox.


I updated my system on 2021:03:18 and I reported this problem to this
list. I can mount a USB thumb disk using mount -F pcfs but the 
automagic
thing is lost. However, when I insert a DVD into the DVD driver the 
automount

thing works.


The usual way this worked was via /etc/logindevperm :

#
# Copyright (c) 1993, 2010, Oracle and/or its affiliates. All rights 
reserved.

#
# /etc/logindevperm - login-based device permissions
#
# If the user is logging in on a device specified in the "console" 
field
# of any entry in this file, the owner/group of the devices listed 
in the

# "devices" field will be set to that of the user.  Similarly, the mode
# will be set to the mode specified in the "mode" field.
#
# If the "console" is "/dev/vt/console_user" which is a symlink to 
the current

# active virtual console (/dev/console, or /dev/vt/#), then the first
# user to log into any virtual console will get ownership of all the
# devices until they log out.
#
# "devices" is a colon-separated list of device names.  A device name
# ending in "/*", such as "/dev/fbs/*", specifies all entries 
(except "."

# and "..") in a directory.  A '#' begins a comment and may appear
# anywhere in an entry.
# In addition, regular expressions may be used. Refer to 
logindevperm(4)

# man page.
# Note that any changes in this file should be made when logged in as
# root as devfs provides persistence on minor node attributes.
#
# console   mode    devices
#
/dev/vt/console_user    0600    /dev/mouse:/dev/kbd
/dev/vt/console_user    0600    /dev/sound/*    # audio devices
/dev/vt/console_user    0666    /dev/fbs/*  # frame buffers
/dev/vt/console_user    0600    /dev/dri/*  # dri devices
/dev/vt/console_user    0400 /dev/removable-media/dsk/*  # 
removable media
/dev/vt/console_user    0400 /dev/removable-media/rdsk/* # 
removable media
/dev/vt/console_user    0400 /dev/hotpluggable/dsk/* # 
hotpluggable storage
/dev/vt/console_user    0400 /dev/hotpluggable/rdsk/*    # 
hotpluggable storage

/dev/vt/console_user    0600    /dev/video[0-9]+    # video devices
/dev/vt/console_user    0600    /dev/usb/hid[0-9]+  # hid 
devices should have the same permission with conskbd and consms
/dev/vt/console_user    0600 /dev/usb/[0-9a-f]+[.][0-9a-f]+/[0-9]+/* 
driver=scsa2usb,usb_mid,usbprn,ugen #libusb/ugen devices

/dev/vt/console_user    0666    /dev/nvidia[0-9a-f]+    # Nvidia
/dev/vt/console_user    0666    /dev/console    # workaround 
for defect.opensolaris.org 12133




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


Hm...
Whichever service should change the ownership of the devices, it 
doesn't seem to work here.


Or am i looking the 'wrong way' ?

steven@fuji:~$ ls -l /dev/vt
total 0
crw---   1 root root 245,  0 Mar 29 09:19 0
crw---   1 root root 245,  1 Mar 29 09:19 1
...
crw---   1 root root 245,  6 Mar 29 09:19 6
crw--w   1 steven   tty  245,  7 Mar 29 09:19 7
crw---   1 root root 245,  8 Mar 29 09:19 8
crw---   1 root root 245,  9 Mar 29 09:19 9
lrwxrwxrwx   1 root root   1 Mar 29 09:19 active -> 7
lrwxrwxrwx   1 root root   0 Mar 29 09:19 console_user -> 7

steven@fuji:~$ ls -l /dev/usb/mass-storage0

lrwxrwxrwx   1 root root  56 Mar 29 09:55 
/dev/usb/mass-storage0 -> 
../../devices/pci@0,0/pci1734,11f3@14/storage@2:scsa2usb


steven@fuji:~$ ls -l /devices/pci@0,0/pci1734,11f3@14/storage@2:scsa2usb
crw---   1 root sys  185, 512 Mar 29 09:55 
/devices/pci@0,0/pci1734,11f3@14/storage@2:scsa2usb


steven@fuji:~$ ls -l /dev/removable-media/dsk/c12t0d0
lrwxrwxrwx   1 root root  17 Mar  2 10:47 
/dev/removable-media/dsk/c12t0d0 -> ../../dsk/c12t0d0


steven@fuji:~$ ls -l /dev/hotpluggable/dsk/c12*
lrwxrwxrwx   1 root root  17 Mar  2 10:47 
/dev/hotpluggable/dsk/c12t0d0 -> ../../dsk/c12t0d0

...

Links don't change ownership, you have to l

Re: [OpenIndiana-discuss] How to mount usb devices?

[Udo Grabowski (IMK)]

On 29.03.21 11:59, Stephan Althaus wrote:

On 03/29/21 11:34 AM, Udo Grabowski (IMK) wrote:



On 29.03.21 11:27, Apostolos Syropoulos via openindiana-discuss wrote:
On Monday, March 29, 2021, 12:10:20 PM GMT+3, Stephan Althaus 
 wrote:



I tested this on a relatively new OI system where the user *should* be
standard, and i get the same:

a) The USB device gets connected ('hotplug') and is accessible via
rmformat & friends
b) The vfat partition on the USB stick is not mounted automatically
c) only the root-role is allowed to mount the partition

So the automount feature needs some additional magic to work, it does
not work rightoutofthebox.


I updated my system on 2021:03:18 and I reported this problem to this
list. I can mount a USB thumb disk using mount -F pcfs but the automagic
thing is lost. However, when I insert a DVD into the DVD driver the 
automount

thing works.


The usual way this worked was via /etc/logindevperm :

#
# Copyright (c) 1993, 2010, Oracle and/or its affiliates. All rights 
reserved.

#
# /etc/logindevperm - login-based device permissions
#
# If the user is logging in on a device specified in the "console" field
# of any entry in this file, the owner/group of the devices listed in the
# "devices" field will be set to that of the user.  Similarly, the mode
# will be set to the mode specified in the "mode" field.
#
# If the "console" is "/dev/vt/console_user" which is a symlink to the 
current

# active virtual console (/dev/console, or /dev/vt/#), then the first
# user to log into any virtual console will get ownership of all the
# devices until they log out.
#
# "devices" is a colon-separated list of device names.  A device name
# ending in "/*", such as "/dev/fbs/*", specifies all entries (except "."
# and "..") in a directory.  A '#' begins a comment and may appear
# anywhere in an entry.
# In addition, regular expressions may be used. Refer to logindevperm(4)
# man page.
# Note that any changes in this file should be made when logged in as
# root as devfs provides persistence on minor node attributes.
#
# console   mode    devices
#
/dev/vt/console_user    0600    /dev/mouse:/dev/kbd
/dev/vt/console_user    0600    /dev/sound/*    # audio devices
/dev/vt/console_user    0666    /dev/fbs/*  # frame buffers
/dev/vt/console_user    0600    /dev/dri/*  # dri devices
/dev/vt/console_user    0400    /dev/removable-media/dsk/*  # 
removable media
/dev/vt/console_user    0400    /dev/removable-media/rdsk/* # 
removable media
/dev/vt/console_user    0400    /dev/hotpluggable/dsk/* # 
hotpluggable storage
/dev/vt/console_user    0400    /dev/hotpluggable/rdsk/*    # 
hotpluggable storage

/dev/vt/console_user    0600    /dev/video[0-9]+    # video devices
/dev/vt/console_user    0600    /dev/usb/hid[0-9]+  # hid devices 
should have the same permission with conskbd and consms
/dev/vt/console_user    0600 /dev/usb/[0-9a-f]+[.][0-9a-f]+/[0-9]+/* 
driver=scsa2usb,usb_mid,usbprn,ugen #libusb/ugen devices

/dev/vt/console_user    0666    /dev/nvidia[0-9a-f]+    # Nvidia
/dev/vt/console_user    0666    /dev/console    # workaround 
for defect.opensolaris.org 12133




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


Hm...
Whichever service should change the ownership of the devices, it doesn't 
seem to work here.


Or am i looking the 'wrong way' ?

steven@fuji:~$ ls -l /dev/vt
total 0
crw---   1 root root 245,  0 Mar 29 09:19 0
crw---   1 root root 245,  1 Mar 29 09:19 1
...
crw---   1 root root 245,  6 Mar 29 09:19 6
crw--w   1 steven   tty  245,  7 Mar 29 09:19 7
crw---   1 root root 245,  8 Mar 29 09:19 8
crw---   1 root root 245,  9 Mar 29 09:19 9
lrwxrwxrwx   1 root root   1 Mar 29 09:19 active -> 7
lrwxrwxrwx   1 root root   0 Mar 29 09:19 console_user -> 7

steven@fuji:~$ ls -l /dev/usb/mass-storage0

lrwxrwxrwx   1 root root  56 Mar 29 09:55 
/dev/usb/mass-storage0 -> 
../../devices/pci@0,0/pci1734,11f3@14/storage@2:scsa2usb


steven@fuji:~$ ls -l /devices/pci@0,0/pci1734,11f3@14/storage@2:scsa2usb
crw---   1 root sys  185, 512 Mar 29 09:55 
/devices/pci@0,0/pci1734,11f3@14/storage@2:scsa2usb


steven@fuji:~$ ls -l /dev/removable-media/dsk/c12t0d0
lrwxrwxrwx   1 root root  17 Mar  2 10:47 
/dev/removable-media/dsk/c12t0d0 -> ../../dsk/c12t0d0


steven@fuji:~$ ls -l /dev/hotpluggable/dsk/c12*
lrwxrwxrwx   1 root root  17 Mar  2 10:47 
/dev/hotpluggable/dsk/c12t0d0 -> ../../dsk/c12t0d0

...

Links don't change ownership, you have to look at the targets (-L)

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

Re: [OpenIndiana-discuss] How to mount usb devices?

[Udo Grabowski (IMK)]

On 29.03.21 11:27, Apostolos Syropoulos via openindiana-discuss wrote:

On Monday, March 29, 2021, 12:10:20 PM GMT+3, Stephan Althaus 
 wrote:


I tested this on a relatively new OI system where the user *should* be
standard, and i get the same:

a) The USB device gets connected ('hotplug') and is accessible via
rmformat & friends
b) The vfat partition on the USB stick is not mounted automatically
c) only the root-role is allowed to mount the partition

So the automount feature needs some additional magic to work, it does
not work rightoutofthebox.


I updated my system on 2021:03:18 and I reported this problem to this
list. I can mount a USB thumb disk using mount -F pcfs but the automagic
thing is lost. However, when I insert a DVD into the DVD driver the automount
thing works.


The usual way this worked was via /etc/logindevperm :

#
# Copyright (c) 1993, 2010, Oracle and/or its affiliates. All rights 
reserved.

#
# /etc/logindevperm - login-based device permissions
#
# If the user is logging in on a device specified in the "console" field
# of any entry in this file, the owner/group of the devices listed in the
# "devices" field will be set to that of the user.  Similarly, the mode
# will be set to the mode specified in the "mode" field.
#
# If the "console" is "/dev/vt/console_user" which is a symlink to the 
current

# active virtual console (/dev/console, or /dev/vt/#), then the first
# user to log into any virtual console will get ownership of all the
# devices until they log out.
#
# "devices" is a colon-separated list of device names.  A device name
# ending in "/*", such as "/dev/fbs/*", specifies all entries (except "."
# and "..") in a directory.  A '#' begins a comment and may appear
# anywhere in an entry.
# In addition, regular expressions may be used. Refer to logindevperm(4)
# man page.
# Note that any changes in this file should be made when logged in as
# root as devfs provides persistence on minor node attributes.
#
# console   modedevices
#
/dev/vt/console_user0600/dev/mouse:/dev/kbd
/dev/vt/console_user0600/dev/sound/*# audio devices
/dev/vt/console_user0666/dev/fbs/*  # frame buffers
/dev/vt/console_user0600/dev/dri/*  # dri devices
/dev/vt/console_user0400/dev/removable-media/dsk/*  # 
removable media
/dev/vt/console_user0400/dev/removable-media/rdsk/* # 
removable media
/dev/vt/console_user0400/dev/hotpluggable/dsk/* # 
hotpluggable storage
/dev/vt/console_user0400/dev/hotpluggable/rdsk/*# 
hotpluggable storage

/dev/vt/console_user0600/dev/video[0-9]+# video devices
/dev/vt/console_user0600/dev/usb/hid[0-9]+  # hid devices 
should have the same permission with conskbd and consms
/dev/vt/console_user0600/dev/usb/[0-9a-f]+[.][0-9a-f]+/[0-9]+/* 
driver=scsa2usb,usb_mid,usbprn,ugen #libusb/ugen devices

/dev/vt/console_user0666/dev/nvidia[0-9a-f]+# Nvidia
/dev/vt/console_user0666/dev/console# workaround for 
defect.opensolaris.org 12133


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

Re: [OpenIndiana-discuss] Replacing Solaris 10 u8

[Udo Grabowski (IMK)]

On 24.03.21 09:08, Toomas Soome via openindiana-discuss wrote:




On 24. Mar 2021, at 02:50, Reginald Beardsley via openindiana-discuss 
 wrote:

My Solaris 10 u8 instance is rather dated.  I'd like to update it, but there 
are some absolute requirements:

Sun/Forte/Oracle Developer Studio


If that is required, then the only option are solaris 11.4, oracle linux 6 & 7, 
redhat 6 & 7.



SunStudio 12.1u1 can still be transported from one instance of OI to
another if you still have the installation packages or rsync the
/opt/SUNWspro directory and set the links into /usr/bin etc. by
hand. We have it running on an 2018.10 Hipster x86. Don't know if
the same applies to Sparc, but I suspect that it will work, too.

Versions later that 12.1u1 have strict license restrictions, and
since 12.4 it's binary incompatible and only available via the
pkg repositories (for which you need service contracts).

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

Re: [OpenIndiana-discuss] How do I verify that fmd is actually able to detect and log ECC errors?

[Udo Grabowski (IMK)]

On 16.03.21 20:08, Reginald Beardsley via openindiana-discuss wrote:

I suspect memory errors on my Sol 10 u8 system, but there are no memory errors reported 
by "fmdump -eV".  All the errors and events are zfs related.

Initial symptom is starting a scrub on a freshly booted system will complete 
properly, but the same operation after the system has been up for a few days 
will cause a kernel panic. Immediately after a reboot a scrub will complete 
normally.  This behavior suggests bit fade to me.

This has been very consistent  for the last few months.  The system is an HP 
Z400 which is 10 years old and generally has run 24x7.  It was certified by Sun 
for Solaris 10 which is why I bought it and uses unbuffered, unregistered ECC 
DDR3 DIMMs.  Since my initial purchase I have bought three more Z400s.

Recently the system became unstable to the point I have not been able to complete a 
"zfs send -R" to a 12 TB WD USB drive.  My last attempt using a Hipster 
LiveImage died after ~25 hours.

My Hipster 2017.10 system shows some events which appear to be ECC related, but I'm not able to interpret them.  I've attached a file with the last such event. 

>

Clearly a memory error, second DIMM of first DRAM channel of CPU 0
(where ever that physically is located is another question...).

If I recall correctly some of your last mails, you had varying boot
times, which indicate that the BIOS internal memtest routine stumbled
across that module. If it once will be sufficiently damaged, the BIOS
should isolate that itself and you'll find yourself with one DIMM memory
less (seen in 'top'). But that could take a long time. The current error
was correctable, so it should not have an immediate impact to your
RAM content.
I would rather suspect some additional issues with your voltages, since
usually, after ten years, the caps of the power supply degrade 
sufficently to generate fluctuations. But still, the BIOS protections

(if there are any) should chime in here if something really goes
haywire. At least, there should be a BIOS page that shows you the
essential voltages (or monitor them with ipmitool sensor, if it has a
BMC). This problem will certainly be load-dependent.

The symptoms you describe usually cannot happen from defect ECC memory,
only non-ECC DIMMs can cause such hassles.

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

Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!

[Udo Grabowski (IMK)]

On 05.03.21 07:56, cretin1997 via openindiana-discuss wrote:

...
Trust me, man. SquashFS is a superior technology ...

> It's the superior technology ...

From  my decades of experience, if I read such sentences,
I immediately know it's not. Superior.
It's just another "something", surrounded by Hipsters
trying to generate a hype around it.


 and is the answer to our problem.


? What problem ? What you are talking about ? Why
not using Linux when everything there is superior
and solves your problems ? What you are doing here ?

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

Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!

[Udo Grabowski (IMK)]

On 04.03.21 17:10, Toomas Soome via openindiana-discuss wrote:




On 4. Mar 2021, at 18:04, Udo Grabowski (IMK)  wrote:

On 04.03.21 16:43, Reginald Beardsley via openindiana-discuss wrote:

  OK I just made several attempts:
First attempt was with 2020.10 GUI install ISO. That was forced to maintenance 
mode and was unable to locate libpcidb.so.1 when I ran prtconf -v.
Second attempt was with 2019.04 USB. That kernel panicked for multiuser and 
single user. Even with a camera ready I couldn't get the message.
Both of those attempts had a 5 TB drive installed. I'm trying again with a 750 
GB drive which happens to have CentOS 7 installed. That tries to boot, but 
doesn't seem to get far before it just spins. The GUI 2020.10 ISO behaves the 
same as with the 5 TB disk.
It completely ignored the 2019.04 USB image even with it selected via F9. The 
20202.10 text ISO also fails for lack of libpcidb.so.1


I can only second your opinion about the the quality of the ISOs, but
two years ago I had some luck with 2018.10, which was the first after
151a9 that actually booted a newer system. Maybe you try that, it's
sufficient for the job (if the rpool does not have activated the most
recent feature flags…)


I think the next version should appear in may, so there is your chance to join 
with release building team to make sure the next version is with expected 
quality.


Yes, happy to help, as indeed two new servers are waiting for
rack install and a new OI (ZStor CIB-448 XEON Gold 6126 based
cluster dual host data graves for 384 TB in 48 slots, including
NVME SSDs and stock 4 x LSI 3008 12 Gb/s SAS HBAs, 88E151* Marvell
Alaska net onboard, Intel 82599ES 10Gbe ). Hope I get these into
the rack soon, COVID-19 still blocks us here.


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

Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!

[Udo Grabowski (IMK)]

On 04.03.21 17:04, Udo Grabowski (IMK) wrote:

On 04.03.21 16:43, Reginald Beardsley via openindiana-discuss wrote:

  OK I just made several attempts:

First attempt was with 2020.10 GUI install ISO. That was forced to 
maintenance mode and was unable to locate libpcidb.so.1 when I ran 
prtconf -v.


Second attempt was with 2019.04 USB. That kernel panicked for 
multiuser and single user. Even with a camera ready I couldn't get the 
message.


Both of those attempts had a 5 TB drive installed. I'm trying again 
with a 750 GB drive which happens to have CentOS 7 installed. That 
tries to boot, but doesn't seem to get far before it just spins. The 
GUI 2020.10 ISO behaves the same as with the 5 TB disk.


It completely ignored the 2019.04 USB image even with it selected via 
F9. The 20202.10 text ISO also fails for lack of libpcidb.so.1




I can only second your opinion about the the quality of the ISOs, but
two years ago I had some luck with 2018.10, which was the first after
151a9 that actually booted a newer system. Maybe you try that, it's
sufficient for the job (if the rpool does not have activated the most
recent feature flags...)



No, sorry, the ISO was 2018.04 (the system was then upgraded to 2018.10)


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

Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!

[Udo Grabowski (IMK)]

On 04.03.21 16:43, Reginald Beardsley via openindiana-discuss wrote:

  OK I just made several attempts:

First attempt was with 2020.10 GUI install ISO. That was forced to maintenance 
mode and was unable to locate libpcidb.so.1 when I ran prtconf -v.

Second attempt was with 2019.04 USB. That kernel panicked for multiuser and 
single user. Even with a camera ready I couldn't get the message.

Both of those attempts had a 5 TB drive installed. I'm trying again with a 750 
GB drive which happens to have CentOS 7 installed. That tries to boot, but 
doesn't seem to get far before it just spins. The GUI 2020.10 ISO behaves the 
same as with the 5 TB disk.

It completely ignored the 2019.04 USB image even with it selected via F9. The 
20202.10 text ISO also fails for lack of libpcidb.so.1



I can only second your opinion about the the quality of the ISOs, but
two years ago I had some luck with 2018.10, which was the first after
151a9 that actually booted a newer system. Maybe you try that, it's
sufficient for the job (if the rpool does not have activated the most
recent feature flags...)

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

Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!

[Udo Grabowski (IMK)]

On 03.03.21 19:16, Udo Grabowski (IMK) wrote:

On 03.03.21 18:22, Toomas Soome via openindiana-discuss wrote:



On 3. Mar 2021, at 18:13, Reginald Beardsley via openindiana-discuss 
 wrote:


Categorically does *not* work on my 4 slot Z400. It kernel panics 
before it reaches the single user milestone using the device 
specified in the prtconf -v output from my system. With the"2822" 
device Gary specified the boot fails. So it is not as simple as has 
been presented.




it Iis a bit more complicated, I’m afraid. I guess, if you boot -k, 
you will see it will complain about being unable to mount rootfs. *if* 
that is the case, you would need to boot from cd/usb, use update_drv 
to bind ahci driver, then import rpool, beadm mount your be and use 
devfsadm -r and bootadm update-archive -R


But the problem seems to be that he has no installed BE because it
doesn't boot from CD/USB. so somehow he must modify the installation
media.


Ah, sorry, no, it seems he has at least a crippled boot disk.
So that CD boot, bootadm  -R path should work.


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

Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!

[Udo Grabowski (IMK)]

On 03.03.21 18:22, Toomas Soome via openindiana-discuss wrote:




On 3. Mar 2021, at 18:13, Reginald Beardsley via openindiana-discuss 
 wrote:

Categorically does *not* work on my 4 slot Z400. It kernel panics before it reaches the 
single user milestone using the device specified in the prtconf -v output from my system. 
With the"2822" device Gary specified the boot fails. So it is not as simple as 
has been presented.



it Iis a bit more complicated, I’m afraid. I guess, if you boot -k, you will 
see it will complain about being unable to mount rootfs. *if* that is the case, 
you would need to boot from cd/usb, use update_drv to bind ahci driver, then 
import rpool, beadm mount your be and use devfsadm -r and bootadm 
update-archive -R


But the problem seems to be that he has no installed BE because it
doesn't boot from CD/USB. so somehow he must modify the installation
media.

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

Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!

[Udo Grabowski (IMK)]

Did you follow Gary's instructions ? It was already clear that the
simple procedure will not work with this crippled BIOS.

On 02.03.21 22:42, Reginald Beardsley via openindiana-discuss wrote:

  Does *not* work on my Z400 machine. I reset the BIOS to "AHCI+RAID" and the 
2020.10 GUI installer enters maintenance mode. prtconf -v won't even run.

With it set to "IDE" in the BIOS it reports "82801JI (ICH10 family) 4 port SATA IDE" and 
the same message but "2 port".

"RAID" never appears in the prtconf -v output. I'm running BIOS 3.19, though I 
do have a couple of machines with an older BIOS (3.07??) installed. Those are all 4 DIM 
slot machines. My newer 6 slot machine is far too precious to fool with. The 4 DIMM 
machines have Vista stickers. The 6 DIMM came with Win 7 Pro.

  I really don't think it's an issue. The numbers below are for a 3 disk RAIDZ1 
pool with a quad core 2.67 GHz Xeon W3520 with 8 GB of RAM. Realistically it's 
not going to be able to crunch data fast enough for the disk transfer rate to 
matter.

sun_x86%rhb {126} /usr/bin/time dd if=/dev/zero bs=65536 count=65536 of=zero.tst
65536+0 records in
65536+0 records out
4294967296 bytes transferred in 46.334185 secs (92695432 bytes/sec)

real 46.3
user 0.1
sys 4.8
sun_x86%rhb {127}
sun_x86%rhb {127} rm zero.tst
sun_x86%rhb {128} /usr/bin/time dd if=/dev/zero bs=65536 count=1048576 
of=zero.tst
1048576+0 records in
1048576+0 records out
68719476736 bytes transferred in 1086.415813 secs (63253384 bytes/sec)

real 18:06.4
user 2.2
sys 1:17.0
sun_x86%rhb {129}

Have Fun!
Reg

On Tuesday, March 2, 2021, 10:49:05 AM CST, Gary Mills  
wrote:

ACHI+RAID does work with Solaris and OI, but you have to do some
preparation first. I know because I have done that with my Z400
and installed OI on it. The instructions are here:

  
https://superuser.com/questions/635829/how-do-i-install-solaris-on-a-fake-raid-a-k-a-ahciraid-sata-sas-controller/635830#635830



   
___

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] Hipster 2020.10 text installer ISO Wow!!!!

[Udo Grabowski (IMK)]

Don't waste your time with this: You are in IDE emulation mode, and
even if you get that working somehow you won't be happy at all,
since that mode is just slow. Get yourself into AHCI mode first,
along the guidelines Gary just posted (and that should've worked
out of the box, these HPE guys manage to break everything...).

On 02.03.21 18:21, Reginald Beardsley via openindiana-discuss wrote:

  Gary,

Thanks. That's *very* nteresting. I shall have to study that closely.

I ran "truss -f -o truss.out format -e /dev/rdsk/c4d0"

down at the end of a *very* long output is this tidbit. Note the ENOENTs. The 
libraries being sought are in /lib and were found previously. I'm rather 
puzzled that with the device specified on the command line, format(1m) walked 
the entire /dev/rdsk tree and then some including sections of the filesysem I'd 
never heard of.

At present I'm trying to sort out how to fix access to the libraries. /mnt/misc 
is a RO filesystem mounted from the DVD, so the obvious solution is not 
possible. This machine only has 8 GB of RAM so I might not be able to create a 
copy of /mnt/misc in ramfs, but I'll give it a try.

I'm unclear about the relationship of c4d0, c4d0p0, etc. I can R/W /dev/rdsk/c4d0p0:c but 
not without the ":c"


3994/1: open("/dev/rdsk/c4d0s0", O_RDONLY|O_NDELAY) = 4
3994/1: stat64("/opt/VRTSvxvm/lib/libadm.so.1", 0x08046968) Err#2 ENOENT
3994/1: ioctl(4, DKIOCGEXTVTOC, 0x080477A8) Err#48 ENOTSUP
3994/1: stat64("/opt/VRTSvxvm/lib/libefi.so.1", 0x08046968) Err#2 ENOENT
3994/1: ioctl(4, DKIOCGMEDIAINFO, 0x08047310) = 0
3994/1: ioctl(4, DKIOCGMBOOT, 0x080979D0) = 0
3994/1: ioctl(4, DKIOCINFO, 0x080472A4) = 0
3994/1: ioctl(4, DKIOCGMEDIAINFO, 0x08047300) = 0
3994/1: ioctl(4, DKIOCGETEFI, 0x080472E8) = 0
3994/1: ioctl(4, DKIOCGETEFI, 0x080472E8) = 0
3994/1: ioctl(4, DKIOCGETEFI, 0x080472E8) = 0
3994/1: close(4) = 0
3994/1: stat("/dev/rdsk/c4d0p0", 0x08047608) = 0
3994/1: open("/dev/rdsk/c4d0p0", O_RDONLY) Err#6 ENXIO
3994/1: fstat64(2, 0x08046640) = 0
3994/1: write(2, " E r r o r : c a n ' t".., 24) = 24
3994/1: write(2, " / d e v / r d s k / c 4".., 16) = 16
3994/1: write(2, " ' .\n", 3) = 3
3994/1: Incurred fault #6, FLTBOUNDS %pc = 0x080658CB
3994/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x0258
3994/1: Received signal #11, SIGSEGV [default]
3994/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x0258



  On Tuesday, March 2, 2021, 05:49:05 PM GMT+1, Gary Mills 
 wrote:
  
  On Tue, Mar 02, 2021 at 03:37:23PM +, Reginald Beardsley via oi-dev wrote:

     Thank you again. Very helpful. The Z400 will only support IDE mode.
     ACHI+RAID is the other option which I think only works with Windows. I
     know it will not work with Solaris and feel fairly certain it doesn't
     work with Linux or *BSD either.


ACHI+RAID does work with Solaris and OI, but you have to do some
preparation first.  I know because I have done that with my Z400
and installed OI on it.  The instructions are here:

     
https://superuser.com/questions/635829/how-do-i-install-solaris-on-a-fake-raid-a-k-a-ahciraid-sata-sas-controller/635830#635830




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