Howdy, folks!

Does anyone know of a terminal based way to read the FreeBSD Documentation without installing an additional tool?

I have something I created, but think there has to be something that does this already within the OS

was it in *roff too?

never checked

unsure what markup handbook used

I do not know what ketas is

I mean what *roff is

well manpages are i think only thing that base has viewer for

That's what I thought. I wonder why that is

AsciiDoc could use a rst generator

What is that?

Ah. EPL license.

AsciiDoc is what the documentation files asre written in, docs.freebsd.org/en/books/fdp-primer/doc-build

so the idea is make rst would build to rst files

Oh okay. Could someone take a look at my script, which uses the freebsd handbook package to make it terminal readable?

HER the plastic is always the worst

because of microplastic

I just became aware of two incoming relases, 13.5 and 14.3 - was it always like this, or something changed 'recently'? sorry for the dumb question, couldn't find answer googling

guys is it  possible to run Freebsd on a playstation 3

xd

briandaed: FreeBSD still supports the 13.X series and the next one in that is 13.5 We also have the 14.X series and the next one in that is 14.3.

TommyC: thanks, so planning package support one should take care of two branches, right?

It should. Ports has quite a bit of separation from the base system.

TommyC: thanks again, that's what I needed.

dstolfa, termbin.com/er9w

CrtxReavr: yeah, as you can see there's no libllvm there, so it should be statically linked into rustc (and it will be whatever version rustc uses)

although there are parts of llvm dynamically linked from the system, namely libgcc_s, libc++ and libcxxrt

but that's a different llvm to the one that rustc expects to use

dstolfa, you're probably reacting to when rustc was coring on me. . . that paste was on a different system that I upgraded to 13.4 and rebuilt the port chain that needed rust.

That really is a huge to chunk to rebuild.

rebuilding rust usually involves building a clean llvm as a part of it and a bunch of its rust dependencies which take forever to link

so... yeah, it takes a while (:

Rust source build sucks time and resources wise

so how good is freebsd at repelling syn flood attacks these days?

i ask because my current server is pretty much under synflood attack 24 hours a day, 7 days a week, forever

and my current server is not running bsd, and it does not handle this well

What is your current server running and what have you tried to handle it?

it runs an old version of macos and i've done nothing to handle it because there are no built in solutions for it. the syn packet protection built into pf is missing and there doesn't seem to be any way to correct that. its not something people at the genius bar are going to know anything about

i am behind my data center's anti ddos system but stoping syn floods specifically is not it's strong suit

Not familiar with Mac OS or its firewall there, sorry.

thats ok. i'm not asking about macos, i'm asking about freebsd :D

i'm overdue for a new server anyway so I'm toying with freebsd, i like how similar it is to macos in many ways

i haven't gotten to network/firewall stuff yet in my exploration of the system

lol thats my post

but i was actually asking about macos not freebsd

and thats the feature that doesn't work on macos, hopefully it does on freebsd

well there's freebsd pf, but also openbsd's pf as well, depending on your preference