#freebsd
These are public posts tagged with #freebsd. You can interact with them if you have an account anywhere in the fediverse.
Steve Wozniak was born OTD in 1950 https://cromwell-intl.com/networking/commands.html?s=mb #MacOS #Linux #FreeBSD
How to use TCP/IP configuration commands on Linux/UNIX,…
Bob's Pages of Travel, Linux, Cybersecurity, and More
@BastilleBSD@fosstodon.orgWorking on BastilleBSD taught me this:
Small, improved steps over time build something unshakable.
In systems and in life.
@adulau @wendynather Probably worth pointing out that Citrix NetScaler is #FreeBSD under the bonnet...
Alrighty, since Ohio illegally passed photo ID laws for "adult" content and no one cares, connectivity in Ohio is about to suck.
I'm building a workaround with a VPN provider, Foxy Proxy, and a SOCKS5 proxy.
Question for my #FreeBSD friends, what do we like for a SOCKS5 server these days?
net/microsocks is the first search result that hasn't been deleted, should I start there?
@Larvitz@burningboard.netThinkPad T480 on FreeBSD 14.3:
- iGPU (Intel): Working!
- dGPU (Nvidia): Working!
- WebCam (integrated): Working!
- Thunderbolt 4 Dock (external Display and USB): Working!
- Intel AX210 5GhZ WiFi: Working!
- External USB headsets: Working!
- Hardware Video-Decoding (vaapi): Working!
That is a perfectly usable setup and the Laptop is just about perfect to a BSD based desktop!
@Larvitz@burningboard.netFreeBSD 14.3 
on ThinkPad T480 with Thunderbolt docked external display and native iwlwifi 5Ghz Wifi with proper speeds. Running KDE Plasma 6.4 with X11 
Amazing, how far we have come in 2025 for a proper FreeBSD desktop experience!! 
@david_chisnall Had a look through the Wine 10.12 source code and there is still quite a few references to the /proc file system. The Wine packages should mention this in the post install message for #FreeBSD
[Again for those on the other side of the pond] -
Friends, it finally happened. On August 7th, 2025, the number of spamtraps rolled past the number of people in my home country. It's time for a retrospective.
Eighteen Years of Greytrapping - Is the Weirdness Finally Paying Off? https://nxdomain.no/~peter/eighteen_years_of_greytrapping.html (tracked https://bsdly.blogspot.com/2025/08/eighteen-years-of-greytrapping-is.html)
#greytrapping #spam #antispam #greylisting #blocklist #openbsd #freebsd #smtp #email #ssh #passwords #passwordguessing #pop3 #security #networking #cybercrime
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟬𝟴/𝟭𝟭 (Valuable News - 2025/08/11) available.
https://vermaden.wordpress.com/2025/08/11/valuable-news-2025-08-11/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟬𝟴/𝟭𝟭 (Valuable News - 2025/08/11) available.
https://vermaden.wordpress.com/2025/08/11/valuable-news-2025-08-11/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
A guide worth his baksheesh can lead you to any tavern you care to name, or to any temple you dare to visit. #Samba #FreeBSD #OpenSource https://cromwell-intl.com/open-source/samba-active-directory/dns.html?s=mc
How to set up the DNS infrastructure with BIND to support…
Bob's Pages of Travel, Linux, Cybersecurity, and More @BastilleBSD@fosstodon.orgYour projects will wait.
Your health won’t.
Close the terminal.
Take a walk.
Sometimes the best commit is a break.
Friends, it finally happened. On August 7th, 2025, the number of spamtraps intended to woo the unwary spammer rolled past the number of inhabitants in my home country of Norway. It's time for a retrospective.
Eighteen Years of Greytrapping - Is the Weirdness Finally Paying Off? https://nxdomain.no/~peter/eighteen_years_of_greytrapping.html (tracked https://bsdly.blogspot.com/2025/08/eighteen-years-of-greytrapping-is.html)
#greytrapping #spam #antispam #greylisting #blocklist #openbsd #freebsd #smtp #email #ssh #passwords #passwordguessing #pop3 #security #networking #cybercrime
FreeBSD provides the standard KDE Plasma package, which is the preferred way as recommended by KDE themselves. Nevertheless, you can still uninstall i.e. Discover and Konqueror, which are part of that base package (like I do).
Don't be put off by the inclusion of kde-base-apps in your removal overview, only the relevant parts for that application will be removed. All other apps and libraries will stay put and continue to work.
#freebsd #kde
'Tis a treasure-heap of powerful weapons. #Linux #FreeBSD #OpenSource https://cromwell-intl.com/open-source/?s=mc
Learn how to administer powerful Linux and BSD servers…
Bob's Pages of Travel, Linux, Cybersecurity, and MoreMost of the time you can, but sometimes there're userland/kernel abi changes which means that after you install the new userland binaries, they might not be able to talk with the currently running kernel and then you won't be able to reboot.
With zfs + be, you should be able to do the update in one go since you can clone the current system, mount it, install to it, and then reboot into the new BE.
Previously mentioned the write-up capabilities of the FreeBSD community. Over the last months I've taken hints and tips from this page. Thanks a lot Wison !
https://github.com/wisonye/freebsd-handbook?tab=readme-ov-file
#freebsd
My personal FreeBSD handbook. Contribute to wisonye/freebsd-handbook…
GitHubI think I've gotten further with this #FreeBSD #wine issue, knowledge-wise. The program I run for it does some live patching in memory (basically reads in a .dll and binary patches it in memory)
This all runs just fine in #Linux but fails in FreeBSD.
The system call I could find for it in WINE debugging was: KERNEL32.ReadProcessMemory
I also get this dreaded message:
wineserver: file_set_error() can't map error: Cannot allocate memory
This is FreeBSD 14.3, wine-devel 10.12.
Have tried disabling ASLR, enabling W^X (which I know is bad), have tried both 64-bit and 32-bit (WINEARCH=win32) prefixes. Same problem happens.
Is FreeBSD preventing WINE programs from reading each others' memory? I don't even know if it even got to the write part, it couldn't read it at all.
Please boost far and wide and many thanks in advance to anyone in the FreeBSD gaming community who might know the answer here (or a friendly FreeBSD dev?)
