i swear if i didn't know any better.. i'm wondering if i'm having an overheating problem on a nic on the fbsd server. it randomly just dies on me.

in this case i had to power it off.

i'll have to see what happens with this go

Sometimes the hardest problems to debug are just flaky hardware.

as an electrical engineer, can confirm

yeah

i think it must be. although i ran proxmox flawlessly for 3 years on this very server

but for some reason fbsd flakes out. it just did it again

ok. i think i just give up on this project lol

i'll just stick with proxmox

oh. wait... there's one last thing i think it might be before i completely give up

oh it can't be. em0 is intel :/

i was hoping maybe it had realteks that were glitchy

realtek is weak and wonky

yeah. my current router uses them

either way. i'm trying to get opnsense to use the ipmi sol

but yeah i have no idea what is going on with the freebsd server

i was making great progress on it.. and everything runs for a while.. but then it just completely takes a dump heh

usually when under high network load so i'm guessing maybe my sfp+ card is wonky and wrecking it.. but i don't know what it is. so i'll just yank those drives back out of it and toss it back in the isilon and mothball it

sweet. have sol working on the other 1u

Pleased to announce I've actually used telnetd in 2025… but it was on that raspberry pi zero because I suspected it was browning out by trying to draw enough power to run ssh.

Hello, all. I am still conused: if I don't update a FreeBSD intallation, how long will `pkg install' remain functional and not break my system? Last time I invoked it on my 14.1, it broke several packates, which I was able to fix only by upgrading the OS to 14.3 .

ant-x: hard to say with certainty; maybe a year and a half, maybe more

(or maybe less)

we don't make any guarantees about forward compatibility, so if a new release hits (+3 months) it's quite likely we made some changes that ports will adapt to and not work on previous releases

where '3 months' can mean a little more, releases go EoL when so@ says they do, which might not be the published date of EoL for convenience (but shouldn't be before)

kevans, but if I keep using /the same/ repository URLs, and always use `pkg --no-repo-update' -- is there a reson it may break?

In other words, are the binaries available for 14.1 when it was supported, suddency become unavailable some time after a new release?

because the repo is build for the oldest non-eol release of that major version

Ah? That explains it!

That will cause trouble for me to keep using FreeBSD 14.3 on a 32-bit machine.

why 14.3? 14.4 won't lose support for 32-bit architectures, as it is a minor release

15 has support for 32 bit architectures

When upgrading form 14.1, 14.3 was the last one. I can upgrade to 14.4, yes.

But what do I do then?

use a cpu made in the last... 15 years

ant-x, switch to NetBSD? >=]

Actually, does Open still support i386?

rtprio, CrtxReavr: I am aware of those other options. My question is how I can keep using FreeBSD. Do the binaries disppear as the release becomes obsolete? If five years late I decide to install GNU PG, will I be able to do it, and how?

you'd probably want to discontinue packages and use ports; for the _longest_ time nearly any ports tree would work with any serviceable os version, but i don't believe that's the case now

The ports tree checks the OS version too, but it's easy to "fix"

Can I ask why you want to keep using an old, unsupported version?

rtprio, re: "use ports" -- that is compile from the sources?

ant-x: if you have the computing power just build from ports. I resently did some software architechture in a FreeBSD 11.1 VM and just checked out a relevant quarterly branch. There was only one distfile I had to dig up manually.

*archeology, not architechture :D

vkarlsen, just to have a static fixed-in-stone computer. I have always followed the strategy: "Update only when necessary (i.e. need some new program or function". It is hard to believe the binaries are not archived and have to be built for unsupported versions of FreeBSD. On the other hand, they probably weigh a lot...

Oks4, thansk for confirming a workable method.

^ That sounded Norwegian. Thanks.

ant-x: If you want it static and set in stone, why do you want to upgrade the pkgs?

vkarlsen, not upgrade, but install actually. I agree never to upgrade them beyond 14.4 on that machine.

But if I find I forgot to install a program, I want to be able to get its old 14.4-contemporary version.

ant-x: I'm not sure I understand the problem then. If you install 14.4 with all the pkgs you need, it won't just stop working one day

vkarlsen, the problem is that I may neglect to intall some packages in time, before it gets EOL.

ant-x: Ah right, that you can do, but you might have to build them yourself because the repo servers won't keep ancient pkgs around

ant-x: ... as long as you can find the necessary distfiles

OK.

ant-x: If you have the disk space for it, you can mirror all the pkgs :)

Those distfiles, are they stored separately from the sources?

Yes, they come from upstream most of the time

vkarlsen, I have thought of mirroring everything, but that seemed fantastic...

vkarlsen, how do I mirror a pkg -- via `pkg fetch' ?

ant-x: Example: devel/swig takes the distfiles from sourceforge: github.com/freebsd/freebsd-ports/blob/main/devel/swig/Makefile#L4

I don't know how easy it is to grab all the pkgs nowadays, but I'm sure someone here can answer that. kevans?

ant-x: yes, ports compile from the sources

Would it be in the order of terabytes?

It won't fit on a cd

vkarlsen, I see no SourceForge reference in that makefile.

SF/swig/swig/swig-${PORTVERSION}

vkarlsen, I can live with not fitting on a CD :-) But I fear it won't fit on a DVD as well.

