00:17:39 I have one with that chipset too. 00:17:48 Thanks for all the wifi work. 00:21:57 so, I was just experimenting with the `zfs jail' feature. is the intended method for exposing a jailed dataset to a jail via `jail.conf' doing something like `exec.created += "/sbin/zfs jail ${name} data/set";'? This seems to work without trouble, but I couldn't really find any documentation on any standard way to do this. 00:44:30 https://vermaden.wordpress.com/2025/10/20/brave-new-pkgbase-world/ 00:44:34 oh looks like it is controversial 00:44:50 so there are others which think pkgbase is a steaming piece of shit too? :P 00:50:45 it looks like the apach24 userdir module is not working in 15.0 00:50:50 apache24* 00:52:16 specialbomb: I think all that's needed is "you need to set jailed=on for dataset" https://cgit.freebsd.org/src/commit/?id=e0dfe185cbca 00:52:32 Looking forward to trying that one out. 00:53:20 oh wsky is here 00:53:35 do you pronounce your nick w-sky or wisky? 00:53:44 it's short for wintersky 00:53:51 oh you already told me that 00:53:53 anyone can confirm my bug? 00:53:56 I still read your nick as "wisky" 00:54:02 it's ok 00:54:09 no im not an alcoholic :P 00:54:12 although beer tastes good 00:54:13 sounds like you need a drink polarian 00:54:22 rtj: already had a wheat beer earlier 00:54:36 Nice, just coffee here. 00:55:04 wsky: cant help with apache though sorry, and sorry for derailing the convo 00:55:14 although I would ask why apache? 00:55:18 nginx is faster and more efficient 00:55:30 No 15 installs here yet. 00:56:04 is there somewhere that shows patch releases? like a list of them? 00:56:18 The announce mailing list. 00:56:59 ok i got it it was just disabled in httpd-userdir.conf 00:57:27 Macer: check the website as well will tell you 00:57:30 freebsd.org 00:57:44 the homepage has a list of security patches and erratas 00:58:05 rtj: yeah, that part is pretty obvious imo, I was more having trouble with "okay, so now how to I automate jails having datasets exposed to them and mounted" 00:58:25 https://lists.freebsd.org/subscription/freebsd-announce 00:58:29 that? 00:58:36 polarian: oh it does? hm. 00:59:01 Macer: and yes that mailing list is the correct one 00:59:18 whenever you get a security advistory (SA) which are also showed on freebsd.org there is an update 00:59:29 however they dont always announce the erratas iirc 00:59:48 specialbomb: Ok had no idea about context. Ty polarian, nice to see you today. 01:00:03 that commit you sent was actually very useful, ty 01:00:08 > The Reg FOSS desk spoke to an OpenBSD developer recently, who thought the change was rash and profoundly counter to established BSD practice. ~ https://www.theregister.com/2025/12/05/freebsd_15 01:00:13 I agree! 01:00:32 FreeLinux not FreeBSD! 01:01:52 It's one of my favorite things how it's seprate. I undersand things change. I will greatly miss it though. 01:02:25 polarian: thanks. 01:03:01 rtj: im protesting, I will compile from source insteasd 01:03:13 and if they remove that, I guess I will need to patch it back in :) 01:03:19 I truly havent been around freebsd long enough to give any opinion on pkgbase. I think definitely benefit from not needing to do delta based updates, but I also think there should be special management for base packages instead of treating them like 3rd party. I hope thats what is decided as time goes on 01:03:21 at some point i need to sort out how to update base with pkg too. i guess that's going to be a thing. 01:03:43 although i was more a fan of keeping pkg for packages and base with freebsd-update 01:04:04 I can't really say anything because I've yet to try it. I'm just a creature of habit though. 01:05:41 vortexx: you are a OpenBSD + FreeBSD user, thoughts on pkgbase 01:06:09 also.. i see there is kmods_quarterly_${VERSION_MINOR} ... is there a latest version of that where quarterly can be changed to latest? 01:06:38 similar to pkg+https://pkg.FreeBSD.org/${ABI}/quarterly being changed to latest 01:07:37 next freebsd will be adopting rust 01:08:16 pkgbase is a big mistake, it disappoints me to see some of the major freebsd devs so passionate about the idea of turning freebsd into Linux 01:08:26 speak of metapackages like its innovative 01:08:39 Linux been doing this shit for decades and it always ends up with the same issue, dependency hell! 01:10:14 probably not so much for the kernel and base utilities 01:10:49 So... the parts are distributed as pieces but that doesn't mean the system isn't cohesive or piecemeal like Linux 01:10:54 thats what im thinking, like if the base system is fully maintained by freebsd as it always has been, I really dont see any issue with it in the regards of "dependency issues" 01:11:13 i'm just more a fan of freebsd-update and pkg being separate because then freebsd-update is a bit more static and independent of anything else 01:11:45 Macer: and so then, what im saying is that there should be very clear and separate management of base packages and third party packages 01:12:05 i'd be worried about pkg somehow breaking pkg or breaking how it can update base somehow... something that you'd probably not run into just keeping freebsd-update 01:12:43 i mean i'm sure there will be tons of testing to prevent that .. but freebsd-update was tested and true :) 01:13:19 id say theres always fear in a new tool. do you trust who makes the tool, is the more important factor here in my opinion 01:14:14 i mean i guess i can understand why they want to do it because then you can keep everything in one place instead of maintaining two things to do something one can do 01:14:22 kenrap: exactly... 01:14:39 took the benefits of BSD and ran them through a shreadder, and then doused them in petrol and fucking burnt them 01:15:37 like wtf is the point of pkgbase 01:15:46 "oh look I can remove this core library" woah 01:15:54 you know what you can also do? remove it from the source and compile your own custom kernel 01:16:03 you know, hacking the OS? 01:16:40 the point is to make one ring to control them all :) 01:17:17 Macer: eh... bad comparison. considering how LOTR goes in that regard :D 01:17:23 going back to talking about linux. i mean i don't really have many issues in something like debian which just uses apt to do essentially the same thing. or at least i've never experienced a wtf moment doing it 01:18:09 but i did like how freebsd kept it separate so i know... this is for this.. and that is for that 01:18:28 specialbomb: you mean mount doom went boom? :p 01:18:58 freebsd is mordor, the ring is pkgbase dropping into mount doom 01:19:00 :) 01:19:29 Macer: I might be young, but I have played with both OS enough to know that the Linux way is inferior 01:19:43 the control you have from the separation of base from ports is amazing 01:19:55 my question would have been when is fbsd moving to systemd :) 01:20:01 the fact your base system is one complete component is a great feature 01:20:20 Macer: that would be fork worthy 01:20:23 tbh pkgbase is fork worthy 01:20:38 I get that delta updates suck, but this is not the solution 01:24:32 polarian: im curious since you dont think this is a viable solution, what WOULD be a viable solution to this? 01:24:46 what would be ideal, in your perspective? 01:25:19 specialbomb: leaving shit how it is :) 01:25:34 maybe rewriting freebsd-update to be more efficient 01:25:58 freebsd-rustdate exists which is meant to take sub-minute to update a system to a new release (from what I hear at eurobsdcon) instead of 10 mins 01:26:24 like if you must pkg it, cant it be one big package 01:26:31 one complete redistributable 01:26:33 one complete system 01:28:13 hello I need help to get my server back online 01:28:18 freebsd server back online 01:28:48 sixpiece what happened? 01:29:26 cat tripped over your cables? 01:30:29 it was the squirels 01:30:46 ah right 01:32:03 Alvin? 01:33:39 Alvin was a chipmunk. 01:34:24 the floor is littered with woodchips and apple cores and hulls of acorns 01:35:23 theres a chattering sound... because they were squirrels! Real squirrels! 01:36:03 Macer you're right, same family though 01:36:21 https://lists.freebsd.org/archives/freebsd-pkgbase/2025-July/000598.html 01:36:39 good to know we are using "it works on linux, so we should do the same" as justification 01:36:43 BSD predates Linux 01:37:09 Linux has only been taken seriously in the last decade or two 01:43:24 hmmm... I dont necessarily agree with that. It's less that "it works on linux", its more that "it works, and it just happens to be on linux distros". its not a bad design decision when handled properly 01:45:50 i don't mind having 2 different utilities at all, i would never perform pkgbase + pkg actions together at the same time either so don't see much benefit in having a single command 01:46:22 oh, I do agree with that. I was disagreeing with polarian :p 01:46:45 everything roger said there was very sensible 01:47:32 s2r basically I was trying to upgrade to freebsd 15.0 and I was extremely tired also doing the installation on my laptop as well and I made a change to one of the files absent mindedly and then it might have been ok but I was scared I did some damage so I used a backup and a snapshot and reversed the change then ever since the internet hasn't been working correctly and lots of issues getting it 01:47:33 connected 01:48:26 I still want to perform the update and that's the situation but I'm like right now not even up and running at all , it was simple stuff that made it pingable and internet out but I still can't connect by ssh I have to login to my cloud vps provider and go in via their novnc connection 01:49:26 sixpiece so you went to a previous snapshot? Did you create a boot environment prior to pkgbase upgrade? 01:49:34 I had a lot of firewall rules because I did sendmail on the server to send out emails and there's a open dkim that required some rules and I sort of commented a few out very quickly hoping to get the firewall running so I have some level of protection maybe I should stop it completely I am not sure for now what to do 01:49:44 specialbomb: disagree with me all you like 01:49:55 I want my base system 01:49:58 it does an automatic 2 times per day backups and I just went on a backup that was 10 hours old 01:50:00 no metapackage 01:50:07 no ports updates with base updates 01:50:09 just my base 01:50:11 as a single entity 01:50:15 figuring that it was largely the weekend and not much happened in terms of development 01:50:33 polarian: no disrespect at all, I simply just disagree. 01:50:42 polarian can't you set all that on the repos to active: no? 01:51:04 it's automatically done by my cloud service provider I just requested the backup then it gave a snapshot then I used the snapshot sorry I couldn't answer your question further than that 01:51:05 specialbomb: ik :) 01:51:12 sixpiece and from that backup you have missing files? 01:51:13 <3 01:51:14 s2r: ? 01:51:54 I'm not sure from the backup I am not able to ssh into the connection for some reason ipfw initially was on that blocked all traffic now I turned it off I was using pf and have some rules I turned that on 01:51:58 polarian if you don;t want to upgrade everything set it to no on the /usr/local/etc/pkg/repo/FreeBSD-base.conf 01:52:17 I could try turning it off and then seeing if that works and then doing the upgrade 01:52:35 sixpiece where is the server located, have you got access to the console? What services are running? 01:53:35 I am running apache, mysql, different things like icecast and stuff like that even an irc server , php and a few things that were failed experiments like named server, opendkim is a service, sendmail, etc.. 01:53:45 sixpiece I ran into some issues while doing pkgbase upgrade mostly related to fingerprints on the .conf file. I couldn't follow step by step the upgrade process from the handbook. 01:54:29 I turned off the firewall and I still can't get into the ssh 01:54:41 sixpiece Is mysql connected to thte internet or listens localhost only? 01:54:43 yes I used granite the ai tool as well as the manual and that helped a lot 01:54:55 normally I just use the manual but started with these ai tools 01:55:04 I can try 01:55:22 mysql failed maybe it's not on 01:55:36 sixpiece I don't remember exactly but couldn't you spawn a shell from mysql if you have the appropiate rights? 01:55:55 it's on but I cannot access it oh right I was sshing into mysql 01:56:33 sixpiece from which version were you upgrading? 01:56:34 I was trying to be conversative but I guess that's my thing I need to do to be balanced centrist 01:56:40 14.3 01:57:07 for some reason maybe it's the snapshot that brought me back in time 01:57:10 maybe I screwed up 01:58:05 sixpiece Have you created a boot environment prior to the upgrade? 01:58:16 s2r: like I will pkgbasify my system lol 01:58:27 Here is a question. For those that really hate pkgbase, what's your "Plan B" for when FreeBSD meets its inevitable demise of pkgbase? :) 01:59:15 which kind of sucks cause I lost months of work by this stupid mistake I was tired 01:59:21 makeworld, makekernel, installkernel (reboot), installworld, etcupdate (reboot) 01:59:30 I am not sure what you mean boot environment? 01:59:36 polarian pkgbase lets you make your system reproducible like the requirements.txt in python 01:59:37 and if thats removed 01:59:39 idk 01:59:48 sixpiece: do you use zfs on root? 01:59:50 I have one from 24 hours ago but I think it was still lost at that time 02:00:07 you should be aware of boot environments if so 02:00:11 sixpiece something like, bectl create 15.0-RELEASE 02:00:16 no it's a cloud instance that they make for me with kvm 02:00:34 in any case I can always fuck off to openbsd for good :P 02:00:50 sixpiece if it's a cloud instance, can't you access the console? 02:00:51 but then wheres the fun in that, I wouldnt be able to moan about pkgbase then 02:01:03 I might get lucky and hopefully the backup is from when I did the work 24 hours ago ... 02:01:23 it's from over a year ago 02:01:54 sixpiece ah ok. so no zfs. 02:02:16 I'll be really lucky but I think it's possible 02:03:11 sixpiece So right now you are trying to revert everything to a known state prior to the failed upgrade, right? 02:03:45 wow just got very lucky I think 02:04:28 it wasn't really a failed upgrade as much as I thought it was but I did make a minor mistake or two deleting configuration I shouldn't have when I was trying to make a merge conflict work 02:09:51 wow it's back I am going to do the upgrade now if I have any issues I will let you know thank you very much sorry it wasn't supposed to be this easy lol 02:10:04 good thing I checked it before that backup got overridden 02:15:52 zip: just submit a PR 02:16:17 kenrap: i have no plan b as despite the hate towards pkgbase you can still manually compile the system as well as ports 02:16:23 kenrap: that isnt going any where 02:16:39 so i guess my plan b is compile form src 02:16:55 cpet: true, src building is the safest option. 02:16:57 sixpiece: you can create be's 02:17:17 kenrap: 15.0 is a .0 most if not .0's are buggy 02:17:30 i have yet to see a .0 that doesnt have some issues 02:18:19 but i dont do any weird things so my brakage is different than yours 02:19:18 It really seems like this .0 has been having a lot more issues than other prior .0 releases though. I think kevans made a good point about the lack of testing in 15.0. 02:19:51 you have not used 5.0 02:20:15 5.x was horrible heh 02:22:48 Got another question, what happens if src building because pkgbasified? :) 02:23:22 *becomes 02:23:32 the whole point in finally releasing pkgbase is to get more use out of it 02:23:55 due to the nature of current i dont think that would be an issue 02:24:10 in theory openbsd recomends you sysupgrade to a snapshot rather build from src anyways 02:24:10 sixpiece are you upgrading right now? 02:25:16 kenrap: with ccache it takes me 28 minutes to compile kernel and world, not everyone has a system like mine so 02:25:22 a lot of people wont bother to compile 02:26:04 s2r yes I am upgrading right now 02:26:15 yeah... its 2025 and i have a family, i'm not compiling my operating system lol 02:26:27 Yeah, pkgbase really makes -current snapshot upgrades accessible. 02:26:35 kenrap: i think the real issue is when a new release comes in people rush to upgrade 02:26:59 kenrap: some goes for seueity issues like russia really want little timmys gaming system and collection of furbies in bmp format 02:27:52 kenrap: the humour i get is when people use something that litteirly says tech release 02:27:58 which meaning its still not production ready 02:28:05 then people like yourself bitch about it :D 02:28:31 I don't bitch because I use -current :) 02:29:19 the only reason i use current if if a specific mission ciritical piece of HW is supported in it 02:29:29 other then that i dont see a point seeing how this desktop is my daily driver 02:31:30 kenrap: the ML's are interesting too such as a freebsd commiter complaiing about current being broken for 9 hours 02:31:33 heh 02:32:43 I just learn to make BEs and snapshots to be able to revert to an older build and stay there until the waves settle down for a newer build. :) 02:34:44 I don't follow the MLs much either. 02:35:56 I should look at the mailing lists 02:41:23 JetpackJackson: it gets pretty bad when you remind a commiter about jenkins 02:41:46 but then again my first port was fceu 02:42:03 not searching first I manage to port somethingthat was already ported :P 02:44:37 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=54297 02:44:43 that was a funny day 02:45:37 kenrap: i just boot kernel.old 02:45:46 i have yet to use be 02:45:48 s 02:46:01 but then again i dont fiddle with my system as much as I should 02:48:44 BEs are easy to make and use. I suggest using a date command for using timestamps to name them too. 02:49:05 if you need to have a lot of BE's think the issue is the user not the OS 02:49:05 heh 02:50:11 cpet: lol 02:50:38 I don't make a lot of them, just a couple at most. I just don't think "backup${N}" is very descriptive and doesn't scale with scripting. 02:51:41 i name my backups backup1 and server-backup 02:51:49 how more descriptive do you need them to be 02:52:12 back-how-i-screwed-up-my-config-12-Dec-25-022321 02:52:14 ? 02:53:07 I'm not trying to argue with you. I thought it was a nice suggestion. Name your BEs however you want. 02:54:00 backup-kenrap-complains-alot-about-fbsd-datestamp 02:54:28 cpet-now-goes-into-my-ignore-list-kthxbye 02:54:39 i dont need to know if you ignore me or not 02:54:58 you don't have to act like jerk either :) 02:55:16 aww cute thought i was on your ignore list 03:01:36 Where can I check where the command named dialog has gone? 03:02:10 Use "which dialog" 03:02:57 cpet: backup-preconfigchange-{date} 03:03:09 V_PauAmma_V I can't find it. I did a find / -name dialog -print and the only place is found is inside a 14.3 jail. I'm running 15.0 03:03:42 tbf i don't think 15.0 was any less tested than any other release, people just don't take advantage of the time we offer for testing this stuff in general for any release 03:03:45 (still in scrollback) 03:04:23 > if you need to have a lot of BE's think the issue is the user not the OS 03:04:31 everyone has different risk tolerance 03:06:19 cpet: ideally you name these things with some idea of *why* you're creating one in the first place, but the exact sense kind of depends on how you model these things 03:07:05 i mean, you can create a BE and operate on that (let's call it 15.x), or create a BE as a backup (let's call it pre-15.x); in any event, they offer more value than just rollback, whether the majority of people take advantage of that or not 03:18:10 s2r, did you install your 15.0 using the pkg installer? 03:19:32 V_PauAmma_V upgraded via pkgbase 03:21:29 just letting you know thank you freebsd 15 seems like it was successfully upgrading on the last leg with post installation tasks 03:21:58 sixpiece: awesome! :) 03:22:21 sixpiece can you check if you have the dialog program? which dialog 03:24:01 V_PauAmma_V I have checked in another upgraded installation and is missing there too. 03:25:55 Hmm. Not in the tree anymore. 03:26:10 * V_PauAmma_V dives into the 15.0 relnotes. 03:29:04 Ah. From https://www.freebsd.org/releases/15.0R/relnotes/#userland-programs: "The bsdconfig(8) and bsdinstall(8) utilities now use bsddialog(1) instead of GNU dialog." 03:29:33 So I suspect dialog was shown the door in the process. 03:30:10 V_PauAmma_V so any pkg depending on it should fix its dependency. Thanks! 03:33:20 V_PauAmma_V how can I check if a program is on the tree? 03:34:35 s2r command not found 03:41:14 sorry s2r for long delays 03:41:20 s2r, either of 2 ways: if you installed sources on your host or VM, "find /usr/src -name dialog -print" (or whichever name you want to know about). If you didn't, point your browser to https://cgit.freebsd.org/src, switch to the branch for your FreeBSD install (so releng/15.0 in your case), click on "tree" in the bar near the top, then look into the appropriate directory (bin, sbin, usr.bin, or 03:41:26 usr.sbin). If you don't find it there, check the contrib directory as well. 03:41:32 tired and speaking to a friend on the phone multitasking 04:06:56 thank you again good night 04:07:06 s2r 04:08:03 kevans: i was giving kenrap a bad time 04:08:36 hello s2r I am interested to learn the thing you were speaking of and I always appreciate the great support of this channel good night thank you 04:08:57 every thing is miraculously working as good as I need it for now and my systems are on freebsd 15 04:09:01 later 07:38:59 Plasma Wayland is a pretty awesome experience 07:57:38 i like wayland. i do not like X.org. finally i can make my system to be free of any X.org traces at all. port's allows this. it was little bit harder few years ago. but qith qt6 it is finally possible as they allows building without X. 07:57:57 there are some quirks though, which can be sorted/patched. 08:10:34 angry_vincent: it seems like you're almost there given the current limitations with the USE_XORG knob. 08:26:01 polarian: I haven't looked at it, I'm on 14.3 for now. I do recall it's replacing freebsd-update which saddens me 08:28:54 hello, i have downloaded the freebsd iso (the big one) and installed it in virtualbox. After the installation, no gcc. I tried to install it via pkg, but sudo is not installed, and su refuses to succeed, and pkg is not there too 08:29:00 is there something to do during installation to have sudo and pkg already installed ? 08:38:09 ›doas‹ instead of ›sudo‹ may be the way 08:39:44 mdo(1) and mac_do(4) is another option and native to FreeBSD. 08:39:45 vtorri: `su -` then use the password for the user `root` (not your password) 08:47:33 ridcully : result : "su: Sorry" 08:47:38 trying the other ways 08:48:45 SomeVisitor: doas is not found 08:49:02 doas needs to be installed. same as sudo 08:49:55 can't you remeber your root password? 08:50:02 mdo : not enough permission 08:50:19 there is no pkg bin in /usr/bin 08:50:28 its in /usr/sbin 08:50:36 and you need root permissions to install anything 08:50:42 i know my su password 08:50:56 but i can't even get to write my password 08:51:06 su fails before 08:51:24 are you member of wheel? 08:51:30 I wonder if it's a pam issue? 08:51:44 tsoome_ what ? 08:51:51 use `id` with your current user, and check if it's in `wheel` 08:52:36 from su(1): In particular, by default only users in the “wheel” group can switch to UID 0 (“root”). 08:53:19 since you run in a vm: switch to another terminal and log in as user root there 08:53:25 ridcully everything in vtorri 08:54:05 You might want to download the memstick or iso image and boot into it, so you can chroot into your install and reset your root password 08:55:09 (Oh wait you already got one) 08:55:21 i'll reinstall again 08:55:21 booting into single mode is usually enough to change root passworx 08:55:33 it's not very long 08:55:37 Oh yeah, do what mzar said. 09:13:33 i'm reinstalling freebsd in VB 09:14:25 at the step : "Distribution sets" or "Tech preview" choice, what should I use ? 09:16:50 kenrap: it is an artificial thing, re USE_XORG. it is automatically appends RUN_DEPENDS for a given entry in USE_XORG ( which is in itself failproof approach - better install more than is needed ). However for purists it is an obstacle. There are complex or lesser understood dependencies. It can be treated specifically depending on what is the goal. I do not like excessive, unnessecary dependencies. But I trained by many years of 09:16:50 Gentoo. FreeBSD while allowing many things to be optional is little bit more conservative in configure options. 09:59:36 angry_vincent: gotcha 12:20:05 32.1T / 69.2T copied at 390M/s, 46.40% done, 1 days 03:42:38 to go so i guess about 2.5 days for me to expand my vdev 12:20:21 i guess later i'll find out if that is vdev dependent 12:20:39 i don't think zfs does any type of reflow if you add a new empty vdev to it 12:24:12 this weekend i'm going to dismantle my old 4TB x 12 pool after moving it to the pool i'm expanding. should be fun with zfs copying 12:58:52 it's nice to see that you are progressing Macer 14:11:16 Macer: you sure are having a hell of a time. makes me feel like I should actually be finding this failing drive in my disk shelf :P 14:12:28 Macer: if you are good with zfs send/receive please give me some working examples for my notes. I run into a lot of times I think it could be useful, but the documentation online is always way over my head. If I just "see" it in action though, I might be able to pick up on it 14:24:48 SponiX: what sort of issue do you have with send/recv? they are somewhat… very simple tools? 14:25:00 one produces a byte stream, the other consumes 14:25:16 like tar c -f - | tar x -f - 14:26:15 Remilia: can you give me a working example of doing it from machine1 to machine2 over a network? I'd like to be able to do it between my virtual machines, and also between my vms and a bare metal box too 14:29:35 SponiX: `zfs send -LRc zroot | mbuffer -q -s 128k -m 32M | ssh target-host 'mbuffer -s 128k -m 32M | zfs recv -Fdu targetpool'` 14:29:53 err 14:29:57 zroot@snapshot* 14:30:15 that's a full replication stream 14:30:43 incremental is adding -i with the previous snapshot to send arguments 14:31:18 so something like `zfs send -LRci zroot@backup-202511 zroot@backup202512` 14:31:34 but the previous snapshot has to exist on the target pool 14:32:20 Yeah, you say that is simple. But that still boggles my mind LOL. I will check back in with you the next time I have a situation that needs this ;) 14:32:21 you do not have to use ssh of course, can just netcat if you trust your network 14:32:44 you also do not need mbuffer, I use to to soften the inter-stream blows 14:32:53 I'm up for using any method that works. netcat might be a bit faster than SSH though 14:33:17 I use nc but I also do it over an IPsec tunnel 14:33:55 there's a bunch of howtos on the internet for this 14:33:58 Well, since these machines are all within my local network (NAT). the additional layers of security aren't needed IMHO 14:34:49 Remilia: I know there are, I've looked at a LOT of them. And haven't found any REAL WORLD examples that I can easily modify to make work in my setup 14:35:05 well the above is what I used many years ago 14:35:20 If I get one good working command, I will just add that to my notes, and pull it from there and modify it any time I need it 14:35:25 right now I have a more complicated one-liner because of mediawiki 14:35:52 well... that's where I pulled that line from 14:36:18 a 15 years old file with all sorts of one-liners I came up with 14:36:43 If I get this spare system built today and still have free time. I might look at doing a snapshot of a users home directory and pushing that from one vm to another 14:36:47 (including StrongSwan pki bs) 14:37:23 SponiX: you cannot do a snapshot of a home directory unless it is its own dataset 14:37:27 I have one user that doesn't want to move over to the new box because of the additional setup required. If I can clone their home from one vm to the other, that should eliminate any additional setup needed 14:37:41 you do not need zfs for that 14:37:52 Oh? 14:37:59 tar solved that issue back in 1970s 14:38:01 Guess I could just do "rsync" 14:38:24 I would not call rsync 'just do' because it's more complicated than zfs 14:38:40 the easiest way is `tar` seriously 14:38:57 well for me rsync between boxes is what I normally use for any backup routines. So that is "simple" :P 14:39:37 The one that is "simple" is the one you already know LOL 14:40:17 SponiX: `tar cJf homedir.txz /usr/home/username` 14:40:33 though that would include path prefix 14:41:39 `tar cJf homedir.txz -C /usr/home username` will chdir to /usr/home so your archive will only have username as the directory inside 14:42:03 then on the target system `tar xf homedir.txz -C /usr/home` if the username is the same 14:42:15 might need to fix owner/group after that if they differ 14:43:07 SponiX: to reiterate, to *only* replicate a single directory and underlying stuff with zfs send, you *have* to have that directory as a separate zfs dataset (filesystem) 14:43:31 send/recv works on snapshot level, and snapshots work on datasets 14:48:58 Okay, I appreciate the input/guidance. zroot/home/username and zroot/poudriere/ports/username both exist in "zfs list" and I think this makes them a dataset 14:50:07 rsync -avP * username⊙110: and the like works fine for me already though. I just would like to learn the zfs process :P 14:50:55 my day is going perfectly cursedly... i worked around the inability of the ums driver to do its thing using uhidd. I'm successfully (ish) using X11 on a system that needed hw.dri.debug to be at 447 in order for the driver to load successfully (suggesting a race condition), and that when I leave the session, will go back to unusably jailbarred VTs, and I will need to go to my ssh'd login session in 14:50:57 order to shut the machine down. 14:52:29 MelMalik: I'm not tracking much of that. BUT, it doesn't sound like much fun 14:52:49 It's a bit of a lorry crash. 14:54:05 Remilia: FreeBSD nc can do a bunch of FreeBSD specific things among others it can request/require per socket scoped IPsec processing 14:54:36 which should be really interesting for those with ConnectX6 cards and their IPsec transport mode offloading 14:56:33 I've barely even used nc - haven't even scratched the surface of what it is capable of. inxi -Fxxzc0 | nc termbin.com 9999 on Linux is about my nc use LOL 14:58:32 Alma Linux chat right now is talking about a "v2" build of Go only running on "v3" hardware... What a snooze fest LOL 14:59:08 I feel very lucky that my X99 system makes it into the v3 category though. v2 support is getting hard to find 14:59:56 dunno, 1.25 works on my old home router 15:01:20 might be because I build it for v1 15:02:29 Yeah, if I wanted ever last shred of performance out of my boxes I'd rebuild everything with the fancy flags. I'd rather run 1-3% slower though and have stability instead LOL 15:02:48 not sure what you mean 15:02:58 I can only build it for v1 because it is AMD Jaguar 15:03:27 pretty sure v2 would crash with illegal instruction 15:03:58 Was talking about my machines/situations. I could rebuild with compiler optimizations more fitting if I really needed to get a small performance bump 15:04:17 HI 15:04:24 BUT, would rather just run the pre-made packages and have better compatibility/stability 15:04:46 * Remilia has her own package repositories 15:06:20 Remilia: Nice... I've done my own when doing bulk builds using poudriere, and just put them in as file:/// local pkgbase sources. Have never done the webserver portion and shared them out though, even though I've read the documentation :P 15:06:46 pkgbase huh 15:06:57 I've only used poudriere for ports stuff, not for base system 15:07:13 probably very different use cases 15:07:56 Yeah, this was for ports, I've never rebuilt the base system for pkgbase. In fact, I have no clue how to do that, but might research it for lolz 15:08:14 I've tinkered with pkgbase, and blown a few of my systems up with it already 15:08:28 both dev vms are just built from source for their base right now 15:09:15 SponiX: you mentioned pkgbase though? 15:09:31 'local pkgbase sources' 15:10:13 sorry I don't really get it, in my case I have the usual repositories for pkg (and previously for old style pkg-add etc.) 15:10:19 hmm, yeah, I did mention it. But not 100% sure that is what it actually is, or what I actually ment 15:10:43 pkgbase = base system in packages via pkg 15:10:47 it was putting a source file for pkg in like /usr/local/etc/pkg/custom-ports.conf 15:11:02 Yeah, guess it wasn't actually pkgbase then LOL 15:11:41 Yeah, it was actually just building pkgs and a regular pkg source file. Not ACTUALLY pkgbase I was doing -- My bad 15:12:12 I just looked off of the pkgbase configuration that was on a system already to make the pkg-src.conf for local 15:12:32 and just did edits based off of that and the handbook 15:59:23 SponiX: in my case I’d be doing it locally. 15:59:45