Elektrine
Log in Register

#freebsd

21 posts · Last used 2d

Back to Timeline
@deaduser@101010.pl · 2d ago
OPNSense zainstalowany, działa zadziwiająco przyjemnie. Odpaliłem #ntop i #suricata poza bazowymi usługami, obciążenie jak widać #opnsense #freebsd #softrouter
View on 101010.pl
0
0
0
@Larvitz@burningboard.net · Mar 09, 2026
Our Mastodon instance "burningboard.net" now internally **ONLY** uses the Internet Protocol in Version 6. I did successfully migrate away from any RFC1918 addresses in any of the internal infrastructure connections. Nginx -> Mastodon: IPv6 Mastodon -> PostgreSQL: IPv6 Mastodon -> Opensearch: IPv6 Mastodon -> Sidekiq: IPv6 Mastodon -> Loki: IPv6 Sidekiq -> PostgreSQL: IPv6 Prometheus -> Mastodon: IPv6 All using globally routed unique addresses and proper routing and packet filtering from "pf" (FreeBSD). Outbound connections to legacy hosts (for example for Federation) uses NAT64 over Tayga. Inbound the Nginx is the only component, that supports IPv4 on NAT on a best-effort approach. But I refuse to put a lot of work into this. We have 2026 and it's a dying, smelly protocol, that I don't even monitor anymore. If someone looks at the Firewall rules.. Yes, we do run a (private) Factorio Server on our Mastodon system :factorio: #mastodon #mastoadmin #ipv6 #networking #freebsd @tux@burningboard.net
View on burningboard.net
0
0
1
@Larvitz@burningboard.net · Mar 02, 2026
New series: FreeBSD Foundationals Part 1 is about Jails - specifically VNET Jails. What epair interfaces actually are (virtual ethernet cables), how bridges tie them together, why the host is basically a router for your jails, and what devfs rulesets control. Covers the full lifecycle from jail.conf through pf firewalling with NAT/RDR for IPv4 and direct routing for IPv6. Plus the gotchas that'll cost you hours if nobody warns you. Not a beginner tutorial, hardcore details. The useful middle. https://blog.hofstede.it/freebsd-foundationals-jails-from-chroot-on-steroids-to-full-virtual-networks/ #Unix #FreeBSD #Networking #Jails #DevOps #SelfHosting #Sysadmin
View on burningboard.net
18
0
13
Thread context 2 posts in path
Parent @reallyflygreg@mstdn.ca Open
on mstdn.ca
Open ancestor post
Current reply
@JdeBP@mastodonapp.uk · Mar 02, 2026
@reallyflygreg@mstdn.ca @toddalio@mstdn.ca I'm inclined to believe that it is indeed the people who don't understand technology (specifically: they think that everything works like their smart 'phone or Microsoft Windows 11 PC do) making policy; or that they did understand the technology and were just crap at drafting legislation such that it could distinguish the Microsoft Store, Google Play, the Apple App Store, et al. from #Ubuntu's package repository and #OpenBSD's ports tree. And that distinguishing criterion is not #FreeSoftware. Given the aims, the #California legislators would want #FDroid to be required to hand over #AgeVerification data to free-software apps that F-Droid allows, that themselves want to impose age restrictions (on, say, showing certain content to minors) via the route of getting the account holder's age (bracket) information from the operating system via a 'signal' from the 'store'. https://monitor.f-droid.org/anti-features #FreeBSD #NetBSD #Debian #CaliforniaLaw #USLaw
View full thread on mastodonapp.uk
0
0
0
@Larvitz@burningboard.net · Feb 26, 2026
I just published a new guide on evolving a single BGP router into a multi-homed, two-PoP network using FreeBSD, FRR, and PF. - Native peering on Vultr + 3 GRE transits - Tying it together with iBGP - Why stateful firewalls break asymmetric transit (and how to fix it) All for ~€18/mo. Read it here: https://blog.hofstede.it/running-your-own-as-going-multi-homed-with-ibgp-and-three-transits/ #FreeBSD #BGP #IPv6 #Networking #Sysadmin #FRR #Homelab
View on burningboard.net
0
0
0
@kuk@podcasts.social · Feb 22, 2026
We can say that it was a great pleasure to meet Emmanuele ( @ebassi@mastodon.social ), a developer behind the GNOME project. Last year, we had the opportunity to meet the developer of Niri, a very personal project that it managed by himself. This episode is about a very large project, GNOME. With Emmanuele's help, we gained insights into GNOME and learned how an open-source project with several hundred developers works. https://www.trommelspeicher.de/podcast/special-the-gnome-project #podcast #kuk #linux #gnome #freebsd
View on podcasts.social
12
0
8
@Larvitz@burningboard.net · Feb 21, 2026
Spent way too long getting HTTP/3 working on FreeBSD with nginx, so I wrote it all up. The highlights: stock OpenSSL silently breaks QUIC at the HTTP/3 framing layer (the TLS handshake succeeds, so openssl s_client lies to you). eBPF worker routing doesn't exist on FreeBSD. And if nginx is in a jail with IPv4 NAT, a pass rule for UDP 443 is useless without a matching rdr. New post: https://blog.hofstede.it/http3-on-freebsd-getting-quic-working-with-nginx-in-a-bastille-jail/ #FreeBSD #nginx #HTTP3 #QUIC #Networking
View on burningboard.net
25
0
16
Thread context 2 posts in path
Parent @cks@mastodon.social Open
on mastodon.social
Open ancestor post
Current reply
@JdeBP@mastodonapp.uk · Feb 12, 2026
@cks@mastodon.social OpenWatcom vi is source available. https://mastodonapp.uk/@JdeBP/116052015020764901 Ritter's Heirloom #vi is in #FreeBSD ports today, coming from the same place that it has for a long time. https://freshports.org/editors/2bsd-vi/ It was dropped from #ArchLinux because it did not compile and hadn't changed in 20 years. Ironically, this is because the (GNU) C language had changed, and it has to nowadays be compiled forcing an older GNU C language version. https://bbs.archlinux.org/viewtopic.php?pid=2285124#p2285124 Several people have independently discovered the Makefile patch that gets it to build on #Debian and the like. https://forums.debian.net/viewtopic.php?p=629775 https://gist.github.com/cwfoo/01abac5c39f398b7e7b16a2b87aa518b #elvis, the precursor to #nvi, is packaged for both #NetBSD/#pkgsrc and #OpenBSD. https://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/editors/elvis/index.html https://github.com/openbsd/ports/tree/master/editors/elvis #retrocomputing #ComputerHistory #Watcom #OpenWatcom
Quoting
JdeBP @JdeBP@mastodonapp.uk
On #Illumos, Jov vi is in /usr/src/cmd/vi: https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/vi On #OpenBSD, Bostic #nvi is in /usr/src/usr.bin/vi/vi; #NetBSD having it in /usr/src/external/bsd/nvi; and #FreeBSD in /usr/src/contrib/nvi: https://github.com/freebsd/freebsd-src/tree/main/contrib/nvi FreeBSD has an nvi2 in ports: https://freshports.org/editors/nvi2/ OpenBSD has elvis in ports: https://github.com/openbsd/ports/blob/master/editors/elvis/pkg/DESCR Ritter's Heirloom vi is on SourceForge: https://ex-vi.sourceforge.net STEVIE was posted to comp.sources.unix in 1988: https://sources.vsta.org/comp.sources.unix/volume15/stevie/ Unfortunately, Sven Guckes's vi Clones WWW site was never completed with some of this, notably lacking Heirloom vi, for example. https://guckes.net/vi/clones.html But it does mention oft-overlooked commercial clones such as Watcom's vi, a from-scratch implementation started in 1983 that is also now source-available: https://github.com/open-watcom/owp4v1copy/tree/master/bld/vi #vi #retrocomputing #ComputerHistory #STEVIE #elvis #VIM #NeoVIM #Watcom #OpenWatcom
View full thread on mastodonapp.uk
0
0
1
Thread context 2 posts in path
Parent @davefischer@hachyderm.io Open
on hachyderm.io
Open ancestor post
Current reply
@JdeBP@mastodonapp.uk · Feb 11, 2026
@davefischer@hachyderm.io I'm guessing that that was Ritter's Heirloom vi. https://mastodonapp.uk/@JdeBP/116052015020764901 There are discussions in an Arch Linux forum of its package being removed because it hadn't changed in two decades and the (GNU flavoured) C language had. It's in the #FreeBSD ports collection; and several people have independently come up with the Makefile patch that gets it to build on Debian Linux. https://freshports.org/editors/2bsd-vi/ #vi #retrocomputing #ComputerHistory #gcc #ArchLinux
Quoting
JdeBP @JdeBP@mastodonapp.uk
On #Illumos, Jov vi is in /usr/src/cmd/vi: https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/vi On #OpenBSD, Bostic #nvi is in /usr/src/usr.bin/vi/vi; #NetBSD having it in /usr/src/external/bsd/nvi; and #FreeBSD in /usr/src/contrib/nvi: https://github.com/freebsd/freebsd-src/tree/main/contrib/nvi FreeBSD has an nvi2 in ports: https://freshports.org/editors/nvi2/ OpenBSD has elvis in ports: https://github.com/openbsd/ports/blob/master/editors/elvis/pkg/DESCR Ritter's Heirloom vi is on SourceForge: https://ex-vi.sourceforge.net STEVIE was posted to comp.sources.unix in 1988: https://sources.vsta.org/comp.sources.unix/volume15/stevie/ Unfortunately, Sven Guckes's vi Clones WWW site was never completed with some of this, notably lacking Heirloom vi, for example. https://guckes.net/vi/clones.html But it does mention oft-overlooked commercial clones such as Watcom's vi, a from-scratch implementation started in 1983 that is also now source-available: https://github.com/open-watcom/owp4v1copy/tree/master/bld/vi #vi #retrocomputing #ComputerHistory #STEVIE #elvis #VIM #NeoVIM #Watcom #OpenWatcom
View full thread on mastodonapp.uk
0
0
0
Thread context 2 posts in path
Parent @JdeBP@mastodonapp.uk Open
@JdeBP@mastodonapp.uk
People waxing lyrical about using 'original vi', both nowadays in 2026 and back in 2006, haven't a clue what that is. There's only one family of operating systems where 'vi' will actually run the orig
Current reply
@JdeBP@mastodonapp.uk · Feb 11, 2026
On #Illumos, Jov vi is in /usr/src/cmd/vi: https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/vi On #OpenBSD, Bostic #nvi is in /usr/src/usr.bin/vi/vi; #NetBSD having it in /usr/src/external/bsd/nvi; and #FreeBSD in /usr/src/contrib/nvi: https://github.com/freebsd/freebsd-src/tree/main/contrib/nvi FreeBSD has an nvi2 in ports: https://freshports.org/editors/nvi2/ OpenBSD has elvis in ports: https://github.com/openbsd/ports/blob/master/editors/elvis/pkg/DESCR Ritter's Heirloom vi is on SourceForge: https://ex-vi.sourceforge.net STEVIE was posted to comp.sources.unix in 1988: https://sources.vsta.org/comp.sources.unix/volume15/stevie/ Unfortunately, Sven Guckes's vi Clones WWW site was never completed with some of this, notably lacking Heirloom vi, for example. https://guckes.net/vi/clones.html But it does mention oft-overlooked commercial clones such as Watcom's vi, a from-scratch implementation started in 1983 that is also now source-available: https://github.com/open-watcom/owp4v1copy/tree/master/bld/vi #vi #retrocomputing #ComputerHistory #STEVIE #elvis #VIM #NeoVIM #Watcom #OpenWatcom
View full thread on mastodonapp.uk
0
0
1
@JdeBP@mastodonapp.uk · Feb 11, 2026
People waxing lyrical about using 'original vi', both nowadays in 2026 and back in 2006, haven't a clue what that is. There's only one family of operating systems where 'vi' will actually run the original vi program by Joy, Horton, et al.: #Illumos and its derivatives #Tribblix, #OmniOS, and #SmartOS. *Everyone else* uses one of the ground-up clones. On #FreeBSD, #OpenBSD, and #NetBSD, it's Bostic's early 1990s #nvi, which was derived from Kirkendall's elvis, a clone written some time around 1990. On Linux-based operating systems, vi either is Bostic nvi, or is one of the derivatives of STEVIE (the middle-1980s vi clone for the Atari ST that inspired Kirkendall to write elvis in the first place): Moolenaar's VIM or NeoVIM. On none of those will you get original Joy+Horton vi in base, or indeed packaged/in ports. Yes, Heirloom vi exists, which is Ritter's 2002 fork of 1985 Joy+Horton vi. But it's not even available in Arch Linux nowadays. #vi #retrocomputing #ComputerHistory
View on mastodonapp.uk
0
1
0
@locaverdi@mstdn.business · Feb 06, 2026
We wrote a little how-to on running FreeBSD 15.0 on a Raspberry Pi 5 with a Raspberry Pi M.2 HAT+ and a 256GB Integral M.2 NVMe SSD. https://locaverdi.com/freebsdrpi5.html #freebsd #rpi5 #howto #locaverdi
View on mstdn.business
0
0
0
@Linuxiarze@fe.disroot.org · Feb 05, 2026
Własny serwer FreeBSD – cz.4: Certyfikat TSL/SSL. W kolejnej części cyklu Własny Serwer FreeBSD zainstalujemy certyfikat TSL/SSL. TLS (ang. Transport Layer Security) – przyjęte jako standard w Internecie rozwinięcie protokołu SSL (ang. Secure Socket Layer) https://linuxiarze.pl/wlasny-serwer-freebsd-cz-4-certyfikat-tsl-ssl/ #bsd #freebsd #server #ssl
View on fe.disroot.org
0
0
0
@xhr@infosec.exchange · Jan 31, 2026
I wrote a small article on how to backup Unix servers using tar and age. Nothing fancy, just the script and concept I use for all my servers. https://xosc.org/backup-server.html #openbsd #freebsd #netbsd #linux
View on infosec.exchange
7
0
4
@bobthetraveler@mastodon.world · Jan 31, 2026
Guido van Rossum, born OTD in 1956, created the #Python programming language https://cromwell-intl.com/open-source/python-social-media-automation/python-program.html?s=mb #FreeBSD #Linux #OpenSource
View on mastodon.world
0
0
1
@bobthetraveler@mastodon.world · Jan 31, 2026
Guido van Rossum, born OTD in 1956, created the #Python programming language https://cromwell-intl.com/open-source/python-social-media-automation/mastodon-twitter-app.html?s=mb #FreeBSD #Linux #OpenSource
View on mastodon.world
0
0
1
@bobthetraveler@mastodon.world · Jan 31, 2026
Guido van Rossum, born OTD in 1956, created the #Python programming language https://cromwell-intl.com/open-source/python-social-media-automation/?s=mb #FreeBSD #Linux #OpenSource
View on mastodon.world
0
0
1
Thread context 2 posts in path
Parent @Larvitz@burningboard.net Open
on burningboard.net
Open ancestor post
Current reply
@tux@burningboard.net · Jan 31, 2026
@Larvitz@burningboard.net Thanks for that! What does “p2” actually mean exactly? Best regards #freebsd
View full thread on burningboard.net
0
4
1
@JdeBP@mastodonapp.uk · Jan 29, 2026
@pu@ieji.de That's difficult to answer without a concrete idea of what a dependency is. If it's who develops it, then #GhostBSD's major developers are in Canada, and #MirBSD's major developers are in the E.U./Switzerland. If it's which BSDs would be unaffected if Microsoft-owned GitHub decided to pull the rug out from underneath them, then the answer is rather different. Financial dependencies, and WWW/mail/other hosting dependencies, are different again. #FreeBSD #OpenBSD #MidnightBSD #DragonFlyBSD #NetBSD
View on mastodonapp.uk
0
0
0
@alfonsosiciliano@mastodon.bsd.cafe · Jan 28, 2026
@pixelate@tweesecake.social Hi, thank you for your feedback on accessibility and open source technologies. I always read your posts with great interest in order to improve the accessibility of FreeBSD, a UNIX and open source operating system. At the FreeBSD Developer Summit in Dublin 2024, I showed other developers (using simulators) the challenges faced by color-blind, low-vision, and blind users. The @FreeBSDFoundation@mastodon.social is currently sponsoring the "Vision Accessibility" project to improve accessibility for users with visual impairments. At the Developer Summit in Zagreb 2025, I presented the new accessibility handbook https://docs.freebsd.org/en/books/accessibility/ focused on the assistive technologies currently available in the system, including practical examples to help developers better understand these challenges. I am in contact with organizations supporting people with low vision, blindness, and deafblindness to implement Braille display subsystem for FreeBSD and to develop interfaces specifically designed to be used with screen readers. Any feedback or suggestions are very welcome. #accessibility #FreeBSD #UNIX #openSource
View on mastodon.bsd.cafe
3
0
3