This one is more self-explanatory: github.com/freebsd/freebsd-ports/blob/main/dns/unbound/Makefile#L5

vkarlsen, is SF an alias to SourceForge?

Yes

I see. So, package depend on separately maintaied distfiles.

When/If I get to building ports, I'll investigate in detail. So far, I'd prefer to download all the packages I may need on that soon-to-be-obsoleted machine.

The method Oks4 described earlier is likely going to be most economic, and more than reliable enough. It's what I would do. It just requires you to get somewhat acquainted with the ports framework.

Downloading all the pkgs is not straight forward either because the dir is not directly indexable, and it will be a very large collection of bytes, most of which you will never need.

Indeed. I'll try the combined approach: 1) use pkg install for what I know I (will) need, 2) learn to build ports.

vkarlsen, I do program in C a bit, and have written my own makefiles, but still large third-part Makefiles often scare me.\

ant-x: Then learning to use the ports framework should be a breeze

Hopefully, the use of ports does not require low-level fiddling the build system.

No, it usually does not

Only for debugging and troubleshooting, probably.

bitrot

Oh, no.

nimaje: "because the repo is build for the oldest non-eol release of that major version" I didn't know it. Is this documented?

Macer: just got an idea related to your nic hangups: have you set -tso -lro on the interface? missing those options has given me headaches on some nics when doing vnet jails

Hi everyone! :)

The last version of FreeBSD I was regularly using was 4.x (until 4.11), and at that time I was using the FreeBSD handbook as my main reference for (up-to-date) documentation, is it still the recommended way today (for 15.x)?

Hello

O HAI!

Someone running FreeBSD on a server (home)

*?

so am i. (cheers)

Hell yeah. Nice. Currently setting up my r320 with FreeBSD 14.3

want to run local DNS Server, Jellyfin and maybe blocky (Some one here recommend me blocky)

but a bit annoying that the fans spin up even if i just copy my pubkey to the server

on my r710 they only soudn like a jet engine on startup, after post they are not that loud

one of these days i need to netboot my lenovo system x 3650m5

Unless you pound on it, then to spins back up to jet engine mode.

Oh shit... i have an R710 too(cold). bought it 1 year ago for 30 EUR (on top).

Under my R320 is a R720 (both SFF) but the R720 consuming ~250 W

does anyone know how to muffle the noise w/o killing the cooling efficiency completely

sorry, -social question

AmyMalik, muffling it would be unwise.

It's just common for real serve hardware to default to panic mode, and run the fans and full speed, 'til they get a sane temp reading from the thermal sensors.

s/serve/server

It's usually just 2-3 seconds.

you could use poweredge-shutup or just adjust the fan speed over IPMI

but i think you'll at least need iDRAC Express

i just lost my enterprise license after a reboot. idk why. but i dont care about that much

the endless droning whine once it finally stops panicking hurt so bad i had to replace the mactine at my earliet conveience

i'm thinkng i should get a long ethernet cable and put it in the attic

You should. i have my server rack next to my desk and bed.

sotov1ch: to stay warm and toasty at night?

i thought it would but its actually cold. i moved to my own apartment almost 3 weeks ago (with 19) because some people dont allow me to run my server by them

do thin jails follow the host release?

they follow the base release jail

for bastille, when a new release comes out, you bootstrap that release, and then update the fstab to point to the newer release. i think their update command will take care of that now, but i'm accustomed to doing it manually

For which use-cases would you recommend Bastille over AppJail? From my understanding Bastille seems better for reproducible and portable jails while AppJail would be better for a more interactive build?