Re: [OpenIndiana-discuss] Compiling KeepassXC on Hipster

[bentahyr]

Ok, I just needed a few more minutes obviously so I found where this 
options were defined by default :

CMakeLists.txt:add_gcc_compiler_flags("-fvisibility=hidden")
CMakeLists.txt:add_gcc_compiler_cxxflags("-fvisibility-inlines-hidden")

commented them out and compiled it

Et voila! It works (64bits as well), I finally have auto type function 
available which is quite cool.

I think I'm ready to try to package it.
Should I do 1PR for libargon2 and 1PR for KeepassXC  or 1 PR for both 
libargon2 and KeepassXC ?

64 bits build only or both 32/64 bits ?

Best regards.
Ben

Le 2019-01-11 11:17, benta...@chez.com a écrit :

Hi all,
I'm coming back to this and spent nearly 1.5 day on this. They used to
have this issue on netbsd and first solved it by removing compilation
option related to symbol visibility, then removed that hack later on
but I cannot figure out how they work it out to not use the hack.

http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/security/keepassxc/Makefile.diff?only_with_tag=MAIN&r1=text&tr1=1.1&r2=text&tr2=1.2

Basically, I would like to try to compile without -fvisibility=hidden
but I cannot get my head around how to make it through cmake
The only packages (curl, gnome2-atk) in OI-userland having something
to do with this option are using autoconfigure and diabling it is part
of the configure script.

What would be the way to force cmake to tell gcc not to use
-fvisibility=hidden ?

Best regards.
Ben

On 05/12/2018 10:43, benta...@chez.com wrote:


The issue on autotype is related to QT.
The plugin for autotype doesn't load at start :
$ LANG=en_US.UTF-8 LD_LIBRARY_PATH=/usr/lib/qt/5.8/lib:/usr/local/lib 
/usr/local/bin/keepassxc

Qt: Session management error: Could not open network socket
Warning: using insecure memory!
Couldn't load translations.
Unable to load auto-type plugin:
Cannot resolve symbol "qt_plugin_instance" in 
/usr/local/lib/keepassxc/libkeepassx-autotype-xcb.so: (ld.so.1: 
keepassxc: fatal: qt_plugin_instance: can't find symbol)

QObject::startTimer: Timers cannot have negative interval

I have to add the LD_LIBRARY_PATH for QT, so I suspect I miss a few 
other path, though :

/usr/lib/qt/5.8/lib$ LANG=en_US.UTF-8 grep -R qt_plugin_instance *
Binary file amd64/libQt5DesignerComponents.so.5.8.0 matches
Binary file amd64/libQt5DesignerComponents.so.5 matches
Binary file amd64/libQt5Core.so.5.8 matches
Binary file amd64/libQt5DesignerComponents.so matches
Binary file amd64/libQt5DesignerComponents.so.5.8 matches
Binary file amd64/libQt5Core.so.5 matches
Binary file amd64/libQt5Core.so.5.8.0 matches
Binary file amd64/libQt5Core.so matches
Binary file libQt5Core.so matches
Binary file libQt5Core.so.5 matches
Binary file libQt5Core.so.5.8 matches
Binary file libQt5Core.so.5.8.0 matches
Binary file libQt5DesignerComponents.so matches
Binary file libQt5DesignerComponents.so.5 matches
Binary file libQt5DesignerComponents.so.5.8 matches
Binary file libQt5DesignerComponents.so.5.8.0 matches

I'm not sure why it doesn't find the symbol

Best regards.
Ben

On 04/12/2018 10:38, benta...@chez.com wrote:

This is not perfect, this is what's left to do :
- 64bits keepassxc and libargon2
- autotype doesn't work, option (menu entries, shortcut) not present

libargon2 compiles out of the box
https://github.com/P-H-C/phc-winner-argon2

cmake :
- cmake linker flags -lsocket -lnsl -lrt -lresolv
- cmake didn't find QT5 config utilities, I had to point it to the 
directory
- did compilation with GCC7 but I think default GCC6 should work as 
well

- due to GCC7, I added -I /usr/gcc/7/include/c++/7.3.0 to CXX_FLAGS

keepassxc patch :
 cut here 
--- src/totp/totp.cpp   2018-08-23 03:25:04.0 +
+++ src/totp/totp.cpp.mod   2018-12-04 09:09:32.413168641 +
@@ -164,7 +164,7 @@
direction = 1;
startpos = 0;

}
-quint32 digitsPower = pow(encoder.alphabet.size(), digits);
+quint32 digitsPower = pow(double (encoder.alphabet.size()), 
digits);


quint64 password = binary % digitsPower;
QString retval(int(digits), encoder.alphabet[0]);
 cut here 

Best regards.
Ben

On 04/12/2018 09:29, Till Wegmüller wrote:

Nice work.

I would also be interested in it.

Could you Publish a patch or put a makefile into OI Userland?

Thanks and Greetings
Till
On 12/03/18 09:28 PM, benta...@chez.com wrote:

Thanks Bob and Alexander, I think I start to understand.

grep digits ../../src/totp/totp.cpp
[...]
quint8 digits = encoder.digits == 0 ? numDigits : encoder.digits;
[...]

From my 30 years old rusty knowledge of C++, this mean that digits is
supposed to be a 'quint8' which is most probably QT version of the 
'int'
and as Bob noticed the pow function expects 'int', 'float', or 
'double'


From Alexander reference, I should have
quint32 digitsPower = pow(encoder.alphabet.size(), int(digits));

In that particular case it was 'encoder.alphabet.size()'  which 
appeared

ambiguous, using 'double (encoder.alphabet.size())' made it. 'digits'
was ok so far

Bottom line is I could compile and

Re: [OpenIndiana-discuss] Compiling KeepassXC on Hipster

[bentahyr]

Hi all,
I'm coming back to this and spent nearly 1.5 day on this. They used to 
have this issue on netbsd and first solved it by removing compilation 
option related to symbol visibility, then removed that hack later on but 
I cannot figure out how they work it out to not use the hack.


http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/security/keepassxc/Makefile.diff?only_with_tag=MAIN&r1=text&tr1=1.1&r2=text&tr2=1.2

Basically, I would like to try to compile without -fvisibility=hidden 
but I cannot get my head around how to make it through cmake
The only packages (curl, gnome2-atk) in OI-userland having something to 
do with this option are using autoconfigure and diabling it is part of 
the configure script.


What would be the way to force cmake to tell gcc not to use 
-fvisibility=hidden ?


Best regards.
Ben

On 05/12/2018 10:43, benta...@chez.com wrote:


The issue on autotype is related to QT.
The plugin for autotype doesn't load at start :
$ LANG=en_US.UTF-8 LD_LIBRARY_PATH=/usr/lib/qt/5.8/lib:/usr/local/lib 
/usr/local/bin/keepassxc

Qt: Session management error: Could not open network socket
Warning: using insecure memory!
Couldn't load translations.
Unable to load auto-type plugin:
Cannot resolve symbol "qt_plugin_instance" in 
/usr/local/lib/keepassxc/libkeepassx-autotype-xcb.so: (ld.so.1: 
keepassxc: fatal: qt_plugin_instance: can't find symbol)

QObject::startTimer: Timers cannot have negative interval

I have to add the LD_LIBRARY_PATH for QT, so I suspect I miss a few 
other path, though :

/usr/lib/qt/5.8/lib$ LANG=en_US.UTF-8 grep -R qt_plugin_instance *
Binary file amd64/libQt5DesignerComponents.so.5.8.0 matches
Binary file amd64/libQt5DesignerComponents.so.5 matches
Binary file amd64/libQt5Core.so.5.8 matches
Binary file amd64/libQt5DesignerComponents.so matches
Binary file amd64/libQt5DesignerComponents.so.5.8 matches
Binary file amd64/libQt5Core.so.5 matches
Binary file amd64/libQt5Core.so.5.8.0 matches
Binary file amd64/libQt5Core.so matches
Binary file libQt5Core.so matches
Binary file libQt5Core.so.5 matches
Binary file libQt5Core.so.5.8 matches
Binary file libQt5Core.so.5.8.0 matches
Binary file libQt5DesignerComponents.so matches
Binary file libQt5DesignerComponents.so.5 matches
Binary file libQt5DesignerComponents.so.5.8 matches
Binary file libQt5DesignerComponents.so.5.8.0 matches

I'm not sure why it doesn't find the symbol

Best regards.
Ben

On 04/12/2018 10:38, benta...@chez.com wrote:

This is not perfect, this is what's left to do :
- 64bits keepassxc and libargon2
- autotype doesn't work, option (menu entries, shortcut) not present

libargon2 compiles out of the box
https://github.com/P-H-C/phc-winner-argon2

cmake :
- cmake linker flags -lsocket -lnsl -lrt -lresolv
- cmake didn't find QT5 config utilities, I had to point it to the 
directory
- did compilation with GCC7 but I think default GCC6 should work as 
well

- due to GCC7, I added -I /usr/gcc/7/include/c++/7.3.0 to CXX_FLAGS

keepassxc patch :
 cut here 
--- src/totp/totp.cpp   2018-08-23 03:25:04.0 +
+++ src/totp/totp.cpp.mod   2018-12-04 09:09:32.413168641 +
@@ -164,7 +164,7 @@
direction = 1;
startpos = 0;

}
-quint32 digitsPower = pow(encoder.alphabet.size(), digits);
+quint32 digitsPower = pow(double (encoder.alphabet.size()), 
digits);


quint64 password = binary % digitsPower;
QString retval(int(digits), encoder.alphabet[0]);
 cut here 

Best regards.
Ben

On 04/12/2018 09:29, Till Wegmüller wrote:

Nice work.

I would also be interested in it.

Could you Publish a patch or put a makefile into OI Userland?

Thanks and Greetings
Till
On 12/03/18 09:28 PM, benta...@chez.com wrote:

Thanks Bob and Alexander, I think I start to understand.

grep digits ../../src/totp/totp.cpp
[...]
quint8 digits = encoder.digits == 0 ? numDigits : encoder.digits;
[...]

From my 30 years old rusty knowledge of C++, this mean that digits is
supposed to be a 'quint8' which is most probably QT version of the 
'int'

and as Bob noticed the pow function expects 'int', 'float', or 'double'

From Alexander reference, I should have
quint32 digitsPower = pow(encoder.alphabet.size(), int(digits));

In that particular case it was 'encoder.alphabet.size()'  which 
appeared

ambiguous, using 'double (encoder.alphabet.size())' made it. 'digits'
was ok so far

Bottom line is I could compile and execute it, it is nice to have it
native (works with wine).

Thanks both of you.
Best regards.
Ben

On 04/12/2018 03:21, Bob Friesenhahn wrote:

On Mon, 3 Dec 2018, benta...@chez.com wrote:

Hello,
'static QString Totp::generateTotp(QByteArray, quint64, quint8,
quint8)':
/home/ben/tmp/keepassxc-2.3.4/src/totp/totp.cpp:167:62: error: call
of overloaded 'pow(int, quint8&)' is ambiguous
quint32 digitsPower = pow(encoder.alphabet.size(), digits);

What is the declared storage type of the 'digits' argument?  From
reading the header, it appears that it must be of type 'int', 'float',
or 'double'.  Any other type would 

Re: [OpenIndiana-discuss] Compiling KeepassXC on Hipster

[bentahyr]

The issue on autotype is related to QT.
The plugin for autotype doesn't load at start :
$ LANG=en_US.UTF-8 LD_LIBRARY_PATH=/usr/lib/qt/5.8/lib:/usr/local/lib 
/usr/local/bin/keepassxc

Qt: Session management error: Could not open network socket
Warning: using insecure memory!
Couldn't load translations.
Unable to load auto-type plugin:
Cannot resolve symbol "qt_plugin_instance" in 
/usr/local/lib/keepassxc/libkeepassx-autotype-xcb.so: (ld.so.1: 
keepassxc: fatal: qt_plugin_instance: can't find symbol)

QObject::startTimer: Timers cannot have negative interval

I have to add the LD_LIBRARY_PATH for QT, so I suspect I miss a few 
other path, though :

/usr/lib/qt/5.8/lib$ LANG=en_US.UTF-8 grep -R qt_plugin_instance *
Binary file amd64/libQt5DesignerComponents.so.5.8.0 matches
Binary file amd64/libQt5DesignerComponents.so.5 matches
Binary file amd64/libQt5Core.so.5.8 matches
Binary file amd64/libQt5DesignerComponents.so matches
Binary file amd64/libQt5DesignerComponents.so.5.8 matches
Binary file amd64/libQt5Core.so.5 matches
Binary file amd64/libQt5Core.so.5.8.0 matches
Binary file amd64/libQt5Core.so matches
Binary file libQt5Core.so matches
Binary file libQt5Core.so.5 matches
Binary file libQt5Core.so.5.8 matches
Binary file libQt5Core.so.5.8.0 matches
Binary file libQt5DesignerComponents.so matches
Binary file libQt5DesignerComponents.so.5 matches
Binary file libQt5DesignerComponents.so.5.8 matches
Binary file libQt5DesignerComponents.so.5.8.0 matches

I'm not sure why it doesn't find the symbol

Best regards.
Ben

On 04/12/2018 10:38, benta...@chez.com wrote:


This is not perfect, this is what's left to do :
- 64bits keepassxc and libargon2
- autotype doesn't work, option (menu entries, shortcut) not present

libargon2 compiles out of the box
https://github.com/P-H-C/phc-winner-argon2

cmake :
- cmake linker flags -lsocket -lnsl -lrt -lresolv
- cmake didn't find QT5 config utilities, I had to point it to the 
directory
- did compilation with GCC7 but I think default GCC6 should work as 
well

- due to GCC7, I added -I /usr/gcc/7/include/c++/7.3.0 to CXX_FLAGS

keepassxc patch :
 cut here 
--- src/totp/totp.cpp   2018-08-23 03:25:04.0 +
+++ src/totp/totp.cpp.mod   2018-12-04 09:09:32.413168641 +
@@ -164,7 +164,7 @@
direction = 1;
startpos = 0;

}
-quint32 digitsPower = pow(encoder.alphabet.size(), digits);
+quint32 digitsPower = pow(double (encoder.alphabet.size()), 
digits);


quint64 password = binary % digitsPower;
QString retval(int(digits), encoder.alphabet[0]);
 cut here 

Best regards.
Ben

On 04/12/2018 09:29, Till Wegmüller wrote:


Nice work.

I would also be interested in it.

Could you Publish a patch or put a makefile into OI Userland?

Thanks and Greetings
Till
On 12/03/18 09:28 PM, benta...@chez.com wrote:

Thanks Bob and Alexander, I think I start to understand.

grep digits ../../src/totp/totp.cpp
[...]
quint8 digits = encoder.digits == 0 ? numDigits : encoder.digits;
[...]

From my 30 years old rusty knowledge of C++, this mean that digits is
supposed to be a 'quint8' which is most probably QT version of the 
'int'
and as Bob noticed the pow function expects 'int', 'float', or 
'double'


From Alexander reference, I should have
quint32 digitsPower = pow(encoder.alphabet.size(), int(digits));

In that particular case it was 'encoder.alphabet.size()'  which 
appeared

ambiguous, using 'double (encoder.alphabet.size())' made it. 'digits'
was ok so far

Bottom line is I could compile and execute it, it is nice to have it
native (works with wine).

Thanks both of you.
Best regards.
Ben

On 04/12/2018 03:21, Bob Friesenhahn wrote:

On Mon, 3 Dec 2018, benta...@chez.com wrote:

Hello,
'static QString Totp::generateTotp(QByteArray, quint64, quint8,
quint8)':
/home/ben/tmp/keepassxc-2.3.4/src/totp/totp.cpp:167:62: error: call
of overloaded 'pow(int, quint8&)' is ambiguous
quint32 digitsPower = pow(encoder.alphabet.size(), digits);

What is the declared storage type of the 'digits' argument?  From
reading the header, it appears that it must be of type 'int', 'float',
or 'double'.  Any other type would require a type transformation which
might be ambiguous.

Bob


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

Re: [OpenIndiana-discuss] Compiling KeepassXC on Hipster

[bentahyr]

This is not perfect, this is what's left to do :
- 64bits keepassxc and libargon2
- autotype doesn't work, option (menu entries, shortcut) not present

libargon2 compiles out of the box
https://github.com/P-H-C/phc-winner-argon2

