#bsd

153 posts · Last used 13h

Replying to
@MsDropbear42@infosec.space Maybe go ahead with #GhostBSD as the "gateway drug" :blobcatamused: into the BSD world. Then when you've "found your BSD feet" with it, hopefully easier to try plain #NetBSD or #OpenBSD. I think that's what I might do. I used friendly PC-BSD back in the 00s but no BSD experience since. (Switching not urgent yet as I'm on Linux Mint Xfce X11, based on a 2024 LTS release, so presumably much less likely to contain slop than a cutting edge release.) #FreeBSD #BSD #NoAI
7
1
3
0
Most of the highly-publicized security vulnerabilities in #Linux these days, including the recent kernel TCP RCE, are the result of races and/or memory corruption. If #BSD were to catch on, all those AI bug-finding bots would be turned on the BSDs…which are written in C. There's probably plenty of vulnerabilities there too. Perhaps fewer than Linux, since Linux is so jam-packed with enterprise features and weird optimizations, but still… 😬 Are #NetBSD and #OpenBSD prepared for this?
10
1
4
0
Replying to
@djl@infosec.exchange so did i... from dec 2013 to aug 2026. now, i feel far less in love with my precious penguins, since they have increasingly thrown themselves over to the scourge of slopbottery. it seems #BSD might be the only safe refuge now... 🥺🤞 #DropbearPooterising #Linux #LinuxWomen #FOSS#FuckGenerativeAI #FuckSlopbots #AntiAI #NoAI #NoSlopJockeys #EscapeFromLinux :kde: :linux: #KDELinux | :archlinux: :kde: :plasma: #ArchLinux #KDEPlasma :opensuse: #Kalpa | :debian: #SparkyLinux | :fedora: #Kinoite
2
4
0
0
Replying to
On the plane, #ThinkPads shed their layer of finger-cheese and inventory tags. They drift to a good home, then take root and undergo a remarkable transformation. As polyps they break into an array of genders, most in the categories of #Linux or #BSD. The polyp phase can last for many years, and usually only terminates as a new polyp is established in the home. At this point they enter the Ephyra stage, rapidly cycling through operating systems, drifting and developing a layer of dust. 2/3
11
3
4
0
Replying to
@Tutanota@mastodon.social ad block; with zero click spyware being deployed via ad delivery, adblock is now mandatory. #nextdns + #adguardhome + @LibreWolf@mastodon.social with @ublockorigin@Reticulum@mastodon.social and @VeilidNetwork@masto.hackers.town is the future of the privacy, check out @veilamp@masto.hackers.town to see what's possible Use #foss OS #linux #bsd and @GrapheneOS@grapheneos.social because you CAN'T trust companies(even Apple for the Stockholm set) to choose your privacy and security over shareholder value. Security and privacy need to be transparently built into the OS
1
0
0
0

The day after the European *BSD event of the year! 😈⛳🐡

We would like to thank all the attendees who made time to visit the event in Brussels 🇧🇪. Great to read so many great comments here... much :flan_heart:​

One more time a A BIG UP to OC for taking care of us these days. :flan_heart:​

If you missed a talk or couldn't attend at all, all the videos are online! https://exquisite.tube/c/ebc2026/videos

#EuroBSDCon #EuroBSDCon2026 #EuroBSDCon2027 #BSD #RUNBSD #FreeBSD #NetBSD #OpenBSD

0
2
0
0
With the help from some great folks here in the Fediverse, I was finally able to get @netbsd@mastodon.sdf.org installed on both my desktop (Dell Optiplex) and laptop (Lenovo ThinkPad T14). I'm posting this from the desktop! Still unable to to get wireless working on the laptop but I am sure a USB wireless adapter will resolve this. I'm going to give this a try later today. My move away from my beloved Linux is moving forward. Thank you to Torvalds and other projects who have ruined it for me after 30+ years. It's sad that I'm moving away, but I know it's the right decision (for me, anyway). Updates coming, and will probably bore you to death. #bsd #netbsd #noAI
49
6
17
0
Hey #NetBSD guys, How do you set up #WireGuard? wg-quick isn't available for NetBSD from what I can tell. I got wireguard-go to create the tun0 interface, but when I try to feed the config file to it, I get a parsing error: rld@discovery:~$ doas wg setconf tun0 /etc/wireguard/protonvpn.conf Line unrecognized: `Address=10.~~~.~~~.~~~/32,2a07:~~~~::2:2/128' Configuration parsing error rld@discovery:~$ (~~~=redacted) #BSD #RunBSD
0
6
1
0
My old ThinkPad T480 is back in daily use, running FreeBSD 15.1. :freebsd: Xfce, 5 GHz Wi-Fi, hardware video decoding in Firefox and Chromium (checked in the decoder, not just a capabilities page), a webcam that survived a 45-minute Zoom call, a Bluetooth speaker via virtual_oss, and SSH and Git signing from a smart card. It's boring now. That's the point. https://blog.hofstede.it/the-t480-is-back-my-freebsd-151-laptop-from-boot-to-browser/ #FreeBSD #ThinkPad #T480 #BSD #Xfce
21
2
20
0

I have a problem installing Netbsd on a #DELL #dell_latitude 3510 laptop.

The sound, wifi and graphics chipsets are based on an Intel Comet Lake:

  • sound : Intel #CometLake PCH-LP cAVS
  • wifi : Intel Comet Lake PCH-LP CNVi WiFi
  • Graoic: Intel CometLake-U GT2 [UHD Graphics]

Sound and wifi do not work at all.

The graphics card works well in shell, but the X server is breaking cables, and it's frying, lag, anyway.

Does anyone have an idea for debugging the computer?

New on BSD, here I feel lost in space :) Thank you!

#BSD #netbsd

0
2
2
0