00:15:26 hello, just updated to freebsd 13.3 from 13.2. the module radeonkms seems to lead to a kernel panic. so, what now? build kernel from scratch? 00:16:47 how do you backup the working kernel as well 00:17:11 I don't want to lose it 00:50:14 nmz, when similar problems happened in the past, the usual cause was a kernel ABI change that sneaked in. If that's also the case here, installing radeonkms from ports instead of packages, or reinstalling it if already installed from ports, should help. You shouldn't need to rebuild the kernel itself. 01:37:55 nmz, I have the same problem here in that I use the radeonkms driver from ports. There are two choices. Compile your own radeonkms against the new 13.3R kernel. Return to 13.2R which is still in support and has a new update recently. I returned to 13.2R for the moment since that was easy. 01:38:41 The easiest thing is to reboot and select the previous Boot Environment. That will return to the previous 13.2-RELEASE from before the upgrade and everything will be good to go again. 01:40:00 The root cause of the problem is that ports are compiled against the oldest supported system version. Which at this time for quartely is 13.2R. That will expire in about another 2 months when 13.2R hits EOL. Then ports will be compiled against 13.3R and so in about two months one could upgrade and the radeonkms in ports should match and work then. 01:41:12 Also let me note again that 13.2R is still in support and a new 13.2-RELEASE-p11 just posted recently. It's not dead yet. No real pressing need to push on at this time. 01:42:02 Or you could push forward to 14.0-RELEASE too. I myself always wait for the .1 release. I am just rather risk adverse. But forward to 14 would be another way to go too. 02:17:16 V_PauAmma_V: make deinstall and make reinstall does nothing, it seems to just fetch the binary 02:17:23 I think its because I never installed /usr/src 02:18:57 rwp: thanks, I just freebsd-update rollback, I'll just wait for the .1 release 03:14:11 any recommendations for youtube channels that have really good vids on zfs? 03:14:26 mostly like the basics, snapshots, clones, copy, etc etc 03:20:20 pools, datasets 03:20:24 https://openzfs.org/wiki/Main_Page 03:20:25 Title: OpenZFS 03:22:01 none of those look like basic overviews 03:25:05 not the ones on the main page, but if you click into learning more about zfs 03:25:08 you would find https://openzfs.org/wiki/Newcomers 03:25:10 Title: Newcomers - OpenZFS 03:25:25 oooo, ty! 03:25:38 zfs is amazing tech. it's the only FS i'll ever run 03:26:22 specifically, https://openzfs.org/wiki/Newcomers#Where_can_I_learn_more_about_OpenZFS? 03:26:23 Title: Newcomers - OpenZFS 03:46:45 watching it now 04:40:24 any ideas what would trigger this?: kernel: GEOM_ELI: Crypto request failed (ENOMEM). gpt/WD14TB_ZV6C.eli[WRITE(offset=3708987219968, length=1036288)] 04:40:56 I'm seeing them steadily roll in, but as far as i can tell, everything is fine 04:41:40 only unusual thing i'm doing is syncing several TBs of data with syncthing 04:41:51 curious if it stops when that is done 04:45:51 fwiw, it's reported for all 4 HDDs that are part of the same zpool, but not at the same time. 05:02:15 that video sucked. didn't actually talk about clones, snapshots, etc. it was basics of how zfs works but not its features 05:09:50 I generally don't like videos for learning things. I much prefer the written word. Can skim faster to the details I am needing at that moment. 05:11:49 markmcb, Obviously that ENOMEM is sounding like memory stress. But I don't actually know anything. I did not think GELI an expanding amount of memory. 05:15:47 rwp ya the handbook has a zfs page i'm gonna go read that 05:18:37 oh, someone else noticed this too: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275336 05:18:39 Title: 275336 – Processes exiting with SIGSEGV on shutdown on ZFS systems 05:29:48 is there any way to increase swap space on a zfs system if you let the freebsd installer set it up for you? 05:30:08 freebsd's installer only setup a 2GB swap when i have 8GB of ram meaning i can't suspend to disk 05:32:03 Assuming that the installer did the normal thing and used all of the available space then the only easy way is to add another disk. 05:32:22 Or you can backup up everything, reinstall with a different partitioning, then restore from backup. 05:34:18 you can't shrink a zpool can you? 05:57:39 You can make it bigger. 06:10:05 sadly you can't shrink it yeah 06:10:47 additionally you need to move it 06:13:29 you could use bigger disk 06:13:39 that saves you from all the hassle 06:19:22 s/disk/whatever storage this s4-doing system has/ 06:34:06 and, unsure if there are good videos on zfs 06:34:18 i haven't needed video for zfs yet 06:54:05 but i've had this problem before, i was able to find text, was given more text upon asking, and noone really got the reason for nor was able to come up with pages with graphics or uni lecture type of video on subject 06:59:36 thanks for the help yesterday, i think its my hw raid controller that is faulty 07:02:59 eh 07:03:40 and that you can't even test 07:04:01 the drives works perfect in other server 07:04:22 same hw, right? 07:04:32 write speeds are ok? 07:04:42 yes its identical server 07:04:49 whoops 07:05:12 have 3 hp bl460c g7 servers 07:05:19 2 with freebsd 1 with debian 07:06:46 wonder if i get correct performance if i skip hw raid from controller and just let it pass through 08:12:44 A month perfectly smooth work on BSD on zfs installed on a dead ssd, on which windows/ntfs struggling to boot, constantly crashing/freezing/bsod... 08:13:02 BSD dont find any errors in /var/log/messages 08:13:57 Is there a logs especially for ZFS to check the filesystem health ? 08:14:17 zfs status clean ( all zeros ) 10:19:37 https://man.freebsd.org/cgi/man.cgi?query=zpool-scrub&apropos=0&sektion=0&manpath=FreeBSD+14.0-RELEASE+and+Ports&arch=default&format=html 10:19:38 Title: zpool-scrub 10:21:38 nerozero: you may want to not entirely trust that drive anyway, even if zfs does a good job at using it 10:23:59 hello 10:25:11 Where does FreeBSD store sockets for services? Is there a guide like the Filesystem Hierarchy Standard? 10:28:50 orbifx: /var/run seems to be the usual place 10:30:09 thanks vortexx 10:30:17 Also I just found this: https://man.freebsd.org/cgi/man.cgi?query=hier&apropos=0&sektion=0&manpath=FreeBSD+8.2-RELEASE&format=html 10:30:18 Title: hier 10:57:46 evilham 10:57:48 thanks ! 10:57:51 scan: scrub repaired 0B in 00:00:11 with 0 errors on Mon Apr 1 14:57:49 2024 11:00:08 the purpose of the installing zfs on a dead drive was testing "will it work"? Now - don't even know to say, just wow... 12:07:49 not so dead now, is it? :) 12:10:17 like evilham said, it wouldn't trust it too much though. if you haven't already, you should clone it to a known good drive & put that in your comp. 12:29:55 Any ops around? 12:33:05 mane: in #freebsd-ops 12:34:45 Thanks 12:51:11 ZedHedTed, this is just a ZFS testing machine build, to check how good ZFS is at working with a bad drives, nothing important there. 12:52:08 I knew that ZFS can tolerate and automatically correct some of the drive errors, but working on a dead drive without experiencing glitches at all with 0 errors ... 12:52:09 WOW 12:58:27 Hi guys, quick question: does behyve work on i386, or is it an amd64 only thing? (on the host) 13:10:20 nerozero: oh. very good. 13:25:17 dansimon, this is more dependent on the cpu and platform you got, your hardware should support virtualization 13:29:19 nerozero: it does, I was just wondering if behyve had a hard amd64 build requirement (like some hypervisors do) 13:30:23 I guess the latest builds does, FreeBSD is stopping all 32-bit Hardware support 13:31:05 I read about that somewhere on a bsd announcement site 13:31:27 Really? I did not know that! 13:32:03 Not sure where, it was back in January I guess 13:34:59 https://www.freebsd.org/platforms/ here it is 13:35:00 Title: Platforms | The FreeBSD Project 13:35:04 look at the bsd15 13:35:34 all i386 platforms are not supported except 32-bit ARMv7 15:33:07 hi all 16:56:19 can a (non-vnet) jail be assigned IP addresses which don't exist on the host but might do later? 18:02:17 how do we learn about vnet? only links i found are in the context of jails 18:02:31 but even base networking runs in vnet 0 so it's not a jail only feature i don't think 18:02:42 vnet is specific to jails, there's no other way to use it 18:02:56 the host's "vnet" is just the default IP stack 18:26:02 Hello. Is FreeBSD known to work on Amlogic S905X? 18:26:34 I'm searching the forum now but the answer is no, I won't search 18:27:05 I have this: https://libre.computer/products/aml-s905x-cc/ 18:41:07 okay it seems the answer is a big NO 18:42:11 alepzi, Other networking features other than "vnet" such as ifconfig creating bridges and epairs and other things all work everywhere though. That's the place to start. The ifconfig documentation. 19:09:40 Is there any way, these days, to support a Logitech Sphere pan/tilt camera in FreeBSD, or is this thing garbage now? 19:13:18 tmux in freebsd question. outside tmux, i can use my mouse in things like htop. if i run htop in tmux, mouse doesn't work. but i use the same tmux config in other OSes and it works. is there a freebsd+tmux consideration for mouse? 19:15:22 I think it's more the fact that your terminal emulation doesn't support it, but I couldn't tell you details. 19:16:49 Whatever configuration lets it work in Linux will probably work in FreeBSD if you can manage to duplicate it. 19:17:00 i can use mouse in tmux just fine though, it's only the apps in the tmux panes that don't respond 19:17:32 GNU Screen probably doesn't work either. 19:17:53 At least, the mouse. 19:29:10 gh00p, Confirm that you have turned mouse support on in tmux with "set -g mouse on"? You can do that on-the-fly with PREFIX : set -g mouse on Enter 19:29:34 Oops! s/gh00p/markmcb/ for the above! Sorry! 19:29:42 rwp: yep, it's on, can toggle it with prefix-m 19:30:08 I can do all mouse things, it's just not passing the MouseDown1 event to the pane 19:30:21 I disable the mouse in the terminal as it disrupts my use of copy-paste so that set -g mouse on is the best I can suggest. 19:31:05 This should handle it (default): bind-key -T root MouseDown1Pane select-pane -t = \; send-keys -M 19:31:14 but it's not for whatever reason 19:31:26 The mouse will select the pane 19:31:39 but that last "send-keys -M" doesn't seem to happen 19:33:18 same config i use works in Linux and OpenBSD with the mouse event passing into the pane 19:34:30 anyone has a guide on how to find a failing dimm based on these messages: kernel: MCA: Bank 8, Status 0x9c00004001010090 ? 19:35:35 markmcb, If it were me I might look through the Linux & OpenBSD tmux config files and see if they do something specific. Then I would look at patches they might have applied to the code. Then I would try comparing and compiling that version on FreeBSD to see if that works. 19:37:25 rwp: thanks. "tmux list-keys" shows no relevant differences i can see for mouse events. maybe it's how it's built. 19:38:18 it's just odd that it works for tmux, and just doesn't passthrough. seems like if mouse works it'd all work. ... unsolved mystery 19:38:18 Another external input is the terminfo/termcap data for the terminals involved. I don't know but that's just another thought I have of where things might be different. 19:41:36 Anyone seen this? https://www.netgate.com/blog/pfsense-software-embraces-change-a-strategic-migration-to-the-linux-kernel 19:41:38 Title: pfSense® Software Embraces Change: A Strategic Migration to the Linux Kernel 19:41:47 it does not seem like an April's Fool joke :( 19:49:17 jmpp, The TrueNAS change is basically the same and definitely already happened well before April 1st. 19:50:34 yeah, for sure. Hardcore TrueNAS CORE user here, so I've been following that with great pain 19:50:40 Also: https://www.reddit.com/r/freebsd/comments/1bhvt2e/comment/kvukh2k/?utm_source=reddit&utm_medium=web2x&context=3 19:50:55 My interpretation and spin on this is that newcomers are more often comfortable working with the Linux kernel and therefore 1) wish to work with the Linux kernel and 2) more people work with the Linux kernel therefore companies can find Linux kernel expertise more easily and it is easier for people to move jobs. 19:52:24 weh, thats a shame 19:53:26 rwp: yeah, but the drain on other OS' such as FreeBSD is quite a shame 19:58:44 This is motivating me that I need to find more time to become more involved in FreeBSD development. 19:59:56 likewise! 19:59:58 Finished reading through the reddit thread. And it is sad that in the move to OpenZFS that FreeBSD went from being number two behind illimos to being what sounds like an also-ran given that it is said that test cases in OpenZFS don't even run on FreeBSD. 20:00:18 100% agree 20:00:27 that's me on Reddit talking with gonzopancho 20:00:59 he did say they did intend to stand behind FreeBSD at least for years to come, true 20:02:41 but, still, the tone of that Reddit discussion, strongly supporting iX's move, as I understood it, did not instill a lot of confidence on how strong said FreeBSD support will be going into the future 20:05:03 By the nicks I make assumptions-connections. And yes that would be ground truth information about why they are moving. 20:06:10 Does anyone know what he was referring to with "The person who was able got chased out because some reporter at a different big publication decided that clickbait was more important than honest journalism"? 20:06:12 It reinforces that zfs sits as an extremely important part of the system. So important that it has become like a fledgling bird and left the nest flying off on its own with OpenZFS. Which is now a major important part of Linux systems. 20:06:52 vkarlsen, Not I but I assume that referred to some register article. And it had me curious too. 20:08:14 FreeBSD has been a major developer of zfs but now is losing out with OpenZFS due to things like OpenZFS not even running tests on FreeBSD. And FreeBSD kernel struggling to make fixes and improvements that are causing real problems for vendors using zfs in their systems. 20:08:32 it also had me pretty curious, but I didn't manage to follow up on that conversation 20:09:07 the netgate one is probably a joke "linux kernel with freebsd userland" is probably inteded to be a tell 20:09:20 Since the Linux kernel has always had more developers, more churn, it is easier to get changes through that process flow. So they are going to chase the new features which means going to the Linux kernel. 20:10:19 I don't think it is a joke. I think that would be a viable system. Linux kernel + FreeBSD userland. 20:10:38 foxiepaws: don't think it's a joke at all: https://www.reddit.com/r/freebsd/comments/1bhvt2e/comment/kvukh2k/?utm_source=reddit&utm_medium=web2x&context=3 20:11:05 besides, aren't there already Linux systems + FreeBSD userlands out there? Devuan, or something like that? 20:12:15 i just don't think they'd release something on april fools day like that when yesterday or tomorrow would be equally fine 20:12:38 to avoid misinterpretation with how things are 20:12:39 I think it's just awful timing for the announcement 20:13:01 but, other than that, it rings true to that discussion gonzo had with me on Reddit 20:13:25 It's the reason April Fool's gags work is because for most companies it is just another business as usual day. They make real announcements that we all wish would have waited so that we would not be questioning them. 20:15:21 In that thread it was hard for me to interpret if gonzopancho said something and meant that what they said was good or what they said was bad. For example the reuse/recycle of vnodes. The complaint was that FreeBSD by legacy is a heavy recycle code base but that Linux & Solaris do not recycle. I presume that means they free/allocate instead of recycling. "This is important for the future of zfs." Yes. But in which direction? 20:16:11 I thought it was pretty clear he was heavily critizing FreeBSD's approach 20:16:23 s/heavily/strongly/ 20:16:31 * jmpp had very little sleep last night 20:17:11 I might presume that means that free/allocate is more dynamic in the use of memory and therefore perhaps can handle short duration memory stress spikes better? But that does not mean that recycling excludes using more dynamic memory too. I just don't know enough about the code base. 20:18:02 I don't know any about that code base, hence my initial reluctance to reply in any depth 20:19:50 I could see that recycling would be much more efficient. Better cache locality. And free/alloc often suffers from what I will say is memory fragmentation due to lack of a better name if memory chunks don't stack up like tetris as nicely and holes of unusual sizes get generated. Not saying there isn't techniques to make that work but it's not absolutely trivial. Look at the effort put into malloc() over the years. It's not a trivial 20:19:59 problem. 20:24:42 also raw speed, 'cause when you allocate a new memory chunk, you have to find said chunk to begin with 20:25:00 whereas if you recycle an already allocated chunk, you spare yourself that potentially expensive step 20:25:29 Sometimes the grass appears greener on the other side of the fence. Sometimes wanting something is not as pleasing of a thing as having. This might be a case of that happening now with these vendors who are jumping from here to there. In which case some might return. Some might continue to offer both. 20:26:30 monocultures are never a good thing 20:26:38 and Linux is very quickly becoming one 20:30:27 jmpp: Ed says: no EN/SA for libarchive #2101 but perhaps for #2107 https://mastodon.social/@emaste/112197323460302957 20:30:28 Title: Ed Maste: "@wednesday⊙nhi IMO the fix in #2101 is too…" - MastodonEd Maste: "@wednesday⊙nhi IMO the fix in #2101 is too…" - Mastodon 20:31:42 Speaking of someone who probably has not had much sleep the past few days, emaste has almost certainly been on task saturation. Can't thank him enough for his work and effort on this. 20:32:38 "IMO the fix in #2101 is too minor to warrant a EN or SA." nice! 20:33:35 Just it by itself seems low risk probability too. That printing of unescaped file names feels like something for a yet different serial stream of connections that the malicious actor was putting in to have available for something else. It would need to be chained along with other things. 20:34:33 but definitely a very dangerous step to have let slip through 20:34:38 thankfully it was caught! 20:35:15 pretty sure that one wasn't malicious, there are a bunch of other instances of not escaping that are pre-existing 20:35:52 maybe not malicious in itself, as in, not leading to an exploit directly 20:36:30 There was a patch put in where there was one review comment before it was merged that said only lgtm (looks good to me) and then it was merged. I looked at that patch and there is no way I would have connected it. Especially since it was *six months prior* to when what the patch affected was injected into other parts of the code base. At the time it was not malicious. But it became malicious later. Truly genius. 20:36:32 but if created by the same xz actor, then it wouldn't surprise me it was in preparation of 20:37:04 exactly 20:38:11 Playing the long-game there with the patience of the sphynx. It's impressive in its cold and calculating malevolence. 20:39:43 there was commit, IIRC on libarchive precisely, and IIRC by this same xz "person", where someone made a comment to the effect of "if not malicious, certainly on track to be" 20:39:47 precisely the point 20:39:51 i've been wondering about this sort of attack ever since the "FBI put a backdoor in OpenBSD IPsec" thing - which i guess turned out to be false in the end, but the idea is clearly viable. it's been done before at least once by researchers: https://arstechnica.com/gadgets/2021/04/linux-kernel-team-rejects-university-of-minnesota-researchers-apology/ 20:39:52 Title: Linux kernel team rejects University of Minnesota researchers’ apology | Ars Technica 20:40:02 i'm curious if there have been any other notable malicious examples 20:41:18 You mean like Ken Thompson? Reflections on Trusting Trust by Ken Thompson http://genius.cat-v.org/ken-thompson/texts/trusting-trust/ 20:41:20 Title: ACM Classic: Reflections on Trusting Trust by Ken Thompson 20:41:30 well, there's Ken Thopmson's paper, of course 20:41:34 I think that is the one. I just searched for it a moment ago to cite it. 20:41:36 * jmpp high five's rwp! 20:41:39 i was thinking more like real world examples 20:42:07 Real world examples are sometimes not found, not caught, still available to be active, and so we just don't know. 20:42:19 lw: Thompson's point was, precisely, you could not tell if his was actually a real world example... or not ;) 20:43:16 kevans: https://github.com/libarchive/libarchive/commit/02cfa8ae67fa60e6d0415b75babf64864f0d8e72#commitcomment-140401844 20:43:18 Title: Reusing code from zip size known and adjusting comments · libarchive/libarchive@02cfa8a · GitHub 20:43:43 i am familiar with the paper, i intended to ask if there are any notable examples *that we know about* (since if we didn't, they wouldn't be notable...) 20:43:50 yes, i was eyeballing that a couple days ago 20:43:56 different issue, perhaps even different code base, but I'm referring to the potential long game pursuit here 20:45:39 lw: certainly lots of finger pointing and even accusations, even about RSA encryption, but right now a demonstrated real world example, other than xz of course, doens't come to mind 20:46:25 Hadn't Jia Tan's GH profile been disabled?! https://github.com/JiaT75 20:46:27 Title: JiaT75 (Jia Tan) · GitHub 20:47:48 i think github received some flak for disability the repository/users involved since it made analysis harder, maybe they undid that 20:47:53 s/disability/disabling 20:48:10 yeah, they did, but xz's is still disabled, though 20:51:22 anyone knows how to interpret MCA errors ? 20:51:32 trying to identify a failing dimm 20:52:00 last1: if possible check your ipmi event log tool 20:52:05 e.g. ipmitool sel list 20:52:08 last1: dmidecode might have per-socket error counts 20:52:30 there's no errors in ipmi 20:53:01 last1, I admit to brute force last time I had this problem. I removed half the ram at a time and ran memtest86(+) and did a binary search to identify the bad ram. Which turned out to be the dimm socket on the motherboard! Drat! 20:53:56 lol 20:54:11 that's pretty hard to do on a production system :| 20:54:21 I was hoping to locating the correct dimm and getting it rma'd 20:54:39 mason: for each dimm ? 20:54:43 looking 20:54:47 I think for each socket. 20:55:18 but I could be confused here 20:55:33 I'm checking too, I don't see anything like that for the dimms 20:55:34 https://pastebin.com/0TnUA248 20:55:35 Title: Handle 0x0020, DMI type 17, 84 bytesMemory Device Array Handle: 0x001 - Pastebin.com 20:56:01 I see the dimm says: Bank Locator: P0_Node0_Channel0_Dimm0 20:56:10 can that be mapped to MCA banks ? 20:56:47 last1: Is that just one stick? And is it ECC? 20:57:08 that's one of the sticks yes, I have 4 x 32Gb, ECC 20:58:32 last1: Have you looked at this yet? https://www.freshports.org/sysutils/mcelog 20:58:33 Title: FreshPorts -- sysutils/mcelog: Collects and decodes Machine Check Exception data 20:59:00 I could have sworn I got memory error data out of dmidecode in the past, but I'm not seeing it just now. 20:59:50 yeah, I used mcelog too, didn't give me more info sadly 21:00:03 last1, I looked in my notes and see a util-linux package reference to lsmem and chmem there. "lsmem" and "lsmem -a" and a note that ,,With "chmem" you can temparily disable memory regions at runtime. So after you found out which RAM bar it is, you may test your suspicion by removing the specific RAM region with "chmem".'' 21:00:19 Ah, "error information handle" in dmidecode might be what I'm thinking of. 21:00:23 I know, util-linux, but it's related information. Maybe some helpful information there regardless. 21:04:24 so what would the point of this warning be in its current format ? 21:04:33 just to get you to start reseating ram and checking them one by one ? 21:11:08 https://www.reddit.com/r/freenas/comments/h9lh4l/mca_correctable_memory_errors/ 21:11:30 I wonder how this guy mapped his error to dmi decode bank 8 21:12:10 That second comment about swapping dimms in slots is one I have used before to identify errors with locations. 21:14:48 ah lol 21:14:52 it says in his dmidecode: Bank Locator: BANK8 21:15:27 hang on a second, maybe it's on the motherboard manual 21:15:28 P1_Node1_Channel0_Dimm0 21:17:58 or not, seems my issue is somewhat common and nobody knows how to figure it out :( https://www.truenas.com/community/threads/finding-bad-memory-chip-location-on-supermicro-x10drl-i-mb.78078/ 21:17:59 Title: Finding bad memory chip location on Supermicro X10drl-i MB | TrueNAS Community 21:19:43 last1: That's the thing - I remember a while back seeing recovered errors, and I thought where I saw them was dmidecode. But I have none showing now so I can't confirm itk. 21:19:48 s/itk/it/ 21:23:53 https://twitter.com/hnasr/status/1774658928913387992 kind of on topic of what we were recently discussing 21:33:51 jmpp: that's bad indeed, but playing devil's advocate, is that much worse than willingly giving up your data to say CloudFlare ? 21:33:59 they are basically mitm, but paid 21:34:17 heh, very very true! 21:35:10 still, there's the issue of consent 21:35:28 even if in the case of CloudFlare it's objectionable, it's still consensual 21:35:35 whereas in the case of Facebook... eehhh... 21:35:46 I honestly don't think many people understand that CF terminates their SSL connection 21:36:06 especially since their free tier is...free 21:36:14 attracts a whole bunch of clueless people 21:36:34 * jmpp hugs his locally hosted HAProxy setup! 21:43:32 is reddit down for you guys ? 21:43:44 I get 503 Service Temporarily Unavailable 21:43:46 not in France 21:44:29 failed for me a couple of times with 503, indeed 21:45:23 failing indeed right now 21:51:50 https://www.reddit.com/r/PFSENSE/comments/1bt3whd/comment/kxlm9tw/ 21:53:44 I understand the Linux kernel is very dynamic and well maintained and blah blah 21:53:52 but the distributions, really, what a shitshow 21:54:02 systemd is a nightmare 21:54:19 10 different ways of doing things across 10 different distributions 21:56:22 last1: yikes, yes, they kicked and forced me out of the Linux ecosystem, I fled in horror to the harmony and consistency of the FreeBSD userland 21:57:29 last1: and please do not mention CentOS "security" framework monstrosity, I'll suffer a PTSD episode! 21:59:17 selinux? 21:59:52 * jmpp starts twitching.... 22:00:10 you're going to cost me a call to a therapist! 22:00:13 :P 22:02:57 https://marc.info/?l=openbsd-cvs&m=171200100510963&w=2 22:02:58 Title: 'CVS: cvs.openbsd.org: src' - MARC 22:04:23 Yikes, I always thankfully forget that OpenBSD is still using CVS! 22:06:08 "xz is a lifted Ford F-250 that "just ran a stop and killed a cyclist"." was that said in hindsight? Or was it visionary...? 22:06:11 :D 22:07:27 wait, you do know about the xz incident, right ? 22:08:14 of course, been talking about it here all weekend, hence my comment 22:08:40 :) 22:08:47 wait, I'm just noticing the date on that commit 22:08:56 is it an April Fool's joke, or something? 22:09:09 * jmpp no follow's... 22:09:27 the bigest indicator is probably "in good company... kernel.org, FreeBSD, and Debian" 22:09:47 there's no way that they'd consider us good company :-) 22:09:58 heh! 22:10:45 I am surprised an April Fool's joke would extend to such a large and potentially misleading commit 22:11:38 Dschihad(-75) in Ramadan! 22:11:38 That is very unreligious. 22:11:48 https://marc.info/?l=openbsd-cvs&m=171200380712333&w=2 first respose 22:11:49 Title: 'Re: CVS: cvs.openbsd.org: src' - MARC 22:11:53 tbf it's almost certainly just a fake e-mail 22:12:15 yeah, that's what I came to think, but man, was that crafted! 22:13:03 we have soem good ones on occasion, too 22:14:18 https://lists.freebsd.org/archives/dev-commits-src-all/2023-April/024787.html was pretty good, haven't seen one fly by this year 22:14:19 Title: git: f001edfb5d41 - internal/admin - Add Charles Root 22:21:58 on the dmidecode, after reading countless pages, there's no reliable way to do it except through manual trial and error 22:22:04 so instead of doing that I'm rma'ing all 4 sticks 22:22:11 and let Samsung figure it out 22:22:23 end of story, too much time wasted on that 22:24:42 last1: Good call honestly. 22:30:17 out of so many, one phrase Bryan Cantrill once said about sys developers separating from sys admins when the time came to understand why a system had crashed. The former don't want you to touch the system, at all sometimes, as that may alter the evidence and impact the investigation; the latter, instead, just wants to get the system back up and running ASAP! 22:30:58 and I loved that comparison 'cause I do a lot of sys admin, but I'm also a dev (though not a low-level OS dev, perhaps unfortunately) 22:32:30 and that mix definitely helped me see the light and learn to classify problems, out of the so many ways they can be classified, into two categories: 1) those I *care* to understand and try to solve, and 2) those I *don't*! 22:34:24 someone pays you to care ? 22:35:27 to bring the platform back up ASAP, for the most part, but then my OCD to understand why something is not working as expected tends to interfere 22:35:46 meh, I moved past that a long time ago 22:35:51 family is more important than the company 22:36:04 very very true 22:36:20 but I'm also a physicist by profession, so it kind of comes built-in with the brain wiring 22:39:20 so quantum physics and those dice must really mess with your brain then 22:40:53 let's just say I had high hopes for Einstein's unrelenting position that, at the end of the day, the world *had* to be deterministic :P 22:43:10 I still can't imagine the fabric/geometry of space time as posited by GR can morphed into gravitation as a field 22:43:34 it's profoundly at odds that mass generates the shape in the fabric, vs the graviton and its field 22:43:55 hopefully they can advance a bit during my lifetime 22:45:56 last1: I don't quite like the "fabric" moniker, I think the morphing of spacetime by a mass/energy distribution is much easier understand if you envision the universe as some kind of a foam in which we're embedded 22:47:02 so, as it's hopefully easy to see, if you step into a massive bubble bath, your mass distribution is going to disrupt that foam around it, in a way intrinsically linked to your specific mass distribution 22:47:24 and that's easy to understand 22:47:34 but different than me emitting gravitons as I enter the bubble bath 22:48:04 on the other hand, gravity waves have been detected, so who the hell knows 22:48:29 well, it turns out every mass-energy distribution does the exact same to the universe itself, and the rest, what we perceive as gravity, is just the Hamilton's principle of least action, i.e. things will evolve in real life in the way that requires the least amount of energy 22:48:54 as in, you naturally buying the product that cost the least while still meeting your specific requirements 22:49:56 well, that's essentially what a geodesic is, and moving along those is what our minds perceive as "falling in a gravitational field" 22:51:32 yep, that's GR 22:52:30 when you talk about gravitons, you're getting back into that pesky QM! :P 23:25:46 how can i verify that i DONT have any swap space? sudo top doesn't show it for my host machine but all of my vms do. is that proof? 23:34:03 alepzi, "swapinfo" 23:34:14 tried that, shows nothing 23:34:23 Then you don't have any swap configured. 23:35:05 so i guess that's no swap? but my bsdinstall installerconfig has ZFSBOOT_SWAP_SIZE="1G" like all my vms have so wtf? it has ZFSBOOT_SWAP_ENCRYPTION=yes but the vms don't, is that breaking it? 23:36:16 alepzi, Example from here showing swap configured: https://termbin.com/cvu7 23:38:10 ya my vms show that info but host doesn't 23:38:34 alepzi, Just as extra information perhaps run "geom -t | less -i +/swap" and look for the swap entries partitioned? 23:38:39 so ZFSBOOT_SWAP_ENCRYPTION=yes is making swap not be created? 23:40:12 hmm 23:40:30 that command shows a swap label and dev on each of the mirrored drives 23:41:04 What do you see here: grep swap /etc/fstab 23:41:34 Another example from here: https://termbin.com/fhjl 23:41:35 2 lines 23:42:07 i have the same, /dev/nvd0p2.eli and /dev/nvd1p3.eli 23:42:09 If swap is configured in /etc/fstab but not present on your system then I would try "swapon" and see what errors are emitted when it is attempted. 23:42:11 same values for each column 23:42:41 Sorry, "swapon -a" 23:43:50 said swapon: /dev/nvd0p3.eli: Invalid parameters, same for /dev/nvd1p3.eli 23:43:55 Hmm... My 13.3R recently upgraded system has no swap either. Did you recently upgrade to 13.3R? 23:44:07 ya i'm on 13.3 23:44:13 but my vms are too 23:44:35 My recently upgraded /etc/fstab is zero sized. Hmm... Looking through the old snapshots to see when that changed... 23:46:02 https://termbin.com/c4yx is my host's ZFS config in installerconfig, just to verify those settings are right? 23:47:17 To show my ignorance I don't know how to drive the installer with those variables. It's not something I have done. 23:47:37 ok np 23:47:50 What does "gmirror status" show for you? On my system the mirror is active. But /etc/fstab is zero sized so it is not mounted. I need to fix that. 23:48:08 status not available, try load first 23:48:43 And the crazy thing is on my system it looks like it has always been that way from the earliest snapshot I look at. So it must have been an oversight on my part on setting up that system. Time to look at another one. 23:50:48 Oh good. The rest of my collective is okay. Just something I missed on that one. That's a good find.