00:13:41 How big is the file? Dropbox can produce public download links. 00:14:05 If it's under 2 GB, a free dropbox account will suffice. Proton Drive will allow up to 5 GB if you do a few things (making a public download link is one of those things). 00:15:53 TommyC: nimaje suggested 0x0.st which worked fine. 00:16:17 TommyC: https://0x0.st/Po2U.zip if you want to try it out. This is for 14.3 00:16:18 Never heard of that 0x0.st, will have to check it out. 00:18:22 to share here too what I shared in #supertux > hm, that binary depends on libfmt.so.11, while I have libfmt.so.12, probably because I use the main branch of the ports tree and not the quarterly branch 00:19:12 I thought we link things statically. 00:22:15 nimaje: Can you have libfmt 11 installed in addition to 12? 00:22:44 I will try with LD_LIBMAP=libfmt.so.11=libfmt.so.12 in a moment, but I have to install physfs first 00:23:23 ah okay 00:25:06 works with that LD_LIBMAP until I try to enter a level, then I get Undefined symbol "_ZN3fmt3v117vformatENS0_17basic_string_viewIcEENS0_17basic_format_argsINS0_7contextEEE", probably a ABI diffrence in libfmt.so.11 and libfmt.so.12 00:26:46 maybe 00:27:47 But at least it runs. 00:33:12 nimaje: What branch do most people use? Also, does that mean that whenever freebsd updates, SuperTux will fail to run? 00:33:55 I guess we need to link libfmt statically 00:40:14 you can't really ship binaries for freebsd that depend on ports, it just doesn't work. ports has frequent or rolling updates so it's only a matter of when it'll break, not if 00:42:46 Alright. 00:43:28 ivy: So how do we get the correct version of libfmt bundled? 00:43:30 I would guess most users use the supertux package so you only need to build your on binary for testing 00:45:27 yeah, assuming this is open source software the right solution is to just have it in ports, so people can install it the normal way. if you do really want to ship a binary... iirc, fmt lets you embed it into your projet fairly easily with cmake? so that would be one option 00:47:10 Well, this is mostly for nightly builds. 00:47:42 we do also have std::format on all supported branches, in case that lets you avoid fmt entirely 00:47:50 (compiler updates are backported, we're on llvm 19 right now) 00:50:00 well, there is more than fmt that can/will break, but for nightlies I guess just using quarterly should be ok 00:50:26 alright 00:53:10 and do we really still need supertux 0.1.3 in ports? hm, probably I should make a patch moving games/supertux2 to games/supertux and put that in a PR 00:55:05 nimaje: I mean, it's milestone 1 00:55:15 Drastically different from milestone 2 01:16:55 nimaje: for a video game, maybe it makes sense to just have 1/2/etc ports 01:17:08 since the old version doesn't become obsolete in the way an old application usually does 06:32:43 pkubaj_, hi! Can I update sysutils/cpuid to new version 20250513? https://www.etallen.com/cpuid.html 06:33:44 Patch is trivial. Tested on live system (build and run) and in poudriere 14.3 amd64. 08:34:51 VVD: i already have it committed, just need to push 08:36:17 VVD: ok, pushed 10:38:45 would you guys say docker has finally gotten close, reached or even surpassed jails? i know it's a convoluted question with a possible convoluted answer 10:38:59 but if it has a simple answer i definitely would like to hear it 10:40:19 or in this case read it 10:42:06 people who actually hear their own voices while reading can still say they're hearing it though. Nuances 10:46:53 Jails and containers are apples & oranges. For the part they overlap, I'd say I consider jails to be better and easier. For the part they don't there is no point comparing. 11:19:47 gt: Alver: jails are apples, containers are some kind of mutated fruit that developed several arms and legs and some sentience 11:20:47 gt: but containers do actually run fairly easy and well on FreeBSD 11:21:42 * SKull uses them for non persistent stuff 11:21:57 but for actual service isolation that runs persistently, i use jails 12:20:51 jails are containers tho, just generally used to run an entire os environment vs a single process; though doing either is possible. running an entire os environment in docker is frowned upon from my understanding. 12:27:47 Docker containers are too ephemeral for serious business, and adding persistence takes special effort. 12:28:08 pkubaj_, thanks! 12:37:33 using bluetooth tethering right now... it's really showing me why mosh is so important 12:38:08 i really wish there were more tools for a terminal that were tui based just in case i'm ever stuck on mars with low bandwidth 13:56:30 mosh is great 14:13:43 it's very handy, I use it daily 14:14:29 greatly appreciate that the installation process is basically just "have existing SSH access, and install the mosh binary on client and server" 15:43:07 hello. I have a rhel server i want to convert to a bhyve virtual machine. It has a 1TB physical disk, but is only using 16GB of space right now. I don't have enough free space on the freebsd server to make a full 1TB disk image. Is there a way to generate a sparse image from the disk? 15:44:09 (I also have a windows desktop that will need the same treatment, but I'll do that later. I never look forward to windows :( ) 15:55:23 gp5st: find a p2v tool that does sparse. dd can to it with the option sparse. 15:58:51 rtprio, oh, i didn't realize that was there. thanks! 15:59:43 not sure if you're going to dd live from rhel or slap the disk in an enclosure and dd it, but both dd's should have it 16:00:08 there probably are a couple of dedicated tools to do it which might have more features 16:08:08 I was going to dd it with the system off. Thinking of doing it on a live system gives me stomach pains. (I actually have 0 reasons, but it _feels_ wrong. Maybe I'm just too old.) 16:10:38 if you're bringing the whole thing down you might think about surgically resizing the disk as part of the migratoin 16:14:17 hmm, that's not a bad idea. The users of this aren't going to store a ton of stuff on here. 16:17:59 ah, they set this up as xfs which doesn't support shrinking 18:02:25 gp5st, When I have needed to do this I have created a new image of the smaller size that I could support but large enough to hold all of the data, cloning the partition table with a smaller size file system, then copied the previous system to the new using rsync with -a --acls --xattrs --hard-links. 18:03:28 I am not a bhyve expert, which is why I lurk here to learn more, but have done that with KVM systems. I would be anxious about using a sparse file system because it has the potential to balloon in size during normal system operation. 18:08:14 but it wouldn't balloon more than the specified size 18:09:19 rwp: rsync or dump/restore that is more what i meant with surgically resizing, yep. not shrinking the partition 18:13:05 I like xfs, it is a good file system, but it is not so flexible with resizing. Increasing the size it is good to increase in multiples of the original size. But decreasing is not supported. 18:14:24 For your MS-Windows task that you mentioned though it is possible to resize smaller the file system. That path is well tested and supported. Shrink it and then binary copy the raw file system. I have done that recently to create a VM and it works well. 18:21:37 For rsync I should mention that -H hard-link detection and copy might need HUGE memory resources. Sometimes it's necessary to "sneak up on it" by copying without hard links being maintained and then fixing those up on a second pass across the data. It all depends upon the system. Just a heads up that it might be a problem though. 18:23:52 In order to copy hardlinks it is necessary to keep a mapping of all files inode numbers with link count greater than 1 (indicating that they are hard linked somewhere) and then duplicating that on the destination. If there are a lot of hardlinked files, such as might happen in a backup situation where the backup uses hardlinks to deduplicate, then this can use a lot of memory. 19:29:32 Thank you rwp and rtprio 20:14:52 is something wrong with opengist in FreeBSD 15.0-RELEASE? I installed the port and it works manually, but the rc.d service doesn't start with default settings (service opengist start -> starting opengist -> service opengist status -> opengist is not running) 20:23:12 swee: did you enable the service too? or onestart? 20:23:24 I enabled it with sysrc yeah 20:24:10 then i would suspect there's some config error preventing it from starting; not every app starts with default settings 20:27:21 yep, from what I'm seeing it looks like I have to do some extra steps, opengist is getting a panic according to /var/log/daemon.log