Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On Tue, Feb 13, 2024 at 1:56 PM Till Wegmüller wrote: > 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 > > Nice to see, however more code should be integrated for the hdmi suppport. > -Till > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On Tue, Feb 13, 2024 at 7:23 AM Stephan Althaus < stephan.alth...@duedinghausen.eu> wrote: > On 2/12/24 17:46, Stephan Althaus wrote: > > On 2/12/24 17:40, Udo Grabowski (IMK) wrote: > >> On 12/02/2024 17:32, Stephan Althaus wrote: > >>> ... > >>> That is the nvidia audio device, i can select it in vlc and hear > >>> nothing, my > >>> monitor speakers should do it - i have no clue at the moment.. > 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. > >>> > >>> i tried USB-C and HDMI connection the the monitor just right now > >>> with no luck.. > >>> > >>> # cat /dev/random > /dev/dsp1 > >>> > >>> gives no sound output.. > >>> > >> > >> mate-volume-control may helps. > >> > >> > >> > >> ___ > >> openindiana-discuss mailing list > >> openindiana-discuss@openindiana.org > >> https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > Hello! > > > > In the mate-volume-control, i have > > nothing in the hardware tab, > > audiohd#5 and Wmonitor of audiohd#5" in the input tab, > > audiohd#5 in the output tab, > > so nothing with audiohd#6 to configure there... > > > > By the way, running latest nvidia 535.154.5. > > > > Regards, > > Stephan > > > > > > > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > Hello! > > i crossed-checked with OI USB stick on a different older laptop with > Nvidia NVS 3100M, > + nvidia 340 gets used, > + the devices below /dev/ look pretty much the same and seem to be correct, > - "pactl list sinks" does not list the nvidia output, > + DDU says it is supported by the audiohd module (and so do i guess from > the links below /dev/), > - the "hardware" tab in the mate-volume-control is empty (it is not if > i boot debian linux with nvidia 340 on this old laptop) > - the nvidia related audiohd#1 devices are not listed within > mate-volume-control > > if i find the time i will check a desktop system with a GT1030.. > > Regards, > Stephan > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] a2ensite, a2dissite, & apache2ctl all command not found
On Tue, Jan 23, 2024 at 8:36 AM Stephan Althaus < stephan.alth...@duedinghausen.eu> wrote: > On 1/23/24 07:53, Christopher D. Bartels wrote: > > Hi, > > > > > > I'm working with a fresh install of apache 24 & am trying to disable > > the default site and enable the virtual host I've configured, but > > can't until I find how to use the a2ensite & a2dissite commands. In my > > case here they're both erroring with command not found with or without > > sudo. > > > > Can someone advise how to get these & other related apache2 commands > > working please? > > > > > > With thanks, > > > > Chris Bartels > > > > > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > Hi! > > These scripts are not delivered with our apache-24 package. > > see: > > $pkg contents apache-24|grep a2 > > > Maybe you could search the sources and create your own script files... > > https://gist.github.com/kevinmesiab/5404a839ce15b5f6e5e7 > > https://github.com/dracorp/a2enmod These scripts were originally specific to Debian packages, they were not provided by the Apache project itself. > > > ... > > > Regards, > > Stephan > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?
On Thu, Dec 14, 2023 at 10:38 AM Marcel Telka wrote: > On Thu, Dec 14, 2023 at 09:30:53AM +0100, Predrag Zečević wrote: > > I understand network - there can be a lot of problems preventing fast > > download, but *pkg* showing packages decreasing... > > Yes, it looks like a bug. Feel free to file a bugreport. > > > Also, is this OK (15GB of OI packages seems too much to me)? > > > > :; pfexec du -sh /var/pkg/publisher/* > > 21M /var/pkg/publisher/hipster-encumbered > > 15G /var/pkg/publisher/openindiana.org > > Not sure if it is okay or not. Here is mine: > > # du -sh /var/pkg/publisher/* > 2.30M /var/pkg/publisher/hipster-encumbered > 1019M /var/pkg/publisher/openindiana.org > # > > I fully update usually at least once a week with a reboot (and new BE). > This update includes bits from illumos-gate. I also update daily > (without reboot) to have always up-to-date userland bits. I do have > (almost) all packages installed. It is my oi and illumos build machine. > I cannot remember which option it is but you can autopurge the cache after successful install using a pkg property. > > HTH. > > -- > +---+ > | Marcel Telka e-mail: mar...@telka.sk | > |homepage: http://telka.sk/ | > +---+ > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox status?
On Wed, Sep 6, 2023 at 11:25 PM Carl Brewer wrote: > On 25/08/2023 9:17 pm, Stephan Althaus wrote: > > > > > YES, the GUI still doesn't work, HEADLESS does. > > > > Some (x11-)libs are not gcc-10 yet.. > Could make a list of the libs you found? > > > > (i had at least one lib where 'gmake test' did have no positive tests > :-/) > > Is this now a "Wait for us to fix it" issue? I don't have the skill or > resources (AFAIK) to be involved in recompiling/porting to gcc-10. > > > > > > For those who need the gui, use > > pkg:// > openindiana.org/system/virtualbox@6.1.40-2022.0.0.0:20221108T082551Z > > > > pfexec pkg install > > pkg:// > openindiana.org/system/virtualbox@6.1.40-2022.0.0.0:20221108T082551Z > > pfexec pkg freeze virtualbox > > Would "freeze" break later updates? VB is up to 7.0.10 now, so this > one's lagging a bit. > > Thank you > > Carl > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] funky update problem
On Thu, Oct 6, 2022 at 9:58 PM L. F. Elia via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > I just tried to upgrade OI and I get this. Ideas? > root@indianajones:~# pkg update -vpkg: 0/1 catalogs successfully updated: > > 1: Invalid contentpath > /var/pkg/cache/incoming-1375/update.20221006T06Z.C: CatalogPart failed > validation: The signature data for the > '/var/pkg/cache/incoming-1375/update.20221006T06Z.C' catalog file is not > valid.. (happened 4 times) 2: Invalid contentpath > /var/pkg/cache/incoming-1375/update.20221006T07Z.C: CatalogPart failed > validation: The signature data for the > '/var/pkg/cache/incoming-1375/update.20221006T07Z.C' catalog file is not > valid.. (happened 4 times) 3: Invalid contentpath > /var/pkg/cache/incoming-1375/update.20221006T15Z.C: CatalogPart failed > validation: The signature data for the > '/var/pkg/cache/incoming-1375/update.20221006T15Z.C' catalog file is not > valid.. (happened 4 times) > /var/pkg/cache/incoming-1375 does not exist > Maintenance is required to fix the issue on the server. We are looking into it. Thank you > > Lee > > > lfe...@yahoo.com, Portsmouth VA, 23701 > Solaris/LINUX/Windows administration CISSP/Security consulting > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] FLAG-DAY: We started to obsolete python 2.7 and 3.5
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
Re: [OpenIndiana-discuss] mkdocs 1.4 op OpenIndiana
On Sun, Oct 2, 2022 at 5:13 PM Marcel Telka wrote: > On Sun, Oct 02, 2022 at 05:04:36PM +0200, s...@pandora.be wrote: > > but the theme error can be solved by: > > > > # pip install mkdocs-bootswatch > > ... > > > or somebody could try to package mkdocs for Python 3.9 in IPS > oi-userland. > > I'm working on it: > https://openindiana.org/pipermail/oi-dev/2022-September/033266.html > > I'll add both mkdocs and mkdocs-bootswatch. Both at latest versions. > Thanks, that's great :) I recall that there was possibly a third package but not sure if that was for an older theme. When I packaged them there was a change in what was delivered in mkdocs, they had split some themes so I do not remember very well... > > Thanks. > > -- > +---+ > | Marcel Telka e-mail: mar...@telka.sk | > |homepage: http://telka.sk/ | > +---+ > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] FLAG-DAY: We started to obsolete python 2.7 and 3.5
On Thu, Sep 29, 2022 at 4:30 PM Marcel Telka wrote: > On Thu, Sep 29, 2022 at 04:18:01PM +0200, Aurélien Larcher wrote: > > We could define some rules or information depending on the nature of the > > package to mark which dependencies are expected. > > Some python modules have been added for the sake of resolving a > dependency > > while others have no consumer in userland but are expected to be > installed > > as "standalone" and consumed by users directly. > > > > Also I am not sure I understood which type of dependencies are considered > > here: > > - resolved within userland either directly or added explicitly in the > > manifest > > - build requirements > > - dependencies detected by pipdeptree (which are a superset of what > > pkg/userland detects) > > > > I just want to make sure that we do not miss some border effects. > > Okay, I'll stop to obsolete more python related packages and leave it as > it is for now so everybody have a chance to add back packages that were > obsoleted, but they are needed for any reason. > I am not asking you to stop anything at all, I am just asking questions to understand if this will not bite us back at some point. If you feel that you have everything covered then it is fine by me. Seeing the stream of obsoletions without warning was quite surprising and raised a few questions. You know how you want to handle things, but this is maybe less clear to others. At least maybe some indications on how to add the packages back and make sure there is no mistake or loss of consistency with the location/naming etc.. Kind regards, Aurélien > > -- > +---+ > | 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
Re: [OpenIndiana-discuss] [oi-dev] FLAG-DAY: We started to obsolete python 2.7 and 3.5
On Thu, Sep 29, 2022 at 4:00 PM Marcel Telka wrote: > On Thu, Sep 29, 2022 at 03:18:29PM +0200, Aurélien Larcher wrote: > > I do not understand the need for obsoleting the entire package and > removing > > all the files instead of updating on the go. > > > > Could you explain the motivation? > > There is no particular need. It is just simpler to obsolete than to > update. And since there is no known consumer, then the obsoletion is > the obvious option chosen. > We could define some rules or information depending on the nature of the package to mark which dependencies are expected. Some python modules have been added for the sake of resolving a dependency while others have no consumer in userland but are expected to be installed as "standalone" and consumed by users directly. Also I am not sure I understood which type of dependencies are considered here: - resolved within userland either directly or added explicitly in the manifest - build requirements - dependencies detected by pipdeptree (which are a superset of what pkg/userland detects) I just want to make sure that we do not miss some border effects. > > > To me this seems a bit of overhead, like removing the mkdocs, cython, > numpy > > packages completely from the tree instead of updating them. > > Feel free to create PRs to get them back. > > > We therefore lose track of what was in the tree and people may start from > > scratch all over again. > > > > Maybe you intend to provide some level of automation later? > > Maybe. If I find it easy to do I'll do so, but I've no immediate plan > to do so. > > > An earlier heads-up before starting to remove everything could have been > > nice to have a chance to update a few components in advance and avoid the > > mumbo-jumbo. > > Sorry. I try to do my best. Nothing is perfect. > > Anyway, an earlier update/rebuild of those packages for non-EOLed python > would be nice from you before you left them fall out of support and be > surprised that they are disappearing. > > Sorry, talking is easy. > > > Thank you. > > -- > +---+ > | 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
Re: [OpenIndiana-discuss] [oi-dev] FLAG-DAY: We started to obsolete python 2.7 and 3.5
On Thu, Sep 29, 2022 at 2:25 PM Marcel Telka wrote: > Hi, > > Currently we provide Python versions 2.7, 3.5, 3.7, and 3.9 for > OpenIndiana, while version 3.9 is the default version. > > Both Python 2.7 and 3.5 are no longer supported for two or almost three > years now respectively - see > https://devguide.python.org/versions/#versions for details, so we > started to obsolete them. Since there are many related packages that > needs to be rebuilt to get python 2.7 and 3.5 obsoleted, this transition > is expected to take long time (probably weeks, maybe months). > > There are basically two sets of related packages: > > #1 software that uses python (e.g. gimp), and > #2 packages that provide some enhancement to python; these are usually >python modules, for example cherrypy. > > For #1 we just need to rebuild packages that require python 2.7 or 3.5 > so they start to require either python 3.7, or python 3.9. Volunteers > are welcome! > > For #2 the situation is a bit more complex. The name of all packages in > this set is starting with 'library/python'. There is usually a basic > package (e.g. library/python/cherrypy) and few version specific packages > (e.g. library/python/cherrypy-35, library/python/cherrypy-37, > library/python/cherrypy-39). Another example is library/python/pycups > and its library/python/pycups-27 and library/python/pycups-35. > > For such packages we will slowly obsolete their -27 and -35 variants. > In a case there is neither -37 nor -39 variant already available, nor it > is needed for some other package, we will end up with all package > variants obsoleted. If this happens, then in addition to obsolete of > both -27 and -35 we will obsolete the base package too. > > For example, cherrypy. There are already -35, -37, and -39 variants. > We will obsolete the -35 variant and both -37 and -39 will be kept, so > we will keep the basic library/python/cherrypy too. > > When looking at pycups, we will obsolete both -27 and -35 variants. > Let's assume there is currently no other package that needs pycups, so > we would end with orphaned library/python/pycups, so we will obsolete > the library/python/pycups package too. > > Based on the rule above we already obsoleted following packages > recently: > > library/python/augeas > library/python/backports.shutil_get_terminal_size > library/python/backports.tempfile > library/python/cheetah > library/python/click > library/python/cssutils > library/python/cython > library/python/dulwich > library/python/geoip > library/python/elixir > library/python/import-profiler > library/python/kafka-python > library/python/livereload > library/python/m2crypto > library/python/mkdocs-bootstrap > library/python/mkdocs-bootswatch > library/python/mkdocs > library/python/netaddr > library/python/netifaces > library/python/numpy > library/python/pygtksourceview > library/python/pymongo > library/python/pyorbit > library/python/pyrex > library/python/pyro > library/python/python-ldap > library/python/python-memcached > library/python/python-mysql > library/python/python-notify > library/python/python-sexy > library/python/pywbem > library/python/scientific-py > library/python/sqlalchemy > library/python/typing > library/python/unittest2 > > Here is a list of packages that could get possibly obsoleted soon: > > library/python/backport_abc > library/python/backports.functools_lru_cache > library/python/backports.ssl_match_hostname > library/python/colorama > library/python/decorator > library/python/enum > library/python/flamegraph > library/python/funcsigs > library/python/ipaddress > library/python/ipython > library/python/ipython_genutils > library/python/notify2 > library/python/pickleshare > library/python/prompt-toolkit > library/python/pyatspi2 > library/python/pycups > library/python/pygobject > library/python/pygtk2 > library/python/python-compizconfig > library/python/python-xdg > library/python/python-xlib > library/python/rbtools > library/python/simplegeneric > library/python/traitlets > > If you need any package from these lists then please create a pull > request (see https://github.com/OpenIndiana/oi-userland/pulls) to get > the package back and built for python 3.7 and/or 3.9 (in a case it is on > the first list of already obsoleted packages), or either let us know or > create a pull request to rebuild the package for python 3.7 and/or 3.9 > (if it is on the second list of packages we could possibly obsolete). > > Any help with this task is very welcome (for example pull requests to > get software in set #1 rebuilt). > > Please note that support for building python modules for python 2.7 and > 3.5 was already dropped from oi-userland. > I do not understand the need for obsoleting the entire package and removing all the files instead of updating on the go. Could you explain the motivation? To me this seems a bit of overhead, like removing the mkdocs, cython, numpy packages completely from the tree instead of updating them. We
Re: [OpenIndiana-discuss] DKIM violationRe: libwww-perl-524 dependency problem
On Wed, Jul 27, 2022 at 11:26 AM Carsten Grzemba via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > > > Am 27.07.22 11:06 schrieb Aurélien Larcher : > > > > On Wed, Jul 27, 2022 at 9:53 AM Carsten Grzemba via openindiana-discuss < > > openindiana-discuss@openindiana.org> wrote: > > > > > If libwww-perl-524 is installed it is not possible to update > xscreensaver > > > and others because the dependency for > > > > > > library/perl-5/encode-locale-524 cannot longer resolved. > > > This package is obsoleted now. > > > > > > > Can anyone fix this? > > > > > > > There is seemingly no problem with the package dependencies, xscreensaver > > does not depend on perl-524 anymore. > > Could you try installing/updating specific package versions? > > > > I have noticed that pkg is sometimes not able to cope well with updates > > involving deprecation. > > It attempts to resolve the dependency to the deprecated packages and > update > > this latter although it should be dropped. > > > > Explicitly providing the versions you want to install on the command line > > usually circumvents the issue. > > > > > This seems to be wrong for me: > > > > > grzemba@oi-hipster:~$ pkg contents -o fmri -t depend > libwww-perl-524@latest > FMRI > library/perl-5/encode-locale-524 > library/perl-5/file-listing-524 > library/perl-5/html-parser-524 > library/perl-5/http-cookies-524 > library/perl-5/http-daemon-524 > library/perl-5/http-date-524 > library/perl-5/http-message-524 > library/perl-5/http-negotiate-524 > library/perl-5/lwp-mediatypes-524 > library/perl-5/net-http-524 > library/perl-5/uri-524 > library/perl-5/www-robotrules-524 > pkg:/runtime/perl-524@5.24.3-2020.0.1.3 > > > and > > pkg list -af library/perl-5/encode-locale-524@latest > NAME (PUBLISHER) VERSION IFO > library/perl-5/encode-locale-524 (openindiana.org) 1.5-2022.0.0.2 --o > I agree. However that does not explain why updating xscreensaver fails although it does not depend on perl 5.24 anymore. > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] libwww-perl-524 dependency problem
On Wed, Jul 27, 2022 at 9:53 AM Carsten Grzemba via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > If libwww-perl-524 is installed it is not possible to update xscreensaver > and others because the dependency for > > library/perl-5/encode-locale-524 cannot longer resolved. > This package is obsoleted now. > Can anyone fix this? > There is seemingly no problem with the package dependencies, xscreensaver does not depend on perl-524 anymore. Could you try installing/updating specific package versions? I have noticed that pkg is sometimes not able to cope well with updates involving deprecation. It attempts to resolve the dependency to the deprecated packages and update this latter although it should be dropped. Explicitly providing the versions you want to install on the command line usually circumvents the issue. > Thanks > -- > > Carsten > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Miscellaneous component fixes and migrations
Hi everyone, due to some changes happening in the past 2 years some components needed to be fixed (for most of them only a Makefile change or migration to newer Python/Perl). With Andreas we have worked to fix some of them in the past week as I could help a bit. However in the process I have found out that 32-bit versions had to be retired due to missing dependencies (e.g. 32-bit gobject-introspection), or conversion to 64-bit builds. So far I have tried to follow dependencies and not to break anything but I cannot ensure the absence of any side effects... Do not hesitate to point out any regression by replying in this thread. Kind regards, Aurélien -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Strange (?) error
Your problem is that boost is compiler as 32 and 64 bits and your program expects to find 64-bit versions where we install the 32-bit. You should pass an environment variable to indicate where the cmake files for the 64-bit version live: /usr/lib/amd64. It is a similar recipe as for PKG_CONFIG_PATH probably. On Tue, May 31, 2022 at 7:21 PM Apostolos Syropoulos via openindiana-discuss wrote: > The maintainer of apgnasm answered as follows to the same question: > > I'm afraid I can't offer much help with non-Linux OS's, but this right > here: > > but it set boost_program_options_FOUND to FALSE so package > "boost_program_options" is considered to be NOT FOUND > > > Indicates to me that what's being found is basically a "dummy" > configuration file which is intentionally setting that to false because > either that functionality isn't available or it's intentionally being > disabled. I'm not sure how package management is done on that system but > you may want to try to either install the actual Boost program options > package or if it is installed try reconfiguring it or re-installing it. > So I am wondering if the person who actually compiles could help me to > resolve this problem? > Kind regards, > Apostolos > > --Apostolos Syropoulos > Xanthi, Greece > > > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Advice for setting up a build zone with a different subnet than the main network interface
On Wed, Feb 2, 2022 at 1:33 PM John D Groenveld wrote: > In message < > cahmq6q02fdhubv0ydcxjurj-cqbzthgawkanvaeqjp7vovv...@mail.gmail.com>, > =?UTF-8?Q?Aur=C3=A9lien_Larcher?= writes: > >GZ: > >root@pegasus:~# dladm show-vnic > >LINK OVER SPEED MACADDRESSMACADDRTYPE VID > >br0 ether0 0 2:8:20:da:ec:bb random 0 > >vnic0ether0 0 2:8:20:cb:7b:85 random 0 > > > >NGZ: > >root@build:~# dladm show-vnic > >LINK OVER SPEED MACADDRESSMACADDRTYPE VID > >vnic0?0 2:8:20:cb:7b:85 random 0 > > In your NGZ, > # ipadm show-if > # ipadm show-addr I ended up deleting all the build zones and rebooting after I discovered using mdb's ::fsinfo that doors for deleted zones were still present on the system. Trying to attach a debugger on zoneadmd process failed miserably. I restarted from scratch with a new zone and things are working as expected. Something went really wrong and I have no idea what... > > > John > groenv...@acm.org > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Advice for setting up a build zone with a different subnet than the main network interface
On Wed, Feb 2, 2022 at 10:57 AM Aurélien Larcher wrote: > Just a small update, on the system where the network froze there are two > zoneadmd processes that seem stuck. > > root@jupiter-cemef:/export/home/alarcher# ps aux | grep zoneadmd > root 3438 0.0 0.0 7004 4012 ?S janv. 29 5:26 zoneadmd -z > build > root 6907 0.0 0.0 5132 1712 ?S janv. 31 0:00 zoneadmd -z > build0 > > I have halted and uninstalled the two zone earlier today. > > If I try to truss the processes I get: > > root@jupiter-cemef:/export/home/alarcher# pgrep zoneadmd > 3438 > 6907 > root@jupiter-cemef:/export/home/alarcher# truss -p 3438 > truss: no such process: 3438 > root@jupiter-cemef:/export/home/alarcher# truss -p 6907 > > > > truss: unanticipated system error: 6907 > > Is it expected? > My goal is to try to understand what triggered this breakage rather than blindly rebooting. > > On Tue, Feb 1, 2022 at 10:57 PM Aurélien Larcher < > aurelien.larc...@gmail.com> wrote: > >> >> >> On Tue, Feb 1, 2022 at 10:53 PM Till Wegmueller >> wrote: >> >>> Huh? >>> >>> Does this not show the etherstub layout? >>> > GZ: >>> > root@pegasus:~# dladm show-vnic >>> > LINK OVER SPEED MACADDRESSMACADDRTYPE >>> > VID >>> > br0 ether0 0 2:8:20:da:ec:bb random >>> 0 >>> > vnic0ether0 0 2:8:20:cb:7b:85 random >>> 0 >>> > >>> > NGZ: >>> > root@build:~# dladm show-vnic >>> > LINK OVER SPEED MACADDRESSMACADDRTYPE >>> > VID >>> > vnic0?0 2:8:20:cb:7b:85 random >>> 0 >>> >>> On OI CI in Hetzner my output looks like this. >>> >>> root@oidc1:~# dladm show-vnic >>> LINK OVER SPEED MACADDRESSMACADDRTYPE >>> VID >>> oijenkins0 oinetint00 2:8:20:e0:f6:20 random 0 >>> gzpublic0public0 0 2:8:20:37:b7:54 random 0 >>> oinetentry0 public0 0 2:8:20:3a:12:52 random 0 >>> oinetentry1 oinetint00 2:8:20:67:a0:16 random 0 >>> >>> So I would expect your output to show at least VNIC0 and a VNIC1. >>> >> >> The output below GZ shows both vnics while in the NGZ "build" it shows >> the vnic but '?' instead of ether0, and nothing can be done on it. >> >> >> >>> Also ip-type=exclusive must be set for it to work. >>> >> >> It is set to exclusive. >> >> Thank you >> >>> >>> Greetings >>> Till >>> >>> On 01.02.22 18:33, Aurélien Larcher wrote: >>> > On Tue, Feb 1, 2022 at 10:27 PM Till Wegmueller >>> > wrote: >>> > >>> >> Hey Aurelian >>> >> >>> >> You need two VNIC's one for the Zone and one for the GZ. John names >>> are >>> >> hard to differentiate but in the example he also uses two VNICS. >>> >> >>> > >>> > That's exactly what I have done. >>> > >>> > The vnic for the zone is not used in the GZ, not configured but fails >>> to be >>> > recognized in the zone. >>> > >>> > If I create a vnic without an etherstub then the vnic is seen in the >>> zone. >>> > >>> >> >>> >> Happy hacking >>> >> Till >>> >> >>> >> On 01.02.22 18:00, Aurélien Larcher wrote: >>> >>>> >>> >>>> >>> >>>> Do not use NWAM: >>> >>>> # svcadm enable svc:/network/physical:default >>> >>>> # ipadm create-addr -T dhcp bge0/v4 >>> >>>> >>> >>>> Do create an etherstub for your build NGZ: >>> >>>> # dladm create-etherstub zonenet0 >>> >>>> # dladm create-vnic -l zonenet0 gz0 >>> >>>> # dladm create-vnic -l zonenet0 bz0 >>> >>>> >>> >>>> Do assign a private network to your etherstub: >>> >>>> # ipadm create-addr -T static -a 192.168.0.1/24 gz0/v4 >>> >>>> >>> >>>> # cat <>> >>>> add net >>> >>>> set allowed-address="192.168.0.2/24" >>> >>>> set physical="
Re: [OpenIndiana-discuss] Advice for setting up a build zone with a different subnet than the main network interface
Just a small update, on the system where the network froze there are two zoneadmd processes that seem stuck. root@jupiter-cemef:/export/home/alarcher# ps aux | grep zoneadmd root 3438 0.0 0.0 7004 4012 ?S janv. 29 5:26 zoneadmd -z build root 6907 0.0 0.0 5132 1712 ?S janv. 31 0:00 zoneadmd -z build0 I have halted and uninstalled the two zone earlier today. If I try to truss the processes I get: root@jupiter-cemef:/export/home/alarcher# pgrep zoneadmd 3438 6907 root@jupiter-cemef:/export/home/alarcher# truss -p 3438 truss: no such process: 3438 root@jupiter-cemef:/export/home/alarcher# truss -p 6907 truss: unanticipated system error: 6907 Is it expected? On Tue, Feb 1, 2022 at 10:57 PM Aurélien Larcher wrote: > > > On Tue, Feb 1, 2022 at 10:53 PM Till Wegmueller > wrote: > >> Huh? >> >> Does this not show the etherstub layout? >> > GZ: >> > root@pegasus:~# dladm show-vnic >> > LINK OVER SPEED MACADDRESSMACADDRTYPE >> > VID >> > br0 ether0 0 2:8:20:da:ec:bb random >> 0 >> > vnic0ether0 0 2:8:20:cb:7b:85 random >> 0 >> > >> > NGZ: >> > root@build:~# dladm show-vnic >> > LINK OVER SPEED MACADDRESSMACADDRTYPE >> > VID >> > vnic0?0 2:8:20:cb:7b:85 random >> 0 >> >> On OI CI in Hetzner my output looks like this. >> >> root@oidc1:~# dladm show-vnic >> LINK OVER SPEED MACADDRESSMACADDRTYPE VID >> oijenkins0 oinetint00 2:8:20:e0:f6:20 random 0 >> gzpublic0public0 0 2:8:20:37:b7:54 random 0 >> oinetentry0 public0 0 2:8:20:3a:12:52 random 0 >> oinetentry1 oinetint00 2:8:20:67:a0:16 random 0 >> >> So I would expect your output to show at least VNIC0 and a VNIC1. >> > > The output below GZ shows both vnics while in the NGZ "build" it shows the > vnic but '?' instead of ether0, and nothing can be done on it. > > > >> Also ip-type=exclusive must be set for it to work. >> > > It is set to exclusive. > > Thank you > >> >> Greetings >> Till >> >> On 01.02.22 18:33, Aurélien Larcher wrote: >> > On Tue, Feb 1, 2022 at 10:27 PM Till Wegmueller >> > wrote: >> > >> >> Hey Aurelian >> >> >> >> You need two VNIC's one for the Zone and one for the GZ. John names are >> >> hard to differentiate but in the example he also uses two VNICS. >> >> >> > >> > That's exactly what I have done. >> > >> > The vnic for the zone is not used in the GZ, not configured but fails >> to be >> > recognized in the zone. >> > >> > If I create a vnic without an etherstub then the vnic is seen in the >> zone. >> > >> >> >> >> Happy hacking >> >> Till >> >> >> >> On 01.02.22 18:00, Aurélien Larcher wrote: >> >>>> >> >>>> >> >>>> Do not use NWAM: >> >>>> # svcadm enable svc:/network/physical:default >> >>>> # ipadm create-addr -T dhcp bge0/v4 >> >>>> >> >>>> Do create an etherstub for your build NGZ: >> >>>> # dladm create-etherstub zonenet0 >> >>>> # dladm create-vnic -l zonenet0 gz0 >> >>>> # dladm create-vnic -l zonenet0 bz0 >> >>>> >> >>>> Do assign a private network to your etherstub: >> >>>> # ipadm create-addr -T static -a 192.168.0.1/24 gz0/v4 >> >>>> >> >>>> # cat <> >>>> add net >> >>>> set allowed-address="192.168.0.2/24" >> >>>> set physical="bz0" >> >>>> set defrouter="192.168.0.1" >> >>>> end >> >>>> EOF >> >>>> >> >>>> Do use ipnat and IP Forwarding to allow your build NGZ to connect >> >>>> your university network: >> >>>> # cat /etc/ipf/ipnat.conf >> >>>> map bge0 192.168.0.0/24 -> 0/32 portmap tcp/udp auto >> >>>> # routeadm -e ipv4-forwarding >> >>>> # routeadm -u >> >>>> >> >>>> >> >>> Dear John, >> >>> thank you for your insightful suggestion and my apologies for the >> delay, >>
Re: [OpenIndiana-discuss] Advice for setting up a build zone with a different subnet than the main network interface
On Tue, Feb 1, 2022 at 10:53 PM Till Wegmueller wrote: > Huh? > > Does this not show the etherstub layout? > > GZ: > > root@pegasus:~# dladm show-vnic > > LINK OVER SPEED MACADDRESSMACADDRTYPE > > VID > > br0 ether0 0 2:8:20:da:ec:bb random 0 > > vnic0ether0 0 2:8:20:cb:7b:85 random 0 > > > > NGZ: > > root@build:~# dladm show-vnic > > LINK OVER SPEED MACADDRESSMACADDRTYPE > > VID > > vnic0?0 2:8:20:cb:7b:85 random 0 > > On OI CI in Hetzner my output looks like this. > > root@oidc1:~# dladm show-vnic > LINK OVER SPEED MACADDRESSMACADDRTYPE VID > oijenkins0 oinetint00 2:8:20:e0:f6:20 random 0 > gzpublic0public0 0 2:8:20:37:b7:54 random 0 > oinetentry0 public0 0 2:8:20:3a:12:52 random 0 > oinetentry1 oinetint00 2:8:20:67:a0:16 random 0 > > So I would expect your output to show at least VNIC0 and a VNIC1. > The output below GZ shows both vnics while in the NGZ "build" it shows the vnic but '?' instead of ether0, and nothing can be done on it. > Also ip-type=exclusive must be set for it to work. > It is set to exclusive. Thank you > > Greetings > Till > > On 01.02.22 18:33, Aurélien Larcher wrote: > > On Tue, Feb 1, 2022 at 10:27 PM Till Wegmueller > > wrote: > > > >> Hey Aurelian > >> > >> You need two VNIC's one for the Zone and one for the GZ. John names are > >> hard to differentiate but in the example he also uses two VNICS. > >> > > > > That's exactly what I have done. > > > > The vnic for the zone is not used in the GZ, not configured but fails to > be > > recognized in the zone. > > > > If I create a vnic without an etherstub then the vnic is seen in the > zone. > > > >> > >> Happy hacking > >> Till > >> > >> On 01.02.22 18:00, Aurélien Larcher wrote: > >>>> > >>>> > >>>> Do not use NWAM: > >>>> # svcadm enable svc:/network/physical:default > >>>> # ipadm create-addr -T dhcp bge0/v4 > >>>> > >>>> Do create an etherstub for your build NGZ: > >>>> # dladm create-etherstub zonenet0 > >>>> # dladm create-vnic -l zonenet0 gz0 > >>>> # dladm create-vnic -l zonenet0 bz0 > >>>> > >>>> Do assign a private network to your etherstub: > >>>> # ipadm create-addr -T static -a 192.168.0.1/24 gz0/v4 > >>>> > >>>> # cat < >>>> add net > >>>> set allowed-address="192.168.0.2/24" > >>>> set physical="bz0" > >>>> set defrouter="192.168.0.1" > >>>> end > >>>> EOF > >>>> > >>>> Do use ipnat and IP Forwarding to allow your build NGZ to connect > >>>> your university network: > >>>> # cat /etc/ipf/ipnat.conf > >>>> map bge0 192.168.0.0/24 -> 0/32 portmap tcp/udp auto > >>>> # routeadm -e ipv4-forwarding > >>>> # routeadm -u > >>>> > >>>> > >>> Dear John, > >>> thank you for your insightful suggestion and my apologies for the > delay, > >> I > >>> have been busy with a handful of PhD students finishing soon... > >>> > >>> I have switched to network/physical:default and implemented your > >> suggestion > >>> with the etherstub. > >>> > >>> However I am very surprised that on both my systems this approach fails > >> as > >>> the network interface is not configured in the zone. > >>> > >>> Even stranger, it seems that the vnic is only partially exposed to the > >> zone. > >>> > >>> For example: > >>> > >>> GZ: > >>> root@pegasus:~# dladm show-vnic > >>> LINK OVER SPEED MACADDRESSMACADDRTYPE > >> VID > >>> br0 ether0 0 2:8:20:da:ec:bb random > 0 > >>> vnic0ether0 0 2:8:20:cb:7b:85 random > 0 > >>> > >>> NGZ: > >>> root@build:~# dladm show-vnic > >>> LINK OVER SPEED MACADDRESS
Re: [OpenIndiana-discuss] Advice for setting up a build zone with a different subnet than the main network interface
On Tue, Feb 1, 2022 at 10:27 PM Till Wegmueller wrote: > Hey Aurelian > > You need two VNIC's one for the Zone and one for the GZ. John names are > hard to differentiate but in the example he also uses two VNICS. > That's exactly what I have done. The vnic for the zone is not used in the GZ, not configured but fails to be recognized in the zone. If I create a vnic without an etherstub then the vnic is seen in the zone. > > Happy hacking > Till > > On 01.02.22 18:00, Aurélien Larcher wrote: > >> > >> > >> Do not use NWAM: > >> # svcadm enable svc:/network/physical:default > >> # ipadm create-addr -T dhcp bge0/v4 > >> > >> Do create an etherstub for your build NGZ: > >> # dladm create-etherstub zonenet0 > >> # dladm create-vnic -l zonenet0 gz0 > >> # dladm create-vnic -l zonenet0 bz0 > >> > >> Do assign a private network to your etherstub: > >> # ipadm create-addr -T static -a 192.168.0.1/24 gz0/v4 > >> > >> # cat < >> add net > >> set allowed-address="192.168.0.2/24" > >> set physical="bz0" > >> set defrouter="192.168.0.1" > >> end > >> EOF > >> > >> Do use ipnat and IP Forwarding to allow your build NGZ to connect > >> your university network: > >> # cat /etc/ipf/ipnat.conf > >> map bge0 192.168.0.0/24 -> 0/32 portmap tcp/udp auto > >> # routeadm -e ipv4-forwarding > >> # routeadm -u > >> > >> > > Dear John, > > thank you for your insightful suggestion and my apologies for the delay, > I > > have been busy with a handful of PhD students finishing soon... > > > > I have switched to network/physical:default and implemented your > suggestion > > with the etherstub. > > > > However I am very surprised that on both my systems this approach fails > as > > the network interface is not configured in the zone. > > > > Even stranger, it seems that the vnic is only partially exposed to the > zone. > > > > For example: > > > > GZ: > > root@pegasus:~# dladm show-vnic > > LINK OVER SPEED MACADDRESSMACADDRTYPE > VID > > br0 ether0 0 2:8:20:da:ec:bb random 0 > > vnic0ether0 0 2:8:20:cb:7b:85 random 0 > > > > NGZ: > > root@build:~# dladm show-vnic > > LINK OVER SPEED MACADDRESSMACADDRTYPE > VID > > vnic0?0 2:8:20:cb:7b:85 random 0 > > > > On the second machin the zone simply refused to boot and the zoneadm > > service is stuck, I cannot boot any other zone. > > > > My setup without the etherstub led to a configured interface, in this > case > > the vnic was linked to the physical interface directly. > > > > I wonder if we have some limitations in vanilla illumos which may have > been > > fixed in e.g. smartos. > > > > > > Kind regards, > > > > Aurélien > > > > > > > > > > > > > > > > > > > > > >> > >> Happy hacking, > >> John > >> groenv...@acm.org > >> > >> ___ > >> 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Advice for setting up a build zone with a different subnet than the main network interface
> > > Do not use NWAM: > # svcadm enable svc:/network/physical:default > # ipadm create-addr -T dhcp bge0/v4 > > Do create an etherstub for your build NGZ: > # dladm create-etherstub zonenet0 > # dladm create-vnic -l zonenet0 gz0 > # dladm create-vnic -l zonenet0 bz0 > > Do assign a private network to your etherstub: > # ipadm create-addr -T static -a 192.168.0.1/24 gz0/v4 > > # cat < add net > set allowed-address="192.168.0.2/24" > set physical="bz0" > set defrouter="192.168.0.1" > end > EOF > > Do use ipnat and IP Forwarding to allow your build NGZ to connect > your university network: > # cat /etc/ipf/ipnat.conf > map bge0 192.168.0.0/24 -> 0/32 portmap tcp/udp auto > # routeadm -e ipv4-forwarding > # routeadm -u > > Dear John, thank you for your insightful suggestion and my apologies for the delay, I have been busy with a handful of PhD students finishing soon... I have switched to network/physical:default and implemented your suggestion with the etherstub. However I am very surprised that on both my systems this approach fails as the network interface is not configured in the zone. Even stranger, it seems that the vnic is only partially exposed to the zone. For example: GZ: root@pegasus:~# dladm show-vnic LINK OVER SPEED MACADDRESSMACADDRTYPE VID br0 ether0 0 2:8:20:da:ec:bb random 0 vnic0ether0 0 2:8:20:cb:7b:85 random 0 NGZ: root@build:~# dladm show-vnic LINK OVER SPEED MACADDRESSMACADDRTYPE VID vnic0?0 2:8:20:cb:7b:85 random 0 On the second machin the zone simply refused to boot and the zoneadm service is stuck, I cannot boot any other zone. My setup without the etherstub led to a configured interface, in this case the vnic was linked to the physical interface directly. I wonder if we have some limitations in vanilla illumos which may have been fixed in e.g. smartos. Kind regards, Aurélien > > Happy hacking, > John > groenv...@acm.org > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Advice for setting up a build zone with a different subnet than the main network interface
Hi everyone, I was wondering if you would have some recommendations for setting up the crossbow configuration on a new server at university. The machine has 3 networking interfaces: - one bge0 with an address 10.202.96.14/24 given by the university's dhcp server, that cannot be changed, I only have the right to get one IP, gateway is 10.202.96.254. - two 25Gb Mellanox interfaces configured as static addresses for serving file shares to two other machines. Until now I have used NWAM for the configuration by creating a specific NCP then I had created a virtual NIC named vnic0 for the zone, and another br0 used as gateway with dladm/ipadm then forwarding/routing rules from vnic0 -> br0 -> bge0 and masquerading from bg0 with a map in /etc/ipf/ipnat.conf. The virtual subnet was such that vnic0 got address 10.202.254.1 and br0 10.202.254.100 with the appropriate netmask (16 I think). However this setup breaks after the reboot because the NWAM configuration creates temporary "objects". Also I am not sure if this virtual nic serving as a gateway is necessary, or if an etherstub should be used. Do you have any pointer or recommendation for such a setup with a zone on a virtual private subnet? Kind regards, Aurélien -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Deprecation of 32-bit encumbered binaries
Hi, I have now deprecated 32-bit builds in the encumbered repository. This means that ffmpeg is now 64-bit only and audacity was migrated to 64-bit. The main motivation is that gcc-10 were failing for 32-bit builds and they are probably not worth the trouble. A few components in userland still rely on 32-bit gstreamer plugins: they should be migrated as well. I have already switched Gthumb to 64-bit yesterday. As a side effect, meson was fixed to handle static linking properly, you should update if you experience similar issues. Kind regards, Aurélien -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Fwd: [developer] SECURITY HEADS UP - illumos#14424
Given that illumos-gate is rebuilt every night, this change will land in Hipster by tomorrow; it was merged into illumos-gate 3 hours ago. Nonetheless I am forwarding the information in case it affects anyone subscribed to these mailing lists. -- Forwarded message - From: Dan McDonald Date: Tue, Jan 18, 2022 at 7:55 PM Subject: [developer] SECURITY HEADS UP - illumos#14424 To: illumos-developer , illumos-discuss < disc...@lists.illumos.org> Cc: Dan McDonald Hello folks! Quick breakdown: IMPACT: This bug allows an unprivileged user with access to a tmpfs to induce a denial of service to the system. This is more serious if untrusted users have access to the system (e.g. a shared environment). ACTION: Please be on the look out for patches from the various distributions and be ready to install them. MITIGATIONS: At this time, there are no known easy mitigations that one can apply short of disabling access to untrusted users and/or removing the ability to use tmpfs from their zones. NEXT STEPS: As we follow up on this, we'll be doing some additional auditing and looking to more generally strengthen our regression test suites to be able to catch issues like this in advance and ensure that that they are not reintroduced. . . . These details are also in https://www.illumos.org/issues/14424 Security researcher Hans Christian Woithe reported CVE-2021-43395 to both us and Oracle. He discovered conditions where any arbitrary user could induce tmpfs to panic with deadlock-detection. This bug tracks our fix for this problem. Tested using Hans's PoC, which now does not induce a panic. Tested on OmniOS both bare-metal (by Andy Fiddaman) and VM (by Dan McD.). Tested on SmartOS bare-metal (by Dan McD.). We will introduce more analysis into the bug report as this fix gets propagated. If you run a distro PLEASE PUT THIS FIX IN ANY SUPPORTED RELEASE YOU HAVE. It's easily backportable/cherry-pickable; I know OmniOS has it in their old-LTS r151030, for example. Thanks to Robert Mustacchi and Andy Fiddaman for feedback of earlier revisions of this fix. Thanks especially to security researcher Hans Christian Woithe, who informed us and Oracle of this very old bug. I appreciate he took the advice here: https://kebe.com/blog/?p=505 and I hope we reacted accordingly and politely (given we coordinated releasing this fix with Oracle). Please update your distros ASAP. And after some time, we'll update 14424 with details on how we arrived at the illumos fix. Thank you, Dan McDonald & Robert Mustacchi - on behalf of secur...@illumos.org -- illumos: illumos-developer Permalink: https://illumos.topicbox.com/groups/developer/T1c9e4f27f8c2f959-M152e45495ece9b9555b52167 Delivery options: https://illumos.topicbox.com/groups/developer/subscription -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] warning - don't update OI
Should we disable the repository momentarily and remove the packages
published in the past 24hours?
On Sat, Jul 24, 2021 at 9:56 AM Andreas Wacknitz wrote:
> Hi all,
>
> something bad has happened with the last updates and rendered two of my
> build servers unbootable. They are both stuck in the boot loader ("start
> not found") such that
> booting with an old BE won't fix that!
>
> SO DON'T UPDATE YOUR SYSTEMS FOR NOW!
>
> I fear that my update of binutils-2.37 may be the culprit.
>
> Regards
> Andreas
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
--
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] still 2020.0.1 ?
On Wed, May 5, 2021 at 9:41 AM Stephan Althaus < stephan.alth...@duedinghausen.eu> wrote: > Hi! > > I am just curious, the pkg versions still state *2020.0.2*, but we are > in 2021 now ? > I do not know if it is the case in this particular instance but we used to delay bumping the year if an update of the userland compiler was foreseen. This was to avoid bumping twice. > > > # pkg update -v > Packages to update: 402 > Estimated space available: 28.24 GB > Estimated space to be consumed: 2.34 GB > Create boot environment: Yes > Activate boot environment: Yes > Create backup boot environment: No >Rebuild boot archive: Yes > > Changed packages: > openindiana.org >SUNWcs > 0.5.11-2020.0.1.20467 -> 0.5.11-2020.0.1.20489 >SUNWcsd > 0.5.11-2020.0.1.20467 -> 0.5.11-2020.0.1.20489 > ... > > > Stephan > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Rolling release considered harmful
On Tue, May 4, 2021 at 3:56 PM Yassine Chaouche < a.chaou...@algerian-radio.dz> wrote: > Le 5/4/21 à 2:34 PM, Toomas Soome via openindiana-discuss a écrit : > > Upgrades of Ubuntu LTS break more than OI on my server and without any > > possibility of rollback to a previous boot environment... > >> Upgrades != updates. > > Hm, what is the difference?:) Rgds, Toomas > > Well you can *update* packages and remain in same OS version. Or, > you can *upgrade* to next OS version, for example from Ubuntu 16 > to Ubuntu 17. In that case yes, breaks happen, and most users > prefer to simply reinstall instead of upgrading, which they > consider cleaner. > Yes and sometimes it does not feel like it is 2021 ;) > > -- Yassine > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Rolling release considered harmful
On Tue, May 4, 2021 at 2:40 PM Judah Richardson wrote: > On Tue, May 4, 2021, 07:25 Yassine Chaouche > wrote: > > > Le 5/4/21 à 5:24 AM, Judah Richardson a écrit : > > > From a practical perspective, I don't think OI has the option you want. > > > It's a rolling release distribution. I > > So, just to be clear for outsiders like myself. I thought Hipster > > was the Rolling Release Branch. I assumed OI had another fixed > > release branche, but apparently there's not ? > > > Hipster is the only release mentioned on the blog in over 2 years and the > only release listed on the download page. I had the same question when I > 1st downloaded OI, but it was pretty obvious to me from the above that > Hipster is the main effort, and so that's what I installed. Don't fight the > paradigm, as I keep saying. > Upgrades of Ubuntu LTS break more than OI on my server and without any possibility of rollback to a previous boot environment... I think the idea of a "stable release" prepared for several years of production should be relaxed... Even on our last supercomputer we had to move to CentOS Stream since CentOS has dropped support for a stable release... > > > > -- Yassine > > > > ___ > > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installing to a RAIDZ2 root pool How-To
On Sun, Apr 18, 2021 at 5:24 PM Toomas Soome via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > > > > On 18. Apr 2021, at 17:16, Reginald Beardsley via openindiana-discuss < > openindiana-discuss@openindiana.org> wrote: > > > > It is my understanding that we can now boot from a RAIDZ pool. Are > there any known limitations? I looked at the wiki and I didn't see any > instructions related to booting from a RAIDZ pool or installing into a > RAIDZ pool. > > > > It looks pretty straight forward, but there are some details that are > not obvious. In particular the need to create the pool and use the > text-install script to install into an existing pool. That will not create > rpool/swap and rpool/dump so the user must run dumpadm and swap to set up > dump and swap space. > > > > As I am going to be doing this shortly with a RAIDZ2 rpool I thought I > should write up the process for the wiki if there is not a How-To already > that I missed. > > > > Reg > > > > I have not used installer for some time, so I can not tell if or how well > the raidz creation will work from installer. > I think only the text installer allows it. > > However, there is one very important limitation; please make sure your > firmware actually can access at least data disks + one parity, otherwise > you will need to relocate disks into accessible slots. > > rgds, > toomas > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Illumos/OI development system installation
On Sat, Apr 10, 2021 at 7:27 PM Reginald Beardsley via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > > Which does what? Does that retrieve the source code? If so, where does it > put it? What are the prerequisites? Neither pkg(1) nor pkg(5) offer any > explanation. > I am not sure what you are trying to achieve but building and installing illumos-gate on OI can be as simple as: - cloning oi-userland, - committing your changes locally or changing the branch to build in oi-userland/components/openindiana/illumos-gate/Makefile and incrementing the branch version, - running gmake publish in components/openindiana/illumos-gate to build and publish to the local repository located in oi-userland/i386/repo - running pkg update -g oi-userland/i386/repo to a new BE, - reboot. > > Reg > > On Saturday, April 10, 2021, 11:48:13 AM CDT, Tomasz Kłoczko < > kloczko.tom...@gmail.com> wrote: > > On Sat, 10 Apr 2021 at 15:34, Reginald Beardsley via openindiana-discuss < > openindiana-discuss@openindiana.org> wrote: > > > I should like to suggest that providing a turnkey development > > installation that would permit someone like me to compile format(1m) and > > fix the SEGV faults would go a long way towards increasing the number of > > people supporting OI and Illumos. > > > > Sorry but you don't need special installer for single command like > "pkg change-facet devel=true" > > kloczek > -- > Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH > ___ > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OpenIndiana-discuss] Filezilla 3.47.2.1 working
Actually you can use 3.1.x with minor patching, that's what we did when 3.1.3 was shipped. FileZilla worked with 3.1.x perfectly. Wxwidgets 3.1.x is the production version recommended by the developers and 3.0.x should be only used if backward compatibility is required. We were told by their developers not to ship 3.0.x but rather 3.1.x and adapt any code to use 3.1.x. I am not sure why FileZilla uses a version that is not recommended On Sat, 3 Apr 2021, 12:43 pm russell, wrote: > HI > > WxWidgets 3.1.X can not be used as it is a development release, you must > build it with WxWidgets Stable Release 3.0.X as can be seen below, the > previous stable release was 2.8.12 released in 2011. > > Replacing the default WxWidgets 2.8.12 (API stable since 2006) with > 3.0.5 released in April 2020 (API stable since 2013) as detailed below > > https://www.wxwidgets.org/downloads/ > > Having the development release available is useful but Filezilla is > coded to build using the stable release only. > > > 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] Updated NVIDIA drivers
On Fri, Mar 12, 2021 at 10:40 PM Reginald Beardsley via openindiana-discuss wrote: > I don't know why I should expect anything different given that gparted > dumps core in 2020.10 and doesn't recognize a Windows 7 Pro and Debian 9.3 > installation on a 2 TB disk in 2017.10. > > Still not detecting the card and installing the correct driver seems > rather lame. > Nice way to thank someone who just spent a few evenings trying to help you. > > "scanpci -v" produces this for the graphics card in my Z400: > > pci bus 0x000f cardnum 0x00 function 0x00: vendor 0x10de device 0x0638 > NVIDIA Corporation G94GL [Quadro FX 1800] > CardVendor 0x10de card 0x062c (NVIDIA Corporation, Card unknown) > STATUS 0x0010 COMMAND 0x0047 > CLASS 0x03 0x00 0x00 REVISION 0xa1 > BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x00 > BASE0 0xf600 SIZE 16777216 MEM > BASE1 0xe000 SIZE 268435456 MEM64 PREFETCHABLE > BASE3 0xf400 SIZE 33554432 MEM64 > BASE5 0xe000 SIZE 128 I/O > MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x03 > > I don't see a lot of difficulty to writing a shell script that takes the > output of scanpci and spits out the appropriate nVidia driver number. If > the install system is sane enough that such a solution will work, I'll > write and maintain it. > > I am proposing: > > GRAPHIC_DRIVER=`/sbin/ ` > > If that is not a viable solution for some reason, then I'm not likely to > keep using OI. I've repeatedly volunteered to help over the last 8-10 > years. I've never ever received useful replies. In most cases, not even a > useless reply. Mostly I just see whining about the limited number of people > providing support. > > I estimate that "nvidia_driver_to_use" would take 3-4 hours to write. Wall > time longer if I need to contact nVidia for device and driver mappings. If > you demand that I spend 2-3 days analyzing the horribly borked install > process, it's just not going to happen. > > I might do that, but only if I get replies. > > Reg > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] error upgrading to hipster -- Action upgrade failed for 'etc/dfs/sharetab'
On Mon, Mar 8, 2021 at 8:38 PM Geoff Nordli wrote: > You are probably right, this server is on its last legs. I was hoping > there was a quick fix to get it upgraded. > A long long time ago Alexander posted some details on the mailing lists to circumvent this bug. > > On 2021-03-08 2:16 a.m., Carl Brewer wrote: > > Sorry for top posting .. > > I gave up doing this and just built a new server, then moved > > everything I cared about across to it. > > > > On 8 March 2021 5:09:46 pm AEDT, Geoff Nordli wrote: > > > > Hi. > > > > I am trying to upgrade the older version of OI (oi_151a9 May 2015) to > > the hipster branch. No search results seemed to help me with this > error. > > > > This is what I am getting below. Any thoughts? > > > > > > Update Phase 10395/54131 > > > > Action upgrade failed for 'etc/dfs/sharetab' > > (pkg://openindiana.org/SUNWcs): TypeError: 'NoneType' object is not > > callable > >The running system has not been modified. Modifications were only > made > > to a clone of the running system. This clone is mounted at > > /tmp/tmpREuU91 should you wish to inspect it. > > pkg: An unexpected error happened during update: 'NoneType' object is > > not callable > > > > The following unexpected or editable files and directories were > > salvaged while executing the requested package operation; they > > have been moved to the displayed location in the image: > > > > usr/share/applications/mimeinfo.cache -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/share/applications/mimeinfo.cache-20210307T214655Z > > var/sadm/system/logs -> > > > /tmp/tmpREuU91/var/pkg/lost+found/var/sadm/system/logs-20210307T214712Z > > var/sadm/system -> > > /tmp/tmpREuU91/var/pkg/lost+found/var/sadm/system-20210307T214712Z > > var/sadm/servicetag/registry -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/var/sadm/servicetag/registry-20210307T214712Z > > var/log/gdm -> > > /tmp/tmpREuU91/var/pkg/lost+found/var/log/gdm-20210307T214712Z > > var/lib/gdm -> > > /tmp/tmpREuU91/var/pkg/lost+found/var/lib/gdm-20210307T214712Z > > var/cache/gdm -> > > /tmp/tmpREuU91/var/pkg/lost+found/var/cache/gdm-20210307T214712Z > > usr/lib/python2.6/xml/parsers -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/xml/parsers-20210307T214713Z > > usr/lib/python2.6/xml/dom -> > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/xml/dom-20210307T214713Z > > usr/lib/python2.6/xml -> > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/xml-20210307T214713Z > > usr/lib/python2.6/vendor-packages/ply -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/vendor-packages/ply-20210307T214713Z > > usr/lib/python2.6/vendor-packages/M2Crypto/SSL -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/vendor-packages/M2Crypto/SSL-20210307T214713Z > > usr/lib/python2.6/vendor-packages/M2Crypto/PGP -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/vendor-packages/M2Crypto/PGP-20210307T214713Z > > usr/lib/python2.6/vendor-packages/M2Crypto -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/vendor-packages/M2Crypto-20210307T214713Z > > usr/lib/python2.6/vendor-packages -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/vendor-packages-20210307T214713Z > > usr/lib/python2.6/site-packages -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/site-packages-20210307T214713Z > > usr/lib/python2.6/logging -> > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/logging-20210307T214713Z > > usr/lib/python2.6/encodings -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/encodings-20210307T214713Z > > usr/lib/python2.6/email/mime -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/email/mime-20210307T214713Z > > usr/lib/python2.6/email -> > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/email-20210307T214713Z > > usr/lib/python2.6/distutils/command -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/distutils/command-20210307T214713Z > > usr/lib/python2.6/distutils -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/distutils-20210307T214713Z > > usr/lib/python2.6/curses -> > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/curses-20210307T214713Z > > usr/lib/python2.6/ctypes -> > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6/ctypes-20210307T214713Z > > usr/lib/python2.6 -> > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.6-20210307T214713Z > > usr/lib/python2.4/site-packages -> > > > > /tmp/tmpREuU91/var/pkg/lost+found/usr/lib/python2.4/site-packages-20210307T214713Z > > etc/rad -> > /tmp/tmpREuU91/var/pkg/lost+found/etc/rad-20210307T214713Z > >
Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!
On Fri, Mar 5, 2021 at 4:10 PM Reginald Beardsley via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > With this piece of utter nonsense I am going to depart from the > conversation in hopes that the actual subject can be addressed in a > sensible fashion at a later time. I have other things to do and it's quite > clear that there is no reason to "upgrade" from 2017.10 any time soon. > There is far too much that needs to be fixed. When the name "Hipster" > appeared it made me uneasy. Unfortunately my concerns have been confirmed. > Your issues have nothing to do with OI itself I am afraid. We ship vanilla illumos without any modification and when it comes to Nvidia drivers they simply do not support illumos i.e. if they "work" we are just lucky. > > BTW I'm not running an OI server and have never said I was. SunOS has been > my preferred native work environment for 30 years. As I don't wish to > gamble with having Solaris 10 u8 connected to the internet, I use OI for > internet and casual computing tasks. The shift from an Atom netbox to a > Z400 to run OI resulted in my tending to do more casual computing on OI. > > McKusic's most recent book arrived yesterday and I wish to find out what > he has to say this time. Even if I never use FreeBSD as my working > environment I'm sure I'll learn more than enough to justify the time spent. > > Reg > > On Friday, March 5, 2021, 04:28:08 AM CST, cretin1997 via > openindiana-discuss wrote: > > ‐‐‐ Original Message ‐‐‐ > On Friday, March 5, 2021 3:34 PM, Udo Grabowski (IMK) < > udo.grabow...@kit.edu> wrote: > > > On 05.03.21 07:56, cretin1997 via openindiana-discuss wrote: > > > > > ... > > > Trust me, man. SquashFS is a superior technology ... > > > > > It's the superior technology ... > > > > From my decades of experience, if I read such sentences, > > I immediately know it's not. Superior. > > It's just another "something", surrounded by Hipsters > > trying to generate a hype around it. > > Except this time you are wrong. You just use experience to beat other > people. You have no first hand experience with SquashFS and no knowledge > about it. I suggest download a live Linux system from distrowatch, you > could choose a random distro, boot it live system, play with it for a > while, and realize how behind we are to Linux in term of live system > technology. > > > > > > and is the answer to our problem. > > > > ? What problem ? What you are talking about ? Why > > not using Linux when everything there is superior > > and solves your problems ? What you are doing here ? > > > > Yeah yeah I know. You are the best! Others are rubbish! You don't have to > learn anything from others but only them learn from you! Yeah, they really > did just that. They learned and imported ZFS from you and now their ZoL > implementation becomes upstream, your implementation is lagged behind. > Yeah, SystemD learned from SMF and FMA, but just superior because they > don't use everything XML like yours. Yeah, I know all of that. > > Childish behavior like yours only caused the interested people to go away. > And I really considered to go away. But the fact is I see I still can do > something useful with OI and don't want to give up too soon. Yeah, I know, > from my experience on this mail list, give up is most of the time the > answers! Sooner or later, I will have to give up. But I don't want to give > it up too soon. Got it? > > ___ > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!
On Fri, Mar 5, 2021 at 11:28 AM cretin1997 via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > ‐‐‐ Original Message ‐‐‐ > On Friday, March 5, 2021 3:34 PM, Udo Grabowski (IMK) < > udo.grabow...@kit.edu> wrote: > > > On 05.03.21 07:56, cretin1997 via openindiana-discuss wrote: > > > > > ... > > > Trust me, man. SquashFS is a superior technology ... > > > > > It's the superior technology ... > > > > From my decades of experience, if I read such sentences, > > I immediately know it's not. Superior. > > It's just another "something", surrounded by Hipsters > > trying to generate a hype around it. > > Except this time you are wrong. You just use experience to beat other > people. You have no first hand experience with SquashFS and no knowledge > about it. I suggest download a live Linux system from distrowatch, you > could choose a random distro, boot it live system, play with it for a > while, and realize how behind we are to Linux in term of live system > technology. > > > > > > and is the answer to our problem. > > > > ? What problem ? What you are talking about ? Why > > not using Linux when everything there is superior > > and solves your problems ? What you are doing here ? > > > > Yeah yeah I know. You are the best! Others are rubbish! You don't have to > learn anything from others but only them learn from you! Yeah, they really > did just that. They learned and imported ZFS from you and now their ZoL > implementation becomes upstream, your implementation is lagged behind. > Yeah, SystemD learned from SMF and FMA, but just superior because they > don't use everything XML like yours. Yeah, I know all of that. > > Childish behavior like yours only caused the interested people to go away. > And I really considered to go away. But the fact is I see I still can do > something useful with OI and don't want to give up too soon. Yeah, I know, > from my experience on this mail list, give up is most of the time the > answers! Sooner or later, I will have to give up. But I don't want to give > it up too soon. Got it? > Chassez le naturel... > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to install MATE or Gnome Desktop?
On Sat, Feb 13, 2021 at 4:12 PM John D Groenveld wrote: > In message <502174374.1119956.1613226927...@mail.yahoo.com>, Jason Long > via ope > nindiana-discuss writes: > >Thank you for your efforts, but doesn't work. I tested all kinds of VGA. > >I will install OI from a GUI version. > > Good luck, but I doubt it is an OI bug and instead is a VirtualBox. > I can't reproduce for guest running on top of VBox 6.1.18 for > MacOS and Windows. > Carl reported recently that 6.1.18 fixed a regression for Solarish hosts introduced in 6.1.0. Not sure if it is related. > > John > groenv...@acm.org > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] screen: CVE-2021-26937
Hi, make sure to update your screen package rather sooner than later. The new package will land in the repository within an hour. Kind regards, Aurélien -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] PostgreSQL 9.5 deprecation notice
Hi, during the migration to newer Python and the OpenSSL update, a few components delivered as 32-bit binaries will either be moved to 64-bit or phased out. According to https://www.postgresql.org/support/versioning/, PostgreSQL 9.5 the last 32/64-bit postgres we deliver, is EOL'ed on 11th February 2021. Therefore you are encouraged to migrate to a newer version as version 9.5 will be deprecated in our repository shortly after its official EOL. Note that PostgreSQL 9.6 will be phased out at the end of November 2021 as well. Kind regards, Aurélien -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Python modules update status
Hi, we are moving forward well with the migration. Out of 172 components: 1) 46 got Python 3.7 and 3.9 support (in bold pending for merge): argcomplete 2.7 3.5 3.7 3.9 atomicwrites 2.7 3.5 3.7 3.9 attrs 2.7 3.5 3.7 3.9 *automat* 3.5 3.7 3.9 chardet 2.7 3.5 3.7 3.9 *cheroot* 3.5 3.7 3.9 *cherrypy* 3.5 3.7 3.9 *constantly* 3.7 3.9 coverage 2.7 3.5 3.7 3.9 *hamcrest* 3.5 3.7 3.9 *hyperlink* 2.7 3.5 3.7 3.9 idna 2.7 3.5 3.7 3.9 importlib-metadata 2.7 3.5 3.7 3.9 incremental 2.7 3.5 3.7 3.9 iniconfig 3.5 3.7 3.9 mock 2.7 3.5 3.7 3.9 more-itertools 3.5 3.7 3.9 *nose* 3.5 3.7 3.9 packaging 2.7 3.5 3.7 3.9 *pexpect* 3.5 3.7 3.9 pip 2.7 3.5 3.7 3.9 pipdeptree 3.5 3.7 3.9 pluggy 2.7 3.5 3.7 3.9 *ptyprocess* 3.5 3.7 3.9 py 2.7 3.5 3.7 3.9 py-cpuinfo 3.5 3.7 3.9 pycodestyle 2.7 3.5 3.7 3.9 pylxml 2.7 3.5 3.7 3.9 pyparsing 3.5 3.7 3.9 pytest 3.5 3.7 3.9 pytest-benchmark 3.5 3.7 3.9 pytest-reporter 3.5 3.7 3.9 python-rapidjson 3.7 3.9 pytz 2.7 3.5 3.7 3.9 requests 2.7 3.5 3.7 3.9 setuptools 3.5 3.7 3.9 setuptools_scm 2.7 3.5 3.7 3.9 six 2.7 3.5 3.7 3.9 sortedcontainers 2.7 3.5 3.7 3.9 toml 3.5 3.7 3.9 twisted 3.5 3.7 3.9 urllib3 2.7 3.5 3.7 3.9 wcwidth 2.7 3.5 3.7 3.9 zc.lockfile 2.7 3.5 3.7 3.9 zipp 2.7 3.5 3.7 3.9 zope-interface 2.7 3.5 3.7 3.9 2) 46 are Python 2.7 only and some of them may simply be deprecated. Thanks to Andreas, Nona, and Gary for their help. Kind regards, Aurélien -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] A rant
On Fri, Jan 29, 2021 at 11:50 PM Lou Picciano wrote: > Reg, > > As a guy partly responsible (apologies!) for the list being generally > pretty quiet, the only contribution I can make to this at the moment is: > > Reg, You Da Man! > > (written from only a few miles from that Bell Labs you so rightly > mentioned…) > Hi, sorry everyone for the tone of recent messages to the mailing lists. While I did enjoy that these latter are less quiet than usual, discussions will hopefully now remain as courteous and as pleasant as they usually are. Thanks for your contributions. Kind regards, Aurélien > > Lou Picciano > > > > On Jan 29, 2021, at 4:47 PM, Reginald Beardsley via openindiana-discuss < > openindiana-discuss@openindiana.org> wrote: > > > > > > I have been ignoring this torrent of BS as patiently as I can, but I'm > really getting tired of it. > > > > First of all, computing has a 75 year old history. There have been many > false starts and mistakes along the way. The failure of the new arrivals to > learn from the past results in the same mistakes being endlessly repeated. > > > > I shall cite a single example from 30 years ago, hard coded filenames. > Motif came out with the name of the keyboard configuration file hard coded > "/etc/keysym.db" IIRC. A the time it was my job to compile and distribute > X11 and Motif binaries on all company research lab systems that did not > have vendor support for X11 and Motif. > > > > This is a common mistake made frequently before the IBM 360 series > appeared and led to "sysin=" and "sysout=" in JCL for the 360 series (That > may not be the exactly correct syntax, but this does not merit my going > into my library to check). But the "genius" who wrote the Motif code could > not be bothered with the past so he repeated the mistake. > > > > No one here "hates" Linux, BSD, Windows or any other OS. We don't like > various operating systems for a variety of legitimate reasons which vary by > task to be accomplished, OS and individual. > > > > Please read the original Bell Labs Unix papers before you subject us to > more of this. Linux has veered so far from the original principles as to be > completely unrecognizable. In any given day I may use Hipster/OI, Solaris > 10 u8, Debian 9.3 or Windows. And I might well spin up Plan 9 or some other > operating systems by inserting the appropriate disk in the machine. In > short, I can crush someone with your attitude in minutes even if they have > a PhD. And have done it more than once. > > > > At such time as you can write intelligently describing the differences > in implementation and philosophy about MVS (and its predecessors) , VM/CMS, > VMS, RSX, Genix, Multics, Perkin-Elmer 3200 OS and a few others you will > have some credibility with me. But until then you are just some child > screaming that they will "hold there breath until they turn blue". I am > quite certain I am not the only one *very* tired of it. I know the names of > most of the people who have been replying to you and have the utmost > respect for all but perhaps a few. Possibly all, as I've not paid close > attention to who replied. The list is generally pretty quiet except for an > occasional nut job. > > > > If you have many years professional experience as a senior member of > staff in large system environments you care about what seems minutiae to > novices. We care because we either got bit or had to clean up after someone > else got bit. Most of the people on this list have been involved in large > system environments for longer than you have been alive. > > > > It is certainly true that the organization of the filesystem in Illumos > et al is a bit of a mess. This is true in every extant OS. IRIX, CLIX, > HP-UX, Ultrix and a dozen other *nix systems I've used are long extinct. > One of the great problems during the workstation wars was dealing with all > the conflicting paths and file names. With xterms open on 6 or more > different systems using a common NFS mounted home directory I had a very > elaborate system for hiding the variations so I could work efficiently > despite the variations. I supported software, both proprietary and GNU > packages across all of them. > > > > Please reply to /dev/null. > > > > Reg > > On Thursday, January 28, 2021, 09:31:12 PM CST, Hung Nguyen Gia via > openindiana-discuss wrote: > > > > Anyone here seems to be hated Linux too much. Does it because their bad > past experience with it or simply because Linux is success and we are loser > and the natural law of the loser hate the winner? > > > > Someone used to said Linux is a cesspool because it's only a kernel and > hacked together to create a working system. > > > > Today I cloned illumos-gate and I see the completely different. > > > > I think Linux is more organized than Illumos. > > > > Saying Linux is a hacked together work is hypocrite and indeed slapping > back into our own faces. > > > > We are no different. Illumos is a hacked together work and was
Re: [OpenIndiana-discuss] python-gi in OI?
On Mon, Jan 25, 2021 at 1:25 PM Tony Brian Albers wrote: > Hi guys, > > I'm trying to get virt-manager to work. But it complains about not being > able to load gi: > > tba@emu:/opt$ virt-manager > Traceback (most recent call last): >File "/usr/bin/virt-manager", line 6, in > from virtManager import virtmanager >File "/usr/share/virt-manager/virtManager/virtmanager.py", line 15, > in > import gi > ModuleNotFoundError: No module named 'gi' > tba@emu:/opt$ > > > Does anyone know if we have gi somewhere? > It does not look like we do: https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/python You can add it by copying the recipe: https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/python/zipp and change the relevant information, set PYTHON_VERSION to $(PYTHON3_VERSIONS) only. You can execute gmake prep to get the sha256 sum to replace. Then: 1) Copy the LICENSE file to gi.license 2) Rename the p5m file to gi-PYVER.p5m 3) Execute gmake sample-manifest 4) Copy the relevant entries from manifests/generic-manifest.p5m to gi-PYVER.p5m 5) Try gmake pre-publish If this fails with undefined dependencies, regenerate the list of deps using 'gmake REQUIRED_PACKAGES'. 6) Cleanup REQUIRED_PACKAGES in the Makefile to remove duplicates. 7) gmake publish (this should pass except if some specific packaging tricks need be pulled, in which case post the details here) 8) git add Makefile gi.license gi-PYVER.p5m manifests pkg5 9) git commit -m "gi: add version XXX" 10) Push your branch and open a PR. Optionally you can install pipdeptree-39 to inspect if all the required dependencies are installed. > pip fails because python.org has disabled their xmlrpc service because > of a DoS problem. (https://status.python.org/) > > TIA > > /tony > > -- > Tony Albers - Systems Architect - IT Development Royal Danish Library, > Victor Albecks Vej 1, 8000 Aarhus C, Denmark > Tel: +45 2566 2383 - CVR/SE: 2898 8842 - EAN: 5798000792142 > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to add a new package to distibution construction?
On Mon, Jan 25, 2021 at 1:56 AM Hung Nguyen Gia via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > So no one know how to do it? > You should add the package FMRI in the distribution constructor manifest like I should in the thread about nano. Add it to one of the manifests included in slim_cd. However sunpro is not available anymore from our repo for legal reasons, it was obsoleted some weeks ago. Also I just remembered that you ask why we do not have cc,c++,cxx etc.. in /usr/bin... I forgot to reply... A lot of software assumes that if /usr/bin/cc is found then it is Sunstudio and sets it as default without checking that it is actually another compiler e.g. GCC. We had to refrain from providing the symlinks in /usr/bin to work around such ill-defined behaviour... > > > > On Sun, 24 Jan 2021 23:11:17 +0700 Hung Nguyen Gia via > openindiana-discuss wrote > > > e.g: I wanted to add the sunpro package into slim_cd_x86.xml > > > > How could I do it? > > > > I found this xml doesn't contain any list of packages to be used at > all. > > > > Please help. Thanks. > > > > ___ > > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] When will AMD XIII CPUs be supported
On Fri, Jan 22, 2021 at 7:45 AM Hung Nguyen Gia via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > Well well. Except sometimes it's stuck for eternity. > > https://www.illumos.org/issues/12963 > > The only solution is to cold reset. It corrupted the disk. > The only way to reuse this disk is from another system using dd > if=/dev/zero to zero fill it. > Even if it's SSD, it took almost an hour to complete. > > Now see the problem? > > This is another reason no one uses your system. > Deployment speed is a very important factor the production. > > Hope it helps. > > BTW, you see? No one cares about the issue I reported. Not even a single > comment to indicate that they do care! > > People here always said that I have disrespected them. > > BS! Pure BS! See who being disrespected? > > They treat me like nothing! > > Don't ever talk about disrespect or something like that with me. > > Otherwise we can't have a respectful conversation. > Hello, can we please keep the discussion focused on solving the problem rather than finger pointing? I'd like to ask you to stop disrupting threads the way you have done in the past week. There is a lot of work to do here and limited manpower, we need all the positive energy possible to keep sailing :) Do not interpret lack of reply to your tickets as disrespect or contempt: we are all volunteers here, contributing in our spare time to help each other. Joshua replied to you in a very inspiring way, I hope his message was understood. However if you can't exchange with people in a courteous manner I'll have to keep you out of the mailing list for some time. Please know that this is something I'd like to avoid as you have been otherwise dynamic and engaging: raising issues is appreciated and discussing problems is encouraged. We can all be frustrated with different limitations and bugs: the way to go is to stay positive and address problems one by one the best we can and as time permits. Kind regards, Aurélien > > > > > On Fri, 22 Jan 2021 13:07:28 +0700 Stephan Althaus > wrote > > > > > Personally i don't care much about install time. Really! > > > > Greetings, > > > > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] distribution constructor for making OI spins?
On Wed, Jan 20, 2021 at 11:00 PM Chris wrote: > On 2021-01-20 13:32, Aurélien Larcher wrote: > > On Wed, Jan 20, 2021 at 10:19 PM Chris wrote: > > > >> On 2021-01-20 12:47, Tim Mooney via openindiana-discuss wrote: > >> > In regard to: Re: [OpenIndiana-discuss] distribution constructor for > >> > making...: > >> > > >> >> On 2021-01-20 04:09, Tim Mooney via openindiana-discuss wrote: > >> >>> In regard to: Re: [OpenIndiana-discuss] distribution constructor for > >> >>> making...: > >> >>> > >> >>>> I would love to have XFCE. > >> >>>> > >> >>>> But as I know, the OI devs will not package other DEs. They stay > >> royal to > >> >>>> MATE. > >> >>>> > >> >>>> You can't found any other DE's packages on the repo. > >> >>> > >> >>> You might want to review the mailing list archives for this mailing > >> list > >> >>> to get a clearer understanding of why that is. It's been discussed > >> >>> before. > >> >>> > >> >>> If you or Chris or someone else builds an entire desktop environment > >> >>> like Cinnamon and publishes a repo that is kept up to date, I would > >> >>> definitely give it a try, at least in a VM. If someone does this > and > >> >>> keeps it up to date for a long time and continues to contribute to > OI, > >> >>> I would probably use that as my main desktop environment. > >> >>> > >> >>> Just building it once, without a commitment to keeping it updated, > >> isn't > >> >>> good for anyone, though. > >> >> TBH The only reason OI isn't my "daily driver" is the DE available. > If I > >> >> had XFCE (what I currently use), or better, Cinnamon. I'd have a hard > >> time > >> >> not using OI. Overall I like it better. But I'm (currently) pretty > well > >> >> committed to FreeBSD as maintainer of some 160 ports, and I create > >> >> installs for all my servers && clients. I've been on BSD since Bill > Joy > >> >> forked 386BSD, and hacked on various NIX' before that. But if I could > >> >> cobble up an OI I could justify as a "daily driver", and something I > >> could > >> >> recommend to my clients. I'd make the switch. > >> >> Which brings me to why I initiated this thread. Since I need > commitment > >> >> to justfy *my* commitment. I thought I'd send out a "feeler" to see > if > >> >> there was any interest. Appears I'm not the only one. So I'm going to > >> >> "take the plunge". I'll start gathering all the information I need to > >> get > >> >> all the dots in a line, so I can start production. Any pointers to > help > >> >> shorten the trajectory would be *greatly* appreciated. As well as > >> keeping > >> >> the wiki working. ;-) > >> > > >> > I'm indifferent to Xfce, but when you start working on Cinnamon and > deps, > >> > that's something that I would be happy to collaborate on and test. > >> That's my *ideal* target. I really like working in Cinnamon, and want to > >> transform my current workspace from XFCE to Cinnamon. So I'll definitely > >> include you in the loop when I start on it. :-) > >> > oi-dev and the irc channels are your best source for help on porting, > >> > and I've gotten good feedback in PRs where I've asked questions or > been > >> > stuck part way through updating or porting a package. > >> > > >> > Also, rather than the wiki, I would highly recommend > >> > > >> > http://docs.openindiana.org/ > >> > > >> > and then "HandBook->Building with oi-userland". That's been migrated > >> from > >> > the old wiki page and updated and had some corrections and a few > >> > clarifications added. There may still be improvements that could be > >> made, > >> > so the > >> > first few times through the process, please pay special attention > >> > to places where that document misses information or appears incorrect. > >> If > >> > you mention the issues on oi-dev, I'll get PRs submitted (or you can, > >> > if you fork the docs too) to try imp
Re: [OpenIndiana-discuss] distribution constructor for making OI spins?
On Wed, Jan 20, 2021 at 10:39 PM Chris wrote: > On 2021-01-20 13:03, Andreas Wacknitz wrote: > > Am 20.01.21 um 21:47 schrieb Tim Mooney via openindiana-discuss: > >> In regard to: Re: [OpenIndiana-discuss] distribution constructor for > >> making...: > >> > >>> On 2021-01-20 04:09, Tim Mooney via openindiana-discuss wrote: > In regard to: Re: [OpenIndiana-discuss] distribution constructor for > making...: > > > I would love to have XFCE. > > > > But as I know, the OI devs will not package other DEs. They stay > > royal to MATE. > > > > You can't found any other DE's packages on the repo. > > You might want to review the mailing list archives for this mailing > list > to get a clearer understanding of why that is. It's been discussed > before. > > If you or Chris or someone else builds an entire desktop environment > like Cinnamon and publishes a repo that is kept up to date, I would > definitely give it a try, at least in a VM. If someone does this and > keeps it up to date for a long time and continues to contribute to OI, > I would probably use that as my main desktop environment. > > Just building it once, without a commitment to keeping it updated, > isn't > good for anyone, though. > >>> TBH The only reason OI isn't my "daily driver" is the DE available. If > I > >>> had XFCE (what I currently use), or better, Cinnamon. I'd have a hard > >>> time > >>> not using OI. Overall I like it better. But I'm (currently) pretty well > >>> committed to FreeBSD as maintainer of some 160 ports, and I create > >>> installs for all my servers && clients. I've been on BSD since Bill Joy > >>> forked 386BSD, and hacked on various NIX' before that. But if I could > >>> cobble up an OI I could justify as a "daily driver", and something I > >>> could > >>> recommend to my clients. I'd make the switch. > >>> Which brings me to why I initiated this thread. Since I need commitment > >>> to justfy *my* commitment. I thought I'd send out a "feeler" to see if > >>> there was any interest. Appears I'm not the only one. So I'm going to > >>> "take the plunge". I'll start gathering all the information I need to > >>> get > >>> all the dots in a line, so I can start production. Any pointers to help > >>> shorten the trajectory would be *greatly* appreciated. As well as > >>> keeping > >>> the wiki working. ;-) > >> > >> I'm indifferent to Xfce, but when you start working on Cinnamon and > deps, > >> that's something that I would be happy to collaborate on and test. > >> oi-dev > >> and the irc channels are your best source for help on porting, > I find IRC stressful while I'm working, and somewhat hard to keep up on > (the threads). FreeBSD has a discord channel > (https://discord.com/channels/) -- IRC but also Web && app based. I find > that pretty darn easy to keep up with, and the (web based) UI really > lends itself to getting things done. Oh, and it's free. Works on yer > so-called smart/handheld devices too. :-) > We actually have a Discord channel for OI devs already, but IRC has been the primary entry point for newcomers. > >> and I've > >> gotten good feedback in PRs where I've asked questions or been stuck > >> part way through updating or porting a package. > >> > >> Also, rather than the wiki, I would highly recommend > >> > >> http://docs.openindiana.org/ > >> > >> and then "HandBook->Building with oi-userland". That's been migrated > >> from > >> the old wiki page and updated and had some corrections and a few > >> clarifications added. There may still be improvements that could be > >> made, so the first few times through the process, please pay special > >> attention > >> to places where that document misses information or appears > >> incorrect. If > >> you mention the issues on oi-dev, I'll get PRs submitted (or you can, > >> if you fork the docs too) to try improve things. > >> > >> Tim > > I will happily merge enhancements to oi-docs. > > And one more thing: We share the Sun Solaris ancestry with Oracle > > Solaris. Some things have diverted during the last decade but the > > solaris-userland > > repository is a first-class source of information and inspiration. > That's a good point, and I considered it. But I was unsure as to the > extent of any divergence. > > > > Andreas > > > --Chris > > -- > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] distribution constructor for making OI spins?
On Wed, Jan 20, 2021 at 10:19 PM Chris wrote: > On 2021-01-20 12:47, Tim Mooney via openindiana-discuss wrote: > > In regard to: Re: [OpenIndiana-discuss] distribution constructor for > > making...: > > > >> On 2021-01-20 04:09, Tim Mooney via openindiana-discuss wrote: > >>> In regard to: Re: [OpenIndiana-discuss] distribution constructor for > >>> making...: > >>> > I would love to have XFCE. > > But as I know, the OI devs will not package other DEs. They stay > royal to > MATE. > > You can't found any other DE's packages on the repo. > >>> > >>> You might want to review the mailing list archives for this mailing > list > >>> to get a clearer understanding of why that is. It's been discussed > >>> before. > >>> > >>> If you or Chris or someone else builds an entire desktop environment > >>> like Cinnamon and publishes a repo that is kept up to date, I would > >>> definitely give it a try, at least in a VM. If someone does this and > >>> keeps it up to date for a long time and continues to contribute to OI, > >>> I would probably use that as my main desktop environment. > >>> > >>> Just building it once, without a commitment to keeping it updated, > isn't > >>> good for anyone, though. > >> TBH The only reason OI isn't my "daily driver" is the DE available. If I > >> had XFCE (what I currently use), or better, Cinnamon. I'd have a hard > time > >> not using OI. Overall I like it better. But I'm (currently) pretty well > >> committed to FreeBSD as maintainer of some 160 ports, and I create > >> installs for all my servers && clients. I've been on BSD since Bill Joy > >> forked 386BSD, and hacked on various NIX' before that. But if I could > >> cobble up an OI I could justify as a "daily driver", and something I > could > >> recommend to my clients. I'd make the switch. > >> Which brings me to why I initiated this thread. Since I need commitment > >> to justfy *my* commitment. I thought I'd send out a "feeler" to see if > >> there was any interest. Appears I'm not the only one. So I'm going to > >> "take the plunge". I'll start gathering all the information I need to > get > >> all the dots in a line, so I can start production. Any pointers to help > >> shorten the trajectory would be *greatly* appreciated. As well as > keeping > >> the wiki working. ;-) > > > > I'm indifferent to Xfce, but when you start working on Cinnamon and deps, > > that's something that I would be happy to collaborate on and test. > That's my *ideal* target. I really like working in Cinnamon, and want to > transform my current workspace from XFCE to Cinnamon. So I'll definitely > include you in the loop when I start on it. :-) > > oi-dev and the irc channels are your best source for help on porting, > > and I've gotten good feedback in PRs where I've asked questions or been > > stuck part way through updating or porting a package. > > > > Also, rather than the wiki, I would highly recommend > > > > http://docs.openindiana.org/ > > > > and then "HandBook->Building with oi-userland". That's been migrated > from > > the old wiki page and updated and had some corrections and a few > > clarifications added. There may still be improvements that could be > made, > > so the > > first few times through the process, please pay special attention > > to places where that document misses information or appears incorrect. > If > > you mention the issues on oi-dev, I'll get PRs submitted (or you can, > > if you fork the docs too) to try improve things. > In all honesty; OI could *really* use some DOC love -- > consolidation/updating. I had a devil of a time discovering where the "truth" was located. It's > currently > fragmented, and out-of-date -- mind you, I'm not shaking my finger at > anyone > here. > Just sharing my current struggle in this regard. If it were to get > consolidated. > I think many more might feel inclined to get onboard w/OI. > Trouble is that we called for contributions to migrate and enrich the new documentation but it never gained momentum. I started writing a maintainer's guide on the Wiki before the migration but have absolutely zero time to dedicate to its migration to the new doc system. Alexander did move some pages to: https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/doc > I'm currently using: https://github.com/OpenIndiana/oi-userland as my > source > of > truth. Having been a (ports/package) maintainer on FreeBSD for some 10yrs. > I'm > finding it enough to read the shell framework to get up to speed. My only > *personal* > nit; is that it's largely bash(1) based. Maybe it's because I'm more used > to > sh(1). > But I find bash to be a bit of a pig, by comparison. But I can get used to > it > -- or > just rewrite all of it in sh(1). ;-) > > Tim, thank you *very* much for all the pointers, and support! :-) > We'll be talking Cinnamon, real soon now. ;-) > > --Chris > > > > Tim > > -- > > ___ > openindiana-discuss
Re: [OpenIndiana-discuss] distribution constructor for making OI spins?
On Wed, Jan 20, 2021 at 9:47 PM Tim Mooney via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > In regard to: Re: [OpenIndiana-discuss] distribution constructor for > making...: > > > On 2021-01-20 04:09, Tim Mooney via openindiana-discuss wrote: > >> In regard to: Re: [OpenIndiana-discuss] distribution constructor for > >> making...: > >> > >>> I would love to have XFCE. > >>> > >>> But as I know, the OI devs will not package other DEs. They stay royal > to > >>> MATE. > >>> > >>> You can't found any other DE's packages on the repo. > >> > >> You might want to review the mailing list archives for this mailing list > >> to get a clearer understanding of why that is. It's been discussed > >> before. > >> > >> If you or Chris or someone else builds an entire desktop environment > >> like Cinnamon and publishes a repo that is kept up to date, I would > >> definitely give it a try, at least in a VM. If someone does this and > >> keeps it up to date for a long time and continues to contribute to OI, > >> I would probably use that as my main desktop environment. > >> > >> Just building it once, without a commitment to keeping it updated, isn't > >> good for anyone, though. > > TBH The only reason OI isn't my "daily driver" is the DE available. If I > > had XFCE (what I currently use), or better, Cinnamon. I'd have a hard > time > > not using OI. Overall I like it better. But I'm (currently) pretty well > > committed to FreeBSD as maintainer of some 160 ports, and I create > > installs for all my servers && clients. I've been on BSD since Bill Joy > > forked 386BSD, and hacked on various NIX' before that. But if I could > > cobble up an OI I could justify as a "daily driver", and something I > could > > recommend to my clients. I'd make the switch. > > Which brings me to why I initiated this thread. Since I need commitment > > to justfy *my* commitment. I thought I'd send out a "feeler" to see if > > there was any interest. Appears I'm not the only one. So I'm going to > > "take the plunge". I'll start gathering all the information I need to get > > all the dots in a line, so I can start production. Any pointers to help > > shorten the trajectory would be *greatly* appreciated. As well as keeping > > the wiki working. ;-) > > I'm indifferent to Xfce, but when you start working on Cinnamon and deps, > that's something that I would be happy to collaborate on and test. Something to keep in mind is that if you focus on another desktop then you may leave behind features like the Time Slider that we have spent a ridiculous amount of time porting from Gnome 2 to MATE and then resynchronizing at each MATE iteration. > oi-dev > and the irc channels are your best source for help on porting, and I've > gotten good feedback in PRs where I've asked questions or been stuck > part way through updating or porting a package. > > Also, rather than the wiki, I would highly recommend > > http://docs.openindiana.org/ > > and then "HandBook->Building with oi-userland". That's been migrated from > the old wiki page and updated and had some corrections and a few > clarifications added. There may still be improvements that could be made, > so the first few times through the process, please pay special attention > to places where that document misses information or appears incorrect. If > you mention the issues on oi-dev, I'll get PRs submitted (or you can, > if you fork the docs too) to try improve things. > > Tim > -- > Tim Mooney tim.moo...@ndsu.edu > Enterprise Computing & Infrastructure / > Division of Information Technology/701-231-1076 (Voice) > North Dakota State University, Fargo, ND 58105-5164 > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] distribution constructor for making OI spins?
On Wednesday, January 20, 2021, Hung Nguyen Gia via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > I would love to have XFCE. > > But as I know, the OI devs will not package other DEs. They stay royal to MATE. > > You can't found any other DE's packages on the repo. > > There are packages for many window manager, though. > > You have to do pretty much anything yourself, with your own repo publisher. > > BTW, at least I know XFCE is possible on Illumos. Tribblix's default desktop is XFCE. > > I don't have much hope about Cinnamon. But if you can bring it up, I would love to have it, too. Hello, it is not really about being loyal to MATE but commiting to maintain the packages. When swithing to gcc 10 I had to patch a few dozen packages that I do not use or maintain but the original maintainer had no time or interest to fix it. We want to avoid situations were large pieces of software are added then left to rot. This is unfortunately the case for some important packahes due to recent circumstances that have reduced our number of maintainers drastically. There is not strong opinion against packages in general, just a question of commitment to maintain them. XFCE would be nice indeed, I packaged it back in OpenSolaris days :) Cheers, Aurélien > > > > > On Wed, 20 Jan 2021 13:55:13 +0700 Chris wrote > > > Well I was finally able to get OI on one of my spares. > > I wanted to do so, so that I could start adding/upgrading > > some OI packages. As I began looking at the process I > > stumbled on distribution-constructor and thought; why > > not build up some additional desktop installs. I had > > intended to build both the Xfce4 and Cinnamon desktop > > packages anyway. So why not ask to see if the any > > OI users/developers/caretakers would be interested in > > providing xfce4 or cinnamon desktop ISO and USB images. > > Would something like this be of any interest? > > If so. I'll start building all the necessary bits straight > > away. > > > > Thanks for your feedback. > > > > --Chris > > -- > > > > ___ > > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The bug is still present
On Tue, Jan 19, 2021 at 6:25 PM Hung Nguyen Gia wrote: > If I can, at all. As I said, I have no idea why it crashed. > > It crashed somewhat randomly. But out of 10 attempts, I think it would > crashed 8. It's the most unreliable piece of software I ever seen. > > The last time it crashed as I recall, I opened one of the source file of > the last swt version supports Solaris, swt 4.6.3, when I hit the close > button of the tab it crashed. > > So, it could be it crashed when you only have one tab left but click to > close this tab but not the close button of the window itself. > The likely explanation is that one of the graphical libraries was not recompiled correctly. My install has zero problems but the graphical libraries have not been updated since last autumn as they were published from my own gcc-10 built repository. Let us bisect then ;) > > > > > On Wed, 20 Jan 2021 00:16:17 +0700 Aurélien Larcher < > aurelien.larc...@gmail.com> wrote > > > > > > OK, at least can you tell me how to (almost) reliably crash Pluma for > instance? > > > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The bug is still present
On Tue, Jan 19, 2021 at 6:15 PM Hung Nguyen Gia wrote: > I'm not very polite but not a bad guy at all on the illumos issues page. > > I'm only bad on this mailing list, to be clear. > Of course I have the core file, but can't upload it. > > If I attach the OI disk into my system, the stupid BIOS will prevent the > whole system from booting. > > My hardware doesn't support hot plug of disk, too. > OK, at least can you tell me how to (almost) reliably crash Pluma for instance? > > > > On Wed, 20 Jan 2021 00:08:08 +0700 Aurélien Larcher < > aurelien.larc...@gmail.com> wrote > > > > > > > On Tue, Jan 19, 2021 at 5:54 PM Hung Nguyen Gia > wrote: > > I'm not gonna to register on that illumos issues page again since I > found like I'm talking to the wall and no one cares. The fact is my > previous account there also lost with my previous email address. So I > answer you here. > > > > https://www.illumos.org/issues/13112 > > > > The bug is still present. It's my honest answer. > > > > You didn't fix it. Nothing changed at all. > > > > Probably if you were more polite people would care more about your > issues... > > > > Maybe look upstream if a similar issue has been reported, the desktop > code is barely patched. > > If you have a core file you could attach it as well to the ticket. > > > > -- > > --- > > Praise the Caffeine embeddings > > > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The bug is still present
On Tue, Jan 19, 2021 at 6:11 PM Hung Nguyen Gia wrote: > Not only pluma. Graphical applications (especially GTK3 based), crashing > very easily. > > Not to mention the gnome keyring app that always crashed and core dumped. > I have Mate terminal crashed for me, too. > > But gnome keyring is trivial. As it crashed all they way for me on systems > other than Linux (the BSDs, to be clear). > > I never had the terminal emulator, Mate terminal or similar things, > crashed for me on those system, though. Only on OI. > > Graphical applications are highly unstable on OI. > > Everything is very easy to crash and I have no idea why. > > The only piece of graphical software that most stable on OI is, Geany and > ... Pale Moon. > > Please note that Geany is build with GTK2, though, at least the version I > got from OI's repo. > > The Pale Moon I said is build with GTK2, too. The GTK3 Pale Moon I already > have, but not used it much so I don't know if it's as stable as the GTK2 > version or not. > > I have to remove the OI disk from my system before I could do something > more with the GTK3 Pale Moon other than loading some simple mostly text > pages. > I am asking you for a reproducer not a rant. > > > > > On Tue, 19 Jan 2021 23:54:46 +0700 Hung Nguyen Gia via > openindiana-discuss wrote > > > I'm not gonna to register on that illumos issues page again since I > found like I'm talking to the wall and no one cares. The fact is my > previous account there also lost with my previous email address. So I > answer you here. > > > > https://www.illumos.org/issues/13112 > > > > The bug is still present. It's my honest answer. > > > > You didn't fix it. Nothing changed at all. > > > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The bug is still present
On Tue, Jan 19, 2021 at 5:54 PM Hung Nguyen Gia wrote: > I'm not gonna to register on that illumos issues page again since I found > like I'm talking to the wall and no one cares. The fact is my previous > account there also lost with my previous email address. So I answer you > here. > > https://www.illumos.org/issues/13112 > > The bug is still present. It's my honest answer. > > You didn't fix it. Nothing changed at all. > Probably if you were more polite people would care more about your issues... Maybe look upstream if a similar issue has been reported, the desktop code is barely patched. If you have a core file you could attach it as well to the ticket. -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Shell to use?
On Tue, Jan 19, 2021 at 5:20 PM Hung Nguyen Gia via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > Everything on OI is too slow, so I decided to go another route. > > I tried with bash as default shell on FreeBSD and the result is the same. > > Also tried on Debian 10 with export SH=/bin/bash, it's pretty much as fast > as on FreeBSD if not to say faster. > > Bash maybe not the problem. > Have you profiled gnu make? > > > > > On Tue, 19 Jan 2021 12:38:28 +0700 edward > wrote > > > > > On 1/18/21 8:27 PM, Hung Nguyen Gia via openindiana-discuss wrote: > > > The output printed on the screen 'Checking for...' is line by line, > very slow. Meanwhile, the same thing on FreeBSD is blazing fast that I > can't even see what's going on at all. > > > > suggest to try the same type of shell freebsd uses? > > > > > > > > ___ > > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Python 3.7 and 3.9
> > 1) Migrate away from 3.5 to 3.7 as the default Python implementation. > First steps of the week, the following modules were updated and support for Python 3.7 and 3.9 was added: argcomplete atomicwrites attrs chardet coverage funcsigs hypothesis idna importlib-metadata incremental ipaddress mock more-itertools packaging pathlib2 pluggy ptyprocess py pycodestyle pytest rapidjson requests scandir setuptools setuptools_scm six sortedcontainers urllib3 zipp zope.interface Updated to use Python 3.9: ninja meson Deprecation: pytest-27 -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] shouldn't uname report 64 bit arch?
On Sat, Jan 16, 2021 at 9:49 PM Pierfrancesco Caci wrote: > I'm not yet arrived at the point where I'm confident that I can modify the > components tree. I'm trying to compile from the git source of this module. > Let me see if I can pass those CFLAGS and LDFLAGS to ./configure somehow. > To help you, that were the flags are defined: https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/make-rules/shared-macros.mk#L1193 and where they are passed to configure: https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/make-rules/configure.mk#L87 > brb > > On Sat, Jan 16, 2021 at 9:45 PM Aurélien Larcher < > aurelien.larc...@gmail.com> > wrote: > > > On Sat, Jan 16, 2021 at 9:12 PM Pierfrancesco Caci > > wrote: > > > > > Hello, > > > I'm trying to compile xf86-video-qxl. It comes out as 32 bits, instead > of > > > 64. > > > > > > $ file /usr/local/lib/xorg/modules/drivers/qxl_drv.so > > > /usr/local/lib/xorg/modules/drivers/qxl_drv.so: ELF 32-bit LSB dynamic > > lib > > > 80386 Version 1, dynamically linked, not stripped > > > > > > > Also all GCC <= 8 default to generating 32-bit binaries for historical > > reasons (32-bit was the lowest common denominator to the i86pc arch). > > > > GCC 9 and 10 default to 64-bit as i386 is not relevant anymore. > > > > Build recipes for X11 components are at: > > > > > https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/x11/ > > > > The build system sets required flags to generate 64-bit (e.g. > CFLAGS=-m64, > > LDFLAGS=-m64). > > > > For simplicity you can add a new component in this tree based on existing > > recipes. > > > > > > > > > > > for comparison: > > > $ file /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so > > > /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so:ELF 64-bit LSB > > > dynamic lib AMD64 Version 1, dynamically linked, not stripped, no > > debugging > > > information available > > > > > > I checked configure.log and it clearly gets the 32 bit info here: > > > > > > $ ./configure --disable-selective-werror > > > > > > ## - ## > > > ## Platform. ## > > > ## - ## > > > > > > hostname = openindiana > > > uname -m = i86pc > > > uname -r = 5.11 > > > uname -s = SunOS > > > uname -v = illumos-dea3b85466 > > > > > > /usr/bin/uname -p = i386 > > > /bin/uname -X = System = SunOS > > > Node = openindiana > > > Release = 5.11 > > > KernelID = illumos-dea3b85466 > > > Machine = i86pc > > > BusType = > > > Serial = > > > Users = > > > OEM# = 0 > > > Origin# = 1 > > > NumCPU = 6 > > > > > > /bin/arch = i86pc > > > /usr/bin/arch -k = i86pc > > > /usr/convex/getsysinfo = unknown > > > /usr/bin/hostinfo = unknown > > > /bin/machine = unknown > > > /usr/bin/oslevel = unknown > > > /bin/universe = unknown > > > [etc] > > > > > > I checked also the OmniOS VM and that also reports i86pc. > > > So, am I misunderstanding something, or did I just find a bug in uname? > > > > > > Pf > > > -- > > > Pierfrancesco Caci, ik5pvx > > > ___ > > > openindiana-discuss mailing list > > > openindiana-discuss@openindiana.org > > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > > > > > -- > > --- > > Praise the Caffeine embeddings > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > -- > Pierfrancesco Caci, ik5pvx > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] shouldn't uname report 64 bit arch?
On Sat, Jan 16, 2021 at 9:46 PM Pierfrancesco Caci wrote: > understood. How do I tell ./configure to compile for 64 bit then? It is > basically using the wrong test to decide the architecture, but I don't know > how to change it. > Passing -m64 is enough. > I can see that config.guess has this portion: > > >i86pc:SunOS:5.*:* | i86xen:SunOS:5.*:*) > set_cc_for_build > SUN_ARCH=i386 > # If there is a compiler, see if it is configured for 64-bit > objects. > # Note that the Sun cc does not turn __LP64__ into 1 like gcc does. > # This test works for both compilers. > if test "$CC_FOR_BUILD" != no_compiler_found; then > if (echo '#ifdef __amd64'; echo IS_64BIT_ARCH; echo '#endif') | > \ > (CCOPTS="" $CC_FOR_BUILD -E - 2>/dev/null) | \ > grep IS_64BIT_ARCH >/dev/null > then > SUN_ARCH=x86_64 > fi > fi > > not sure if it is relevant though. > > On Sat, Jan 16, 2021 at 9:36 PM Aurélien Larcher < > aurelien.larc...@gmail.com> > wrote: > > > On Sat, Jan 16, 2021 at 9:12 PM Pierfrancesco Caci > > wrote: > > > > > Hello, > > > I'm trying to compile xf86-video-qxl. It comes out as 32 bits, instead > of > > > 64. > > > > > > $ file /usr/local/lib/xorg/modules/drivers/qxl_drv.so > > > /usr/local/lib/xorg/modules/drivers/qxl_drv.so: ELF 32-bit LSB dynamic > > lib > > > 80386 Version 1, dynamically linked, not stripped > > > > > > for comparison: > > > $ file /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so > > > /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so:ELF 64-bit LSB > > > dynamic lib AMD64 Version 1, dynamically linked, not stripped, no > > debugging > > > information available > > > > > > I checked configure.log and it clearly gets the 32 bit info here: > > > > > > $ ./configure --disable-selective-werror > > > > > > ## - ## > > > ## Platform. ## > > > ## - ## > > > > > > hostname = openindiana > > > uname -m = i86pc > > > uname -r = 5.11 > > > uname -s = SunOS > > > uname -v = illumos-dea3b85466 > > > > > > /usr/bin/uname -p = i386 > > > /bin/uname -X = System = SunOS > > > Node = openindiana > > > Release = 5.11 > > > KernelID = illumos-dea3b85466 > > > Machine = i86pc > > > BusType = > > > Serial = > > > Users = > > > OEM# = 0 > > > Origin# = 1 > > > NumCPU = 6 > > > > > > /bin/arch = i86pc > > > /usr/bin/arch -k = i86pc > > > /usr/convex/getsysinfo = unknown > > > /usr/bin/hostinfo = unknown > > > /bin/machine = unknown > > > /usr/bin/oslevel = unknown > > > /bin/universe = unknown > > > [etc] > > > > > > I checked also the OmniOS VM and that also reports i86pc. > > > So, am I misunderstanding something, or did I just find a bug in uname? > > > > > > > On Solaris/illumos i86pc denotes the architecture encompassing x86 and > > x86_64, here called i386 and amd64 respectively. > > > > The command 'isainfo' returns the supported Instruction Set Architectures > > (ISA) for the machine while 'isalist' returns all the extensions. > > > > narval> isainfo > > amd64 i386 > > narval> isalist > > amd64 pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86 > > > > > > > Pf > > > -- > > > Pierfrancesco Caci, ik5pvx > > > ___ > > > openindiana-discuss mailing list > > > openindiana-discuss@openindiana.org > > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > > > > > -- > > --- > > Praise the Caffeine embeddings > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > -- > Pierfrancesco Caci, ik5pvx > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] shouldn't uname report 64 bit arch?
On Sat, Jan 16, 2021 at 9:12 PM Pierfrancesco Caci wrote: > Hello, > I'm trying to compile xf86-video-qxl. It comes out as 32 bits, instead of > 64. > > $ file /usr/local/lib/xorg/modules/drivers/qxl_drv.so > /usr/local/lib/xorg/modules/drivers/qxl_drv.so: ELF 32-bit LSB dynamic lib > 80386 Version 1, dynamically linked, not stripped > Also all GCC <= 8 default to generating 32-bit binaries for historical reasons (32-bit was the lowest common denominator to the i86pc arch). GCC 9 and 10 default to 64-bit as i386 is not relevant anymore. Build recipes for X11 components are at: https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/x11/ The build system sets required flags to generate 64-bit (e.g. CFLAGS=-m64, LDFLAGS=-m64). For simplicity you can add a new component in this tree based on existing recipes. > for comparison: > $ file /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so > /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so:ELF 64-bit LSB > dynamic lib AMD64 Version 1, dynamically linked, not stripped, no debugging > information available > > I checked configure.log and it clearly gets the 32 bit info here: > > $ ./configure --disable-selective-werror > > ## - ## > ## Platform. ## > ## - ## > > hostname = openindiana > uname -m = i86pc > uname -r = 5.11 > uname -s = SunOS > uname -v = illumos-dea3b85466 > > /usr/bin/uname -p = i386 > /bin/uname -X = System = SunOS > Node = openindiana > Release = 5.11 > KernelID = illumos-dea3b85466 > Machine = i86pc > BusType = > Serial = > Users = > OEM# = 0 > Origin# = 1 > NumCPU = 6 > > /bin/arch = i86pc > /usr/bin/arch -k = i86pc > /usr/convex/getsysinfo = unknown > /usr/bin/hostinfo = unknown > /bin/machine = unknown > /usr/bin/oslevel = unknown > /bin/universe = unknown > [etc] > > I checked also the OmniOS VM and that also reports i86pc. > So, am I misunderstanding something, or did I just find a bug in uname? > > Pf > -- > Pierfrancesco Caci, ik5pvx > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] shouldn't uname report 64 bit arch?
On Sat, Jan 16, 2021 at 9:12 PM Pierfrancesco Caci wrote: > Hello, > I'm trying to compile xf86-video-qxl. It comes out as 32 bits, instead of > 64. > > $ file /usr/local/lib/xorg/modules/drivers/qxl_drv.so > /usr/local/lib/xorg/modules/drivers/qxl_drv.so: ELF 32-bit LSB dynamic lib > 80386 Version 1, dynamically linked, not stripped > > for comparison: > $ file /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so > /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so:ELF 64-bit LSB > dynamic lib AMD64 Version 1, dynamically linked, not stripped, no debugging > information available > > I checked configure.log and it clearly gets the 32 bit info here: > > $ ./configure --disable-selective-werror > > ## - ## > ## Platform. ## > ## - ## > > hostname = openindiana > uname -m = i86pc > uname -r = 5.11 > uname -s = SunOS > uname -v = illumos-dea3b85466 > > /usr/bin/uname -p = i386 > /bin/uname -X = System = SunOS > Node = openindiana > Release = 5.11 > KernelID = illumos-dea3b85466 > Machine = i86pc > BusType = > Serial = > Users = > OEM# = 0 > Origin# = 1 > NumCPU = 6 > > /bin/arch = i86pc > /usr/bin/arch -k = i86pc > /usr/convex/getsysinfo = unknown > /usr/bin/hostinfo = unknown > /bin/machine = unknown > /usr/bin/oslevel = unknown > /bin/universe = unknown > [etc] > > I checked also the OmniOS VM and that also reports i86pc. > So, am I misunderstanding something, or did I just find a bug in uname? > On Solaris/illumos i86pc denotes the architecture encompassing x86 and x86_64, here called i386 and amd64 respectively. The command 'isainfo' returns the supported Instruction Set Architectures (ISA) for the machine while 'isalist' returns all the extensions. narval> isainfo amd64 i386 narval> isalist amd64 pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86 > Pf > -- > Pierfrancesco Caci, ik5pvx > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] local pkg repo error
On Thu, Jan 14, 2021 at 9:26 PM Pierfrancesco Caci wrote: > cool thanks, in the meantime I found that I could do this: > > root@openindiana:~# pkg list -avHf sudo > pkg://ik5pvx-repo/security/sudo@1.9.3.1-2020.0.1.0:20210114T173814Z > --- > pkg://openindiana.org/security/sudo@1.9.3.1-2020.0.1.0:20201031T120907Z > i-- > pkg://openindiana.org/security/sudo@1.8.31-2020.0.1.0:20200330T16Z > --- > root@openindiana:~# pkg install ik5pvx-repo/security/sudo > > pkg install: The following pattern(s) did not match any allowable > packages. Try > using a different matching pattern, or refreshing publisher information: > > ik5pvx-repo/security/sudo > root@openindiana:~# pkg install > pkg://ik5pvx-repo/security/sudo@1.9.3.1-2020.0.1.0:20210114T173814Z > Packages to update: 1 >Create boot environment: No > Create backup boot environment: Yes > [...etc] > > It is running my version now, although it didn't take all the modifications > I did. But that's another story. > Congratulations on your first steps :) > > > > On Thu, Jan 14, 2021 at 9:15 PM Aurélien Larcher < > aurelien.larc...@gmail.com> > wrote: > > > On Thu, Jan 14, 2021 at 9:08 PM Pierfrancesco Caci > > wrote: > > > > > The "rebuild" did the trick, but how do I specify to pkg to install the > > > version from my repo instead of the official one? The version is the > same > > > > > > > First you need to allow cross-publisher updates: > > > > pfexec pkg set-publisher --non-sticky openindiana > > > > so that you can update from a package published at openindiana's repo to > > yours. > > > > Then: > > > > pfexec pkg update -g /path/to/repo my_package_name > > > > Also you can do: > > > > pfexec pkg install -g /path/to/repo my_package_fmri > > > > where my_package_fmri is the full package identifier that you can > > copy/paste from the output of gmake publish. > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jan 14, 2021 at 8:39 PM Aurélien Larcher < > > > aurelien.larc...@gmail.com> > > > wrote: > > > > > > > You can even > > > > > > > > pkgrepo -s /path/to/repo list > > > > > > > > to make sure it was published where you think it was. > > > > > > > > On Thu, 14 Jan 2021, 8:10 pm Aurélien Larcher, < > > > aurelien.larc...@gmail.com > > > > > > > > > wrote: > > > > > > > > > You can try to: > > > > > > > > > > pkgrepo -s /path/to/repo rebuild > > > > > > > > > > to update the repo index. > > > > > > > > > > On 1/14/21, Pierfrancesco Caci wrote: > > > > > > Hello, > > > > > > I'm trying to learn how to recompile a package and put it in a > > local > > > > > repo. > > > > > > I've followed the ips-dev-guide.pdf for setting up the repo, and > > the > > > > > > "Getting started with the Userland Consolidation" from github. > > > > > > I got the package to compile and copy to the repo (gmake > publish), > > > but > > > > > when > > > > > > I try to search for that package with "pkg search sudo" I get > this > > > > error: > > > > > > > > > > > > pkg: Some repositories failed to respond appropriately: > > > > > > ik5pvx-repo: > > > > > > file protocol error: code: E_FTP_WEIRD_PASS_REPLY (11) reason: > > > Search > > > > > > temporarily unavailable. > > > > > > Repository URL: 'file:///export/home/ik5pvx/my-repo'. (happened 4 > > > > times) > > > > > > > > > > > > What am I doing wrong? > > > > > > > > > > > > Pf > > > > > > > > > > > > -- > > > > > > Pierfrancesco Caci, ik5pvx > > > > > > ___ > > > > > > openindiana-discuss mailing list > > > > > > openindiana-discuss@openindiana.org > > > > > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > > > > > > > > > > > > > > > > > -- > > > > > --- > > > > > Praise the Caffeine embeddings > > > > > > > > > ___ > > > > openindiana-discuss mailing list > > > > openindiana-discuss@openindiana.org > > > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > > > > > > > > > -- > > > Pierfrancesco Caci, ik5pvx > > > ___ > > > openindiana-discuss mailing list > > > openindiana-discuss@openindiana.org > > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > > > > > -- > > --- > > Praise the Caffeine embeddings > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > -- > Pierfrancesco Caci, ik5pvx > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] local pkg repo error
On Thu, Jan 14, 2021 at 9:08 PM Pierfrancesco Caci wrote: > The "rebuild" did the trick, but how do I specify to pkg to install the > version from my repo instead of the official one? The version is the same > First you need to allow cross-publisher updates: pfexec pkg set-publisher --non-sticky openindiana so that you can update from a package published at openindiana's repo to yours. Then: pfexec pkg update -g /path/to/repo my_package_name Also you can do: pfexec pkg install -g /path/to/repo my_package_fmri where my_package_fmri is the full package identifier that you can copy/paste from the output of gmake publish. > > > On Thu, Jan 14, 2021 at 8:39 PM Aurélien Larcher < > aurelien.larc...@gmail.com> > wrote: > > > You can even > > > > pkgrepo -s /path/to/repo list > > > > to make sure it was published where you think it was. > > > > On Thu, 14 Jan 2021, 8:10 pm Aurélien Larcher, < > aurelien.larc...@gmail.com > > > > > wrote: > > > > > You can try to: > > > > > > pkgrepo -s /path/to/repo rebuild > > > > > > to update the repo index. > > > > > > On 1/14/21, Pierfrancesco Caci wrote: > > > > Hello, > > > > I'm trying to learn how to recompile a package and put it in a local > > > repo. > > > > I've followed the ips-dev-guide.pdf for setting up the repo, and the > > > > "Getting started with the Userland Consolidation" from github. > > > > I got the package to compile and copy to the repo (gmake publish), > but > > > when > > > > I try to search for that package with "pkg search sudo" I get this > > error: > > > > > > > > pkg: Some repositories failed to respond appropriately: > > > > ik5pvx-repo: > > > > file protocol error: code: E_FTP_WEIRD_PASS_REPLY (11) reason: > Search > > > > temporarily unavailable. > > > > Repository URL: 'file:///export/home/ik5pvx/my-repo'. (happened 4 > > times) > > > > > > > > What am I doing wrong? > > > > > > > > Pf > > > > > > > > -- > > > > Pierfrancesco Caci, ik5pvx > > > > ___ > > > > openindiana-discuss mailing list > > > > openindiana-discuss@openindiana.org > > > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > > > > > > > > > -- > > > --- > > > Praise the Caffeine embeddings > > > > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > -- > Pierfrancesco Caci, ik5pvx > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] local pkg repo error
You can even pkgrepo -s /path/to/repo list to make sure it was published where you think it was. On Thu, 14 Jan 2021, 8:10 pm Aurélien Larcher, wrote: > You can try to: > > pkgrepo -s /path/to/repo rebuild > > to update the repo index. > > On 1/14/21, Pierfrancesco Caci wrote: > > Hello, > > I'm trying to learn how to recompile a package and put it in a local > repo. > > I've followed the ips-dev-guide.pdf for setting up the repo, and the > > "Getting started with the Userland Consolidation" from github. > > I got the package to compile and copy to the repo (gmake publish), but > when > > I try to search for that package with "pkg search sudo" I get this error: > > > > pkg: Some repositories failed to respond appropriately: > > ik5pvx-repo: > > file protocol error: code: E_FTP_WEIRD_PASS_REPLY (11) reason: Search > > temporarily unavailable. > > Repository URL: 'file:///export/home/ik5pvx/my-repo'. (happened 4 times) > > > > What am I doing wrong? > > > > Pf > > > > -- > > Pierfrancesco Caci, ik5pvx > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > -- > --- > Praise the Caffeine embeddings > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] local pkg repo error
You can try to: pkgrepo -s /path/to/repo rebuild to update the repo index. On 1/14/21, Pierfrancesco Caci wrote: > Hello, > I'm trying to learn how to recompile a package and put it in a local repo. > I've followed the ips-dev-guide.pdf for setting up the repo, and the > "Getting started with the Userland Consolidation" from github. > I got the package to compile and copy to the repo (gmake publish), but when > I try to search for that package with "pkg search sudo" I get this error: > > pkg: Some repositories failed to respond appropriately: > ik5pvx-repo: > file protocol error: code: E_FTP_WEIRD_PASS_REPLY (11) reason: Search > temporarily unavailable. > Repository URL: 'file:///export/home/ik5pvx/my-repo'. (happened 4 times) > > What am I doing wrong? > > Pf > > -- > Pierfrancesco Caci, ik5pvx > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Just get Pale Moon
On Thu, Jan 14, 2021 at 12:31 PM Hung Nguyen Gia wrote: > You don't have to. I'm bored talking with people doesn't hear me. > > And I also said everything I could say. The decision is up to you. > > No need to kick my ass out of this list. > Thank you, no problem. I understand your frustration. We all have to deal with difficulties and things that do not work... I started working again on the migration to GCC 10 and to Python 3.9 and it is a bit daunting... ;) Cheers, Aurélien On Thu, 14 Jan 2021 18:25:29 +0700 Aurélien Larcher < > aurelien.larc...@gmail.com> wrote > > > > > > > On Thu, Jan 14, 2021 at 12:12 PM Hung Nguyen Gia via > openindiana-discuss wrote: > > I have no power to make decisions. But I will show you what I mean when > I said SANE or INSANE. > > > > First, we have to know where we are. The glory of Solaris has faded to > the past. > > > > Today, we are even inferior to FreeBSD! Honestly speaking, if someone > wanted to build a server, both for normal or storage purpose, I would > recommend them to use FreeBSD. > > > > FreeBSD got their ZFS from Illumos, right. But today, FreeBSD's ZFS is > more easy to use and more stable than Illumos! > > > > Not to mention initiative like ZoF. You are left behind. Yes, I know > you will going to go to OpenZFS 2.0, too. > > > > Since there is no where else you could go. You don't have the ability > to maintain ZFS yourself. > > > > Then the only way is to rely on Linux people's work, ZoL, with a fancy > rename to be OpenZFS 2.0, nothing other than ZoL with a bunch of #ifdef for > other minor OSes. > > > > Yes, you are now being a minor OSes. Accept it or not, you are no > longer upstream. Do you feel any shame when it's all reversed? From being > upstream, now just a downstream minority only able to going thanks to the > mercy of the Linux guys? > > > > Not to mention, if it's about a desktop system, what OI is for, OI is > completely inferior to FreeBSD. > > > > Just download GhostBSD, compare, and see. > > > > The BSDs could reject Pale Moon, because they have PLENTY of > alternatives. They have working Firefox, some of them even Chromium. > > > > What do you have now? Are you in a place you could do as them? No way! > > > > Do you able to show me even just a preview version of the Firefox you > are working on? > > > > You can't, do you? > > > > It's SANE to just import Pale Moon into the encumbered repo. They are > plenty of software they install to /opt, doesn't it? Just put Pale Moon and > all of their sh8t shipped libraries there and no one care. > > > > It's INSANE when you don't know what you are and where you are but act > as like you have plenty of choices when indeed you have NONE. You are not > any less ARROGANT than the Pale Moon devs. I think it can only be MORE than > them. > > > > Accept that you are LOSER, and do your best to get back to your place, > it's what SANE people do. > > > > INSANE people talk very much about discipline, 'quality standard', bla > bla... but indeed can deliver nothing! Proving wrong very easy, give me a > preview of your Firefox! But I know, you can't. > > > > Hi, > > there is probably no question that illumos is a minor OS when it comes > to the size of the community; hardware support and software availability is > therefore more limited than systems backed by big companies and a few > hundred developers. > > > > However until now this small community has always been courteous and > friendly. > > > > Could you please make your point in a less offensive manner and > possibly be more constructive? > > > > These mailing lists are a place for people exchanging ideas and > providing help, not for arsonists. > > > > If you cannot cool your jets you'll be sent off the pitch for one week. > > > > Kind regards, > > > > Aurélien > > > > > > > > > > > > > > On Thu, 14 Jan 2021 17:00:16 +0700 Volker A. Brandt > wrote > > > > > > All of your so called 'quality standard' are just pure BS. > > > > > > > > > Buf if you really want to act like a boss and have Pale Moon > on OI as > > > > > your wish, consider DM-ing me? I think I can arrange that for > you -- if > > > > > you pay me will enough, of course. > > > > > > > > >
Re: [OpenIndiana-discuss] Just get Pale Moon
On Thu, Jan 14, 2021 at 12:12 PM Hung Nguyen Gia via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > I have no power to make decisions. But I will show you what I mean when I > said SANE or INSANE. > > First, we have to know where we are. The glory of Solaris has faded to the > past. > > Today, we are even inferior to FreeBSD! Honestly speaking, if someone > wanted to build a server, both for normal or storage purpose, I would > recommend them to use FreeBSD. > > FreeBSD got their ZFS from Illumos, right. But today, FreeBSD's ZFS is > more easy to use and more stable than Illumos! > > Not to mention initiative like ZoF. You are left behind. Yes, I know you > will going to go to OpenZFS 2.0, too. > > Since there is no where else you could go. You don't have the ability to > maintain ZFS yourself. > > Then the only way is to rely on Linux people's work, ZoL, with a fancy > rename to be OpenZFS 2.0, nothing other than ZoL with a bunch of #ifdef for > other minor OSes. > > Yes, you are now being a minor OSes. Accept it or not, you are no longer > upstream. Do you feel any shame when it's all reversed? From being > upstream, now just a downstream minority only able to going thanks to the > mercy of the Linux guys? > > Not to mention, if it's about a desktop system, what OI is for, OI is > completely inferior to FreeBSD. > > Just download GhostBSD, compare, and see. > > The BSDs could reject Pale Moon, because they have PLENTY of alternatives. > They have working Firefox, some of them even Chromium. > > What do you have now? Are you in a place you could do as them? No way! > > Do you able to show me even just a preview version of the Firefox you are > working on? > > You can't, do you? > > It's SANE to just import Pale Moon into the encumbered repo. They are > plenty of software they install to /opt, doesn't it? Just put Pale Moon and > all of their sh8t shipped libraries there and no one care. > > It's INSANE when you don't know what you are and where you are but act as > like you have plenty of choices when indeed you have NONE. You are not any > less ARROGANT than the Pale Moon devs. I think it can only be MORE than > them. > > Accept that you are LOSER, and do your best to get back to your place, > it's what SANE people do. > > INSANE people talk very much about discipline, 'quality standard', bla > bla... but indeed can deliver nothing! Proving wrong very easy, give me a > preview of your Firefox! But I know, you can't. > Hi, there is probably no question that illumos is a minor OS when it comes to the size of the community; hardware support and software availability is therefore more limited than systems backed by big companies and a few hundred developers. However until now this small community has always been courteous and friendly. Could you please make your point in a less offensive manner and possibly be more constructive? These mailing lists are a place for people exchanging ideas and providing help, not for arsonists. If you cannot cool your jets you'll be sent off the pitch for one week. Kind regards, Aurélien > > > On Thu, 14 Jan 2021 17:00:16 +0700 Volker A. Brandt > wrote > > > > All of your so called 'quality standard' are just pure BS. > > > > > > > Buf if you really want to act like a boss and have Pale Moon on OI > as > > > > your wish, consider DM-ing me? I think I can arrange that for you > -- if > > > > you pay me will enough, of course. > > > > > > > > > > I don't want to be boss. The fact is I suffered from such people on > my real life. > > > > > > But frankly speaking, your team needs more people like that. At least > they are SANE. > > > > With your superior intellect, and your sharp powers of observation, in > a > > matter of days, you have identified many of the problems the > incompetent > > and insane OI devs have failed to fix for years. > > > > Congratulations! > > > > So which one are you going to start working on first? > > > > > > Regards -- Volker > > -- > > > > > Volker A. BrandtConsulting and Support for Solaris-based > Systems > > Brandt & Brandt Computer GmbH WWW: > http://www.bb-c.de/ > > Am Wiesenpfad 6, 53340 Meckenheim, GERMANYEmail: > v...@bb-c.de > > Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: > 46 > > Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt > > > > "When logic and proportion have fallen sloppy dead" > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] This is for someone said we had desktop/wine for ages
Wine was provided by a third-party repository called SFE, but that was a few years ago. Probably OpenCSW had it as well. I guess that's what was referred to. On 1/14/21, Hung Nguyen Gia via openindiana-discuss wrote: > He just recall from his memory without any fact checks! > > Then others come in and 'agreed' with him, my very real concern being pissed > off! > > http://pkg.openindiana.org/hipster/en/search.shtml?token=wine=Search > > http://pkg.openindiana.org/hipster-encumbered/en/search.shtml?action=Search=wine=1 > > There is even people said just use LibreOffice. > > No, man. If the people I mentioned could use LibreOffice, they would rather > just use it on Windows! > > Microsoft Office is still the de facto standard. > > We really really need Wine. Even a shaky version like of Tribblix is better > than nothing. > > Just to be more clear, Tribblix has Wine 4.0, and as I recall sfw Wine is > just 1.9.5, if I'm not wrong. > > Otherwise, people will come in and post misleading info without even fact > check it! > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hipster install on Lenovo P61
On Wed, Jan 13, 2021 at 8:41 PM Stephan Althaus < stephan.alth...@duedinghausen.eu> wrote: > Hello! > > I tried a P51 some time ago. It had a "optimus" called constellation > between the intel and the nvidia graphics. > If you have this, i doubt you have a chance to get nvidia graphics to work. > Without porting switcheroo is it impossible to get this to work. > > If you have very dedicated hardware paths for each graphic controller, > you must be able to completely disable the intel graphics. > On my DELL Precision 7720 i am able to do it this way. > > Have a close look into your BIOS settings. > > For recent NVidia drivers have a look at > https://wiki.openindiana.org/oi/Nvidia+Graphics > https://www.nvidia.com/en-us/drivers/unix/solaris-display-archive/ > > Greetings, > Stephan > > > On 01/13/21 19:58, a.j...@zebworx.com wrote: > > Hello, > > > > I installed the latest OI-Hipster on an Lenovo P61, it works so far > > but some parts didn't work. > > > > Has someone experients with the following components: > > > > The "Intel Corporation HD Graphics 630" only works with vgatext, > > which is very slow and > > Graphic "NVIDIA Corporation GM206GLM [Quadro M2200 Mobile] did not > > work at all. > > > > Also the Wireless Card "Intel Corporation Wireless 8265 / 8275" is not > > recogniced. > > > > Has someone some hints how i can get it work? > > > > > > Best regards and sorry for my bad english, > > Alex > > > > ___ > > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Microphone and pulseaudio
On Tue, Jan 12, 2021 at 4:17 PM Udo Grabowski (IMK) wrote: > > > On 12.01.21 16:10, Tony Brian Albers wrote: > > I'm having issues getting an analogue (using a 3,5mm jack connector) > > microphone to work properly. > > > > It shows up in the mate-volume-control window, but even when it's at > > 100% volume, there's no sound level indication. The mic works, because > > when I test it with > > $ cat >/tmp/foo.au > > $ cat /tmp/foo.au >>/dev/audio > > > > I can hear the words I say, but it's awfully low and the noise level is > > normal. The words are only just audible. > Check the volume with audioctl, it defaults to 75%. > > > > Is there a way that I can use something like mic boost? I've been > > rummaging around in pulseaudio(pacmd etc.) all day now, but I can't find > > anything that's not set to a 100% volume with regards to the microphone. > > > > Any ideas and suggestions are welcome. > > Maybe it's not switched on in the mixer ? > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Newer JDKs
On Tue, Jan 12, 2021 at 1:01 PM Hung Nguyen Gia via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > We stuck with OpenJDK 8 u232. > > pkgsrc has newer versions. But they have troubles with libdemangle. > Installing sunpro package simply not enough to fix this. > > Nothing strange. They are built on SmartOS. A very different environment > than us. > > Don't expect they run 100% fine. > > OmniOS has never versions, too. > > Tribblix, of course. P. Tribble seemed to be OpenJDK's maintainer for > Illumos. > > I don't ask much. Just get the latest version of OpenJDK 8 and OpenJDK 11 > is enough. > > Both are LTS. Maybe just pulling the patches from Tribblix? > > I think the OmniOS guys did the same. > Yes we need to add OpenJDK 11, I think Franklin was working on adding the component. If he is busy I can take over and build the package this week, or if any other developer is interested. > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] WINE
On Tue, Jan 12, 2021 at 1:01 PM Udo Grabowski (IMK) wrote: > On 12.01.21 12:56, Hung Nguyen Gia via openindiana-discuss wrote: > > Tried to build WINE from sources on OI. Failed at the configure step. > > > > Don't know how P. Tribble could have a working version of WINE on > Tribblix. > > > > Maybe Illumos is not always the same. Between the distros there are more > different than between Linux distros. > > > > Hope someday you guys could have WINE working. > > > > > Wine is running for ages on OI => desktop/wine > We actually have a pending PR which was never merged: https://github.com/OpenIndiana/oi-userland/pull/5124 > > > > I'm not going for gaming. > > > > I'm about to find other possible usage for OI. > > > > Microsoft Office w/o Windows. > > > > I think this is known as Libreoffice... > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How is IvyBridge support on recent IO?
Hello, Could you open a ticket describing the issue? Thank you :) On Mon, 11 Jan 2021, 9:16 pm Chris, wrote: > On 2021-01-11 11:53, John D Groenveld wrote: > > In message , Chris writes: > >> OK text install gave me the screens to install. But > >> 1) could'nt use the F keys to advance (needed ESC-N sequence) > >> 2) at the end of root/user pass/creation, pressing ESC-2 > >> returned me to "Install OI" menu > >> > >> IOW install procedure will not go past finishing > >> root password/create (new) user (next simply returns to start > >> of install). > > > > Tab down to create user and then ESC-2. > > If you ESC-2 while the cursor is in the root password dialog, > > the installer crashes. > Thank you very much for the reply, John! > The cursor is in the new user 2nd password field when I hit ESC-2. > This apparently *also* causes the installer to crash. > The "magic" I just discovered with your help. Is that if the cursor > is in *any* cursor field. The installer will crash. So I simply > moved it into the Full Name field after creating the new user. Then > ESC-2. > The install is now proceeding as I write this reply. > > Thanks again, John! > > --Chris > > > > John > > groenv...@acm.org > > > > ___ > 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] When this misery end?
On Sun, Jan 10, 2021 at 8:30 PM Hung Nguyen Gia via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > Too many people replied me. I can't answer each of them. This is an AIO > answer of mine. > > First: No, the kernel alone is not enough for you to be a 64 bit ready OS. > You can only be a 64 bit ready OS when you are 64 bit only. 32 bit lib > shipped with the system for compatibility is fine. It's what a typical > multi-lib multi-arch system works. But all of the binaries, must be 64 bit > only. The compiler, should or should not, be a multi-lib multi-target > supported compiler, that allowing cross compile to the 32 bit target. > > Do you think you really meet this definition? > No, but this is your definition :) > > Second: Enterprise OS and compatibility > > Switching all of the binaries to be 64 bit only doesn't effect > compatibility at all. Targeting 64 bit binaries doesn't effect > compatibility at all. As long as you still support running 32 bit apps and > ship with 32 bit lib to enable those apps to run. Unless, your apps have a > hard requirement that some tools must be 32 bit otherwise it will not work? > I don't know anything like that exists. > > Third: Create a package? > > Got it. You have to use complicated scripts to mitigate Sun's bad decision > in the past, when they are not transitioned completely to a 64 bit system. > Or not yet? Sun had to stop before it has any chance. Oracle acquired it. > > Now I know why you have too few apps. Software developers prefer the plain > old ./configure make make install you just said is the past. It plain and > simple way allows them to have a glimpse if their software would build and > run on your OS or not. Remember, you are not the primary platform. > Nowadays, it's Linux. Requiring them to setup a whole system like a real OI > developer just to be able to correctly compile their software? Forget it, > your OS grey-listed. Not worth the effort! > > The idea of setting up a whole system like that also ill formed. I think > the FreeBSD Ports get it more correct. The software must be able to build > and run fine on the porter's computer first. Only after that, he created a > port (make files) and submit it to the project to get it build and ready to > be installed for the users. You did the completely reverse thing. > > Fourth: Sun's approach made more sense? > > Nope. When everyone in the world switch to eat potatoes, if you continue > to eat bread people will call you crazy. All of the other OSes, not > mentioning Linux, the BSDs, all following Linux's convention, let alone > it's a big if if Sun's approach really made any more sense at all. > > But you have to keep it to keep compatibility. It's understandable, for an > enterprise system. > > But, you could change anything that doesn't break compatibility, don't > you? Let's make the life of all of us more easier. > > Fifth: I know the problem is ld incorrectly link my 64 bit objects with a > 32 bit crt. But how can I stop it from happening? > > It's your linker's fault, not me. It could be a limitation, or even bug. I > correctly have all of my objects being 64 bit, but it still incorrectly > link them with a 32 bit crt. > > Which flags I needed to specify? LD='ld -64' or LD='ld -m64'? Nope. Not > work. Even hacked the meson.build file to add these 64 flags doesn't have > any affects. > > Why it's too complicated and annoying on your OS? On Linux, or the BSDs, I > could simply doing everything the old way straight forward. > > BTW, if the full oi-userland thingy is the only way to get everything > correctly, I think I would give it a try. Not promise, though. > > I was cut off from my friend's PC and now on my old 4 cores 8 GB RAM PC. > > OpenIndiana eats resources like hell. Even when limiting the ZFS ARC Cache > size. > > Someone on this lists did said me to just dd my efi partition of OI on my > external SSD to the USB stick? Well, this destroyed my friend's Windows 10 > boot loader. Good job, Mr. Hacker. Good job. > > > On Mon, 11 Jan 2021 01:45:35 +0700 Aurélien Larcher < > aurelien.larc...@gmail.com> wrote > > > On Sun, Jan 10, 2021 at 6:55 AM Hung Nguyen Gia via openindiana-discuss > < > > openindiana-discuss@openindiana.org> wrote: > > > > > Unlike other systems, Illumos is a weirded platform! You have a 64 > bit OS > > > but the compiler by default will generate 32 bit binaries! The linker > by > > > default link 32 bit binaries! This has caused endless of troubles for > > > people wanted to have their software working on your platform and the > > > porters wanted to port software to your platform! I h
Re: [OpenIndiana-discuss] When this misery end?
On Sun, Jan 10, 2021 at 6:55 AM Hung Nguyen Gia via openindiana-discuss <
openindiana-discuss@openindiana.org> wrote:
> Unlike other systems, Illumos is a weirded platform! You have a 64 bit OS
> but the compiler by default will generate 32 bit binaries! The linker by
> default link 32 bit binaries! This has caused endless of troubles for
> people wanted to have their software working on your platform and the
> porters wanted to port software to your platform! I have asked many people,
> apart from the reason you are being a minor platform ('outdated', 'dead
> OS', 'too little market share',...) this insanity is the second reason why
> they all afraid!
>
The reason is simple, historically the compiler and toolchain would default
to the least common denominator.
In this case there was not really a question of right or wrong but a matter
of convention.
Solaris defines an Instruction Set Architecture (ISA) which may be
supplemented with processor-specific extensions.
In our case the architecture is i386 and amd64 is seen as an extension.
The toolchain for a given ISA would therefore default to 32-bit (the least
common denominator) or use extensions if instructed to do so with flags.
This has been the convention for Solaris on sparc and i386.
Alan would be able to explain this better than I do.
This was also an approach chosen on at least some IRIX versions where some
workstations with MIPS R10K and dedicated ASICS would use optimized
binaries with such support.
The path chosen by most Linux distributions was to consider amd64 (later
renamed x86_64) as a different architecture and therefore distribution pure
64-bit.
However Debian for instance discovered rather soon that they had to provide
32-bit libraries for compatibility and retrofitted the "lib32" libraries,
and later on delivered libraries in subdirectories based on the platform
triplet.
So IMHO the Solaris approach made more sense, since you had to specify
which ISA and which standard compliance were intended.
On the contrary Linux distributions relied often on defaults guided by
convenience and selecting the "standard of the day", this has changed a lot
in recent years.
However, one could argue that 32-bit is not relevant anymore and that the
least common denominator should be replaced by the actual intended
architecture: 64-bit in this case.
Therefore I took the liberty of selecting 64-bit code generation by default
since I packaged gcc-9, and kept the same rule for gcc-10.
So your complaint is not founded at all: we are transitioning as fast as
time permits.
Some of the issues with the migration to gcc-10 was indeed the assumption
the build system made on the defaut bitness of generated binaries.
I fixed about a hundred of such issues back in spring last year.
Most of your issues come from incorrect assumptions: this is often the case
when you are used to one type of system and some of the problems you
mention denote a lack of experience with UNIX in a broad sense.
I had the same expectation when I started my Linux/UNIX journey 15 years
ago as a student in engineering.
However I was very curious and willing to learn the differences between
systems so I installed and played with Debian, OpenBSD, NetBSD, FreeBSD,
Solaris 7/8/9/10, IRIX, on various machines including SPARC and Alpha
workstations.
Talking and throwing anathema is not really something I am interested in.
I'd rather work on contributing and take a constructive approach.
I was a member of a Linux user group from 2003 to 2008 where BSD/Solaris
users were often mocked for using inferior systems: I was once called an
idiot for installing NetBSD and Solaris on my machines.
Interestingly whenever the discussion became a bit technical and concrete
about what they did not like about BSD/Solaris/IRIX most Linux proselytes
in the group would actually admit that they had never run anything else
than Debian or Red Hat :)
The Slackware guru in the group always sided with BSD people though :P
We would eventually reconcile around a few bottles of beer and a few pizzas
:D
In any case, as other people mentioned we have a build system to set all
the flags automatically if you are not familiar with UNIX.
If you choose to compile things outside this environment then you need some
minimal knowledge of the environment.
These things, while they could be made more convenient, are luckily fairly
trivial and most of us deal with them.
We talked about this some months ago and unfortunately I got sick and could
not do the gcc-10 migration.
So here we are again with you complaining :P :P :P
Cheers
Aurelien
> When would we could be as normal as other 64 bit system, when people no
> longer have to pass CC='gcc -m64' CXX='g++ -m64' before any configure
> scripts with a very high rate of failure just to have 64 bit binaries
> generated, I wonder?
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
>
Re: [OpenIndiana-discuss] Dual screen setup with intel DRM & VESA
On Sat, Jan 9, 2021 at 3:00 AM Araragi Hokuto wrote: > OK, apparently I've jumped into conclusion here, since the Skylake GPU > is actually not supported by illumos DRM right now, so this setup is > probably impossible. I'll update this after I've come up with another idea. > Hi, our drm/i915 kernel driver is a bit dated and needs some work. I have a branch with some updates but it is hard to close the gap as there are dependencies between drm/i915, libdrm, mesa which are hard to untangle. One missing bit in illumos is proper HDMI support which is now a requirement for moden drm kernel. module. This can be ported from OpenBSD last time I checked. Kind regards Aurelien > > Thanks anyway. > > On 1/8/21 5:44 PM, Araragi Hokuto wrote: > > Hello everyone. > > > > I'm trying to setup an OI installation for my illumos dev tasks. My > > system has a i7-6700 CPU and RX480 graphics card, with a dual monitor > > setup. Since there is no AMDGPU driver avaliable for illumos (Correct > > me if I'm wrong, but https://www.illumos.org/issues/8069 does not seem > > to have a corresponding kernel module, and I couldn't get that working > > by simply installing the userland component, I'm assuming there is > > still no actual support at this moment?), I'm currently using VESA > > xorg driver, which works fine for me; but since it uses VESA BIOS for > > display, there is no dual screen support. > > > > But I noticed that there is intel DRM support on illumos, and I do > > have a intel GPU (the integrated GPU in my i7), so I'm thinking: is it > > possible to utilize both GPU for dual screen support? > > > > More specifically, these are what I'm trying to do: > > > > a) Use VESA driver for RX480, and connect the primary screen to its > > HDMI output, which is already working by default, and: > > > > b) Enable intel DRM on the integrated GPU, and connect the secondary > > monitor to the HDMI port provided by my motherboard. > > > > a) is working by default now, and enabling intel GPU while keep the > > AMD GPU working is certainly doable in my BIOS (verified under Linux > > with xrandr). But I'm not sure how to configure X server on illumos to > > make it aware of this setup. > > > > Therefore, is there anyone have ideas of what configure should I try, > > or some alternative way to setup dual screen with VESA/intel DRM? > > Unfortunately there is only one HDMI port on my motherboare, so I > > don't think connecting both monitor to intel GPU is an option (again, > > correct me if I'm wrong). > > > > Thanks in advance. > > > > > > > > ___ > > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Python 3.7 and 3.9
Hi, just a few notes: 1) Following Apostolos message python-37 was modified to provide IDLE in a separate package: idle-37. After the next update you may need to reinstall it. 2) The library libpython3.so which provides a stable ABI was not provided by python-3X packages, this is now the case for 3.7; the link is mediated. 3) Two fixes (sendfile and sched_get_priority) were backported from 3.8/3.9; 4) Python 3.9.1 was added based on solaris-userland patchset + testsuite fixes from Andy, thanks go to them. No we need to: 1) Migrate away from 3.5 to 3.7 as the default Python implementation. 2) Provide required Python 3.9 modules for pkg5 (cherry-py, rapidjson, six, etc..). 3) Automate/simplify the update process for Python modules to reduce manual intervention. As Till pointed out, we need to be smart about it. Kind regards, Aurélien -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Qt5 republished
Hi, Cristian reported that some of the libraries provided by the qt5 package were not updated correctly: https://www.illumos.org/issues/13439 The package has been republished and this is now fixed. Aurélien -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Tasks to focus on
On Thu, Jan 7, 2021 at 10:57 PM Till Wegmueller wrote: > Hey Aurelian > > Nice to have you back! > > We had a Maintainer meetup yesterday aswell and I am still processing > the notes. And translating to English. (we where all German) > > But in short: > I will get myself a Physical host with Hetzner with a ton of RAM and CPU > so we can dedicate some zones and VM's to OpenIndiana building packages. > Olaf has been working on a revised Jenkins pipeline which fully > automates PR builds and allows to push them into seperate repos for > testing with others. So others can just use that repo for testing and > don't need to build. We will implement that Capability there. > Great initiative! > We also talked about making a rustup.mk which will use jmclulows rustup > work to bootstrap a rust compiler to build rust software and rust itself. > I worked on the updating the component months ago so my recipe has become obsolete since Joshua made illumos a first class rust citizen :) > > As we plan to eventually migrate our build and repository server onto > that Hetzner machine, we can also look into rebuild then, as we will > probably have to do one from scratch. > I will also set up a build zone on a file server which has fairly low workload now (2 x 20 cores, 192GB RAM) to resume the gcc-10 builds. There were only ~10 packages left to fix back then. > > PS. would you like to be invited to the Maintainer meetup? It's on the > thirst Wednesday every month 19:00 PM Berlin timezone. > Count me in :) Kind regards, Aurelien > > -Till > > > On 07.01.21 18:39, Aurélien Larcher wrote: > > Hi, > > since I have now more or less recovered from Covid I can be active to > some > > extent. > > > > Back in March I was working on: > > - building oi-userland with GCC-10 (everything was built except ~10 > > packages). > > - providing Python 3.8 and 3.9. > > - migrating pkg5 to Python 3.7. > > - updating Boost. > > - updating Clang. > > - updating Rust. > > - updating libdrm to 2.4.100. > > - bringing automated rebuild of oi-userland packages and dependencies in > > order. > > > > However priorities should be set as I cannot dedicate too much time... > > > > - What do you think should be prioritized? > > - Is anybody interested in picking up one of the tasks? I can assist and > > provide some guidance. > > > > Kind regards, > > > > Aurelien > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
On Thu, Jan 7, 2021 at 11:04 PM Till Wegmueller wrote: > No. Nobody is ever too small to achieve something. You just need to be > clever about it. We always have the assumption that building packages is > the main burden for Systems, but that is only if you don't have the > right automation. And that is possible. Fully automate bumping package > versions is possible. Build systems are similar enough, aaand many > projects now switch to meson which is specifically automate able and > standardized. So the burden is only there if you are not innovative. And > our size makes us the perfect group for such innovation. We have the > need. The Debian community does not have a need for innovation in > packaging automation they are to big. When I talk with my friend which > is Debian packager from the very beginning, he says the same. Everybody > is happy with the Status quo and wants no changes as they don't need > them. Then they get stuck. We can't afford to get stuck. Thats a good > thing. > +1 :) > > -Till > > On 07.01.21 18:50, Guenther Alka wrote: > > In the end I do not think in these categories. > > > > A few years ago all my own servers were OpenIndiana and maybe 40% of my > > users on Solaris. Now I am 100% on OmniOS beside a OI evaluation machine > > (and miss OI features and use cases) and maybe 10% of my users are left > > on Solaris with OI near to not relevant now. > > > > OmniOS and OI are OpenSource. Why not take over this from OmniOS to keep > > them more in sync? > > On Linux Debian and Ubuntu are big enough to be independent while very > > similar. On Illumos everyone may be too small alone in the long run. > > > > Gea > > > >> > >> What you want is to make a OmniOS extra respoitory (git) with GUi > >> packages. That would factually mean abandoning OI and the Goal of a > >> General Purpose OS. That would be an acquisition not a merger. > >> > >> -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 > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Tasks to focus on
Hi, since I have now more or less recovered from Covid I can be active to some extent. Back in March I was working on: - building oi-userland with GCC-10 (everything was built except ~10 packages). - providing Python 3.8 and 3.9. - migrating pkg5 to Python 3.7. - updating Boost. - updating Clang. - updating Rust. - updating libdrm to 2.4.100. - bringing automated rebuild of oi-userland packages and dependencies in order. However priorities should be set as I cannot dedicate too much time... - What do you think should be prioritized? - Is anybody interested in picking up one of the tasks? I can assist and provide some guidance. Kind regards, Aurelien -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
On Thu, Jan 7, 2021 at 6:23 PM Andreas Wacknitz wrote: > Am 07.01.21 um 18:08 schrieb Guenther Alka: > > Not broken as it never worked > > (multi purpose Illumos Unix with a stable/long term stable/newest beta > > base). > > > > OI currently: always and only newest beta based > > so Yes: (maybe easy to say as I cannot help to do the needed work - > > unsure about the needed efforts) > > > > When I remember the first steps of OpenIndiana, the lack of a stable > > was a constant item on all meetings. > > > > When OmniOS started they first tried to use OpenIndiana as base what > > was more or less OpenSolaris at that time with too many dependencies. > > Then Illumos started as a minimalistic OS based on OpenSolaris and > > OmniOS used this as base. Now as OI is pure Illumos as base and OmniOS > > is more or less pure Illumos freezed in a fork per release there is no > > real reason to have two bases and two software repositories for > > different use cases with the problem for OI that the underlying > > Illumos can change from day to day. > > > > Gea > You don't seem to have read my former answers, so I will retry: > > The most important answer you have to give is: Who will do the necessary > work? > > Actual numbers: > > Number of active OI maintainers: > Number of active OI maintainers with commit rights: 1 > Number of testers (not also being a maintainer): 1 > Number of admins (not also being a maintainer with commit rights): 0 > > > More questions you should answer as a business man: > - Do you have an estimation of the needed efforts, eg. for creating a > minimal version (tdb!) of what you propose? > - What are you willing to spend to start/support these efforts? > I do not think starting from scratch to aim at building something right here right now, but keeping a convergence with OmniOS on the overlap that Joshua and Andy have mentioned should be a goal. If we do not pay attention I am worried that we end up with an increasing gap like on pkg5 (we are two Python versions behind Andy on pkg5). There are areas when it comes to package maintenance where contributions are welcome: - Python (our build system is not flexible enough, too much manual work for nothing) - Boost - Rust - LLVM/Clang Then only after Clang and Rust are updated we can consider updating Firefox as many have requested. Without valuable contributors like you, Nona, Rick, Jim, Till, it will be hard to keep up. I have tried to keep rebuilding the entire userland with GCC 10, my goal is to have this done by the next snapshot. > > > We need to increase all the numbers I presented above before it makes > even sense to discuss a change like you are proposing! > OI is an open source project without any company background and without > anybody getting money for what he/she is doing! > > As I wrote before: We don't lack good ideas, we lack people doing actual > work! > > > Andreas > > > > > > > Am 07.01.2021 um 17:24 schrieb Chris: > >> On 2021-01-07 06:02, Kalle Anka via openindiana-discuss wrote: > >>> Well spoken,, Gea! I am in favour of consolidating the OpenSolarish > >>> community. If > >>> merging would reinvogarate interest and momentum, it can be worth > >>> it. And you guys > >>> have been discussing this merging for ages, it is your old idea > >>> taken up again. It > >>> seems that several of you think this is the only way forward, in the > >>> long run. > >>> This is what we want to do. Base a desktop package ontop OmniOS > >>> stable (or LTS). I > >>> am interested in helping such an effort. > >>> Some people say yay, some say nay. Should we create a poll, to see > >>> how large the > >>> interest is? > >> > >> I vote: NAY. > >> There is no need to fix what is not broken. > >> > >>> ___ > >>> 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
On Wed, Jan 6, 2021 at 8:58 PM Jim Klimov wrote: > On January 6, 2021 4:33:23 PM UTC, Apostolos Syropoulos < > asyropou...@yahoo.com> wrote: > > > >>Is IDLE packaged by OI? Missing a dependency then? > > > >This means that IDLE should be packaged with the tkinter? > >A.s. > >-- > >Apostolos Syropoulos > >Xanthi, Greece > > Rather, IF it is packaged, then its IPS metadata (p5m file) should declare > that IDLE package depends on tkinter and so requires it to get installed. > It is actually my mistake... I added idle to the main python package as I did not know its purpose. > > Jim > -- > Typos courtesy of K-9 Mail on my Android > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
On Thu, Dec 31, 2020 at 10:05 PM Chris wrote: > On 2020-12-31 04:25, Andreas Wacknitz wrote: > > Am 30.12.20 um 21:14 schrieb Andreas Wacknitz: > >> Am 30.12.20 um 19:10 schrieb Kalle Anka via openindiana-discuss: > >>> I have a problem with my mail list settings, so I write one single > >>> reply, adressing three different persons. I am a newbie to the > >>> OpenSolarish scene, so I dont know much about it, or who the people > >>> we should talk to, though. :) > >>> > >>> @Aurelien,Yes, I was quite certain I was not alone in seeing the > >>> disadvantages of having separate small teams instead of one single > >>> larger team. It is good that you people already had this discussion. > >>> Maybe it is time to revive your old discussion again? > >>> It was not diplomatic to say that OI was inferior, but now some > >>> additional water has passed under the bridge and you all have had > >>> some time to work and deliver your own product. I think that if > >>> people were more diplomatic it would benefit OpenSolarish, and the > >>> world as a whole. We dont want a cursing and yelling culture as in > >>> some other OSes no? > >>> I dont understand your statement of no vanilla illumos anymore. Is > >>> OmniOS not illumos, but OI is? In that case, that is sad, yes. But in > >>> the greater scheme of things, it would be better for OpenSolarish > >>> community even if we have to give up vanilla illumos. If we merge OI > >>> and OmniOS, it is not irrecoverable, it will be possible later to try > >>> to tweak our new distro to a more vanilla illumos distro. Or, if > >>> someone in the future, did the additional minor work to tweak the new > >>> merged distro to vanilla illumos - that would be much less work than > >>> creating OI today, I guess? > >>> > >>> I bet many more than I, would be very excited in one unified illumos > >>> distro where we merge OmniOS and OI. I understand there is lot of > >>> prestige involved, but if we dont do want OpenSolaris to diminish and > >>> die to Linux, we all maybe should put aside the prestige? :) > >>> > >>> > >>> @Andy,Regarding who will do all the work. Realistically, it will be > >>> you and the other OI devs who will do all the work. I bet several > >>> other people would love to help, but not all of us can do what you > >>> can do. I want to help though. Maybe help to coordinate, and help > >>> discuss with the OmniOS team? And write manuals? Of course, if we can > >>> merge OI and OmniOS there will be lot of work for you guys in the > >>> beginning. But in the long run your work will be less as there are > >>> more developers involved. And as you guys already have discussed this > >>> earlier, maybe it is time to rethink this old train of thought of > >>> yours, again? You know the process better now and have a shipped > >>> product, so you do stand on your own legs. A large team of talented > >>> developers is better than a small team? This would also cause some > >>> attention in the FOSS world, and the OpenSolarish community. More > >>> people will be exposed to your work, and benefit from it. There are > >>> already lot of work done by OmniOS, you and the OI devs could > >>> leverage their work? What is your thought of working with a new set > >>> of talented developers creating something new together that we all > >>> could benefit from? Is there too much prestige involved for this to > >>> be realistic? > >> Most OI maintainers are "dormant" at the moment. I have been the only > >> active member with commit rights for roughly three months now. > >> We don't even have enough people to test important things, eg. I have > >> asked to test and look at an update of bind without any reaction for > >> almost two weeks now. > >> > >> Adding a desktop on top of OmniOSce is A LOT OF WORK. Maintaining a > >> desktop is quite more complex than focussing on the server aspects of > >> an OS alone. The amount of work that is already done > >> for OI (many parts of it inherited from OpenSolaris) is tremendous. If > >> "we" start this endeavour it will most probably mean that you won't > >> see anything in months if not years. > >> In my eyes it will kill OI and in the end will leave Tribblix as the > >> only illumos based desktop OS. > >> > >> I haven't been involved in the earlier discussions but only read the > >> messages then. I just started to be more active at that time and > >> didn't feel experienced enough to take part at the discussion. > >> Today I am not sure whether a unification would be a good idea. Not > >> because I don't want to work with the OmniOSce guys but because we > >> have different interests. Sure, we share some technologies, > >> like illumos, the boot loader and IPS. But OmniOSce is targeted as a > >> server OS because that's the only area where people are willing to pay > >> for things. OmniOSce is a product of some companies > >> while OI is an all-purpose OS with a desktop created by people in > >> their spare time without any monetary interests
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
This is something that was discussed in the past when OmniOSCE was created but back then there was a focus on providing continuity of releases and too few people: the goal for to have a true reference distribution. Back then Adam and I had suggested to merge the distributions given the size of our respective communities: use OmniOS as a core OS with their release schedule and use oi-userland to provide extra packages but there was no interest. Tobias suggested to me that OI being an inferior distribution I should better use my time and provide X11 packages to OmniOS instead. Obviously his comment did not motivate me much :) I think merging both makes sense to gain momentum and stopping reinventing the wheel given the number of developers (us pulling from OmniOS and Dominik packaging stuff that we already have). But then it means that there is no illumos distribution actually running vanilla illumos which is a bit sad. We've had good interactions on compilers and pkg so that's at least a great start. Also this may be an overhead for Andy and he should have a good idea if it is doable, if this is something that would be positive for him and what would be the milestones. On Wed, Dec 30, 2020 at 12:39 PM Kalle Anka via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > A question. I am sure this has been discussed before, but maybe it is time > to update the discussion? :) > As I have understood it, OmniOS is a robust server OS with no good desktop > environment. It is possible to install X11, though: > https://geekblood.wordpress.com/2017/10/26/installing-x11-and-a-desktop-environment-on-omnios/ > Would it be possible to merge OI and OmniOS? Say, try to transform OI into > a desktop environment ontop OmniOS? Both OSes share lot of common ground, > so technically it would not be impossible to for instance port MATE to > OmniOS? > OpenSolarish is a bit fragmented as of now. There are several developers > working on their own stuff, with different IPS repos, etc. If we could > unite some of the work, OpenSolarish would benefit as a whole. > OmniOS would get new developers, a good desktop environment, and also lot > of users coming from OI. > OI would benefit from all the work the OmniOS developers are doing in > getting a stable and robust server OS, so it would free up OI developers to > more quickly advance desktop environment. Lot of synergy effects and > win-win. OmniOS does the server backend, and OI do the desktop frontend. > This lessens the burden for the developers. The more developers, the better. > The situation is similar to two competing camps developing ReactOS - the > open sourced WindowsXP clone. Why not unite the two teams instead? It would > be much less work for the OI developers if we could build on the excellent > work from OmniOS team, and vice versa. Remember, we all love OpenSolarish > and it would be better to have one single strong distro, than several > competing distros. FreeBSD has only one distro and that is better than the > Linux fragmentation mess today. There are only so many OpenSolarish > developers, and our community would benefit from one single strong distro. > Or, have I missed something? Like, for instance, do the illumos community > also suffer from "Not Invented Here" syndrome like some other OSes? The > only truly innovative OS is Solaris, and lets keep it that way by > consolidating and uniting our teams so we can make faster progress? I am > interested in trying to help the community too. Because Solaris is the best > OS! :) > > > BTW. Earlier I reported that OpenZFS renders ZFS disks unusable: If you > import a zpool v28 and ZFS v5, into Linux using OpenZFS, then Solaris 11.3 > cannot import the zpool again. Someone suggested that Linux OpenZFS renames > the disks as "/dev/sda" instead of "/dev/c0t0d0" in the zpool. So this > problem could maybe be fixed by importing and exporting the zpool by a > illumos distro which would automatically rename the "/dev/sda" entries to > "/dev/c0t0d0" back which means Solaris v11.3 could import the zpool. I have > not tested this yet, but it sounds plausible? > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Since OI update - Lightdm fails to start
Can you provide more details like logs, type of hardware etc... On Sat, Oct 24, 2020 at 3:21 PM russell wrote: > Hi > > After receiving the warning about the CVE today and the recommendation > to update, I did perform an update @13:27 and created a new BE, after a > reboot Lightdm failed to start correctly. > > Reverted to previous BE which was created 21st October @22:06. > > Regards > > Russell > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Office suite?
http://pkg.openindiana.org/hipster/en/search.shtml?token=libreoffice=Search On Mon, Oct 5, 2020 at 8:35 AM Tony Brian Albers wrote: > Hi guys, > > I my search-fu might not be optimal right now, but is it true that there > is no recent LibreOffice or OpenOffice build for OI? > > SFE seems to have only a couple of older versions, and neither > ravenports not pkgsrc seems to have one. > > /tony > > -- > Tony Albers - Systems Architect - IT Development Royal Danish Library, > Victor Albecks Vej 1, 8000 Aarhus C, Denmark > Tel: +45 2566 2383 - CVR/SE: 2898 8842 - EAN: 5798000792142 > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Kernel panic after pkg update
The only outstanding things since May were switching gfx-drm to gcc-7 and cherry-picking gcc-10 patches from upstream. On Tue, Aug 18, 2020 at 9:43 AM Tony Brian Albers wrote: > Here you go: > > https://magpie.fubar.farm/index.php/s/zpgyaLBmyDqrqxk > > /tony > > > On Tue, 2020-08-18 at 07:18 +, Alexander Pyhalov via openindiana- > discuss wrote: > > Hi. Can you share stack trace or dump file? > > > > С уважением, > > Александр Пыхалов, > > программист отдела телекоммуникационной инфраструктуры > > управления информационно-коммуникационной инфраструктуры ЮФУ > > > > > > > > От: Tony Brian Albers > > Отправлено: 18 августа 2020 г. 10:14 > > Кому: openindiana-discuss@openindiana.org > > Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update > > > > FYI > > > > I removed and reinstalled all xorg-related pkgs. I also ran pkg > > update > > again. > > > > Now Xorg loads more driver modules and there are no errors in > > Xorg.log, > > but the system still panics. > > > > Kernel illumos-0d54f452f4 > > > > The panic message in /var/adm/messages seems to be exactly the same. > > > > /tony > > > > > > > > > > On Tue, 2020-08-18 at 06:50 +, Tony Brian Albers wrote: > > > Hi guys, > > > > > > I'm trying to get my workstation to run the latest OI. Installation > > > of > > > the desktop-image went fine, and after reboot everything is still > > > ok. > > > > > > Then I did a pkg update. Now running kernel illumos-06260e34c2 > > > > > > Now, everytime I try to start X, it panics and reboots. I've > > > disabled > > > the displaymanager(tried both gdm and xdm) and now I get to a > > > normal > > > login. But if I login and run startx it panics again. > > > > > > > > > The interesting thing I've discovered is that Xorg fails with: > > > > > > snip--- > > > [61.472] List of video drivers: > > > [61.512]nvidia > > > [61.513] (II) LoadModule: "nvidia" > > > [61.517] (II) Loading > > > /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so > > > [61.531] (II) Module nvidia: vendor="NVIDIA Corporation" > > > [61.531]compiled for 4.0.2, module version = 1.0.0 > > > [61.531]Module class: X.Org Video Driver > > > [61.584] No devices to configure. Configuration failed. > > > [61.585] (EE) Server terminated with error (2). Closing log > > > file. > > > snip--- > > > > > > But I don't have a Nvidia card :( I'm using the Intel GPU on the > > > CPU > > > itself. And it worked fine before the pkg update. > > > > > > > > > Pkgs installed relating to video drivers: > > > > > > root@emu:~# pkg list |grep video > > > x11/server/xorg/driver/xorg-video 0.5.11- > > > 2020.0.1.1 i-- > > > x11/server/xorg/driver/xorg-video-ast 1.1.5- > > > 2020.0.1.3 i-- > > > x11/server/xorg/driver/xorg-video-ati 6.14.6- > > > 2020.0.1.4 i-- > > > x11/server/xorg/driver/xorg-video-cirrus 1.5.3- > > > 2020.0.1.3 i-- > > > x11/server/xorg/driver/xorg-video-intel 2.99.917- > > > 2020.0.1.10 i-- > > > x11/server/xorg/driver/xorg-video-mach64 6.9.6- > > > 2020.0.1.2 i-- > > > x11/server/xorg/driver/xorg-video-mga 1.6.5- > > > 2020.0.1.3 i-- > > > x11/server/xorg/driver/xorg-video-nv 2.1.21- > > > 2020.0.1.3 i-- > > > x11/server/xorg/driver/xorg-video-openchrome 0.6.0- > > > 2020.0.1.4 i-- > > > x11/server/xorg/driver/xorg-video-r1286.10.2- > > > 2020.0.1.3 i-- > > > x11/server/xorg/driver/xorg-video-savage 2.3.9- > > > 2020.0.1.3 i-- > > > x11/server/xorg/driver/xorg-video-trident 1.3.8- > > > 2020.0.1.3 i-- > > > x11/server/xorg/driver/xorg-video-vboxvideo 1.0.1- > > > 2020.0.1.4 i-- > > > x11/server/xorg/driver/xorg-video-vesa2.4.0- > > > 2020.0.1.2 i-- > > > x11/server/xorg/driver/xorg-video-vmware 13.3.0- > > > 2020.0.1.2 i-- > > > root@emu:~# > > > > > > > > > Here's what it says in /var/adm/messages: > > > > > > snip--- > > > Aug 17 21:15:43 emu unix: [ID 836849 kern.notice] > > > Aug 17 21:15:43 emu ^Mpanic[cpu1]/thread=fe2cedcf1080: > > > Aug 17 21:15:43 emu genunix: [ID 335743 kern.notice] BAD TRAP: > > > type=e > > > (#pf Page fault) rp=fe003e3d5710 addr=0 occurred in > > > module "unix" due to a NULL pointer dereference > > > Aug 17 21:15:43 emu unix: [ID 10 kern.notice] > > > Aug 17 21:15:43 emu unix: [ID 839527 kern.notice] Xorg: > > > Aug 17 21:15:43 emu unix: [ID 753105 kern.notice] #pf Page fault > > > Aug 17 21:15:43 emu unix: [ID 532287 kern.notice] Bad kernel fault > > > at > > > addr=0x0 > > > Aug 17 21:15:43 emu unix: [ID 243837 kern.notice] pid=4770, > > > pc=0xfb88151b, sp=0xfe003e3d5808, eflags=0x10246 > > > Aug 17
Re: [OpenIndiana-discuss] Support Icon on Desktop
Hi, I actually suggested this similar idea three years ago: https://github.com/OpenIndiana/oi-userland/pull/2497 This would have distributed the OI documentation in a package and provided a menu icon to open it in a browser. The proposal was rejected. Kind regards, Aurélien On Sat, Jun 27, 2020 at 1:54 PM bscuk2 wrote: > Dear All, > > Perhaps OI should have a default launcher on the desktop pointed at Oi > handbook and other support documentation online to assist the user ? > > Regards, > > > Robert Jones > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What's the easiest, straight-shot way to upgrade to a new boot SSD?
It would be nice to have this documented in oi-docs actually :) On Saturday, June 20, 2020, Guenther Alka wrote: > Another option is to backup the current BE to the datapool via zfs send. 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] 2020.04: tcl/tk
Hi,
It is very strange because the library installed in the proto area on the
build server is correct:
o...@hipster.openindiana.org:/jenkins/jobs/oi-userland/workspace/components/tcl/tk$
strings build/prototype/i386/usr/lib/libtk8.6.so | grep 8.6
libtk8.6.so
8.6.10
libtk8.6.so
optionStrings.19896
.L826
.L896
yet the library delivered in pkg://
openindiana.org/runtime/tk-8@8.6.10-2020.0.1.1:20200522T194741Z is invalid.
The reason is that the libraries were not copied again in
build/prototype/i386/mangled/ so that build/prototype/i386/mangled/usr/lib/
libtk8.6.so is the wrong one...
This indicates an issue in the build system.
I will republish the package.
Thank you for reporting the issue and sorry about the trouble...
On Thu, Jun 18, 2020 at 5:48 PM Ralf Bormann <
openindiana-disc...@irb.cs.uni-dortmund.de> wrote:
> Hi,
> some days ago I installed OI hipster 2020.04 on a notebook.
> I played a little with the installation, and everything seemed
> to work. Especially, my own installation of 'tkdiff' worked.
>
> Then I did a 'pkg update' and installed a lot of additional
> pkgs. After that, tkdiff did not work any longer. The 'pkg
> update' replaced tcl/tk 8.6.7 by 8.6.10, but there must have
> happened strange things with the tk-8 pkg.
>
>12% tkdiff
>application-specific initialization failed: Can't find a usable
>tk.tcl in the following directories: /usr/lib/amd64/tk8.6
>/usr/lib/tcl8.6/tk8.6 /usr/lib/tk8.6 /lib/tk8.6 /lib/tk8.6
>/lib/tk8.6 /library
>
>/usr/lib/tk8.6/tk.tcl: version conflict for package "Tk": have
>8.6.7, need exactly 8.6.10 version conflict for package "Tk": have
>8.6.7, need exactly 8.6.10 while executing
>"package require -exact Tk 8.6.10"
>(file "/usr/lib/tk8.6/tk.tcl" line 14)
>invoked from within
>"source /usr/lib/tk8.6/tk.tcl"
>("uplevel" body line 1)
>invoked from within
>"uplevel #0 [list source $file]"
>
>
>This probably means that tk wasn't installed properly.
>
>13% pkg list | egrep '(tcl-8|tk-8)'
>runtime/tcl-8 8.6.10-2020.0.1.1 i--
>runtime/tk-8 8.6.10-2020.0.1.1 i--
>
>14% strings /usr/lib/libtcl8.6.so | fgrep 8.6.
>8.6.10
>8.6.10
>15% strings /usr/lib/libtk8.6.so | fgrep 8.6.
>8.6.7
>8.6.7
>[ Same output in the /usr/lib/amd64 directory. ]
>
> Am i the only one with this problem?
>
>
> Ralf
>
> --
> Ralf Bormann
> TU Dortmund, IRB
> 44221 Dortmund, Germany
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
--
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Error updating from hipster-202000504
Usually this happens when the repository is being refreshed or rebuilt. On Saturday, June 6, 2020, Gary Mills wrote: > When I attempted to update a system from hipster-202000504 (the latest > USB image, I got this error message: > > Creating Plan (Download Manifests 407/437) - > > Errors were encountered while attempting to retrieve package or file data for > the requested operation. > Details follow: > > http protocol error: Unknown error code: 503 reason: Service Unavailable > URL: ' http://pkg.openindiana.org/hipster/openindiana.org/manifest/0/runtime%2Fperl-522@5.22.4%2C5.11-2020.0.1.2%3A20200512T191345Z ' > > What might be the cause. > > > -- > -Gary Mills--refurb--Winnipeg, Manitoba, Canada- > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ICU update and rebuilds
Rebuilds are done... let us hope everything republished fine... There was a problem in qt5, sorry about the delay. On Mon, Jun 1, 2020 at 8:47 PM Tim Mooney wrote: > In regard to: [OpenIndiana-discuss] ICU update and rebuilds, Aur?lien...: > > > ICU is being updated to a non-ABI compatible version and quite a few > > components need a rebuild...so the server will be quite busy and > > unavailable at times in the coming 10 hours. > > I would suggest postponing any update... > > I looked at updating ICU about 6 months ago, saw the list of dependencies, > and decided to tackle other packaging updates that didn't seem so > insurmountable. > > OpenSSL is another place where I "gave up", though it's even more > complicated than ICU because of the API changes and potential dependent > component updates required. > > Do you have any words of wisdom or suggestions for how to approach > a component with so many dependencies? Were there any "tricks" that > you used to make the ICU updates easier? It looks like for many of the > "easy" rebuilds, you grouped them into one PR (#5829). How did you decide > which ones could all be handled in one branch, and which ones needed > their own separate git branch and PR? > > Has there ever been any discussion about splitting just the library > into a separate package so that it's possible to have multiple versions > of the shared library installed at once, to make it possible to migrate > dependencies in "phases" to the latest version, rather than having to > coordinate rebuilding dozens of packages? > > Thanks for your work on this! I can only imagine how tedious this > was to accomplish... > > Tim > -- > Tim Mooney tim.moo...@ndsu.edu > Enterprise Computing & Infrastructure / > Division of Information Technology/701-231-1076 (Voice) > North Dakota State University, Fargo, ND 58105-5164 > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ICU update and rebuilds
On Mon, Jun 1, 2020 at 8:47 PM Tim Mooney wrote: > In regard to: [OpenIndiana-discuss] ICU update and rebuilds, Aur?lien...: > > > ICU is being updated to a non-ABI compatible version and quite a few > > components need a rebuild...so the server will be quite busy and > > unavailable at times in the coming 10 hours. > > I would suggest postponing any update... > > I looked at updating ICU about 6 months ago, saw the list of dependencies, > and decided to tackle other packaging updates that didn't seem so > insurmountable. > > OpenSSL is another place where I "gave up", though it's even more > complicated than ICU because of the API changes and potential dependent > component updates required. > > Do you have any words of wisdom or suggestions for how to approach > a component with so many dependencies? Were there any "tricks" that > you used to make the ICU updates easier? It looks like for many of the > "easy" rebuilds, you grouped them into one PR (#5829). How did you decide > which ones could all be handled in one branch, and which ones needed > their own separate git branch and PR? > I looked at dependencies using pkg search -r -o pkg.name "depend:require:library/icu" and then iterated through the dependencies. > > Has there ever been any discussion about splitting just the library > into a separate package so that it's possible to have multiple versions > of the shared library installed at once, to make it possible to migrate > dependencies in "phases" to the latest version, rather than having to > coordinate rebuilding dozens of packages? > > Thanks for your work on this! I can only imagine how tedious this > was to accomplish... > Unfortunately it did not go so well as the build server decided to become unavailable at the last round of builds... For now the build server is down and the latest packages have not been published... I am very sorry about that... :( Currently the procedure is partly manual and fragile but there is some work by Adam to automating rebuilds of dependent packages by iteratiing on the graph (and breaking cycles). It requires more integration but will be crucial to deal with OpenSSL. Another difficulty is packages that may fail to build because our build server is either on an older verson of osnet-incorporation or because OpenGL code builds differently in zones... > > Tim > -- > Tim Mooney tim.moo...@ndsu.edu > Enterprise Computing & Infrastructure / > Division of Information Technology/701-231-1076 (Voice) > North Dakota State University, Fargo, ND 58105-5164 > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] ICU update and rebuilds
Hi, ICU is being updated to a non-ABI compatible version and quite a few components need a rebuild...so the server will be quite busy and unavailable at times in the coming 10 hours. I would suggest postponing any update... Aurélien -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] problem related to avahi when trying to print from pluma
On Mon, May 25, 2020 at 11:37 AM Marc Lobelle wrote: > Hello, > > Up to a few days ago, I could print from pluma. > > (At that time and still now, when starting pluma, a lot of warning > messages are printed in the command line window from which I start pluma: > > Theme parsing error: :5:22: The :focused pseudo-class is > deprecated. Use :focus instead. > > If there is a cleaner way to avoid that than redirecting error messages > from pluma to /dev/null, I would be interested in) > > However, my main problem with pluma is that since a few days, pluma > cannot print any more and says: > > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name > org.freedesktop.Avahi was not provided by any .service files > > Avahi is installed on my OI-hipster2020.4 system, but svcs doesn't show > it and svcadm enable avahi does not find it. ps -aef does not show it > either. > I did rebuild avahi a few days ago but the code did not change: https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/network/avahi When was your previous BE created? before or after the bump to 0.7.0 on Jan 23, 2020? > The only things I changed recently in my system were adding fail2ban, > but I think the printing problem with pluma is older, adding > CSWlibgamin1-0-0 that is needed by cswcourier-imap, and adding > emailrelay. After installing emailrelay, pluma was still able to print. > > Does anybody know where to look or whag could be wrong ? > > Thanks > > Marc > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] GCC 10: help with oi-userland fixes
Still 67 components to fix: https://www.illumos.org/issues/12722 On Thu, May 14, 2020 at 3:36 PM Aurélien Larcher wrote: > Hi, > I have updated the ticket at: > > https://www.illumos.org/issues/12722 > > As you can see there is a list of about 120 components left to fix out of > ~1650 components in total: close to 90% of the packages are now republished. > > If you are a consumer of one of these packages and have some interest in > contributing, any help will be very much appreciated :) > I added the build logs in a tarball for reference so you can decide which > component to pick in the list. > > Kind regards, > > Aurelien > > -- > --- > Praise the Caffeine embeddings > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Σχετ: Re: VirtualBox 6.1.6 errors after OI Hipster upgrade
On Tue, May 19, 2020 at 4:25 PM Predrag Zecevic < predrag.zece...@2e-systems.com> wrote: > > On 18.05.2020 19:50, Apostolos Syropoulos via openindiana-discuss wrote: > > Hello, > > I installed the 6.1.8 build but it is notworking. I am more than sure > thatthe problem is with AMD processors.BTW, all people who reported > successstories have Intel systems. > > Apostolos > > Στάλθηκε από το Ταχυδρομείο Yahoo σε Android > > > >Στις Δευ, 18 Μαΐ, 2020 στις 19:21, ο χρήστηςEspen Martinsen< > e...@pogostick.net> έγραψε: > >> Let me know if you can install this: > > > > > > Seem Apostolos noticed good. > Is one of you able to look at the commit history between 6.1.4 and 6.1.6 to understand what is going on? Maybe diff the source if it is easier? > I am using Intel CPU and that it works fine (did not check sound in VM): > :; pkg list virtualbox > NAME (PUBLISHER) VERSION > IFO > system/virtualbox 6.1.8-2020.0.1.0 > i-- > > From "prtdiag -v" > Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz CPUSocket > > > Regards. > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > -- > Predrag Zečević > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade
Let me know if you can install this: http://dlc-int.openindiana.org/users/aurelien/virtualbox/virtualbox_6.1.8.p5a pfexec pkg install -g virtualbox_6.1.8.p5a virtualbox (virtualbox-additions also provided for guests) On Sun, May 17, 2020 at 4:41 PM Carl Brewer wrote: > On 17/05/2020 8:00 pm, Aurélien Larcher wrote: > > > Would you be able to give it shot? > > I can assist if there is any problem but currently there is still a lot > of > > work with the gcc-10 builds and rust/firefox update... > > I can test, but I don't know how to do a build > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade
On Mon, May 18, 2020 at 12:03 PM Stephan Althaus <
stephan.alth...@duedinghausen.eu> wrote:
> Hello!
>
> I build and installed VB 6.1.8 in to a new BW, got some errors on startup.
> Patch #18 ist no more needed. Makefile ist attached.
>
> $ svcs -xv
> svc:/application/virtualbox/vboxservice:default (VirtualBox Service.)
> State: maintenance since 18 May 2020 at 11:44:26 CEST
> Reason: Start method failed repeatedly, last exited with status 1.
> See: http://illumos.org/msg/SMF-8000-KS
> See: /var/svc/log/application-virtualbox-vboxservice:default.log
> Impact: This service is not running.
>
> svc:/application/virtualbox/vboxmslnk:default (VirtualBox Mouse module
> link.)
> State: maintenance since 18 May 2020 at 11:44:26 CEST
> Reason: Start method failed repeatedly, last exited with status 1.
> See: http://illumos.org/msg/SMF-8000-KS
> See: /var/svc/log/application-virtualbox-vboxmslnk:default.log
> Impact: This service is not running.
> steven@dell6510:~$ cat
> /var/svc/log/application-virtualbox-vboxservice:default.log
> [ May 18 11:44:25 Enabled. ]
> [ May 18 11:44:25 Rereading configuration. ]
> [ May 18 11:44:26 Executing start method ("/usr/bin/VBoxService"). ]
> VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
> [ May 18 11:44:26 Method "start" exited with status 1. ]
> [ May 18 11:44:26 Executing start method ("/usr/bin/VBoxService"). ]
> VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
> [ May 18 11:44:26 Method "start" exited with status 1. ]
> [ May 18 11:44:26 Executing start method ("/usr/bin/VBoxService"). ]
> VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
> [ May 18 11:44:26 Method "start" exited with status 1. ]
> steven@dell6510:~$ cat
> /var/svc/log/application-virtualbox-vboxmslnk:default.log
> [ May 18 11:44:25 Enabled. ]
> [ May 18 11:44:25 Rereading configuration. ]
> [ May 18 11:44:26 Executing start method ("/usr/sbin/vboxmslnk"). ]
> Oracle VM VirtualBox Guest Additions enabling utility for Solaris pointer
> integration Version 6.1.8
> (C) 2020 Oracle Corporation
> All rights reserved.
>
> Failed to open /dev/vboxms - please make sure that the node exists and that
> you have permission to open it. The error reported was:
> Invalid argument
> [ May 18 11:44:26 Method "start" exited with status 1. ]
> [ May 18 11:44:26 Executing start method ("/usr/sbin/vboxmslnk"). ]
> Oracle VM VirtualBox Guest Additions enabling utility for Solaris pointer
> integration Version 6.1.8
> (C) 2020 Oracle Corporation
> All rights reserved.
>
> Failed to open /dev/vboxms - please make sure that the node exists and that
> you have permission to open it. The error reported was:
> Invalid argument
> [ May 18 11:44:26 Method "start" exited with status 1. ]
> [ May 18 11:44:26 Executing start method ("/usr/sbin/vboxmslnk"). ]
> Oracle VM VirtualBox Guest Additions enabling utility for Solaris pointer
> integration Version 6.1.8
> (C) 2020 Oracle Corporation
> All rights reserved.
>
> Failed to open /dev/vboxms - please make sure that the node exists and that
> you have permission to open it. The error reported was:
> Invalid argument
> [ May 18 11:44:26 Method "start" exited with status 1. ]
>
>
I do not understand... is it in the host or the guest?
>
> Greetings,
> Stephan
>
>
> On 05/17/20 12:00, Aurélien Larcher wrote:
> > On Sun, May 17, 2020 at 11:55 AM Carl Brewer
> wrote:
> >
> >> On 16/05/2020 10:25 pm, Aurélien Larcher wrote:
> >>> This is now fixed in
> >>>
> >>>
> >>
> https://github.com/illumos/illumos-gate/commit/bd025ac2b6fbfbc59dfc0bd50a0e56dd56de9229
> >>> and will be published to the repository within 1 hour.
> >> Hot on its heels, 6.1.8 has just been released.
> >>
> > Would you be able to give it shot?
> > I can assist if there is any problem but currently there is still a lot
> of
> > work with the gcc-10 builds and rust/firefox update...
> > Thank you :)
> >
> >
> >> ___
> >> 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
>
--
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Σχετ: Re: Σχετ: Re: Latest VirtualBox
On Sun, May 17, 2020 at 12:43 PM Apostolos Syropoulos via openindiana-discuss wrote: > > Upgrading the BIOS may make thesystem unbootable. I have seen thisbehavior > a couple of times. BTW this isnot an option since the previous > versionworked. > You should then open a ticket at the Virtualbox tracker describing your problem, they are more likely to know what they changed in the code. > Στάλθηκε από το Ταχυδρομείο Yahoo σε Android > > Στις Κυρ, 17 Μαΐ, 2020 στις 13:30, ο χρήστηςAurélien Larcher< > aurelien.larc...@gmail.com> έγραψε:> > > In one ticket the person had to upgrade the BIOS as it was the culprit. > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Σχετ: Re: Latest VirtualBox
On Sun, May 17, 2020 at 12:02 PM Apostolos Syropoulos via openindiana-discuss wrote: > First I tried to disable AMD virtualization from > Settings --> System --> Processor > and by unticking the option > Enable Nested Vt-x/AMD-V > And kvm is not installed on this system: > $ pkg list kvm > > pkg list: no packages matching the following patterns are installed: > kvm > > The question is: other people who reportedthe same error, continue to see > the sameerror? > In one ticket the person had to upgrade the BIOS as it was the culprit. > Regards, > Apostolos > > Στάλθηκε από το Ταχυδρομείο Yahoo σε Android > > Στις Κυρ, 17 Μαΐ, 2020 στις 12:39, ο χρήστηςAurélien Larcher< > aurelien.larc...@gmail.com> έγραψε > Also I wonder if our kvm package may be interfering with VirtualBox... > Could you check whether it is installed? > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade
On Sun, May 17, 2020 at 11:55 AM Carl Brewer wrote: > On 16/05/2020 10:25 pm, Aurélien Larcher wrote: > > This is now fixed in > > > > > https://github.com/illumos/illumos-gate/commit/bd025ac2b6fbfbc59dfc0bd50a0e56dd56de9229 > > > > and will be published to the repository within 1 hour. > > Hot on its heels, 6.1.8 has just been released. > Would you be able to give it shot? I can assist if there is any problem but currently there is still a lot of work with the gcc-10 builds and rust/firefox update... Thank you :) > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
