Re: OBS-Studio 26.1.0 and later
Den ons 13 dec. 2023 kl 03:17 skrev hammer2_zfs : > >OBS-Studio has never been in the ports tree. You must have been using a > >third party build or self-built binaries. > > Maybe, OpenBSD 7.1/snapshots packages have OBS-Studio 26.1.0. > https://newreleases.io/project/github/obsproject/obs-studio/release/26.1.0 > > No, you can look for it at https://ftp.eu.openbsd.org/pub/OpenBSD/7.1/packages/amd64/ https://ftp.eu.openbsd.org/pub/OpenBSD/7.1/packages/i386/ and see that it is not there. I'm also fairly certain that Stuart checked the ports cvs history and did not find it there, in order to claim "it was never in the ports tree". If it wasn't ever in the ports tree, then it was never available as a package, at least not made by the OpenBSD project. So there is no 'maybe'. If there was a precompiled binary for OpenBSD, it was made by someone else and not reachable via pkg_* tools. said "Added OpenBSD support [grayed]". > https://undeadly.org/cgi?action=article;sid=20210113072623 > > Might be worth your time to read all of that rather short article. > When I was tried pkg_mgr and pkg_info -Q obs-studio, pkg_add obs-studio on > 2021. > recently. I tried these commands and get a "obs-studio is not found". > It is "not found" for the reasons you already have been told. -- May the most significant bit of your life be positive.
Re: gre over carp
Den ons 13 dec. 2023 kl 04:15 skrev All : > > >I'd like to add sasyncd in the mix and a 2nd router for higher > availability. > Don't do it. sasyncd is known not to work properly in failover scenarios. > When I ran it it did work fine for the first fail-over, but seldom (or perhaps never?) on fail-back when the master returned, so it was ok for giving me nice redundancy if the current carp master died, then I could choose a suitable time after fixing this node when to take a the hit of a new tunnel-setup as I flipped back. Never knew why it would only work one-way for me, but we had certain issues with broadcom bnx(4) cards and multicast at the time, so it could have been related to that. > >Will gre over carp work? > I think you can just try out in a vm. Don't see the reason why it would > not. > But perhaps there are some features that CARP interface doesn't support > for gre. > Do mind that carp on software-defined switch networks might need some settings in order to allow the virtual eth cards to send out frames with "bogus" mac-addresses, since some hypervisors keep good track of which macs they have given to a VM and drop ethernet frames sent with not-those mac-addresses as source. But to add to the original reply, I would probably go for two gre's towards the non-carp ips, since you are using ospf anyhow, you might just tell ospfd that one gre has a slightly higher cost than the other, and let it deal with the new network map when one of them fails. -- May the most significant bit of your life be positive.
firewall hardware
Hello! Please advise me hardware for an OpenBSD firewall: - 8 gigabit ethernet interfaces, - >= 4 Gbps throughput. Thanks, Alexei
Re: gre over carp
Yes, exactly. The fail-back never worked. All SAs would disappear and subsequent failover to slave dropped SAs there too. There was a story behind this from the developer somewhere in the mail archives. A while back. On Wednesday, December 13, 2023 at 05:55:50 p.m. GMT+9, Janne Johansson wrote: Den ons 13 dec. 2023 kl 04:15 skrev All : > > >I'd like to add sasyncd in the mix and a 2nd router for higher > availability. > Don't do it. sasyncd is known not to work properly in failover scenarios. > When I ran it it did work fine for the first fail-over, but seldom (or perhaps never?) on fail-back when the master returned, so it was ok for giving me nice redundancy if the current carp master died, then I could choose a suitable time after fixing this node when to take a the hit of a new tunnel-setup as I flipped back. Never knew why it would only work one-way for me, but we had certain issues with broadcom bnx(4) cards and multicast at the time, so it could have been related to that. > >Will gre over carp work? > I think you can just try out in a vm. Don't see the reason why it would > not. > But perhaps there are some features that CARP interface doesn't support > for gre. > Do mind that carp on software-defined switch networks might need some settings in order to allow the virtual eth cards to send out frames with "bogus" mac-addresses, since some hypervisors keep good track of which macs they have given to a VM and drop ethernet frames sent with not-those mac-addresses as source. But to add to the original reply, I would probably go for two gre's towards the non-carp ips, since you are using ospf anyhow, you might just tell ospfd that one gre has a slightly higher cost than the other, and let it deal with the new network map when one of them fails. -- May the most significant bit of your life be positive.
Firefox problem
Running OpenBSD -current. Trying to run Firefox results in: /home/oscar $ firefox XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0: File not found Couldn't load XPCOM. Any suggestions would be appreciated.
Re: Firefox problem
I have the same issue on 7.4 GENERIC.MP#1485 amd64. CCing ports and maintainer. On Wed, 13 Dec 2023 at 12:31, wrote: > Running OpenBSD -current. Trying to run Firefox results in: > > /home/oscar $ firefox > XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0: > File not found > Couldn't load XPCOM. > > Any suggestions would be appreciated. > >
Re: Firefox problem
On Wed, Dec 13, 2023 at 9:37 AM Gabriel Brito wrote: > > I have the same issue on 7.4 GENERIC.MP#1485 amd64. > > CCing ports and maintainer. > > On Wed, 13 Dec 2023 at 12:31, wrote: > > > Running OpenBSD -current. Trying to run Firefox results in: > > > > /home/oscar $ firefox > > XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0: > > File not found > > Couldn't load XPCOM. > > > > Any suggestions would be appreciated. > > > > There's already a thread on the issue. https://marc.info/?l=openbsd-ports&m=17022810948&w=2 Regards, - Claudio Miranda
Re: OBS-Studio 26.1.0 and later
So you were using OBS-Studio in the past but can't remember how you installed it? As has been shown by others there never was a package for 7.1. And then you blame the project for removing a package that was never there in the first place. Wow. And you're also totally confusing some OS support with a full implementation. On Mon, Dec 11, 2023 at 10:06 PM hammer2_zfs wrote: > Hi dears! > > I am scripts' kitty ;-) > I was using OBS-Studio 26.1.0 for Streaming by OpenBSD 7.1. > since 7.1 to now... > > recently, My USB device was gone... > then, I tried install by pkg_add obs-stuido on OpenBSD 7.4... > but, I couldn't get the OBS-Studio... > > I want to use the OBS-Studio... > Why, close the support for OBS-Studio... >
