Re: [OpenIndiana-discuss] elegant way to move from PHP-81 to PHP-82

[Till Wegmüller]

Hi Stephan

Not really if you only want to have specific packages installed.
The only other thing is to install all php-82 packages.

-Till

On 17.05.24 10:09, Stephan Althaus wrote:

Hello!

Is there a more elegant way to move from php-81 to php-82 than this:

pkg list | grep php | grep 81 | awk '{print $1}' | sed "s/81/82/g" | 
xargs pfexec pkg install


.. maybe something by changing a mediator ??


Regards,

Stephan




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


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

Re: [OpenIndiana-discuss] Sun Management Centre

[Till Wegmüller]

Hi Rainer

I am happy to dig through the docs and provide commands for what you 
need. Thus far I simply did not have the need to dig into RBAC related 
things.


Please file issues on the docs what you are missing so we can 
collaboratively fix them. Please also only use material on 
docs.openindiana.org and the welcome pages. Other material out on the 
web is not necessarily under our control and google has started to die 
slowly, so searches may result in bad results.


-Till

On 14.05.24 08:52, Rainer Heilke wrote:


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


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


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

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


thanks,
toomas


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


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


Rainer



___
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] Co Working Session Sunday April 28th 2024

[Till Wegmüller]

Hello all,

The work on OpenIndiana continues. Join us tomorrow Sunday at 17:00 CEST 
at https://meet.chaostreffbern.ch/OpenIndianaCoWorkingSessions there are 
rumblings of people working on software and we want to look again into 
package quality.


-Till

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

[OpenIndiana-discuss] No CoWorking session this week due to easter

[Till Wegmüller]

Hello all

We will not have a CoWorking Session tomorrow due to easter :) Enjoy the 
time with the family and don't hack too much. Burnouts are literally a 
Risk to national security!


Sorry had to make that pun
/shows himself out to easter

Happy easter
Till/Toasterson

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

[OpenIndiana-discuss] CoWorking Session 24.03.2024

[Till Wegmüller]

Hello all

Just a quick late reminder.
Don't forget this weeks #OpenIndiana CoWorking Session today Sunday 
17:00 CET at https://meet.chaostreffbern.ch/OpenIndianaCoWorkingSessions


-Till

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

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

[Till Wegmüller]

On 13.02.24 14:03, Marcel Telka wrote:

On Tue, Feb 13, 2024 at 01:56:07PM +0100, Till Wegmüller wrote:

libdrm 109 is in the pipeline if somebody can get the builds to compile on
gcc13. It's a bit out of my depth unfortunetely.

https://github.com/illumos/gfx-drm/pull/26


Unfortunately, the illumos/gfx-drm seems stale.  We should probably dust
off https://github.com/OpenIndiana/gfx-drm and switch oi-userland to use
it instead of https://github.com/illumos/gfx-drm.



Gordon Ross answered me within a day last thing I asked. I don't think 
that is necessary. But we need somebody to freshen up the PR :)


Also @alarcher can you provide a list or a bug report on 
illumos.org/issues so we can get somebody to work on adding those 
components?


-Till

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

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

[Till Wegmüller]

On 13.02.24 09:46, Aurélien Larcher wrote:
We lack support for hdmi audio. This is provided in recent drm code, I 
think the code can be ported easily from the OpenBSD/FreeBSD source. I 
had a drm tree synchronized with libdrm 100, more recent kernel driver 
sources, and hdmi but it would freeze now and then so I never got the 
chance to integrate it.


Hello,

libdrm 109 is in the pipeline if somebody can get the builds to compile 
on gcc13. It's a bit out of my depth unfortunetely.


https://github.com/illumos/gfx-drm/pull/26

-Till

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

[OpenIndiana-discuss] Info CoWorking sessions

[Till Wegmüller]

Hello all

Reminder: Tomorrow Sunday 17:00 CET Coworking sessions are at 
https://meet.chaostreffbern.ch/OpenIndianaCoWorkingSessions


Some people want to show some of their work I hear :)

Hope to see many of you all there.

-Till

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

Re: [OpenIndiana-discuss] Known Problem with IPS

[Till Wegmüller]

On 14.01.24 15:30, Bob Friesenhahn wrote:
The fastest JSON parser I am aware of was developed by a previous 
work-mate. It is at 
"https://github.com/gdavidbutler/jsonTrivialCallbackParser".  There is a 
trade-off in that it places more responsibilities on the using code and 
thus any performance issues will be due to the using code.  If this was 
attached to Python (using a C-language glue layer), then Python would be 
the bottleneck. Perhaps the license (LGPL-3) is not good for OpenIndiana.


Using C code to read JSON and transform it to the database used for the 
rest of the work seems more feasible.


We already use RapidJSON. But the base JSON is then turned into OOP 
classes and so on. It will require some carefull programming. But yes 
something like rust or C to read the JSON repo to a base definition and 
having the python only handle the image/base parts is the idea.


-Till

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

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

[Till Wegmüller]

On 09.01.24 18:14, Alan Coopersmith wrote:

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


mate_install is the metapackage of toplevel packages we install manually 
for a GUI install. It's direct dependencies should count as the toplevel 
for analysis.


-Till

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

Re: [OpenIndiana-discuss] 32-bit libraries disappearing

[Till Wegmüller]

Hi Mathew

On 08.01.24 04:40, Matthew R. Trower wrote:


Well, I'd be willing to commit time towards such an effort.  I'd 
certainly rather commit that time to the main project, than maintain my 
own private fork.  We'd need to discuss what the workload is, what I can 
help with, and whether that help would be enough to make a difference.


To further discuss this, is mail the best medium or would it be better 
for me to show up to a meeting?  If a meeting is best, could you please 
give a time and venue?


Awesome to hear!

We have multiple mediums that you can join in for.
- mail. On this list as Usual and in oi-dev
- meetings. I offer the CoWorking sessions for people that are new to 
the Project they are good to get some discussion going on the projects. 
With you we are already 4 or 5 semi permanent visitors.

- github. All PR related discussions are held on GitHub.

I Usually give out a mail for the meetup but they are on Sunday 17:00 
CET at https://meet.chaostreffbern.ch/OpenIndianaCoWorkingSessions


-Till

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

Re: [OpenIndiana-discuss] NUC boot

[Till Wegmüller]

Then it's indeed the USB Key which is not found by the kernel, but found 
by loader.


Can you try out the back ports where the keyboard is currently plugged 
in? My NUC has a problem with the USB in early boot but they come online 
eventually.


-Till

On 30.10.23 15:54, James via openindiana-discuss wrote:

On 30/10/2023 13:14, Till Wegmüller wrote:


Can you press control-d at this screen and grab the output of "svcs -xv"


control-d refers me to /lib/svc/share/README and goes back to the same 
place "Console login service(s) cannot run".


User name root gets a shell prompt but svcs is not on the path and I can 
not find it.  "find" is not there either which makes finding harder. "ls 
/**/svcs", No such file...



James.


___
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] NUC boot

[Till Wegmüller]

Hi James

Can you press control-d at this screen and grab the output of "svcs -xv"

Thanks
Till

On 29.10.23 13:50, James wrote:

Good afternoon,

I am playing with an Intel NUC 7PJYH3 [1], J5005 CPU, 16GB RAM.
Openindiana boot from USB fails, text install or live, transcript from 
screen grab:


---begin
Loading unix...
Loading /platform/i86pc/amd64/boot_archive...
Loading /platform/i86pc/amd64/boot_archive.hash...
Booting...
OpenIndiana Hipster 2023.04 Version illimos-676abcc77c 64-bit
WARNING: sdhost0: slot 0: Host does not support standard voltages.
WARNING: sdhost0: slot 0: Unable to initialize card!
WARNING: sdhost0: slot 0: Host does not support standard voltages.
WARNING: sdhost0: slot 0: Unable to initialize card!
Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  570.182.03 
  Fri Feb 24 03:20:38 UTC 2023

Hostname: openindiana
Remounting root read/write
Probing for device nodes...
Preparing live image for use
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login services(s) cannot run

Enter user name for system maintenance (control-d to bypass)
---end

I can login as root but I see nothing much and I am not sure what system 
maintenance I am supposed to do at this stage.



Note OmniOS runs from the boot USB, exit to shell and it seems to behave.

Is there any hope of me avoiding Linux on this?


James.


1. 
https://ark.intel.com/content/www/us/en/ark/products/126137/intel-nuc-kit-nuc7pjyh.html


___
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] Mailman available via Web again

[Till Wegmüller]

Hello Everyone

As most other options have ran aground I put the new openindiana website 
on an Nginx server in our infra and setup a couple of reverse proxy 
entries for mailman. While this is not ideal it makes all links work 
again :)


Greetings
Till

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

Re: [OpenIndiana-discuss] Readahead Batch error

[Till Wegmüller]

Considering that SMB comes from Windows, this might be intentional.

-Till

On 21.07.23 20:51, Michelle wrote:

Hi Till,

Unfortunately it didn't work.

I tested by running a video and then attempting to rename it while it
was running.

Previously it worked on ver 1.0 but even with cache=none and ver=3.0 it
failed to rename with the resource temporarily unavailable.

I'll read up on the cache variable and see what options I can try.

Michelle.

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

Hey Michelle

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

-Till
On 21.07.23 13:41, Michelle wrote:

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

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

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

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

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

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

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

Errors received in syslog are...

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

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


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



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


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

Re: [OpenIndiana-discuss] Readahead Batch error

[Till Wegmüller]

Hey Michelle

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


-Till
On 21.07.23 13:41, Michelle wrote:

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

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

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

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

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

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

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

Errors received in syslog are...

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

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


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

Re: [OpenIndiana-discuss] list archives?

[Till Wegmüller]

On 21.07.23 02:22, Carl Brewer wrote:
Given the apparent reluctance to maintain this mailing list (despite the 
benefits - open, it's an automagic archive, it's enough of a barrier to 
entry to stop modern spammers but everyone has email) etc etc


What -should- we be using to report issues & help each other?

I would suggest lemmy https://join-lemmy.org/

-Till

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

Re: [OpenIndiana-discuss] list archives?

[Till Wegmüller]

On 20.07.23 21:15, James Madgwick wrote:


So it is not possible to have a new domain to host the mailman site
pages (say lists.openindiana.org)?
Nope, I tried I would need to hack the database and I have to hack that 
admin account first Mailman basically binds the list to the domain.



r/OpenIndiana and r/illumos have been around a while and don't get much
traffic. While this decentralised stuff is interesting, I'm not sure
it would be much more popular than Reddit.


It actually is looking at the engagement the other illumos projects get.



I would hope that any migration would continue to support the old way
of doing things, at least for a while. Otherwise there would be a risk
of the community being lost for good.

Something which could help as an interim step would be a site using
something like Ponymail (https://ponymail.apache.org/). This allows
users to easily browse the list online and to reply online.


Yeah Topicbox is basically a competitor to Ponymail with a hosted setup 
ontop of illumos and is currently hosting almost all other illumos 
project. Unfortunately the admin for illumos.org is currently on hiatus 
to finish all the stuff Oxide has been working on. Until he is back that 
migration plan is on hold


Frankly I might have to bite the bullet on mailman due to the 
illumos.org abmin being on hiatus so that we at least have something. 
Although Pony mail seems to be a solution? I'll have to play around with 
it but I might be able to make it work.


Let's see.

-Till

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

Re: [OpenIndiana-discuss] list archives?

[Till Wegmüller]

Hi James

There are no plans for the mailing list other to at least replace the 
mailman setup with something I don't have to administer and can update. 
The Mailman links exist but I cannot change things there so that they 
would be available under a new Domain. The site went offline as I could 
not teach GitHub pages to do the same redirect thing that nginx did before.


I am in favour of a modern Fediverse setup so if we found a Lemmy server 
(Open and federated version of Reddit) we could see to migrate there.


Our mailinglist is only used for existing people with very few new 
signups. And currently only the mailman subscribe via mail mechanism is 
usable. [0] A technology where people from the FOSS space actually are 
would be better


[0] https://www.list.org/mailman-member/node13.html

-Till

On 16.07.23 15:24, James Madgwick wrote:

Hello,

I was just going through some documentation and noticed this link is
still broken. While it will still be possible to sign up to the mailing
list, there's now no webpage explaining these things.

Do you think that site will be back online or is it gone for good? If
it's gone we'll want to remove the links to it and replace with
instructions for signing up etc. Unless there's a plan to migrate
elsewhere. I would support that, I see mailing lists as increasingly
retro and a barrier to entry for new contributors.


James


On Tue, 9 May 2023 09:43:52 +0200
Till Wegmüller  wrote:


Hi,

Yeah sorry about that. I wanted to change the lists host as to not
conflict with GitHub pages anymore but alas GNU mailman is not
wanting me to do that.

I'll have to check how to change anything there. Personally I would
prefer to migrate to topicbox like all other distros did. But we will
have to see.

For now use https://www.mail-archive.com/ as archive.

-Till

On 09.05.23 08:09, Carl Brewer wrote:

On 9/05/2023 4:08 pm, Espen Martinsen wrote:


... as found in the archive :-)
https://www.mail-archive.com/openindiana-discuss@openindiana.org/


That'll do it.  Maybe whomever runs the list, can fix the footer to
have that in it?




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

     
That's wrong!

Carl


___
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] HP Proliant Microserver N54L Upgrade

[Till Wegmüller]

Hi David

With such an old release version many steps to upgrade are required and 
you are more likely to sucess installing a new System from ISO/USB to 
the existing rpool which will create an independant boot environment 
with newest software.


It wouold also alow you to test the newest release on the Hardware first 
without requiring any changes to your setup.


The Option to install into an existing pool is part of the Installer.

-Till

On 07.06.23 11:52, david allan finch wrote:

Hi All,

Might be interesting to someone out there ;)

I still have this little box, use it as a file server and still using 
oi_151a9.


I have progressively been replacing the HDD with bigger and bigger 
drives and all still works well. I keep think of replacing the hardware 
but never yet really got around to it. I think since the original 2Tb 
HHDs I have increase it to 6Tb, 10Tb, then 14Tb in stages.


I just replace my 3 disk raid5 pool, which used to have 3x14Tb with some 
new 3x20Tb Tosh disks.


Last time it took 10hr each to re-silver the replaced disks from 10Tb to 
14Tb, this time it took 33hr for each disk (ie 100hr to do all three 
over 5 days).


I have tried to update the OS before and always it fails at some point, 
so in the end just stayed with what worked.


On 2/12/15 10:36, david allan finch wrote:

Hi all,

I was wondering if anyone had any ideas of what to do for an upgrade?

I have a HP Proliant Microserver N54L with 4x 2Tb drives which I have 
been happy with for more than a year but I have started to run out of 
disk space in my zfs pool. I have been pruning the snapshots and 
rubbish but filling it up now is inevitable.


What I would really like to do is to swap the disks out for larger one 
but I doubt that this is really practical as to make this work you 
need spare disk slots which I don't have.


Another option might be to add a SATA card and add more disk that way. 
But I have no idea of where to start with this, and even if this 
microserver can do that.


And a third is just to get a new server. I can't see any which have 
more than 4 drive bays do these exist (for reasonable money) or do you 
need to make your own? If so anyone got a recommendation?



___
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] Add inotify support to illumos-gate

[Till Wegmüller]

Hi

You will have to ask on illumos-developer mailinglist
This is the distribution mailinglist I don't know how many illumos 
advocates are lurking here at this moment.


-Till

On 24.05.23 15:37, Stephan Althaus wrote:

On 5/12/23 10:30, Stephan Althaus wrote:

On 5/2/23 20:25, Till Wegmüller wrote:

Hi Stephan

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


What does mate-system-monitor use inotify for?

-Till

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


Hello!

mate-system-monitor dumps core, because of a glib::gio dependency, 
because gio can't find(?) a filesystem-monitor-implementation : 
"g-io-error-quark: Unable to find default local file monitor type".. 
(see below)


It would be nice if we could solve the problem before we announce the 
new release ISO images.


How can we achieve this? i am willing to help, but, because of my 
lacking experience i need someone who tells me what exactly to do..



Regards,
Stephan


$ mate-system-monitor
(:11943): glibmm-CRITICAL **: 10:27:01.361:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 11943:    mate-system-monitor
- thread# 1 / lwp# 1 -
 0044b0a1 
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 111
 7fff73009ab0 
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 160

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

 7fffac50bef3 g_application_run () + 133
 004239f1 main () + 61
 00422d37 _start_crt () + 87
 00422c98 _start () + 18



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


Hello!

Sorry if i am asking something wrong here, if i don't know 'the right 
way' ...


It would be nice to have this smartos-commit (origin 2014) upstreamed to 
illumos-gate:

https://github.com/TritonDataCenter/illumos-joyent/commit/a9a246c0c49e192616e7499eaa2362b21fde8f5e

Is someone willing to support this - at least in a somewhat 'political' 
manner?


Regards,
Stephan


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


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

Re: [OpenIndiana-discuss] Problems with gcc-7 and gcc-10 built binaries

[Till Wegmüller]

Hi Russel

This is an ongoing work and we have been at it for about 2~3 releases 
thus far. So there is a good chance your libarries are already gcc 10. 
We build every update with Gcc10 since the start of the move. However 
some packages also needed more work as they were not Gcc10 compatible in 
the versions we delivered. Thus it always is our strategy in these cases 
to upgrade as independantly as possible between packages. So that we can 
handle the workload with the few people we have.


More helping hands are always welcome.

Greetings
Till

On 21.05.23 22:35, russell wrote:

Hi

Back in October 2022, when I was experiencing issues building 
libfilezilla in response to my posting Till pointed out that gcc-7 and 
gcc-10 have an ABI break.


7/10/22 18:22, Till Wegmueller wrote:


Hi Russel

Thats an ABI break.

Looks like Gcc7 and Gcc10 produce different output.

You will have to compile all with the same compiler.

-Till



So, are there plans to switch to using gcc-10 for the entire build of 
OpenIndiana to eliminate the ABI compatibility issue of mixing gcc-7 and 
gcc-10?


Kind Regards

Russell
___
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] pkg folder size escalated

[Till Wegmüller]

On 18.05.23 22:53, Goetz T. Fischer wrote:

On Thu, 18 May 2023 12:53:48 +0200, Till Wegmüller wrote:

The specific difference you are describing is purely due to our package
manifests not having received a major update to split up SUNWCS.


much thanks for the insight!


We would be quite happy if somebody started carrying the torch in
bringing those package manifest changes upstream into illumos from
illumos-omnios.


what would be required to do so?
Git knowledge and patience to find and group the commits from 
omnios-illumos https://github.com/omniosorg/illumos-omnios that modify 
files under usr/src/pkg and the makefiles and push it through 
https://illumos.org/docs/contributing/


Probably also some Wine and nice mails to the omnios guys as they 
probably have already intended on doing so and have some more info about 
this set of commits or the diff.


If you manage to find a git invocation that shows the differing files 
between forks, that would help a lot already.


Hope this gives a starter
Till

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

Re: [OpenIndiana-discuss] pkg folder size escalated

[Till Wegmüller]

The Software and packaging framework to make packages is roughly the 
same though features have diverged even inbetween illumos distros 
(although a merge is planned there) The package graph however ist 
completely distro dependant. And also different illumos gat forks like 
illumos-omnios have differing package manifests that change the package 
graph extremely.


The specific difference you are describing is purely due to our package 
manifests not having received a major update to split up SUNWCS. Solaris 
finished that migration post source closure/fork. illumos-omnios also 
has updated manifests so omnios will have a smaller chache of files. 
Please also note that linked zones share this cache and it is used to 
restore your system with pkg fix although anything missing will be 
downloaded. In case of openindiana since we are rolling release there is 
however a chance that you'll have to upgrade first before having all 
files available to download and fix the system when a diskoutage too 
your root pool down.


We would be quite happy if somebody started carrying the torch in 
bringing those package manifest changes upstream into illumos from 
illumos-omnios.


-Till


On 18.05.23 11:39, Goetz T. Fischer wrote:

On Thu, 18 May 2023 11:59:52 +0300, Toomas Soome via openindiana-discuss wrote:

those numbers are meaningless without checking what is inside of those files.


