Howdy, folks!

oh yes you weren't there.

nicholaus04: why not use the builtin openssh in Win11?

vortexx: Ah, good point. But PuTTY works as well, but thanks!

Hmm...

Howdy, again!

Now using Win11's implementation of OpenSSH as a SSH client. Host OS is still the same(FreeBSD).

nicholaus04: Not sure you saw my post above, but as a novice with FreeBSD I don't get the point of using SSH and Putty in this instance. How is it different than running Tiny 11 in a virtual machine on your FreeBSD host desktop?

JustBleedFan: The funny thing about that, Tiny11 is running on 100% actual hardware.

So it's actually 2 seperate PCs, with different OSs.

So you're remoting into a different computer on your network, playing a game "on" a FreeBSD computer that otherwise would not run on the game by remoting into a Windows machine.

Not exactly, but yep.

I have Tiny 10 on my Linux Mint laptop. Used it a few times for different things.

i want to clone and expand an existing freebsd installation to a new drive

what is the best way if the old drive has bad blocks

unix.stackexchange.com/questions/31…e-and-extend-to-new-disk-in-freebsd <--this looks pretty sound

i would do a fresh install (using ZFS) and restore a known good copy of the data on the new instance

mornings

does anyone know how to use VALE if I want to expose my VMs to the outside world?

I tried using netgraph, but I can't get past 5Gbps

antranigv: How did you test the speed?

tercaL iperf3. I can get 10Gbps between two jails on NetGraph, but not on VMs. Maybe a tuning issue?

wanted to check VALE as well, haven't used it before.

np[therealvorteckz⊙lf] - Lithe - Numb

wrong channel sorry

Hello, I am tinkering around with an old version of FreeBSD (v11.2) . I know it's an really old version, I am just wondering if there is a package repository somewhere where I can get packages for v11.2 ?

14.0-RELEASE EOL is in a month, does that imply that afterwards drm-kmod packages has a chance to be bumped to Linux 6.1 version?

Pionat: Your best bet is probably to find a tag in ports and build everything yourself.

Pionat: For example with git you can check out this tag: github.com/freebsd/freebsd-ports/tree/release/11.2.0

erk: thanks

vedranm: well, drm-kmod is just a meta port choosing the real version depending on the build host, the condition ${OSVERSION} >= 1400508 (cgit.freebsd.org/ports/tree/graphics/drm-kmod/Makefile#n28) should be fullfilled as soon as the build host gets upgraded to 14.1 I guess, you could check by reading OSVERSION on a 14.1 system, e.g. via make -f /usr/share/mk/bsd.port.mk -V OSVERSION

(you may have to set PORTSDIR if you don't have it at /usr/ports/)

erk: Yes, the software that I want to install on this old 11.2 system was included in freebsd repo,

erk: how do I use the files held in freebsd-ports for building the software myself? (There is a Makefile, pkg-plist, and some other files)

erk: obviously I need to download the source code for the software (and right version), finding that isn't hard

Pionat: The handbook has a section on it and as far as I can tell it should fit with the older version: docs.freebsd.org/en/books/handbook/ports/#_installing_ports

erk: thanks

vedranm: if changes to the LKPI that drm-kmod ports use have been changed in 14-STABLE, maybe?

Pionat: freebsd can't provide binary packages for old versions; we tried, and we ran out of space.

antranigv: there was some (GSoC?) work back in 2015 on ptnetmap involving vale and bhyve, but I don't know the status of it

antranigv: you can also have a look at freshports.org/net/vether-kmod

valectl has the -h switch to attach things at multiple ends, which i think is the crucial things

s/s$//

that's all i remember at present, though

nimaje: yes, I know I can build it from source already on 14.1-RELEASE

debdrup: it requires >=1400508

14.1-RELEASE(-p3) is 1401000

what is 14-STABLE?

that's what'l become 14.2 eventually

debdrup: yes

is 14-STABLE "yes"? :P

it's a source branch

i should hope i know what it is ;)

debdrup: OK :)

my understanding is that packages are built to be compatible with all 14 releases, and my question is whether that is a moving target once 14.0 goes EOL

packages are built to be compatible with the oldest-supported -RELEASE, and yes that's a moving target when one minor release gets EOL'd

that's paraphrased from freebsd.org/portmgr/policies_eol

debdrup: excellent, fingers crossed

drm-kmod ports are a special case, because they're so dependent on LKPI though

which is why when there's multiple minor versions supported, the newer ones often require you to build the port locally with /usr/src populated with a tree that matches your version

and that's not a simple thing to solve, as it turns out

debdrup: why doesn't WiFi have the same issue?

vedranm: it's possible that the LKPI-based drivers that'll be in ports, once bz@ finishes the work, will have the same issus

hm, is the problem with drm-kmod that you can't use a version build on 14.0 on 14.1? as I understood the description, that drm-61-kmod uses stuff not present on 14.0, so you can only build drm-519-kmod, but still use it on 14.1

nimaje: correct

debdrup thank you!

If I just want to manage jails and no VMs, is cbsd overkill? I never really used cbsd, for now I mostly used bastille.

convince me to come back pls

btw how is wayland support these days

Wayland sucks

Boom, you're convinced

i ain't trying wayland on any OS until it gets its shit together & has as many DE options as X11

systemd for x11

Hmm, I went directly for Wayland this time around. And I haven't been dissapointed with the stability on FreeBSD. I have however a pretty simple setup with just sway basically.

ibs: What graphics hardware?

cd /etc

craigger: Built-in Intel UHD Graphics 620

ibs: thanks!

mikewilzn: I imagine there are better places for your comedy than #freebsd

It wasn't comedy :)

No, you're right, it wasn't funny. ;)

Good because it was meant to be taken seriously :)

Well, trolling isn't appreciated in here either.

It wasn't a troll either

Sure seemed like it.

It's also exactly what a troll would say.. ;)

found bug in 14.1-RELEASE - llvm's csetjmp C++ header gripes about setjmp.h causing certain pports to fail to build. Not sure if fixed in newer source (I saw no indication of that). bugs.freebsd.org/bugzilla/show_bug.cgi?id=281257

right now I am getting all of the packages built from ports that I need and don't really want to suspend the proces to fetch new source and rebuild (especially llvm build).

anyway affects graphics/inkscape and graphic/xaos - 'workaround' patches in bug report

looks like graphics libs associated with blender and inkscape are affected. did not really see this until I started building that kind of stuff

07:15 <gtlwuc> is there a terminal sequence that does something like -- given the terminal screen consist of byte sequence {line1, line2 . . . line23, line24}, and I ask for cursor position -- the response would include a byte-position in the stream and a number of bytes, to cover cases such as unicode grapheme clusters and cjkv ideographs?

CPR only provides row and column nums

which does not map quite well into bytes