00:11:30 <nicholaus04> Howdy, folks!
00:12:22 <vortexx> oh yes you weren't there.
00:12:33 <vortexx> nicholaus04: why not use the builtin openssh in Win11?
00:13:05 <nicholaus04> vortexx: Ah, good point. But PuTTY works as well, but thanks!
00:13:31 <nicholaus04> Hmm...
00:21:31 <nicholaus04> Howdy, again!
00:22:20 <nicholaus04> Now using Win11's implementation of OpenSSH as a SSH client. Host OS is still the same(FreeBSD).
00:46:54 <JustBleedFan> 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?
01:18:49 <nicholaus04> JustBleedFan: The funny thing about that, Tiny11 is running on 100% actual hardware.
01:19:14 <nicholaus04> So it's actually 2 seperate PCs, with different OSs.
01:21:00 <JustBleedFan> 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.
01:35:11 <nicholaus04> Not exactly, but yep.
01:54:53 <JustBleedFan> I have Tiny 10 on my Linux Mint laptop. Used it a few times for different things.
02:15:38 <CCFL_Man> i want to clone and expand an existing freebsd installation to a new drive
02:16:41 <CCFL_Man> what is the best way if the old drive has bad blocks
02:23:00 <CCFL_Man> https://unix.stackexchange.com/questions/313832/how-to-clone-and-extend-to-new-disk-in-freebsd <--this looks pretty sound
02:34:28 <mjp> i would do a fresh install (using ZFS) and restore a known good copy of the data on the new instance
07:20:19 <antranigv> mornings
07:20:31 <antranigv> does anyone know how to use VALE if I want to expose my VMs to the outside world?
07:20:51 <antranigv> I tried using netgraph, but I can't get past 5Gbps
07:30:32 <tercaL> antranigv: How did you test the speed?
07:31:11 <antranigv> tercaL iperf3. I can get 10Gbps between two jails on NetGraph, but not on VMs. Maybe a tuning issue?
07:31:19 <antranigv> wanted to check VALE as well, haven't used it before.
07:31:23 <vorteckz> np[therealvorteckz⊙lf] - Lithe - Numb
07:31:27 <vorteckz> wrong channel sorry
09:38:16 <Pionat> 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 ?
09:48:27 <vedranm> 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?
09:57:03 <erk> Pionat: Your best bet is probably to find a tag in ports and build everything yourself.
09:58:14 <erk> Pionat: For example with git you can check out this tag: https://github.com/freebsd/freebsd-ports/tree/release/11.2.0
10:02:46 <Pionat> erk: thanks
10:21:17 <nimaje> vedranm: well, drm-kmod is just a meta port choosing the real version depending on the build host, the condition ${OSVERSION} >= 1400508 (https://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
10:21:19 <nimaje> (you may have to set PORTSDIR if you don't have it at /usr/ports/)
11:14:01 <Pionat> erk: Yes, the software that I want to install on this old 11.2 system was included in freebsd repo,
11:20:52 <Pionat> 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)
11:22:29 <Pionat> erk: obviously I need to download the source code for the software (and right version), finding that isn't hard
11:22:42 <erk> Pionat: The handbook has a section on it and as far as I can tell it should fit with the older version: https://docs.freebsd.org/en/books/handbook/ports/#_installing_ports
11:25:45 <Pionat> erk: thanks
11:34:35 <debdrup> vedranm: if changes to the LKPI that drm-kmod ports use have been changed in 14-STABLE, maybe?
11:36:23 <debdrup> Pionat: freebsd can't provide binary packages for old versions; we tried, and we ran out of space.
11:43:44 <debdrup> antranigv: there was some (GSoC?) work back in 2015 on ptnetmap involving vale and bhyve, but I don't know the status of it
11:48:19 <debdrup> antranigv: you can also have a look at https://www.freshports.org/net/vether-kmod
11:49:59 <debdrup> valectl has the -h switch to attach things at multiple ends, which i think is the crucial things
11:50:16 <debdrup> s/s$//
11:52:04 <debdrup> that's all i remember at present, though
12:34:45 <vedranm> nimaje: yes, I know I can build it from source already on 14.1-RELEASE
12:35:07 <vedranm> debdrup: it requires >=1400508
12:35:29 <vedranm> 14.1-RELEASE(-p3) is 1401000
12:35:57 <debdrup> what is 14-STABLE?
12:36:04 <debdrup> that's what'l become 14.2 eventually
12:36:09 <vedranm> debdrup: yes
12:36:22 <debdrup> is 14-STABLE "yes"? :P
12:36:46 <vedranm> it's a source branch
12:37:14 <debdrup> i should hope i know what it is ;)
12:37:28 <vedranm> debdrup: OK :)
12:38:06 <vedranm> 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
12:38:55 <debdrup> 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
12:39:43 <debdrup> that's paraphrased from https://www.freebsd.org/portmgr/policies_eol/
12:40:16 <vedranm> debdrup: excellent, fingers crossed
12:40:49 <debdrup> drm-kmod ports are a special case, because they're so dependent on LKPI though
12:41:34 <debdrup> 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
12:41:54 <debdrup> and that's not a simple thing to solve, as it turns out
12:43:40 <vedranm> debdrup: why doesn't WiFi have the same issue?
13:31:52 <debdrup> vedranm: it's possible that the LKPI-based drivers that'll be in ports, once bz@ finishes the work, will have the same issus
13:36:40 <nimaje> 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
14:09:41 <vedranm> nimaje: correct
14:22:55 <antranigv> debdrup thank you!
14:28:31 <souji> If I just want to manage jails and no VMs, is cbsd overkill? I never really used cbsd, for now I mostly used bastille.
18:17:19 <Success> convince me to come back pls
18:17:33 <Success> btw how is wayland support these days
18:19:59 <mikewilzn> Wayland sucks
18:20:03 <mikewilzn> Boom, you're convinced
18:32:42 <ZedHedTed> i ain't trying wayland on any OS until it gets its shit together & has as many DE options as X11
19:01:38 <Demosthenex> systemd for x11
19:10:57 <ibs> 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.
19:19:18 <craigger> ibs:  What graphics hardware?
19:27:29 <craigger> cd /etc
19:30:45 <ibs> craigger: Built-in Intel UHD Graphics 620
20:45:29 <craigger> ibs: thanks!
20:47:06 <debdrup> mikewilzn: I imagine there are better places for your comedy than #freebsd
20:47:49 <mikewilzn> It wasn't comedy :)
20:56:31 <debdrup> No, you're right, it wasn't funny. ;)
20:57:21 <mikewilzn> Good because it was meant to be taken seriously :)
20:57:55 <debdrup> Well, trolling isn't appreciated in here either.
20:58:19 <mikewilzn> It wasn't a troll either
20:58:29 <debdrup> Sure seemed like it.
21:04:32 <debdrup> It's also exactly what a troll would say.. ;)
22:06:15 <shbrngdo> 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).  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281257
22:07:51 <shbrngdo> 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).
22:08:58 <shbrngdo> anyway affects graphics/inkscape and graphic/xaos - 'workaround' patches in bug report
22:57:55 <shbrngdo> looks like graphics libs associated with blender and inkscape are affected.  did not really see this until I started building that kind of stuff
23:17:50 <gtlwuc> 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?
23:19:10 <gtlwuc> CPR only provides row and column nums
23:20:01 <gtlwuc> which does not map quite well into bytes