gh00p: it should break out corresponding cuaU*/ttyU* ports that you can drive it via serial with

not sure best approach from there

odd warning during a src build, seems like something is being installed without DESTDIR perhaps? make[5]: warning: /lib/geom: Permission denied.

lw: lots of those, harmless

jrtc27 had a fix, but it wasn't quite right

what causes it?

Title: ⚙ D30990 src.sys.obj.mk: Export OBJTOP like OBJROOT

phew

couldn't figure out how to get phab to render your reviews on the mobile app

s/render/list/

ohhh reviews.freebsd.org.. this is how i see the hsitory of things that make it into -CURRENT :)

finally.. the brain kicked in...

voy4g3r2: usually if a commit has a phab review the url will be in the commit message

i just started noticing this in commits

and edmaste accepted one of my "little" manual pages

and there was a reviews.freebsd.org entry which i do not recall making..

yeah, it hoovers up all commits

/D* URLs are reviews, /r* imported commits

so if i was to "update" this bugs.freebsd.org/bugzilla/show_bug.cgi?id=247900 i probalby should brush up on uploading stuff to there

Title: 247900 – printf.3 improvements

instead of polluting the github stuff

either works, more or less

if you can find someone to land them via github that's good enough

hehe mhorne started reviewing.. so i was "pestering"

this bug is a big update, i do like how the openbsd version reads.. i am like yeah i get it

What version of FreeBSD was the last one that had PHP 7.4 in its ports tree?

I know it's long EOL, but I have a website by a customer who refuses to update his code, and doesn't run on PHP 8.

The only alternative is to put it on a Devuan machine instead.

The ports tree isn't tied to a FreeBSD version.

You could checkout a version of the ports tree dating back to when version 7.4 was last available.

You may have issues compiling though.

Give it a go nonetheless.

OK.

remiliascarlet: I've done this a few times recently

I can help find the relevant ports tree if you get stuck, but aside from that the overall process is:

- build everything using poudriere

- make a poudriere jail for the appropriate vintage of out-of-support OS, using `-m ftp-archive`

- look back through ports tree quarterly branches for when php7.x disappears

- build the packages

- add your package repo to the customer system and $profit

doing it without poudriere is significantly more painful, far more pain than setting up poudriere for the first time

in ports tree `grep php74\| MOVED` shows `lang/php74|lang/php80|2022-12-25|Has expired: Security support ended on 2022-11-22`

remiliascarlet: so it should be in 2022Q4 branch

remiliascarlet: so cgit.freebsd.org/ports/tree/lang/php74?h=2022Q4 exists

Title: php74 « lang - ports - FreeBSD ports tree

remiliascarlet: I actually need to document this for $WORK so docs.skunkwerks.at/s/qqMOZxZdu# is a start on that. Once I fleshed it out the post will appear on my blog

Title: Building expired ports for unsupported releases - HedgeDoc

hi all

hi adilix

dvl: hows your graylog work going? need a hand?

dch: Still trying to get opensearch to start, so not well. Yes, please. I was just composing an email to opensearch AT FreeBSD.org about this.

dch: [2024-03-23T11:53:49,826][ERROR][o.o.s.s.u.SSLCertificateHelper] [graylog-1] Alias sslrooteccca [jdk] does not exist or contain a certificate chain

bin.langille.org/?56894ed53ef6ec56#…QKuMHxqNEh342PdHyqagoWnK3mL19w1Q4kT has a bit of output from that tile

Title: PrivateBin

Thing is, there's lots of very carefully crafted documentation, but I can't find anything helpful. ;)

I've not used keystore at all, it looks equisitely painful

^ I got it going with plugins.security.disabled: true

if you get it working with tls let me know I'll gladly switch too

Now building textproc/opensearch-dashboards (which needs www/npm-node18 & www/node18)

Now it's another battle to get opensearch-dashboard up and running. I start it, it stops. Nothing logs. Thanks. :)

is it just me or are all search servers very annoying to administrate?

Too many projects lack practical examples. Get your potential users to the starting blocks so they can get up and running. Lots of documentation isn't helpful if I can get the damn thing to run first.

lw: I ran elasticsearch years ago, and killed those jails when they became too much work.

i used to manage Solr a lot at my old job and while it wasn't the worst thing i ever used, all the Javaness was pretty annoying

the worst thing with graylog is the dependency mgmt. mongo upgrades are a PITA. elasticsearch -> opensearch was a major PITA.

luckily in my case I can simply drop the DB if the upgrade is too painful, I have no legal requirement to retain those logs

hello, is possible ask support for freebsd? iam stuck on terminal sh after installation, xrandr and startx not recognize my videocard

my problem is= i install xorg, i install intel driver but when i try to use xrandr it say "i can't open videocard" (or something like that). on Xorg.0.log i have a error like (EE) No devices detected.

but i see the terminal.. so a videocard is used in some way...

forums.freebsd.org/threads/after-in…g-cant-setup-intel-video-card.92818 here my error, if someone can help me.. please ping me

Title: After installing xorg cant setup intel video card | The FreeBSD Forums

beautiful VimDiesel! amazing! ahahaha

