is there somewhere I can read about the upcoming service jails? I'm curious how they're implemented and if it's much different than single executable jails and the way I've been playing with doing that with runit .

duskmoss: it's just a jail with path=/

ah.

easy thanks :)

which means the isolation is not very strong (basically useless for anything that runs as root) but i hope it can be expanded later

is 15 on track?

kerneldove: yes

nice

much excite

I've been using linux for a number of years, I've tried freebsd a number of times. I'm now ready to install & test freebsd as a desktop. My concerns relate the wifi compatability under freebsd for my dell i5-10210U, it's a Atheros QCA6174. I know that it has limited compatability both for wifi & bluetooth. If look attatch a dongle with wifi & bluetooth, what do you guys recommend? Is there an positive options for 5G wifi or only 2.4G. Thanks.

pardon my grammar?

_mystified: Looks like there are options for you. You may have already seen this, but if not: forums.freebsd.org/threads/question…about-configuring-ath10k-wifi.93859

That thread's over a year old, so maybe things are better now, but I suspect the avenues to try are the same.

No, I'll look it now, Thank you !

The person gave up in the end, but maybe things have changed, and it might be that with a bit more diligence wifibox would have worked. And maybe the driver's better now, over a year later.

_mystified: on the off chance your wifi card is mini-pci(e), you could swap it for an intel card

That too.

My thoughts is to purchase a dongle, but I'm trying to ascertain, which dongle would be my best option ?

Has anyone tried this CSR8510 A10 Bluetooth Dongle

hello?

hi

I just got a "⚠ Cannot send to nick/channel" in another room. What does it mean?

hi

o/

been a while since i've bought bandwidth in datacenters. anyone have some ballpark figures on what 100gbps and 1/4 cabinet goes for? i'd be looking for a DC around the seattle SIX ideally but flexible

kerneldove: you'll probably get a better answer in #networking

tried hehe

No chance to ever get my Linuxulator patch even looked at by anybody? reviews.freebsd.org/D47417

(I was just reminded of it by that one app that motivated me to do it in the first place.)

btw. I noticed that AppImages now run without prior extraction (14.3). Nice!

rhaberkorn: if you aren't a committer, i strongly recommend using github to submit patches, not phabricator. github has a process to find reviewers for patches and commit them, phab does not (it assumes the submitted knows who should review it and will commit it themselves)

also, you're likely to get a better answer for this sort of question in EFnet #bsdcode than here, not many committers hang out here

ivy: Thanks. Back then I was advised to submit via Phabricator.

What about port upgrades? Still via bugs.freebsd.org?

yes, non-maintainer ports updates must go via bugzilla because there's where the automation is - i think some ports are now using github but you'd know if you were working on a port that does that, i think

rhaberkorn: that is quite a large change to review, but the header moves look straight forward

rhaberkorn: also if a committer told you to use phabricator, you should complain to them and ask for more reviews :-)

non-*committer* port updates need to go via bugzilla

many maintainers aren't committers

paulf: no, committer updates should also go via bugzilla because that's how the maintainer is notified and can approve the update or not

paulf: the only exception that i'm aware of is a committer who isn't a ports committer updating a port they maintain, which can go via phab

(because maintainer approval is implicit in that case)

the one time I didn't approve a change (in Phab) the change went in anyway despite the committer not having a clue what they were doing

well, that sounds like a good reason to not submit non-maintainer changes via phab

it was the clueless committer that also started the Phab review

but yes, I think that most port updates should go via bugzilla

fwiw, i would never update someone else's port via phab and i think it's wrong to do this, you would not be wrong to complain to portmgr about that

I opposed the change strongly but portmgr went with it anyway

and I must say I lost a great amount or respect for committers and portmgr

Guys a big problem here

which is?

paulf: he has big problems asking specific questions

GTK hangs on Linux compatibility layer FreeBSD.. until I make PC sleep "zzz", then I making it wake up

It stops the hang and the program opens..

rtprio: Heh, sorry ;)

I believe that bug never happens when I disable my radeon drivers

mosaid: did you try acpi reset video sysctl?

mosaid, why not native GTK?

ivy: it's also not invalid to do phab reviews for ports if the maintainer is also a committer, but if you're expecting a timeout you need bugzilla

CrtxReavr: I want to run some Linux software which I need

just keep the pc awake

polyduekes: I will try

rtprio: To run any linux program make use of gtk, I need to sleep the pc then wake it up

or disable my drivers

which will make resolution so low

what

o_O

oh, it's not working

rtprio: ?

i find it hard to believe your resolution is different without video drivres

Oh found the error

syscall inotify_init not implemented

syscall inotify_init1 not implemented

So is this causing the error or something else?

An error or a warning?

Let me see

It didn't mention

what is it

But that behaviour is so strange

hi all, when "hand"-managing jails, how should I be changing osrelease and osreldate (from jail(8))? I thought one of the main advantages of jails was the ability to have an older release in a jail and it still running. If I bootstrap and run 13.5-RELEASE-p3 in /usr/local/jails/containers/135_heta but have 14.3-RELEASE-p2 on the host, the jail is super confused. /etc/os-release in the jail also

holds some info, but nothing seems to agree with anything

arent jails are now called iocage for a cuter name ? :D

moviuro: In what way is the jail confused? I have done this before

moviuro, One way to check versions is "freebsd-version -kru" for the host kernel installed, kernel running, and userland. And "jls" and then "freebsd-version -j nginx" (using nginx for example).

In jails only the userland version is significant. And then ports/pkgs are completely separate.

This is a quickie command line one-liner: for jname in $(jls -N | awk '$1!="JID"{print$1}'); do printf "%s %s\n" $jname $(freebsd-version -j $jname); done

I had bad memories of pkg(8) screaming about inconsistent osreldate when some upgrades happened. I was terrified theis would happen again. But the good news is that pkg -dj $jail install whatever properly shows that it's looking for the correct ABI (the one from the jail).