Re: [OpenIndiana-discuss] Tasks to focus on
Am 08.01.21 05:15 schrieb Chris : > > On 2021-01-07 19:06, Till Wegmueller wrote: > >On 07.01.21 23:47, Joshua M. Clulow via openindiana-discuss wrote: > >>On Thu, 7 Jan 2021 at 13:57, Till Wegmueller wrote: > >>>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. > >> > >>Before you spend any money, or at least in parallel with doing so, I > >>would encourage you to see if Fosshost will provide some resources for > >>the project. They have reached out to illumos in the past, and I > >>think OpenIndiana meets all of their eligibility criteria (open > >>source, no commercial backing, etc): > >> > >> https://fosshost.org > >> > >>It seems they will provide one or more virtual machines to projects > >>for hosting of web resources and builds and such. > >> > > > >Oh nice will have a talk with them also. That one server is not just for OI, > >it is > >also to replace my failed HomeLab server and move stuff from that out to a > >DC. And > >then also to host some company resources and others. But Of course I would > >not > >need that much RAM for that. > > > >Let's see what they can do. But having infrastructure under our control is > >the > >Goal. Evercity is doing a very good sponsoring but we need to do updates to > >the > >Jenkins infrastructure and redo the setup. So having somewhere where we can > >do > >that without needing to burden work onto others is one of our goals with > >this. And > >we will also need a couple of package servers. > You might also be interested in what Oregon State University is offering > (free to opren source && includes IPv6) > https://osuosl.org/services/hosting/ > > > > >>>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. > >> > >>If you hit any trouble with Rust, I'd love to hear about it! We have > >>a good relationship with the Rust project itself, so we should be able > >>to get things fixed as they arise, without needing to float additional > >>patches. > I try to build firefox 78esr for openindiana. The problems with Rust are much smaller than a while ago. But I stopped to use the rustc installed with rustup because this use a toolchain naming like x86_64-unknown-illumos. For that the rustc sources build instruction have to extent for target_os "solaris" to target_os "illumos", which is an additional effort. So I updated the oi-userland build reciept for rust to provide an newer version (1.41.1) where the target tripple x86_64-sun-solaris is used. So there are no patching of lib.rs and others is necessary. Or it is possible with rustup to get the target toolchain x86_64-sun-solaris also? > > > > > >Will let you know how it went in any case. I expect no big problems though. > > > >-Till > > > >___ > >openindiana-discuss mailing list > >openindiana-discuss@openindiana.org > >https://openindiana.org/mailman/listinfo/openindiana-discuss > > -- > ~40yrs of UNIX and counting > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- Carsten Grzemba ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Tasks to focus on
On 2021-01-07 19:06, Till Wegmueller wrote: On 07.01.21 23:47, Joshua M. Clulow via openindiana-discuss wrote: On Thu, 7 Jan 2021 at 13:57, Till Wegmueller wrote: 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. Before you spend any money, or at least in parallel with doing so, I would encourage you to see if Fosshost will provide some resources for the project. They have reached out to illumos in the past, and I think OpenIndiana meets all of their eligibility criteria (open source, no commercial backing, etc): https://fosshost.org It seems they will provide one or more virtual machines to projects for hosting of web resources and builds and such. Oh nice will have a talk with them also. That one server is not just for OI, it is also to replace my failed HomeLab server and move stuff from that out to a DC. And then also to host some company resources and others. But Of course I would not need that much RAM for that. Let's see what they can do. But having infrastructure under our control is the Goal. Evercity is doing a very good sponsoring but we need to do updates to the Jenkins infrastructure and redo the setup. So having somewhere where we can do that without needing to burden work onto others is one of our goals with this. And we will also need a couple of package servers. You might also be interested in what Oregon State University is offering (free to opren source && includes IPv6) https://osuosl.org/services/hosting/ 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. If you hit any trouble with Rust, I'd love to hear about it! We have a good relationship with the Rust project itself, so we should be able to get things fixed as they arise, without needing to float additional patches. Will let you know how it went in any case. I expect no big problems though. -Till ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss -- ~40yrs of UNIX and counting ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Tasks to focus on
On Thu, 7 Jan 2021 at 19:06, Till Wegmueller wrote: > On 07.01.21 23:47, Joshua M. Clulow via openindiana-discuss wrote: > > On Thu, 7 Jan 2021 at 13:57, Till Wegmueller wrote: > > https://fosshost.org > > > > It seems they will provide one or more virtual machines to projects > > for hosting of web resources and builds and such. > Let's see what they can do. But having infrastructure under our control > is the Goal. Evercity is doing a very good sponsoring but we need to do > updates to the Jenkins infrastructure and redo the setup. So having > somewhere where we can do that without needing to burden work onto > others is one of our goals with this. And we will also need a couple of > package servers. Yes, my hope would be that you'd get full control (including console access) to one or more full virtual machines, and thus be able to install and run OI and manage your own updates on your own schedule. Cheers. -- Joshua M. Clulow http://blog.sysmgr.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Tasks to focus on
On 07.01.21 23:47, Joshua M. Clulow via openindiana-discuss wrote: On Thu, 7 Jan 2021 at 13:57, Till Wegmueller wrote: 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. Before you spend any money, or at least in parallel with doing so, I would encourage you to see if Fosshost will provide some resources for the project. They have reached out to illumos in the past, and I think OpenIndiana meets all of their eligibility criteria (open source, no commercial backing, etc): https://fosshost.org It seems they will provide one or more virtual machines to projects for hosting of web resources and builds and such. Oh nice will have a talk with them also. That one server is not just for OI, it is also to replace my failed HomeLab server and move stuff from that out to a DC. And then also to host some company resources and others. But Of course I would not need that much RAM for that. Let's see what they can do. But having infrastructure under our control is the Goal. Evercity is doing a very good sponsoring but we need to do updates to the Jenkins infrastructure and redo the setup. So having somewhere where we can do that without needing to burden work onto others is one of our goals with this. And we will also need a couple of package servers. 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. If you hit any trouble with Rust, I'd love to hear about it! We have a good relationship with the Rust project itself, so we should be able to get things fixed as they arise, without needing to float additional patches. Will let you know how it went in any case. I expect no big problems though. -Till ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Tasks to focus on
On Thu, 7 Jan 2021 at 18:26, Nelson H. F. Beebe wrote: > Those compilers can then bootstrap LLVM / Clang compilers. Absolutely > EVERYTHING ELSE is contingent on having reliable and modern C and C++ > compilers (and also Ada, D, Java (gcc-6 and earlier only), Fortran, > Objective C/C++, Pascal, ). Those can then build new gcc-go, > Rust, awk / mawk / gawk, Javascript, pcc, Python, tcc, releases. > > Google Go was originally written in C, but two or three years ago, it > was rewritten in Go, with a C-based bootstrap compiler used to get the > process rolling. You shouldn't need the old (Go ~1.4) C-based bootstrap compiler any longer. You can build an illumos/amd64 bootstrap archive of the Go main branch on any platform that supports Go; e.g., Linux or Mac OS X or any other illumos system. Ideally everything you want to build with Go can be built with the current latest official Go toolchain without patches. We have a good relationship with the Go project and can make fixes upstream as problems arise, and I can likely help get patches pushed up there as well. If you need a prebuilt illumos toolchain to get started I have put a few versions up at: https://illumos.org/downloads/ Cheers. -- Joshua M. Clulow http://blog.sysmgr.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Tasks to focus on
On Thu, 7 Jan 2021 at 13:57, Till Wegmueller wrote: > Hey Aurelian > > Nice to have you back! Yes, indeed! Sorry to hear you were ill, and glad to hear you are on the mend! > 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. Before you spend any money, or at least in parallel with doing so, I would encourage you to see if Fosshost will provide some resources for the project. They have reached out to illumos in the past, and I think OpenIndiana meets all of their eligibility criteria (open source, no commercial backing, etc): https://fosshost.org It seems they will provide one or more virtual machines to projects for hosting of web resources and builds and such. > 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. If you hit any trouble with Rust, I'd love to hear about it! We have a good relationship with the Rust project itself, so we should be able to get things fixed as they arise, without needing to float additional patches. Cheers. -- Joshua M. Clulow http://blog.sysmgr.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Tasks to focus on
Aurelien Larcher kindly posted his OpenIndiana project list from last spring in e-mail on this list of Thu, 7 Jan 2021 22:39:12 +0100. Among your projects from March 2020, I believe strongly that the most important BY FAR is getting gcc-10 to build itself and all of the OpenIndiana / Omnios software suite. Once that is done, then gcc-11 should be a breeze (I've personally done several thousand builds of gcc-x for x in 2--11). Those compilers can then bootstrap LLVM / Clang compilers. Absolutely EVERYTHING ELSE is contingent on having reliable and modern C and C++ compilers (and also Ada, D, Java (gcc-6 and earlier only), Fortran, Objective C/C++, Pascal, ). Those can then build new gcc-go, Rust, awk / mawk / gawk, Javascript, pcc, Python, tcc, releases. Google Go was originally written in C, but two or three years ago, it was rewritten in Go, with a C-based bootstrap compiler used to get the process rolling. The GNU Ada translator (gnat) has a similar bootstrap problem, because part of gnat after gcc-4.x was foolishly rewritten in Ada itself, instead of being kept in portable Standard C that can be built pretty much anywhere, and also made available in new CPU environments as new compiler backends are written (e.g,, ARM and RISC-V in recent years). That makes porting software and O/Ses to new CPU platforms much easier. I've been using Unix systems for almost 40 years, and have a farm of more than 500 flavors of such for most of the main CPU families. Old vendor-supplied compiler versions have caused huge pain in Red Hat, CentOS, Solaris, and OpenBSD, because they make it impossible to build a lot of newer software. While I'm often able to build newer gcc and clang releases, most computer users are completely stuck with what the vendor or O/S distribution provides, and could not possibly build gcc or clang on their own. --- - Nelson H. F. BeebeTel: +1 801 581 5254 - - University of UtahFAX: +1 801 581 4148 - - Department of Mathematics, 110 LCBInternet e-mail: be...@math.utah.edu - - 155 S 1400 E RM 233 be...@acm.org be...@computer.org - - Salt Lake City, UT 84112-0090, USAURL: http://www.math.utah.edu/~beebe/ - --- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] New SPARC ISO for testing
This ISO is the same as the previous 2018 ISO except for two bug
fixes. If the last one didn't work for you, this one might.
One of the fixes is for one of disk drivers, one that's only used on
newer systems. It happens because driver is in two parts, causing the
boot to fail. It stops with this error:
undefined symbol 'sata_split_model'
The other is for the bash shell. The problem in this case, is that
it needs a library. If it's missing, the single-user console fails,
resulting in this error:
bash: fatal: libncurses.so.5: open failed
To use the new ISO, first download it from this location:
https://apt.dilos.org/oi-sparc/OI_2018_02_Text_SPARC.iso.gz
Then, check it's integrity like this:
$ digest -a sha256 OI_2018_02_Text_SPARC.iso.gz
9ea289ef064e320200ae979dae25e0c2aa8846fa57f033d742c0612cd654397f
Next, uncompress it with a command like this:
$ gunzip OI_2018_02_Text_SPARC.iso.gz
Then, burn it to a DVD. Note that the file OI_2018_02_Text_SPARC.iso
is a bootable DVD image. There's no known way to transfer it to a USB
stick. You must create and boot a DVD. As well, only the text DVD
image is available for the SPARC platform.
Next, boot the DVD on your SPARC machine. This OBP command worked for
me, although I had to do it twice:
{0} ok boot cdrom
When the text boot is successful, it will guide you through the
process of configuring and installing OI. Near the end, it will ask
you to select a disk to receive the OI installation.
Finally, boot the disk that contains the newly-installed copy of OI.
It can be used with the original repository to install new packages.
I'd like to get your reports on this new ISO. Both it and the
original ISO boot and run correctly on my T2000 system. However, it
may not run on different SPARC systems. In particular, I'd like to
know if the new ISO boots and runs on newer hardware. Please report
your hardware, and whether it succeeded or failed. If it failed, I'd
like to see the error messages. If the new ISO is successful, I will
be uploading a newer matching repository.
--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-
___
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 2021-01-07 13: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. IMHO No that RHEL is in bed with IBM, and as a result; RHEL, and CentOS taking quite a different path. OI is likely to see a greater influx of users. A quick look on the CentOS mailinglists/forums indicates thier userbase is LIVID about the changes. The was not one single positive note about the change. tl;dr A lot of CentOS, and as a result, RHEL users; are abandoning ship. They'll all be going *somewhere*. Maybe it's to OI. :-) --Chris 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
Re: [OpenIndiana-discuss] [oi-dev] Tasks to focus on
On 2021-01-07 13: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. Congrats on your Covid recovery! I can relate, as I got it bad back in late December. It's no picnic; that's for sure. While I'm not attempting to create your priority list. As the maintainer of some 160 FreeBSD ports, and a happy OI user. I'd like to pitch in, and offer time, and CPU cycles to help out. I'm afraid I wouldn't know where to start. Or rather; I'm well familiar with setting up build farms (jails) and building/fixing rebuilding everything. I'm really just looking for a list of things to start with. Feel free to contact me off list if you like. All the best! --Chris Kind regards, Aurelien ___ oi-dev mailing list oi-...@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev ___ 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
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
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. -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
Re: [OpenIndiana-discuss] Tasks to focus on
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. 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. 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. PS. would you like to be invited to the Maintainer meetup? It's on the thirst Wednesday every month 19:00 PM Berlin timezone. -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
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
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] 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] Virtualbox and USB webcam
Hey Tony That sounds to me like the a kernel driver is attaching to the device and thus Virtualbox cannot do that anymore. There is a blacklisting capability but I have never done that or know how exactly that works, or if it helps in this situation. It should be comparable to bhyve passthrough setups where a Host OS driver already attaches. And I know there are guides there for that. but you might ask best on IRC about specifically Virtualbox passthrough. As we have new facilities to achieve such a passthrough. I also remember this issue being solved once before. So you may also want to search the archives. -Till On 07.01.21 11:53, Tony Brian Albers wrote: Hi guys, I'm trying to get my webcam to work in a vbox guest (to use zoom), but even though it seems to be present in the VM, cheese, zoom and qv4l2 only shows a blank screen. The video device is there though. On the host I see: messages:Jan 7 15:46:00 emu usba: [ID 691482 kern.warning] WARNING: /pci@0,0/pci1028,546@14 (xhci0): usb_mid2 cannot be reset due to other applications are using it, please first close these applications, then disconnect and reconnectthe device. In /var/adm/messages. I'm using virtualbox 6.1.16 r140961 with the extension pack of the same version and guest additions. I use the webcam passthrough option under "Devices". The guest is SolydX64 (debian respin) Does anyone have any ideas? I haven't been able to find any info about this specific issue. TIA /tony ___ 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)
Nope On 07.01.21 18:05, Guenther Alka wrote: Please ignore my lack of knowledge if I am not correct or simplify too much. As far as I know kayak is a tool to setup OmniOS. I do not use. I download either the OI or OmniOS installer, create a bootable dvd or USB stick from it and install the OS. When I use the OI text installer the result is quite identical to a OmniOS default setup. The installer is kayak on OmniOS. On OpenIndiana it is slim_cd whcih is the OpenSolaris one. would this work and gives you the current OI user experience on top of a stable OmniOS base? Nope. That would give you a package dependency hell. No package would be installable, as they are all built against different dependency version. 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
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
Please ignore my lack of knowledge if I am not correct or simplify too much. As far as I know kayak is a tool to setup OmniOS. I do not use. I download either the OI or OmniOS installer, create a bootable dvd or USB stick from it and install the OS. When I use the OI text installer the result is quite identical to a OmniOS default setup. What would happen if - you use a current OI text setup with the default current OmniOS stable repository instead the OI repository (update this every 6 months to next OmniOS repo on next regular OI iso or via an OI update) After this OmniOS and OI should be quite identical even after a pkg update - add the OmniOS extra repository with some server related packages (I mostly use smartmontools, nc and minIO) this gives all tools that are supported by OmniOS (update every 6 months to next stable) - add the OI repository (that contains all OI packages minus the ones from OmniOS default and extra) - then install tools like Mate GUI, browser or Office would this work and gives you the current OI user experience on top of a stable OmniOS base? Gea Am 07.01.2021 um 20:53 schrieb Till Wegmueller: So, to that question a bit of Background. OmniOS is more than just illumos and omni repo. It's also kayak and all their Projects. That is a huge amount of projects. There was work to allow installation of omnios illumos-gate instead of illumos-gate by simply switching packages. That can work, because we have consolidations and metapackages that bundle illumos-gate into one tree of packages where everything depends on. This work was started by Jim Klimov and me on the last FOSDEM but due to lack of experience with oi-userland and make it never went anywhere. It's in PR https://github.com/OpenIndiana/oi-userland/pull/5528 If anyobody is actually interested in picking it up. And a last not on illumos-gate and stability. Originally the patches omnios included into it's for of illumos-gate where still considered experimental/not yet ready to upstream. Now we see people saying those experimental patches are more stable than the illumos-gate with stability guarantee in master. If anything is broken from illumos-gate it gets fixed very quickly. The problem all complaints are about packages from oi-userland not illumos-gate. -Till On 07.01.21 14:29, Guenther Alka wrote: I forgot What is the problem to install either pure Illumos or a Illumos freeze from OmniOS and use the OI repository additional to the core OmniOS and OmniOS extra repository to use the additional options? Where are the problems? Is this only to have same packages in different repositories or that OI would need something similar to the OmniOS extra repository when using Illumos to avoid conflicts? Maybe this can be solved to allow a underlying pure ongoing Illumos or one of the three OmniOS flavours. Please educate me. Gea Am 07.01.2021 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 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-d
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)
So, to that question a bit of Background. OmniOS is more than just illumos and omni repo. It's also kayak and all their Projects. That is a huge amount of projects. There was work to allow installation of omnios illumos-gate instead of illumos-gate by simply switching packages. That can work, because we have consolidations and metapackages that bundle illumos-gate into one tree of packages where everything depends on. This work was started by Jim Klimov and me on the last FOSDEM but due to lack of experience with oi-userland and make it never went anywhere. It's in PR https://github.com/OpenIndiana/oi-userland/pull/5528 If anyobody is actually interested in picking it up. And a last not on illumos-gate and stability. Originally the patches omnios included into it's for of illumos-gate where still considered experimental/not yet ready to upstream. Now we see people saying those experimental patches are more stable than the illumos-gate with stability guarantee in master. If anything is broken from illumos-gate it gets fixed very quickly. The problem all complaints are about packages from oi-userland not illumos-gate. -Till On 07.01.21 14:29, Guenther Alka wrote: I forgot What is the problem to install either pure Illumos or a Illumos freeze from OmniOS and use the OI repository additional to the core OmniOS and OmniOS extra repository to use the additional options? Where are the problems? Is this only to have same packages in different repositories or that OI would need something similar to the OmniOS extra repository when using Illumos to avoid conflicts? Maybe this can be solved to allow a underlying pure ongoing Illumos or one of the three OmniOS flavours. Please educate me. Gea Am 07.01.2021 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 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 ___ 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)
Hello everybody, I'm not in the position of propose something or provide some insight to this topic since I've started contributing to OI just in recent three months. But I can say that I don't lack spirit, yet I do lack experience and knowledge. My backgroud isn't IT, I'm not familiar with C family languages and everything is new to me. It takes me forever to prepare propper PR. I'm able to contribute just because I can choose what to do and when something doesn' t work, I can abandon it. Therefore, if the projects merged, I wouldn't be able to contribute in any way since I hardly know what I'm doing when things are stable in OI. What I'm trying to say is that just because somebody contributes to some project doesn't necessarily mean that this person is developer to be count on. I'm affraid that on OI side, the work would heavily lie on a few (if not one) experienced delevopers. Nona -- Původní e-mail -- Od: Guenther Alka Komu: openindiana-discuss@openindiana.org Datum: 7. 1. 2021 18:53:56 Předmět: Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS) "I also own a project with mainly me and a few contributors (napp-it). It's not the number of devs but the spirit to do something that matters. You exactly point to the essential point. With not enough people working on something not paid for doing without hope and energy your only choices are sudden death (if you are the last one to leave, please switch off the light) or slow death (nobody discovered that you are already dead). As I have used Solaris, OpenSolaris, NexentaCore and now use OmniOS and OI, I would miss OI nearly as most as I would miss OmniOS. With only a few people working on something it is a matter of surviving to bundle work and not to do everything twice. OmniOS has a commercial background that may help but there are also not too many devs for an OpenSource OS. If all efforts in a free Solaris can be combined, its future is better than when you seperate them additionally without real reason. Gea Am 07.01.2021 um 18:23 schrieb Andreas Wacknitz: > 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? > > > 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. >>> __
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
I also own a project with mainly me and a few contributors (napp-it). It's not the number of devs but the spirit to do something that matters. You exactly point to the essential point. With not enough people working on something not paid for doing without hope and energy your only choices are sudden death (if you are the last one to leave, please switch off the light) or slow death (nobody discovered that you are already dead). As I have used Solaris, OpenSolaris, NexentaCore and now use OmniOS and OI, I would miss OI nearly as most as I would miss OmniOS. With only a few people working on something it is a matter of surviving to bundle work and not to do everything twice. OmniOS has a commercial background that may help but there are also not too many devs for an OpenSource OS. If all efforts in a free Solaris can be combined, its future is better than when you seperate them additionally without real reason. Gea Am 07.01.2021 um 18:23 schrieb Andreas Wacknitz: 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? 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
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
I forgot What is the problem to install either pure Illumos or a Illumos freeze from OmniOS and use the OI repository additional to the core OmniOS and OmniOS extra repository to use the additional options? Where are the problems? Is this only to have same packages in different repositories or that OI would need something similar to the OmniOS extra repository when using Illumos to avoid conflicts? Maybe this can be solved to allow a underlying pure ongoing Illumos or one of the three OmniOS flavours. Please educate me. Gea Am 07.01.2021 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 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
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
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? 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
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
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 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] Great job of programming!
This is the best UNIX (BSD) type system on the internet. In fact, it is the only BSD designed Unix that has installed on my laptop or desktop computers without spending hours upon hours of work and still failing to get the system working. It appears that all other distros have dropped support for HP G-60 series laptops and Dell's series Studio XPS computers with I-7 and AMD graphic cards. ___ 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 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] Virtualbox and USB webcam
Hi guys, I'm trying to get my webcam to work in a vbox guest (to use zoom), but even though it seems to be present in the VM, cheese, zoom and qv4l2 only shows a blank screen. The video device is there though. On the host I see: messages:Jan 7 15:46:00 emu usba: [ID 691482 kern.warning] WARNING: /pci@0,0/pci1028,546@14 (xhci0): usb_mid2 cannot be reset due to other applications are using it, please first close these applications, then disconnect and reconnectthe device. In /var/adm/messages. I'm using virtualbox 6.1.16 r140961 with the extension pack of the same version and guest additions. I use the webcam passthrough option under "Devices". The guest is SolydX64 (debian respin) Does anyone have any ideas? I haven't been able to find any info about this specific issue. 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
Re: [OpenIndiana-discuss] Merging OI + OmniOS? (And OpenZFS vs ZFS)
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? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
