Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Carl Brewer]

On 5/10/2022 11:22 pm, Joshua M. Clulow via openindiana-discuss wrote:

On Wed, Oct 5, 2022, 00:28 david allan finch  wrote:


Not quite sure what has broken it but, I installed the latest version of
VirtualBox 6.1.38 and updated the client extension into my OpenIndiana
VM client (it was the last build 2021Oct from the ISO). Around the same
time I did a pkg update to the latest changes. Since then the Shared
Folders have not worked. (The host is a windows 11 box there was also an
microsoft update on that day which I initially wondered about).

On boot of the VM I now see undefined symbol 'removectx' and
'installctx' from /usr/kernel/drv/smd64/vboxguest.



I believe that's related to: https://www.illumos.org/issues/13917


The reference into VB's git seems to suggest that it was done in January?

https://github.com/omniosorg/omnios-extra/pull/921

I'm not seeing any issues with VB 6.1.38 on my OI servers, with a build 
from a week ago, but I'm not using shared folders at all.





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

Re: [OpenIndiana-discuss] mkdocs 1.4 op OpenIndiana

[s...@pandora.be]

- Op 4 okt 2022 om 16:15 schreef Marcel Telka mar...@telka.sk:

> All mkdocs packages are back and updated to their latest versions:

Good.  mkdocs is useful to have in the repository, I suppose.

Thanks for updating the mkdocs package because obviously the situation with 
python 2.7 was ugly,
I was using "pip install futures" to make the IPS package work.

Now it's packaged for python 3.7 and python 3.9 :

> # pkg list library/python/mkdocs{,-bootstrap,-bootswatch}
> NAME (PUBLISHER)  VERSION
> IFO
> library/python/mkdocs 1.4.0-2022.0.0.1   
> i--
> library/python/mkdocs-bootstrap   1.1-2022.0.0.0 
> i--
> library/python/mkdocs-bootswatch  1.1-2022.0.0.0 
> i--
> #
> 
> Please try and let me know if you find any problem.

For the moment I tested with "pip install mkdocs" and "pip install 
mkdocs-bootswatch" and as such,
mkdocs works with python 3.9 and renders the oi-docs.

http://docs.openindiana.org/contrib/getting-started/  explains how to submit 
updates to the documentation.

The getting-started guide actually clearly indicates that you have a choice to 
use either IPS (pkg install)
or "pip", because the guide indicates that most operating systems use "pip" and 
you can submit documentation updates from non-OpenIndiana systems.

For example the getting-started guide indicates that you can create a OI doc 
update on say, some other Unix-like system, and then use the pip install method 
on that other Unix-like system, preview the update there, and then submit the 
update ...

Regards,
David Stes

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

Re: [OpenIndiana-discuss] Net booting OI Hipster using iPXE

[Nikola M.]

On 9/22/22 17:59, Fox Martin wrote:

Apologies if this has been answered elsewhere, I searched long and hard and 
could not find what I really needed.
I have a working iPXE server with various Linux and Windows images served up 
over HTTP.


Hi, Maritn,
Have you take a look at this, (other distros)
https://wiki.smartos.org/pxe-booting-smartos/

Apparently nothing stops 
you from booting your desired OS or the whole production environment on 
top of hypervisor..




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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Joshua M. Clulow via openindiana-discuss]

On Wed, Oct 5, 2022, 00:28 david allan finch  wrote:

> Not quite sure what has broken it but, I installed the latest version of
> VirtualBox 6.1.38 and updated the client extension into my OpenIndiana
> VM client (it was the last build 2021Oct from the ISO). Around the same
> time I did a pkg update to the latest changes. Since then the Shared
> Folders have not worked. (The host is a windows 11 box there was also an
> microsoft update on that day which I initially wondered about).
>
> On boot of the VM I now see undefined symbol 'removectx' and
> 'installctx' from /usr/kernel/drv/smd64/vboxguest.
>

I believe that's related to: https://www.illumos.org/issues/13917


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

Re: [OpenIndiana-discuss] [oi-dev] FLAG-DAY: We started to obsolete python 2.7 and 3.5

[Aurélien Larcher]

On Tue, Oct 4, 2022 at 4:34 PM Marcel Telka  wrote:

> On Fri, Sep 30, 2022 at 07:16:18PM +0200, s...@pandora.be wrote:
> >
> > Part of the problem is, I think, that there is no maintainer any longer,
> as far as I know, for the mkdocs component in oi-userland.
> >
> > If someone knows how to build mkdocs with python 3 (which is perhaps
> possible, I don't know, I have no experience with building python
> components) then this would solve most of the problem, I think ...
> >
> > Thanks for your work on this, because as I confirmed, there are indeed
> really issues with the mkdocs python2.7.
> >
> > Several people related to the oi-docs are aware that we have a Python
> 2.7 problem, but we are unsure how to fix it, I think.
> >
> > For example in my Vagrantfile I have a comment about a missing 2.7
> 'futures' component:
> >
> >
> https://github.com/OpenIndiana/vagrantfiles/blob/main/oi-docs/Vagrantfile
> >
> >   # there used to be a futures package in the repo ...
> >   # library/python/futures seems to have a problem now
> > pfexec pkg install -v \
> >   git lynx links\
> >   library/python/futures \
> >   library/python/mkdocs \
> >   developer/documentation-tool/mdl
> >   # as of 21/9/2021 futures IPS is missing so install by pip
> >   pfexec pip install futures
> >
> > Because such "pip install" actions print a clear warning by Python that
> we are using an unsupported Python 2.7, it is clear that something must be
> done.
>
> The futures python package was obsoleted in May 2021 in OpenIndiana.
> The reason is, apparently, this - see https://pypi.org/project/futures/:
>
> It does not work on Python 3 due to Python 2 syntax being used in the
> codebase. Python 3 users should not attempt to install it, since the
> package is already included in the standard library.
>

Marcel is right, there were a few modules to ensure the transition from
Python 2 to Python 3 such as this one and other backport.* packages.
Migrating to Python 3 as default and obsoleting these transitional packages
should be enough.


>
>
> Regards.
>
> --
> +---+
> | Marcel Telka   e-mail:   mar...@telka.sk  |
> |homepage: http://telka.sk/ |
> +---+
>
> ___
> oi-dev mailing list
> oi-...@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] VirtualBox Client Extensions Broken

[david allan finch]

Hi,

Not quite sure what has broken it but, I installed the latest version of 
VirtualBox 6.1.38 and updated the client extension into my OpenIndiana 
VM client (it was the last build 2021Oct from the ISO). Around the same 
time I did a pkg update to the latest changes. Since then the Shared 
Folders have not worked. (The host is a windows 11 box there was also an 
microsoft update on that day which I initially wondered about).


On boot of the VM I now see undefined symbol 'removectx' and 
'installctx' from /usr/kernel/drv/smd64/vboxguest.


There is also after that a whole host of messages about vboxguest as it 
tries to start the service.


When I installed client extension there was an error message about 
vboxguest not installing correctly.


Anyone got any clues what I did wrong or intrested in the dmesg error or 
the output of the errors in the installing of the client extensions?




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