cmake :
- cmake linker flags -lsocket -lnsl -lrt -lresolv
- cmake didn't find QT5 config utilities, I had to point it to the 
directory

- did compilation with GCC7 but I think default GCC6 should work as well
- due to GCC7, I added -I /usr/gcc/7/include/c++/7.3.0 to CXX_FLAGS

keepassxc patch :
 cut here 
--- src/totp/totp.cpp   2018-08-23 03:25:04.0 +
+++ src/totp/totp.cpp.mod   2018-12-04 09:09:32.413168641 +
@@ -164,7 +164,7 @@
 direction = 1;
 startpos = 0;

}
-quint32 digitsPower = pow(encoder.alphabet.size(), digits);
+quint32 digitsPower = pow(double (encoder.alphabet.size()), 
digits);


 quint64 password = binary % digitsPower;
 QString retval(int(digits), encoder.alphabet[0]);
 cut here 

Best regards.
Ben

On 04/12/2018 09:29, Till Wegmüller wrote:


Nice work.

I would also be interested in it.

Could you Publish a patch or put a makefile into OI Userland?

Thanks and Greetings
Till
On 12/03/18 09:28 PM, benta...@chez.com wrote:

Thanks Bob and Alexander, I think I start to understand.

grep digits ../../src/totp/totp.cpp
[...]
quint8 digits = encoder.digits == 0 ? numDigits : encoder.digits;
[...]

From my 30 years old rusty knowledge of C++, this mean that digits is
supposed to be a 'quint8' which is most probably QT version of the 
'int'

and as Bob noticed the pow function expects 'int', 'float', or 'double'

From Alexander reference, I should have
quint32 digitsPower = pow(encoder.alphabet.size(), int(digits));

In that particular case it was 'encoder.alphabet.size()'  which 
appeared

ambiguous, using 'double (encoder.alphabet.size())' made it. 'digits'
was ok so far

Bottom line is I could compile and execute it, it is nice to have it
native (works with wine).

Thanks both of you.
Best regards.
Ben

On 04/12/2018 03:21, Bob Friesenhahn wrote:

On Mon, 3 Dec 2018, benta...@chez.com wrote:

Hello,
'static QString Totp::generateTotp(QByteArray, quint64, quint8,
quint8)':
/home/ben/tmp/keepassxc-2.3.4/src/totp/totp.cpp:167:62: error: call
of overloaded 'pow(int, quint8&)' is ambiguous
quint32 digitsPower = pow(encoder.alphabet.size(), digits);

What is the declared storage type of the 'digits' argument?  From
reading the header, it appears that it must be of type 'int', 'float',
or 'double'.  Any other type would require a type transformation which
might be ambiguous.

Bob


___
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] Compiling KeepassXC on Hipster

[bentahyr]

Thanks Bob and Alexander, I think I start to understand.

grep digits ../../src/totp/totp.cpp
[...]
quint8 digits = encoder.digits == 0 ? numDigits : encoder.digits;
[...]

From my 30 years old rusty knowledge of C++, this mean that digits is 
supposed to be a 'quint8' which is most probably QT version of the 'int' 
and as Bob noticed the pow function expects 'int', 'float', or 'double'


From Alexander reference, I should have
quint32 digitsPower = pow(encoder.alphabet.size(), int(digits));

In that particular case it was 'encoder.alphabet.size()'  which appeared 
ambiguous, using 'double (encoder.alphabet.size())' made it. 'digits' 
was ok so far


Bottom line is I could compile and execute it, it is nice to have it 
native (works with wine).


Thanks both of you.
Best regards.
Ben

On 04/12/2018 03:21, Bob Friesenhahn wrote:


On Mon, 3 Dec 2018, benta...@chez.com wrote:


Hello,
'static QString Totp::generateTotp(QByteArray, quint64, quint8, 
quint8)':
/home/ben/tmp/keepassxc-2.3.4/src/totp/totp.cpp:167:62: error: call of 
overloaded 'pow(int, quint8&)' is ambiguous

quint32 digitsPower = pow(encoder.alphabet.size(), digits);


What is the declared storage type of the 'digits' argument?  From 
reading the header, it appears that it must be of type 'int', 'float', 
or 'double'.  Any other type would require a type transformation which 
might be ambiguous.


Bob


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

[OpenIndiana-discuss] Compiling KeepassXC on Hipster

[bentahyr]

Hello,

I'm trying to compile KeepassXC from source using gcc-7 but I fall onto 
the following issue :


[ 53%] Building CXX object 
src/CMakeFiles/keepassx_core.dir/totp/totp.cpp.o
/home/ben/tmp/keepassxc-2.3.4/src/totp/totp.cpp: In static member 
function 'static QString Totp::generateTotp(QByteArray, quint64, quint8, 
quint8)':
/home/ben/tmp/keepassxc-2.3.4/src/totp/totp.cpp:167:62: error: call of 
overloaded 'pow(int, quint8&)' is ambiguous

 quint32 digitsPower = pow(encoder.alphabet.size(), digits);
  ^
In file included from /usr/include/math.h:32:0,
 from /usr/gcc/7/include/c++/7.3.0/bits/std_abs.h:40,
 from /usr/gcc/7/include/c++/7.3.0/cstdlib:77,
 from /usr/gcc/7/include/c++/7.3.0/bits/stl_algo.h:59,
 from /usr/gcc/7/include/c++/7.3.0/algorithm:62,
 from /usr/lib/qt/5.8/include/QtCore/qglobal.h:108,
 from /home/ben/tmp/keepassxc-2.3.4/src/totp/totp.h:22,
 from 
/home/ben/tmp/keepassxc-2.3.4/src/totp/totp.cpp:19:
/usr/include/iso/math_iso.h:84:15: note: candidate: double 
std::pow(double, double)

 extern double pow __P((double, double));
   ^~~
