00:05:21 ZedHedTed: you can apply this directly with sysctl 00:28:46 thank you CrtxReavr 00:29:18 I already have an old clonezilla pendrive I got to shell but I didn't try any nt commands. will investigate more. 02:51:54 using 4GB of RAM for: ZFS, DE/WM, browser media player 02:51:55 ty 03:16:10 jauntyd: cool 03:17:07 :) 03:17:38 pretty amazing in these modern times, which is why I pointed it out 03:17:50 what is amazing ? 03:17:58 only uses 4GB RAM 03:18:15 yeah 03:18:27 if it works, nice 03:19:03 and you can always upgrade 03:20:40 jauntyd: whats DE WM ? 03:21:57 enlightenment 03:22:25 cool 08:02:24 FWIW, I had the issue of creating raw ZFS (no partitioning) on disk without previously cleaning up GPT and its backup from the disk; in my case, the complicated procedure with dd described in https://forums.freebsd.org/threads/gpt-table-corrupt.52102/#post-292341 was not necessary as gpart -F removed remaining GPT backup without destroying ZFS, kudos for having such useful tools in the OS 10:32:33 I don't know why wblock@ recommends using dd over gpart, but it _is_ an almost decade-old post - so that could have something to do with it. 10:32:51 On the other hand, overwritng sectors with dd _will_ work. 10:34:50 The previous utility for manipulating GPT was gpt(8), but that was removed way more than a decade ago, so I've really no idea. 12:13:22 vedranm: gpart(8) only manipulates the partition tables, not the filesystems laid out inside the partitions 12:13:34 this is sometimes annoying and other times very useful 12:13:54 you can "move" partition ordering, without losing the data, for example. 12:15:18 vedranm: `zpool labelclear` probably is the thing you want to use for that, but it wasn't around in 2015 for that blogpost 12:22:42 dch: it was added to illumos in 2009 (https://github.com/illumos/illumos-gate/commit/096d22d) and openzfs in 2013 (https://github.com/openzfs/zfs/commit/51a3ae72d) 12:22:50 dch: the issue was dmesg reporting backup differing from main GPT, zpool import worked fine tho 12:23:16 zfs doesn't really care about disk partitioning, so long as there's no encryption like GELI being used 12:23:17 that is very annoying when the gpt backup headers don't match what zfs has/sees 12:23:21 ack 12:23:55 i've noticed this problem before and never got around to working out the cause - does ZFS not automatically clear the backup header when you create a pool? 12:26:05 i'm not sure it should, as there's a theoretical way to recover data from a disk where the labels are intact and none of the data has been overwritten 12:26:43 having zpool-labelclear(8) be an unambiguously destructive administrative command prevents last-ditch footgunning 12:27:12 or it at least has the potential to work that way 12:29:54 that's a reasonable argument, but i think it should print a notice when creating the pool then. or does it do that nowadays? i haven't created a new pool for a while 12:53:09 it always has, if memory serves 12:54:10 what is the lightest live image of freebsd i could find to test if my wifi works 13:23:17 ober: thanks! i'll read the man page for sysctl. my RAM's coming in today anyway. 13:25:57 sibyla: if you're looking to test your hardware, try nomadbsd. it's live and based on freebsd, but kinda large. 4GB. it loads all the drivers for you and starts X so you can try connecting to an SSID w/ their GUI applet. 13:26:31 thanks 17:33:07 I try to run a binary and it exits with 'Bus error' 17:33:13 what is that exactly ? 17:36:17 the program is trying to access memory that's not permitted or that doesn't exist 17:38:03 great, I guess welcome to openssl 1.1 vs 3.0 hell 17:39:52 what binary? 17:40:37 check_mysql from nagios plugins, nvm, recompiled it with openssl 3.3 17:40:40 works fine now 17:40:46 weird because I wasn't checking an SSL host 17:41:36 if it was linked, it would be accessed when the program was ran 17:41:43 even if it didn't use any functions within 17:42:11 I am pretty sure that Bus Error indicates invalid opcodes. Doesn't it? Not a segmentation violation. 17:42:50 rwp: that would be SIGILL 17:43:11 SIGBUS is usually a memory error that's not specifically an access violation, things like accessing misaligned data for example 17:43:34 Hmm... Misaligned data access. 17:44:23 (might be some newer memory protection mechanisms also raise SIGBUG, not really sure) 17:45:58 last1, On what architecture? 17:47:44 SIGBUG!? 17:52:45 am64, 14.1 17:52:49 just upgraded the server 18:46:15 ivy: excellent news, it turns out that the hp elitedesk mini that died on me when I tried setting it up with freebsd is not dead, it was just booting into a stupid bios mode that my shitty old monitor did not want to talk to 18:46:52 on a hunch I attached it to another monitor and it was like "please enter these four digits to disable secure boot", which I am sure seriously improves the security of it or some shit 18:48:44 9991 18:49:07 anyway now I guess I can play with FreeBSD on x86 18:49:16 as a real computer that can do shit like hypervisors 18:50:20 I wanted to use this machine as a base for VMs anyway so I hope that bhyve is less annoying than connecting libvirt to systemd or whatever 18:51:16 as far as hypervisors go i have a mental model of it and the networking setup which is largely in tune with how it really works 18:52:11 sounds helpful, I hope bhyve is that 18:53:36 maybe, but the reasons for using freebsd on workstations do not involve bhyve for me. 18:59:49 i used kvm until i discovered bhyve 18:59:56 i like bhyve quite a bit better 19:04:53 https://www.reddit.com/r/sysadmin/comments/1gk2qdu/windows_2022_servers_unexpectedly_upgrading_to/ 19:13:39 one of the reasons i'm not a windows sysadmin 19:18:36 Never ever again 19:49:56 oh, I don't intend to use this as a workstation 19:50:03 I intend to use it as a little server in my data closet 20:02:53 a workstation is not dissimilar to a server. in just does personal things. 20:41:32 ok 20:50:06 Workstation = what consumer boards used to be like, with enough PCI(e) lanes etc 21:22:44 I feel like it's a crime when motd doesn't fit in 80 columns. 21:23:16 Well having an motd is a crime initsself. 21:50:32 What, you don't want people accessing your system to know that they could be subject to law enforcement if they're not entitled to access, or some legalese nonsense like that? 21:50:54 I've lost count of how many times I've seen that. 21:59:14 you must logoff immediately if you are law enforcement 21:59:17 lolol 23:44:58 * FreeBaSeDGirl use to use a bsod.ansi file for /etc/motd 23:48:29 hah