00:38:51 I'm struggling to use syncoid. I think I have a sanoid configuration working fine on my system. I would like to pull replicate to another systems 00:42:14 Do I simply add a cron job on my backup machine that does syncoid root@remote_host/pool/zfs_fs local_pool/zfs_fs 00:52:55 syncoid --no-sync-snap root@$remote_host:$src_dataset $dst_dataset 00:53:11 you can always just run it outside of cron first to get it going 00:53:47 but eventually that is the run paradigm, just call that command from a cronjob 00:54:23 if your dst_dataset will be zroot/backup/fun/pics, you need there to be a dataset /zroot/backup/fun, and that dataset /zroot/backup/fun/pics will be created by syncoid 00:54:41 thanks! 00:54:42 yeah, exactly, have cron run it however often you want 00:55:03 happy to be useful! 00:55:09 I can chime in later if you hit a snag 00:55:27 will that replicate all snapshots not just ones created by sanoid? 00:56:29 I have a zfs fs of application installs, I create a snapshot @install after I install it since it should never change. Can I use sanoid like above to sync that even thought sanoid didn't create that snapshot? 00:57:15 if you do --no-sync-snap, it won't create its own snapshot. it'll just pull from the earliest common snapshot, which means it'll pull all of them on the first run 00:57:47 thank you 00:57:50 you'll use sanoid on the destination merely to trim the amount of snapshots you're holding onto 00:58:48 sanoid won't sync anything. syncoid is the mechanism for moving the snapshots around 09:05:58 What the hell. I have a server with zfs exported over NFS .. on the client I mounted and copied a bunch of files over, but I don't see those files on zfs datasets on the server side. I can see space is used on the dataset but files are nowhere to be found. I can see files from the client side only. 09:06:06 Both server and client are FreeBSD 09:44:15 Oh nevermind, zfs filesystem as dataset vs directory on the parent filesystem .. split view 16:37:40 Question *Dwight Schrute voice* 16:37:43 If you exclude creating a Dockerfile (I hate Docker), and cloning the FreeBSD instance... What's your preferred way of backing up a FreeBSD system, as if you needed to rebuild it and wanted to keep track of installed programs and their config files? 16:38:54 Mine sites in AWS, so I could easily clone, but I want to learn this process for when I migrate the AWS instance on-prem once I get my rack setup at home. 16:39:46 I'm not asking for a tutorial, just your preferred methods. I can dig into the particulars myself. 16:54:11 hello 17:09:04 nulltaz: site files, pkg origins, /usr/local/etc/ is a good start 17:39:26 anyone see THIS? It affects FreeBSD by mandatinbng the OS support an age-verification feature [remember the S. Korea banking ActiveX fiassco from the 90's?) and specifically afects open source operating systems... https://x.com/LundukeJournal/status/2027131106336948290. Self-explanatory 17:41:41 I would not mention it here except for its direct relevance to FreeBSD. 17:42:42 I have serious doubts any of that will happen 17:43:03 yeah 17:43:33 it's already a law ibn California and Colorado is working on a similar one. Thats the problem. WE jknow its ridiculous, but this is gummint. 17:44:08 Anyway to avoid going freebsd-politics I'll stop now. 17:44:43 [th fines are ENORMOUS] 17:45:08 plenty of time to get stuck in the courts; 17:46:34 true. But at some point the devs might have to create a patch or something and now we have "the california version" and it'll have a feature that, like the ActiveX-based S. Korean banking sysdtem, inserts a security crater into the OS, directly or indirectly 17:47:29 the S. Korean system from the late 90's was ok. The problem was it rquired ActiveX support, a massive securrity crater. Like that. 17:47:34 /usr/src/usr.sbin/age-verification/main.c int main() { return true; } 17:47:37 one of the few saving graces of those currently in charge is that they will purposely just *not* do something because California did it 17:48:44 thankfully! Anyway I've ben tagging various people onX about this, including EFF 'cause this is a threat to FOSS in general 17:49:48 rtprio - I wish it were that simple. I do not think there is even sa standard or API for applications to use it yet. 17:50:33 anyeays raising attention to it 'cause 1/1/2027 is the "or else" date, apparently 17:50:54 vague, bad laws are not that simple 17:51:20 and furthermore, the law makers obvs don't understand what an open source OS is because just how would that work 17:51:39 I'm dure there's as giasant privacy/security hole waiting to have people drop into it 17:52:35 rtprio - we think like engineers. When you say that to them they thionk "choo choo" 17:53:23 that's why the freebsd foundation has attorneys 17:53:52 The law is a mess. I don’t think it requires FreeBSD support age verification, though. 17:54:03 here's hoping. I should check mailing lists to see what's up I guess. welp later 17:54:18 Note that the restrictions are between a developer/application and a “operating system *provider*”, not an “operating system”. 17:54:57 So FreeBSD is probably okay, but if you have an account with something the FreeBSD Foundation runs there might be issues (by the letter of the law, anyway). 17:55:00 I just don't wanna see asn OS I like get perverted by clueless legisdlators 17:55:53 I'm sure Linus Torvalds already gave thenm the middle finger but you know Red Hat might bend the knee... so that's a potential problem 17:57:50 foss is global, foss can be forked 17:58:19 Maybe. For now I’m setting aside *potential* FreeBSD problems and focusing on *real* FreeBSD problems: why x11 is buggered after my upgrade to 15. :-) 17:59:12 bugged in what way? and what part of X11? 17:59:28 time for the foundation to be settled off shores in international waters /j 18:00:32 anth: are there any logs? 18:04:40 lucius: yes, but I haven’t found anything helpful yet. I’m still going over xev output. 18:04:48 anth: weird keystrokes when typing, right? 18:05:05 Yeah. xev reports that I’m auto-repeating…. Something. 18:05:15 Happens with multiple keyboards, too. 18:05:58 anth: did you create a xorg.conf file or just let it automagic it 18:06:29 anth: what driver do you use? kms? 18:06:51 Scfb 18:07:30 rtprio I left the one from 13 that was working. I don’t remember how I created that one (many years ago) but I don’t think I did it manually. 18:08:06 hm, the man page for that doesn't read like you want to use it if you have any other option 18:09:11 I see that zpool status identifies disks with "gpt/zfs-". How can this be changed to show something more meaningful, like the physical drive SN? - I tried gpart modify -i 1 -l da0 but this caused the drive to show up as da0p1 in zpool status... 18:10:09 anth: try to move xorg.conf out of the way, install and load drm-kmod and see if xorgs autoconfig works better 18:11:05 I have drm-kmod installed but I’m going to reinstall. There were some other pkg oddities after the upgrade. 18:11:18 Should it re-populate a missing xorg.conf? 18:12:04 Wasn’t there an x11-config or something? Lord it’s been a minute since I’ve done this. 18:12:32 no, not having any xorg.conf is totally fine as long as xorg configures stuff correctly 18:13:17 it has been a while since having an xorg.conf was required 18:15:31 "auto-repeating…. Something." Maybe you have sticky keys? I'm just guessing. 18:16:56 Tonn3k: no, it’s auto-repeating something that isn’t an actual key. Also I tried multiple keyboards. 18:17:33 Is there a meta-package that will get drm-kmod and all the relevant loadable drivers? 18:17:56 drm-kmod is the meta-package 18:18:06 K 18:18:55 Ugh, now the X server just doesn’t start. 18:19:05 (Which feels like an improvement; probably easier to debug.) 18:19:29 did you load the kms kernel modul for your graphic card? 18:23:56 Not explicitly? dmesg makes it look like it did? 18:25:17 Let me double-check I’m looking at the right driver for this kit… 18:25:48 also dont forget modesetting if you have nvidia 18:30:43 No, intel. (It’s a NUC 6) 18:30:48 tbh i would probably move your old config aside and start over 18:31:15 I did. Now it doesn’t start at all. 18:32:48 1. do you have the right shiz loaded for your video card? 18:32:50 The xorg.0.log mentions a seg fault, which seems “promising”. 18:34:03 i suppose suggesting wayland would be not appreciated 18:34:06 hm, I expect that to need kldload i915kms.ko like about all intel graphic cards 18:34:08 But it doesn’t say what’s segfaulting. 18:34:42 I915kms.ko is already in there, per kldstat 18:35:36 rtprio: I doubt wayland will work any more than xorg in this case 18:36:22 you might be surprised 18:36:42 ok, so you have i915.. .and is there a dmesg line regarding i915? 18:36:54 (thing is i havne't configured xorg now in many years) 18:36:58 Yes 18:37:32 But I’m wondering if these modules are outdated. 18:37:42 (Like, my installed copies.) 18:37:48 the kernel modules? they shouldn't load if they are 18:37:59 freebsd-version -kru shows everything the same version? 18:38:31 I wouldn’t think so. But the dates suggest otherwise. But maybe freebsd-update set the date to something other than when I did the install? 18:39:08 Hrm I get two -p2 and one -p3. 18:39:56 freebsd-update shouldn't touch stuff installed via pkg 18:40:31 Does pkg put things in /boot? 18:40:51 if using pkgbase, yeah 18:42:21 "But it doesn’t say what’s segfaulting" I wonder what it was doing before the segfault? That could give some clues. 18:42:32 and the drm drivers are put in /boot/modules too 18:59:59 Removed and reinstalled everything I could think of xorg or drm related. Server’s back, but no change in behavior. 19:02:13 Something definitely doens’t like not having an xorg.conf, though. 19:10:37 i would consider making a new xorg.conf 19:10:44 without an xorg.conf xorg tries to load diffrent drivers in order, until it can load one, if one of these gets xorg to segfault instead of just failing to load that would be a problem. And to make sure, you rebooted after reinstalling the drm firmware, to make sure the reinstalled one is loaded? 19:13:26 Yes. But I’m more confused. 19:14:02 I manually moved the modules from /boot/moduels into a subdirectory to get them out of the way. 19:14:22 That subdir is now gone after reboot, but also the 915 modules don’t seem to be there, but dmesg says it’s loading them? 19:31:35 anth - ios this Xorg after 2 years of updates were reverted recently? So it might be a regression. I installed xorg-server-21.1.20,1 about 2 months ago, no problms. Maybe a DOWNgrade would help? 19:33:02 but you should not mess with /boot/modules like that. I suggest re-making the dir and putting the files back 19:33:54 also cn you boot to conole? disable xdm or whatever display manager got installed 19:34:48 I always use startx. Then you can see the text as it loads, and why it craps out, then look at /var/log/Xorg.0.log 19:35:00 boot to console 19:35:41 drwxr-xr-x 2 root wheel 31744 Feb 2 12:29 /boot/modules 19:36:12 [that way you have all of the permissions etc. for it] 19:37:45 * shbrngdo mentions some drama between Xorg and Xlibre, not unlike what happened with FBSD 5 and Dragonfly a decade or two ago, and 2 years' worth of commits on Xorg got reverted. 19:40:32 * shbrngdo also points out that installing the 'mode' X11 driver creates a boatload of modues, but is necessary for Intel graphics to perform correctly 19:41:47 these need to be re-instaalled whenever you upodate the kernel. build from source is proibably mest for klernel modules. not sure where yor knowledge level is, so hopefully not bering "captsain obvious" 19:42:17 ah, stoopid keyboard 19:44:00 Shbr 19:44:10 Sigh. Stupid IRC client. 19:44:26 shbrngdo: yes, I always boot to console and run startx, too. 19:45:45 My FreeBSD knowledge used to be very strong but is quite rusty. Feel free to state the obvious. :-) 19:45:57 Where could it be getting those kernel modules from/ 19:45:58 ? 20:16:44 FreeBSD runs almost exclusively on servers. Does it have a clever solution for generating proper entropy for RNG, without user hardware like mouse / keyboard being attached? 20:28:09 if it's that important to you, they used to have ssl accelerator cards that had an entropy device 20:28:12 otherwise, lavalamps 20:28:43 rtprio: lavalamps? 20:29:23 cloudflare uses lavalamps as entropy 20:29:31 that article was ages ago 20:34:08 jemius This might be of help: https://papers.freebsd.org/2017/vbsdcon/gurney-A_Deep_Dive_into_FreeBSDs_Kernel_RNG.files/gurney-A_Deep_Dive_into_FreeBSDs_Kernel_RNG.pdf 20:34:17 jemius: There's hardware support to init. rng. 20:37:12 thx for the link 21:44:04 https://www.youtube.com/watch?v=4qu5-tXVSGw 21:44:20 " MidnightBSD Responds to California's Age Verification Law by Excluding California" 22:54:14 I created a wg interface and applied the necessary config to my wg interface using the 'wg setconf' command. Will I need to manually declare my wireguard interface as a cloned interface in my rc.conf for the interface to persist across boots? I wasn't sure about this, since wg support is within the system kernel, rather than a standalone package. 23:12:44 I have a question 100% disconnected from my X11 problems. 23:13:25 Is anyone here connected to the FreeBSD foundation? I’m trying to figure out who their official liaison to the risc-v foundation is. Anyone know that, or know how I would figure that out? 23:44:11 I'm curious if FreeBSD has taken any position on what they're going to do about the new California age verification law that requires operating systems to very age. 23:46:53 I don't know about FreeBSD but MidnightBSD has changed their license to exclude California. I am sure that is to avoid liability of being sued since that's what the new law allows. 23:50:21 crb, interesting, thanks for sharing. i feel that a law like that stifles creativity and innovation. i was a teenageer when i first got into unix-like operating systems. 23:56:06 Oh, things are just starting. The DB48x project is a free firmware replacement for calculators. They meet all of the criteria for being an operating system and therefore under the jurisdiction of the new law. So they have also done this. https://github.com/c3d/db48x/commit/7819972b641ac808d46c54d3f5d1df70d706d286 23:56:27 Any more discussion on this topic should be moved to #freebsd-social or it will get out of hand here real quick.