sure, but only to some extend. it's both ips. unless of course illumos did a 
massive rewrite there and
just kept the name for historical reasons. and the options and the messages and 
the package format and
... you get the idea :-)


illumos (openindiana) is not solaris. The systems are different and we are not 
intending
to be free clone of Solaris.


i know what illumos is and where it came from and i didn't imply it had to be 
the same either. my
question was about the size of the pkg folder and that i think it's too big. 
which then turned out to be
right considering the solution with flush-content-cache-on-success and its 
result. the latter should be
True by default if i may suggest that.
as for the size, i think even the original solaris pkg folder is too big for 
that number of packages.
looking at rhel for example i see 65mb for 485 packages. of course that depends 
on what packages they
are but it does give a rough estimate.

___
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] pkg update fails

[Till Wegmüller]

Hi all

The problem is, we keep fixing it in new spots. The last time this 
occured was a couple of python versions ago. Now it seems they again 
found a way to trigger this edge case.


We can forcefully set LANG when calling python but that variable can 
leak into the program at anytime from your ENV. Thus in general Please 
use a UTF-8 locale. Any UTF-8 locale will do. C.UTF-8 for root is 
preffered wince we always test with that but any UTF-8 locale will do.


If you have an application or user that needs a non UTF-8 locale try to 
limit the override as close to just the application as possible.


We tried to fight upstream python on this before but it's a Cat and 
mouse game and we are loosing that. As long as pkg is written in python 
this kind of error will keep happening with non UTF-8 locales.


I know this is not the good answer but it's what we can do given the 
circumstances. No other OS is fighting python on the UTF-8 issue anymore.


Hope this clarifies situation.
In short. Try to limit the usage of non UTF-8 locales to non IPS related 
informations.


-Till

On 15.05.23 22:40, Tim Mooney via openindiana-discuss wrote:
In regard to: Re: [OpenIndiana-discuss] pkg update fails, Predrag 
Zečević...:



But, why suddenly that is required? I never had to do it...

Will that be fixed in near future?


I remember a thread about a very similar issue, and I found it:

 Subject: pkg update is failing
 Date: Sept 4, 2019

Predrag posted in that thread (as did I).  At the time, it was suggested 
that

any of the UTF8 locales would be enough.

Tim


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

Re: [OpenIndiana-discuss] pkg update fails

[Till Wegmüller]

Can you try set the LANG variable of the user using pkg to C.UTF-8 and 
try again? Or force root to use C.UTF-8


This seems locale and python related.

-Till

On 15.05.23 17:17, Oscar del Rio wrote:


On 2023-05-15 4:01 a.m., Predrag Zecevic via openindiana-discuss wrote:

Invalid Package Name: dat`base/mariadb-106/client


Bit flip somewhere that turned 'database' into 'dat`base'?

binary ascii code for 'a' is 0111
binary ascii code for '`' is 0110

___
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] geforce 6600 troubles

[Till Wegmüller]

The only thing I can think of is pkgrecv ing the solaris driver from the 
Solaris 10 install and using that as compat solution.



The errors shown are just lightdm complaining we are using consolekit 
and not systemd. Which we wont use so it will keep complaining.


Your 6600 card seems a bit picky. Can you check X.org logs and see what 
it reports? Also please check /var/adm/messages for kernel related 
things. Or boot with verbose mode set to on (you can find that in the 
bootloader under menu 5 advanced options)


Hope this helps to narrow it down
-Till


On 15.05.23 02:37, Goetz T. Fischer wrote:

hello everyone,

i ran into a curious issue with a geforce 6600. since it's not supported by the 
shipped nvidia drivers,
i installed version 304.137 as described there: 
http://docs.openindiana.org/dev/graphics-stack/#nvidia
the procedure worked fine but the driver didn't although the 6600 is listed 
explicitly.
svc:/application/graphical-login/lightdm:default switched to maintenance and 
the log showed the
following errors:

** (lightdm:744): WARNING **: 08:30:19.854: Failed to get list of logind seats:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.login1 was not provided
by any .service files
** (lightdm:744): WARNING **: 08:30:19.871: Error getting user list from 
org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not
provided by any .service files
lightdm: Got tty: '/dev/vt/7'
** (process:758): WARNING **: 08:30:22.571: Error getting user list from 
org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not
provided by any .service files
** (lightdm:744): WARNING **: 08:30:22.698: Error activating ConsoleKit session:
GDBus.Error:org.freedesktop.DBus.GLib.UnmappedError.CkSeatError.Code0: 
Activation is not supported for
this kind of seat

now to the curious part:
i also tried a different way. first i installed the older 173.14.39 and after a 
reboot i installed
version 304.137. both not using the method described in the docs but directly 
i.e. i just ran the files.
no extra bootenv or anything else. this time it worked at least partially: the 
nvidia control center
worked and i had more resolutions to choose from compared to vgatext. however, 
i could still not change
the refresh rate which made this endeavor quite pointless.

that's a pity because with solaris 10 and whatever nvidia driver it has, the 
card worked just fine. if
there're any secrets to getting the nvidia drivers work properly, i would be 
very interested in learning
about them.

thanks in advance for any help


--
R-A-C
Götz T. Fischer CertIT
+49(0)7225/98 98 79
g.fisc...@r-a-c.de
r-a-c.de

___
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] list archives?

[Till Wegmüller]

Hi,

Yeah sorry about that. I wanted to change the lists host as to not 
conflict with GitHub pages anymore but alas GNU mailman is not wanting 
me to do that.


I'll have to check how to change anything there. Personally I would 
prefer to migrate to topicbox like all other distros did. But we will 
have to see.


For now use https://www.mail-archive.com/ as archive.

-Till

On 09.05.23 08:09, Carl Brewer wrote:

On 9/05/2023 4:08 pm, Espen Martinsen wrote:


... as found in the archive :-)
https://www.mail-archive.com/openindiana-discuss@openindiana.org/


That'll do it.  Maybe whomever runs the list, can fix the footer to have 
that in it?





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

    
That's wrong!

Carl


___
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] usb3 with openindiana

[Till Wegmüller]

Hi

That is unfortunately a piece of Hardware we never test as we have USB3 
ports usually in all setups I am aware. So there wont be a report.


It should generally just work as USB is pretty standardised so is PCIE. 
So if you can get one inside your Budget that you can get even on risk I 
would try that.


-Till


On 06.05.23 19:16, Marc Lobelle wrote:

Hello

I would like to use an external usb3 disk for backups of an openindiana 
computer without usb3 port (a tower with P8B-M ASUS motherboard). Is 
there an usb3 PCIE add-on card known the work with openindiana ?


Thanks

Marc


___
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] zoom on openindiana

[Till Wegmüller]

An OpenSource Client we could think about supporting is libwebrtc for 
the brwoser versions. Our Firefox may be convinced to add that 
capability since it is present on the Linux build of Firefox.


- https://wiki.mozilla.org/Media/WebRTC/Architecture

- https://webrtc.org/

If somebody gets it built locally I am gladly moving it into our package.

-Till

On 05.05.23 13:34, Richard L. Hamilton wrote:

AFAIK, Zoom is proprietary and only available for Windows, macOS, (some) Linux, 
and iOS and Android mobile devices. It uses a number of TCP and UDP ports, 
including TCP ports 80 and 443 (http/https) to get started, but others too.

So I think there is probably no open source or Solaris client. There are some 
incompatible open source alternatives, but they're not nearly as widely used, 
and probably don't have as rich a feature set.

And (AFAIK, i.e. Wikipedia or occasional alerts) Zoom has a history of security 
and privacy issues that one might want to be aware of if one is in any position 
to consider alternatives.

I think browser extensions do NOT implement Zoom, but simply provide a way that 
URLs with certain patterns can invoke the Zoom client on supported platforms, 
so that clicking on a link can initiate a session.


On May 5, 2023, at 04:51, Marc Lobelle  wrote:

Hello,

One of the few times I have to start a computer in Windows is to run ZOOM for 
video conferences. Is there a way to use ZOOM  on Openindiana ?

Thanks

Marc


___
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] Add inotify support to illumos-gate

[Till Wegmüller]

Hi Stephan

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


What does mate-system-monitor use inotify for?

-Till

On 02.05.23 12:10, Stephan Althaus wrote:

Hello!

As a search result from this morning, glib misses inotify/fam support,
which is a reason for mate-system-monitor to dump core.

FAM seems to be too old, but inotify-support is not in illumos-gate,
but Smartos has support for it.


Which is the "right" way to include inotify support in OI ?

a) Should we hopefully ask some smartos-developer to upstream this?

b) As a patch (-set) within oi-userland to illumos-gate ?

c) ??


A small search in the smart-os tree gives this:

$ find . -iname "*inotify*"
./illumos-joyent/usr/src/lib/libc/port/sys/inotify.c
./illumos-joyent/usr/src/test/zfs-tests/tests/functional/cli_root/zfs_mount/zfs_mount_watched_inotify.ksh
./illumos-joyent/usr/src/man/man3c/inotify_rm_watch.3c
./illumos-joyent/usr/src/man/man3c/inotify_init.3c
./illumos-joyent/usr/src/man/man3c/inotify_add_watch.3c
./illumos-joyent/usr/src/man/man7/inotify.7
./illumos-joyent/usr/src/uts/sparc/inotify
./illumos-joyent/usr/src/uts/intel/inotify
./illumos-joyent/usr/src/uts/common/io/inotify.c
./illumos-joyent/usr/src/uts/common/io/inotify.conf
./illumos-joyent/usr/src/uts/common/sys/inotify.h


Regards,

Stephan Althaus



___
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] Mail archives 404

[Till Wegmüller]

Hi All

This is actually a bug I am aware of. During the migration to the new 
Website I overlooked the mailman HTTP interface and haven't been able to 
fix it thus far. I have another chance to look into it tomorrow, until 
then please use mail-archive.com as posted by Guenther.


-Till

On 19.04.23 14:24, Guenther Alka wrote:

It seems the footer link is wrong,
https://www.mail-archive.com/openindiana-discuss@openindiana.org/


All the links to the list archives are gone:


___
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] Proper invocation for zfs sharenfs

[Till Wegmüller]

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



,anon=abuild  is not a valid sharenfs option.


Hi Udo

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


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


Greetings
Till

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

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

[Till Wegmüller]

Thank you Marcel that was it!

On 12.04.23 15:57, Marcel Telka wrote:

On Wed, Apr 12, 2023 at 03:19:04PM +0200, Till Wegmüller wrote:

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

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

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

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

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


Do you have the service/file-system/nfs package installed?



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

[OpenIndiana-discuss] Proper invocation for zfs sharenfs

[Till Wegmüller]

Hello everyone

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


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


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


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


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


Thanks
Till

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

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

[Till Wegmüller]

On 05.03.23 18:42, Richard L. Hamilton wrote:




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

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


Hi

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



As a historical interlude, speed was very much a key focus of creating IPS
to replace
SVR4 packaging. One of the key criticisms of the old packaging system was
that it
was considered inordinately slow (one manifestation of this was that the
development
workflow for Solaris involved installing updated bits, SVR4 was too slow
for impatient
engineers, hence bfu as a hack, but that rendered the system unsupportable,
but is
what led to onu).

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

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

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



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

But it is a HUGE improvement on SVR4 packages (and patches!), which were not 
only extremely slow, but one had to do some degree of sorting out manually, 
although I recall that someone (Casper?) had created a set of tools for 
deploying patches on a large scale; I recall using that to make Y2K updates 
doable at scale (back in the day of lots of Sun workstations; although servers 
tended to be done by hand when downtime was permissible).

The biggest improvement is that in a sense, speed doesn't matter if a new boot 
environment is being created, provided the system isn't hurting for 
performance. One can run the pkg update at a convenient hour, and do the reboot 
when it can be scheduled to be non-disruptive, with the assurance of a trivial 
and quick recovery plan if there's a problem (boot again to the previous BE). 
That satisfies everyone while minimizing lost sleep and/or overtime. :-)

My problem with all the new-fangled stuff is simply that I go back to 
mainframes and punched cards and Unix v7 on a PDP-11...and still have emulators 
for those and others (like Apollo workstations, or Multics, or even CP/M), in 
case I get nostalgic. With all that very slowly fading out of my head, getting 
something new in can be an uphill battle, esp. retired when I usually just do 
it if it's fun. :-)

For instance, although I never used them, I wish there was something in C or 
C++ like PL/I area variables, where one could create a multi-megabyte or 
nowadays multi-gigabyte variable WITHIN which other variables could be 
allocated and referenced via offsets rather than pointers, such that the entire 
area and its contents and internal allocation information and dynamic data 
structures could be written out to disk, and later read back in again (although 
the program reading it would of course have to have all the appropriate 
declarations). Think of that if one wanted to make predigesting a complex 
human-readable file into cacheable internal form relatively easy...or these 
days, saving state in something, perhaps a game or long-running modeling 
program, I suppose. And mainframes had checkpoint/restart support, which mostly 
one has to roll one's own in a limited (user space) way on Unix/Linux systems.


The File format thing sounds something like FlexBuffers 
https://github.com/google/flatbuffers/tree/master/rust/flexbuffers
But there are probably more formats supported by serde that fit the bill 
https://serde.rs/


Keywords in todays Jargon are Serialization and Zerocopy.

-Till




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


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

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

[Till Wegmüller]

That will actually give you a different install result. Although as we 
are generating a ton of userland-incorporations that may be one package 
or two that should have been updated anyway.


We will be starting to thin them out soon so this method will start 
generating divergences in results once we do.


But since it's community supported and rolling release it's probably 
more helpfull to not have it installed for some people. Depending on dev 
capabilities.


-Till

On 05.03.23 21:00, Marcel Telka wrote:

On Sun, Mar 05, 2023 at 05:12:55PM +, Peter Tribble wrote:

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


I found that with a slow machine and with a lot of packages installed it
is usually faster (and requires less RAM) to uninstall
userland-incorporation before the actual update, then do the update, and
finally install userland-incorporation back.


HTH.



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

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

[Till Wegmüller]

No not quite,

You can check my go port for formats and some incomplete server code 
https://github.com/Toasterson/pkg6-go


My C++ port attempt for sax parsing and history format implementation
https://github.com/Toasterson/pkg6

And my current rust port for Manifest reading code and an attempt to 
make things faster

https://github.com/OpenFlowLabs/ips

And the docs of the original for details from the Original developers 
fom 2011.

https://github.com/OpenIndiana/pkg5/tree/oi/doc

In there is a complete manual how everything works and Implementation 
details and notes from the devlopers about the algorithms and the 
original reasons why things are why they are. There is a t least 
conference 20 talks worth of reading in there.


-Till


On 05.03.23 17:47, Richard L. Hamilton wrote:

Thanks! That covers the useful part of my questions; for curiosity details I 
can always look at the source code. :-) Unfortunately for a more than casual 
overview, I'd have to learn Python. :-(


On Mar 5, 2023, at 11:19, Till Wegmüller  wrote:

Hi

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

If you want to speed up the time it is usually good to add more RAM and faster 
disks, as IPS consumes a lot of memory resolving dependencies. And doing 
Catalog operation. The Actual update is alsmost instant.

A lot of the phases during package actions are spent in internal bookkeeping 
things which are simply slow on OpenIndiana due to how IPS was initially 
designed with releases and not rolling release. This can be fixed in the future 
but I did not have time to do anything there. A update would require a couple 
months worth of work and currently nobody is paying for that. It's good enough 
for people as it is.

The stages you see are:
- Downloading and updating cached JSON catalogs of all packages available (this 
usually takes the longest)
- instrumenting beadm
- downloading manifest files
- Downloading and copying files (uncomress) into place as described by the 
manifests. (check the contents with `pkg contents -m`
- Creating a search index for pkg search actions (this also takes a long time)

Boot environments are created on updates that update more than one package. The 
package can inform IPS if a new boot environment is required. Installation 
uninstall etc. do not require a new boot environment.

Hope this helps
Till

On 05.03.23 16:41, Richard L. Hamilton wrote:

Given the output
- output begins --
root@openindiana:~# pkg update
 Packages to update: 375
Create boot environment: Yes
Create backup boot environment:  No
DOWNLOADPKGS FILESXFER (MB)   SPEED
Completed375/375 5209/5209  181.4/181.4  878k/s
PHASE  ITEMS
Removing old actions   1015/1015
Installing new actions 1017/1017
Updating modified actions  6585/6585
Updating package state database Done
Updating package cache   375/375
Updating image stateDone
Creating fast lookup database   Done
Updating package cache   2/2
A clone of openindiana-2023:03:03 exists and has been updated and activated.
On the next boot the Boot Environment openindiana-2023:03:05 will be
mounted on '/'.  Reboot when ready to switch to this updated BE.
Updating package cache   2/2
---
NOTE: Please review release notes posted at:
https://docs.openindiana.org/release-notes/latest-changes/
---
- output ends -
what do the various phases mean? And what drives the decision whether to create 
a new boot environment, or a backup boot environment (or maybe neither)?
Knowing those might be helpful if anything went badly wrong (although the simplest remedy 
would be to fall back to a previous boot environment!) or if one intended to create a 
package, and would certainly be more satisfying waiting for the slower phases to 
complete, being able to say to oneself what it was doing then.  Oh, and why does 
"Updating package cache" appear twice?
Updates on Solaris 11 and derivatives (OpenIndiana, etc) are certainly very 
robust (if packages and repositories are correct!) and provide generous means 
of recovery. But they do seem to be quite slow compared to e.g. either Red Hat 
based or Debian based Linux methods (yum or apt, or the underlying local-only 
facilities). That's not counting download time either (since repository servers 
are not all equal).
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindia

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

[Till Wegmüller]

Hi

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


If you want to speed up the time it is usually good to add more RAM and 
faster disks, as IPS consumes a lot of memory resolving dependencies. 
And doing Catalog operation. The Actual update is alsmost instant.


A lot of the phases during package actions are spent in internal 
bookkeeping things which are simply slow on OpenIndiana due to how IPS 
was initially designed with releases and not rolling release. This can 
be fixed in the future but I did not have time to do anything there. A 
update would require a couple months worth of work and currently nobody 
is paying for that. It's good enough for people as it is.


The stages you see are:
- Downloading and updating cached JSON catalogs of all packages 
available (this usually takes the longest)

- instrumenting beadm
- downloading manifest files
- Downloading and copying files (uncomress) into place as described by 
the manifests. (check the contents with `pkg contents -m`
- Creating a search index for pkg search actions (this also takes a long 
time)


Boot environments are created on updates that update more than one 
package. The package can inform IPS if a new boot environment is 
required. Installation uninstall etc. do not require a new boot environment.


Hope this helps
Till

On 05.03.23 16:41, Richard L. Hamilton wrote:

Given the output
- output begins --
root@openindiana:~# pkg update
 Packages to update: 375
Create boot environment: Yes
Create backup boot environment:  No

DOWNLOADPKGS FILESXFER (MB)   SPEED
Completed375/375 5209/5209  181.4/181.4  878k/s

PHASE  ITEMS
Removing old actions   1015/1015
Installing new actions 1017/1017
Updating modified actions  6585/6585
Updating package state database Done
Updating package cache   375/375
Updating image stateDone
Creating fast lookup database   Done
Updating package cache   2/2

A clone of openindiana-2023:03:03 exists and has been updated and activated.
On the next boot the Boot Environment openindiana-2023:03:05 will be
mounted on '/'.  Reboot when ready to switch to this updated BE.

Updating package cache   2/2

---
NOTE: Please review release notes posted at:

https://docs.openindiana.org/release-notes/latest-changes/
---

- output ends -

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

Knowing those might be helpful if anything went badly wrong (although the simplest remedy 
would be to fall back to a previous boot environment!) or if one intended to create a 
package, and would certainly be more satisfying waiting for the slower phases to 
complete, being able to say to oneself what it was doing then.  Oh, and why does 
"Updating package cache" appear twice?

Updates on Solaris 11 and derivatives (OpenIndiana, etc) are certainly very 
robust (if packages and repositories are correct!) and provide generous means 
of recovery. But they do seem to be quite slow compared to e.g. either Red Hat 
based or Debian based Linux methods (yum or apt, or the underlying local-only 
facilities). That's not counting download time either (since repository servers 
are not all equal).



