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

[Al Slater]

Hi,

I am currently using a Quadro K2000 (GK107GL)

regards

Al


On 02/10/2019 20:16, Michal Nowak wrote:
> Hi,
>
> which nvidia graphics card type you use with OpenIndiana?
>
> Currently we ship the version 340 of nvidia Solaris driver, which
> supports following cards:
> https://www.nvidia.com/Download/driverResults.aspx/135163/en-us.
> However, newer devices are not supported in this driver version.
>
> I was wondering if users are fine with a newer version like 390? It adds
> new cards but drops old ones. List of supported cards in this version:
> https://www.nvidia.com/Download/driverResults.aspx/149144/en-us.
>
> Anyone knows might be affected? (I don't have a plan, just wondering.)
>
> You can get the type of graphics card with `nvidia-settings` or in
> /var/log/Xorg.0.log file.
>
> The other, proper solution is to have a way to switch between driver
> versions but work on this stalled some time ago.
>
> Thanks,
> Michal
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss


Essiell is a limited company registered in England with company number: 1957652 
and VAT registered number: GB 760 2433 55. Our registered office is at 5th 
Floor, Park Gate, 161-163 Preston Road, Brighton, East Sussex BN1 6AU.
This message is intended solely for the addressee and may contain confidential 
information. It may also contain material which is subject to legal privilege. 
If you have received this message in error please delete it and all copies from 
your system and notify us immediately by return email.
For information about how we process data and monitor communications please 
read our Privacy Policy and Cookie 
Policy. And please read our Terms of 
Use when visiting our website.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Alternate web browsers?

[Al Slater]

Hi,

I had the same error when I tried to build the new firefox.

I tracked this down to clang, which seems to be built to look for the
gcc includes in the wrong place.  Presumably because it was built
against a slightly older version of gcc6.

clang was looking in /usr/gcc/6/include/c++/6.4.0 for the includes, but
the system has /usr/gcc/6/include/c++/6.5.0.

I solved the problem with a link

root@buildzone:~# ls -l /usr/gcc/6/include/c++/
total 18
lrwxrwxrwx   1 root root   5 Apr  2 04:05 6.4.0 -> 6.5.0
drwxr-xr-x  13 root sys   99 Apr  2 04:03 6.5.0

I could then complete the firefox build.

Which is now running on my system.

The only issue that I have spotted so far is that the branch dropdown in
github projects does not work.

Al

On 01/04/2019 20:26, Stephan Althaus wrote:
> Hi Till!
>
>
> I think i followed the instructions carefully, but i have get a build error.
> I did a pkg update now  to prove that the system is up to date,
> the error remains the same..
>
> I did a short pkg list to list what gcc have installed:
> steven@dell:/rpool1/build/oi/vanilla/oi-userland/components/web/firefox$
> pkg list|grep gcc
> developer/gcc-6
> 6.5.0-2018.0.0.1   i--
> developer/gcc-7
> 7.4.0-2018.0.0.0   i--
> developer/illumos-gcc
> 4.4.4-2018.0.0.6   i--
> sfe/system/library/gcc-49-runtime (localhostoih)
> 4.9.4-0.2017.0.0.5 i--
> sfe/system/library/gcc-runtime (localhostoih)
> 4.9.4-0.2017.0.0.5 i--
> system/library/gcc-3-runtime
> 3.4.3-2018.0.0.3   i--
> system/library/gcc-4-runtime
> 4.9.4-2018.0.0.6   i--
> system/library/gcc-6-runtime
> 6.5.0-2018.0.0.1   i--
> system/library/gcc-7-runtime
> 7.4.0-2018.0.0.0   i--
>
> The hopefully unneccesary parts <--snipped--> away:
>
> steven@dell:/rpool1/build/oi/vanilla/oi-userland/components/web/firefox$
> nice nice gmake publish
> (cd
> /rpool1/build/oi/vanilla/oi-userland/components/web/firefox/build/amd64
> ; /usr/bin/env
> PATH=/usr/bin/amd64:/usr/bin:/usr/gnu/bin:/usr/sbin:/usr/perl5/bin
> CC=/usr/gcc/6/bin/gcc CFLAGS="-m64 -O3 " CXX=/usr/gcc/6/bin/g++
> CXXFLAGS=" -m64 -O3 " LDFLAGS="-m64 -lm" MOZILLA_OFFICIAL=1
> MOZ_TELEMETRY_REPORTING=1 MOZ_PACKAGE_JSSHELL=1 MOZ_PKG_FORMAT=XZ
> PKG_SKIP_STRIP=1 MOZILLA_PKG_NAME=firefox SHELL="/bin/bash"
> LDFLAGS="-L/rpool1/build/oi/vanilla/oi-userland/components/web/firefox/build/amd64/dist/lib
> -L/rpool1/build/oi/vanilla/oi-userland/components/web/firefox/build/amd64/dist/bin"
> PYTHON="/usr/bin/amd64/python2.7" /usr/bin/env
> PATH=/usr/bin/amd64:/usr/bin:/usr/gnu/bin:/usr/sbin:/usr/perl5/bin
> CC=/usr/gcc/6/bin/gcc CFLAGS="-m64 -O3 " CXX=/usr/gcc/6/bin/g++
> CXXFLAGS=" -m64 -O3 " LDFLAGS="-m64 -lm" MOZILLA_OFFICIAL=1
> MOZ_TELEMETRY_REPORTING=1 MOZ_PACKAGE_JSSHELL=1 MOZ_PKG_FORMAT=XZ
> PKG_SKIP_STRIP=1 MOZILLA_PKG_NAME=firefox SHELL="/bin/bash"
> LDFLAGS="-L/rpool1/build/oi/vanilla/oi-userland/components/web/firefox/build/amd64/dist/lib
> -L/rpool1/build/oi/vanilla/oi-userland/components/web/firefox/build/amd64/dist/bin"
> PYTHON="/usr/bin/amd64/python2.7" \
> /usr/gnu/bin/make\
> )
> make[1]: Entering directory
> '/rpool1/build/oi/vanilla/oi-userland/components/web/firefox/build/amd64'
>
> <-- snip -->
>
>Compiling style_traits v0.0.1
> (/rpool1/build/oi/vanilla/oi-userland/components/web/firefox/firefox-60.6.1/servo/components/style_traits)
> warning: use of deprecated item 'std::ascii::AsciiExt': use inherent
> methods instead
>   --> servo/components/style_traits/viewport.rs:10:30
>|
> 10 | #[allow(unused_imports)] use std::ascii::AsciiExt;
>|  
>|
>= note: #[warn(deprecated)] on by default
>
>Compiling style v0.0.1
> (/rpool1/build/oi/vanilla/oi-userland/components/web/firefox/firefox-60.6.1/servo/components/style)
> error: failed to run custom build command for `style v0.0.1
> (/rpool1/build/oi/vanilla/oi-userland/components/web/firefox/firefox-60.6.1/servo/components/style)`
> process didn't exit successfully:
> `/rpool1/build/oi/vanilla/oi-userland/components/web/firefox/build/amd64/toolkit/library/release/build/style-dcf3b3f3b2b5fc51/build-script-build`
> (exit code: 101)
>
> <-- snip -->
>
> --- stderr
> /rpool1/build/oi/vanilla/oi-userland/components/web/firefox/build/amd64/dist/include/mozilla/Compiler.h:49:10:
> fatal error: 'cstddef' file not found
>
> <-- snip -->
>
> stack backtrace:
>0:   0x82a33e -
> std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h563f81f6af186079
>1:   0x83eda6 -
> std::sys_common::backtrace::print::h8ed111738dc46dbe
>2:   0x8334db -
> std::panicking::default_hook::{{closure}}::h852231eb38896e30
>3:   0x833238 - std::panicking::default_hook::h555d38db9a26f1fd
>4:   0x833bbb -
> std::panicking::rust_panic_with_hook::h4c5650c84c4200c9
>5:   0x833749 -
> std::panicking::continue_panic_fmt::h0364dd584f19717c
>6:   

Re: [OpenIndiana-discuss] Amazon AMI

[Al Slater]

Hi Jacques,

On 24/05/18 14:14, Jacques Hugo wrote:
> I’m assuming the question was asked before, but did anyone successfully 
> create an AMI image of OI Hipster?

See
https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/

regards

-- 
Al Slater

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

Re: [OpenIndiana-discuss] Firefox 32bit future

[Al Slater]

On 25/01/18 18:57, Alan Coopersmith wrote:
> On 01/25/18 10:40 AM, russell wrote:
>> Is there any immediate danger of Mozilla retiring the 32bit version of 
>> Firefox?
> 
> I believe the most immediate item of concern is that Firefox now uses code
> written in Rust, so you'll be limited to platforms that the Rust compiler
> generates code for, and I don't know if anyone is bothering to do 32-bit code
> generation for Solaris/illumos in Rust.
> 
> Of course, with the elimination of Netscape plugin support, there's little
> reason to still use a 32-bit version of Firefox.

Apart from the fact that 32bit versions die before gobbling *all* of
your system RAM.  I find this "feature" very useful!

-- 
Al Slater

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

Re: [OpenIndiana-discuss] ZFS and encryption

[Al Slater]

Hi Kai,

On 24/07/17 19:44, Kai Windle wrote:
> Hello, Thank you for the fast replies. Other than the link that
> Andrew provided how do people using Illumos based distributions go
> about using encryption for their hard drives?

I don't need full disk encryption, but I use lofi to encrypt zfs volumes.

See https://blogs.oracle.com/darren/encrypting-zfs-pools-using-lofi-crypto


> On 24 July 2017 at 19:22, Alexander Lesle
>  wrote:
> 
>> Hallo Kai,
>> 
>> all Illumos based distributions have no ZFS encryption at the 
>> moment.
>> 
>> On Juli, 24 2017, 19:48  wrote in [1]:
>> 
>>> Hi all,
>> 
>>> I'm just making a quick inquiry as to whether ZFS has encryption
>>> built
>> into
>>> OI? I've tried googling around but nothing appears to be giving
>>> me a
>> definitive
>>> yes or no answer.
>> 
>>> If encryption is not supported via ZFS how would I go about
encrypting my
>>> entire hard drive?
>> 
>>> Sorry I'm still new to Openindiana
>> 
>>> Many thanks
>> 
>> 
>>> Kai. ___ 
>>> openindiana-discuss mailing list 
>>> openindiana-discuss@openindiana.org 
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>> 
>> -- Best Regards Alexander Juli, 24 2017  [1]
mid:CAG838zjnN-baTmyocTT1gVH6HNWaFYsMY0e=9h3pdtoduix...@mail.gmail.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
> 


regards

Al




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

Re: [OpenIndiana-discuss] Am i banned from list?

[Al Slater]

On 09/04/2016 13:14, Predrag Zecevic wrote:
> Test,
> 
> because my posts are not distributed.
> Please, ignore...



FYI, I have received the following from you 3 times in the last 5 days

[OpenIndiana-discuss] /hipster: latest kernel updates cause crash when
vbox guest is started

and the following once

[OpenIndiana-discuss] Filter on openindiana-discuss@openindiana.org

-- 
Al Slater



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

Re: [OpenIndiana-discuss] recommendation for a distribuition to run Virtualbox on?

[Al Slater]

On 22/04/2015 11:59, Jonathan Adams wrote:

As far as I know, I run the Solaris VirtualBox without trouble on my OI
hipster, and I've seen discussions on the use of VirtualBox on XStreamOS.


I run VirtualBox on XStreamOS with no issues.  I have windows and omnios 
guests running just fine.


I can recommend XStreamOS desktop, it has a few rough edges but is very 
stable.


--
Al Slater





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

Re: [OpenIndiana-discuss] What encryption options are available? [b 151_9]

[Al Slater]

On 26/08/2014 15:31, Harry Putnam wrote:

Bob Friesenhahn bfrie...@simple.dallas.tx.us writes:


On Tue, 26 Aug 2014, Harry Putnam wrote:


Hopefully I've gotten it all wrong.
I'd hoped for something as simple as `encfs', then read that encryption
was now built into zfs.  But then it appears not to be so for oi?


Zfs encryption is for the data stored on disk and is not 'file'
level. Regardless, it is not provided for OpenIndiana.  FreeBSD has an
encryption layer which can be used on devices underneath zfs.


Can anyone spell out what is available to use on OI 151_9 in the way
of really basic encryption?

I'm basically only looking for something that would baffle script
kiddies.  I don't expect to be attacked by serious players.


If you want to protect individual files you could install and use pgp.

The problem with so-called script kiddies is that usually such
scripts are run from within the cone of trust so they have access to
decrypted data.  If the filesystem automatically decrypts the data for
the applications (the normal case for an encrypting filesystem), then
a script running on that filesystem is able to use it.


Thanks for the good info.
Maybe I should provide a description of what I want to do.

With encfs... which I've used on other os's until now, works like this:

Create a password protected container then whatever you put in it is
encrypted.

I keep only things like uid and passwords for the dozens of things one
collects over time, and bits of info I'd rather not share.  Nothing too
drastic.  But I guess UID and Passwd would be enough to drain my bank
account of all 50 bucks ... hehe.

What I do is (manually )open the containter when I need something
which is usually like once/twice per day or so, then close the
container. So basically it stays encrypted most of the time.

There is no automatic application access involved.

So, I guess a script kiddie would have to first hack my host, then
hack my UID/Passwd, and then hack the passwd on the encrypted
container.

As it is now, even root does not have access to the container without
the passwd.

So, all and all, I guess I'm looking for something that works along
those lines.


How about a lofi encrypted zvol?

https://blogs.oracle.com/darren/entry/encrypting_zfs_pools_using_lofi


--
Al Slater




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

Re: [OpenIndiana-discuss] CIFS performance issues

[Al Slater]

On 26/01/2012 08:32, Open Indiana wrote:

Please skip the whole ifconfig and plumb this or that discussion.

Virtualbox works on any interface that is plumbed since only then the
interface is visible in the menu.


That is untrue.  All interfaces are visible in VB regardless of whether 
they are plumbed or not.  Just verified that on OI and Solaris 10.


--
Al Slater



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

Re: [OpenIndiana-discuss] Linux vs. Solaris

[Al Slater]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 29/03/2011 15:00, Apostolos Syropoulos wrote:
 
 
 A friend of mine who is a long time Linux user but with
 an interest in OpenIndiana and OpenBSD and NetBSD
 asked me to send the following. Message.
 
 A.S.
 
 --
 Apostolos Syropoulos
 Xanthi, Greece
 
 
 
  
 Gary Gender wrote:
 
 For example, init 0 on Linux vs init 5 
 on Solaris and init 5 vs init 6.  I'm not sure if all of them can be 
 resolved for everyone.  I came from the other end...  A long time 
 Solaris admin going to Linux.  Why didn't everyone scream that Linux 
 doesn't do the right thing?
 
 The problem is always legacy stuff.  If you change the behaviors then 
 expect that things that people wrote for Solaris to fail.  For example, 
 napp-it, webmin, etc.
 
 +1
 --
 Apostolos Syropoulos
 Xanthi, Greece
 Why should solaris change the commands to immitate linux ? Who said
 the linux behavior is correct and the solaris one is wrong ?
 
 Neither a install-time choice is needed/correct. What if i use the
 linux way in my box and then go to fix some problem on my friend's box
 that didn't choose the linux way ? 
 
 The proper fix is to educate solaris users. I know that the manpage
 for reboot has all the information, but a put_OS_here user will suppose
 the behavior is the same and won't read the manpage. Also, it is difficult
 to read 100 manpages in order to use the system. A wiki page or tutorial
 or whatever that contains useful information would be the best solution IMHO
 to get things started and from then ofcourse there are the manpages.

What rubbish!  Suppose I spend all day administrating solaris boxes and
then I have to administer a linux box occassionally.  Clearly, following
your logic above, the linux boxes need fixing because it is different
and I won't read a man page for some reason.

Unfortunately for your logic, that is exactly what I do.  I spend 95% of
my time using solaris, 1% of my time using linux and 4% on other
flavours of stuff.  They all have slight nuances and I have to learn
them.  It's not hard.

- -- 
Al Slater

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2R8i0ACgkQz4fTOFL/EDYeHACglxIa3Mf88s5pAGvuzu3LymFH
+FQAnjX1WLpJ5t5TDcsq9lUsRkRyuCwZ
=xMDb
-END PGP SIGNATURE-


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

Re: [OpenIndiana-discuss] OI boot problem

[Al Slater]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 28/03/2011 13:58, Apostolos Syropoulos wrote:
 The shutdown command certainly is not broken.  If indeed the Linux
 newbie must be catered to, then we can change the defaults, and tell
 them to just use shutdown.
 
 This command does not do the expected thing and that is the problem.

The reboot command most certainly does do exactly what I expect it to
do, and what it has been successfully doing for years.  It may not do
what *you* expected it to do, but you know different now?

- -- 
Al Slater

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2QjhUACgkQz4fTOFL/EDZE5wCeMYD/X7WQhjygPJX9NcJbmu/9
uooAnjsUJ9yT1IfFJ5fh9SwZy48712ds
=6Chk
-END PGP SIGNATURE-


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

Re: [OpenIndiana-discuss] OI boot problem

[Al Slater]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 28/03/2011 14:53, Apostolos Syropoulos wrote:
 This command does not do the expected thing and that is the problem.

 The reboot command most certainly does do exactly what I expect it to
 do, and what it has been successfully doing for years.  It may not do
 what *you* expected it to do, but you know different now?

  
 Really? Do you know how many times my system became useless
 just because I had used reboot? 

Nope.  But I have used it 1000s of times on test and production systems
and have never managed to render a system useless.


- -- 
Al Slater

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2QlW0ACgkQz4fTOFL/EDbrUQCfW8QvT/8dAq1B/XEUC2eNL4V3
zmMAnAupfU9QcHrNntiOnXdCuXFUJffh
=qDoA
-END PGP SIGNATURE-


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

Re: [OpenIndiana-discuss] OI boot problem

[Al Slater]

On 28/03/2011 5:51 PM, Michael Schuster wrote:

On Mon, Mar 28, 2011 at 17:39, Apostolos Syropoulos
asyropou...@yahoo.com  wrote:

SunOS has a long history of providing many flavors of commands. No one will
object to adding a few.  However, changing the behavior of commands that have
been around for 20+ years really doesn't make any sense.  Many of these are


But that is exactly the problem with these commands: they are too old and
outdated. In many respects this was the main problem of Solaris: it was
not moving fast enough.


I fail to see the benefit of changing well-known behaviour in an
incompatible way. Change for the sake of change may be chique for
fashion items, but not necessarily a good thing in a server-grade OS.


+1


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