Re: [OpenIndiana-discuss] Virtualbox 6.1.22?
On 10/05/2021 9:47 pm, Andreas Wacknitz wrote: I have created a PR: https://github.com/OpenIndiana/oi-userland/pull/6739 As I said before: I cannot test it so I will leave it to the community to test it appropriately and give it an approval. Testing it now, will let you know Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Which OI service cleans up hidden NFS files?
I can confirm the problem is solved. I also unmounted the "problematic"
datasets since znapzend doesn't need them to be mounted.
On Tue, May 4, 2021 at 6:42 PM Judah Richardson
wrote:
> nfsfind script is as follows:
>
> if [ ! -s /etc/dfs/sharetab ]; then exit ; fi
>
> # Get all NFS filesystems exported with read-write permission.
>
> DIRS=`/usr/bin/nawk '($3 != "nfs") { next }
> ($4 ~ /^rw$|^rw,|^rw=|,rw,|,rw=|,rw$/) { print $1; next }
> ($4 !~ /^ro$|^ro,|^ro=|,ro,|,ro=|,ro$/) { print $1 }'
> /etc/dfs/sharetab`
>
> for dir in $DIRS
> do
> find $dir -type f -name .nfs\* -mtime +7 -mount -exec rm -f {} \;
> done
>
> Here's what's in /etc/dfs/sharetab:
>
> /znapzend/DellOptiPlex390MT/ROOT/openindiana- nfs
> sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32
> /znapzend/DellOptiPlex390MT/export/home/judah - nfs
> sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32
> /znapzend/DellOptiPlex390MT - nfs sec=sys,rw=@
> 192.168.0.107/32,root=@192.168.0.107/32
> /rpool1 - nfs sec=sys,rw=@
> 192.168.0.107/32,root=@192.168.0.107/32
> /znapzend - nfs sec=sys,rw=@
> 192.168.0.107/32,root=@192.168.0.107/32
> /znapzend/DellOptiPlex390MT/export - nfs sec=sys,rw=@
> 192.168.0.107/32,root=@192.168.0.107/32
> /znapzend/DellOptiPlex390MT/export/home - nfs sec=sys,rw=@
> 192.168.0.107/32,root=@192.168.0.107/32
> /znapzend/DellOptiPlex390MT/ROOT- nfs sec=sys,rw=@
> 192.168.0.107/32,root=@192.168.0.107/32
>
> Now, I only ever explicitly (i.e. manually executed a command to) NFS
> shared rpool1. It looks like all the child filesystems (created
> afterwards) got shared too.
>
> Let's see what happens when I try to unshare the child datasets:
>
> # zfs set sharenfs=off rpool1/znapzend
>
> Now /etc/dfs/sharetab contains:
>
> /rpool1 - nfs sec=sys,rw=@
> 192.168.0.107/32,root=@192.168.0.107/32
>
> $ cd /rpool1 (where rpool1 is mounted) works, so I think that should fix
> the problem, in theory. Unless anyone thinks it won't, in which case I urge
> you to speak up :)
>
> Thank you for the investigative direction idea and you and Alan both for
> the quick replies.
>
> On Tue, May 4, 2021 at 6:28 PM Joshua M. Clulow via openindiana-discuss <
> openindiana-discuss@openindiana.org> wrote:
>
>> On Tue, 4 May 2021 at 16:25, Judah Richardson
>> wrote:
>> > Extremely stupid question: is the fact that those mounted locations
>> contain
>> > ZFS snapshots resulting from znapzend's underlying use of zfs send &
>> receive
>> > and not actual physical directories possibly why find, cd, etc. can't
>> reach
>> > them?
>> >
>> > Shooting in the dark here; that's the only thing I can come up with.
>>
>> I think it would be easiest to take a look at the shell script and see
>> what it gets out of sharetab and what it does with find.
>>
>> Cheers.
>>
>> --
>> Joshua M. Clulow
>> http://blog.sysmgr.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] OpenIndiana Issue-Services Won't Start
In message , Mike Carroll writes: >So using the latest image (and used Linux DD command to make a bootable USB), >it hangs on the preparing live image (then complains of services not starting >and needing to get into the maintenance mode). I am using an HP 800 G1 Mini. Possibly this bug: https://www.illumos.org/issues/13598> Two potential work-arounds for you: Configure your firmware to boot in BIOS mode. Use a USB CD drive. John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OpenIndiana Issue-Services Won't Start
Ok. I might just have to load a CD drive as I have Legacy enabled. From: John D Groenveld Sent: Monday, May 10, 2021 2:05 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] OpenIndiana Issue-Services Won't Start In message , Mike Carroll writes: >So using the latest image (and used Linux DD command to make a bootable USB), >it hangs on the preparing live image (then complains of services not starting >and needing to get into the maintenance mode). I am using an HP 800 G1 Mini. Possibly this bug: https://www.illumos.org/issues/13598> Two potential work-arounds for you: Configure your firmware to boot in BIOS mode. Use a USB CD drive. 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
[OpenIndiana-discuss] The Register today
https://www.theregister.com/2021/05/10/illumos_deprecates_sparc_support/?td=keepreading-btm Sad, but that's the way it is. /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] The Register today
On Sun, 9 May 2021 at 23:55, Tony Brian Albers wrote: > https://www.theregister.com/2021/05/10/illumos_deprecates_sparc_support/?td=keepreading-btm > Sad, but that's the way it is. For perhaps more context, there was a thread on the illumos developer mailing list as well: https://illumos.topicbox.com/groups/developer/T3f72cd35e06c75bd/ipd-19-sunset-sparc 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] Virtualbox and USB webcam
On Fri, 2021-05-07 at 17:37 +1000, Carl Brewer wrote: > On 8/01/2021 10:09 pm, Till Wegmueller wrote: > > Hey Tony > > > > Here in the EU I always get myself a USB Gaming Headset for my > > Audio > > needs. They are Cheap(ish) and you can get yourself a Wireless > > Headset > > that has a dedicated receiver that needs no special driver, other > > than > > Audio. You might also get away by simply using the Mic, Headset on > > the > > host and using Virtuablox Audio. > > > > And thanks for that Note that may be why I was unsuccessful in the > > past > > with certain pass through combinations. > > This isn't relevant? > https://www.virtualbox.org/ticket/20176 > > > Nah, I managed to get the webcam working fine as soon as I got the USB port right. But the mentioned bug is something that we should be aware of nevertheless. /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] The Register today
> On 10. May 2021, at 09:55, Tony Brian Albers wrote: > > https://www.theregister.com/2021/05/10/illumos_deprecates_sparc_support/?td=keepreading-btm > > Sad, but that's the way it is. > Please note that while IPD is filed, there is not yet line drawn, at least I want to get few updates integrated so whoever will decide to create fork, will get those bits too. That includes support for cpio boot archive (needs forth boot code to read cpio), code to recognize T4 cpu properties and perhaps few other bits. rgds, toomas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The Register today
> On 10. May 2021, at 10:33, Volker A. Brandt wrote:
>
> Toomas Soome via openindiana-discuss writes:
>> Please note that while IPD is filed, there is not yet line drawn, at least I
>> want to get few updates integrated so whoever will decide to create fork,
>> will get those bits too. That includes support for cpio boot archive (needs
>> forth boot code to read cpio), code to recognize T4 cpu properties and
>> perhaps few other bits.
>
> We appreciate your work, Toomas!
>
> What I find strange is that "public" reactions (like The Register) all
> mention lack of hardware. There is a lot of hardware available, and
> hosting has been offered as well.
>
> IMHO it's not hardware, it's people.
>
> I would be interested in a description of the compiler problem that
> needs to be fixed to move SPARC forward, preferably in layman's terms.
> :-) Or is it a number of unrelated issues?
>
> TBH I never paid much attention because I just assumed that my skillset
> isn't up to understanding the problem anyway, let alone fixing it.
>
> We are very close to having a self-hosted OpenIndiana for SPARC, and I
> would like to investigate how to leverage that.
>
>
The immediate issue is https://www.illumos.org/issues/2757. In core, this issue
means that negative 32-bit numbers are not translated to negative 64-bit
numbers. Currently used gcc 4.4.4 does implement such translation in compiler,
there is no such patch for more recent compilers (firstly, the code path in
more recent compilers has changed a lot, and secondly, such translation should
be done by OS). This effectively does block switch from gcc 4.4.4. I actually
am running gcc 7 built system, knowingly, keeping in mind that I may be bitten
by problems cause by this issue.
Secondly, there are SPARC optimizer issues in gcc 7 and gcc 9 (likely with 10
as well), crashing compiler while building specific parts of illumos tree. One
example:
libcurses: gcc 9 bug with -O2
../screen/tparm.c: In function 'tparm':
../screen/tparm.c:727:1: error: insn does not satisfy its constraints:
727 | }
| ^
(insn:TI 66 1769 1770 (set (reg:DI 8 %o0)
(mem/u/c:DI (plus:DI (reg:DI 13 %o5)
(symbol_ref:DI ("result.4619") [flags 0x2] )) [0 S8 A64])) 125 {*movdi_insn_sp64}
(expr_list:REG_EQUAL (symbol_ref:DI ("result.4619") [flags 0x2]
)
(nil)))
during RTL pass: final
../screen/tparm.c:727:1: internal compiler error: in final_scan_insn_1, at
final
.c:3013
0x6ba95b _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/rtl-error.c:1
08
0x6ba997 _fatal_insn_not_found(rtx_def const*, char const*, int, char
const*)
/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/rtl-error.c:1
18
0x42a623 final_scan_insn_1
/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:3013
0x42a6bf final_scan_insn(rtx_insn*, __FILE*, int, int, int*)
/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:3153
0x429fb7 final_scan_insn_1
/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:2759
0x42a6bf final_scan_insn(rtx_insn*, __FILE*, int, int, int*)
/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:3153
0x42a943 final_1
/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:2021
0x42c3cb rest_of_handle_final
/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:4659
0x42c3cb execute
/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:4737
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
I haven’t had time to open bugreport with gcc.
And then there are some other issues related to optimizations/hacks created to
support specific network cards, and so on. A lot of work to get those issues
fixed, so that we wont be blocking illumos-gate, and unfortunately, very small
group of users.
As a side note, it is interesting to see SPARC related discussion in this list;
there is no package repository for SPARC by OpenIndiana;)
Considering all the above, I was also one of those asking if it is really good
for illumos to keep this baggage. Perhaps it is time to let go.
rgds,
toomas
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The Register today
Toomas Soome via openindiana-discuss writes: > Please note that while IPD is filed, there is not yet line drawn, at least I > want to get few updates integrated so whoever will decide to create fork, > will get those bits too. That includes support for cpio boot archive (needs > forth boot code to read cpio), code to recognize T4 cpu properties and > perhaps few other bits. We appreciate your work, Toomas! What I find strange is that "public" reactions (like The Register) all mention lack of hardware. There is a lot of hardware available, and hosting has been offered as well. IMHO it's not hardware, it's people. I would be interested in a description of the compiler problem that needs to be fixed to move SPARC forward, preferably in layman's terms. :-) Or is it a number of unrelated issues? TBH I never paid much attention because I just assumed that my skillset isn't up to understanding the problem anyway, let alone fixing it. We are very close to having a self-hosted OpenIndiana for SPARC, and I would like to investigate how to leverage that. Thanks -- 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
Re: [OpenIndiana-discuss] The Register today
Toomas Soome writes: > The immediate issue is https://www.illumos.org/issues/2757. In core, this > issue means that negative 32-bit numbers are not translated to negative > 64-bit numbers. Currently used gcc 4.4.4 does implement such translation in > compiler, there is no such patch for more recent compilers (firstly, the > code path in more recent compilers has changed a lot, and secondly, such > translation should be done by OS). This effectively does block switch from > gcc 4.4.4. I actually am running gcc 7 built system, knowingly, keeping in > mind that I may be bitten by problems cause by this issue. In other words, when that issue is fixed, the primary compiler could be switched to gcc 7? > Secondly, there are SPARC optimizer issues in gcc 7 and gcc 9 (likely with > 10 as well), crashing compiler while building specific parts of illumos > tree. One example: [...] Could this be worked around by selectively turning off -O2 until that is fixed? > I haven’t had time to open bugreport with gcc. Fair enough. [...] > As a side note, it is interesting to see SPARC related discussion in this > list; there is no package repository for SPARC by OpenIndiana;) Yes. However, there are people working on new infrastructure for OI; as soon as that is in place there will be a public repo for OI/SPARC. Cheers -- 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
Re: [OpenIndiana-discuss] Virtualbox 6.1.22?
Am 07.05.21 um 09:35 schrieb Carl Brewer: Hey Andreas et al, I just noticed VirtualBox 6.1.22 was released a few days ago, I'm happy to test it out if there's a build ready to go? Thank you Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I have created a PR: https://github.com/OpenIndiana/oi-userland/pull/6739 As I said before: I cannot test it so I will leave it to the community to test it appropriately and give it an approval. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The Register today
> On 10. May 2021, at 12:05, Volker A. Brandt wrote: > > Toomas Soome writes: >> The immediate issue is https://www.illumos.org/issues/2757. In core, this >> issue means that negative 32-bit numbers are not translated to negative >> 64-bit numbers. Currently used gcc 4.4.4 does implement such translation in >> compiler, there is no such patch for more recent compilers (firstly, the >> code path in more recent compilers has changed a lot, and secondly, such >> translation should be done by OS). This effectively does block switch from >> gcc 4.4.4. I actually am running gcc 7 built system, knowingly, keeping in >> mind that I may be bitten by problems cause by this issue. > > In other words, when that issue is fixed, the primary compiler could be > switched to gcc 7? yes, assuming the needed cleanups are done;) but then again, this issue has been open for ~10 years. > >> Secondly, there are SPARC optimizer issues in gcc 7 and gcc 9 (likely with >> 10 as well), crashing compiler while building specific parts of illumos >> tree. One example: > [...] > > Could this be worked around by selectively turning off -O2 until that > is fixed? I have -O1 in my local patch, yes. But, the implication of this issue is, we do not really know how much, or to what extent, we can count on gcc. I do realize this does sound like FUD, but we do depend on external compiler and projects are rather removing SPARC support... > >> I haven’t had time to open bugreport with gcc. > > Fair enough. > > [...] >> As a side note, it is interesting to see SPARC related discussion in this >> list; there is no package repository for SPARC by OpenIndiana;) > > Yes. However, there are people working on new infrastructure for OI; > as soon as that is in place there will be a public repo for OI/SPARC. > Yes, I am aware of that too. From one hand it is nice, but from other hand, there is a reason *why* I would vote for removing SPARC support. And the reason is, I do think we should stop looking backward and start looking forward. I’d rather spend my time on building support for things like arm64 or risc-v or some quantum computer or something what really matters for future of this OS. rgds, toomas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] OpenIndiana Issue-Services Won't Start
So using the latest image (and used Linux DD command to make a bootable USB), it hangs on the preparing live image (then complains of services not starting and needing to get into the maintenance mode). I am using an HP 800 G1 Mini. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
