https://www.youtube.com/watch?v=tiJuJxerg7o
#FreeBSDMeetings #FreeBSD #laptopDesktopWorkgroup #StatusUpdate #WorkgroupRecording #LDWG #RunBSD #BSD
Discovered this evening: a FreeBSD committer badmouthing me in an early January response to a survey.
I wish I had known about that, before I quit FreeBSD Discord a few days later: https://mastodon.bsd.cafe/@grahamperrin/113884929411349951
Rewind to November 2024: the same committer abused someone else. A few days later, his mentor wrote: "… Do not make me into a baby-sitter; I will not accept this role. …"; around an hour later, he apologised for use of a diminutive term.
Frankly:
― the offender does need a baby-sitter.
I have screenshots of the offender ranting in Discord, and so on. This is why I have largely withdrawn from contributing to the FreeBSD Project.
@emaste sorry, I'll not participate in tomorrow's meeting of the Laptop and Desktop Workgroup.
Spirits of cooperation: their lives, deaths, afterlives, and endings … I find it increasingly difficult to handle the emotional and other aftereffects of being targeted by irrational, ugly, ad homimem abuse, from a developer, in an online working group space between 05:30 and 06:06 a few days ago. Maybe more prolonged; I quit the server, without responding to the abuser, after waking to find a bad situation made worse by a so-called moderator. This is, perhaps, not the type of group work that inspires a person. It certainly does not foster a spirit of cooperation. Rewind: I lost sleep, much more than I ever admitted, in 2023. Fast-forward to 2025: I'm losing sleep, again. Despite my best efforts, the passing of time is not improving the situation, I need to do some thing quickly to halt the tide, the thing is this post. Part of this morning's sleeplessness was spent philosophically and positively, crafting various ways in which I might sugar-coat the situation. In my mind's eye this morning was a perfunctory, factual post that ended upbeat, by thanking (but not naming) a great peacemaker who reached out to me in 2023. Less philosophically: I'm tired, I'm disinclined to sugar-coat casually-dropped turds, and ― frankly ― the tiredness, past and present, is a direct consequence of unreasonable behaviour. I'm no angel, but hey, I have a breaking point, and if you wanna get your kicks and giggles through breaking people: I'll prefer alternative spaces, where the good in people can be brought out. This is not rocket science, you shit-heads, you utter shit-heads. To anyone who might respond here: please understand that I'll probably not continue the conversation. Further unravelling in private, or public, is not the way forward. Right now, I like the idea of a quiet end to this phase of my life. Around a decade might have been long enough. I want the decade ahead to please me, and I'm suitably calmed by the idea of silently abandoning everything from 2015 to date. I abandoned masses of stuff about which I was passionate in the past, never regretted moving on, if now is another ending I'll have no regrets. I'm calmed not only by the idea of abandonment, I was also calmed at the end of my working day by using two operating systems that worked perfectly. It's now 19:15, I'm done with writing about this. Cat time :-) To future peacemakers: thank you. To casual troublemakers: I have had more than enough of your turds. Don't make me share additional thoughts on the subject.
FreeBSD Laptop and Desktop Working Group Survey – LDWG Work Relevance Ranking
FreeBSD Project-provided repositories for kernel modules in the ports collection: usage
<https://blendit.bsd.cafe/post/821622>
14.1-RELEASE to 14.2-RELEASE
… an interim approach to avoiding the DRM graphics issue that was noted for 14.2-RELEASE before the release announcement …
#FreeBSD #upgrade #FAQ #Ludwig #LDWG #CFT #callfortesting #DRM #graphics #kmods #kernel
# 14.1-RELEASE to 14.2-RELEASE Essential reading: - installation information at https://www.freebsd.org/releases/14.2R/ [https://www.freebsd.org/releases/14.2R/] – you can create a configuration file for a Project-provided FreeBSD-kmods repo before beginning to follow the steps at https://www.freebsd.org/releases/14.2R/installation/#upgrade-binary [https://www.freebsd.org/releases/14.2R/installation/#upgrade-binary]. 1. mkdir -p /usr/local/etc/pkg/repos ; cd /usr/local/etc/pkg/repos 2. cp /etc/pkg/FreeBSD.conf ./FreeBSD-kmods.conf 3. ee ./FreeBSD-kmods.conf 4. change the repository name from FreeBSD to FreeBSD-kmods 5. change quarterly to kmods_quarterly_2 6. escape, save 7. cd 8. follow official installation information up to, and including, the second run of freebsd-update install 9. pkg upgrade --repository FreeBSD-kmods 10. ignore the mismatch (y) 11. if any upgraded kernel module is offered, proceed (y) 12. continue with official installation information – the first restart of the operating system, and so on 13. finally, re-edit /usr/local/etc/pkg/repos/FreeBSD-kmods.conf – change kmods_quarterly_2 to kmods_quarterly_${VERSION_MINOR} Notes: - the Project’s official call for testing (CFT) will lead to simplicity – please see https://old.reddit.com/r/freebsd/comments/1hd2h51/freebsd_projectprovided_repositories_for_kernel/m1ukuno/ [https://old.reddit.com/r/freebsd/comments/1hd2h51/freebsd_projectprovided_repositories_for_kernel/m1ukuno/] - the less simple steps, above, are an interim approach to avoiding the DRM graphics issue that was noted for 14.2-RELEASE before the release announcement – https://www.freebsd.org/releases/14.2R/errata/#open-issues [https://www.freebsd.org/releases/14.2R/errata/#open-issues] - the steps assume use of the traditional quarterly repo for packages of ports. https://wiki.freebsd.org/Ports/QuarterlyBranch [https://wiki.freebsd.org/Ports/QuarterlyBranch] should help to understand the difference between quarterly and latest - and beware of confusion with base_latest, which relates to pkgbase [https://wiki.freebsd.org/PkgBase] (base, separate from ports).
VirtualBox 7 on FreeBSD:
― not yet in the ports collection
― significant progress in recent weeks.
The first LDWG meeting, in December 2024, drew attention to <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271146>.
<https://wiki.freebsd.org/LaptopDesktopWorkingGroup> ◀ <https://old.reddit.com/r/freebsd/comments/1gm6ej6/freebsd_laptop_and_desktop_working_group_ldwg/>
@lproven good news,
Donation of the working iwx driver — <https://lists.freebsd.org/archives/freebsd-desktop/2024-December/005173.html>
In addition, I learnt in FreeBSD Discord that <https://github.com/orgs/FreeBSDFoundation/projects/1/?pane=issue&itemId=84366575&issue=FreeBSDFoundation%7Cproj-laptop%7C5> is iwx – but not yet marked as such.
The Tom mentioned in <https://lists.freebsd.org/archives/freebsd-desktop/2024-December/005182.html> is Tom Jones, whose FreeBSD Network Status reports I highly recommend:
<https://adventurist.me/tag/networkstatus>
#iwx #WiFi #wireless #OpenBSD #FreeBSD #Ludwig #LDWG #FBSD_LDWG
@duncan_bayne maybe of interest, in the board for the Foundation's Laptop Project:
― Put a specific laptop model into S4 hibernation <https://github.com/orgs/FreeBSDFoundation/projects/1/views/4?pane=issue&itemId=88118534&issue=FreeBSDFoundation%7Cproj-laptop%7C29>
― Implement s2idle low power state <https://github.com/orgs/FreeBSDFoundation/projects/1/views/4?pane=issue&itemId=88143979&issue=FreeBSDFoundation%7Cproj-laptop%7C35>
― Implement S0ix low power states — <https://github.com/orgs/FreeBSDFoundation/projects/1/views/4?pane=issue&itemId=88119601&issue=FreeBSDFoundation%7Cproj-laptop%7C32>.
The reason for me very rarely listening, to things that do interest me, is simple. It is entirely unrelated to content:
― Bluetooth.
A consequence of difficulty with, or the absence of, Bluetooth:
― I very rarely watch videos about BSD.
We have two FreeBSD Foundation Laptop Project contexts:
― Ensure Bluetooth drivers work <https://github.com/orgs/FreeBSDFoundation/projects/1/views/4?pane=issue&itemId=90563442&issue=FreeBSDFoundation%7Cproj-laptop%7C43>
― Improve Bluetooth management/usability <https://github.com/orgs/FreeBSDFoundation/projects/1/views/4?pane=issue&itemId=90563966&issue=FreeBSDFoundation%7Cproj-laptop%7C44>
The current milestone for both: 2025, third quarter.
Background, thanks to Joe Mingrone (Project Manager at the Foundation): <https://mail-archive.freebsd.org/cgi/mid.cgi?86y10enucl.fsf> or (without links) <https://lists.freebsd.org/archives/freebsd-desktop/2024-December/005126.html>.
<https://freebsdfoundation.org/donate/>
One-off cc: @duncan_bayne @david_chisnall @thindil @uastronomer @pauamma
#FreeBSD #Ludwig #LDWG #laptop #silence #Bluetooth #audio #sound #Foundation
@mwl sounds great. I look forward to your preview of the comparison at the first meeting of the Laptop and Desktop Workgroup on Monday 16th.
Seeking time-fillers only because, of course, there'll be nothing for laptop or desktop users to discuss.
Loosely translated: expect heated discussion of installers, despite the absence of the word "installer" at <https://wiki.freebsd.org/LaptopDesktopWorkingGroup>.
@garyhtech also:
<https://github.com/freebsd/freebsd-doc/pull/442>
― 14.2R/errata: news: inclusion of Wi-Fi firmware · Pull Request #442 · freebsd/freebsd-doc
「… chicken-and-egg … hard to download and install firmware if you don't already have the firmware you need to connect to the Internet. …」
In plain English: with the installer for FreeBSD 14.2, there's not only the pictured ability – automatically detecting, downloading, and installing hardware-specific packages from a mainstream Project-provided repo.
There's also – within the image that provides the installer:
― additional firmware, to greatly increase the likelihood of people gaining an Internet connection during installation.
For this reason, and others, 14.2 is a greater milestone than many people have realised. Foundational changes in 14.2 make various things – some of which are obscure, but game-changing – easier to achieve. I'll drop a hint to you, privately …
#mainstream #chicken #egg #FreeBSD #Internet #WiFi #wireless #firmware #installer #install #RELEASE #novelty #pkg #packages #hero #milestone #LDWG