gyptazy.ch is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟰/𝟬𝟰/𝟮𝟵 (Valuable News - 2024/04/29) available.
https://vermaden.wordpress.com/2024/04/29/valuable-news-2024-04-29/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟰/𝟬𝟰/𝟮𝟵 (Valuable News - 2024/04/29) available.
https://vermaden.wordpress.com/2024/04/29/valuable-news-2024-04-29/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
There's a KVirc (https://www.kvirc.net/) update approaching for #FreeBSD ports, and more and more we're getting "do we update this for Qt6 or not?" I think there's going to be a sea change to Qt6-based things "soon".
(for me personally, that would require VirtualBox to go to Qt6 as well, although I'm not afraid of having multiple UI toolkits installed)
@david_chisnall yep, it's kinda ridiculous, and don't get me started about FreeBSD having kTLS vs (linux's marginal improvements on top of self-congratulatory marginal performance)
oh, but 'Linus dictatorman', please do tell us all about the superiority of kernel features that struggle with NUMA balancing and management, or the convoluted nature of SR-IOV integration or... let's just say the list is extensive...
@winterschon @david_chisnall preach on about SR-IOV in #FreeBSD !! :)
Help needed.
I set up #wireguard on #FreeBSD according to @stefano's excellent journal entry at https://freebsdfoundation.org/our-work/journal/browser-based-edition/make-your-own-vpn-freebsd-wireguard-ipv6-and-ad-blocking-included/
While the wireguard connection between my clients (Android and Windows) is established, it is unusable slow. See screenshot.
Speedtest shows latency between 2 and 21 seconds. The server is hosted at @netcup, and both the connection there and my client's connection is of course much faster.
I tinkered with MTU on both server and client but no luck, either.
Totally missed that this #openzfs issue was fixed 🤦♂️
Will test again jailed #samba shadow copies.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
I started a simple project called checkrc that validates the /etc/rc.conf file on #FreeBSD. I'm still a beginner in C programming, but I'm giving it a shot with something usful:
https://github.com/scovl/checkrc
The project is still a work in progress, right at the beginning, so don't expect too much yet. But I'll be working on it every day. One day I'll be great!
I'm one of these mad guys refusing to pull some "modern" buildsystem (like cmake or meson) into my projects, yet also dislike the complexity and overhead of autotools ... so I created my own "buildsystem" many many years ago, which is basically a #gmake (#GNU #make) framework using "eval" to generate rules on the fly.
Over the years, I piled up features in there as I needed them for current projects. The result is (although it still "worked") chaos. 🙈 More and more, I'm having trouble understanding my own code, and changing things is almost guaranteed to also break things. 🙄
I now decided to refactor a lot, giving some structure to that mess, and took inspiration from #FreeBSD's #ports framework by introducing a "USES" concept to load optional parts. So far, this seems to turn out well, it also gives the opportunity to better document that stuff given the clear responsibility of each USES, see e.g. the one handling installation of freedesktop.org stuff:
https://github.com/Zirias/zimk/blob/master/lib/uses/fdofiles.mk
🚀 Netflix Case Study – FreeBSD Foundation
「 “We decided what we were doing was silly, and what we should do is track FreeBSD-CURRENT. It sounds crazy because that’s where everybody pushes all their stuff, but it’s actually the best thing in the world for us.” 」
@mms hi. From a recent article:
「… since we are not using GNU/Linux, all hacks that make software run fast there may now work here, or even create huge problems. Firefox on FreeBSD is a hack layered over a hack running slowly. …」
Focusing on the web browser: please, can you elaborate?
My own use of www/firefox is a mixture of:
— wildly excessive (e.g. the screenshot of Firefox at <https://forums.freebsd.org/posts/653046>)
— necessarily simplistic, with regard to AV content (over the years, I learnt to not punish myself by attempting to untangle the mysteries of audio/Bluetooth/USB).
I wanted the basic ability to sleep/suspend a laptop without ungracefully forcing off the power; without having to think about channels, switching and so on. Note that these audio-related frustrations were not limited to Firefox, and were largely avoidable by disabling PulseAudio.
Things now are VERY different. My comments about audio-related enhancements have been happily scattered and intentionally vague. For now, in a nutshell: "the greatest improvement since I began using PC-BSD maybe eight years ago.".
cc @lproven
I should spend some time this afternoon getting used to #FreeBSD. My Gen8 Microserver has been sitting on the floor next to my desk for almost a month now, case off, waiting to be migrated from the Arch installation that has served me surprisingly well (because Arch is not known for its suitability as a server distro) for almost a decade.
#DuckDuckFedi and #FreeBSD bubble :
I'm having trouble with horizontal scrolling using a #ThinkPad #TrackPoint of the Lenovo external USB keyboards. I didn't find any docs or drivers related to this but also didn't dig very deep into it. Does anyone know how to get the track point's horizontal scrolling in a graphical environment (wlroots + Firefox is my issue) to work ?
For the first time, I'm seeing people, who are anxious, asking me for fifth article about #FreeBSD for #developers. And I've been writing articles for a long time, usually ini my native language. That's interesting!
This account has been a little quiet lately, but there's been work going on in the background.
I hope to share more details soon. Watch for an announcement in the coming weeks.
Happy Friday #FreeBSD
https://underjordab.cmail19.com/t/t-e-eitkye-jdiddyjim-c/
I want an easy path like this onto #freebsd development.
Any interest @dch
@garyhtech @laffer1 success!
startx
– without attempting to use a display manager (although I will install Firefox, and reinstall XDM, to maybe learn a little more).
A prior experiment with EFI enabled in VirtualBox – not a default, for FreeBSD guests – failed. No surprise there.
The pictured search for scfb was pure imagination.
I've just landed a patch adding %N (i.e., a nanosecond conversion specification) to #date(1) on #FreeBSD.
Now you can run "date +%N" or "date -Ins" and enjoy the nanosecond precision of your dates.
https://cgit.freebsd.org/src/commit/?id=eeb04a736cb9c07d191af886e25d5f198824658e
Using #freebsd 13 with #zfs Take a look at the errata notice:
https://www.freebsd.org/security/advisories/FreeBSD-EN-24:09.zfs.asc
What is FreeBSD Missing?
https://www.youtube.com/watch?v=ISJrVuajlAw
Discussions: https://discu.eu/q/https://www.youtube.com/watch?v=ISJrVuajlAw
@mms https://github.com/charliemaiors/freebsd-ansible -- there are a few plays with tasks related to automatically updating bare metal and #jails. Haven't tested these yet, but they look promising. This kind of infrastructure management is necessary for managing #FreeBSD at scale. #Puppet and salt stack might be good alternatives if you don't #Ansible. See also : https://docs.ansible.com/ansible/latest/os_guide/intro_bsd.html
We had nice talks about improving #BoxyBSD, getting new users attracted into #BSD based systems like #FreeBSD, #OpenBSD, #NetBSD but also covering the lacks of it. Outcome was, that a one already worked on that which might result in a new community project (which may also result into a new service). I don’t want to teaser too much, the related persons will provide more details and insights. It was a great first meeting, looking forward into the next upcoming ones!
More details and participating informations at: https://wiki.bsd.cafe/docs:weekly-bsdpub
For my #ThrowbackThursday, here's a snapshot of my desk from 2013. Although my workspace was pretty cluttered then and still is, despite being in a different house now. Under the table, there was a tower PCs, running #FreeBSD. The laptop that was on was using #MacOS, while the mini ITX desktop was powered by #NetBSD with #Xen, hosting various services in some domUs. My smartphone at the time was a QWERTY-equipped Samsung #Android, which I had chosen in the hopes of finding a keyboard experience similar to the superb one offered by #BlackBerry. Additionally, there was another laptop beneath the phones operating on #OpenBSD. The Dockstar, running NetBSD, served as my file server; it even had remote access, albeit with a modest broadband speed of just 1.5 Mbit/sec.
Ah, the good old days. 🙂
Just wrapped up the first virtual meeting of 'BSD Pub,' hosted by @gyptazy
Had a delightful and friendly conversation with wonderful folks, and some really interesting ideas emerged for the future. Thanks to everyone and... looking forward to the next meeting!
Details will be posted on the corresponding page: https://wiki.bsd.cafe/docs:weekly-bsdpub
#BSDPub #BSD #BSDCafe #OpenSource #Community #FreeBSD #OpenBSD #NetBSD #DragonFlyBSD #RunBSD
@cuddle :)
I am not switching to Docker even if it is faster with disk I/O. I would rather learn how to properly speed up ZFS itself. SAS SSDs ( which ones )? NVMEs ( which ones )? Tons of RAM ( how much is a ton )? It looks more adequate to invest in hardware and be on par with Linux/Docker than switching to Linux/Docker in the first place.
Back to the point: I would like to find out what #freebsd community thinks about the said research.
best regards,
Dmitry
good morning, nice #freebsd community.
I have just come across the Valuable News – 2024/04/22 issue by @vermaden. Specifically this article ( Jails vs Docker ): https://www.diva-portal.org/smash/get/diva2:1453017/FULLTEXT01.pdf.
The conclusions the authors of the PDF present are quite concerning.
I would like to know your thoughts on this.
best regards,
Dmitry
Has anyone successfully mounted on #macOS #NFS or #Samba shares hosted on a #FreeBSD server?
If I use NFSv3, then all my shares are full of #AppleDouble files (i.e., with the "._" prefix).
If I use #NFSv4, then "git fetch" just hangs forever and never finishes.
If I use #Samba, then either 1) everything is 755 but I cannot delete files xD or 2) (after applying https://askubuntu.com/a/1126633/413683) the permissions are correct, but something is wrong with my .git: ad_convert: Failed to convert [.git].
:(
So, I am a stickler for a serial console on Unix systems because, quite frankly, it is the most reliable way to get into remote systems - even in an era of VOIP you can get a usable 9600 baud connection into a modem the other side of the planet and even at 2400 you can "do things"…
Well, I haven't been able to get any of the serial ports on Supermicro X12 motherboards to work, not even a peep.
They are happily detected by, say, #OpenBSD
com0 at acpi0 UAR1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo
com1 at acpi0 UAR2 addr 0x2f8/0x8 irq 3: ns16550a, 16 byte fifo
but then the getty on the serial port shows nothing into the cable. Not only, if you connect the Supermicro to a Tripplite which has a serial line diagnostic, it shows that there is no activity
same with #FreeBSD and, because someone always says "use Linux", well, it doesn't work either!
I scoured the manuals for the motherboards and cannot find anything, according to the BIOS the serial ports are enabled, the cables are correct but… not a peep. This over several motherboards, not just one!
Am I the only lucky person failing to get a serial port to work on Supermicro X12 mobos?
@BoxyBSD@bsd.cafe #hosting #opensource #BSD #freevm #education
NEW VIDEO! - MidnightBSD - My First Impressions!
#FreeBSD #MidnightBSD #Unix #opensource #garyhtech
https://youtu.be/O0G5slB0WoU?si=nMKgyn-nelxT3KEd via @YouTube
Added 𝗨𝗣𝗗𝗔𝗧𝗘 𝟯 - 𝗔𝗻𝘀𝗶𝗯𝗹𝗲 𝗟𝗮𝗻𝗴𝘂𝗮𝗴𝗲 𝗦𝗲𝗿𝘃𝗲𝗿 𝗳𝗿𝗼𝗺 𝗻𝗽𝗺(𝟭) 𝗣𝗮𝗰𝗸𝗮𝗴𝗲𝘀 (UPDATE 3 - Ansible Language Server from npm(1) Packages) to the 𝗣𝗲𝗿𝗳𝗲𝗰𝘁 𝗡𝗲𝗼𝘃𝗶𝗺 𝗔𝗻𝘀𝗶𝗯𝗹𝗲 𝗦𝗲𝘁𝘂𝗽 (Perfect Neovim Ansible Setup) article.
https://vermaden.wordpress.com/2024/03/13/perfect-neovim-ansible-setup/
Added 𝗨𝗣𝗗𝗔𝗧𝗘 𝟯 - 𝗔𝗻𝘀𝗶𝗯𝗹𝗲 𝗟𝗮𝗻𝗴𝘂𝗮𝗴𝗲 𝗦𝗲𝗿𝘃𝗲𝗿 𝗳𝗿𝗼𝗺 𝗻𝗽𝗺(𝟭) 𝗣𝗮𝗰𝗸𝗮𝗴𝗲𝘀 (UPDATE 3 - Ansible Language Server from npm(1) Packages) to the 𝗣𝗲𝗿𝗳𝗲𝗰𝘁 𝗡𝗲𝗼𝘃𝗶𝗺 𝗔𝗻𝘀𝗶𝗯𝗹𝗲 𝗦𝗲𝘁𝘂𝗽 (Perfect Neovim Ansible Setup) article.
https://vermaden.wordpress.com/2024/03/13/perfect-neovim-ansible-setup/
Interesting #FreeBSD patch: implement DTrace SDT probes using hot-patching
👉 #FreeBSD uses less memory.
For more than 25 years, Beckhoff Automation has used Windows as the exclusive operating system for its products. By adopting FreeBSD, they decreased their operating system footprint over sevenfold. Beckhoff came for FreeBSD’s permissive license and stayed for its smaller footprint.
Read the case study here:
https://freebsdfoundation.org/freebsd-case-studies/beckhoff-case-study/
Weekly BSD Pub
*BSD friends, just remember that on Thursday there'll be the first Weekly BSD Pub virtual meeting, organized by @gyptazy
More information here: https://wiki.bsd.cafe/docs:weekly-bsdpub
From my travels:
...the question arises if the classic, basic #fuzz technique is still useful and applicable... we found that 9 crash or hang out of 74 utilities on #Linux, 15 out of 78 utilities on #FreeBSD, and 12 out of 76 utilities on #MacOS... failure rates are somewhat higher than our in previous 1995, 2000, and 2006 studies of the reliability of command line utilities...
Hey everyone, I'm studying #C and planning to contribute to some open-source projects soon. I have a question: in #FreeBSD, do you usually use #gmake, #bmake, or #cmake more frequently? (I'm a beginner, but I got the impression that cmake is the most comprehensive). Is there one that's more universal and can be used across all projects, or does it depend on the project? And for #Emacs, which one helps more with configuration?
Since #Chromium is still missing in the binary ports for #FreeBSD 14.0R, I'm setting up #Firefox for the time being with all of the tabs I need for work and then some. Normally, Firefox is what I default to, but for work purposes, I need to use Chromium, especially because of Microsoft 365. Hoping whatever is holding back Chromium's re-inclusion to the binary ports database is resolved soon.
My current #freebsd hw probe https://bsd-hardware.info/?probe=7ae4c9320c
@FiLiS Whenever I can, I update #FreeBSD manually by creating a new BE first, and then using that as the installation target for kernel, base (world) and packages. That's perfectly safe (not touching the currently running system at all) and requires just a single reboot when everything goes fine.
It might be a bit underdocumented though, IIRC the handbook only describes upgrading the live system (still safe when creating a BE beforehand of course)
@FiLiS Whenever I can, I update #FreeBSD manually by creating a new BE first, and then using that as the installation target for kernel, base (world) and packages. That's perfectly safe (not touching the currently running system at all) and requires just a single reboot when everything goes fine.
It might be a bit underdocumented though, IIRC the handbook only describes upgrading the live system (still safe when creating a BE beforehand of course)
Going from #FreeBSD 13.2 to 14.0 on a laptop in a #BootEnvironment using packages from my own #poudriere repo with one simple reboot and running into just one small hiccup.
Having a box that even I can understand quite a bit of is worth so much.
Thank you, #FreeBSD community for building all this. <3 #runbsd
@lobocode bmake makes you think about your makefile in a more declarative way. As a result, bmake supports querying Makefiles for the value of a variable, e.g., `bmake -V CC` would give you the value of CC.
Usually, it is possible to express the GNU Make functions with the "!=" assignment in bmake. E.g., when I need an equivalent of GNU Make's `$(wildcard ...)` I tend to use `FOO!= ls *` instead.
@lobocode They're just very different.
#gmake excells in "meta-programming", providing functions (builtin and custom) and the "evil" $(eval ...) (and indeed, code using that is hard to keep at least remotely readable), basically containing a functional programming language. OTOH, it sucks in surprising ways, e.g. it has no idea of numbers/arithmetics. It also has things I'd personally call total "misfeatures", like these default variable values, default rules, even pattern rules can bite you badly ...
Among the strong points of #bmake are many very concise and flexible variable expansion modifiers (including arbitrary replacements, also using regular expressions, and even a "loop expansion").
#FreeBSD makes good use of the nice #bmake features in its build systems (at least base and ports).
@lobocode They're just very different.
#gmake excells in "meta-programming", providing functions (builtin and custom) and the "evil" $(eval ...) (and indeed, code using that is hard to keep at least remotely readable), basically containing a functional programming language. OTOH, it sucks in surprising ways, e.g. it has no idea of numbers/arithmetics. It also has things I'd personally call total "misfeatures", like these default variable values, default rules, even pattern rules can bite you badly ...
Among the strong points of #bmake are many very concise and flexible variable expansion modifiers (including arbitrary replacements, also using regular expressions, and even a "loop expansion").
#FreeBSD makes good use of the nice #bmake features in its build systems (at least base and ports).
Is there any advantage to using #bmake in #FreeBSD instead of #gmake? I get the impression that gmake allows for more modern directives (like adding multiple files to the SOURCE parameter instead of pointing them out one by one, or having to delete this in a shell). But, I dunno, sometimes that can also be a disadvantage...
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟰/𝟬𝟰/𝟮𝟮 (Valuable News - 2024/04/22) available.
https://vermaden.wordpress.com/2024/04/22/valuable-news-2024-04-22/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟰/𝟬𝟰/𝟮𝟮 (Valuable News - 2024/04/22) available.
https://vermaden.wordpress.com/2024/04/22/valuable-news-2024-04-22/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
@david_chisnall
I have a suggestion: #FreeBSD Core proceedings be completely open except for the few instances when executive session is appropriate.
Referring to one's "time on Core" isn't the flex anyone thinks it is if no one knows what takes place.
@stevelord @vermaden
Made a decision.
For the longest time I've always had too many distros that I tried to run and support.
I need to fokus on something in the end... and not drift around all the time.
So, #Debian it is - only
I use #Debian all day / every day.
It does not make sense for me to run any other distro.
On the #BSD side I will focus on #FreeBSD - that's it.
The many distros / derivatives have learned me a lot over the years... and I'm very thankful for that. But, less is more.
In my next article, I'll focus on the development environment, and from time to time, I'll offer tips on tools within the #FreeBSD atmosphere. Of course, there will be plenty of tips about Emacs as well.
Here's another lengthy and useful article about #FreeBSD for developers. In this one, I explain about the backbone of FreeBSD, which is the rc.conf, about manipulating shells, and the practical use of pkg:
Another text for today - " Why you shouldn't run a BSD on a PC"
"Changing GNU/Linux distribution can be done on a whim, as underneath all of that you’ve got the same basic operating systems. With BSDs it’s not the same. One should try to understand the downsides, as not to waste the next 20 years exploring an OS that simply is not a good fit."
https://michal.sapka.me/bsd/why-not-bsd/
(I thought I will write the pro-BSD text first, but the hell with calendars)
All the articles from now on will be secondary compared to this one. I've been writing it for some time... #freebsd
I spent some time testing BSD Mail today.
I tried to crash the whole system, to see how stable Dovecot's replica is (spoiler: it's definitely reliable). I've made up my mind that passwords will be encrypted via bcrypt, ensuring modern, reliable, and secure cryptography.
From now on, it's possible to change your password through SOGo, which will update the DB where Dovecot and opensmtpd fetch their data from.
Let's move forward!
#BSDMail #Dovecot #OpenSMTPD #OpenBSD #FreeBSD #SOGo #Security #IT
Remember to send your #BSD probes to
http://bsd-hardware.info/
Thought I'd just check in with the latest updates on #FreeBSD by way of running the #GhostBSD live iso on my ThinkPad P14s AMD and the WiFi actually works now !
OMG I may need to investigate further to see if everything now works !
You do understand this is purely for research though. This post was made on a running #BSD system. 😉
@peterkotrcka Qt isn't *that* huge ... built it e.g. for my cross-toolchain, so I could produce #Windows binaries on #FreeBSD (not #qXmoji of course, this would make little sense for Windows).
But then, there's little difference for qXmoji either. Most notably the format of the history in the settings file (because Qt5 can't correctly produce emojis in utf8, while utf8 is the default for settings in Qt6 and works fine there).
Regarding Ubuntu, well, the packages are there. Just without the .pc files for pkg-config. Probably worth a bug report, but I won't create it, I don't even use any Linux 😉
It should build with Qt6 after installing qt6-base-dev and qt6-base-dev-tools, getting the .pc files I added to the repo and pointing PKG_CONFIG_PATH to them 🙈
@PurpleJillybeans
1. It works. At least for me.
2. It has #ZFS fully integrated. Boot environments work on top of that, they're very useful for a desktop as well. Similar for #jails, although admittedly a bit less relevant on desktops.
3. It's "designed". The whole base system is a well-integrated piece of software from a single source repository. You can easily understand how it works (at least from the user perspective). Changes are done in a thoughtful way, not "just because", and not in isolation with no "big picture" in mind like you often see in the GNU/Linux ecosystem.
4. When I use it on my server anyways, using something else for my desktop would just be unnecessary friction for me.
More of my reasons: https://sekrit.de/webdocs/freebsd/advocacy.html
Yes, I used some Linux system before. Getting increasingly frustrated with it around 10 years ago (yes, #systemd had its share, but wasn't the only thing), I looked for something better. I quickly became a #FreeBSD ports contributor and later commiter.
@PurpleJillybeans I switched to #FreeBSD because I got the base system stability of #Debian while still having access to all the latest packages as if I were running #ArchLinux. It's a sweet spot for me.
Playing videos, displaying images and streaming online content on #bsd without a graphical server.
@yeti @mms
IIRC and IIUC, #FreeBSD and #NetBSD are branched quite early phase. #FreeBSD (including former #386BSD) focused on performance and stability on (ATM) i386 only, and #NetBSD focused on portability by strictly separating MD parts and MI parts. #OpenBSD was derived later from #NetBSD, focusing on security.
The plan is to release the information gradually, but I still have a lot of material to share about how this operating system completely won me over... it's simply sensational... https://dev.to/scovl/freebsd-for-devs-03-4dhd #freebsd #os #developers #devs #c #java #go #lisp #bestie
Coming soon ... #freebsd
We started the year with little infrastructure in place but now have completed CfP, a Schedule, Open Registration, near-complete SWAG orders, and a solid list of awesome Sponsors.
EPIC thank you to the team of volunteers who are making this possible.
Please register today and it's NEVER too late to sponsor!
♥️
@brainwagon @stefano Pretty sure I installed 386BSD from floppy disks, before #FreeBSD and #NetBSD evolved from the "Jolix" work.
[Edit - Lynne's obituary of William Jolitz: https://386bsd.org/memoriam ]
Registration for the 20th BSDCan conference at the University of Ottawa is open! Visit https://www.bsdcan.org/2024/registration.php to register. (Please allow three days for your conference payment via paypal to register). The conference will be May 31 - June 1, preceded by two days of tutorials.
You can find our list of programming including talks and tutorials, masking policy, information about the venue and local accommodations and more at https://bsdcan.org. A tourism group will be visiting Ottawa attractions concurrently with the conference, so bring your families!
We are still welcoming volunteers, sponsors and lightning talk participants. Join our announcements mailing list at https://lists.bsdcan.org for the most complete and timely conference updates. We're looking forward to a fun, safe and valuable conference!
#BSDCan #TechConference #bsd #netBSD #openBSD #freeBSD #dragonflyBSD
🍁 Registration for #BSDCan 2024 is now open!
The 20th BSDCan will include tutorials on PF, running your own email, TLS, BGP, and NSH, as well as two days of talks on everything from systems administration, networking, and programming.
Register here: https://www.bsdcan.org/2024/registration.php
#FreeBSD #RunBSD #opensource #softwaredevelopment
High-quality content about #FreeBSD coming your way on your screen! https://dev.to/scovl/freebsd-for-devs-02-44mk for #developers
Remote host execution for vscode landed in the 2024Q2 branch of ports. 😘 #freebsd
Happy Friday #FreeBSD
Here's a #port for #FreeBSD offering qt5 and qt6 flavors:
https://people.freebsd.org/~zirias/patches/0001-x11-qxmoji-Add-new-port.patch
@gyptazy Ok, I see. :)
I have been asking because we have spent a lot of time on getting #Jitsi to run on #FreeBSD (the latest version is available as a #Potluck container at https://github.com/bsdpot/potluck/tree/master/jitsi-meet or in the repository at https://potluck.honeyguide.net/blog/jitsi-meet/) but we never managed to have it work reliably with all client/browser types (some simply try to connect again and again). It works 90% of the time but not always - and that of course if not good enough if you really want to use it.
It probably has something to do with getting all the components (Prosody etc) work together correctly but none of the how-tos on the Internet helped to get a really correct setup...
#qXmoji v0.6 released!
https://github.com/Zirias/qxmoji/releases/tag/v0.6
This brings a *lot* of improvements and fixes, the most relevant being immediate persistence of settings and watching the settings file for external changes. To make this feasible also for restoring the history, a lot of work went into generating static emoji data that can be used efficiently (e.g. containing a hash table to find an emoji quickly).
BTW, this even works on #NFS, so if you have your home shared and you're running qXmoji on two machines as the same user, the history will auto-update in both instances 🥳
Important dates for #eurobsdcon 2024:
2024-05-01: Registration opens (https://2024.eurobsdcon.org/registration.html)
2024-06-15: CfP closes (https://2024.eurobsdcon.org/cfp/index.html)
2024-06-22: PC finalizes speaker selection
2024-07-15: Schedule published
2024-09-19—22: EuroBSDCon 2024 in Dublin (2 tutorial days, 2 talks days)
#bsd #freesoftware #openbsd #freebsd #netbsd #development #conference #dublin
Our first weekly will start on the 25th, April 2024 at 7 PM (GMT+2).
You can find all the details on the #BSDCafe wiki:
https://wiki.bsd.cafe/docs:weekly-bsdpub
For the first one, I already created a small agenda (https://wiki.bsd.cafe/docs:weekly-bsdpub-meeting-minutes-2024-04-25). You are highly encouraged to modify and extend this, as well as upcoming agendas!
Overview:
Day: Thursdays (weekly)
Time: 7 PM - 8 PM (GMT +2)
Where: https://meet.gyptazy.ch/BSDPub (Jitsi)
Infos: https://wiki.bsd.cafe/docs:weekly-bsdpub
Agenda: https://wiki.bsd.cafe/docs:weekly-bsdpub-meeting-minutes-2024-04-25
Info: No recordings, no deep tech dives (keep it simple, we have calls for the details, no pressures to anyone, have fun and enjoy)
When I started the poll to ask for interests in such a meeting I wasn’t sure that even more than 5 people would be interested. I’m happy to see this amount of interested BSD users. I’m aware of the different timezones and it might make sense to have a second timeslot. This one mostly covers the European and near-east users. I’m happy to hear suggestions regarding preferred timeslots for the US, Asia,… so far, I’m happy to see at least a few of you next Thursday in the call!
#FreeBSD #OpenBSD #NetBSD #helloSystem #BSDCafe #BSDNetwork #OpenSource #Solaris #illumos #openindiana #community #meeting #havefun #fun #BSDPub
#FreeBSD 14.1 release engineering process started: https://cgit.FreeBSD.org/src/commit/?id=7a2c2599a760156d8ef8bdf741adc1abd4ad26fc
Dear all, how is #OpenBSD with the #Nvidia (m)GPU?
#FreeBSD 14 is failing me on the desktop side and I haven't been able to spot the causes.
I am thinking to test OpenBSD but differently from FreeBSD it doesn't have the official driver, I am concerned to get a very poor experience because the gpu driver, and the idea to reinstall later FreeBSD doesn't get me excited at all...
Thanks in advance...
Registration for the twentieth
year of BSDCan is now open! See
https://www.bsdcan.org/2024/registration.php
We have tutorials on PF, running your own email, TLS, BGP,
and NSH + Two days of talks on everything from systems
administration, networking, and programming #bsd #openbsd #freebsd #netbsd #freesoftware #development #bsdcan
Small rant:
#BSD is a sane platform - period!
Why?
It works and is dependable.
Does that matter anymore?
More than ever!
We live in a constantly changing world - for better or worse.
Many chase the next best thing... code is getting bloated more and more by the hour.
In the end we have a safe place to grow and learn...
It is called: #BSD
Run #BSD and enjoy the journey!
After all: This is #UNIX the way it was supposed to be! 😎
I've expanded the #FreeBSD handbook with a section about #zeroconf and #Avahi. (#mdns/#dnssd).
https://docs.freebsd.org/en/books/handbook/network-servers/#network-zeroconf
Feedback welcome!
I'll start sharing my experience with #FreeBSD in this space here: https://dev.to/scovl/freebsd-for-devs-3n0k
This is what I'm hoping we can achieve in the next decade: at least one deployment of a censorship- and surveillance-resistant wireless mesh network.
We would run these nodes (and supsernodes) on #HardenedBSD.
There is work in #FreeBSD to support wireless mesh networking. There's even a presentation on it coming up at #BSDCan 2024: https://indico.bsdcan.org/event/1/contributions/12/
The work we're doing in HardenedBSD would pair very well with this.
I'm doing unholy things with #FreeBSD #OpenZFS VM-IMAGES can can cause checksum errors and panics. Would you be willing to try to reproduce the issue and report back? I have included a script to reproduce the issue and all you need is a downloaded VM-IMAGE and a pool not named 'zroot'. I automate those if needed.
♥️
Any comments/experience from anyone out there using #Contabo S3 Object Storage via
https://www.freshports.org/sysutils/fusefs-s3fs/
Kissing #Vultr goodbye.
good morning, nice #freebsd community!
I have a misunderstanding how installation procedure works.
The Context: Dell T640 setup to do UEFI boot; 4x Crucial P5+ NVMEs in simple Glotrend NVME-to-PCI adapters;
The Workflow:
1. I install #freebsd on the NVME as a 4-way mirror from a USB stick; installation runs just fine
2. I remove the USB stick and reboot the machine
3. The machine cannot find the device to boot from and expects the USB stick to be present :(
It is obvious, that I am missing something here :(
Please share your thoughts/ideas. I would like to learn to do it properly.
UPD: https://forums.freebsd.org/threads/dell-t640-install-boot-from-nvme.93165/#post-652095
best regards,
Dmitry
@txt_file You shouldn't install and (try to) use a mix of #packages from different sources (locally built vs official pkgs) ... but doing `pkg install git-tiny` and later update that from #ports won't hurt. Another bootstrap option is to just fetch and extract the `ports.txz` snapshot that's created with every release.
When you're new to #FreeBSD, are you sure you need to build yourself at all? Using official packages is recommended unless you have an actual need to customize build-time options ... or, of course, there are no packages for your target architecture.