ox1eef_: got your message, thanks for the info, I'm going to install it and see :)

If I were to start a BSD user group in Seattle, would anyone be interested? (Or... are there any pre-existing groups I didn't find?)

xtile, the website looks dead: seabug.org/

Yep, I noticed that. The web archive has a snapshot of it in 2017 but it doesn't seem very up to date at that time either.

Little bit further up "Hamilton BSD Group" ( hambug.ca ) meets up rather regularly

Title: Hamilton BSD User Group

s/BSD/& User/

Pretty far away, though their meets are online, and Jitsi is pretty fine.

is there any event like hardcore DIY driver-writing workshop? since my hardwares are supported i lost the motivation

write-your-own-driver workshop

micttyl: what Hardware is it that you have there?

just graphics and wireless

it's more like admins here i think. such questions seem to be answered well.

anbody up for some ipv6 help?

I swapped back to my freebsd router again, and the (AFAICT) working config from May last year doesn't do the ipv6 things again

internet <> ISP-inflicted pass-through router <> FreeBSD gadget <> pppoe

pppoe being md5

*mpd5

mpd5? pppoe? hell, i used that for "VPN"

yeah its all I can use here

dch: that's a lot of hops, and lots of opportunities for things to go wrong

meena: its no different to anybody else

pppoe is the way the freebsd box does a pass-through connect to the internet

some people have a nicer connection option, sadly not here

micttyl: #freebsd-dev is where (some) devs hang out. #bsddev on EFnet is (also) where (some (other?)) devs hang out

micttyl: that said, those are two incredibly complex devices, and writing drivers for them will not be easy

micttyl: wifi is on #freebsd-wifi and graphics #freebsd-xorg both on EFnet

active but not across all timezones

micttyl: I guess you already know about docs.freebsd.org/en/books/arch-handbook/driverbasics & the book `FreeBSD Device Drivers: A Guide for the Intrepid` too

Title: Chapter 9. Writing FreeBSD Device Drivers | FreeBSD Documentation Portal

hey all if you had the following disks: dpaste.org/xX8uF and you was setting up a development work station which is a mixture of one bhyve container (running linux+docker) and some local development on freebsd (over ssh); how would you configure such a selection of disks

my present implementation is: zfs/RAID1(3 magnetic disks) with log and cache on the nvme, swap is also on the nvme, the SSD is where freebsd is installed

the VM sits on a zpool that is on that raid1

starting to think I should have done for freebsd to the RAID1 of magnetics and used the ssd for the VM, the nvme for cache,logs,swap etc

daemon: thats kinda what I ends up with

2x2 hdd in striped mirror

with a SLOG on the tail end of the NVMe

also, for a large part of my stuff, I turned sync=disabled on because its not very valuable data

at least, on the hdd

anyway its all about the backups guarantees

what I have on the nvme is a small set of stuff thats tarsnapped, that I really rely on, and a large chunk of stuff that is sent to rsync.net with restic

ah I use the magnetics as its 3 disks in raid1 for important stuff

I use the nvme for low latency fast read/writes

with the SSD kind of as the OS disk

yeah so I can afford the risk of a few hours of lost work, most stuff is git pushed elsewhere

same here

if you have an nvme do you really need an os disk at all

yeah the bios does not support booting from it, its not motherboard native I shoved a nvme card into an unused pciex16

thats a good rason

*reason

its such a weird box, its actually my work box (given to me by work a few years ago)

but you get 150 GBP 'desktop budget' per year to do what you want

so I got it the nvme

the hard drives come about because I was dealing with a huge database and needed the space

but its almost entirely headless

do not think its ever even had X installed (except the first 2 weeks I was there, where linux mint was pre-installed)

so its a kind of odd amalgamation

if I owned it I would upgrade its ram, when I am in the office on wednesday I will pop the panel have a look see what it supports

according to dmidecode, its a Gigabyte Technology Co., Ltd. H81M-DS2V

bah only supports 16G of ram

how to get the total writen bytes of an SSD ?

daemon: There is a good chance that max RAM statement is wrong. Many boards' specs are not updated as larger RAM modules become available.

occ look at smartctl in ports, and consider reviewing vendor-specific tools

ok, I got ipv6 working ... on the route

tomorrow, extend it to my PC so I can work instead of shaving yaks

bald yaks , bald yaks everywhere

dch: I used smartctl ,but it tells the TBW from system online,not the TBW of life.

s/ ,/,/

rokit go zoom

whoops, wrong window.

Hello friends! Do any of you use tigervnc? I was wondering why there doesn't seem to be a service in any of the `rc.d` directories

I have used that, only as a client

Hmmm

I've used it extensively in Linux. They recommend you only start it from a service

"They" who, Linux system or "tigervnc"? What was the context? I had seen "tigervnc" suggest to use "systemd" on Rocky Linux for otherwise life is damn too hard (because of "systemd"). Sure same might have been, or could be, done for FreeBSD by the interested parties

I have used *vnc routinely off and on as needed. I have always run it as myself rather than as root.

I can't imagine the use model for starting vnc as a root system service. But I have a hard time fathoming many systemd decisions.

rwp: it's not always necessary to start services as root, you know that, right?

parv: "They" being tigervnc. The recommendations are the same regardless of Linux or BSD. When I try to start it without a service, it complains about "deamonizing failed," so I'll have to figure that out later

meena, Even if "root" passes control to "rwp" that seems like a silly place to do it. Better for me to simply start vnc up as rwp.

rwp: yeah, but if you start a service as you for you, it's still a service

I think parv had the right idea as to it though because systemd wants to start everything for a strict parent child relationship where systemd is the parent of every process and has a concept of user services.

It's very patriarchal.

But systems not running systemd have no such need for that strict requirement of being a child of systemd.

I am not of that body but this describes it in some detail wiki.archlinux.org/title/Systemd/User

Title: systemd/User - ArchWiki

OT Rant: On Linux/systemd type systems such as Ubuntu just doing a file transfer with sftp will launch for that user a lot of processes such as the audio server such as the tracker-miner-fs indexer and gvfs services and more. WAT?!

where do i find changelogs for minor release updates?

specifically i'm trying to figure out if the kernel changes to linuxkpi needed for drm-kmod PRs 163 and 208 (updating to 5.11 and 5.12 respectively) have been integrated into a release yet.

phryk: reading over the commit log generally gives me a good enough idea what changed

phryk: freshbsd.org/freebsd/src/branch/releng/13.1 but also, the UPDATING file should inform you about breaking changes

Title: FreeBSD / src - FreshBSD

meena: oh duh, good call, now i feel dumb for not thinking of that. :'D i assume -CURRENT is the main branch? :)

okay, was able to make some educated guesses about which commits in main correspond to what i need and can see in cgit that these are indeed not merged into releng/13.1

thanks for the pointers^^

phryk: when you are interested to changes into releases, consider also reading release notes such as freebsd.org/releases/13.1R/relnotes . Of course, they are not as complete as the commit logs however

Title: FreeBSD 13.1-RELEASE Release Notes | The FreeBSD Project

salvadore: those are only for the initial release tho, aren't they? i'm looking for stuff happening *after* the initial release.

phryk: the order is CURRENT, STABLE, RELEASE. A CURRENT commit marked as MFC, means merge from CURRENT.

These are so marked if the developer has the foresight that it'll be good to have in STABLE branches and in a RELEASE

sometimes, commits are merged without MFC, and sometimes MFC commits are forgotten ;)