naxil: the fact that you see the terminal doesn't mean that your videocard is used...

what is your hardware?

that should be fixed by installing proper package for your graphics card

V-T60: is a intel stick pc (micropc) is called STCK1A32WFC

V-T60: you can see my hw here termbin.com/upjh

i have install the packed on handbook for intel and the tip pack on handbook (dri part)

naxil: did tyou install a video driver yet?

yes i install the intel package on handbook

naxil: just looking through your forums thread

thank you

i install drm-kmod package

and libva-intel-driver mesa-libs mesa-dri

naxil: I assume you rebooted after installing the packages?

but are the dmesg/pciconf info from after a reboot too?

yes i rebooted

naxil: i would first try removing your 20-intel.conf file in /usr/local/etc/X11/xorg.conf.d/ and reboot again

the hardware should be auto-detected and a driver attached

i manage the irc client on smartphone (now iam on diff os) and i load the freebsd os... wait a minute please

very tricky!

bbl, family times

naxil: if after that the driver hasn't attached it might not be recognised. I think the appropriate drivers are available, you can always try installing freebsd 15.0-CURRENT which might have a newer pci mapping

when is out the 15?

i think the latest is the 14

hi iam here with smartphone

now i boot freebsd

the advice is remove the 20 cfg file?

who is the guy helpme before?

i have deleted the conf fe

file

failed to load module intel so try to load modesetting and other driver but abort with "caught signal 6"

the driver do more impostation is "glamoregl"

ternbin.com/6fgc

sorry termbin.com/6fgc

if someone can help me.. iam infront freebsd terminal

I built chromium-123.0.6312.58 with poudriere, but my computer keeps crashing every time I attempt to build version 123.0.6312.58_1 of chromium.

Why is that?

what's so fundamentally different between chromium-123.0.6312.58 and chromium-123.0.6312.58_1 that I was able to build the former, but can't build the latter?

RhodiumToad: it's so bizarre because yesterday I built the earlier version using the MAKE_JOBS_NUMBER=20 setting, but can't build the _1 version even when MAKE_JOBS_NUMBER's value is as low as 4.

I have a DS18B20 connected to a raspberry pi running 13.2. I think it is set up properly, but there is no dev.ow visible. I have `dtoverlay=w1-gpio` in my config.txt. What might I be missing?

Oh, and I have set `owc_load`and `ow_temp_load` in /boot/loader.conf.

lw

jbo: if it's ports related i'm not here, have spent the last two days working on src arm64 stuff, now i'm taking a break :-)

lw, nice!

lw, no ports related issue :)

do people here have any recommendations for periodic scripts within jails when a host has a growing number of them?

I am noticing that there's a growing performance impact during the late hours of the night, when periodic runs, not to mention the amount of disk activity...

jmpp, Dan Langille posted that included a list of things to turn off from periodic in jails, and probably useful elsewhere too. gist.github.com/dlangille/ce60ac76b69f267a3f1de33495a338fc

Title: Periodic things to turn off in FreeBSD jails · GitHub

rwp: awesome, thanks!

and given the amount of jails Dan runs, that must be reliable advice!

It's always a Thundering Herd problem when everything happens at once. And for the most part we don't want any of those things happening in a container.

rwp: yeah, so I'm learning

another one that's cropping up upon getting deeper and deeper into jails: to clonejail, or to basejail...?

well, actually, I'd say the appropriate question would be: to clonejail, or to thickjail?

'cause I'm currently running all of this on TrueNAS CORE, which ties me to iocage, and in iocage a basejail is a collection of nullfs mounts, which I don't want for my jails

if I happen to move these jails to a separate, presumably vanilla FreeBSD host, I'll look at BastilleBSD and thickjails

i just enable dedup on the filesystem holding the jail roots. with the small amount of data in the root filesystem, memory use is unlikely to be a concern, but it does mean application data needs to be stored somewhere else

oh neat, noto-extra got split into different character set packages, so I can select what I need and not have it flood the dropdown menu of fonts I don't use.

kenrap: didn't that get immediately reverted?

ah crap, bad timing on ports pull then.

well, seems like someone reverted it then committed their own version... so not sure what the status is exactly bugs.freebsd.org/bugzilla/show_bug.cgi?id=275758

Title: 275758 – x11-fonts/noto-basic and x11-fonts/fontconfig together enable ligatures in "monospace" font

is portsnap still the preferred method for grabbing the ports tree?

I'd like to try out drm-61-kmod on 14-STABLE, but there isn't a package even in latest

tm512: no, use git, portsnap is deprecated and will be removed

lw: after doing a ports pull, it didn't seem to affect poudriere-bulk after running it.

lw: alright. glad I asked

wow, did not know configuring periodic for my jails would be *so* involved!

I guess I should also mentioned that due to the latest librewolf update, the browser configuration path changed from ~/.mozilla/firefox to ~/.mozilla/librewolf, which is a good change but a confusing one since I thought the update had decimated it.

moving the old one to that latter path solves that

lw: actually I think I know why poudriere-bulk didn't react the way I would've expected. Since sunpoet reverted tijl's portrevision 3 back to 2 and then committed their as "3" again, it didn't look like anything had change at all to poudriere.