___
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] netbooting openindiana

[Till Wegmüller]

To add

The Magic incantation to build the the ISO is:

```
distro_const build /usr/share/distro_const/text_install/text_mode_x86.xml

```

The package to install is: 
`pkg:/install/distribution-constructor@0.5.11-2022.0.0.1065`


-Till


On 04.03.23 22:45, Marcel Telka wrote:

On Sat, Mar 04, 2023 at 10:24:12PM +0100, Till Wegmüller wrote:

Due to limitations on how the install media are created at the this is not
possible. You would have to develop a media that can do that. Some work has
been done to allow supplying the media via NFS after booting the kernel but
it is undocumented and very beta.

Contributions welcome. I can also help getting you started on that
development effort.


The good news is that with this merged:
https://github.com/OpenIndiana/slim_source/pull/72 the install image
supports network booting OOTB.  The only problem is that the latest
available install image at https://www.openindiana.org/download/ was
created before the above PR got merged.

To make the netboot working you just need to mount the ISO image on your NFS
server, share the mounted ISO via NFSv3 and configure your PXE server
properly (see `man pxeboot`).

Without the above PR merged you would additionally need to manually
mount the install media once OpenIndiana boots over PXE using the
following command:

mount -o vers=3 NFSSERVER:ROOTPATH /.cdrom


HTH.



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

Re: [OpenIndiana-discuss] netbooting openindiana

[Till Wegmüller]

Hi Rolf

Due to limitations on how the install media are created at the this is 
not possible. You would have to develop a media that can do that. Some 
work has been done to allow supplying the media via NFS after booting 
the kernel but it is undocumented and very beta.


Contributions welcome. I can also help getting you started on that 
development effort.


Greetings
Till

On 04.03.23 21:37, Rolf M. Dietze wrote:

Hi,
is there any hint on how to netboot the openindiana install media?
Nothing found about netbooting on http://docs.openindiana.org/handbook
There is however some docu on omnios, tribblix and so, as well as
Oracle Solaris AI, but I haven't found anything on netbooting OI.
Is ist just booting off the kernel and supplying the rest via nfs
as it works with smartos?

If there is a doc I missed, then please give me a hint.

regs, Rolf



___
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] update failed ??

[Till Wegmüller]

Hi Marc

Looks like the graphics card packages messed up there. It's 
unfortunately something we have to let people shoose, as nvidia keeps 
dropping old graphics cards. You will need to go back to the old BE and 
mount the failed one via beadm mount and use pkg's -R switch to modify 
the BE so that it has the correct nvidia package installed into it.


basically
- use beadm to mount be with updated system
- use pkg -R /path/to/be/mount
- use install uninstall as normal and install the correct nvidia 
package.

-beadm unmount

Activeate and boot new be rinse and repeat until you found the right 
combination.


If that does not solve it we will need to analyse the case more.

Greetings
Till

On 27.02.23 17:06, Marc Lobelle wrote:

Hello,

A few days ago, I tried to update openindiana on a HP notebook elitebook 
2560P (with intel core i7), as I do regularly on my systems (I always 
first try updates on an older computer I might afford to loose...: well, 
this time I lost it!). I did:


#pkg refresh --full

#pkg update -v

When rebooting, I got the following information:

cpu0 microcode has been upfdated from version 0x18 to version 0x2f

Openindiana Hipster 2022.10 version 58b0c75051

VMX support disabled  by BIOS

Then came error messages:

1. on Feb 22  23:30:54: module nvidia not found (I do not think there
    is nvidia hardware in this notebook: as far as I remember it is all
    Intel, thus I assume there is nothing wrong with this)
2. on Feb 22 23:32:56: network/ipfilter times out and transitioned to
    maintenance: this should not block the system: this service is not
    activated by default
3. on Feb 23 00:00:54: milestone/multi-user timed out and transitioned
    to maintenance.

The notebook did not print anything after that: it looks blocked

Of course I assume I could reboot an old BE, but will doing that and 
retrying the update provide a working and up to date system ? Was there 
a problem with this version of OI ? If yes, is it solved ?


Thanks

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


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

Re: [OpenIndiana-discuss] What would the steps be needed to host a website on OpenIndiana?

[Till Wegmüller]

Hi

The most popular webserver we have packaged (bundled) is nginx. It is 
usually better to use the DNS that your domain registrar offers you. 
Most do. Since those have some basic sense of reliability.


For Let's encrypt SSL one can use dehydrated or lego as a client.

The Golang toolchain is bundled if one wants to get lego going.

Greetings
Till


On 23.02.23 00:11, Mike Carroll wrote:

Sweet. I'll go digging around for the BIND documentation on the site.

From: Carl Brewer 
Sent: Wednesday, February 22, 2023 5:05 PM
To: openindiana-discuss@openindiana.org 
Subject: Re: [OpenIndiana-discuss] What would the steps be needed to host a 
website on OpenIndiana?

On 23/02/2023 9:58 am, Mike Carroll wrote:

That is a very true statement that it ranges from simple to complex. I am just 
really looking for a static site setup to host a personal site with a domain 
that I purchased. Just HTML and CSS, and not much more than that-so security is 
essential but with little attack surface.


BIND is bundled up, as is apache, so you don't need a database or PHP if
it's just static HTML.



___
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] OI on HP Gen 10 Microserver

[Till Wegmüller]

Are there no M.2 Slots or PCI slots on the Gen10+?

If you want an SSD a PCIe M.2 SSD Card is your best and most performant 
option. You can also use it as L2ARC for the spinning rust if you take 
two Adapters and with 2 SSD's each for example. One thing of note 
though. Be absolutely certain your RAID controller is in HBA mode and at 
best buy a dedicated HBA instead to avoid drive weirdness and slowness. 
ZFS does not like RAID controllers at all.


-Till

On 16.02.23 23:44, Michelle wrote:

Hi Rolf,

Thanks for this.

What I find interesting is that looking at the data sheet, etc. there
is no clear indication that two are 6G and 2 are 3G. They aren't
exactly up front about it.

That's what's worrying me about the 10+, I can't find anything that
spells it out what the ports are capable of.

However, it does appear that the 10 is a Marvell controller and doesn't
advertise raid 5, whereas the 10+ is a Smart Array S100i controller and
supports raid 5, so I would have believed that they will all be 6G. If
they advertised RAID 5 and one of the drives was operating at half the
speed, then they'd likely be in for a bit of a backlash I would have
thought.

The only way to find out for sure... if someone doesn't already know...
is to wait until I've got it, put some drives in and see what the BIOS
says that the drives are connected at.

At the moment, given the bug that Carsten mentioned with booting rpool
from USB, I'm thinking of using one bay for SSD (with an SFF LFF
adaptor caddy) and the other three for the spinning rust. Backup drives
will just have to be attached by USB 3 caddy, I guess.

Michelle.

On Thu, 2023-02-16 at 22:21 +0100, Rolf M. Dietze wrote:

Hi Michelle,

don't know about the G10+ boxes. I meant:
https://buy.hpe.com/uk/en/servers/proliant-microserver/proliant-microserver/proliant-microserver/hpe-proliant-microserver-gen10/p/1009955118
and with that issue of 2 ports 6G and 2 ports 3G I rather looked into
boxes from other manufacturers than HP to recomend them to customers.

With the older Gen10 boxes one needs .NET for a console via the build
in system controler, even if you purchase the advanced license. Since
there is no windows in the net at all, I set them up on a KVM server
and never bought any boxes fom HP because of this rather flimsy
design
(no console via systemcontroller, 6G/3G sata ports)

But if I have to choose between OI and FreeBSD and what experiences
running OI as a server OS on those boxes, I go for OI and that was
the original discussion

regs, Rolf


Quoting Michelle :


The target server is actually going to be the Gen 10 Plus...
https://uk-new.ingrammicro.com/site/productdetail?id=2M2SBG9

The specs are light on the exact specs of the speed, but the manual
doesn't help either...
https://www.serversdirect.co.uk/PDFs/P16006-421_1_7006250_Original.pdf?v=27

The best they say is... "The embedded HPE Smart Array S100i SR
Gen10
Controller supports SATA drive installation. This controller
supports
RAID levels 0, 1, 5, and 10" ... and it would be a bit odd for them
to
support RAID levels like that and have two ports down to 3Gbs.

Grateful for any insight.

Michelle.


On Thu, 2023-02-16 at 19:55 +0100, rmd wrote:

Hi

it depends a bit on the BIOS version of the Gen 10. With the
early
version
it works best, pulling all disks out of the bays, do the install,
reboot, halt
again, put the drives back in, repower and boot, then do the disk
configs.

With my Gen 10, I put a 4i4o SAS-controler in it, plug the sas-
plug
of the
internal drive bays on the i-cnector of that additional 4i4o sas
card
and
connect SSDs with a fan out cable to the on board sas connector.
With
a bit of soldering an additional power connector for the SSDs is
simply
set up an the OS goes on those SSDs. Hence, the Gen10 supports
only
2 diskbays with 6G througput and the other two bays only support
3G.

regs, Rolf


On Feb 16, 2023, at 9:34 AM, Michelle 
wrote:

One of my older servers has died and I'm looking to replace
with a
Gen
10 microserver.

On my N54L, there are four bays, but a top CD bay where the
operating
system drive sits with OI on it, leaving me with four bays for
spinning
rust.

However, on the Gen 10 I've looked at the motherboard and I
can't
see
anything other than a USB connector and the SATA harness
connector.
I
can't see a DVD/CD drive either.

Has anyone managed to get OI on another drive, or am I going to
have to
take up a bay for the OS drive please?

Thanks for any hints and advice,

Michelle.


___
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

Re: [OpenIndiana-discuss] OI on HP Gen 10 Microserver

[Till Wegmüller]

Hi Michelle

I have my own G10 Running combined root and data pool as raidz1. OI 
supports pool creation via the Installer and the live System built in 
shell. Since the root dataset only takes up a bit of space it works well 
for a shared scenario.


Greetings
Till

On 16.02.23 09:34, Michelle wrote:

One of my older servers has died and I'm looking to replace with a Gen
10 microserver.

On my N54L, there are four bays, but a top CD bay where the operating
system drive sits with OI on it, leaving me with four bays for spinning
rust.

However, on the Gen 10 I've looked at the motherboard and I can't see
anything other than a USB connector and the SATA harness connector. I
can't see a DVD/CD drive either.

Has anyone managed to get OI on another drive, or am I going to have to
take up a bay for the OS drive please?

Thanks for any hints and advice,

Michelle.


___
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] /export/home on second disk

[Till Wegmüller]

Hi Apostolos

That should just work by creating a seperate zpool on the other disk and 
setting that pools mountpoint to either /export/home or creating a 
Dataset whos mountpoint is /export/home. If you want to migrate a user 
you'll need to do a send -> receive -> rename for the users dataset you 
want to copy over before changing the mountpoint. So something like make 
new pool while using the alternate root mount switch -> send over all 
datasets from /export/home including peroperties (-p) -> set old 
datasets to canmount=noauto -> reboot to activate new config.


Hope this helps
-Till


On 08.02.23 10:31, Apostolos Syropoulos via openindiana-discuss wrote:

Hello,
I have a computer that has two harddisks: an ssd and an "ordinary" 
disk.Naturally, I want to install the systemon the SSD disk but at the same time I want 
to have the users directories onthe second disk. Can anyone suggesta strategy to realize 
this requirement?
Regards,
Apostolos
Στάλθηκε από το Ταχυδρομείο Yahoo σε 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] warning - libtiif will be updated and will damage many packages until they have been rebuild - update process finished

[Till Wegmüller]

Yes, it is that issue :)

-Till

On 30.01.23 22:27, Alan Coopersmith wrote:

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

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

After that it was needed to rebuild qt5 again to get working binaries.


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

 -alan-

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


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

Re: [OpenIndiana-discuss] pkg install conflicts

[Till Wegmüller]

Hi Richard

You can uninstall system/library/gcc-4-runtime it has been superseeded 
partially by system/library/gcc-10-compat-links which bumps the default 
gcc runtime links in /usr/lib to gcc-10 it may be that you need to 
switch back to gcc-4.9 runtimes if some software doesn't work as we need 
to recompile many packages. It's a good stopping point so that people 
know that they need to test after this upgrade.


Greetings
Till

On 20.01.23 10:24, Richard L. Hamilton wrote:

This VM is updated almost daily, so it’s not as if it was so out-of-date that 
problems might be expected; so I imagine something is not consistent in the 
packages in the repository.

root@openindiana:~# pkg update
Creating Plan (Checking for conflicting actions): |
pkg update: The requested change to the system attempts to install multiple 
actions
for link 'usr/lib/amd64/libgcc_s.so' with conflicting attributes:

 1 package delivers 'link path=usr/lib/amd64/libgcc_s.so 
target=../../gcc/10/lib/amd64/libgcc_s.so':
 
pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z
 1 package delivers 'link path=usr/lib/amd64/libgcc_s.so 
target=libgcc_s.so.1':
 
pkg://openindiana.org/system/library/gcc-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171440Z


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

The following packages deliver conflicting action types to 
usr/lib/amd64/libgcc_s.so.1:

   link:
 
pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z
   file:
 
pkg://openindiana.org/system/library/gcc-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171440Z

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

The requested change to the system attempts to install multiple actions
for link 'usr/lib/amd64/libgomp.so' with conflicting attributes:

 1 package delivers 'link path=usr/lib/amd64/libgomp.so 
target=../../gcc/10/lib/amd64/libgomp.so':
 
pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z
 1 package delivers 'link path=usr/lib/amd64/libgomp.so 
target=libgomp.so.1':
 
pkg://openindiana.org/system/library/gcc-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171440Z


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

The following packages deliver conflicting action types to 
usr/lib/amd64/libgomp.so.1:

   link:
 
pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z
   file:
 
pkg://openindiana.org/system/library/gcc-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171440Z

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

The requested change to the system attempts to install multiple actions
for link 'usr/lib/amd64/libssp.so.0' with conflicting attributes:

 1 package delivers 'link path=usr/lib/amd64/libssp.so.0 
target=../../gcc/10/lib/amd64/libssp.so.0':
 
pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z
 1 package delivers 'link path=usr/lib/amd64/libssp.so.0 
target=libssp.so.0.0.0':
 
pkg://openindiana.org/system/library/g++-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171432Z


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

The requested change to the system attempts to install multiple actions
for link 'usr/lib/libssp.so' with conflicting attributes:

 1 package delivers 'link path=usr/lib/libssp.so 
target=../gcc/10/lib/libssp.so':
 
pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z
 1 package delivers 'link path=usr/lib/libssp.so target=libssp.so.0.0.0':
 
pkg://openindiana.org/system/library/g++-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171432Z


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

The requested change to the system attempts to install multiple actions
for link 'usr/lib/amd64/libstdc++.so' with conflicting attributes:

 1 package delivers 'link path=usr/lib/amd64/libstdc++.so 
target=../../gcc/10/lib/amd64/libstdc++.so':
 
pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z
 1 package delivers 'link path=usr/lib/amd64/libstdc++.so 
target=libstdc++.so.6.0.20':
 
pkg://openindiana.org/system/library/g++-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171432Z


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

The requested change to the system attempts to install multiple actions
for link 'usr/lib/libssp.so.0' with conflicting attributes:

 1 package 

Re: [OpenIndiana-discuss] Virtualbox 7.0.4?

[Till Wegmüller]

Hi Carl

If you can at least check the compile process in [0] or even update the 
makefile then we can easily make the PR to update it.


I can also lead you through the process on IRC, Matrix or Discord or 
here on mail.


Greeting
Till

[0] 
https://github.com/OpenIndiana/oi-userland/tree/ced366e8e9a0a065ec50a3b5e08ae4415df9b9b8/components/sysutils/virtualbox


On 15.01.23 03:00, Carl Brewer wrote:

Hey,
Virtualbox 7 was released not long ago, now at 7.0.4, in oi-userland 
it's 6.1.40.  Anything I can do to help get it going?



___
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] fail2ban

[Till Wegmüller]

Hi Marc

I don't think we ever had a fail2ban IPS package in OI.
But for python we have pip the python native package manager. Try `pip 
install fail2ban==0.9.4` as root in order to see if that works or `pip 
install fail2ban` That should get yout the python package installed 
again. Depending how you created /usr/local/bin/fail2ban-client that 
might also need adjustment to the newest package version so it grabs the 
right python files.


Hope this helps
Greetings
Till

On 03.01.23 13:26, Marc Lobelle wrote:

Hello all,

I had installed fail2ban about 10 years ago, following instructions by 
jarret@megatron related to omnios and it worked nicely since that time.


Unfortunately, svcs told me that it is now in maintenance mode.

Is there an openindiana package for this program ? I'm running 
openindiana 2022.10 and just updated all packages.


Thanks for your help,

Marc

  /var/svc/log/network-fail2ban:default.log ends with:

Stopping fail2ban-server with /etc/fail2ban/fail2ban.conf
[ janv.  3 12:20:08 Method "stop" exited with status 0. ]
[ janv.  3 12:20:08 Restarting too quickly, changing state to 
maintenance. ]

Traceback (most recent call last):
   File "/usr/local/bin/fail2ban-client", line 4, in 
     __import__('pkg_resources').run_script('fail2ban==0.9.4', 
'fail2ban-client')
   File "/usr/lib/python3.9/vendor-packages/pkg_resources/__init__.py", 
line 3260, in 

     def _initialize_master_working_set():
   File "/usr/lib/python3.9/vendor-packages/pkg_resources/__init__.py", 
line 3234, in _call_aside

     f(*args, **kwargs)
   File "/usr/lib/python3.9/vendor-packages/pkg_resources/__init__.py", 
line 3272, in _initialize_master_working_set

     working_set = WorkingSet._build_master()
   File "/usr/lib/python3.9/vendor-packages/pkg_resources/__init__.py", 
line 581, in _build_master

     ws.require(__requires__)
   File "/usr/lib/python3.9/vendor-packages/pkg_resources/__init__.py", 
line 909, in require

     needed = self.resolve(parse_requirements(requirements))
   File "/usr/lib/python3.9/vendor-packages/pkg_resources/__init__.py", 
line 795, in resolve

     raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: *The 'fail2ban==0.9.4' distribution 
was not found and is required by the application*

___
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] Automatic install

[Till Wegmüller]

On 03.01.23 11:46, Marcel Telka wrote:

Hi,

I would like to install OpenIndiana on few machines.  To get the same
(and easily reproducible) results I'd like to utilize some kind of
automatic installation.

Since AI (auto_install) was removed from OpenIndiana about 5 years back
there seems to be no way to do the automatic OpenIndiana installation
now.

Any suggestion?


Thanks.



Hi Marcel

If you would like to beta test you could try my illumos-installer work [0]

You will need rustup, cargo and cargo-make installed. cargo-make can be 
installed via `cargo install cargo-make` then run `makers package_ips` 
to build and IPS package under the cargo target directory. You will need 
an image to `dd` to the disk. One can use the illumos image builder to 
generate one from IPS packages.


It will require some scripting I could only get the config process 
reasonably automated thus far. Installing an image or from packages with 
pkg -r will require a ramdisk ISO and a shellscript. Although it is 
probably the easiest to modify the existing ISO in distro const and then 
having a service method do the lifting of grabbing the install shell 
script and executing it.



[0] https://github.com/Toasterson/illumos-installer
[1] https://github.com/jclulow/omnios-image-builder

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

Re: [OpenIndiana-discuss] Zone install failure

[Till Wegmüller]

Nope that wont work. LC_ALL=C is hardcoded into the zone install scripts 
and wrong. It needs to be `LC_ALL=C.UTF-8` this is a requirement within 
python3


-Till
On 08.11.21 16:23, Christian Meier wrote:

Hi Predrag
or you can try the following:
export LC_ALL=C
and try to install the zone again

Best Regards
Christian

On 08/11/2021 15:59, Till Wegmüller wrote:

Hi Predrag

Yes you must Update the GZ not the Zone. The GZ needs the patch 
installed.


-Till
On 08.11.21 15:57, Predrag Zečević wrote:

Hi Till,

so, it is brand new zone, and first installation has failed!

So, how to update to that version?

Shall I update GZ first (which is not case, I am struggling with 
Nvidia driver and waiting with update)?


