00:01:07 You can boot from anything if EFI is there 00:45:47 rtprio: during installation. encrypted and in wheel group 05:10:06 debdrup: may I PM? Re: FreeBSD Docs 06:52:28 <|cos|> Good morning! I'm having trouble installing FreeBSD on an UEFI only system. Searching the web suggest one needs to fiddle with repartioning the memstick image. Is that really the case these days? 06:53:50 |cos|: no. I have installed on an UEFI only system a few months ago, using the default memstick image. I don't recall having to do anything at all 06:54:00 Hi, usually not. The default image should work fine. 07:25:35 <|cos|> Thanks! I found some kind of legacy boot option hidden in the bios after all, thus getting it booting. 07:44:40 <|cos|> ...and the machine seems to at least be able to UEFI boot the installed system... (That's what the graphical beastie means, right?) 09:31:17 jauntyd: I'd prefer it if you just asked here.. 10:40:27 what's the way to find out what module a sysctl is in? like security.bsd.see_jail_proc 10:41:31 man sysctl.conf "named /etc/sysctl.kld.d/.conf" but how do we figure out that modulename 10:49:24 it talks about kernel module specific sysctls there, I would expect that security.bsd.see_jail_proc isn't kernel module specific and even if it where it would be in a module compiled into the kernel and not loaded by rc in normal use cases 10:56:15 so what's the way to know if a sysctl is module specific or not, and what module it's from if so? 11:02:21 polyex: just grep the source code (or better yet, use ctags), and look for those sysctl declaration macros 11:02:48 the sysctl for security.bsd.see_jail_proc is declared in sys/kern/kern_prot.c, around line 1434 11:03:08 (not a module btw) 11:07:09 oprs tyvm! so does that mean security.bsd.see_jail_proc CANNOT be in /etc/sysctl.kld.d/.conf? 11:10:34 I would expect so, yes, since it's not bound to any specific kld. You can still set it in /etc/sysctl.conf though. 11:14:33 ya but that's an inconsistency in freebsd design. usually we can put config in /etc/file.conf, or /etc/file.conf.d/.conf. like how loader.conf.d can work and any other number of examples 11:14:46 that really sucks tbh no hate 11:20:01 I'm not sure what exactly you're trying to achieve here. And tbh you can probably set any sysctl (assuming it's already available) from any of the /etc/sysctl.kld.d/*.conf files, but that sounds like a misuse, since those files are supposed to be reserved for module-specific settings. 11:22:44 security.bsd.see_jail_proc is defined in kern_prot.c, which deals with general process protection; it's just part of the kernel (not a particular kld), so it only makes sense to use /etc/sysctl.conf for that right ? 11:29:01 oprs no because sometimes ppl like to build configs compositionally in multiple files instead of combined into 1 file 11:34:24 just get to the bottom question please ;-) what are you trying to achieve ? 12:04:11 oprs it's what i already said. to organize contents of sysctl.conf into their own files 12:04:46 i guess i just abuse sysctl.kld.d for that since there isn't a generic sysctl.conf.d like there should be! 12:09:03 well, you could argue for that on the mailing list or bugzilla 13:06:04 I had four FreeBSD 12.2 installations virtualized by KVM-QEMU-libvirt stack in Linux for few weeks. During that time the so to say virtual power cord of the VMs was pulled multiple times, i.e VMs were shut down with "virsh destroy". At some point I noticed that both pwd.db and spwd.db databases on all fours installations are corrupt. The FreeBSD machines were in idle state, no users were logged in, etc. Just 13:06:05 out of curiosity, any ideas what might have caused the corruption of /etc/pwd.db and /etc/spwd.db databases? There isn't a process constantly/frequently writing to those databases, is there? 14:17:47 Hi! I am facing this problem here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275760 and the patch works for me. How can I install the fixed version of bhyve? 14:19:29 is this patch available in 14.1? 14:31:55 Ronis_BR_ it looks like it's allready in the 14.1 Release: https://cgit.freebsd.org/src/tree/usr.sbin/bhyve/usb_mouse.c?h=releng/14.1&id=2ee407b6068a994bba45597c995c5ea76eec9cf3#n157 14:37:03 it was commited to stable/14 in january and releng/14.1 got created in may, so it should be in 14.1 15:45:05 mrtnt: no i would not expect those files to be open unless login is in the process of authenticating 15:45:11 but they should be able to be rebuilt 16:20:58 rtprio: ok, strange 17:23:54 no channel log? 17:25:02 wanna see if ober or anyone else replied to me after i d/c earlier. like 4-5 hours ago 17:25:22 about abusing sysctl.kld.d 17:29:06 did you see my message? (it was before your disconnect according to my client) there was no reaction of anyone else to that 17:33:41 ya about arguing with ppl on mailing list ty 17:37:21 I expect that extending where /etc/sysctl.conf is handled to load /etc/sysctl.conf.d/*.conf too is simple (but I haven't looked at it) and would guess that when you provide a patch, that it will get applied 17:40:39 what lang is the sysctl loading in? 17:42:14 seems to be handled in libexec/rc/rc.d/sysctl so sh 17:49:21 polyex: quick hack, in rc.d/sysctl, replace line 29: 17:49:23 for _f in /etc/sysctl.conf /etc/sysctl.conf.local; do 17:49:29 with: 17:49:29 for _f in /etc/sysctl.conf /etc/sysctl.conf.local /etc/sysctl.conf.d/*.conf; do 17:50:12 then you should be able to create /etc/sysctl.conf.d/, and populate it as you like 17:51:07 if it's actually that easy would you PLEASE submit a patch so everyone can benefit? 17:51:12 keep in mind that if you change /etc/rc.d/sysctl directly, your modifications may get reverted next time you run freebsd-update thoufh 17:51:21 ya exactly 18:00:35 oprs my argument for why everyone would benefit from this is it makes freebsd more consistent. ALL types of config can either be in a single file, (loader.conf) or in multiple files (loader.conf.d/) 18:00:47 it's the only exception i found so far 18:00:58 ty so much 18:05:47 anyone can submit patches, you're welcome to do it yourself ;) 18:06:06 if you do, don't forget to update the manpage for sysctl.conf 18:10:49 oprs how can i submit a patch? 18:17:04 make an acccount on bugs.freebsd.org, create a patch and write a problem report on bugs.f.o with your patch attached 18:17:54 need an email? 18:18:05 i just want to submit the patch info 18:30:43 oprs btw can't abuse sysctl.kld.d and use arbitrary somefile.conf with foo=bar 18:31:06 can someone with bugzilla account pls ad patch? 18:33:26 you would need to use a name of some kernel module you load via kld_list probably 18:36:08 ya but what module is "security.bsd..." in? 18:37:34 oprs showed that not all oids are from a module, so you can't even define them in /etc/sysctl.kld.d/*, showing yet another hole in the sysctl config story in ADDITION to the inconsistency with other parts of freebsd which is what sysctl.conf.d/*.conf would solve 18:56:38 Can 14.1 be built from 13.2? 18:58:25 there any way using ~ in .login_conf is bad and absolute path should be used instead? 19:00:20 polyex, appears multiple places in mine: https://termbin.com/hcgi 19:00:43 Well, /etc/login.conf 19:07:32 CrtxReavr: likely not 20:54:43 question.. is there any bsd client for crowdstrike? 20:55:07 no, not looking to install 22:23:26 debdrup: I was wondering if I could resume working on doc bugs? 23:26:18 pretty sure -CURRENT should be buildable from all supported releases at that time and so 14.1 should be buildable from 13.2 23:45:45 jauntyd: I don't see what's stopping you?