Why FreeBSD remains our OS of choice after 25 years in online gaming 🎮
Stability, scalability, and simplicity make FreeBSD the perfect fit for handling 100k queries/sec. ZFS integration is a game-changer for data management. Read why FreeBSD is E-Card's OS of choice: https://buff.ly/4i5lQOT #FreeBSD#OpenSource#TechInfrastructure
In our discussion of IPC, we noticed that each form must use some sort of buffer. But what is the actual size of those buffers? Is it the same across #NetBSD, #Linux, #FreeBSD and other Unix versions?
Creating a #freebsd#openbsd "security/tor" gateway in the cloud, so I can connect with all my Browsers/Apps/Services (Desktop & Mobile) from everywhere and route my traffic through it?
And to pump it up, I also would install a #headscale server, so I could tunnel my traffic to the VPS via Tailscale privately.
Netflix's FreeBSD Servers and Their Impact on Open Source
Netflix, one of the world's leading video streaming services, is renowned for its robust and efficient infrastructure that powers billions of hours of content streaming globally. At the core of this infrastructure lies FreeBSD, a free and open-source operating system.
Anyone tips to reduce the CPU and memory usage of #BHyve instances?
Looking at my #freebsd box running 10 jails, these 2 at the top consume more then all 10 jails together
I can reduce the assigned CPU and memory, but anything else would help. The 2 Linux VMs are needed due to their invasive installs. Maye #Podman can come to the rescue?
「The Laptop and Desktop Workgroup (LDWG) is a platform for the community to collaborate on development, testing, knowledge exchange, and advocacy for FreeBSD on laptops and desktops. Our mission is to advocate, support, and improve the use of FreeBSD on laptops and desktops for both business and personal users. …」
ok but in all seriousness, let's say I want to send some SMS/RCS using my cell, but I want to do that from the computer... should be feasible?
iPhone's iMessage: "we love our walled garden so much that NO ONE can send messages using a web interface, despite iMessage being an iCloud enabled app and the ecosystem having iCloud apps available online to any non-Mac -- but we decided that iMessage alone should never be usable on the iCloud web interface (because reasons?)"
Android via Messages App: "sure thing fellow Happy Camper! here you go! https://messages.google.com and it's just as secure as using the device itself."
Blocky is a DNS proxy and ad-blocker for the local network written in Go with following features:
Features
Blocking - Blocking of DNS queries with external lists (Ad-block, malware) and allowlisting
Definition of allow/denylists per client group (Kids, Smart home devices, etc.) Periodical reload of external allow/denylists Regex support Blocking of request domain, response CNAME (deep CNAME inspection) and response IP addresses (against IP lists) Advanced DNS configuration - not just an ad-blocker
Custom DNS resolution for certain domain names Conditional forwarding to external DNS server Upstream resolvers can be defined per client group Performance - Improves speed and performance in your network
Customizable caching of DNS answers for queries -> improves DNS resolution speed and reduces amount of external DNS queries Prefetching and caching of often used queries Using multiple external resolver simultaneously Low memory footprint Various Protocols - Supports modern DNS protocols
DNS over UDP and TCP DNS over HTTPS (aka DoH) DNS over TLS (aka DoT) Security and Privacy - Secure communication
Supports modern DNS extensions: DNSSEC, eDNS, ... Free configurable blocking lists - no hidden filtering etc. Provides DoH Endpoint Uses random upstream resolvers from the configuration - increases your privacy through the distribution of your DNS traffic over multiple provider Blocky does NOT collect any user data, telemetry, statistics etc. Integration - various integration
Prometheus metrics Prepared Grafana dashboards (Prometheus and database) Logging of DNS queries per day / per client in CSV format or MySQL/MariaDB/PostgreSQL/Timescale database - easy to analyze Various REST API endpoints CLI tool Simple configuration - single or multiple configuration files in YAML format
Simple to maintain Simple to backup Simple installation/configuration - blocky was designed for simple installation
Stateless (no database, no temporary files) Docker image with Multi-arch support Single binary Supports x86-64 and ARM architectures -> runs fine on Raspberry PI Community supported Helm chart for k8s deployment
Real-time monitoring of CPU, memory, disks, network & processes #GPU support for #NVIDIA#AMD#Intel graphics Interactive UI with full mouse support and customizable themes Tree view of processes with detailed statistics
⚡ Technical Highlights:
Efficient performance with minimal system impact Support for true color and 256-color terminals Extensive configuration options via btop.conf Available through #homebrew#pkg#snap package managers
🛠️ Installation Options:
Binary releases for multiple architectures Source compilation with Make or CMake Simple package manager installation on major distributions
Since moving to #FreeBSD I've noticed quite a few blocks and unfollows. I get the unfollows but blocks from folk that don't follow me and I don't follow them is strange. Anyway each to their own as they say.
So I'm looking to follow more #BSD family to get more BSD content on my feed so if that's you come say hi and tell me what and why you run said BSD.
Please boost for more reach and thanks in advance.
The original #BSD daemon was drawn by John Lasseter for Sam Leffler's "Unix System Manager's Manual". (Lasseter & Leffler (previously at CSRG) worked at Lucasfilm, which sold the Graphics Group to Steve Jobs to become Pixar.)
He then drew the version used by McKusick's "The Design and Implementation of the 4.3BSD Operating System" (McKusick still holds the copyright for that daemon). It was used by #FreeBSD until 2005; #NetBSD used the Iwo Jima inspired daemons logo until 2004.