Regards.

On 11/8/21 3:51 PM, Till Wegmüller wrote:

Hi Predrag

You will need to uninstall the zone and update to a version that has 
https://github.com/OpenIndiana/pkg5/pull/93 installed. This landed 4 
days ago.


-Till

On 08.11.21 15:43, Predrag Zečević wrote:

I have created zone (IP addreses mangled):

:; zonecfg -z solarium export
create -b
set zonepath=/export/Zones/solarium
set brand=nlipkg
set autoboot=false
set ip-type=shared
add net
set address="xxx.xxx.xxx.154/24"
set physical="e1000g0"
set defrouter="xxx.xxx.xxx.254"
end
add device
set match="/dev/vboxdrv"
end
add device
set match="/dev/ip"
end
Then tried to install:
---8<--
:; pfexec zoneadm -z solarium install
    Image: Preparing at /export/Zones/solarium/root.

    Publisher: Using openindiana.org 
(https://pkg.openindiana.org/hipster/).
    Publisher: Using hipster-encumbered 
(https://pkg.openindiana.org/hipster-encumbered/).

    Cache: Using /var/pkg/publisher.
   Installing: Packages (output follows)
Packages to install: 175
Mediators to change:   7
  Services to change:   6

DOWNLOAD    PKGS FILES    XFER (MB) SPEED
Completed    175/175   34602/34602 
327.2/327.2 5.4M/s


PHASE ITEMS
Installing new actions   25402/49855Action install 
failed for 
'etc/certs/CA/NetLock_Arany_(Class_Gold)_F\u0151tan\xfas\xedtv\xe1ny.pem' 
(pkg://openindiana.org/crypto/ca-certificates):
   UnicodeEncodeError: 'ascii' codec can't encode character 
'\u0151' in position 69: ordinal not in range(128)
pkg: An unexpected error happened during install: 'ascii' codec 
can't encode character '\u0151' in position 69: ordinal not in 
range(128)

ERROR: failed to install package

---8<--

and now:

:; zoneadm list -cv

   ID NAME STATUS PATH BRAND    IP
    0 global   running    / ipkg shared
    - solarium incomplete /export/Zones/solarium nlipkg shared


How to proceed (finish zone installation)?

Thanks and regards.

--
Predrag Zečević
Operations and Support Analyst
Technical Support Analyst
2e Systems GmbH

tel: +49 - 6196 - 95058 - 15
mob: +49 - 174 - 3109288
fax: +49 - 6196 - 95058 - 94
e-mail: predrag.zece...@2e-systems.com

headquarter: 2e Systems GmbH, Koenigsteiner Str. 107, 65812 Bad 
Soden am Taunus, Germany

registration: Amtsgericht Koenigstein (Germany), HRB 7303
managing director: Phil Douglas

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



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


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




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


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


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

Re: [OpenIndiana-discuss] Zone install failure

[Till Wegmüller]

Hi Predrag

Yes you must Update the GZ not the Zone. The GZ needs the patch installed.

-Till
On 08.11.21 15:57, Predrag Zečević wrote:

Hi Till,

so, it is brand new zone, and first installation has failed!

So, how to update to that version?

Shall I update GZ first (which is not case, I am struggling with Nvidia 
driver and waiting with update)?


Regards.

On 11/8/21 3:51 PM, Till Wegmüller wrote:

Hi Predrag

You will need to uninstall the zone and update to a version that has 
https://github.com/OpenIndiana/pkg5/pull/93 installed. This landed 4 
days ago.


-Till

On 08.11.21 15:43, Predrag Zečević wrote:

I have created zone (IP addreses mangled):

:; zonecfg -z solarium export
create -b
set zonepath=/export/Zones/solarium
set brand=nlipkg
set autoboot=false
set ip-type=shared
add net
set address="xxx.xxx.xxx.154/24"
set physical="e1000g0"
set defrouter="xxx.xxx.xxx.254"
end
add device
set match="/dev/vboxdrv"
end
add device
set match="/dev/ip"
end
Then tried to install:
---8<--
:; pfexec zoneadm -z solarium install
    Image: Preparing at /export/Zones/solarium/root.

    Publisher: Using openindiana.org 
(https://pkg.openindiana.org/hipster/).
    Publisher: Using hipster-encumbered 
(https://pkg.openindiana.org/hipster-encumbered/).

    Cache: Using /var/pkg/publisher.
   Installing: Packages (output follows)
Packages to install: 175
Mediators to change:   7
  Services to change:   6

DOWNLOAD    PKGS FILES    XFER 
(MB)   SPEED
Completed    175/175   34602/34602 
327.2/327.2 5.4M/s


PHASE ITEMS
Installing new actions   25402/49855Action install 
failed for 
'etc/certs/CA/NetLock_Arany_(Class_Gold)_F\u0151tan\xfas\xedtv\xe1ny.pem' 
(pkg://openindiana.org/crypto/ca-certificates):
   UnicodeEncodeError: 'ascii' codec can't encode character '\u0151' 
in position 69: ordinal not in range(128)
pkg: An unexpected error happened during install: 'ascii' codec can't 
encode character '\u0151' in position 69: ordinal not in range(128)

ERROR: failed to install package

---8<--

and now:

:; zoneadm list -cv

   ID NAME STATUS PATH   BRAND    IP
    0 global   running    / ipkg shared
    - solarium incomplete /export/Zones/solarium nlipkg   shared


How to proceed (finish zone installation)?

Thanks and regards.

--
Predrag Zečević
Operations and Support Analyst
Technical Support Analyst
2e Systems GmbH

tel: +49 - 6196 - 95058 - 15
mob: +49 - 174 - 3109288
fax: +49 - 6196 - 95058 - 94
e-mail: predrag.zece...@2e-systems.com

headquarter: 2e Systems GmbH, Koenigsteiner Str. 107, 65812 Bad Soden 
am Taunus, Germany

registration: Amtsgericht Koenigstein (Germany), HRB 7303
managing director: Phil Douglas

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



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


___
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] Zone install failure

[Till Wegmüller]

Hi Predrag

You will need to uninstall the zone and update to a version that has 
https://github.com/OpenIndiana/pkg5/pull/93 installed. This landed 4 
days ago.


-Till

On 08.11.21 15:43, Predrag Zečević wrote:

I have created zone (IP addreses mangled):

:; zonecfg -z solarium export
create -b
set zonepath=/export/Zones/solarium
set brand=nlipkg
set autoboot=false
set ip-type=shared
add net
set address="xxx.xxx.xxx.154/24"
set physical="e1000g0"
set defrouter="xxx.xxx.xxx.254"
end
add device
set match="/dev/vboxdrv"
end
add device
set match="/dev/ip"
end
Then tried to install:
---8<--
:; pfexec zoneadm -z solarium install
    Image: Preparing at /export/Zones/solarium/root.

    Publisher: Using openindiana.org 
(https://pkg.openindiana.org/hipster/).
    Publisher: Using hipster-encumbered 
(https://pkg.openindiana.org/hipster-encumbered/).

    Cache: Using /var/pkg/publisher.
   Installing: Packages (output follows)
Packages to install: 175
Mediators to change:   7
  Services to change:   6

DOWNLOAD    PKGS FILES    XFER 
(MB)   SPEED
Completed    175/175   34602/34602 327.2/327.2 
5.4M/s


PHASE ITEMS
Installing new actions   25402/49855Action install 
failed for 
'etc/certs/CA/NetLock_Arany_(Class_Gold)_F\u0151tan\xfas\xedtv\xe1ny.pem' (pkg://openindiana.org/crypto/ca-certificates): 

   UnicodeEncodeError: 'ascii' codec can't encode character '\u0151' in 
position 69: ordinal not in range(128)
pkg: An unexpected error happened during install: 'ascii' codec can't 
encode character '\u0151' in position 69: ordinal not in range(128)

ERROR: failed to install package

---8<--

and now:

:; zoneadm list -cv

   ID NAME STATUS PATH   BRAND    IP
    0 global   running    / ipkg shared
    - solarium incomplete /export/Zones/solarium nlipkg   shared


How to proceed (finish zone installation)?

Thanks and regards.

--
Predrag Zečević
Operations and Support Analyst
Technical Support Analyst
2e Systems GmbH

tel: +49 - 6196 - 95058 - 15
mob: +49 - 174 - 3109288
fax: +49 - 6196 - 95058 - 94
e-mail: predrag.zece...@2e-systems.com

headquarter: 2e Systems GmbH, Koenigsteiner Str. 107, 65812 Bad Soden am 
Taunus, Germany

registration: Amtsgericht Koenigstein (Germany), HRB 7303
managing director: Phil Douglas

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



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


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

Re: [OpenIndiana-discuss] Installation in KVM for OSS porting

[Till Wegmüller]

Ah yes exactly that.

I think that is classifiable as typo :)

I didn't remember it was that long ago. SO yeah thats fixed in 2020.04.


-Till
On 19.10.20 18:29, Joshua M. Clulow via openindiana-discuss wrote:
> I don't believe it is the Print Screen key, but rather the Scroll Lock
> key.  I had this issue myself with the SPICE console used by default
> in many libvirt/KVM systems, and it was fixed in illumos as:
> 
> 11501 Scroll Lock translation to control sequence is patently unhelpful
> 
> https://www.illumos.org/issues/11501

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

Re: [OpenIndiana-discuss] Installation in KVM for OSS porting

[Till Wegmüller]

Hi

This escape sequence is the "Print Screen" Button. Spice clients use
that keypress as keep-alive signal. The "Print screen" Button is unknown
to illumos, solaris as Sun keyboards did not use to have that key. We
noticed some months ago and added support for that key so this should
not happen anymore. I though this was already in 2020.04 but maybe not.

If you have vagrant installed you can use the Official Vagrant box as an
installation. It has a libvirt image available. [0]
These are updated monthly. I heartly recommend vagrant for managing VM's
for OS porting.

As for your installation. If the escape sequence has made it into the
language selection you can try to edit it in /etc/default/init

Also we have a feature called boot_environments which allow you to
always go back to a state before the update in the boot loader. Try to
boot the old environment after installation if the new one does not work.

Hope this helps
Till

[0] https://app.vagrantup.com/openindiana/boxes/hipster
On 19.10.20 13:53, Nelson H. F. Beebe wrote:
> Gerhard reports on Mon, 19 Oct 2020 13:39:35 +0200:
> 
>>> I installed OI-Hipster 2020.04 from DVD image in a KVM on Ubuntu-18.04.
>>> this was tricky because something poisoned the text fields with escape
>>> sequence ^[[210z every two seconds or so - challenging in the password
>>> fields...
> 
> I too have seen that on several Solaris-family systems installed on
> VMs, and I later found a workaround that I recorded about four years
> ago in my system notes:
> 
>>> ...
>>> One thing that plagued me during the initial console installation was
>>> the bogus, and rapid, generation of unwanted ESC-[210z input
>>> characters interspersed with normal keyboard input.  That made it
>>> EXTREMELY difficult to type commands in the console window, or even to
>>> login.  
>>>
>>> We later found identical problems with other OpenSolaris-based systems
>>> (Dyson, Illumian, Tribblix, and XStreamOS), and we found a workaround
>>> that changes the virtual display device: select the QEMU virt-manager
>>> Display Spice button in the white left panel, and change the Type
>>> field from "Spice server" to "VNC server".  Then reboot: the unwanted
>>> input no longer appears.
>>> ...
> 
> ---
> - Nelson H. F. BeebeTel: +1 801 581 5254  
> -
> - University of UtahFAX: +1 801 581 4148  
> -
> - Department of Mathematics, 110 LCBInternet e-mail: be...@math.utah.edu  
> -
> - 155 S 1400 E RM 233   be...@acm.org  be...@computer.org 
> -
> - Salt Lake City, UT 84112-0090, USAURL: http://www.math.utah.edu/~beebe/ 
> -
> ---
> 
> ___
> 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] Next/Own-cloud client?

[Till Wegmüller]

Hey Tony

I haven't tried with MATE but GNOME2 used to be able to navigate to
Webdav shares as if they where mounted filesystem. Just paste the Webdav
URL into the folder navigation textbox.

You can get the Webdav URL from the Webinterface in the settings part
below the Trashbin.

It s usually something like https://$SERVER/remote.php/dav/files/$USER/

Greetings
Till
On 07.10.20 14:54, Tony Brian Albers wrote:
> Hi guys,
> 
> I'm trying to figure out how to use my Nextcloud server from OI.
> 
> I haven't been able to find a client for OI/Illumos, and the original 
> Nextcloud client has a lot of QT dependencies that I don't know if OI 
> can satisfy, so I haven't tried to build it.
> 
> I've tried using JFileSync3 (https://github.com/mgoellnitz/JFileSync3) 
> but it's not ideal.
> 
> Another project, savegamesync (https://github.com/pseiler/savegamesync) 
> looks like it can be modified to act as a sync-client for more than just 
> savegame files.
> 
> But does anyone have a native Nextcloud/Owncloud client working?
> 
> TIA,
> 
> /tony
> 
> ___
> 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] OpenIndiana LibreOffice Instalation

[Till Wegmüller]

Hi

This step should have been

pkg uninstall libreoffice4


Greetings
Till

On 05.10.20 12:04, Apostolos Syropoulos via openindiana-discuss wrote:
> pkg uninstall libreoffice52

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

Re: [OpenIndiana-discuss] Nvidia card installed.. now lightdm fails

[Till Wegmüller]

Hi

Could be that you need libEGL.so.1 from mesa then


x.org can run without opengl but lightdm can't

Greetings
Till
On 25.08.20 10:08, Tony Brian Albers wrote:
> Ok, so I investigated further.
> 
> It seems that the NVIDIA-Solaris-x86-304.137 package bundle does not
> include libEGL.so.1, but versions 390.138 and 340.108 do.
> 
> But since X is actually working, is this an issue with lightdm?
> 
> /tony
> 
> 
> On Tue, 2020-08-25 at 06:36 +, Tony Brian Albers wrote:
>> Good morning,
>>
>> So I managed to find an old nvidia card, and I got the nvidia driver
>> installed. I followed the notes here:
>> https://wiki.openindiana.org/oi/Nvidia+Graphics
>>
>> But to uninstall driver/graphics/nvidia, I also had to remove xorg-
>> video (meta package).
>>
>> During the 'bootadm update-archive -R /mnt' step, it reported that
>> the
>> driver was 32-bit and would be excluded.
>>
>> After that, and a reboot, lightdm won't start.
>>
>> Xorg works, running startx when logged in gives me a nice twm
>> desktop.
>> Also, Xorg.0.log states that the nvidia driver 304.137 is actually in
>> use.
>>
>> But lightdm -not so much.
>> From /var/log/lightdm/seat0-greeter.log :
>>
>> ** Message: 07:24:18.123: [Configuration] Reading file:
>> /etc/lightdm/lightdm-gtk-greeter.conf
>> ld.so.1: lightdm-gtk-greeter: fatal: libEGL.so.1: open failed: No
>> such
>> file or directory
>> ld.so.1: lightdm-gtk-greeter: fatal: relocation error: file
>> /usr/lib/64/libcairo.so.2: symbol eglGetProcAddress: referenced
>> symbol
>> not found
>> ld.so.1: lightdm-gtk-greeter: fatal: relocation error: file
>> /usr/lib/64/libgtk-3.so.0: symbol cairo_pattern_destroy: referenced
>> symbol not found
>> ld.so.1: lightdm-gtk-greeter: fatal: relocation error: file
>> /usr/sbin/lightdm-gtk-greeter: symbol gtk_init: referenced symbol not
>> found
>>
>> Which is odd, since it used to work.
>> Using ldd on /usr/sbin/lightdm-gtk-greeter, it reports:
>>
>> libEGL.so.1 =>   (file not found)
>>
>> And chasing down the symbolic links, I get:
>>
>> root@emu:/usr/lib/amd64# ls -l /usr/lib/64/libEGL.so.1
>> lrwxrwxrwx   1 root root  23 aug. 23 12:52
>> /usr/lib/64/libEGL.so.1 -> ../GL/amd64/libEGL.so.1
>>
>> root@emu:/usr/lib/amd64# ls -l /usr/lib/GL/amd64/libEGL.so.1
>> lrwxrwxrwx   1 root root  48 aug. 23 12:52
>> /usr/lib/GL/amd64/libEGL.so.1 ->
>> ../../../../var/run/opengl/lib/amd64/libEGL.so.1
>>
>> root@emu:/usr/X11/lib# ls -l /var/run/opengl/lib/amd64/libEGL.so.1 
>> lrwxrwxrwx   1 root root  37 aug. 25 07:24
>> /var/run/opengl/lib/amd64/libEGL.so.1 ->
>> /usr/X11/lib/NVIDIA/amd64/libEGL.so.1
>>
>> root@emu:/usr/lib/amd64# ls -l /usr/X11/lib/NVIDIA/amd64/libEGL.so.1
>> /usr/X11/lib/NVIDIA/amd64/libEGL.so.1: No such file or directory
>>
>> Hmm..
>>
>> So, what package is supposed to provide this?:
>>
>> root@emu:/var/log/lightdm# pkg search -l libEGL.so.1
>> INDEX  ACTION VALUE  PACKAGE
>> basename   link   usr/lib/amd64/libEGL.so.1  pkg:
>> /service/opengl/ogl-select@0.5.11-2020.0.1.5
>> basename   link   usr/lib/GL/amd64/libEGL.so.1   pkg:
>> /service/opengl/ogl-select@0.5.11-2020.0.1.5
>> basename   link   usr/lib/GL/libEGL.so.1 pkg:
>> /service/opengl/ogl-select@0.5.11-2020.0.1.5
>> basename   link   usr/lib/libEGL.so.1pkg:
>> /service/opengl/ogl-select@0.5.11-2020.0.1.5
>> basename   link   usr/lib/mesa/amd64/libEGL.so.1 pkg:
>> /x11/library/mesa@13.0.6-2020.0.1.7
>> basename   link   usr/lib/mesa/libEGL.so.1   pkg:
>> /x11/library/mesa@13.0.6-2020.0.1.7
>>
>> Looking closer at these, it seems that only the files from "mesa" are
>> actual files. The others are just symlinks.
>> These are the 'real' ones:
>>
>> root@emu:/usr# ls -l lib/mesa/libEGL.so.1
>> lrwxrwxrwx   1 root root  15 aug. 23 12:52
>> lib/mesa/libEGL.so.1 -> libEGL.so.1.0.0
>>
>> root@emu:/usr# ls -l lib/mesa/amd64/libEGL*
>> lrwxrwxrwx   1 root root  15 aug. 23 12:52
>> lib/mesa/amd64/libEGL.so -> libEGL.so.1.0.0
>> lrwxrwxrwx   1 root root  15 aug. 23 12:52
>> lib/mesa/amd64/libEGL.so.1 -> libEGL.so.1.0.0
>> -r-xr-xr-x   1 root bin   224736 aug. 23 18:32
>> lib/mesa/amd64/libEGL.so.1.0.0
>>
>> root@emu:/usr/lib/mesa/amd64# file libEGL.so.1.0.0
>> libEGL.so.1.0.0:ELF 64-bit LSB dynamic lib AMD64 Version 1,
>> dynamically linked, not stripped, no debugging information available
>>
>>
>> So it seems that the files are there, but the symlinks are incorrect.
>>
>> It looks like the libs from the mesa package are never found.
>>
>>
>> What could be the cause of this and how do I fix it?
>>  
>> TIA,
>>
>> /tony
>>

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

Re: [OpenIndiana-discuss] Nvidia card installed.. now lightdm fails

[Till Wegmüller]

Hi Tony

We use the SMF service ogl-select (OpenGL Select) to switch between the
mesa and nvidia implementations of OpenGL libraries. Nvidia due to it's
proprietary nature had to reimplement all GPL libraries aswell. If you
have a 32bit nvidia driver you will be missing the required 64bit OpenGL
Libraries. Try to see if you can find a more current driver. There was a
support cut of cards around version 304 but that should already be
64bit. The guide in "https://wiki.openindiana.org/oi/Nvidia+Graphics;
may be out of date though. We still have
https://github.com/OpenIndiana/oi-userland/pull/3673 open to make the
process of picking nvidia cards smooth. But nobody had the resources or
the need to work on that. If you'd like to contribute some testing, PR
3673 would be something that should benefit you aswell.


Greetings
Till

On 25.08.20 08:36, Tony Brian Albers wrote:
> Good morning,
> 
> So I managed to find an old nvidia card, and I got the nvidia driver
> installed. I followed the notes here:
> https://wiki.openindiana.org/oi/Nvidia+Graphics
> 
> But to uninstall driver/graphics/nvidia, I also had to remove xorg-
> video (meta package).
> 
> During the 'bootadm update-archive -R /mnt' step, it reported that the
> driver was 32-bit and would be excluded.
> 
> After that, and a reboot, lightdm won't start.
> 
> Xorg works, running startx when logged in gives me a nice twm desktop.
> Also, Xorg.0.log states that the nvidia driver 304.137 is actually in
> use.
> 
> But lightdm -not so much.
> From /var/log/lightdm/seat0-greeter.log :
> 
> ** Message: 07:24:18.123: [Configuration] Reading file:
> /etc/lightdm/lightdm-gtk-greeter.conf
> ld.so.1: lightdm-gtk-greeter: fatal: libEGL.so.1: open failed: No such
> file or directory
> ld.so.1: lightdm-gtk-greeter: fatal: relocation error: file
> /usr/lib/64/libcairo.so.2: symbol eglGetProcAddress: referenced symbol
> not found
> ld.so.1: lightdm-gtk-greeter: fatal: relocation error: file
> /usr/lib/64/libgtk-3.so.0: symbol cairo_pattern_destroy: referenced
> symbol not found
> ld.so.1: lightdm-gtk-greeter: fatal: relocation error: file
> /usr/sbin/lightdm-gtk-greeter: symbol gtk_init: referenced symbol not
> found
> 
> Which is odd, since it used to work.
> Using ldd on /usr/sbin/lightdm-gtk-greeter, it reports:
> 
> libEGL.so.1 =>   (file not found)
> 
> And chasing down the symbolic links, I get:
> 
> root@emu:/usr/lib/amd64# ls -l /usr/lib/64/libEGL.so.1
> lrwxrwxrwx   1 root root  23 aug. 23 12:52
> /usr/lib/64/libEGL.so.1 -> ../GL/amd64/libEGL.so.1
> 
> root@emu:/usr/lib/amd64# ls -l /usr/lib/GL/amd64/libEGL.so.1
> lrwxrwxrwx   1 root root  48 aug. 23 12:52
> /usr/lib/GL/amd64/libEGL.so.1 ->
> ../../../../var/run/opengl/lib/amd64/libEGL.so.1
> 
> root@emu:/usr/X11/lib# ls -l /var/run/opengl/lib/amd64/libEGL.so.1 
> lrwxrwxrwx   1 root root  37 aug. 25 07:24
> /var/run/opengl/lib/amd64/libEGL.so.1 ->
> /usr/X11/lib/NVIDIA/amd64/libEGL.so.1
> 
> root@emu:/usr/lib/amd64# ls -l /usr/X11/lib/NVIDIA/amd64/libEGL.so.1
> /usr/X11/lib/NVIDIA/amd64/libEGL.so.1: No such file or directory
> 
> Hmm..
> 
> So, what package is supposed to provide this?:
> 
> root@emu:/var/log/lightdm# pkg search -l libEGL.so.1
> INDEX  ACTION VALUE  PACKAGE
> basename   link   usr/lib/amd64/libEGL.so.1  pkg:
> /service/opengl/ogl-select@0.5.11-2020.0.1.5
> basename   link   usr/lib/GL/amd64/libEGL.so.1   pkg:
> /service/opengl/ogl-select@0.5.11-2020.0.1.5
> basename   link   usr/lib/GL/libEGL.so.1 pkg:
> /service/opengl/ogl-select@0.5.11-2020.0.1.5
> basename   link   usr/lib/libEGL.so.1pkg:
> /service/opengl/ogl-select@0.5.11-2020.0.1.5
> basename   link   usr/lib/mesa/amd64/libEGL.so.1 pkg:
> /x11/library/mesa@13.0.6-2020.0.1.7
> basename   link   usr/lib/mesa/libEGL.so.1   pkg:
> /x11/library/mesa@13.0.6-2020.0.1.7
> 
> Looking closer at these, it seems that only the files from "mesa" are
> actual files. The others are just symlinks.
> These are the 'real' ones:
> 
> root@emu:/usr# ls -l lib/mesa/libEGL.so.1
> lrwxrwxrwx   1 root root  15 aug. 23 12:52
> lib/mesa/libEGL.so.1 -> libEGL.so.1.0.0
> 
> root@emu:/usr# ls -l lib/mesa/amd64/libEGL*
> lrwxrwxrwx   1 root root  15 aug. 23 12:52
> lib/mesa/amd64/libEGL.so -> libEGL.so.1.0.0
> lrwxrwxrwx   1 root root  15 aug. 23 12:52
> lib/mesa/amd64/libEGL.so.1 -> libEGL.so.1.0.0
> -r-xr-xr-x   1 root bin   224736 aug. 23 18:32
> lib/mesa/amd64/libEGL.so.1.0.0
> 
> root@emu:/usr/lib/mesa/amd64# file libEGL.so.1.0.0
> libEGL.so.1.0.0:ELF 64-bit LSB dynamic lib AMD64 Version 1,
> dynamically linked, not stripped, no debugging information available
> 
> 
> So it seems that the files are there, but the symlinks are incorrect.
> 
> It looks like the libs from the mesa package are never found.
> 
> 
> What could be the cause of this and how do I fix it?
>  
> TIA,
> 
> /tony
> 

Re: [OpenIndiana-discuss] ati graphics and driver installed, but X complains

[Till Wegmüller]

Hi Tony

Unfortunately no. While the amdgpu drivers are Open-SOurce these days,
nobody has finished the work of porting them from Linux to illumos yet.

There was some people in the community talking about doing it, but I do
not know the status of that project.

You can of course port the driver, but thats the only way to get ATI
graphics cards to run.

Hope this helps
Greetings
Till
On 24.08.20 10:00, Tony Brian Albers wrote:
> Hi guys,
> 
> Following the issues with the Intel graphics, I installed an ati card
> in the machine. The machine no longer panics, but I'm only able to use
> the vesa driver for some reason.
> 
> From Xorg.0.log:
> [37.225] (==) Matched ati as autoconfigured driver 0
> [37.225] (==) Matched vesa as autoconfigured driver 1
> [37.225] (==) Assigned the driver to the xf86ConfigLayout
> [37.225] (II) LoadModule: "ati"
> [37.226] (II) Loading
> /usr/lib/xorg/modules/drivers/amd64/ati_drv.so
> [37.226] (II) Module ati: vendor="X.Org Foundation"
> [37.226]compiled for 1.19.5, module version = 6.14.6
> [37.226]Module class: X.Org Video Driver
> [37.226]ABI class: X.Org Video Driver, version 23.0
> [37.226] (II) LoadModule: "radeon"
> [37.227] (II) Loading
> /usr/lib/xorg/modules/drivers/amd64/radeon_drv.so
> [37.229] (II) Module radeon: vendor="X.Org Foundation"
> [37.229]compiled for 1.19.5, module version = 6.14.6
> [37.229]Module class: X.Org Video Driver
> [37.229]ABI class: X.Org Video Driver, version 23.0
> [37.230] (II) LoadModule: "vesa"
> [37.230] (II) Loading
> /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so
> [37.262] (II) Module vesa: vendor="X.Org Foundation"
> [37.262]compiled for 1.19.5, module version = 2.4.0
> [37.262]Module class: X.Org Video Driver
> [37.262]ABI class: X.Org Video Driver, version 23.0
> [37.262] (II) RADEON: Driver for ATI Radeon chipsets:
> .
> 
> GPU only supported with KMS, using vesa instead.
> 
> 
> So, how do I get it to work? Is it even possible?
> 
> /tony
> 
> 
> 

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

Re: [OpenIndiana-discuss] System unstable after pkg update Aug 6 and 8

[Till Wegmüller]

Hi Jack


Yes you can install into an existing zpool with the text installer
available on both the live image and the the text image.

In cases like this a crashdump is needed to analyse what the culprit may
be. You can also get that by mounting the zpool in the live image and
using savecore from the live image on the pool.

The manpage of savecore also mentions the posibility of gathering a dump
from a file with the -f flag. According to the manpage the trick is to
copy the dump with dd to a file and use savecore -f on that file. I have
not used this but my guess is dd will copy the whole device and that
will take up the full size of the device on disk. So you will need quite
a bit of disk space.

Hope this helps
Greetings
Till

On 10.08.20 03:29, Jack Whitehead wrote:
> Greetings all,
> 
> My machine was quite stable until I did a "pkg update" on Aug 6. I did 
> another on Aug 8 hoping to fix the problem. I do have a few panic dumps.
> The machine was stable enough this morning to run savecore a couple of times 
> but it won't stay up long enough to do much with mdb now.
> 
> I'm running memtest86+ at the moment. Two passed so far with no errors makes 
> me think the culprit was the last update.
> 
> Has anyone else experienced stability problems after a recent update?
> 
> I suspect my only option at this point is a reinstall given that I don't have 
> a BE old enough to go back to.
> 
> Hopefully I can reinstall to the existing rpool so that I can recover the 
> crash dump.
> 
> Thanks in advance for any suggestions.
> 
> Jack
> ___
> 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] Next Autoconf release and OpenIndiana

[Till Wegmüller]

Hi Bob

Thanks for the Initiative. We have begun integrating the new beta
release for testing into OI-userland builds [0]

OI userland also includes up to date vagrant boxes to build packages in.
Both for libvirt provider and virtualbox. [1]

Hope this helps

Greetings
Till

[0] https://github.com/OpenIndiana/oi-userland/pull/5911
[1] https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/Vagrantfile
On 04.08.20 20:49, Bob Friesenhahn wrote:
> FYI, for those of you who are not paying attention, there is a new
> Autoconf release coming soon.  I have provided the developers with
> access to OpenIndiana and OmniOS machines in order to flush out
> remaining issues.
> 
> If there is something which has been troubling you about Autoconf under
> OpenIndiana, this would be a good time to join the autoconf mailing list
> for discussion, or post Autoconf bug reports regarding issues you are
> aware of which still exist in the latest git version.
> 
> If have heard that Autoconf git now passes its test suite on my
> OpenIndiana machine.
> 
> It turns out that having /usr/xpg4/bin prior to some other directory
> containing a 'rm' program causes the ksh93 AST shell to emulate the 'rm'
> but it's emulation works incorrectly for 'rm -f' (it returns an error)
> when no argument to it is provided.  Recent Automake releases will
> refuse to work in this case.
> 
> See https://savannah.gnu.org/support/?110283 for the details.
> 
> Bob

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

Re: [OpenIndiana-discuss] Firefox

[Till Wegmüller]

Hi

From my side Work on this has started and stalled multiple times,
because the Complexity for this release has increased quite a bit. Also
this release seems to behave differently depending on which developer
compiles it sometimes someone runs into a header conflict and somebody
else doesn't. We have still some people who want to try their luck but
Firefox has become a PITA for some reason and we cant say why. It will
take time but we cannot say how long.


Sorry to not have better news.
Greetings
Till

On 07.07.20 09:42, Alexander Pyhalov via openindiana-discuss wrote:
> Hi.
> Not on my side.
> So far I have no time for large tasks. I can do small thing here and there, 
> but I think I'll not be able to contribute something complex in the next 
> several months.
> 
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
> 
> 
> 
> От: Apostolos Syropoulos via openindiana-discuss 
> 
> Отправлено: 5 июля 2020 г. 13:10
> Кому: Discussion List for OpenIndiana
> Копия: Apostolos Syropoulos
> Тема: [OpenIndiana-discuss] Firefox
> 
> Hello,
> Are there any plans to have a more recentversion of Firefox? Some Google 
> sitescomplain that this version is quite old!I upgraded my system last May.
> Kind regards,Apostolos
> Στάλθηκε από το Ταχυδρομείο Yahoo σε 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
> 

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

Re: [OpenIndiana-discuss] What's the easiest, straight-shot way to upgrade to a new boot SSD?

[Till Wegmüller]

Have a look at zfs-send(1m)

it's -r. You must have a snapshot to send you cannot sent datasets
directly. The snapshots must be named exaclty the same on the whole
pool. You can achieve this with zfs snap -r very easily.

Hope this helps
Greetings
Till

On 21.06.20 01:03, Judah Richardson wrote:
> I can't seem to find any command that recursively sends all the datasets on
> 1 zpool to another ...
> 
> This is all very confusing and frustrating. Disk upgrades must have been a
> considered user operation, no? Why not make it intuitive and simple? :(
> 
> On Sat, Jun 20, 2020 at 5:58 PM Jonathan Adams 
> wrote:
> 
>> I've never done that, but it must be worth a go, unless you want to just
>> install a new system in the new disk and copy over the files you want to
>> change afterwards ...
>>
>> On Sat, 20 Jun 2020, 23:46 Judah Richardson, 
>> wrote:
>>
>>> On Sat, Jun 20, 2020 at 2:29 AM Guenther Alka 
>> wrote:
>>>
 Another option is to backup the current BE to the datapool via zfs
>> send.

>>> Would it be possible to just zfs send everything from the current SSD to
>>> the new one, then enable autoexpand on the new SSD and make it bootable?
>>>
>>> This can be done continously via incremental send for ongoing backups.
 If the system disk fails (or you want to replace), add a new disk,
 install a default OS, import the datapool and restore the BE via zfs
 send. Then activate this BE and reboot to have the exact former OS
 installation restored.

   Gea
 @napp-it.org

 Am 19.06.2020 um 21:19 schrieb Gary Mills:
> On Fri, Jun 19, 2020 at 01:23:35PM -0500, Judah Richardson wrote:
>> I currently run OpenIndiana Hipster on a 32 GB SSD. I'd like move
>> that
>> installation to a 128 GB SSD. What's the easiest way to do this?
> The easiest way is to use zpool commands.  First, add the large SSD
>> as
> half a mirror to the smaller one.  Then, detach the smaller one.
> These options are all described in the zpool man page.
>
> You will likely need to use the installboot command on the large SSD
> to make it bootable before you do the detach.  This operation is
> described in the installboot man page.
>
>> I was thinking of using Clonezilla, but I'm not sure if that's the
>> way
 to
>> go here.
> I'd recommend using native illumos commands instead.
>

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

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

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

Re: [OpenIndiana-discuss] problem with gcc 7.5

[Till Wegmüller]

Hi Marc

That is the Compiler for the SFE Project not the System one capable of
compiling own Projects.

You will want
pkg://openindiana.org/developer/gcc-7@7.5.0-2020.0.1.1:20200330T115854Z

Greetings
Till
On 18.05.20 09:36, Marc Lobelle wrote:
> Hello,
> 
> I tried to recompile fig2dev on a freshly installed OI-hipster2020.04
> and ./configure failed. Can one of you suggest me what to do ?
> 
> Thanks
> 
> 
> Marc
> 
> the installed gcc is pkg://localhostoih/sfe/developer/gcc
> 
> system/header is also installed
> 
> ml@spitfire:/opt/fig2dev-3.2.6a# ./configure
> checking for a BSD-compatible install... /usr/gnu/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /usr/gnu/bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking for gcc... gcc
> checking whether the C compiler works... no
> configure: error: in `/opt/fig2dev-3.2.6a':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
> ml@spitfire:/opt/fig2dev-3.2.6a# cat config.log
> ...
> 
> 
> ## --- ##
> ## Core tests. ##
> ## --- ##
> 
> configure:2324: checking for a BSD-compatible install
> configure:2392: result: /usr/gnu/bin/install -c
> configure:2403: checking whether build environment is sane
> configure:2458: result: yes
> configure:2609: checking for a thread-safe mkdir -p
> configure:2648: result: /usr/gnu/bin/mkdir -p
> configure:2655: checking for gawk
> configure:2671: found /usr/bin/gawk
> configure:2682: result: gawk
> configure:2693: checking whether make sets $(MAKE)
> configure:2715: result: yes
> configure:2744: checking whether make supports nested variables
> configure:2761: result: yes
> configure:2963: checking for gcc
> configure:2979: found /usr/gnu/bin/gcc
> configure:2990: result: gcc
> configure:3219: checking for C compiler version
> configure:3228: gcc --version >&5
> gcc (GCC) 7.5.0
> Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> configure:3239: $? = 0
> configure:3228: gcc -v >&5
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/gcc-sfe/7/lib/gcc/i386-pc-solaris2.11/7.5.0/lto-wrapper
> 
> Target: i386-pc-solaris2.11
> Configured with: ../gcc-7.5.0/configure --prefix=/usr/gcc-sfe/7
> --libdir=/usr/gcc-sfe/7/lib --libexecdir=/usr/gcc-sfe/7/lib
> --mandir=/usr/gcc-sfe/7/share/man --infodir=/usr/gcc-sfe/7/info
> --with-build-time-tools=/usr/sfw --with-as=/usr/sfw/bin/gas
> --with-gnu-as --with-ld=/usr/bin/ld --without-gnu-ld
> --enable-languages=c,c++,fortran,objc --enable-shared --disable-static
> --enable-decimal-float --with-gmp=/usr/gnu --with-mpfr=/usr/gnu
> --with-mpc=/usr/gnu --disable-bootstrap --disable-nls
> --without-libiconv-prefix --enable-plugins --enable-initfini-array
> --disable-libitm --enable-frame-pointer
> Thread model: posix
> gcc version 7.5.0 (GCC)
> configure:3239: $? = 0
> configure:3228: gcc -V >&5
> gcc: error: unrecognized command line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> configure:3239: $? = 1
> configure:3228: gcc -qversion >&5
> gcc: error: unrecognized command line option '-qversion'; did you mean
> '--version'?
> gcc: fatal error: no input files
> compilation terminated.
> configure:3239: $? = 1
> configure:3259: checking whether the C compiler works
> configure:3281: gcc    conftest.c  >&5
> gcc: error trying to exec 'as': execvp: No such file or directory
> configure:3285: $? = 1
> configure:3323: result: no
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME "fig2dev"
> | #define PACKAGE_TARNAME "fig2dev"
> | #define PACKAGE_VERSION "3.2.6a"
> | #define PACKAGE_STRING "fig2dev 3.2.6a"
> | #define PACKAGE_BUGREPORT "thomas.loi...@tuwien.ac.at"
> | #define PACKAGE_URL "https://sourceforge.net/projects/mcj;
> | #define PACKAGE "fig2dev"
> | #define VERSION "3.2.6a"
> | /* end confdefs.h.  */
> |
> ...
> 
> 
> ___
> 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] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd May 2020

[Till Wegmüller]

Did we import the mandatory Virtualbox Patch yet? Since a few days the
illumos kernel initialises hma_vmx for bHyve and kvm, Virtualbox needs a
patch otherwise this will occur.


-Till

On 06.05.20 21:01, Alexander Pyhalov via openindiana-discuss wrote:
> Hi.
> Do you have KVM VMs running?
> Are there any errors in /var/adm/messages regarding hma_vmx_init?
> 
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
> 
> 
> 
> От: russell 
> Отправлено: 6 мая 2020 г. 21:13
> Кому: Discussion list for OpenIndiana
> Тема: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd 
> May 2020
> 
> Hi
> 
> Just upgraded to latest OpenIndiana Hipster release this evening and now
> when I attempt to start VirtualBox I get the following error
> 
> VirtualBox can't enable the AMD-V extension. Please close all other
> virtualization programs. (VERR_SVM_IN_USE).
> 
> Result Code:
> 
> 
> 
> NS_ERROR_FAILURE (0x80004005)
> 
> Component:
> 
> 
> 
> ConsoleWrap
> 
> Interface:
> 
> 
> 
> IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
> 
> ___
> 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] OpenIndiana Hipster 2020.04

[Till Wegmüller]

And current Vagrant images are live under [0]

[0] https://app.vagrantup.com/Toasterson/boxes/openindiana-hipster


Greetings
Till

On 05.05.20 12:11, Alexander Pyhalov via openindiana-discuss wrote:
> OpenIndiana Hipster 2020.04 snapshot is ready.
> 
> Images:
> 
> http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-gui-20200504.iso
> http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-gui-20200504.usb
> 
> http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-text-20200504.iso
> http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-text-20200504.usb
> 
> http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-minimal-20200504.iso
> http://dlc.openindiana.org/isos/hipster/20200504/OI-hipster-minimal-20200504.usb
> 
> 
> SHA 256 checksums are available at ${link}.sha256sum
> Signed SHA 256 checksums are available at ${link}.sha256sum.asc
> The OpenIndiana Release Engineering key has key id 0x3a021afadbe31887
> Note - I've had to update key today,  pks key servers still refer to outdated 
> key. ).
> 
> Release notes: 
> http://docs.openindiana.org/release-notes/2020.04-release-notes/
> 
> 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] Server crash diagnostics?

[Till Wegmüller]

0062A7D487d0
> 
> 1.61.51.92.7  0.0  0.00.05.0   0   1 
> c4t5000C50062B279E7d0
> 
> 1.61.51.92.7  0.0  0.00.05.0   0   1 
> c4t5000C50062A6E74Bd0
> 
> 1.61.51.92.7  0.0  0.00.04.9   0   1 
> c4t5000C50062A7D78Bd0
> 
> 1.61.51.92.7  0.0  0.00.05.0   0   1 
> c4t5000C50062B3EFBFd0
> 
> 7.31.4   41.32.7  0.0  0.10.07.8   0   3 
> c4t5000C5007F5AE0F3d0
> 
> 7.21.4   41.32.7  0.0  0.10.07.8   0   3 
> c4t5000C5007F57A403d0
> 
> 7.31.4   41.32.7  0.0  0.10.07.8   0   3 
> c4t5000C5007F5C8077d0
> 
> 7.31.4   41.32.7  0.0  0.10.07.8   0   3 
> c4t5000C5007F5929DBd0
> 
> 7.31.4   41.32.6  0.0  0.10.07.8   0   3 
> c4t5000C5007F5AC47Bd0
> 
> 7.31.4   41.32.7  0.0  0.10.07.8   0   3 
> c4t5000C5007F5B639Bd0
> 
> 7.31.4   41.32.7  0.0  0.10.07.8   0   3 
> c4t5000C5007F5FE40Bd0
> 
>   377.81.3 22175.02.5  0.0  1.40.03.6   0  63 
> c4t5000C5008518AC43d0
> 
>23.61.5  373.12.8  0.0  0.10.05.5   0   7 
> c4t5000C5008518F793d0
> 
>23.51.5  373.12.8  0.0  0.10.05.6   0   7 
> c4t5000C500851C0F43d0
> 
>23.51.5  373.12.8  0.0  0.10.05.6   0   7 
> c4t5000C5008518D683d0
> 
>   377.81.3 22176.62.5  0.0  1.40.03.6   0  63 
> c4t5000C5008518A757d0
> 
>   379.71.3 22178.12.5  0.0  1.40.03.6   0  62 
> c4t5000C5008518F957d0
> 
>23.61.5  373.22.8  0.0  0.10.05.5   0   7 
> c4t5000C5008518C007d0
> 
>23.61.5  373.22.8  0.0  0.10.05.6   0   7 
> c4t5000C50085151C57d0
> 
>   379.31.3 22176.82.5  0.0  1.30.03.5   0  62 
> c4t5000C5008519177Bd0
> 
>   378.31.3 22177.12.5  0.0  1.30.03.5   0  62 
> c4t5000C5008515EE8Bd0
> 
>23.61.5  373.32.8  0.0  0.10.05.5   0   7 
> c4t5000C5008519BD0Bd0
> 
>   378.51.3 22194.92.5  0.0  1.40.03.6   0  62 
> c4t5000C5008518AFFFd0
> 
>   378.01.3 22194.52.5  0.0  1.40.03.6   0  63 
> c4t5000C5008518BA9Fd0
> 
> 0.00.00.00.0  0.0  0.00.00.0   0   0 
> c4t5000C50085151A1Fd0
> 
>23.61.5  373.62.8  0.0  0.10.05.5   0   7 
> c4t5000C5008518D25Fd0
> 
> 5.03.78.47.9  0.0  0.00.04.7   0   2 
> c4t5000C500980D4333d0
> 
> 0.00.00.00.0  0.0  0.00.00.0   0   0 
> c4t5000C500980D11EBd0
> 
> 5.03.78.47.9  0.0  0.00.04.7   0   2 
> c4t5000C500980D0E53d0
> 
> 5.03.88.47.9  0.0  0.00.04.7   0   2 
> c4t5000C500980D087Fd0
> 
> 5.03.78.47.9  0.0  0.00.04.7   0   2 
> c4t5000C500980D443Fd0
> 
> 5.03.78.47.9  0.0  0.00.04.7   0   2 
> c4t5000C500980D2913d0
> 
> 5.03.78.47.9  0.0  0.00.04.7   0   2 
> c4t5000C500980D0C4Fd0
> 
> 1.51.32.12.7  0.0  0.00.07.4   0   1 
> c4t5000C5008CF235EBd0
> 
> 0.00.00.20.2  0.0  0.00.01.5   0   0 
> c4t5000C500B1B3BE12d0
> 
> 0.00.00.20.2  0.0  0.00.01.7   0   0 
> c4t5000C500B1B5529Ad0
> 
> 0.00.00.20.2  0.0  0.00.01.6   0   0 
> c4t5000C500B1B6C4EBd0
> 
> 0.00.00.20.2  0.0  0.00.01.6   0   0 
> c4t5000C500B1B65CF2d0
> 
> 5.81.26.52.6  0.0  0.00.06.9   0   2 
> c4t5000C5008CF23EC1d0
> 
> 4.93.48.47.9  0.0  0.00.05.7   0   2 
> c4t5000C5008CF23896d0
> 
> 0.00.00.20.2  0.0  0.00.01.7   0   0 
> c4t5000C500B1B1BE97d0
> 
> 0.00.00.20.2  0.0  0.00.01.9   0   0 
> c4t5000C500B1B4DB26d0
> 
> 5.81.26.42.6  0.0  0.00.06.3   0   2 
> c4t5000C500B0E7E1A9d0
> 
> 5.03.88.47.9  0.0  0.00.04.9   0   2 
> c4t5000C5007E98965Fd0
> 
> 5.92.55.83.9  0.0  0.00.05.2   0   2 
> c4t5000C500B70E2A6Fd0
> 
>18.31.6   25.22.8  0.0  0.10.06.1   0   6 
> c0t5000C5008518AEFAd0
> 
> 0.0  543.50.0 22610.6  0.0  0.50.00.9   0  48 
> c4t5000C500AF3E90DBd0
> 
> 
> 
> 
> 
> -Original Message-
> From: Till Wegmüller 
> Sent: Tuesday, April 21, 2020 12:43 PM
> To: openindiana-discuss@openindiana.org
> Subject: Re: [OpenIndiana-discuss] Server crash diagnostics?
> 
> 
> 
> Hi Bart
>

Re: [OpenIndiana-discuss] Thunderbird troubles

[Till Wegmüller]

Hi

A shot in the dark but.
Is a dialog being hidden by the Thunderbird main window?

Greetings
Till

On 21.04.20 21:28, John Garrison wrote:
> I am having the same exact issue as all here...i will keep tinkering with
> it though.
> ___
> 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] Server crash diagnostics?

[Till Wegmüller]

Hi Bart

That is not too hard to debug. There are two possible options. It's a
Software bug. THe solution to that is simple. Update your Box. The
second and more probable option, is that one of your disks is being
nasty. Unfortunately I have had the pleasure with such disks before.

To find any nasty disks run `iostat -xn 1` where 1 is the interval to
measure the statistics in seconds.

This will produce an output like so:
extended device statistics
r/sw/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
2.9   47.8   27.6 1038.5  0.2  0.03.80.3   0   1 rpool
2.9   59.2   27.6 1038.5  0.0  0.00.20.1   1   0 c5t0d0
extended device statistics
r/sw/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
0.0  135.60.0 1067.6  0.2  0.01.60.1   1   1 rpool
0.0  137.60.0 1067.6  0.0  0.00.00.0   0   1 c5t0d0
extended device statistics
r/sw/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
0.00.00.00.0  0.0  0.00.00.0   0   0 rpool
0.00.00.00.0  0.0  0.00.00.0   0   0 c5t0d0


Important is asvc_t and %w statistics. Under load it can be normal for
them to be up to 80 or 100. a value over 100 means the disk or a
hardware in between is delaying writes to the disk. In that case ZFS
will try to cache as much as it can to let the hardware catch up until
it exhausts it's resources. Some disks manage to get the server offline
as they simply time out all scsi commands instead of returning errors.

Once you have found the disk offline it with zpool offline and replace
it. As soon as the disk has been taken offline your performance should
normalise. You might need to wait for a situation where load occurs though.

Hope this helps
Greetings
Till

On 21.04.20 21:14, Bart Brashers via openindiana-discuss wrote:
> Hi everyone, I'm new to this listserv. I run Air Quality and Meteorological 
> models on an HPC cluster, which is all CentOS except for one storage server 
> running OpenIndiana (SunOS 5.11 oi_151a9 November 2013). I know, I know, it's 
> a ridiculously old installation, please don't bug me about that.
> 
> I would like to figure out what happened to that server this past weekend. My 
> goal is to figure out if there's something I can do to avoid having the 
> problem described below happen again.
> 
> OpenIndiana is running on a Supermicro box, with a SAS attached JBOD, about 
> 85 spinning disks in two ZFS pools, one of SAS disks the other of SATA disks. 
> Periodically, when load gets too high, it becomes unresponsive for 5 - 30 
> minutes, but if we're patient enough it comes back. The load (as reported by 
> /usr/bin/top) immediately after such an event is ~200, which rapidly falls 
> back to a more normal range of ~0.5.
> 
> Two days ago on Sunday evening, it went off into la-la land again, but after 
> a few hours hadn't come back. The IMPI interface was also not responding, so 
> I couldn't reboot it remotely. I went in to the office on Monday morning and 
> shut down the server, then pulled the power cords for 20 seconds. The 
> complete removal of power often helps in situations like this, I've found.
> 
> The server then entered an endless loop, where it would try to boot, timeout 
> about 6 times (taking ~5 minutes for each timeout) with the following 
> message, then kernel panic and reboot.
> 
> Warning: /pci@0,0/pci8086,3c04@2/pci100,3020@0 (mpt_sas10):
>Disconnected command timeout for Target 156
> ...repeat...
> panic[cpu0]/thread=ff01e80cbc40: I/O to pool 'pool0' appears to be hung.
> 
> Great! This OS already has so many names for disks, here's another one: which 
> disk is Target 156? Sometimes it was Target 75, sometimes it was Target 150. 
> Or is that a SAS expander? I could not log in, it would never get that far 
> before the kernel panic and reboot.
> 
> I was able to boot into single-user mode (append -s to the grub line 
> containing "kernel") and poked around until I found two disks that were 
> reporting errors. fmdump -eV was useful, though so verbose it took a while to 
> figure out what to read. The best/clearest method was echo | format, which is 
> not a command I would have guessed based on decades of experience with Linux 
> ;-). I pulled two bad disks, and rebooted... and it went back into the 
> endless panic-reboot loop.
> 
> I eventually found this page: 
> https://docs.oracle.com/cd/E23824_01/html/821-1448/gbbwc.html#scrolltoc and 
> followed this procedure:
> 
> 
>   *   When the booting gets to the grub stage, press e to edit
>   *   Scroll to the line containing "kernel" and press e again edit
>   *   At the end of the line, add the text -m milestone=none and press enter
>   *   Press b to boot
>   *   Login as root
>   *   (The root filesystem [mounted at /] was already read-write, not 
> read-only, for me)
>   *   Rename /etc/zfs/zpool.cache to something else
>   *   

Re: [OpenIndiana-discuss] Thunderbird Gmail on OI?

[Till Wegmüller]

Hi all

Google has recently started to disable Anything else but OAuth. Please
switch to the OAuth Method. You will need to have at least OI Hipster
and the newest available Thunderbird from IPS installed on that.


Greetings
Till

On 21.04.20 15:26, Predrag Zecevic wrote:
> Hi all,
> 
> I am using "OAuth2" authentication method (Server settings for account)
> - and only that works
> 
> Regards.
> 
> On 21.04.2020 14:43, Bob Friesenhahn wrote:
>> Since yesterday I have been trying to get Thunderbird set up to work
>> with my Gmail email account (IMAP+SMTP).  Thus far I have not been
>> successful.
>>
>> Everything appears to work with account setup but when I click on Done
>> in the Mail Account Setup screen, it sits in "Checking password..."
>> forever.
>>
>> Google does all of its normal notifications so you can confirm that it
>> was you.  Behavior seems normal on the Google side.
>>
>> I did manage to set up a working configuration using my own (dovecot)
>> mail server.
>>
>> Are others encountering this problem?  Is there a work-around?
>>
>> Bob
> 

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

Re: [OpenIndiana-discuss] OT Help with Repair of HPxw8600

[Till Wegmüller]

The most common thing that happens for me is dust in the electronic
connectors. Although I do live in a house with terrible dust issue.

Vacuuming the Machine will not hurt though.

Greeting
Till

On 19.04.20 20:06, Harry Putnam wrote:
> Sorry about OT topic but hoped someone here could offer helpful URLS
> and such.
> 
> My old HP xw8600 that I have been running OI one for some years has
> broke down.
> 
> I'm a bit lost at trying to repair an old HP xw8600.
> 
> I get 5 beeps pause and repeat on attempt to boot.
> 
> From Manuals and such I find that means a memory problem.
> 
> I guess it would require me to remove 1 at a time and attempt to boot
> to find one or more that are faulty.
> 
> I'm a bit nervous about trying this myself.
> 
> Ok is that one a time scenario even a real option?  I wondered what
> happens when you remove a mem stick... will a boot be
> possible. even with all but one removed?
> 
> Also curious if parts are even available for older HP xw8600
> manufactured in 2008.
> 
> The helpful forums that used to be on HP's own site appear to have
> been redone or maybe consolidated or something... at any rate was not
> able to find forum help I used several years ago there.  And a posted 
> question about the 5 beep syndrome has gone unanswered for a week.
> 
> Again, not looking for a discussion here only hoping for URLS or other
> pointers that will help me do it myself.
> 
> Especially would be good if someone knows someone who actual has done
> such work and is willing to correspond with me.
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

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

Re: [OpenIndiana-discuss] /hipster: migrate rpool to bigger disk

[Till Wegmüller]

Hi Predrag

You will want to have a look at bootadm(1) manpage.

You will need to both install the bootloader and update the archive with
the -R (altroot) switch.

Greetings
Till

On 15.04.20 15:30, Predrag Zecevic wrote:
> Hi all,
> 
> I was searching around how to migrate (copy) rpool to bigger disk. Found
> plenty solutions with grub solution, but for /hipster we use boot
> loader, right?
> 
> This
> (https://openindiana.org/pipermail/openindiana-discuss/2017-September/021431.html)
> does not explain procedure and is only result I could get with my logic
> of searching web...
> 
> Do we have some documentation available somewhere?
> 
> My case is single disk rpool, and I want to "clone" it to larger, and
> perhaps with ashift=12 option newly created "rpool", which then will
> become new bootable device.
> 
> Thanks in advance for any pointer (I did ignored docs from
> wiki.openindiana.org and could not find guide on docs.openindiana.org).
> 
> Regards.

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

Re: [OpenIndiana-discuss] Upgraded to lastest hipster release today - pkg broken

[Till Wegmüller]

Hi

You can either switch to the old BE or use the method described by Stephan.

If you choose this method. Please run "pkg fix" after, so that you have
a working system state. And remove
"/usr/gnu/lib/amd64/libstdc++.so.6.disabled" Just to be safe.

Greetings
Till

On 05.04.20 09:36, Stephan Althaus wrote:
> HI!
> 
> :; pfexec mv /usr/gnu/lib/amd64/libstdc++.so.6
> /usr/gnu/lib/amd64/libstdc++.so.6.disabled
> 
> Greetings,
> Stephan
> 
> On 04/05/20 01:00, russell wrote:
>> Hi
>>
>> Performed a pkg upgrade today creating a new BE, now when I use pkg I
>> get the following error
>>
>> # pkg refresh --full
>> Traceback (most recent call last):
>>   File "/usr/bin/pkg", line 87, in 
>>     import pkg.actions as actions
>>   File "/usr/lib/python3.5/vendor-packages/pkg/actions/__init__.py",
>> line 68, in 
>>     globals(), locals(), [modname])
>>   File "/usr/lib/python3.5/vendor-packages/pkg/actions/signature.py",
>> line 37, in 
>>     from . import generic
>>   File "/usr/lib/python3.5/vendor-packages/pkg/actions/generic.py",
>> line 49, in 
>>     import pkg.variant as variant
>>   File "/usr/lib/python3.5/vendor-packages/pkg/variant.py", line 36,
>> in 
>>     from pkg.misc import EmptyI
>>   File "/usr/lib/python3.5/vendor-packages/pkg/misc.py", line 76, in
>> 
>>     import pkg.json as json
>>   File "/usr/lib/python3.5/vendor-packages/pkg/json.py", line 24, in
>> 
>>     from rapidjson import loads, load, dumps, dump, JSONDecodeError
>> ImportError: ld.so.1: python3.5: fatal: relocation error: file
>> /usr/lib/python3.5/vendor-packages/rapidjson.cpython-35m.so: symbol
>> __gxx_personality_v0: referenced symbol not found
>>
>> How can I fix this or should I just activate the previous BE and
>> delete the current boot environment?
>>
>> TIA
>>
>>
>>
>> ___
>> 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] minIO on OpenIndiana

[Till Wegmüller]

Hi Thanks for that work

Please be advised, that running Go binaries compiled on illumos on
Solaris is not supported and is known to break. We have included the
illumos build tag for that. I do not know if these binaries will
continue to work. You can compile binaries for the Platform they are
going to be running on by either setting GOOS environment variable to
"illumos" or "solaris" respectively. Cross compiling requires the
Environment variable CGO_ENABLED to be set to 0

Greetings
Till

On 03.04.20 19:08, Günther Alka wrote:
> **minIO on OpenIndiana***
> 
> *MinIO is a Amazon S3 compatible ultrafast cloud service and supported
> by napp-it 19.12/ 20.x as a filesystem property. It is included in the
> OmniOS extra repository. From first tests, the OmniOS binaries are
> working on OpenIndiana and Solaris,
> https://www.napp-it.org/doc/downloads/minio.zip
> 
> Copy the /opt/* files to /opt/ and set the binaries for minio, minio
> client and rclone to executable
> more,
> https://forums.servethehome.com/index.php?threads/amazon-s3-compatible-zfs-cloud-with-minio.27524/
> 
> ___
> 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] Setting static IP after OpenIndiana boot

[Till Wegmüller]

Hi

Yes, You are reading the wrong documentation. Solaris and illumos have
diverged significantly since 2010.

Have a look at the OpenIndiana documentation instead

http://docs.openindiana.org/handbook/systems-administration

Greetings
Till
On 26.03.20 17:51, Nicholas Papadonis wrote:
> Hi Folks,
> 
> Is this a known issue or am I reading the wrong documentation?
> 
> Thanks
> 
>> On Mar 25, 2020, at 3:59 PM, Nicholas Papadonis 
>>  wrote:
>>
>> I installed OpenIndiana and am trying to configure a static IP.  I try to 
>> delete the address to follow the procedure for a static ip, however this 
>> action does not work.
>>
>> Any guidance appreciated.  Thanks
>>
>> $ ipadm show-addr
>> ADDROBJ   TYPE STATEADDR
>> lo0/v4static   ok   127.0.0.1/8 
>> e1000g0/_bdhcp ok   10.0.2.15/24 
>> e1000g1/_bdhcp ok   192.168.56.102/24 
>> 
>> lo0/v6static   ok   ::1/128
>> e1000g0/_aaddrconf ok   fe80::a00:27ff:fefc:14ce/10
>> e1000g1/_aaddrconf ok   fe80::a00:27ff:fea4:1a43/10
>>
>> $ sudo ipadm delete-addr e1000g1/_b
>>
>> $ sudo ipadm show-addr
>> ADDROBJ   TYPE STATEADDR
>> lo0/v4static   ok   127.0.0.1/8 
>> e1000g0/_bdhcp ok   10.0.2.15/24 
>> e1000g1/_bdhcp ok   192.168.56.102/24 
>> 
>> lo0/v6static   ok   ::1/128
>> e1000g0/_aaddrconf ok   fe80::a00:27ff:fefc:14ce/10
>> e1000g1/_aaddrconf ok   fe80::a00:27ff:fea4:1a43/10
>>
>> $ sudo ipadm down-addr e1000g1/_b
>> ipadm: Could not mark the address down: Persistent operation on temporary 
>> object
>>
>> I'm reading:
>> https://docs.oracle.com/cd/E23824_01/html/821-1458/gjwiq.html 
>> 
>>
>>
>>
> 
> ___
> 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] Setting static IP after OpenIndiana boot

[Till Wegmüller]

Hi you defined dhcp in the Installation wizzard I guess?

In that case the application network automagic is managing the ip
addresses not ipadm commands. You will have to disable the nwam service
first.

use svcadm disable svc:/network/physical:nwam

All entries will then disapear aswell.
Than you can create a static ip with
ipadm create-addr -T static -a a.b.c.d/24 e1000g1/v4

Hope this helps
Greetings
Till
On 25.03.20 20:59, Nicholas Papadonis wrote:
> I installed OpenIndiana and am trying to configure a static IP.  I try to
> delete the address to follow the procedure for a static ip, however this
> action does not work.
> 
> Any guidance appreciated.  Thanks
> 
> $ ipadm show-addr
> ADDROBJ   TYPE STATEADDR
> lo0/v4static   ok   127.0.0.1/8
> e1000g0/_bdhcp ok   10.0.2.15/24
> e1000g1/_bdhcp ok   192.168.56.102/24
> lo0/v6static   ok   ::1/128
> e1000g0/_aaddrconf ok   fe80::a00:27ff:fefc:14ce/10
> e1000g1/_aaddrconf ok   fe80::a00:27ff:fea4:1a43/10
> 
> $ sudo ipadm delete-addr e1000g1/_b
> 
> $ sudo ipadm show-addr
> ADDROBJ   TYPE STATEADDR
> lo0/v4static   ok   127.0.0.1/8
> e1000g0/_bdhcp ok   10.0.2.15/24
> e1000g1/_bdhcp ok   192.168.56.102/24
> lo0/v6static   ok   ::1/128
> e1000g0/_aaddrconf ok   fe80::a00:27ff:fefc:14ce/10
> e1000g1/_aaddrconf ok   fe80::a00:27ff:fea4:1a43/10
> 
> $ sudo ipadm down-addr e1000g1/_b
> ipadm: Could not mark the address down: Persistent operation on temporary
> object
> 
> I'm reading:
> https://docs.oracle.com/cd/E23824_01/html/821-1458/gjwiq.html
> ___
> 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] Components to check/fix before 2020.04

[Till Wegmüller]

On 18.03.20 19:22, Aurélien Larcher wrote:
> 
> You could probably update to http://pkg.openindiana.org/gcc-next/ in a
> BE but be aware that OpenGL does not work correctly on Intel currently
> with this repo (I need to fix drm and mesa).

Turns out I did it wrong. I needed to override the GCC_VERSION in
shared-macros. Now I managed to build clang with gcc-7. After
republishing clang rust worked. We don't have much rust software we can
compile right now but I can send in my rust PR :) We now have 1.40.
Firefox is next.

Greetings
Till

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

Re: [OpenIndiana-discuss] Components to check/fix before 2020.04

[Till Wegmüller]

On 18.03.20 10:53, Aurélien Larcher wrote:
> I have not done anything special but I am on a system entirely built
> with gcc-7...
> 
> Passing GCC_VERSION=7 should be enough to set all the required variables.
> 

And it did not work for me... Clang 9 is installed from locally
published package I checked...

ldd /usr/clang/9.0/lib/libLLVM-9.so
libedit.so.0 =>  /usr/lib/64/libedit.so.0
libz.so.1 => /usr/lib/64/libz.so.1
libdl.so.1 =>/lib/64/libdl.so.1
libcurses.so.1 =>/lib/64/libcurses.so.1
libstdc++.so.6 =>/usr/gcc/6/lib/amd64/libstdc++.so.6
libm.so.2 => /lib/64/libm.so.2
librt.so.1 =>/lib/64/librt.so.1
libgcc_s.so.1 => /usr/gcc/6/lib/amd64/libgcc_s.so.1
libc.so.1 => /lib/64/libc.so.1


I guess I have to wait for GCC to hit the release before I can continue
with rust 140...

Greetings
Till

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

Re: [OpenIndiana-discuss] Components to check/fix before 2020.04

[Till Wegmüller]

On 18.03.20 10:53, Aurélien Larcher wrote:
> 
> I have not done anything special but I am on a system entirely built
> with gcc-7...
> 
> Passing GCC_VERSION=7 should be enough to set all the required variables.


Ah I did not know this trick. I'll try that then :) thanks.

--Till

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

Re: [OpenIndiana-discuss] Components to check/fix before 2020.04

[Till Wegmüller]

On 18.03.20 10:43, Aurélien Larcher wrote:
> Hi Till,
> did you republish clang-9 with gcc-7 as compiler?
> Maybe this has changed in newer libraries but rpath to runtime libraries
> was hardcoded in clang to the compiler used to build clang itself.
> On my machine everything is linked to gcc-7.
> Kind regards,
> 
> Aurélien

That is what I tried to but I could not get clang to build with gcc-7.
Is there a trick to doing that? It would help me finish up rust faster
if I knew how to tell oi-userland which compiler to use :) otherwise
I'll have to wait for the gcc-7 work.

Greetings
Till

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

Re: [OpenIndiana-discuss] Components to check/fix before 2020.04

[Till Wegmüller]

Hey Aurelian

I was Compiling rust yesterday and found that it works except for the
problem that rust wants to link against gcc7 runtime and clang keeps
linking against gcc6 runtime. Did you have any problems linking clang
against gcc7 runtime? Do I need to setup your branch to be able to do
that? Note that I only noticed with ldd on /usr/bin/clang-9. Did your
gcc7 build of clang linkt to gcc7 runtime sucessfully or did it silently
link against gcc6 like mine did?

Greetings
Till

On 17.03.20 19:33, Aurélien Larcher wrote:
> On Tue, Mar 17, 2020 at 8:25 PM Alexander Pyhalov via openindiana-discuss <
> openindiana-discuss@openindiana.org> wrote:
> 
>> openindiana/illumos-closed publishes here.
>> What's wrong with openindiana/pkg (works here with GCC_VERSION=7)?
>>
> 
> For some reason env-prep failed and the zone headers were missing, false
> alarm...
> 
> 
>>
>> It seems https://github.com/OpenIndiana/slim_source/pull/63 is enough to
>> fix slim_source.
>>
> 
> Great! thank you!
> 
>>
>> С уважением,
>> Александр Пыхалов,
>> программист отдела телекоммуникационной инфраструктуры
>> управления информационно-коммуникационной инфраструктуры ЮФУ
>>
>>
>> 
>> От: Aurélien Larcher 
>> Отправлено: 17 марта 2020 г. 20:46
>> Кому: Discussion list for OpenIndiana
>> Тема: Re: [OpenIndiana-discuss] Components to check/fix before 2020.04
>>
>> So... right now the list narrows down to:
>>
>> database/mongodb-40
>> openindiana/illumos-closed
>> openindiana/pkg
>> openindiana/qemu-kvm (work in progress)
>> openindiana/slim_source
>>
>> everything else is published with gcc-7
>>
>> On Tue, Mar 17, 2020 at 3:17 PM Aurélien Larcher <
>> aurelien.larc...@gmail.com>
>> wrote:
>>
>>> cluster/pcs also requires self to be already installed as it relies on
>>> ruby gems that can only be installed by root.
>>> One would need to patch the build system to install to the proto
>> directory.
>>>
>>> On Tue, Mar 17, 2020 at 2:37 PM Aurélien Larcher <
>>> aurelien.larc...@gmail.com> wrote:
>>>

 I have now fixed the following components:

 python/netifaces
> python/psutil
> sysutils/sysstat
>

 and I have bumped

> web/icedtea-web
>

 although an issue remains with password handling...

 The problem with runtime/sbcl and multimedia/totem was that they need to
 be already installed on the system to publish correctly.

 --
 ---
 Praise the Caffeine embeddings

>>>
>>>
>>> --
>>> ---
>>> Praise the Caffeine embeddings
>>>
>>
>>
>> --
>> ---
>> 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
>>
> 
> 

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

Re: [OpenIndiana-discuss] /hipster: Problem installing golang in Zone

[Till Wegmüller]

The Problem is zlogin explicitly sets LANG=C

Otherwise it can be set in /etc/default/init which works well with ssh.

Greetings
Till
On 27.02.20 16:48, Predrag Zecevic - Unix Systems Administrator wrote:
> On 02/27/20 16:43, Till Wegmüller wrote:
>> Hi
>>
>> The Problem is that you Zone doe not use a UTF-8 locale. It will be the
>> same with any package that includes files with non ASCII characters.
>> This has popped up some months ago already. And is expected although
>> IMHO stupid behaviour of Python3 (And Ruby and Perl for that matter)
>>
>> The fix is simple. Always run "export LANG="en_US.UTF-8" before you
>> install packages.
>>
>>
>> Greetings
>> Till
> Hi Till,
> 
> Yes! That has "fixed" it. I am not sure where this info has to be
> published or even added to skeleton files...
> 
> Regards.
> 
>>
>> On 27.02.20 16:39, Predrag Zecevic - Unix Systems Administrator wrote:
>>> On 02/27/20 16:34, Predrag Zecevic - Unix Systems Administrator wrote:
>>>> Hi all,
>>>>
>>>> I have tried to install golang in /hipster (updated today) zone:
>>>>
>>>> :; pfexec pkg install developer/golang-112
>>>>  Packages to install:  1
>>>>  Mediators to change:  1
>>>>  Create boot environment: No
>>>> Create backup boot environment: No
>>>>
>>>> DOWNLOAD    PKGS FILES    XFER
>>>> (MB)   SPEED
>>>> Completed    1/1 9101/9101
>>>> 139.7/139.7  --
>>>>
>>>> PHASE  ITEMS
>>>> Installing new actions 7693/9117Action install
>>>> failed for
>>>> 'usr/lib/golang/1.12/test/fixedbugs/issue27836.dir/\xc4foo.go'
>>>> (pkg://openindiana.org/developer/golang-112):
>>>>     UnicodeEncodeError: 'ascii' codec can't encode character '\xc4' in
>>>> position 51: ordinal not in range(128)
>>>>
>>>> The Boot Environment zbe-263 failed to be updated. A snapshot was
>>>> taken before the failed attempt and is mounted here /tmp/tmpvfqi85fv.
>>>> Use 'beadm unmount zbe-264' and then 'beadm activate zbe-264' if you
>>>> wish to boot to this BE.
>>>> pkg: An unexpected error happened during install: 'ascii' codec can't
>>>> encode character '\xc4' in position 51: ordinal not in range(128)
>>>>
>>>>
>>>> GZ runs:
>>>> :; uname -rosv
>>>> SunOS 5.11 illumos-d4990cfc1b illumos
>>>>
>>>> :; pkg info developer/golang-112
>>>>    Name: developer/golang-112
>>>>     Summary: The Go Programming Language
>>>>    Category: Development/Other Languages
>>>>   State: Installed
>>>>   Publisher: openindiana.org
>>>>     Version: 1.12.13
>>>>  Branch: 2019.0.0.0
>>>>  Packaging Date: Thu Nov 21 07:39:50 2019
>>>> Last Install Time: Fri Sep 20 06:42:02 2019
>>>>    Last Update Time: Mon Nov 25 09:13:23 2019
>>>>    Size: 385.77 MB
>>>>    FMRI:
>>>> pkg://openindiana.org/developer/golang-112@1.12.13-2019.0.0.0:20191121T073950Z
>>>>
>>>>
>>>>     Project URL: https://golang.org/
>>>>  Source URL:
>>>> https://storage.googleapis.com/golang/go1.12.13.src.tar.gz
>>>>
>>>>
>>>> I am asking here first, maybe solution is simple?
>>>>
>>>> Regards.
>>>
>>> FYI: same problem with golang-113:
>>> ...
>>>
>>> Action install failed for
>>> 'usr/lib/golang/1.13/test/fixedbugs/issue27836.dir/\xc4foo.go'
>>> (pkg://openindiana.org/developer/golang-113):
>>>    UnicodeEncodeError: 'ascii' codec can't encode character '\xc4' in
>>> position 51: ordinal not in range(128)
>>> ...
>>>
>>> Regards.
>>>
>>> P.S: I see golang-114 is coming...
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
> 

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

Re: [OpenIndiana-discuss] /hipster: Problem installing golang in Zone

[Till Wegmüller]

Hi

The Problem is that you Zone doe not use a UTF-8 locale. It will be the
same with any package that includes files with non ASCII characters.
This has popped up some months ago already. And is expected although
IMHO stupid behaviour of Python3 (And Ruby and Perl for that matter)

The fix is simple. Always run "export LANG="en_US.UTF-8" before you
install packages.


Greetings
Till

On 27.02.20 16:39, Predrag Zecevic - Unix Systems Administrator wrote:
> On 02/27/20 16:34, Predrag Zecevic - Unix Systems Administrator wrote:
>> Hi all,
>>
>> I have tried to install golang in /hipster (updated today) zone:
>>
>> :; pfexec pkg install developer/golang-112
>>     Packages to install:  1
>>     Mediators to change:  1
>>     Create boot environment: No
>> Create backup boot environment: No
>>
>> DOWNLOAD    PKGS FILES    XFER
>> (MB)   SPEED
>> Completed    1/1 9101/9101 
>> 139.7/139.7  --
>>
>> PHASE  ITEMS
>> Installing new actions 7693/9117Action install
>> failed for
>> 'usr/lib/golang/1.12/test/fixedbugs/issue27836.dir/\xc4foo.go'
>> (pkg://openindiana.org/developer/golang-112):
>>    UnicodeEncodeError: 'ascii' codec can't encode character '\xc4' in
>> position 51: ordinal not in range(128)
>>
>> The Boot Environment zbe-263 failed to be updated. A snapshot was
>> taken before the failed attempt and is mounted here /tmp/tmpvfqi85fv.
>> Use 'beadm unmount zbe-264' and then 'beadm activate zbe-264' if you
>> wish to boot to this BE.
>> pkg: An unexpected error happened during install: 'ascii' codec can't
>> encode character '\xc4' in position 51: ordinal not in range(128)
>>
>>
>> GZ runs:
>> :; uname -rosv
>> SunOS 5.11 illumos-d4990cfc1b illumos
>>
>> :; pkg info developer/golang-112
>>   Name: developer/golang-112
>>    Summary: The Go Programming Language
>>   Category: Development/Other Languages
>>  State: Installed
>>  Publisher: openindiana.org
>>    Version: 1.12.13
>>     Branch: 2019.0.0.0
>>     Packaging Date: Thu Nov 21 07:39:50 2019
>> Last Install Time: Fri Sep 20 06:42:02 2019
>>   Last Update Time: Mon Nov 25 09:13:23 2019
>>   Size: 385.77 MB
>>   FMRI:
>> pkg://openindiana.org/developer/golang-112@1.12.13-2019.0.0.0:20191121T073950Z
>>
>>    Project URL: https://golang.org/
>>     Source URL:
>> https://storage.googleapis.com/golang/go1.12.13.src.tar.gz
>>
>>
>> I am asking here first, maybe solution is simple?
>>
>> Regards.
> 
> FYI: same problem with golang-113:
> ...
> 
> Action install failed for
> 'usr/lib/golang/1.13/test/fixedbugs/issue27836.dir/\xc4foo.go'
> (pkg://openindiana.org/developer/golang-113):
>   UnicodeEncodeError: 'ascii' codec can't encode character '\xc4' in
> position 51: ordinal not in range(128)
> ...
> 
> Regards.
> 
> P.S: I see golang-114 is coming...

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

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

[Till Wegmüller]

Remote Display is the only thing that works inside zones. By definition
any app that runs in a zone does remote display. Mostly over unix
socket. DRI and KMS is based on shared memory as PÁSZTOR correctly
assumed. Desktops like KDE depend on the Speed of that to work these days.

-- 
Till

On 2020-02-18 21:51, Bob Friesenhahn wrote:
> On Tue, 18 Feb 2020, PÁSZTOR György wrote:
>>
>> Btw.: What is the situation with joyent's pkgsrc repo?
>> I never checked but If memory serves well I read about that on this list,
>> that one used pkgsrc repo + omnios to have some decent-recent gui.
>> Maybe not kde, which needed linux-specific drm/kms interface.
> 
> I use pkgsrc under OmniOS to serve as an X11 development environment for
> GraphicsMagick.  I have not observed any problems.  I only do remote
> display though without some fancy desktop.
> 
> Bob

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

Re: [OpenIndiana-discuss] node/npm question(s)

[Till Wegmüller]

On 09.02.20 16:32, Michal Nowak via openindiana-discuss wrote:
> I am afraid we don't have any other tiling terminal at this moment...


Well we do have tmux. That is in all intents and purposes a tiling
terminal (window) manager.

Greetings
Till

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

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

[Till Wegmüller]

Hi Mark


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

Greetings
Till

On 05.02.20 05:57, Mark Kosmowski wrote:
> Is it possible to run X applications from within an lx zone?
> 
> If so, would it work for the global zone to run the X server and the lx
> zone to provide plasma/KDE?
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

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

Re: [OpenIndiana-discuss] node/npm question(s)

[Till Wegmüller]

Hi Predrag

I assume you are running this inside a Zone via zlogin?

We had a bug a few months ago. Basicaly bash gets a SIGHUP from the
process and quits.

We fixed this bug some time ago. You can also work around it by
connecting to the zone via ssh. It will keep the shell running.

If this does not work let us know. It might be another signal missfire.

Hope this helps
Greetings
Till

On 31.01.20 13:54, Predrag Zecevic - Unix Systems Administrator wrote:
> Hi all,
> 
> I have strange feeling that something is wrong with nodejs. I have
> installed:
> :; pkg list | grep nodejs
> runtime/nodejs    0.12.18-2018.0.0.2    
> i--
> runtime/nodejs-10 10.18.1-2019.0.0.0    
> i--
> runtime/nodejs-12 12.14.1-2019.0.0.0    
> i--
> runtime/nodejs-6  6.17.1-2018.0.0.0     i--
> runtime/nodejs-8  8.17.0-2019.0.0.0     i--
> 
> Default is:
> :; pkg mediator nodejs
> MEDIATOR    VER. SRC. VERSION IMPL. SRC. IMPLEMENTATION
> nodejs  system    12  system
> 
> This command works:
> :; node --version
> v12.14.1
> 
> But this exists terminal (and works fine on Linux):
> :; npm ---version # same is true for 'npm version' command
> 
> When I call it like this, it works:
> :; npm --version |& tee
> 6.13.4
> 
> Am I doing something wrong here?
> 
> Regards.
> 
> P.S:
> :; npm init  # worked fine
> :; npm install xterm # from https://xtermjs.org/ - has finished
> installation, but then exited terminal - very annoying
> 

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

Re: [OpenIndiana-discuss] Meaning of `list list' header columns particularly REFER

[Till Wegmüller]

I can't remember where I learned it but I know what they mean.

I think all if from the zfs man page.

Refer is short for Blocks referenced. It shows the size of the
Filesystem table at that the Snapshot or Dataset References. Even if the
Blocks on disk are not related to that snapshot. Usefull when restoring
a clone via rsync from a snapshot for a testing database for example. So
you know how much space the clone will consume. Used refers to the
Blocks the Snapshot or Dataset uses on Disk. It is what is really eating
your diskspace if you run out of it.


Greetings
Till

On 25.12.19 17:58, Harry Putnam wrote:
> "Richard L. Hamilton"  writes:
> 
>> https://docs.oracle.com/cd/E19253-01/819-5461/gazss/index.html
>> 
>> appears to have a brief description of ALL of the space related
>> properties of zfs. Also see
>> https://docs.oracle.com/cd/E19253-01/819-5461/gcfgz/index.html
>>  which
>> gives more detail of what makes up "used".
> 
> Well, it covers a bit of it... but pretty weak all in all, far as a
> full description of what each field really means
> 
> Thanks much for putting in the legwork.
> 
> 
> ___
> 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] Might have jumped too soon with damaged rpool

[Till Wegmüller]

Hi James

Yes these points I missed thanks for adding.


Greetings
Till
On 18.12.19 13:05, James wrote:
> On 18/12/2019 10:47, Till Wegmüller wrote:
> 
>> 1. Buy or Organize a new Disk with the same RPM and the same or Bigger
>> Capacity. If your current disk is not sold anymore then just focus on a
>> brand you trust with the same RPM and bigger Capacity. If the new disk
>> is bigger than c5d1 then any excess will simply not be addressable by
>> ZFS. Which is not be an issue if it is just a couple of GB. If you wish
>> to have two new disks as you final configuration then just grab any two
>> disks you like or even SSD's. The main assumption is of course that any
>> disk you pick fits your physical Plugs.
> 
> I thought the sector size should match else it causes a performance
> problem.
> 
> Harry, test with:
> $ zdb -C | grep ashift
> 
> and expect either 512 or 4096; new HDDs are typically 4096.  Check
> before we worry what to do about it.
> 
> 
> 
>> 8. Issue "zpool set autoexpand=on rpool"
> 
> 9. After expansion issue "zpool set autoexpand=off rpool" and restore
> the default value for the future.
> 
> 10. Make bootable:
> # installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/$NEWDEVICE
> 
> 
> 
> 
> 
> ___
> 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] Might have jumped too soon with damaged rpool

[Till Wegmüller]

Hi Harry

In the situation you are in there is nothing you can do anymore for that
one disk. It's gone. You'll need a new one.

That said thanks to ZFS all your data is still there and you can get
into a clean state very easily.

1. Buy or Organize a new Disk with the same RPM and the same or Bigger
Capacity. If your current disk is not sold anymore then just focus on a
brand you trust with the same RPM and bigger Capacity. If the new disk
is bigger than c5d1 then any excess will simply not be addressable by
ZFS. Which is not be an issue if it is just a couple of GB. If you wish
to have two new disks as you final configuration then just grab any two
disks you like or even SSD's. The main assumption is of course that any
disk you pick fits your physical Plugs.

2. Insert the new disk in place where c5d0 was.
3. Issue "zpool replace rpool c5d0s0"
4. Wait until done.

If you wish to also renew c5d1 with a new model you would continue as
follows. If not ignore the steps below:

5. Issue "zpool offline rpool c5d1" and pull the disk
6. Insert new disk in place of c5d1 and Issue "zpool replace rpool c5d1"
7. Wait for completion
8. Issue "zpool set autoexpand=on rpool"

Now you have a pool on two new disks exanded to the max capacity.

Pro tip: Always buy an extra disk and store it on a shelf inside it's
protective bag. That way you can quickly replace the drive without
having to worry about getting new ones.


Hope this helps
Greetings
Till
On 18.12.19 10:29, Harry Putnam wrote:
> Running quite an old version of hipster
> 
>SunOS 2x 5.11 illumos-a356818ef9 i86pc i386 i86pc
> 
> I have a setup so shaky I've been afraid to try update to current
> hipster.  But that is not the subject of this post:
> 
> I found this message on rpool
> 
> ,
> | root # zpool status rpool
> |   pool: rpool
> |  state: DEGRADED
> | status: One or more devices are faulted in response to persistent errors.
> | Sufficient replicas exist for the pool to continue functioning in a
> | degraded state.
> | action: Replace the faulted device, or use 'zpool clear' to mark the device
> | repaired.
> |   scan: scrub repaired 0 in 1h18m with 0 errors on Mon Jan  8 18:38:42 2018
> | config:
> | 
> | NAMESTATE READ WRITE CKSUM
> | rpool   DEGRADED 0 0 0
> |   mirror-0  DEGRADED 0 0 0
> | c5d0s0  FAULTED  0 0 0  too many errors
> | c5d1ONLINE   0 0 0
> `
> 
> As you see, this status was taken after completing a scrub attempting
> to correct the problems
> 
> You see the result of the scrub was goose eggs
> 
> I also tried the `zpool clear' recommended in status report above.
> 
> That failed to clear the problem.
> 
> I decided to detached the bad disk (c5d0s0), thinking there was some repair
> possibilities  working on the disk by itself... and soon discovered I
> didn't really have a clue how proceed.
> 
> Googling turned up a good bit about working on s pool, but having trouble
> finding what I can do to the detached disk to fix it.
> 
> Can anyone offer a way to proceed?
> 
> 
> ___
> 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] Problem with VirtualBox

[Till Wegmüller]

Hi Stephan

If I google the Hex Code on the VirtualBox sites I get a Virtual
Networking related error. The Topic in the Forums at [0] suggest to boot
the VM's without network cards once and then try again with a network
card. In any case this seems network related but maybe somehow different
to the mentioned one.


Another thing that I would check is if the vboxnet driver and the
VirtualBox Package are installed in the same version. We had problems
generating incorporations some Weeks ago this might come have an impact
on you. If they don't match try to update with incorporation and once
just installing all VirtualBox packages suffixed with @latest to force
pkg to error if the latest can not be installed.

Hope this helps
Greetings
Till

[0] https://forums.virtualbox.org/viewtopic.php?t=33196
On 24.11.19 11:01, Stephan Althaus wrote:
> Hello!
> 
> What i did test so far:
> a) Remove ~/.config/VirtualBox, start GUI, create new machine, start -
> same Error
> b) uninstall virtualbox package, reboot, install package - same error
> 
> The user is in the vbpusers group
> $ groups
> lp sys staff vboxuser family
> 
> The tail of the dtrace is
> $ sudo dtrace -n 'syscall::open*:entry { printf("%s
> %s",execname,copyinstr(arg0)); }'|grep -i box
> 0  18427   open:entry VirtualBoxVM
> /opt/VirtualBox/amd64/VBoxNetDHCP.so
>   0  18427   open:entry VirtualBoxVM
> /opt/VirtualBox/amd64/VBoxNetNAT
>   0  18427   open:entry VirtualBoxVM
> /opt/VirtualBox/amd64/VBoxNetNAT.so
>   0  18427   open:entry VirtualBoxVM /dev/null
>   0  18427   open:entry VirtualBoxVM /dev/null
>   0  18427   open:entry VirtualBoxVM /dev/null
>   0  18427   open:entry VirtualBoxVM /dev/null
>   0  18427   open:entry VirtualBoxVM
> /devices/pseudo/vboxdrv@0:vboxdrv
>   2  18427   open:entry VBoxSVC
> /devices/pseudo/devinfo@0:devinfo
> 
> 
> hmm...(???)
> 
> 
> 
> 
> On 11/23/19 16:38, Stephan Althaus wrote:
>> Hello!
>>
>> I suddenly have some problem with virtualbox,
>> id did run well before, and i don't know what i did to ..
>>
>> i did a pkg update just *now*
>>
>> The error was there *before* this update,
>> this was done just to be sure..
>>
>> Error is
>>
>> $ VBoxManage startvm aLinux
>> Waiting for VM "aLinux" to power on...
>> VBoxManage: error: The virtual machine 'aLinux' has terminated
>> unexpectedly during startup with exit code 1 (0x1)
>> VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
>> component MachineWrap, interface IMachine
>>
>> Something got wrong, i don't know what..
>>
>> $ svcs -a|grep virt
>> disabled   15:50:12 svc:/application/virtualbox/balloonctrl:default
>> disabled   15:50:12 svc:/application/virtualbox/autostart:default
>> disabled   15:50:12 svc:/application/virtualbox/webservice:default
>> disabled   15:50:13 svc:/application/virtualbox/zoneaccess:default
>> online 15:50:30 svc:/application/virtualbox/run-once:default
>>
>> $ modinfo|grep vb
>> 239 f93c8000  588e8 304   1  vboxdrv (VirtualBox HostDrv
>> 6.0.14r13205)
>> 240 f93be000   77d8 305   1  vboxflt (VirtualBox NetDrv
>> 6.0.14r132055)
>> 240 f93be000   77d8   -   1  vboxflt (VirtualBox NetMod
>> 6.0.14r132055)
>> 241 f8e425a8    d08 306   1  vboxnet (VirtualBox NetAdp
>> 6.0.14r132055)
>> 245 f8ef5e28   48d8 308   1  vboxusbmon (VirtualBox USBMon
>> 6.0.14r132055
>>
>> pkg verify pkg:/system/virtualbox
>> showed nothing.
>>
>> What else could i check?
>>
>> Any hints are welcome!
>>
>> Thanks,
>>
>> Stephan
>>
>>
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss

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

Re: [OpenIndiana-discuss] New laptop compatibility? System76?

[Till Wegmüller]

Hi Leonard

You will most probably get it working but wifi is an unknown. It claims
to be an Intel Card. But we do not have many drivers linux has.
Especially wifi ones.

Greetings
Till

On 17.11.19 18:27, Leonard Sitongia wrote:
> Hi,
> 
> I’m wondering if new laptops that are available now and run Linux are likely 
> to be compatible with OI? In particular, I’m looking at the latest System76 
> Galago Pro. I don’t know the specs for the graphics and wifi. I see a couple 
> of older System76 laptops on the hardware list. I wonder about their latest 
> offerings.
> 
> Thanks!
> ==Leonard Sitongia
> 
> 
> 
> 
> ___
> 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] Bluetooth mouse?

[Till Wegmüller]

Unfortunately no.

We lack Bluetooth completely. Wireless mouse can only be used by using
proprietary dongles like Logitech which hide the Wireless part.

Greetings
Till

On 10.11.19 20:08, L Sitongia wrote:
> Is there hope for support for this Bluetooth dongle?
> 
> Nov 10 11:45:59 nuc usba: [ID 349649 kern.info] usba:   no driver found
> for interface 0 (nodename: 'interface') of Broadcom Corp BCM20702A0
> BC14EF638498
> 
> I see an illumos gate but report about this,
> https://www.illumos.org/issues/2267
> 
> Thank you.
> 

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

Re: [OpenIndiana-discuss] OpenIndiana Hipster 2019.10

[Till Wegmüller]

You always need to reboot.

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

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

The IO error you are getting points to either a defect Hardware or
Connection problems. Can you run "curl -iv http://pkg.openindiana.org; ?

That should give you more information what is not working.

Greetings
Till

On 10.11.19 19:55, L Sitongia wrote:
> 
> 
> On 11/10/19 12:44 AM, Andreas Wacknitz wrote:
>>
>> Am 10.11.2019 um 03:21 schrieb L Sitongia:
>>> On 11/07/19 05:47 AM, Alexander Pyhalov via openindiana-discuss wrote:
 Hi.

 OpenIndiana Hipster 2019.10 snapshot is ready.


>>>
>>> Thank you.
>>>
>>> Sorry to be clueless, but how do I upgrade to this? I'm running
>>> 2019.04 on an older Intel NUC. I periodically run "pfexec pkg
>>> image-update", but apparently that does not do a major upgrade like
>>> I'm looking for. Do I download an installer USB/DVD and it will
>>> upgrade the boot environment that I'm running now? I don't see
>>> information about this in the Documentation, Wiki or the searchable
>>> list at Mail Archive.
>>>
>> Hipster is a rolling release. You don't need to install from USB/DVD
>> again. What you only need to do is "pfexec pkg update" (or "pkg update
>> -nv" for a dry-run (-n) and more verbose information (-v)).
>> This will typically create a new boot environment which needs to be
>> activated by a reboot initiated by"pfexec init 6".
> 
> Also, it does look like the image-update updated the system, because I
> now see
> 
> root@nuc:~# cat /etc/release
>  OpenIndiana Hipster 2019.10 (powered by illumos)
> 
> After I ran image-update, it still said 2019.04, but after rebooting, I
> now see this.
> 

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

Re: [OpenIndiana-discuss] 20190511 gui/text boot fails on Dell R710 II

[Till Wegmüller]

Thanks for the info.

When Talking with tsoome he mentioned that some Firmaware might not be
that inteligent when Updating boot options and Instead rely on the OS to
instruct them what to boot from UEFI.

We currently lack the framework to set these variables from the os.

So It might be as simple as only needing to update the Boot Options in
the BIOS settings of UEFI boot mode.

Greetings
Till
On 08.11.19 21:38, Jedi Tek'Unum wrote:
> All comments here are relative to 20191106…
> 
> On Nov 7, 2019, at 1:30 PM, Till Wegmüller  wrote:
>>
>> Cool so something was better this time round with the media
>>
>> I talked to the developer of loader tsoome (cc'd as he is not on this
>> list) today.
>>
>> Basically the situation you where experiencing with loader and the text
>> image can only happen if the system is returning reads with one of
>> following codes: result == 0x20 || result == 0x31 || result == 0x80 - we
>> do not print error messages on those.
>> 0x20 is controller failure, 31 and 80 are no media in drive
>>
>> If the system is reporting read errors, only thing loader can do is to
>> reset the controller and try again - the biosdisk.c does 3 attempts
>> there (except for those 3 errors).
>>
>> What you could try is booting via UEFI mode and see if that works.
> 
> Good news and bad news.
> 
> All 3, minimal, text, and gui will boot from Virtual CD using UEFI.
> 
> However, after installing from each, none of the installations will boot 
> using UEFI (“No boot device available.” error). BUT, they will boot after 
> going back to BIOS mode.
> 
>> My guess is that Dell broke something in the old Bios Bootloader code.
>>
>> The new error you are getting from the gui image could also be a read error.
>>
>> Could you post the output of lsdev from the ok prompt?
> 
> This is from the gui failure booting from Virtual CD using BIOS mode.
> 
> fd devices:
>   fd0:BIOS drive A (2880 X 512):
>   fd1:BIOS drive B (2880 X 512):
> cd devices:
>   cd0:BIOS drive H (348160 X 2048):
> disk devices:
>   disk0:  BIOS drive C (976773168 X 512):
> disk0s1: Solaris 2
>   disk0s1a: root
>   disk0s1i: boot
>   disk1:  BIOS drive D (1 X 512):
>   disk2:  BIOS drive E (286749480 X 512):
>   disk3:  BIOS drive F (976773168 X 512):
>   disk4:  BIOS drive G (286749480 X 512):
> zfs devices:
>   zfs:rpool
> 
>> I am curious if loader is able to see the VirtualCD drive.
>>
>> Greetings
>> Till
>> On 07.11.19 19:34, Jedi Tek'Unum wrote:
>>> OI-hipster-minimal-20191106.iso works
>>>
>>> OI-hipster-text-20191106.iso works! This is a change from 20190511. I went 
>>> back and tried 20190511 again and it still fails.
>>>
>>> OI-hipster-gui-20191106.iso fails as before with
>>>
>>> loading CORE EXT words
>>> loading SEARCH & SEARCH-EXT words
>>> loading Johns-Hopkins locals
>>> loading MARKER  
>>> loading ficl O-O extensions
>>> loading ficl utility classes
>>> loading ficl string classes
>>> \
>>> start not found
>>>
>>> Type ‘?’ for a list of commands, ‘help’ for more detailed help.
>>> ok
>>>
>>> ___
>>> openindiana-discuss mailing list
>>> openindiana-discuss@openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

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

Re: [OpenIndiana-discuss] 20190511 gui/text boot fails on Dell R710 II

[Till Wegmüller]

Cool so something was better this time round with the media

I talked to the developer of loader tsoome (cc'd as he is not on this
list) today.

Basically the situation you where experiencing with loader and the text
image can only happen if the system is returning reads with one of
following codes: result == 0x20 || result == 0x31 || result == 0x80 - we
do not print error messages on those.
0x20 is controller failure, 31 and 80 are no media in drive

If the system is reporting read errors, only thing loader can do is to
reset the controller and try again - the biosdisk.c does 3 attempts
there (except for those 3 errors).

What you could try is booting via UEFI mode and see if that works.

My guess is that Dell broke something in the old Bios Bootloader code.

The new error you are getting from the gui image could also be a read error.

Could you post the output of lsdev from the ok prompt?

I am curious if loader is able to see the VirtualCD drive.

Greetings
Till
On 07.11.19 19:34, Jedi Tek'Unum wrote:
> OI-hipster-minimal-20191106.iso works
> 
> OI-hipster-text-20191106.iso works! This is a change from 20190511. I went 
> back and tried 20190511 again and it still fails.
> 
> OI-hipster-gui-20191106.iso fails as before with
> 
>   loading CORE EXT words
>   loading SEARCH & SEARCH-EXT words
>   loading Johns-Hopkins locals
>   loading MARKER  
>   loading ficl O-O extensions
>   loading ficl utility classes
>   loading ficl string classes
>   \
>   start not found
> 
>   Type ‘?’ for a list of commands, ‘help’ for more detailed help.
>   ok
> 
> ___
> 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] 20190511 gui/text boot fails on Dell R710 II

[Till Wegmüller]

Whoops. yep you are right i messed up month and day location. I copied
it from the PR on github and did not read properly in half sleep.

Sorry for the noise.

- Till
On 06.11.19 22:26, Tim Mooney wrote:
> In regard to: Re: [OpenIndiana-discuss] 20190511 gui/text boot fails on...:
> 
>> While not yet officially released, could you try
>> http://dlc.openindiana.org/isos/hipster/20190511/ ?
> 
> That's the link to the images from April/May, that we've been testing
> with.  If you have the link to the unreleased images from October 2019,
> I'll happily check them out.
> 
> Tim
> 
>> On 06.11.19 21:36, Jedi Tek'Unum wrote:
>>> On Nov 6, 2019, at 1:59 PM, Till Wegmüller  wrote:
>>>>
>>>> That is definetly the Bootloader.
>>>> I would like to know some more.
>>>>
>>>> Can the same server boot FreeBSD?
>>>> We use the same bootloader as FreeBSD. If it cannot we could check with
>>>> the FreeBSD people and tsoome why this happens. If FreeBSD can boot,
>>>> then something with our loader port is wrong or with the bootloader on
>>>> the ISO/Image.
>>>
>>> I just downloaded and booted FreeBSD-12.1-RELEASE-amd64-disc1.iso
>>> using Virtual CD without any issue. My bandwidth is rather poor (DSL)
>>> so I went with the smaller CD image. Hopefully Tim will try the dvd :)
>>>
>>> Dell R710-II
>>> BIOS 6.6.0
>>> iDRAC 6 firmware 2.92 build 05
>>>
>>> Note that OI-minimal does work.
>>>
>>>
>>> ___
>>> 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] 20190511 gui/text boot fails on Dell R710 II

[Till Wegmüller]

While not yet officially released, could you try
http://dlc.openindiana.org/isos/hipster/20190511/ ?

I am curious how the newest images hold up. Hopefully the loader error
was a thing only in 2019.04

Also OmniOSCE uses loader. Would be good to know if their image boots.
Because then it is definitely a problem with our images.

[0] https://omniosce.org/download.html

Greetings
Till

On 06.11.19 21:36, Jedi Tek'Unum wrote:
> On Nov 6, 2019, at 1:59 PM, Till Wegmüller  wrote:
>>
>> That is definetly the Bootloader.
>> I would like to know some more.
>>
>> Can the same server boot FreeBSD?
>> We use the same bootloader as FreeBSD. If it cannot we could check with
>> the FreeBSD people and tsoome why this happens. If FreeBSD can boot,
>> then something with our loader port is wrong or with the bootloader on
>> the ISO/Image.
> 
> I just downloaded and booted FreeBSD-12.1-RELEASE-amd64-disc1.iso using 
> Virtual CD without any issue. My bandwidth is rather poor (DSL) so I went 
> with the smaller CD image. Hopefully Tim will try the dvd :)
> 
> Dell R710-II
> BIOS 6.6.0
> iDRAC 6 firmware 2.92 build 05
> 
> Note that OI-minimal does work.
> 
> 
> ___
> 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