02:59:30 <kindrobot> Hey all, I just installed freebsd14 and in the installer, the wifi works, but on boot, it doesn't. I'm seeing "iwlwifi0: ERROR: lkpi_ic_scan_start: hw_scan returned -5" on the tty
05:41:12 <|cos|> kindrobot: i recognize wifi troubles when first installning, but do not remember the exact error message. are you able to get it working if going through the steps of https://docs.freebsd.org/en/books/handbook/network/#network-wireless manually?
05:41:13 <VimDiesel> Title: Chapter 7. Network | FreeBSD Documentation Portal
07:30:25 <babz_> crb: zfs list -p -o name,creation -t snapshot
09:00:11 <yourfate> i sometimes run gameservers in a linux compatibility system
09:00:22 <yourfate> I chroot into that, but then I'm root, and I don't want to run the game servers as root
09:00:41 <yourfate> but I don't have my regular users in there, do I have to create new users in the linux chroot?
12:32:53 <V_PauAmma_V> yourfate, I think so.
13:27:51 <yourfate> ooooh I just found out about unprivileged chroot
13:27:54 <yourfate> that would be nice
13:28:03 <yourfate> so I could just chroot from an unprivileged user
13:28:08 <yourfate> and not have to recreate them in linux
13:28:24 <yourfate> it says its enabled by `security.bsd.unprivileged_chroot`, how does that work?
13:29:10 <yourfate> sysctl --help
13:29:11 <yourfate> oops
13:30:25 <yourfate> found it
13:30:30 <yourfate> its done with sysctl
14:37:45 <yourfate> ok, I also copied the user entry to the passwd file in ubuntu, so it has a name for the ID
14:37:59 <yourfate> now my valheim server runs as an unprivileged user in linux compantibility, which is nice.
16:37:58 <beastwick> Hi, I am trying to setupa Linux thin jail following the handbook, but when I try to start the jail, after setting up the template and then the base container, I am getting: jail: mount.devfs: /usr/local/jails/linux/dev: No such file or directory
16:38:15 <yourfate> it seems the mounts are not set up right
16:38:29 <yourfate> did you set up the mounts in fstab, and run `mount -a`?
16:38:37 <yourfate> ah, and start the linux service
16:39:53 <beastwick> yourfate: yes I setup linux on the host and ran the service. The handbook says to not perform any jail configuration, and it gives a long cli command to run to start initially.
16:43:07 <yourfate> hmm then you probably need someonw that knows about jails
16:43:13 <yourfate> I only use the compat layer without jails
16:43:32 <beastwick> np, I will see if I can figure it out
17:47:06 <F0ma> hello
17:47:25 <anexit> Well this camera wasn't what I wanted
17:47:27 <anexit> crap
17:47:39 <mzar> hello F0ma
17:47:52 <F0ma> hey mzar
17:48:35 <F0ma> need advice
17:52:31 <F0ma> have problem with disk, when try download file to my mounted additional disk disk unmounts and couldn't be mounted then run fsck and could mount it back again. does it looks like file access issue?
17:53:41 <F0ma> i use transmission for file download
17:53:47 <mzar> what's the filesystem on this disk ?
17:53:55 <F0ma> ufs
17:53:58 <F0ma> it is
17:54:40 <mzar> that's supported FS, no advice from my side, but perhaps someone else will give you better advice
17:57:42 <F0ma> no problem, thanks
17:58:51 <mzar> perhaps the system panics frequently during this file transfer and after reboot disk is not in consistent state ?
18:01:43 <F0ma> restar shoul work too i think
18:14:36 <mzar> F0ma: OK, if you don't want dirty filesystem after panic, use ZFS
18:18:29 <F0ma> ok I think about that thanks
18:21:16 <polarian> I have just thought about it, FSF has pretty strong opinions on free meaning freedom not free as in free beer... what does the "free" in FreeBSD mean?
18:21:23 <polarian> FreedomBSD or FreeBSD (as in free beer)
18:21:37 <polarian> (thanks fsf for causing so much confusion when free is used in naming)
18:23:16 <deimosBSD> polarian: https://docs.freebsd.org/en/books/faq/#why-called-FreeBSD
18:23:17 <VimDiesel> Title: Frequently Asked Questions for FreeBSD | FreeBSD Documentation Portal
18:23:38 <polarian> dammit I forgot to RTFM again
18:23:40 <polarian> also hi deimosBSD
18:24:12 <deimosBSD> that might not fully answer your question though
18:24:34 <deimosBSD> tldr: bsdi charged for BSD OS, freebsd didn't
18:24:53 <deimosBSD> the far longer answer is https://klarasystems.com/articles/history-of-freebsd-unix-and-bsd/
18:24:54 <VimDiesel> Title: History of FreeBSD – Part 1: Unix and BSD | Klara Inc
18:26:11 <deimosBSD> it was originally 386bsd, etc
18:27:30 <polarian> which also what netbsd forked
18:27:31 <polarian> and the netbsd was forked into openbsd
18:27:31 <polarian> due to deraadt controversy and being kicked out
19:09:54 <polarian> I am struggling to find two things I need, 1. some guide/article on separate partitions and mount options, the handbook touches on it, and OpenBSD has a good explanation on useful mountflags to increase security, but I am wondering if there is something for FreeBSD on this topic
19:10:26 <polarian> and 2. multiple FDE pools/disks
19:10:41 <polarian> will GELI always prompt for decryption of anything in the fstab?
19:11:47 <polarian> I know it prompts for the boot disk... but what about additional storage mountpoints?
19:12:18 <polarian> if someone could provide good articles on both of these, it would be highly appreciated,
19:20:08 <saper> polarian: /etc/rc.conf can have geli_devices="...."
19:21:37 <polarian> saper: that variable is waht prompts you for decryption on boot?
19:22:02 <polarian> checked rc.conf(5), it is thanks :)
19:22:25 <polarian> easier than I thought, what about 1 though :)
19:24:13 <saper> polarian: no
19:24:33 <saper> the bootloader ask for the boot device, and then the userland, once it is running
19:25:11 <polarian> hmmm right ok
19:25:30 <polarian> so it will be decrypted in the userspace after init?
19:31:29 <saper> some time during the processing of rc scripts
19:32:33 <saper> (I actually had a problem recently - the bootloader did not open both of my ZFS mirrors, only one device, so I had to geli attach another disk manually and "zpool oneline pool anothervdev" to sync the mirrors again ('resilver')
19:35:31 <polarian> yikes now that is scaring me
19:35:57 <saper> don't worry
19:36:12 <saper> if you are booting from the ZFS mirror you will know what you are doing for sure :)
19:36:43 <saper> I really like that our third stage loader can do stuff like decryption and ZFS. No need for initrd or such stuff.
19:37:31 <saper> and that /boot/pmbr fakes GPT support \/
19:41:08 <polarian> I know nothing about the FreeBSD boot cycle :P
19:41:16 <polarian> I believe its in the handbook though...
19:41:37 <polarian> im sure there is a ton of books you can buy about *BSD boot process
19:43:20 * |cos| just struggled to convince pkg to force upgrading all ports, and still seem to have the exact same builds. Does that mean that step wasn't needed when going from 14.0 to 14.1?
19:49:13 <kenrap> ah, I forgot that 14.1 will be officially announced tomorrow, sweet.
19:51:05 <kenrap> |cos|: All 14.x releases use the same ABI, so no rebuilds necessary
19:51:18 <kenrap> Same with every major release
19:56:18 <|cos|> thanks. makes sense. i hope someone is a bit amused of how persistant i was in getting that unnecessary action done. :)
19:59:45 <saper> |cos|: some time ago my pkg database got corrupted. still finding some ancient stuff in /usr/local/bin that has never been updated since, as those files no longer belong to anything.
21:10:09 <vext01> hey, I've got a zfs volume here that's acting as a device node for a linux vm virtual disk
21:10:30 <vext01> i've just expanded the zvol, but what's the easiest way to resize the linux partition?
21:10:43 <vext01> is there something easier than fdisk?
21:10:55 <vext01> as far as I know, I can't used gpart for this?
21:15:31 <vext01> ah, had to set the devmode to full
21:28:54 <tmp_> Using "u-boot", is there anything to be done in the case of: XHCI timeout on event type 33 ?
21:30:10 <tmp_> I've tried adding the offending device to usb_ignorelist, but that makes no difference in this case.