/usr/include/iso/math_iso.h:161:16: note: candidate: double 
std::pow(double, int)

  inline double pow(double __X, int __Y) { return
^~~
/usr/include/iso/math_iso.h:181:15: note: candidate: float 
std::pow(float, float)

  inline float pow(float __X, float __Y) { return __powf(__X, __Y); }
   ^~~
/usr/include/iso/math_iso.h:182:15: note: candidate: float 
std::pow(float, int)

  inline float pow(float __X, int __Y) { return
   ^~~
/usr/include/iso/math_iso.h:212:21: note: candidate: long double 
std::pow(long double, long double)

  inline long double pow(long double __X, long double __Y) { return
 ^~~
/usr/include/iso/math_iso.h:214:21: note: candidate: long double 
std::pow(long double, int)

  inline long double pow(long double __X, int __Y) { return
 ^~~
gmake[2]: *** [src/CMakeFiles/keepassx_core.dir/build.make:1545: 
src/CMakeFiles/keepassx_core.dir/totp/totp.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:230: 
src/CMakeFiles/keepassx_core.dir/all] Error 2

gmake: *** [Makefile:141: all] Error 2

I think KeepassXC code expect pow coming from 
/usr/gcc/7/include/c++/7.3.0/complex.h rather than 
/usr/include/iso/math_iso.h


I tried to shuffle around the -I on the compiler command line but it 
doesn't seem to have any impact


Compile command is :

cd /home/franck/tmp/keepassxc-2.3.4/build/src && /usr/bin/g++-7  
-DKEEPASSX_BUILDING_CORE -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB 
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG 
-DQT_NO_EXCEPTIONS -DQT_STRICT_ITERATORS -DQT_WIDGETS_LIB 
-I/home/franck/tmp/keepassxc-2.3.4/build/src/keepassx_core_autogen/include 
-I/home/franck/tmp/keepassxc-2.3.4/src 
-I/home/franck/tmp/keepassxc-2.3.4/build/src 
-I/home/franck/tmp/keepassxc-2.3.4/src/zxcvbn -isystem 
/usr/lib/qt/5.8/include -isystem /usr/lib/qt/5.8/include/QtCore -isystem 
/usr/lib/qt/5.8/./mkspecs/solaris-g++ -isystem 
/usr/lib/qt/5.8/include/QtWidgets -isystem /usr/lib/qt/5.8/include/QtGui 
-isystem /usr/lib/qt/5.8/include/QtNetwork -isystem 
/usr/lib/qt/5.8/include/QtConcurrent -isystem 
/usr/lib/qt/5.8/include/QtDBus -fno-common -Wall -Wextra -Wundef 
-Wpointer-arith -Wno-long-long -Wformat=2 -Wmissing-format-attribute 
-fvisibility=hidden -fvisibility-inlines-hidden -fstack-protector-strong 
-fno-exceptions -fno-rtti -Wnon-virtual-dtor -Wold-style-cast 
-Woverloaded-virtual -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 
-Werror=format-security -Wcast-align -std=c++11 -O3 -DNDEBUG   -fPIC 
-std=gnu++11 -o CMakeFiles/keepassx_core.dir/totp/totp.cpp.o -c 
/home/franck/tmp/keepassxc-2.3.4/src/totp/totp.cppEPASSX_BUILDING_CORE 
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB 
-DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
-DQT_STRICT_ITERATORS -DQT_WIDGETS_LIB -I/usr/gcc/7/include/c++/7.3.0 
-I/home/franck/tmp/keepassxc-2.3.4/build/src/keepassx_core_autogen/include 
-I/home/franck/tmp/keepassxc-2.3.4/src 
-I/home/franck/tmp/keepassxc-2.3.4/build/src 
-I/home/franck/tmp/keepassxc-2.3.4/src/zxcvbn -isystem 
/usr/lib/qt/5.8/include -isystem /usr/lib/qt/5.8/include/QtCore -isystem 
/usr/lib/qt/5.8/./mkspecs/solaris-g++ -isystem 
/usr/lib/qt/5.8/include/QtWidgets -isystem /usr/lib/qt/5.8/include/QtGui 
-isystem /usr/lib/qt/5.8/include/QtNetwork -isystem 
/usr/lib/qt/5.8/include/QtConcurrent -isystem 
/usr/lib/qt/5.8/include/QtDBus -fno-common -Wall -Wextra -Wundef 
-Wpointer-arith -Wno-long-long -Wformat=2 -Wmissing-format-attribute 
-fvisibility=hidden -fvisibility-inlines-hidden -fstack-protector-strong 
-fno-exceptions -fno-rtti -Wnon-virtual-dtor -Wold-style-cast 
-Woverloaded-virtual -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 
-Werror=f

Re: [OpenIndiana-discuss] Wine and recent Openindiana

[bentahyr]

As additional note, there is a bug file with wine. The comment for the 
Wine team leader is "It sounds like LDT support got broken somehow. If 
you haven't done that already, you should probably file a bug against 
the OpenIndiana kernel."


I found an article (https://lwn.net/Articles/741878/) stating that " On 
current Linux systems, the LDT is almost unused but some applications 
(Wine, for example) still need it. When it is used, the LDT must be 
available to both kernel and user space, but it must live in kernel 
space."


I'm not sure how it is tackled down in illumos kernel as it is way 
beyond my comprehension level, 'just throwing stuff as brainstorming 
information.


Should I open a bug report on illumos bugtracker ?

Best regards.
Ben

Le 2018-05-29 12:35, benta...@chez.com a écrit :

I recompiled wine (3.9) with -ggdb and -O0
Here is the output (using WINEDEBUG=+all env)

$ gdb --args /opt/wine/bin/wine winefile
GNU gdb (GDB) 7.10.1
[...]
Reading symbols from /opt/wine/bin/wine...done.
(gdb) r
Starting program: /opt/wine/bin/wine winefile
[Thread debugging using libthread_db enabled]
[New Thread 1 (LWP 1)]
trace:virtual:NtAllocateVirtualMemory  7ffe 0001 3000 
0004

trace:virtual:VIRTUAL_DumpView View: 7ffe -
7ffetrace:virtual:VIRTUAL_DumpView  (valloc)
trace:virtual:VIRTUAL_DumpView   7ffe - 7ffe c-rw-
trace:virtual:NtAllocateVirtualMemory  0 0230 101000 
0004

trace:virtual:map_view got mem in reserved area 3000-4000
trace:virtual:VIRTUAL_DumpView View: 3000 -
3ffftrace:virtual:VIRTUAL_DumpView  (valloc)
trace:virtual:VIRTUAL_DumpView   3000 - 3fff c-rw-
trace:ntdll:RtlInitializeBitMap (7ffddf6c,3044,64)
trace:ntdll:RtlInitializeBitMap (7ffddf74,3154,1024)
trace:ntdll:RtlInitializeBitMap (7ffddf7c,321c,128)
trace:ntdll:RtlSetBits (7ffddf6c,0,1)
trace:ntdll:RtlSetBits (7ffddf7c,0,1)
trace:virtual:NtAllocateVirtualMemory  0 4000 101000 
0004

trace:virtual:map_view got mem in reserved area 3fff8000-3fffc000
trace:virtual:VIRTUAL_DumpView View: 3fff8000 -
3fffbffftrace:virtual:VIRTUAL_DumpView  (valloc)
trace:virtual:VIRTUAL_DumpView   3fff8000 - 3fffbfff c-rw-

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1 (LWP 1)]
0xfeda904d in wine_set_fs (val=4103) at 
../../include/wine/library.h:188

188 __DEFINE_SET_SEG(fs)
(gdb) bt full
#0  0xfeda904d in wine_set_fs (val=4103) at 
../../include/wine/library.h:188

No locals.
#1  wine_ldt_init_fs (sel=4103, entry=0x8046ac0) at ldt.c:433
No locals.
#2  0x7ff7e6ca in signal_init_thread (teb=0x3fff8000) at 
signal_i386.c:2319

fpu_cw = 639
thread_data = 0x3fff81d4
fs_entry = {LimitLow = 4095, BaseLow = 32768, HighWord =
{Bytes = {BaseMid = 255 '\377',
  Flags1 = 243 '\363', Flags2 = 64 '@', BaseHi = 63 '?'},
Bits = {BaseMid = 255,
  Type = 19, Dpl = 3, Pres = 1, LimitHi = 0, Sys = 0,
Reserved_0 = 0, Default_Big = 1,
  Granularity = 0, BaseHi = 63}}}
ss = {ss_sp = 0x3fff9000, ss_size = 12288, ss_flags = 0}
#3  0x7ff86f6d in thread_init () at thread.c:360
teb = 0x3fff8000
addr = 0x3000
suspend = 256
size = 4096
info_size = 1
exe_file = 0x0
now = {u = {LowPart = 134507336, HighPart = -16954553},
{LowPart = 134507336,
HighPart = -16954553}, QuadPart = -72819250518791352}
status = 0
thread_data = 0x3fff81fc
debug_info = {str_pos = 0x0, out_pos = 0x0, strings = '\000'
,
  output = '\000' }
#4  0x7ff54454 in __wine_process_init () at loader.c:3440
kernel32W = {107, 101, 114, 110, 101, 108, 51, 50, 46, 100, 
108, 108, 0}

wm = 0x8046ba8
status = -19225578
func_name = {Length = 27560, MaximumLength = 2052, Buffer =
0xfef525d4 "\264"}
init_func = 0xfeda97af 
#5  0xfedaa427 in wine_init (argc=2, argv=0x8047044, error=0x8046bcc
"", error_size=1024)
at loader.c:979
context = {index = 3, buffer = 0x8a1cf98 "", name = 0x8a1cfb4
"/ntdll.dll.so", namelen = 10,
  win16 = 0}
path = 0x8a1cfa2 "/opt/wine/lib/wine/ntdll.dll.so"
ntdll = 0xfebc04f0
init_func = 0x7ff5443d <__wine_process_init>
#6  0x0805149c in main (argc=2, argv=0x8047044) at main.c:258
error =
"\000\000\000\000\000\000\000\000\364\344\374\376\250\260\377\376H\211\314\376@s\324\376",
'\000' ,
"\002\000\000\000\000\000\000\000@s\324\376\004\000\000\000\200\231\324\376\000\000\000\000\000\000\000\000\000
\324\376@*\275\376\000\000\000\000\070l\004\b\337\224\314\376@s\324\376\000\000\000\000\001\000\000\000S\230\313\376\000
\324\376@*\275\376xl\004\bR\260\314\376@*\275\376\000\000\000\000\210l\004\bk\274\314\376@s\324\376\000\000\000\000\300s\324\376\000s\324\376@*\275\376\000\000\000\000\210l\004\b\250\260\377\376\200\000\000\000\020\310\377\376\230l\004\b\221\233\374\376\003\000\000\000\020\310\377\376\250l\0

Re: [OpenIndiana-discuss] Wine and recent Openindiana

[bentahyr]

I recompiled wine (3.9) with -ggdb and -O0
Here is the output (using WINEDEBUG=+all env)

$ gdb --args /opt/wine/bin/wine winefile
GNU gdb (GDB) 7.10.1
[...]
Reading symbols from /opt/wine/bin/wine...done.
(gdb) r
Starting program: /opt/wine/bin/wine winefile
[Thread debugging using libthread_db enabled]
[New Thread 1 (LWP 1)]
trace:virtual:NtAllocateVirtualMemory  7ffe 0001 3000 
0004
trace:virtual:VIRTUAL_DumpView View: 7ffe - 
7ffetrace:virtual:VIRTUAL_DumpView  (valloc)

trace:virtual:VIRTUAL_DumpView   7ffe - 7ffe c-rw-
trace:virtual:NtAllocateVirtualMemory  0 0230 101000 
0004

trace:virtual:map_view got mem in reserved area 3000-4000
trace:virtual:VIRTUAL_DumpView View: 3000 - 
3ffftrace:virtual:VIRTUAL_DumpView  (valloc)

trace:virtual:VIRTUAL_DumpView   3000 - 3fff c-rw-
trace:ntdll:RtlInitializeBitMap (7ffddf6c,3044,64)
trace:ntdll:RtlInitializeBitMap (7ffddf74,3154,1024)
trace:ntdll:RtlInitializeBitMap (7ffddf7c,321c,128)
trace:ntdll:RtlSetBits (7ffddf6c,0,1)
trace:ntdll:RtlSetBits (7ffddf7c,0,1)
trace:virtual:NtAllocateVirtualMemory  0 4000 101000 
0004

trace:virtual:map_view got mem in reserved area 3fff8000-3fffc000
trace:virtual:VIRTUAL_DumpView View: 3fff8000 - 
3fffbffftrace:virtual:VIRTUAL_DumpView  (valloc)

trace:virtual:VIRTUAL_DumpView   3fff8000 - 3fffbfff c-rw-

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1 (LWP 1)]
0xfeda904d in wine_set_fs (val=4103) at ../../include/wine/library.h:188
188 __DEFINE_SET_SEG(fs)
(gdb) bt full
#0  0xfeda904d in wine_set_fs (val=4103) at 
../../include/wine/library.h:188

No locals.
#1  wine_ldt_init_fs (sel=4103, entry=0x8046ac0) at ldt.c:433
No locals.
#2  0x7ff7e6ca in signal_init_thread (teb=0x3fff8000) at 
signal_i386.c:2319

fpu_cw = 639
thread_data = 0x3fff81d4
fs_entry = {LimitLow = 4095, BaseLow = 32768, HighWord = {Bytes 
= {BaseMid = 255 '\377',
  Flags1 = 243 '\363', Flags2 = 64 '@', BaseHi = 63 '?'}, 
Bits = {BaseMid = 255,
  Type = 19, Dpl = 3, Pres = 1, LimitHi = 0, Sys = 0, 
Reserved_0 = 0, Default_Big = 1,

  Granularity = 0, BaseHi = 63}}}
ss = {ss_sp = 0x3fff9000, ss_size = 12288, ss_flags = 0}
#3  0x7ff86f6d in thread_init () at thread.c:360
teb = 0x3fff8000
addr = 0x3000
suspend = 256
size = 4096
info_size = 1
exe_file = 0x0
now = {u = {LowPart = 134507336, HighPart = -16954553}, {LowPart 
= 134507336,

HighPart = -16954553}, QuadPart = -72819250518791352}
status = 0
thread_data = 0x3fff81fc
debug_info = {str_pos = 0x0, out_pos = 0x0, strings = '\000' 
,

  output = '\000' }
#4  0x7ff54454 in __wine_process_init () at loader.c:3440
kernel32W = {107, 101, 114, 110, 101, 108, 51, 50, 46, 100, 108, 
108, 0}

wm = 0x8046ba8
status = -19225578
func_name = {Length = 27560, MaximumLength = 2052, Buffer = 
0xfef525d4 "\264"}

init_func = 0xfeda97af 
#5  0xfedaa427 in wine_init (argc=2, argv=0x8047044, error=0x8046bcc "", 
error_size=1024)

at loader.c:979
context = {index = 3, buffer = 0x8a1cf98 "", name = 0x8a1cfb4 
"/ntdll.dll.so", namelen = 10,

  win16 = 0}
path = 0x8a1cfa2 "/opt/wine/lib/wine/ntdll.dll.so"
ntdll = 0xfebc04f0
init_func = 0x7ff5443d <__wine_process_init>
#6  0x0805149c in main (argc=2, argv=0x8047044) at main.c:258
error = 
"\000\000\000\000\000\000\000\000\364\344\374\376\250\260\377\376H\211\314\376@s\324\376", 
'\000' , 
"\002\000\000\000\000\000\000\000@s\324\376\004\000\000\000\200\231\324\376\000\000\000\000\000\000\000\000\000 
\324\376@*\275\376\000\000\000\000\070l\004\b\337\224\314\376@s\324\376\000\000\000\000\001\000\000\000S\230\313\376\000 
\324\376@*\275\376xl\004\bR\260\314\376@*\275\376\000\000\000\000\210l\004\bk\274\314\376@s\324\376\000\000\000\000\300s\324\376\000s\324\376@*\275\376\000\000\000\000\210l\004\b\250\260\377\376\200\000\000\000\020\310\377\376\230l\004\b\221\233\374\376\003\000\000\000\020\310\377\376\250l\004\b\371!\374\376\003\000\000\000"...

i = 134551599


Best regards.
Ben


Le 2018-05-22 07:01, Alexander Pyhalov a écrit :
On 21.05.2018 19:23, Apostolos Syropoulos via openindiana-discuss 
wrote:

Hi I used to compile Wine and it used to work quite well but recent
update to OpenIndiana nailed it quite hard as it seg fault's  for
anything more than --version.


I would like to confirm that wine-2.21 worked just fine before 
upgrading

but now it reports:

Segmentation Fault (core dumped)
In my case I have used gdb and the result is:

(gdb) bt full
#0  0xfeda8f08 in wine_ldt_init_fs () from 
/opt/gnu/wine/lib/libwine.so.1

No symbol table info available.
#1  0x7ff7ddec in signal_init_thread ()
   from /opt/gnu/wine/lib/wine/ntdll.dll.so
No symbol table info available

Re: [OpenIndiana-discuss] Wine and recent Openindiana

[bentahyr]

Yes, thanks for the work by the OI team, it is quite easy to compile 
recent version.


For wine 3.8, just use the following patch :
= BEGIN
--- dlls/ntdll/signal_i386.c2016-12-24 08:52:13.0 +1300
+++ dlls/ntdll/signal_i386.c2017-01-03 15:34:44.137167786 +1300
@@ -326,6 +326,10 @@
 #define gregs regs
 #endif

+#if defined(__sun) && defined(__SVR4)
+#include 
+#endif
+
 #define EAX_sig(context) ((context)->uc_mcontext.gregs[EAX])
 #define EBX_sig(context) ((context)->uc_mcontext.gregs[EBX])
 #define ECX_sig(context) ((context)->uc_mcontext.gregs[ECX])
--- dlls/ntdll/virtual.c2018-05-12 06:20:21.0 +
+++ dlls/ntdll/virtual.c2018-05-22 14:00:17.283013377 +
@@ -1853,7 +1853,7 @@
  */
 void virtual_get_system_info( SYSTEM_BASIC_INFORMATION *info )
 {
-#ifdef HAVE_SYSINFO
+#if defined(HAVE_SYSINFO) && !defined(__sun)
 struct sysinfo sinfo;
 #endif

@@ -1862,7 +1862,7 @@
 info->PageSize= page_size;
 info->MmLowestPhysicalPage= 1;
 info->MmHighestPhysicalPage   = 0x7fff / page_size;
-#ifdef HAVE_SYSINFO
+#if defined(HAVE_SYSINFO) && !defined(__sun)
 if (!sysinfo(&sinfo))
 {
 ULONG64 total = (ULONG64)sinfo.totalram * sinfo.mem_unit;
= END

then :
 make sure you have /usr/gnu/bin first in you PATH
 $ ./configure CFLAGS=-std=gnu99 CXXFLAGS=-std=gnu99 LDFLAGS=-lumem 
--prefix=/opt/wine

 $ gmake -j4
 # gmake install (as root)
 $ export UMEM_OPTIONS=backend=mmap

And enjoy.

If you want wine staging, apply the staging patches first then the above 
patch.
This only compile 32bits, I haven't find the way to compile the 64bits 
version (in between the libs path in the linux world and the solaris 
world and the 64bits switches).


Best regards.
Ben

Le 2018-05-23 23:24, openbabel a écrit :

Has anyone managed to compile the latest versions 3.x of wine ?

regards,

Robert




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

Re: [OpenIndiana-discuss] Wine and recent Openindiana

[bentahyr]

I did the update and I can say that wine (3.0) works.

$ uname -a
SunOS kamahi 5.11 OS-6906-0-g1d9a8ab82e i86pc i386 i86pc Solaris

It's interesting as I tried to disable KPTI (in /boot/conf.d/) but 
couln't run wine.


Best regards.
Ben


Le 2018-05-21 20:42, Alexander Pyhalov a écrit :

On 05/21/18 10:43 AM, Alexander Pyhalov wrote:


Hi. The issue seems similar to sbcl one. I'd blame KPTI, but this need 
confirming. Can you check it on illumos-gate prior to KPTI changes?




I've published illumos-gate prior to KPTI changes here -
http://buildzone.oi-build.r61.net:8151/en/index.shtml

You can add on-nightly preferred publisher, make openindiana.org
publisher non-sticky and try updating and see if it fixes wine issues.


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

[OpenIndiana-discuss] Wine and recent Openindiana

[bentahyr]

Hi I used to compile Wine and it used to work quite well but recent 
update to OpenIndiana nailed it quite hard as it seg fault's  for 
anything more than --version.


$ winecfg
Segmentation Fault (core dumped)

Update date | illumos v. | result
2018-03-28  | 243bebc0df | ok
2018-05-06  | 4ff15898b7 | ko
2018-05-18  | 8dfe5547fb | ko

$ dbx /opt/wine/bin/wine core
Reading wine
core file header read successfully
Reading ld.so.1
Reading libwine.so.1.0
Reading libsocket.so.1
Reading libnsl.so.1
Reading libc.so.1
Reading ntdll.dll.so
Reading libm.so.2
Reading libmd.so.1
Reading libmp.so.2
program terminated by signal SEGV (no mapping at the fault address)
0xfeda8ee8: wine_ldt_init_fs+0x0049:movw %eax,%fs
(dbx)

$ mdb /opt/wine/bin/wine core
Loading modules: [ libc.so.1 ld.so.1 ]

$C
08046aa8 libwine.so.1.0`wine_ldt_init_fs+0x49(1007, 8046ad0, 8046ae8, 
7ff7f98c)
08046ae8 ntdll.dll.so`signal_init_thread+0xb8(3fff8000, 0, 8046b58, 
7ff87e20)
08046b58 ntdll.dll.so`thread_init+0x33d(8063de8, 0, 7ff5680c, feda964a, 
8046bb8, fef530b4)
08046b88 ntdll.dll.so`__wine_process_init+0x17(3, 8063de8, 8063e04, a, 
0, 7ff5680c)

08046bb8 libwine.so.1.0`wine_init+0x135(2, 8047054, 8046bdc, 400)
08046fe8 main+0x112(8046fec, fed5f2c8, 8047028, 8051168, 2, 8047054)
08047028 _start_crt+0x97(2, 8047054, fefd1c00, 0, 0, 0)
08047048 _start+0x1a(2, 8047188, 804719b, 0, 80471a7, 8047aa9)

Rebuilding wine with the new "environment" doesn't change the outcome.
I was wondering if it was related to the KPTI code but starting with 
KPTI disable doesn't change things.
So I come to see if anyone has an idea how to approach this as I don't 
know how to interpret the debuggers output.


Best regards.
Ben

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

[OpenIndiana-discuss] Audio with multiple devices

[bentahyr]

Hi

I've been fiddling with sound and discovered that I can use a USB headset so 
the Logitech H650e works great.
If I understand correctly :
- Pulseaudio is configured to use /dev/audio (sources/sink)
- Solaris audio /dev/audio point to the proper /dev/sound/[Device number]

What I'd like to do is, use:
- the mic input from a usb device
- the output using the onboard sound card

What are my options ? 
I could configure pulseaudio to expose multiple device ? like sink using 
/dev/audio and source using /dev/sound/1
What about application using directly OSS drivers (i.e. VirtualBox) ?

Best regards.
Ben

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

[OpenIndiana-discuss] Wine and 3D applications

[bentahyr]

Hi,
Just to let you know that from a comment from a bug open on winehq 
(https://bugs.winehq.org/show_bug.cgi?id=40783), I was able to run 3D 
applications including a few (old) Windows games.
You just have to run using the folowing env :
$ LD_PRELOAD=libumem.so UMEM_OPTIONS=backend=mmap wine whatever.exe

Test and enjoy.
Best regards.
Ben

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

Re: [OpenIndiana-discuss] Cisco IPSec VPN

[bentahyr]

Hi all,
Ok with match=/dev/tun and match=/dev/tap in zone configuration, it working 
like a charm.
I can connect to a Cisco VPN from the NGZ and keep the OpenVPN server running 
(and serving clients) in the GZ.

Thanks for your great work.
Something that I notice is when I stop the openconnect process, it (vpnc?) 
doesn't restore the /etc/resolv.conf which ends up in a non functional name 
resolution in the NGZ.
I'll try to check if there is a way to tell "before quitting, restore 
resolv.conf"


Superb!

Best regards.
Ben

- Mail original -
De: "Jim Klimov" 
À: "Discussion list for OpenIndiana" , 
"Adam Števko" 
Envoyé: Dimanche 27 Novembre 2016 06:52:59
Objet: Re: [OpenIndiana-discuss] Cisco IPSec VPN

26 ноября 2016 г. 14:46:17 CET, "Adam Števko"  пишет:
>Hi,
>
>yes, they can. However, you can’t use the same tun device name e.g.
>tun0 in the GZ and NGZ as tun module is not zone aware. See
>https://github.com/joyent/smartos-live/issues/626
>.
>
>Adam
>
>> On Nov 25, 2016, at 8:15 AM, Jim Klimov  wrote:
>> 
>> 24 ноября 2016 г. 23:30:06 CET, benta...@chez.com пишет:
>>> Ok, I see.
>>> If I follow the SFE way, could I have an issue running OpenVPN
>server
>>> over TUN on GZ and wanting to run Openconnect client over TUN in NGZ
>?
>>> Like the device /dev/tun is both used in GZ and NGZ.
>>> 
>>> Best regards.
>>> Ben
>>> 
>>> - Mail original -
>>> De: "Thomas Wagner" 
>>> À: "Discussion list for OpenIndiana"
>>> 
>>> Envoyé: Vendredi 25 Novembre 2016 10:16:51
>>> Objet: Re: [OpenIndiana-discuss] Cisco IPSec VPN
>>> 
>>> For SFE we've solved this by just adding the driver modules to the
>NGZ
>>> as dead files. So there is no install contraint regarding
>zones-type.
>>> That way the IPS dependency just matches in any case.
>>> 
>>> I use a driver match rule in the NGZ to get tun passed through:
>>> 
>>> 
>>> Thomas
>>> 
>>> On Thu, Nov 24, 2016 at 09:15:11PM +0100, benta...@chez.com wrote:
 By the way, is there a way to install openconnect in a zone ?
 I can't seem to get it running because tap driver doesn't want to
>>> install :
 
 vpnzone# pkg install openconnect
 Creating Plan (Running solver): |
 pkg install: No matching version of network/openconnect can be
>>> installed:
  Reject: 
>>>
>pkg://openindiana.org/network/openconnect@7.7.20161105-2016.1.0.0:20161119T064832Z
  Reason:  No version matching 'require' dependency
>>> driver/network/tap can be installed

Reject: 
>>>
>pkg://openindiana.org/driver/network/tap@1.3.2-2016.0.0.0:20160730T021914Z
Reason:  This version is excluded by installed incorporation
>>> consolidation/userland/userland-incorporation@0.5.11-2016.1.0.7919
Reject: 
>>>
>pkg://openindiana.org/driver/network/tap@1.3.2-2016.1.0.1:20161124T055026Z
 
>>>
>pkg://openindiana.org/driver/network/tap@1.3.2-2016.1.0.1:20161124T172113Z
Reason:  Package supports image variant
>>> variant.opensolaris.zone=[global] but doesn't support this image's
>>> variant.opensolaris.zone (nonglobal)

  Reject: 
>>>
>pkg://openindiana.org/network/openconnect@7.7.20161105-2016.1.0.0:20161119T114634Z
  Reason:  No version matching 'require' dependency
>>> driver/network/tap can be installed
 
 
 Best regards.
 Ben
 
 - Mail original -
 De: "Jim Klimov" 
 À: "Discussion list for OpenIndiana"
>>> , "Andrey Sokolov"
>>> 
 Envoyé: Vendredi 25 Novembre 2016 07:07:36
 Objet: Re: [OpenIndiana-discuss] Cisco IPSec VPN
 
 16 но�бр� 2016 г. 14:02:44 CET, Andrey Sokolov
>>>  пишет:
> Hi!
> I use
 

>http://pkg.openindiana.org/sfe/info/0/system%2Fnetwork%2Fvpnc%400.5.3%2C5.11-0.151.1.5%3A20120819T093748Z
> 
> 2016-11-14 15:35 GMT+03:00 Jim Klimov :
> 
>> Hi all,
>> 
>> I am faced with a prospect of connecting to a remote network
>>> behind
> Cisco
>> IPSec VPN (the one with user, password, group and shared keys;
>>> will
> be
>> practically trying sometime soon this week). Should I expect it
>to
> work in
>> OI Hipster out of the box? Are there docs/blogs on it, or would
> Oracle docs
>> I found so far (some hints about conf files and then ipadm tun
> commands) be
>> relevant here? Or should I try some other OS right away?
>> 
>> TIA, Jim
>> --
>> Typos courtesy of K-9 Mail on my Samsung Android
>> 

 Thanks,
 
 In the end vpnc did work for me; also I saw that openconnect could
>>> connect to Juniper/Cisco SSL VPNs... so I couldn't resist and now
>both
>>> are packaged in OI/Hipster userland ;)
 
 Thanks,
 Jim
 --
 Typos courtesy of K-9 Mail on my Samsung Android
 
 
>>> 
>>> -- 
>>> -- 
>>> Thomas Wagner
>>> 

>> 
>> I think this coexistence should not be a problem - several progra

Re: [OpenIndiana-discuss] Cisco IPSec VPN

[bentahyr]

Ok, I see.
If I follow the SFE way, could I have an issue running OpenVPN server over TUN 
on GZ and wanting to run Openconnect client over TUN in NGZ ? Like the device 
/dev/tun is both used in GZ and NGZ.

Best regards.
Ben

- Mail original -
De: "Thomas Wagner" 
À: "Discussion list for OpenIndiana" 
Envoyé: Vendredi 25 Novembre 2016 10:16:51
Objet: Re: [OpenIndiana-discuss] Cisco IPSec VPN

For SFE we've solved this by just adding the driver modules to the NGZ
as dead files. So there is no install contraint regarding zones-type.
That way the IPS dependency just matches in any case.

I use a driver match rule in the NGZ to get tun passed through:


Thomas

On Thu, Nov 24, 2016 at 09:15:11PM +0100, benta...@chez.com wrote:
> By the way, is there a way to install openconnect in a zone ?
> I can't seem to get it running because tap driver doesn't want to install :
> 
> vpnzone# pkg install openconnect
> Creating Plan (Running solver): |
> pkg install: No matching version of network/openconnect can be installed:
>   Reject:  
> pkg://openindiana.org/network/openconnect@7.7.20161105-2016.1.0.0:20161119T064832Z
>   Reason:  No version matching 'require' dependency driver/network/tap can be 
> installed
> 
> Reject:  
> pkg://openindiana.org/driver/network/tap@1.3.2-2016.0.0.0:20160730T021914Z
> Reason:  This version is excluded by installed incorporation 
> consolidation/userland/userland-incorporation@0.5.11-2016.1.0.7919
> Reject:  
> pkg://openindiana.org/driver/network/tap@1.3.2-2016.1.0.1:20161124T055026Z
>  
> pkg://openindiana.org/driver/network/tap@1.3.2-2016.1.0.1:20161124T172113Z
> Reason:  Package supports image variant variant.opensolaris.zone=[global] 
> but doesn't support this image's variant.opensolaris.zone (nonglobal)
> 
>   Reject:  
> pkg://openindiana.org/network/openconnect@7.7.20161105-2016.1.0.0:20161119T114634Z
>   Reason:  No version matching 'require' dependency driver/network/tap can be 
> installed
> 
> 
> Best regards.
> Ben
> 
> - Mail original -
> De: "Jim Klimov" 
> À: "Discussion list for OpenIndiana" , 
> "Andrey Sokolov" 
> Envoyé: Vendredi 25 Novembre 2016 07:07:36
> Objet: Re: [OpenIndiana-discuss] Cisco IPSec VPN
> 
> 16 но�бр� 2016 г. 14:02:44 CET, Andrey Sokolov 
>  пишет:
> >Hi!
> >I use
> >http://pkg.openindiana.org/sfe/info/0/system%2Fnetwork%2Fvpnc%400.5.3%2C5.11-0.151.1.5%3A20120819T093748Z
> >
> >2016-11-14 15:35 GMT+03:00 Jim Klimov :
> >
> >> Hi all,
> >>
> >> I am faced with a prospect of connecting to a remote network behind
> >Cisco
> >> IPSec VPN (the one with user, password, group and shared keys; will
> >be
> >> practically trying sometime soon this week). Should I expect it to
> >work in
> >> OI Hipster out of the box? Are there docs/blogs on it, or would
> >Oracle docs
> >> I found so far (some hints about conf files and then ipadm tun
> >commands) be
> >> relevant here? Or should I try some other OS right away?
> >>
> >> TIA, Jim
> >> --
> >> Typos courtesy of K-9 Mail on my Samsung Android
> >>
> >> ___
> >> 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
> 
> Thanks,
> 
> In the end vpnc did work for me; also I saw that openconnect could connect to 
> Juniper/Cisco SSL VPNs... so I couldn't resist and now both are packaged in 
> OI/Hipster userland ;)
> 
> Thanks,
> Jim
> --
> Typos courtesy of K-9 Mail on my Samsung Android
> 
> ___
> 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
> 

-- 
-- 
Thomas Wagner


Service rund um UNIX(TM), Wagner Network Services, Thomas Wagner
Solaris(TM), Linux(TM)Eschenweg 21, 89174 Altheim, Germany
Windows(TM)   TEL: +49-731-9807799, FAX: +49-731-9807711
Telekommunikation, LAN,   MOBILE/CELL: +49-171-6135989
Internet-Service, Elektronik  EMAIL: wag...@wagner-net.com

___
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] Cisco IPSec VPN

[bentahyr]

By the way, is there a way to install openconnect in a zone ?
I can't seem to get it running because tap driver doesn't want to install :

vpnzone# pkg install openconnect
Creating Plan (Running solver): |
pkg install: No matching version of network/openconnect can be installed:
  Reject:  
pkg://openindiana.org/network/openconnect@7.7.20161105-2016.1.0.0:20161119T064832Z
  Reason:  No version matching 'require' dependency driver/network/tap can be 
installed

Reject:  
pkg://openindiana.org/driver/network/tap@1.3.2-2016.0.0.0:20160730T021914Z
Reason:  This version is excluded by installed incorporation 
consolidation/userland/userland-incorporation@0.5.11-2016.1.0.7919
Reject:  
pkg://openindiana.org/driver/network/tap@1.3.2-2016.1.0.1:20161124T055026Z
 
pkg://openindiana.org/driver/network/tap@1.3.2-2016.1.0.1:20161124T172113Z
Reason:  Package supports image variant variant.opensolaris.zone=[global] 
but doesn't support this image's variant.opensolaris.zone (nonglobal)

  Reject:  
pkg://openindiana.org/network/openconnect@7.7.20161105-2016.1.0.0:20161119T114634Z
  Reason:  No version matching 'require' dependency driver/network/tap can be 
installed


Best regards.
Ben

- Mail original -
De: "Jim Klimov" 
À: "Discussion list for OpenIndiana" , 
"Andrey Sokolov" 
Envoyé: Vendredi 25 Novembre 2016 07:07:36
Objet: Re: [OpenIndiana-discuss] Cisco IPSec VPN

16 ноября 2016 г. 14:02:44 CET, Andrey Sokolov  пишет:
>Hi!
>I use
>http://pkg.openindiana.org/sfe/info/0/system%2Fnetwork%2Fvpnc%400.5.3%2C5.11-0.151.1.5%3A20120819T093748Z
>
>2016-11-14 15:35 GMT+03:00 Jim Klimov :
>
>> Hi all,
>>
>> I am faced with a prospect of connecting to a remote network behind
>Cisco
>> IPSec VPN (the one with user, password, group and shared keys; will
>be
>> practically trying sometime soon this week). Should I expect it to
>work in
>> OI Hipster out of the box? Are there docs/blogs on it, or would
>Oracle docs
>> I found so far (some hints about conf files and then ipadm tun
>commands) be
>> relevant here? Or should I try some other OS right away?
>>
>> TIA, Jim
>> --
>> Typos courtesy of K-9 Mail on my Samsung Android
>>
>> ___
>> 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

Thanks,

In the end vpnc did work for me; also I saw that openconnect could connect to 
Juniper/Cisco SSL VPNs... so I couldn't resist and now both are packaged in 
OI/Hipster userland ;)

Thanks,
Jim
--
Typos courtesy of K-9 Mail on my Samsung Android

___
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] Fwd: TEST-pkg available: Hipster's future VirtualBox-5.1.6-SunOS-amd64-r110634.pkg

[bentahyr]

I did some tests with 2 different USB Webcams.
To sum up, USB passthrough didn't work but webcams abstraction from virtualbox 
worked for the logitech one

== Microsoft LifeCam Studio
Works fine with Cheese
ben@whitestar:~$ vboxm list usbhost
Host USB Devices:

UUID:   538da37f-1ea6-4226-bd66-17cdd14e738e
VendorId:   0x045e (045E)
ProductId:  0x0772 (0772)
Revision:   1.19 (0119)
Port:   4
USB version/speed:  2/High
Manufacturer:   Microsoft
Product:Microsoft  LifeCam Studio(TM)
Address:0x45e:0x772:275:/pci@0,0/pci1028,21e@1d,7/miscellaneous@4
Current State:  Busy

But bizarrely it isn't recognized by Virtualbox webcam abstraction :
ben@whitestar:~$ vboxm list webcams
Video Input Devices: 1
 ""

An empty item appears in the GUI that if I select crashes all the VMs running!!!

Passthrough fails with an error message (see next one for error message)
But device seems to be captured :
ben@whitestar:/var/adm$ vboxm list usbhost
Host USB Devices:

UUID:   d570fbe8-c5a4-4ad0-8c04-b727fd1e0dca
VendorId:   0x045e (045E)
ProductId:  0x0772 (0772)
Revision:   1.19 (0119)
Port:   4
USB version/speed:  2/High
Manufacturer:   Microsoft
Product:Microsoft  LifeCam Studio(TM)
Address:0x45e:0x772:275:/pci@0,0/pci1028,21e@1d,7/miscellaneous@4
Current State:  Captured

== Logitech C270
Works fine with Cheese
ben@whitestar:~$ vboxm list usbhost
Host USB Devices:

UUID:   3fc67bad-5706-4417-bd26-4252d158df6c
VendorId:   0x046d (046D)
ProductId:  0x0825 (0825)
Revision:   0.18 (0018)
Port:   8
USB version/speed:  2/High
Manufacturer:   Logitech,Inc.
Product:WebcamC270
SerialNumber:   F2746AD0
Address:0x46d:0x825:18:/pci@0,0/pci1028,21e@1d,7/miscellaneous@8
Current State:  Busy

ben@whitestar:~$ vboxm list webcams
Video Input Devices: 1
.1 "Generic USB videoclass device"
/dev/video0

Passtrough fails with the same error message :
00:02:35.891343 USBLibR3:Function (c0185685) failed. rc=VERR_NOT_FOUND
00:02:35.891538 USBLibR3:USBLibGetClientInfo VBOXUSBMON_IOCTL_CLIENTPATH 
failed! rc=VERR_NOT_FOUND
00:02:35.891566 USBProxy: Failed to get client info. rc=VERR_NOT_FOUND 
szDeviceIdent=0x46d:0x825:18:/pci@0,0/pci1028,21e@1d,7/miscellaneous@8
00:02:35.891647 usbProxyConstruct: Failed to open 
'0x46d:0x825:18:/pci@0,0/pci1028,21e@1d,7/miscellaneous@8', rc=VERR_OPEN_FAILED
00:02:35.891717 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) 
aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} 
aText={Failed to create a proxy device for the USB device. (Error: 
VERR_OPEN_FAILED)}, preserve=false aResultDetail=0

But the Virtualbox webcam works fine (no microphone though)

Best regards.
Ben

- Mail original -
De: benta...@chez.com
À: "Discussion list for Open Indiana" 
Cc: "Мартин Бохниг" 
Envoyé: Mardi 20 Septembre 2016 10:59:11
Objet: Re: [OpenIndiana-discuss] Fwd: TEST-pkg available: Hipster's future  
VirtualBox-5.1.6-SunOS-amd64-r110634.pkg

Hi,
Install went on fine.
I just needed to add the SMAP setting in the /etc/system file

Nice splash and "About" screen.
One thing to notice is that the Guest addition ISO is only offering Solaris 
version and the ISO itself is rather small compared to the VBox Windows version.

I'll do some test using USB passthrough later on.

Best regards,
Ben

- Mail original -
De: "Aurélien Larcher" 
À: "Мартин Бохниг" , "Discussion list for OpenIndiana" 

Envoyé: Mardi 20 Septembre 2016 05:09:50
Objet: Re: [OpenIndiana-discuss] Fwd: TEST-pkg available: Hipster's future  
VirtualBox-5.1.6-SunOS-amd64-r110634.pkg

On Mon, Sep 19, 2016 at 10:51 AM, Мартин Бохниг via
openindiana-discuss  wrote:
>
>
>
>  Пересылаемое сообщение 
> От кого: Мартин Бохниг 
> Кому: OpenIndiana Developer mailing list 
> Дата: Понедельник, 19 сентября 2016, 8:50 UTC
> Тема: TEST-pkg available: Hipster's future 
> VirtualBox-5.1.6-SunOS-amd64-r110634.pkg
>
>
> Hello,
>
>
> as promised here finally the binary SVR4 package for use on 
> Hipster/OpenIndiana, OpenSXCE, XStreamOS or TribbliX from 2015 or newer.
> The ips stuff still needs some polishing and I release the src 
> hipster-userland integration later today or next night after first some sleep.
> Yes, I *do* mean it when I say community team work (as you see from 
> mentioning friendly distros).
> And more: I took the freedom to incorporate Jim Klimov's excellent 
> https://github.com/jimklimov/vboxconfig_sh/blob/master/vboxconfig.sh
> Ahh and btw, I fixed the
> /platform/i86pc/kernel/drv/amd64/vboxusbmon
> /platform/i86pc/kernel/drv/amd64/vboxusb
> problem and now the (Oracle created/Solaris11.3 designed) driver loads on 
> Illumos again, so thanks to this plus vboxconfig.sh postinstall completes 
> without error.
>
>
> Here the test bins (src diffs, Makefile and ips manifest to follow soo

Re: [OpenIndiana-discuss] Fwd: TEST-pkg available: Hipster's future VirtualBox-5.1.6-SunOS-amd64-r110634.pkg

[bentahyr]

Мартин, 
The test I've done so far are on Hipster/illumos-cb3c687 on a Dell T5400.
The ISO from the windows version works fine as well as the extension pack 
installs fine.
I'll see later on with a different hardware (more recent) and USB Webcam + 
sound.

Don't forget to put "Rest/Have a beer" in you task list.

Best regards.
Ben

- Mail original -
De: "Мартин Бохниг" 
À: "Мартин Бохниг" , "Discussion list for OpenIndiana" 

Cc: benta...@chez.com
Envoyé: Mardi 20 Septembre 2016 11:29:22
Objet: Re[2]: [OpenIndiana-discuss] Fwd: TEST-pkg available: Hipster's future 
VirtualBox-5.1.6-SunOS-amd64-r110634.pkg

It should be permissions based. 
Only giving whatever access to the respective devices on the host doesn't work, 
modifications regarding suid against /opt/VirtualBox/VirtualBox are also not 
doing the trick. 
In the past with vbox4 test runs with vbox as root made USB and on another 
aspect also optical media passthrough (on non-USB) work. 

The curiosity with Vbox5.0.x and 5.1.x (no matter if Oracle bins or self-built) 
is, that you cannot properly run vbox5 as root (for a short test), because the 
Qt GUI gets messed up and no text is shown. Quite odd. 
But more on that after the TODO list was completed. 
Life is, tough. And short, especially with such hobbies. 









I'm looking forward to more test results, especially USB. 
For me it doesn't work at the moment, but Oracle's binary package also doesn't 
work for me. 
That's still a problematic area which needs extra reviews. 


Best regards, 
%martin 



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

Re: [OpenIndiana-discuss] Fwd: TEST-pkg available: Hipster's future VirtualBox-5.1.6-SunOS-amd64-r110634.pkg

[bentahyr]

Hi,
Install went on fine.
I just needed to add the SMAP setting in the /etc/system file

Nice splash and "About" screen.
One thing to notice is that the Guest addition ISO is only offering Solaris 
version and the ISO itself is rather small compared to the VBox Windows version.

I'll do some test using USB passthrough later on.

Best regards,
Ben

- Mail original -
De: "Aurélien Larcher" 
À: "Мартин Бохниг" , "Discussion list for OpenIndiana" 

Envoyé: Mardi 20 Septembre 2016 05:09:50
Objet: Re: [OpenIndiana-discuss] Fwd: TEST-pkg available: Hipster's future  
VirtualBox-5.1.6-SunOS-amd64-r110634.pkg

On Mon, Sep 19, 2016 at 10:51 AM, Мартин Бохниг via
openindiana-discuss  wrote:
>
>
>
>  Пересылаемое сообщение 
> От кого: Мартин Бохниг 
> Кому: OpenIndiana Developer mailing list 
> Дата: Понедельник, 19 сентября 2016, 8:50 UTC
> Тема: TEST-pkg available: Hipster's future 
> VirtualBox-5.1.6-SunOS-amd64-r110634.pkg
>
>
> Hello,
>
>
> as promised here finally the binary SVR4 package for use on 
> Hipster/OpenIndiana, OpenSXCE, XStreamOS or TribbliX from 2015 or newer.
> The ips stuff still needs some polishing and I release the src 
> hipster-userland integration later today or next night after first some sleep.
> Yes, I *do* mean it when I say community team work (as you see from 
> mentioning friendly distros).
> And more: I took the freedom to incorporate Jim Klimov's excellent 
> https://github.com/jimklimov/vboxconfig_sh/blob/master/vboxconfig.sh
> Ahh and btw, I fixed the
> /platform/i86pc/kernel/drv/amd64/vboxusbmon
> /platform/i86pc/kernel/drv/amd64/vboxusb
> problem and now the (Oracle created/Solaris11.3 designed) driver loads on 
> Illumos again, so thanks to this plus vboxconfig.sh postinstall completes 
> without error.
>
>
> Here the test bins (src diffs, Makefile and ips manifest to follow soon) :
>
> http://opensxce.org/virtualbox5_qt4/testbins/

HI Martin,
I can also report complete success, this is brilliant, thank you. :)

Kind regards

Aurélien

>
>
> -1#.) Requires Hipster 2015++ (such as with a libc compatible to 
> illumos-f83b46b) and /usr/lib/qt/4.8
>
> #0.) Remove all previous SUNWvbox related packages (in the past userland bins 
> and kernel modules were split into 2 packages).
> Now it is enough to:
> # yes|pkgrm SUNWvbox
>
>
> which will look like this:
>
>
> # yes|pkgrm SUNWvbox
>
> The following package is currently installed:
>SUNWvbox  Oracle VM VirtualBox
>  (i386) 5.1.6,REV=2016.09.19.10.01.110634
>
> Do you want to remove this package? [y,n,?,q]
> ## Removing installed package instance 
>
> This package contains scripts which will be executed with super-user
> permission during the process of removing this package.
>
> Do you want to continue with the removal of this package [y,n,?,q] ## 
> Verifying package 
[...]
> Updating the boot archive...
>
> Installation of  was successful.
>
> <>
>
>
> --
> Мартин Бохниг
> --
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings

___
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] Nobody for whom OI/Hipster Mate on i915/KMS is working fine wants to report?

[bentahyr]

Мартин,
I'll do the tests, I already started the download of Solaris 11.3 and will 
perform a boot trial on the live DVD.

I found a HDD to install Hipster on for this laptop (lucky me I kept 2 of these 
laptops when this generation went to the bin).

I'll try to do that during nights as from tonite, I'm dad full time for the 
rest of the week-end, so don't hold your breath unless you're good at 
freediving.

Best regards.
Ben

- Mail original -
De: "Мартин Бохниг via openindiana-discuss" 

À: "Мартин Бохниг" , "Discussion list for OpenIndiana" 

Envoyé: Vendredi 9 Septembre 2016 14:21:39
Objet: Re: [OpenIndiana-discuss] Nobody for whom OI/Hipster Mate on i915/KMS is 
working fine wants to report?

Errgh, 1 self-correction after google lead me to efb (vintage Radeon 7000 for 
SPARC), rather than i915 for Intel:


https://java.net/projects/solaris-x11/sources/x-s12-clone/content/open-src/kernel/efb/src/agpgart.h?rev=1528
line 127: #define AGPIOC_RW_GTT   _IOW(AGPIOC_BASE, 15, agp_rw_gtt_t)


It is 4:18 AM here in Berlin.
Nevertheless, that's it also for x64 and agpgart on IA32 and x64.

I will check the details after some break.
Good Night for now.


___
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] Nobody for whom OI/Hipster Mate on i915/KMS is working fine wants to report?

[bentahyr]

So I downloaded the ISO from 
http://buildzone.oi-build.r61.net/OI-install-tests-201608, burnt and booted 
up to a black screen.
( I can see grub, initial illumos boot up screen, then initial openindiana text 
console where it sets hostname and a few other things, then pitch back)

Please find scanpci, dmesg and Xorg.0.log :
https://share.gns.cri.nz/3UKLCK0PSZCC/scanpci.txt.html
https://share.gns.cri.nz/0M0CQO77SEZR/dmesg.txt.html
https://share.gns.cri.nz/HIA27PA2Y6J0/Xorg.0.log.html

To add a few more interesting bits : 
root@openindiana:/var/adm# isainfo -v
64-bit amd64 applications
vmx xsave sse4.1 ssse3 cx16 sse3 sse2 sse fxsr mmx cmov amd_sysc
cx8 tsc fpu
32-bit i386 applications
vmx xsave sse4.1 ssse3 ahf cx16 sse3 sse2 sse fxsr mmx cmov sep cx8
tsc fpu

root@openindiana:/var/adm# ls -l /dev/dri
total 2
lrwxrwxrwx 1 root root 42 Sep  8 23:58 card0 -> 
../../devices/pci@0,0/display@2:controlD64
lrwxrwxrwx 1 root root 36 Sep  8 23:58 card1 -> 
../../devices/pci@0,0/display@2:drm0

Best regards.
Ben

- Mail original -
De: benta...@chez.com
À: "Discussion list for OpenIndiana" 
Envoyé: Jeudi 8 Septembre 2016 21:59:23
Objet: Re: [OpenIndiana-discuss] Nobody for whom OI/Hipster Mate on i915/KMS is 
working fine wants to report?

Hmm Ok, I'll do some tests tomorrow with ISO from buildzone.oi-build.r61.net.
I'll gather requested info and tell you how it goes.

Best regards.
Ben

- Mail original -
De: "Alexander Pyhalov" 
À: "Discussion list for OpenIndiana" 
Envoyé: Jeudi 8 Septembre 2016 20:27:23
Objet: Re: [OpenIndiana-discuss] Nobody for whom OI/Hipster Mate on i915/KMS is 
working fine wants to report?

On 09/ 8/16 05:50 AM, benta...@chez.com wrote:
> Hi Martin,
>
> I got my hands on a Intel based laptop for testing.
> Downloaded and burnt the ISO from 
> http://dlc-int.openindiana.org/hipster/20160816/
>

Hi.
Wait, wait, wait... ISOs from 
http://dlc-int.openindiana.org/hipster/20160816/ doesn't have KMS bits 
integrated. Only OI_MATE* ISOs from 
http://buildzone.oi-build.r61.net/OI-install-tests-201608/ have new 
Intel DRM driver.
-- 
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

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

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

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

Re: [OpenIndiana-discuss] Nobody for whom OI/Hipster Mate on i915/KMS is working fine wants to report?

[bentahyr]

Hmm Ok, I'll do some tests tomorrow with ISO from buildzone.oi-build.r61.net.
I'll gather requested info and tell you how it goes.

Best regards.
Ben

- Mail original -
De: "Alexander Pyhalov" 
À: "Discussion list for OpenIndiana" 
Envoyé: Jeudi 8 Septembre 2016 20:27:23
Objet: Re: [OpenIndiana-discuss] Nobody for whom OI/Hipster Mate on i915/KMS is 
working fine wants to report?

On 09/ 8/16 05:50 AM, benta...@chez.com wrote:
> Hi Martin,
>
> I got my hands on a Intel based laptop for testing.
> Downloaded and burnt the ISO from 
> http://dlc-int.openindiana.org/hipster/20160816/
>

Hi.
Wait, wait, wait... ISOs from 
http://dlc-int.openindiana.org/hipster/20160816/ doesn't have KMS bits 
integrated. Only OI_MATE* ISOs from 
http://buildzone.oi-build.r61.net/OI-install-tests-201608/ have new 
Intel DRM driver.
-- 
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

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

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

Re: [OpenIndiana-discuss] Nobody for whom OI/Hipster Mate on i915/KMS is working fine wants to report?

[bentahyr]

Hi Martin,

I got my hands on a Intel based laptop for testing.
Downloaded and burnt the ISO from 
http://dlc-int.openindiana.org/hipster/20160816/

I booted it and got a desktop but I seem to use the VESA driver.
Do I have to install it to get the Intel driver or some special switches at 
grub ?

Please, find prtdiag + xorg.0.log attached.


Ben.


- Mail original -
De: "Private openbabel" 
À: openindiana-discuss@openindiana.org
Envoyé: Mercredi 7 Septembre 2016 08:44:32
Objet: Re: [OpenIndiana-discuss] Nobody for whom OI/Hipster Mate on i915/KMS is 
working fine wants to report?

I was testing the DVD mates again and decided to install it but could 
not get the partition manager to work. this is in addition to add to 
panel omission of the volume appelet.

look forward to using this in the future.

Robert



On 06/09/2016 16:23, Мартин Бохниг via openindiana-discuss wrote:
> Ok, hi Apostolos,
>
> as said already: A pity that (almost) nobody of all those others for whom it 
> apparently works fine took the time to report, while there are always enough 
> individuals interested in discussing "code of conduct" and worse pogroms..
> Now that the only feedback anybody hears on-list about the i915 backport is 
> "oh, doesn't work" it appears as if it is "instable crap", to quote certain 
> well-known geniuses.
>
> Nevertheless thanks for reporting and sorry that you are experiencing 
> problems.
>
> Now, let's nail this issue: Yes, the same pciid 42 was already attched for 
> the old ums i915:
>
> https://searchcode.com/codesearch/view/6730577/
> alias = pci8086,42  \
>
> And yes, it should also still work with Oracle's newer driver designed for 
> Solaris 12 that I backported to OpenSolaris.
> Your output below is a good beginning at best, but what's missing:
> *Did you still test in 32bit mode, without 32bit i915/drm bins on the 
> Hipster/Mate DVD?*
>
> If yes, then it wonders little that you ended with what you call a "black 
> screen", because as there is no 32bit compiled version of i915/drm included 
> on the DVD, how would it work?
>
> Yesterday I stated already that it *is* possible to build old IA32 bins of 
> i915/drm, and they are for download (together with the 64bit bins)  here, as 
> said:
> http://opensxce.org/intelkms_working_testbins/Intel_DRMxKMS_S12_to_Illumos_backport__RELEASE/01__GLOBAL/01__BINS/TAR/
>
> They would already be part of the Illumos-gate and would by default get built 
> for IA32 _and_ x64, if Illumos was anything related to what they claim to be 
> (free bird and stuff).
> But history took different routes on scary alarming paths.
> So, that's why users of outdated hardware still running 32bit kernels have to 
> perform the installation manually after the OS is installed in text mode 
> following the steps as outlined in   
> http://opensxce.org/intelkms_working_testbins/Intel_DRMxKMS_S12_to_Illumos_backport__RELEASE/01__GLOBAL/01__BINS/TAR/INSTALL.txt
>
> So to test them you need at least a USB stick or a growisofs or a 
> hdd-installation (because otherwise you have a tough time copying any 32bit 
> variant of i915/drm into the boot_archive on wrirte-protected media).
>
> You didn't send /var/log/Xorg.0.log*,
> You didn't send syslog
> You didn't send any more information, such as where does the "the screen is 
> black" event happen.
> You did not say if you are now in 64bit mode off DVD, 32bit mode off DVD and 
> if 64bit mode, why you first said you wanted to run it in 32bit mode.
>
>
>  From your pciid I could now derive that this is:
>
> {0x8086, 0x42, CHIP_I9XX|CHIP_I965,  "Intel IGDNG_D" }, \
>
> so i965,and in  https://de.wikipedia.org/wiki/Intel-900-Serie
>
>
> that it appears to be:
> P965 [17]
> Broadwater 90 nm Q2 2006 ICH8 / ICH8R / ICH8-DH 533 / 800 / 1066 MHz 19 W 8 
> GB RAM DDR2-533/667/800
> 1.1 keine
> Q965 [18]
> Broadwater 90 nm Q2 2006 ICH8 / ICH8R / ICH8-DH 533 / 800 / 1066 MHz 19 W 8 
> GB RAM DDR2-533/667/800
> 1.1 GMA 3000
>
>
>
>
>
> But as you didn't tell me more about your Netbook (not even its name, only 
> its vendor), I can only *guess* if it is 64bit capable: PROBABLY NOT.
>
>
> So then again tell me how you can expect it to function with the current 
> Hipster/Mate KMS LiveDVD, after I explained long and well *that* and *why* it 
> does *not* contain IA32 bins for i915/drm?
>
>
> If you want to test my backport on your vintage hardware, then you need to 
> perform the installation in text mode or vesa mode and then take the 32bit 
> bins after installation from the link I provided.
> Again:  
> http://opensxce.org/intelkms_working_testbins/Intel_DRMxKMS_S12_to_Illumos_backport__RELEASE/01__GLOBAL/01__BINS/TAR/
>
>
>
>> When I try the live DVD on this machine I see a black screen.
> Did you read what I wrote yesterday already?
> NO 32bit bins of i915/drm on this current iso/DVD.
>
>
>
> %martin bochnig
>
>
>> Вторник,  6 сентября 2016, 14:23 UTC от Apostolos Syropoulos 
>> :
>>
>> Hello,
>>
>> As I reported yesterday I have t

[OpenIndiana-discuss] Darktable 2.0.5

[bentahyr]

Hi,
I'm trying to compile this software on OI and fell onto the requirement of 
dprintf :

darktable-release-2.0.5/src/common/darktable.c:174:3: error: implicit 
declaration of function 'dprintf' [-Werror=implicit-function-declaration]
   dprintf(fout, "this is %s reporting a segfault:\n\n", PACKAGE_STRING);
   ^
cc1: some warnings being treated as errors
src/CMakeFiles/lib_darktable.dir/build.make:279: recipe for target 
'src/CMakeFiles/lib_darktable.dir/common/darktable.c.o' failed
gmake[2]: *** [src/CMakeFiles/lib_darktable.dir/common/darktable.c.o] Error 1

It seems that Openindiana doesn't support this function, am I correct ?

If yes, should I use fprintf instead (with some file descriptor juggling ?

Best regards.
Ben

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

Re: [OpenIndiana-discuss] OpenGL/3D application

[bentahyr]

Hi Ken,
Aurélien was the first (only) one to mention a working OpenGL application this 
is why I tried to compile Paraview beginning from the latest. I have no need 
for it.

I'm glad to learn that flighgear works on OI as pkg search flightgear doesn't 
retuern anything.
Actually any recent and real world OpenGL application would be good enough for 
me, glxgear always works as soon as you have a DRI loaded and I'm sure OpenGL 
as it is used by wine today has nothing to do with OpenGL from 10 years ago.

I'll have a second look at Paraview next week and will resubmit sslh to 
userland.

Best regards.
Ben

On Thu, Jul 14, 2016 at 09:31:47PM +, ken mays via openindiana-discuss 
wrote:
> Hello,
> Define if you need the Hipster environment updated to successfully build 
> Paraview 5.1.0.
> Otherwise we either use the Mesa software renderer or mainly use the Nvidia 
> driver (high-performance driver) for any serious OpenGL work.
> There are several packages, like FlightGear, that we've use on OI for years.
> 
> Thanks,Ken 
> 
> On Thursday, July 14, 2016 12:09 PM, Andreas Wacknitz  
> wrote:
>  
> 
>  
> 
> Am 14.07.16 um 08:41 schrieb Aurélien Larcher:
> > Ok, I tried more recent version of Paraview without success, especially as
> >> v5+ requires cmake 3.x to compile.
> >>
> > CMake 3.x compiles and installs out of the box.
> Then why we don't update to the newer version?
> 
> Regards
> Andreas
> 

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

Re: [OpenIndiana-discuss] OpenGL/3D application

[bentahyr]

Ok, I tried more recent version of Paraview without success, especially as v5+ 
requires cmake 3.x to compile.
So this is the only 3D OpenGL application we have working.
I'm trying to dig out what is not working properly in wine 3D stuff. This is 
the reason I'm asking this, I need to have a reference that works.


Did you have to do anything special to compile v4.1? v4.4 does seem to require 
some jugling with compiler options?

Best regards.
Ben

PS :
As reference WebGL demo from the following pages do work on firefox 45.0.2 + 
Nvidia driver 340.96
https://www.chromeexperiments.com/webgl
https://davidwalsh.name/webgl-demo

PS2 :
To Nikola, I'm fully aware that my way of posting to the list is not compatible 
with everyone's client thread management, I'm working that out as well.


On Fri, Jul 08, 2016 at 12:53:48PM +, Aurélien Larcher wrote:
> 
> 
> À ven. juil. 8 01:00:07 2016 GMT+0200, benta...@chez.com a écrit :
> > Hi,
> > 
> > Is anyone using current Hipster with 3D/OpenGL software whether it is for 
> > data visualisation or any other purposes. The only 3D application I have 
> > working in Hipster is Firefox running WebGL demos.
> > I sense something fishy in the Mesa/OpenGL stack on Hipster but I cannot 
> > find any standard I could use to benchmark the stack.
> 
> I have Paraview 4.1 compiled on Hipster.
> 
> > 
> > Best regards.
> > Ben
> > 

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

[OpenIndiana-discuss] OpenGL/3D application

[bentahyr]

Hi,

Is anyone using current Hipster with 3D/OpenGL software whether it is for data 
visualisation or any other purposes. The only 3D application I have working in 
Hipster is Firefox running WebGL demos.
I sense something fishy in the Mesa/OpenGL stack on Hipster but I cannot find 
any standard I could use to benchmark the stack.

Best regards.
Ben

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

Re: [OpenIndiana-discuss] USB3 devices needed for driver testing

[bentahyr]

Hi,

My main home PC is USB3 compatible and running hipster.
I have access to a variety of USB3 storage devices. For testing purposes, I'm 
sure I can borrow a Dell Optiplex 9020 for a few weeks to do some additional 
testing.

USB3 compatible platforms :
- ASRock z87 Extreme 4 based
- Dell Optiplex 9020 

USB3 Device :
- Various Corsair Voyager keys
- Various Seagate MyPassport disks
- Unitek SATA docking station
- Icydock SATA docking station 
- Probably other external drives

Best regards.
Ben

On Mon, Jul 04, 2016 at 10:13:12PM +0200, Adam Števko wrote:
> Hello folks,
> 
> there is an ongoing work on USB3 support in illumos and we should participate 
> in testing. OI community can provide good testing background as I bet there 
> is plenty of USB3 hardware.
> 
> I’d like to create a list of person (email), device and driver, so we have 
> that ready when actual driver testing comes.  Any exotic USB3 device or 
> peripheral will help.
> 
> So if anybody is interested in helping, please respond to this email. I’d 
> also gladly ask others to not debate off-topic stuff in this thread. Thanks 
> for understanding!
> 
> Cheers,
> Adam



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

Re: [OpenIndiana-discuss] Testing updates from /dev to /hipster-2015 and /hipster

[bentahyr]

Hi,

For the moment I just notice tiny differences :
- openvpn on /dev comes from sfe and uses /etc/openvpn/config as default 
config file
- openvpn on /hipster-2015+ comes from main and uses 
/etc/openvpn/openvpn.conf as default config file

Testing more package is quite hard, for example I only discovered the 
difference between the config of openvpn because I actually used it.
Anyway is there a way to install every package other than pkg install 
pkg:/* (which doesn't work) ?
If I can install all packages, I'll try an update see which packages are 
missing but I won't be able to check config or functionality difference 
of everything.

Best regards.
Ben

On Tue, May 10, 2016 at 08:50:02AM +0200, Nikola M wrote:
> On 05/10/16 12:13 AM, benta...@chez.com wrote:
> > But the latest fails due to a bunch of pkg list |grep '0\.151\.1\.' 
> > packages.
> >
> > So it is not possible right now to update directly from /dev to /hipster
>
> Thanks very much Ben!
> See if you can stay inside ML thread with a reply, with no new thread (new
> thread helps atm, but got to say ;P)
> I actually don't expect for /hipster as a moving target to be updatable from
> old_/dev , now nor in the future, for it's (thankfully) dynamic nature it
> should be expected and changes accumulating as we speak.
> So we need anchor releases to and what this testing is all about.
>
> So with first reports
> (and it is taking too long already, since first report from Woody/alp was
> months ago, http://openindiana.org/pipermail/oi-dev/2015-October/003823.html
> ) ,
> we have positive responses in updating from /dev to hipster-2015.
>
> I propose next step would be to install all packages in /dev, and see what
> can be updated to /hipster-2015. so to catch any application update
> problems, not commonly installed on fresh install, with
> Compiling workarounds (like package removals before update then reinstall or
> configs transitions).
> For this step,  we still don't need any infrastructure.
>
> After that I propose making a new publisher called /dev-test , populated
> with packages from hipster-2015 then updated to OI hipster 20160421 snapshot
> state
> and start  old_/dev to /dev-test update testing.
>
> When we have more (if any) bug reports for both hipster-2015 update and
> 20160421 update and a list of changes (and/or manuals) that need to be made
> for update to work,
> It could then require infrastructure for building separate from hipster, but
> fully identical that would allow changes to facilitate update to land in
> /hipster and /dev-test
> At that time we would suppose to have working packagemenager GUI ,
> updatemenager added and 151a branded zone.
> Then it would be landing in /dev as a new /dev release
>
> As part of the process /hipster will accept results of update testing as
> part of bug fixing process, including temporary package removal for not
> fulfilling quality standards
> It would allow supporting OI use in production while all contributions to go
> to /hipster.
> And contributions to /hipster will allow new releases of /dev :)
> Testing with updates from one snapshot to another would result in bringing
> up the quality.
> Snapshots and landings in /dev would become more frequent and more bugs
> would be found and fixed in the process, therefore pumping up OI quality
> while in the process providing support for wider audience and therefore
> increasing in OI use, that requires releases with high quality standards.
>
> Please test as much packages in installed in old /dev to see how update
> works with as many packages as possible, to be able to go to the next step
> with /dev-test repo.
>

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

Re: [OpenIndiana-discuss] Testing updates from /dev to /hipster-2015 and /hipster

[bentahyr]

Hi,

What I mean is during the validation phases of the pkg update, pkg 
refuse to update various package due to conflicts not resolvable 
(notably perl, php, mysql) when pkg update from /dev to /hipster-2015 
does validate and succeed.

So to speak, the update doesn't take place per say as it fails during 
validation phase which is a perfectly sane behaviour.


If you want I can provide a full output of it after I finished some more 
tests about update of /dev to /hipster-2015.

Best regards.
Ben

On Tue, May 10, 2016 at 10:58:32AM +0300, Alexander Pyhalov wrote:
> On 05/10/2016 01:13, benta...@chez.com wrote:
> > Hi,
>
> > But the latest fails due to a bunch of pkg list |grep '0\.151\.1\.' 
> > packages.
>
> Hi.
> What do you mean by "the latest fails" - does update fail or after update
> there are *0.151.1* packages are left? If the latter, can you share the
> list?
>

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

Re: [OpenIndiana-discuss] Testing updates from /dev to /hipster-2015 and /hipster

[bentahyr]

Hi,

Today I started to the update from 151a9 to hipster (without hipster-2015 
stage).
I followed the same process than the one I described before :
1 - Create a BE to start and boot to it :
# beadm create -a Openindiana-HipUpdate-S1
# reboot

2 - remove all packages from external repositories (like SFE/SFE-encumbered but 
SFWpackages as well) :
# pkginfo | grep SFW
# pkgrm SFW[whatevername]
# pkg uninstall --be-name Openindiana-HipUpdate-S2 `pkg list -v | egrep sfe | 
cut -d" " -f1`

3 - Reboot to new env Openindiana-HipUpdate-S2

4 - Remove external IPS publishers :
# pkg unset-publisher sfe
# pkg unset-publisher sfe-encumbered

5 - Change publisher to Hipster 2015
# pkg set-publisher -g http://pkg.openindiana.org/hipster -G 
http://pkg.openindiana.org/dev openindiana.org
# pkg refresh --full
# pkg update --be-name OpenIndiana-Latest

But the latest fails due to a bunch of pkg list |grep '0\.151\.1\.' packages.

So it is not possible right now to update directly from /dev to /hipster

Best regards.
Ben

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

Re: [OpenIndiana-discuss] Testing updates from /dev to /hipster-2015 and /hipster

[bentahyr]

Thanks for the great job.

I tested today the update from oi_151a9 to Hipster2015 to hipster.
It was a long journey.
The hardware is a Dell Precision T5400 (16GB of memory and 2 mirrored pools)
It took me the whole day as I have very poor IO performance on that hardware.

Here is the process I followed for reference and for the doc project :
1 - Create a BE to start and boot to it :
# beadm create -a Openindiana-HipUpdate-S1
# reboot

2 - remove all packages from external repositories (like SFE/SFE-encumbered but 
SFWpackages as well) :
# pkginfo | grep SFW
# pkgrm SFW[whatevername]
# pkg uninstall --be-name Openindiana-HipUpdate-S2 `pkg list -v | egrep sfe | 
cut -d" " -f1`

3 - Reboot to new env Openindiana-HipUpdate-S2

4 - Remove external IPS publishers :
# pkg unset-publisher sfe
# pkg unset-publisher sfe-encumbered

5 - Change publisher to Hipster 2015
# pkg set-publisher -g http://pkg.openindiana.org/hipster-2015 -G 
http://pkg.openindiana.org/dev openindiana.org
# pkg refresh --full
# pkg update --be-name Openindiana-HipUpdate-S3

6 - Reboot to Hipster 2015

7 - Verify any leftovers
# pkg list |grep '0\.151\.1\.'
* must be empty *

7 - Install incorporations
# pkg install --no-backup-be userland-incorporation entire

8 - Change publisher to Hipster
# pkg set-publisher -g http://pkg.openindiana.org/hipster -G 
http://pkg.openindiana.org/hipster-2015 openindiana.org

9 - Update to latest Hipster
# pkg update --be-name OpenIndiana-Latest
# reboot

Now test extensively, reinstall missing applications, enable SFW for 
Hipster,
Once you're sure and happy, clean up transitioning BE :
# beadm destroy Openindiana-HipUpdate-S1
# beadm destroy Openindiana-HipUpdate-S2
# beadm destroy Openindiana-HipUpdate-S3

I noticed that VirtualBox (v5.0.16)went through the update seamlessly.

Tomorrow I'll test update from 151a9 to /hipster directly

Best regards
Ben 
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] ZFS smb logs

[bentahyr]

Hi,

I see series of strange CIFS requests on the /var/adm/messages logs :
starsystem is the hostname
deadstar is the hostname of the old system this one has replaced and is still 
used in some services (Apache)

Apr 18 07:29:39 starsystem smbsrv: [ID 138215 kern.notice] NOTICE: smbd[NT 
Authority\Anonymous]: deadstar access denied: IPC only
Apr 18 07:29:39 starsystem last message repeated 1 time
Apr 18 07:29:39 starsystem smbsrv: [ID 138215 kern.notice] NOTICE: smbd[NT 
Authority\Anonymous]: deadsta share not found
Apr 18 07:29:39 starsystem last message repeated 1 time
Apr 18 07:29:39 starsystem smbsrv: [ID 138215 kern.notice] NOTICE: smbd[NT 
Authority\Anonymous]: deadstar access denied: IPC only
Apr 18 07:29:39 starsystem last message repeated 1 time
Apr 18 07:29:39 starsystem smbsrv: [ID 138215 kern.notice] NOTICE: smbd[NT 
Authority\Anonymous]: deadstar share not found
Apr 18 07:29:39 starsystem last message repeated 1 time
Apr 18 07:29:39 starsystem smbsrv: [ID 138215 kern.notice] NOTICE: smbd[NT 
Authority\Anonymous]: deadstar access denied: IPC only
Apr 18 07:29:39 starsystem last message repeated 1 time
Apr 18 07:29:39 starsystem smbsrv: [ID 138215 kern.notice] NOTICE: smbd[NT 
Authority\Anonymous]: deadsta share not found
Apr 18 07:29:39 starsystem last message repeated 1 time
Apr 18 07:29:39 starsystem smbsrv: [ID 138215 kern.notice] NOTICE: smbd[NT 
Authority\Anonymous]: deadstar.bat share not found
Apr 18 07:29:39 starsystem last message repeated 1 time
Apr 18 07:29:39 starsystem smbsrv: [ID 138215 kern.notice] NOTICE: smbd[NT 
Authority\Anonymous]: deadstar.cmd share not found
Apr 18 07:29:39 starsystem last message repeated 1 time
Apr 18 07:29:39 starsystem smbsrv: [ID 138215 kern.notice] NOTICE: smbd[NT 
Authority\Anonymous]: deadstar.exe share not found
Apr 18 07:29:39 starsystem last message repeated 1 time
Apr 18 07:29:39 starsystem smbsrv: [ID 138215 kern.notice] NOTICE: smbd[NT 
Authority\Anonymous]: deadstar.com share not found
[...]


I was wondering if there is a way to make it log the source IP of the 
connection ?

Best regards.
Ben

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

[OpenIndiana-discuss] Hipster, virtualisation and USB devices

[bentahyr]

Hi,

I've been playing with Virtualbox 5 in order to be able to use Skype and still 
have the following issues :
- embedded mic on webcam doesn't work,
- USB pass-through brings peaks of latency, slowlyness,
- Virtualbox webcam still present 1s latency.

I wanted to know if anyone had success running Win7/Skype for video 
conferencing and what was the set-up they used (sound coming from USB device ? 
from mic-in ? using VB Webcam or USB pass-through ? good frame rate without 
latency ? 3D emulation in guest ?)

And finally if kvm behaves ok/better in that matter (USB pass-through) ?

Best regards.
Ben

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

Re: [OpenIndiana-discuss] VirtualBox 5.0.16, USB and rights

[bentahyr]

Yes, indeed, I forgot when I installed the Hipster machine to add users to the 
vboxusers group. 

Thanks. 
Ben 

On 16/03/16 20:31, Jim Klimov wrote: 


15 марта 2016 г. 22:40:44 CET, benta...@chez.com пишет: 

Hi, 

Just in case, is your account who executes the virtualbox VM a root, or a 
member of vboxusers group, on the OI host? And are all VB services running? And 
did you use the patched vboxconfig.sh (IIRC vboxusb was among modules that's 
not installed on non-oracle solaris by default).

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


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

[OpenIndiana-discuss] Wine on Hipster

[bentahyr]

Hi,

I'm quite happy with Hipster as a desktop, right now, I think it reached a nice 
state offering a good desktop experience for basic users. I know there is still 
a lot to do but it looks fantastic, especially when I see my 6 years old 
daughter using it to start VLC or gCompris (I'll package it later when I'm 
better at packaging, I have a lot to learn).

Now what I miss and while I can work around it, is Wine. If I wanted to have 
Wine on Hipster, is there a version somewhere (I have 1.7.7 from SFE on 
oi_151a9) ? If I was to package one, what repo should it belongs to ?

Best regards.
Ben

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

[OpenIndiana-discuss] VirtualBox 5.0.16, USB and rights

[bentahyr]

Hi,

Running hipster,I noticed one difference between hipster and 151a9 is the USB 
passthrough doesn't seem to work ok.

On OI 151a9 :
-

$ VBoxManage list usbhost
Host USB Devices:

UUID:   e4f05ec6-78d1-4022-8edd-a0ddecac67d8
VendorId:   0x046d (046D)
ProductId:  0xc077 (C077)
Revision:   114.0 (11400)
Port:   2
USB version/speed:  2/Low
Manufacturer:   Logitech
Product:USB Optical Mouse
Address:0x46d:0xc077:29184:/pci@0,0/pci1028,21e@1d
Current State:  Busy

UUID:   92e7965f-00d0-4b71-b8ae-99147c672275
VendorId:   0x413c (413C)
ProductId:  0x2003 (2003)
Revision:   3.1 (0301)
Port:   1
USB version/speed:  1/Low
Manufacturer:   Dell
Product:Dell USB Keyboard
Address:0x413c:0x2003:769:/pci@0,0/pci1028,21e@1d
Current State:  Busy

On Hipster :

$ VBoxManage list usbhost
Host USB Devices:



$ sudo VBoxManage list usbhost  


Password: 
Host USB Devices:

UUID:   bc6ed094-509a-41b1-8cad-f6696e06716d
VendorId:   0x04d9 (04D9)
ProductId:  0x1203 (1203)
Revision:   2.112 (02112)
Port:   7
USB version/speed:  2/Low
Manufacturer:   Holtek Semiconductor, Inc.
Product:Keyboard
Address:0x4d9:0x1203:624:/pci@0,0/pci1849,8c26@1d/hub@1
Current State:  Busy

UUID:   e6f08c61-fda0-46a2-9acb-9bded3b76356
VendorId:   0x08ca (08CA)
ProductId:  0x0010 (0010)
Revision:   1.5 (0105)
Port:   2
USB version/speed:  1/Low
Manufacturer:   AIPTEK International Inc.
Product:USB Tablet Series Version 1.05
Address:0x8ca:0x10:261:/pci@0,0/pci1849,8c26@1d/hub@1
Current State:  Busy

UUID:   b0e381b7-c536-4754-89dc-cbdda127ed7d
VendorId:   0x14cd (14CD)
ProductId:  0x1212 (1212)
Revision:   1.0 (0100)
Port:   4
USB version/speed:  2/High
Manufacturer:   Generic
Product:Mass Storage Device
SerialNumber:   121220130416
Address:0x14cd:0x1212:256:/pci@0,0/pci1849,8c26@1d/hub@1
Current State:  Busy

UUID:   a4d1297d-45cd-4699-815b-ab78c5755e96
VendorId:   0x1bcf (1BCF)
ProductId:  0x0007 (0007)
Revision:   0.16 (0016)
Port:   8
USB version/speed:  2/Low
Manufacturer:   Sunplus Innovation Technology Inc.
Product:USB Optical Mouse
Address:0x1bcf:0x7:16:/pci@0,0/pci1849,8c26@1d/hub@1
Current State:  Busy

There is an issue around rights on USB devices, is it related to the bug #6728 
(https://www.illumos.org/issues/6728) ?

Best regards.
Ben

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

Re: [OpenIndiana-discuss] Debugging SMF method

[bentahyr]

Thank you this was quite handy to read. 

On 14/03/16 01:40, Volker A. Brandt wrote: 




On 13/03/2016 04:34, benta...@chez.com wrote: 

I'm working on the SMF service and I need to run method script but I can't 
because 

> if I run it by hand I don't have the SMF variable and env loaded. 

Is there a way to load this environment so I can run the method script manually 
? 

. /lib/svc/share/smf_include.sh 

Before that, you should read the section "Shell Programming Support"
in smf_method(5).


Regards -- Volker 


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

[OpenIndiana-discuss] Debugging SMF method

[bentahyr]

Hi,

I'm working on the SMF service and I need to run method script but I can't 
becauseif I run it by hand I don't have the SMF variable and env loaded.

Is there a way to load this environment so I can run the method script manually 
?

Best regards.
Ben

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

Re: [OpenIndiana-discuss] USB 2 performance

[bentahyr]

From the tests I did, UFS gave good results so I guess ZFS would be ok.
The USB device is used to exchange data with foreign platforms and 
unfortunately ZFS is far away from being the common denominator filesystem wise.

I suspect the fuse layer being the issue, here but won't have the oportunity to 
verify this before September.

Best regards.
Ben

- Mail original -
De: "Jonathan Adams" 
À: "Discussion list for OpenIndiana" 
Envoyé: Jeudi 30 Juillet 2015 17:09:47
Objet: Re: [OpenIndiana-discuss] USB 2 performance

I know it's a little off-topic, but have you thought of creating a zpool on
the USB stick and seeing how that goes?

ZFS on Linux works well for removable media, assuming you can "sudo zpool
import"

Jon

PS. I generally end up dd'ing with a block size of 4M to get maximum
throughput.

On 30 July 2015 at 15:17, Jean-Pierre André 
wrote:

> benta...@chez.com wrote:
>
>> Hi Jean-Pierre,
>>
>> I was using 2012.1.15AR.8 from SFE, with no specific option for mount
>> command :
>> # ntfs-3g -o uid=101 /dev/dsk/c2t0d0p1 /mnt
>>
>> Since then I switched to the last version available on your website
>> (2015.3.14AR.1), and redid the test, still using the same mount command.
>> $ dd if=FreeDOS-1.1-memstick-2-2048M.img
>> of=/mnt/FreeDOS-1.1-memstick-2-2048M.img
>> 1412712+0 records in
>> 1412712+0 records out
>> 723308544 bytes (723 MB) copied, 2552.51 s, 283 kB/s
>> I stopped it as it wasn't necessary to wait 3h
>>
>> $ dd if=FreeDOS-1.1-memstick-2-2048M.img
>> of=/mnt/FreeDOS-1.1-memstick-2-2048M.img bs=4096
>> 166643+0 records in
>> 166643+0 records out
>> 682569728 bytes (683 MB) copied, 2360.02 s, 289 kB/s
>> Stopped as well
>>
>> Mount with big_writes option
>> # ntfs-3g -o big_writes,uid=101 /dev/dsk/c2t0d0p1 /mnt
>>
>
> The big_writes option is not supported by the fuse variant
> for OpenIndiana.
>
> $ dd if=FreeDOS-1.1-memstick-2-2048M.img
>> of=/mnt/FreeDOS-1.1-memstick-2-2048M.img bs=4096
>> 207578+0 records in
>> 207578+0 records out
>> 850239488 bytes (850 MB) copied, 3691.7 s, 230 kB/s
>> Stopped as well
>>
>> Now I format the disk on Win7 to NTFS, 512b rather than defaulting to
>> 4096b
>> $ dd if=FreeDOS-1.1-memstick-2-2048M.img
>> of=/mnt/FreeDOS-1.1-memstick-2-2048M.img
>> 172937+0 records in
>> 172937+0 records out
>> 708349952 bytes (708 MB) copied, 2367.44 s, 299 kB/s
>> Stopped as well
>>
>> I don't really know what to blame, maybe the FUSE stage might the
>> bottleneck here.
>>
>
> ntfs-3g has never been efficient on bulk transfers because
> it is organized on top of fuse, but there must be another
> explanation for this very bad throughput.
>
> I have no idea why, ATM.
>
> Regards
>
> Jean-Pierre
>
> Maybe dd is not really the good command to test this as well.
>> I wanted to test exFAT as weel but I'm running out of time before going
>> off until September.
>>
>> Ben
>>
>
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

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

Re: [OpenIndiana-discuss] USB 2 performance

[bentahyr]

Hi Jean-Pierre,

I was using 2012.1.15AR.8 from SFE, with no specific option for mount command :
# ntfs-3g -o uid=101 /dev/dsk/c2t0d0p1 /mnt

Since then I switched to the last version available on your website 
(2015.3.14AR.1), and redid the test, still using the same mount command.
$ dd if=FreeDOS-1.1-memstick-2-2048M.img 
of=/mnt/FreeDOS-1.1-memstick-2-2048M.img
1412712+0 records in
1412712+0 records out
723308544 bytes (723 MB) copied, 2552.51 s, 283 kB/s
I stopped it as it wasn't necessary to wait 3h

$ dd if=FreeDOS-1.1-memstick-2-2048M.img 
of=/mnt/FreeDOS-1.1-memstick-2-2048M.img bs=4096
166643+0 records in
166643+0 records out
682569728 bytes (683 MB) copied, 2360.02 s, 289 kB/s
Stopped as well

Mount with big_writes option
# ntfs-3g -o big_writes,uid=101 /dev/dsk/c2t0d0p1 /mnt
$ dd if=FreeDOS-1.1-memstick-2-2048M.img 
of=/mnt/FreeDOS-1.1-memstick-2-2048M.img bs=4096
207578+0 records in
207578+0 records out
850239488 bytes (850 MB) copied, 3691.7 s, 230 kB/s
Stopped as well

Now I format the disk on Win7 to NTFS, 512b rather than defaulting to 4096b
$ dd if=FreeDOS-1.1-memstick-2-2048M.img 
of=/mnt/FreeDOS-1.1-memstick-2-2048M.img
172937+0 records in
172937+0 records out
708349952 bytes (708 MB) copied, 2367.44 s, 299 kB/s
Stopped as well

I don't really know what to blame, maybe the FUSE stage might the bottleneck 
here.
Maybe dd is not really the good command to test this as well.
I wanted to test exFAT as weel but I'm running out of time before going off 
until September.

Ben

- Mail original -
De: "Jean-Pierre André" 
À: openindiana-discuss@openindiana.org
Envoyé: Mardi 28 Juillet 2015 20:16:25
Objet: Re: [OpenIndiana-discuss] USB 2 performance

Jean-Pierre André wrote:
> Aurélien Larcher wrote:
>> Hi,

[...]

>>>
>>> using NTFS-3g
>>> $ dd if=FreeDOS-1.1-memstick-2-2048M.img
>>> of=/mnt/FreeDOS-1.1-memstick-2-2048M.img
>>> 3948544+0 records in
>>> 3948544+0 records out
>>> 2021654528 bytes (2.0 GB) copied, 15867.8 s, 127 kB/s
>>>
>>> After reformating to UFS
>>> $ dd if=FreeDOS-1.1-memstick-2-2048M.img
>>> of=/mnt/ben/FreeDOS-1.1-memstick-2-2048M.img
>>> 3948544+0 records in
>>> 3948544+0 records out
>>> 2021654528 bytes (2.0 GB) copied, 110.893 s, 18.2 MB/s
>>>
>>>
>>> Yeah, really, something is wrong with the implementation of FAT/NTFS
>>> on OpenIndiana.
>>> Would a more recent NTFS-3G help ? Currently using 2012.1.15AR.8 from
>>> SFE.
>
> Which version of ntfs-3g were you using and what are
> your mount options ? What is the output of "ntfs-3g -help" ?
>

Oh, I forgot : retry dd with option "bs=4096", so that the
fuse kernel module need not concatenate write chunks (the
default block size is 512 for dd).

Jean-Pierre



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

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

Re: [OpenIndiana-discuss] USB 2 performance

[bentahyr]

I did some test today with another USB drive.
Here are the results :

From Linux (NTFS)
$ dd if=FreeDOS-1.1-memstick-2-2048M.img 
of=/media/ben/MD/FreeDOS-1.1-memstick-2-2048M.img
3948544+0 enregistrements lus
3948544+0 enregistrements écrits
2021654528 octets (2.0 GB) copiés, 91.5862 s, 22.1 MB/s

From OI
Jul 28 08:50:42 hostname usba: [ID 912658 kern.info] USB 2.0 device 
(usb5e3,702) operating at hi speed (USB 2.x) on USB 2.0 root hub: storage@7, 
scsa2usb0 at bus address 2
Jul 28 08:50:42 hostname usba: [ID 349649 kern.info]  USB TO IDE
Jul 28 08:50:42 hostname genunix: [ID 936769 kern.info] scsa2usb0 is 
/pci@0,0/pci1028,21e@1d,7/storage@7
Jul 28 08:50:42 hostname genunix: [ID 408114 kern.info] 
/pci@0,0/pci1028,21e@1d,7/storage@7 (scsa2usb0) online

using NTFS-3g
$ dd if=FreeDOS-1.1-memstick-2-2048M.img 
of=/mnt/FreeDOS-1.1-memstick-2-2048M.img
3948544+0 records in
3948544+0 records out
2021654528 bytes (2.0 GB) copied, 15867.8 s, 127 kB/s

After reformating to UFS
$ dd if=FreeDOS-1.1-memstick-2-2048M.img 
of=/mnt/ben/FreeDOS-1.1-memstick-2-2048M.img
3948544+0 records in
3948544+0 records out
2021654528 bytes (2.0 GB) copied, 110.893 s, 18.2 MB/s


Yeah, really, something is wrong with the implementation of FAT/NTFS on 
OpenIndiana.
Would a more recent NTFS-3G help ? Currently using 2012.1.15AR.8 from SFE.

Ben

- Mail original -
De: benta...@chez.com
À: "Discussion list for OpenIndiana" 
Envoyé: Lundi 27 Juillet 2015 16:24:44
Objet: Re: [OpenIndiana-discuss] USB 2 performance

Thanks for the FAT trick.
I don't remember when the disk used to be NTFS, 1 or 2 years ago. I had to 
reformat it for compatibility issues with shiny hardware I don't manage.

I'll try to reformat it to NTFS and see how it goes.

Best regards.
Ben

- Mail original -
De: "Aurélien Larcher" 
À: openindiana-discuss@openindiana.org
Envoyé: Lundi 27 Juillet 2015 16:08:25
Objet: Re: [OpenIndiana-discuss] USB 2 performance

I guess it depends which filesystem you are using, but for FAT yes definitely.
Maybe just a matter of block size in this case.
Also make sure that USB2 is actually used, I found Solaris/illumos to fallback 
to USB1 on several occasions.

Aurélien

À lun. juil. 27 06:00:21 2015 GMT+0200, benta...@chez.com a écrit :
> I redid the test, it is more around 30-35 MB/s on other OS's actually.
> 
> - Mail original -
> De: benta...@chez.com
> À: "Discussion list for OpenIndiana" 
> Envoyé: Lundi 27 Juillet 2015 15:56:33
> Objet: [OpenIndiana-discuss] USB 2 performance
> 
> Hi,
> 
> I always found the performance of USB devices connected to OI behind other OS.
> Is it related to the implementation or is it just me (oi159a) ?
> 
> For example, same drive transfer (one big file) is :
> - 8MB/s on OI
> - 45MB/s on Linux/Windows
> 
> Ben
> 

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

Re: [OpenIndiana-discuss] USB 2 performance

[bentahyr]

Thanks for the FAT trick.
I don't remember when the disk used to be NTFS, 1 or 2 years ago. I had to 
reformat it for compatibility issues with shiny hardware I don't manage.

I'll try to reformat it to NTFS and see how it goes.

Best regards.
Ben

- Mail original -
De: "Aurélien Larcher" 
À: openindiana-discuss@openindiana.org
Envoyé: Lundi 27 Juillet 2015 16:08:25
Objet: Re: [OpenIndiana-discuss] USB 2 performance

I guess it depends which filesystem you are using, but for FAT yes definitely.
Maybe just a matter of block size in this case.
Also make sure that USB2 is actually used, I found Solaris/illumos to fallback 
to USB1 on several occasions.

Aurélien

À lun. juil. 27 06:00:21 2015 GMT+0200, benta...@chez.com a écrit :
> I redid the test, it is more around 30-35 MB/s on other OS's actually.
> 
> - Mail original -
> De: benta...@chez.com
> À: "Discussion list for OpenIndiana" 
> Envoyé: Lundi 27 Juillet 2015 15:56:33
> Objet: [OpenIndiana-discuss] USB 2 performance
> 
> Hi,
> 
> I always found the performance of USB devices connected to OI behind other OS.
> Is it related to the implementation or is it just me (oi159a) ?
> 
> For example, same drive transfer (one big file) is :
> - 8MB/s on OI
> - 45MB/s on Linux/Windows
> 
> Ben
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

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

Re: [OpenIndiana-discuss] USB 2 performance

[bentahyr]

I redid the test, it is more around 30-35 MB/s on other OS's actually.

- Mail original -
De: benta...@chez.com
À: "Discussion list for OpenIndiana" 
Envoyé: Lundi 27 Juillet 2015 15:56:33
Objet: [OpenIndiana-discuss] USB 2 performance

Hi,

I always found the performance of USB devices connected to OI behind other OS.
Is it related to the implementation or is it just me (oi159a) ?

For example, same drive transfer (one big file) is :
- 8MB/s on OI
- 45MB/s on Linux/Windows

Ben

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

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

[OpenIndiana-discuss] USB 2 performance

[bentahyr]

Hi,

I always found the performance of USB devices connected to OI behind other OS.
Is it related to the implementation or is it just me (oi159a) ?

For example, same drive transfer (one big file) is :
- 8MB/s on OI
- 45MB/s on Linux/Windows

Ben

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

Re: [OpenIndiana-discuss] Who is trying to break in ?

[bentahyr]

Hi, 
I've been using sshl to multiplex openvpn, https and ssh on port 443 to be able 
to go through anything and before that I was using tcpproxy for the same reason.
I'm pretty impressed by sshl and I hope to use it when I replace the linux 
all-in-one box by an refurbished Ultra 20/hipster.

To be honest, for a very long time I had port 22 opened as well for ssh the 
time to trust sshl and the difference is quite noticeable, security wise.
On the other hand, if you don't allow root login, have good passwords for users 
and root and log rotation correctly set, port 22 or not is just a convenience 
question but I'm not a security guy, really.

Ben.

- Mail original -
De: "Jim Klimov" 
À: "Discussion list for OpenIndiana" , 
"Till Wegmüller" 
Envoyé: Lundi 29 Juin 2015 21:02:44
Objet: Re: [OpenIndiana-discuss] Who is trying to break in ?

29 июня 2015 г. 9:37:26 CEST, "Till Wegmüller"  пишет:
>Brogyányi József schrieb am Sunday 28 June 2015 11.01:55:
>
>> /The last was strange a little bit because he wanted to switch of the
>
>> server. I think you have to change the 21 and 22 communication port.
>> I use the 443 port for ssh. I can reach the server easily from
>anywhere 
>> because every company left it open that port.
>
>I Advise Strongly against using a different port for SSH. Especially a
>port like 443 which by default is used by apache and other webservers.
>Some Webservers might refuse to launch depending on their
>configuration.
>
>> I've noticed some text output before shutting down the system.
>> It seems someone ( or bots ) are constantly trying to log in as root.
>
>Yea there are some Chinese Bot nets that scan for open SSH Ports and
>try to log in with root. I have them on every SSH capable server which
>is Internet reachable. They don't only scan 22 but also 666 or 1337.
>But they only make tries with weak default passwords like 12345. 
>
>If you want to block them I suggest the Tool fail2ban. I use it on my
>Linux boxes and it works like a charm. There also seems to be a Port
>for snv_134 https://github.com/jamesstout/fail2ban-0.8.4-OpenSolaris
>but I haven't tested that.
>
>Greetings Till
>
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss

Got no qualms about ssh (or openvpn) on port 443 - indeed, if one sets up 
something non-standard, gotta be ready for the consequences. And to all ids'es 
and sniffers, cryptotraffic looks much the same (different dynamic flow 
patterns may be discerned by the smarter filters out there though).

As was said earlier, many networks (especially free wifi, and some cellulars) 
only allow http(s) outwards, so there's not much choice for road-workers.

Also, there are server-side projects to colocate frontends for https and ssh or 
openvpn on the same socket to veil it even more.


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

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

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

Re: [OpenIndiana-discuss] Using OI-userland to develop software

[bentahyr]

Merci Aurélien,

Thanks for the explanations. I found a way to get what I wanted, now I can 
start the real thing and I fell into something quite interesting.

--- output --
During compilation of code I fall onto the error :
/usr/include/signal.h:144:1: error: unknown type name ‘sigset_t’
 extern int sigwait(const sigset_t *_RESTRICT_KYWD, int *_RESTRICT_KYWD);
 ^   
--- end--

Which is strange as sigset_t is defined in /usr/include/sys/signal.h which is 
include at the begining of /usr/include/signal.h
So I'm not sure it doesn't pickup the def as I would expect error in my code 
not in between /usr/include/signal.h and /usr/include/sys/signal.h

I have to admit to go back to C/C++ after more than 15 years makes me feel my 
brain is in concrete.

Best regards.
Ben

- Mail original -
De: "Aurélien Larcher" 
À: "Discussion list for OpenIndiana" 
Envoyé: Lundi 22 Juin 2015 11:53:58
Objet: Re: [OpenIndiana-discuss] Using OI-userland to develop software

Dear Ben,

1) Glib being based on Autotools the relevant "recipes" are in this file:

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/make-rules/configure.mk

As you see, changing the value of COMPONENT_PREFIX to /opt/local in your
glib Makefile will achieve what you want.

2) Instead of getting root to install the package to the local repository,
you can consider giving software installation credentials to your user,
change the line in /etc/user_attr:

usertype=normal;profiles=Software Installation

Best

Aurelien



On Mon, Jun 22, 2015 at 1:39 AM,  wrote:

> Hi,
>
> I'm trying to use oi-userland on hipster.
> The current config I set up is :
> - main repository host is 151a9 exporting oi-userland
> - work is done on hipster virtual machines powered by VirtualBox and
> mounting the oi-userland from host by NFS
>
> As an example I'm trying to work on software requiring a more recent glib
> than what's on hipster (v2.28.8) and oi-userland seems to be able to
> provide v2.43.4.
> I followed the wiki and am able to build the glib, no issue there.
> I'm stuck at next stage.
> I would like to use it in a another directory, like /opt/local/req.
> I tried to change the PROTO_DIR variable but it doesn't seem to be the way
> to do it.
> I tried to publish but I need to be root to pkgsend nd of course, I have
> root_squash on NFS export from hosts.
>
> What would be the canonical way to do things ?
> Should I create an entry (directory and makefile, and...) for my software
> in oi-userland ?
> Should I just get to apply the patches and make clean, autogen with
> different prefix in glib-2.43.4 subdirectory ?
>
> Best regards.
> Ben
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
LARCHER Aurélien  | KTH, School of Computer Science and
Communication
Work: +46 (0) 8 790 71 42 | Lindstedtsvägen 5, Plan 4, 100 44 Stockholm,
SWEDEN
---
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

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

[OpenIndiana-discuss] Using OI-userland to develop software

[bentahyr]

Hi,

I'm trying to use oi-userland on hipster.
The current config I set up is :
- main repository host is 151a9 exporting oi-userland
- work is done on hipster virtual machines powered by VirtualBox and mounting 
the oi-userland from host by NFS

As an example I'm trying to work on software requiring a more recent glib than 
what's on hipster (v2.28.8) and oi-userland seems to be able to provide v2.43.4.
I followed the wiki and am able to build the glib, no issue there.
I'm stuck at next stage.
I would like to use it in a another directory, like /opt/local/req.
I tried to change the PROTO_DIR variable but it doesn't seem to be the way to 
do it.
I tried to publish but I need to be root to pkgsend nd of course, I have 
root_squash on NFS export from hosts.

What would be the canonical way to do things ?
Should I create an entry (directory and makefile, and...) for my software in 
oi-userland ?
Should I just get to apply the patches and make clean, autogen with different 
prefix in glib-2.43.4 subdirectory ?

Best regards.
Ben

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

Re: [OpenIndiana-discuss] fishing for suggestions for new motherboard

[bentahyr]

Hi Jerry,

For me the most important is network support because I would be really annoyed 
with an unsupported NIC. It already happened and hopefully I could use Wifi as 
it was on a laptop... so the 3 criteria are :
- NIC support
- SATA controller support
- USB2/PS2 support

I'm in process of refurbishing an old Ultra 20 as well and I'm collecting 
hardware as I see some good oportunities on second hand stuff, the motherboard 
I found is an ASRock Z97 Extreme4 which seems to fit my bill, I don't really 
know about the support for Realtek ALC1150 sound chipset tho.

Ben.

- Mail original -
De: "Jerry Kemp" 
À: "Discussion list for OpenIndiana" 
Envoyé: Jeudi 14 Mai 2015 07:12:43
Objet: [OpenIndiana-discuss] fishing for suggestions for new motherboard

I'm long overdue to build out a new x86/x64 system to run (primarily) 
OpenIndiana on, and I looking for comments and suggestions from others who have 
recently done the same.

I have already reviewed our HCL here:

http://wiki.openindiana.org/oi/Motherboards

But I fear it is dated, as the last update was almost a year ago.

I'm planning to run an Intel CPU due to some issues with another OS, and I need 
it to handle at least 32 Gb of ram.  This is for me at $HOME, but I run a lot 
of 
zones + virtualization via VirtualBox.

Size - I own a small collection of old Sun Ultra 20 cases that I like to use, 
so 
I am looking for an ATX sized board.

If it matters, I typically always run an NVIDIA frame buffer as they seem to be 
the path of least resistance and always have nice *Solaris drivers.

Thanks for any comments,

Jerry

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

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

[OpenIndiana-discuss] Creating packages

[bentahyr]

Hi,

I started to makeput in place mechanism/structures to build packages.
But I have the following problem when I want to install a package from a client 
(host is hosting the repo and oi-dev is the test client, both are 151a9).

ben@host:~/tmp/build_home$ pkgrepo info -s /export/data/oi-project/oi-dev/repo  
  
EDITEUR   PACKAGES STATUT   MIS A JOUR
extra-dev 1online   2014-12-22T08:12:09.675506Z
ben@host:~/tmp/build_home$ pkgrepo list -s /export/data/oi-project/oi-dev/repo
EDITEUR   NOM   O VERSION
extra-dev developer/build/autogen 
5.18.4,5.11-0.151.1.9:20141222T081209Z

ben@oi-dev:~$ pkg info -r pkg://extra-dev/developer/build/autogen   

  Name: developer/build/autogen
   Summary: autogen - GNU autogen utility
   Description: GNU autogen - repetitious text utility (5.18.4)
  Category: Development/Other Languages
 State: Not installed
 Publisher: extra-dev
   Version: 5.18.4
 Build Release: 5.11
Branch: 0.151.1.9
Packaging Date: 22 décembre 2014 08:12:09 
  Size: 2.59 MB
  FMRI: 
pkg://extra-dev/developer/build/autogen@5.18.4,5.11-0.151.1.9:20141222T081209Z

ben@oi-dev:~$ sudo pkg install -vn pkg://extra-dev/developer/build/autogen
Password: 
Creating Plan /
pkg install: No matching version of developer/build/autogen can be installed:
  Reject:  
pkg://extra-dev/developer/build/autogen@5.18.4,5.11-0.151.1.9:20141222T081209Z
  Reason:  This version is excluded by installed incorporation 
pkg://openindiana.org/consolidation/sfw/sfw-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z

ben@oi-dev:~$ pkg publisher
PUBLISHER TYPE STATUS   URI
openindiana.org   origin   online   
http://pkg.openindiana.org/dev/
sfe   origin   online   
http://pkg.openindiana.org/sfe/
sfe-encumberedorigin   online   
http://pkg.openindiana.org/sfe-encumbered/
extra-dev origin   online   http://host:9001/

It might be quite easy for you guys, but I don't understand this incorporation 
stuff and why it exclude my version of autogen.
Does anyone know about it ?

Best regards
Ben

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

Re: [OpenIndiana-discuss] About moving to hipster

[bentahyr]

Harry,

I'm in the same situation. I refreshed a few application and would like to 
offer to the community.
From what Nicola posted, I'm trying to set up a process to do this:
There are 2 steps that I'm working on right now (well, late at night):
1 - How to make an IPS package (found some docs here and there including oracle 
website)
2 - How to make a clean and reproducible environment to :
2.1 - compile/build
2.2 - test install and software

The first one seems quite simple and writing a simple process to do it 
shouldn't take long.
The second one is a bit trickier as I'm not familiar with zones and vbox seems 
a bit overkill for this task.

If I have to step in, I have this problem as well, and would like to have an 
answer, which is to define what compiler I should use :
1 - stay as close as possible to oracle solaris using SunStudio
2 - GNU userland and compilers and which version should I aim for.

It seems that some decisions have to be made, indeed.

Best regards.
Ben

- Mail original -
De: "Harry Putnam" 
À: openindiana-discuss@openindiana.org
Envoyé: Jeudi 16 Octobre 2014 08:51:03
Objet: Re: [OpenIndiana-discuss] About moving to hipster

"Nikola M."  writes:

> On 10/13/14 05:42 PM, Harry Putnam wrote:
>> Can any of you tell me how one navigates the pkgs.  In my install
>> there seems to be no pkg manager.
>>
>> I'm familiar with the pkg cmdline but digging out specific stuff
>> without the name is a bit primitive. And time consuming.
>
> Hi Harry,
> GUI packagemanager and update manager were removed from upstream
> Oracle codebase and need maintaining to be included back.
> Hipster pulled upstream changes and lost GUI tools this year, without
> actions on fixing issue or getting to maintain it. (and it was broken
> in Hipster from Hipster's day1, anyway)
> Someone (aurelien larcher) posted it on Github:
>
> https://github.com/alarcher/packagemanager
>
>> It is just a repository with EOLed files but at least it is somewhere.
>
> So it could be first thing to do , Getting back Packagemanager and
> update manager back to working state.
> But maybe even better then that, it would be better
> to make connection between tested /dev releases and Hipster - in a way
> you exactly needed,
> and that is updating from /dev with a chance of using new /dev in the
> future in line with existing ones.
>
> Getting back update manager and Package manager is required for new
> /dev anyway.
> See if you can include yourself on oi-dev mailing list.

Thanks for all the helpful information you've been posting.

I want to step off into helping in some low level way to get oi and
hipster up to speed.

Trying to work that in to something I need done ... turns out to be
sendmail. 

Unless I've really missed some important things (which is not at all
unlikely) It seems I am not able to get a working sendmail setup
going.

I suspect pilot error, but it actually appears that something may be
wrong with the way sendmail.cf gets generated.

I will need to put the rest into a different post but please try to
explain once more how I should go about this.

Currently I've download the latest sendmail sources and compiled
them. I haven't installed as yet.

So lets say I want to bring the sendmail oi/hip uses more up to date.

If I just build and install and start using it... I've only made my
own oi/hip install un-updateable... what to do?

It may be best to wait until I post about what I think may be a
sendmail pkg bug and get some help in determining if it is really a
bug.

Please watch for post... Subject: Sendmail is the pkg buggy?


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

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

[OpenIndiana-discuss] Firefox and newcomers

[bentahyr]

Hi,

I'm jumping in as the activity seems to increase after the bash bug lately and 
there's a will to organise things.

I see a lot of people requesting Firefox and other Mozilla softwares, just to 
to make sure everyone is aware that Mozilla still provides binaries for Solaris 
platforms :

ftp://ftp.mozilla.org/pub/firefox/releases/latest-esr/contrib/

And they work very well with a9 (except the limited amount of plugins available 
especially the ad blockers).

Now as I've been using more and more a9 as a base I would like to know what 
is/would be the process to get involve in testing as you guys want to test 
things and to publish newer version of packages for various applications.

As I'm a console user, I have elinks, mutt and other standard tools like these 
in recent version recompiled with Sunstudio 12.3 as much as I can and I started 
to play with gcc 4.9.1 to some extend.

So yes... to sum up :
1 - If I want to provide some application in packaged form and submit them to 
"OI", how should I do that ?
2 - If I want to help for testing things without "moving to hipster" how should 
I do that ? (vbox, zones)

As soon as there are clear process for these 2 things, it should be easier for 
people to jump in and contribute.

Best regards.
Ben

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