phryk: you can find post-release stuff int the errata pages, e.g. freebsd.org/releases/13.1R/errata

Title: FreeBSD 13.1-RELEASE Errata | The FreeBSD Project

meena: wait, stuff is merged into STABLE *before* RELEASE?

salvadore: i thought only security- and bugfixes are in there? i'm more interested in features.

phryk: CURRENT is for development, STABLE is for testing, and RELEASE is for running in production

meena: ah, i always assumed that STABLE would see even less merges than RELEASE, so I just avoided it^^

normally no new features are added to a RELEASE after it is released. If you want more features, then you have to move to STABLE

nah, STABLE is for… stabilising

mhh, bit of a misnomer then, but i think changing it now would just add to the confusion^^

mhh, the changes already seem to be in stable/13. but with what salvadore said, i assume this means they'll be integrated into the upcoming 13.2 but not the already released 13.1?

phryk: depends on what changes, but chances are: correct

yes, indeed

not 100% sure bit it sounds like it only adds functionality needed for newer drivers to linuxkpi. that might still mean somebody could install a too-new drm-kmod version and drivers on a kernel that can't handle them… tho i think pkg can detect kernel abi requirements?

s/bit/but/

okay, now i'm even more confused. i just found the package for my new gpus firmware in the pkg repo…

i'll see if pkg installing it will raise an error about kernel abi, that would clear some of the confusion^

nope, it installed just fine. :'D

pkg can indeed detect kernel abi requirements: if you do pkg info <package_name> you will see a field called FreeBSD_version that is used for that

more information about FreeBSD_version can be found here: cgit.freebsd.org/src/tree/sys/sys/param.h#n63

Title: param.h « sys « sys - src - FreeBSD source tree

and a useful list of changes corresponding to the FreeBSD_version values can be found here: docs.freebsd.org/en/books/porters-handbook/versions

Title: Chapter 18. __FreeBSD_version Values | FreeBSD Documentation Portal