02:43:09 <_xor> What are the issues again with having an over-sized swap?
03:55:27 <yetoo> Anybody have suggestions for gigabit ethernet card with open source driver
04:15:48 <skered> yetoo: anything inteL?
04:24:15 <rwp> The standard Intel GigE ethernet cards have good free software driver support.
04:27:50 <yetoo> I'm looking for 4 port 802.1Q. Are they all open source. I'm weary of botnet from intel, but I suppose there's no choice given I can't find anything but Intel for my criteria on  bsd-hardware.info
04:28:44 <rwp> Botnet from Intel?  Reference?
04:32:19 <yetoo> rwp: backdoors in amt/ME cus gov. I'm wary of silicon backdoors or bad firmware in some soc on the card.
04:32:50 <yetoo> i know amt/me is motherboard, but i'm pointing out gov overreach
04:34:01 <yetoo> cooperation
05:34:31 <RhodiumToad> _xor: only issue with over-sized swap I know of is that the kernel will whine about maxswzone, and may be unable to use all of the swap space.
05:35:37 <_xor> I'm just going with 4G for the default size in this installer image.
05:36:37 <RhodiumToad> what arch?
05:36:46 <_xor> amd64
05:37:02 <_xor> ...though I do have a question about this really quick: https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html#dmi-specific-kernel-commandline
05:37:03 <VimDiesel> Title: NoCloud - cloud-init 23.1.1 documentationMenuExpandLight modeDark modeAuto light/dark mode
05:37:31 <_xor> "Cloud-init performs variable expansion of the seedfrom URL for any DMI kernel variables present in /sys/class/dmi/id (kenv on FreeBSD)."
05:37:57 <_xor> How does that map in kenv? Is it literally just sys.class.dmi.id?
05:38:17 <RhodiumToad> no idea
05:38:18 <_xor> I looked at a list of vars on my system and saw that they're named differently.
05:38:34 <_xor> Hmm yeah it's a bit ambigious.
05:40:08 <_xor> Like, dmi.system-uuid listed in the table on that page maps to smbios.system.uuid on my system.
05:40:51 <_xor> dmi.system-serial-number == smbios.planar.serial
05:41:29 <_xor> Wait, maybe not. There's also smbio.system.serial but it's left at the original value.
05:42:06 <RhodiumToad> smbios.system.serial="To be filled by O.E.M."
05:42:34 <_xor> Yup, mine too. I have what looks to be a valid serial string for smbios.planar.serial though.
05:42:37 <RhodiumToad> (that's what it says on mine :-)
05:42:41 <RhodiumToad> smbios.planar.serial="To be filled by O.E.M."
05:42:55 <_xor> hmm
05:45:20 <_xor> What's the syntax at the boot loader to set kenv variables?
05:45:45 <RhodiumToad> set blah=whatever
05:45:50 <_xor> oh that's simple.
05:46:32 <_xor> That's equivalent to adding my.variable.value=blah in /boot/loader.conf?
05:47:19 <RhodiumToad> yes
05:55:05 <_xor> Ooooh, I get it now.
05:55:41 <_xor> Those variable names are correct, the docs are just written...less then greatly.
05:56:10 <_xor> cloud-init knows that on FreeBSD the variable names are different. I grep'ed the source and found where it's being read.
05:56:55 <_xor> https://github.com/canonical/cloud-init/blob/6d09df5e4786a2a6c79d6098ab413c93b205221c/cloudinit/dmi.py#L24
05:56:56 <VimDiesel> Title: cloud-init/dmi.py at 6d09df5e4786a2a6c79d6098ab413c93b205221c · canonical/cloud-init · GitHub
05:58:35 <_xor> RhodiumToad: Does your system have a valid UUID for smbios.system.uuid?
06:03:56 <RhodiumToad> ... for some value of "valid" - it has a uuid-like string, but the version and type fields are invalid
06:04:06 <RhodiumToad> smbios.system.uuid="031b021c-040d-056c-4106-100700080009"
06:04:22 * RhodiumToad suspects that is not actually unique
06:07:44 <RhodiumToad> valid uuids have  xxxxxxxx-xxxx-Vxxx-Rxxx-xxxxxxxxxxxx  where V is 1,3,4,5 and R is 8,9,A,B
06:08:29 <RhodiumToad> (and V=3 or V=5 are special purpose non-random non-unique UUIDs)
06:09:44 * RhodiumToad knows way too much about uuids
06:10:52 <_xor> RhodiumToad: I was just checking my other systems and noticed the funky IDs too.
06:11:21 <_xor> I found out the hard way a good while back about how close UUIDs can be generated.
06:11:48 <_xor> I think remember seeing something in the changelog for 13.2 which addresses that.
06:12:38 <_xor> "The uuidgen(1) utility has a new option -r to generate a random UUID, version 4. 8fd1953b7eb2"
06:13:21 * RhodiumToad would like kernel support for v1mc uuids
06:13:52 <RhodiumToad> which are time-based like v1, except the mac address is replaced each time with a different random multicast address
06:14:01 <_xor> Good.
06:14:40 <RhodiumToad> the kernel uses a random multicast address for uuids on boot, but it generates the random value only once
06:16:24 <_xor> I had an issue with some template generator a while back where one of my templates was generating UUIDs in a loop...except I noticed all of the UUIDs were the exact same. After reading up a bit, turns out that there's some kind of caching behavior some UUID libs use. It wasn't just in this template generator either, I noticed it with uuidgen too at
06:16:24 <_xor> some point.
06:17:16 <_xor> It was really strange. Ended up doing some reading on various id schemas, including the various versions of UUID. I did kind of like ULIDs, but they're not widely supported.
06:18:26 <RhodiumToad> caching uuids seems... weird
06:18:58 <_xor> Yes, very.
06:20:09 <_xor> Ah, this was the issue I was running into I'm pretty sure...
06:20:10 <_xor> https://stackoverflow.com/a/45080709
06:20:11 <VimDiesel> Title: Ansible random UUID generation - Stack Overflow
06:20:50 <_xor> Oh, the caching was in the template rendering engine. Not the UUID generator.
06:21:14 <_xor> Still, kind of dumb when there's a uuid() function. You would think that would be blacklisted from being cached.
06:22:36 <_xor> https://github.com/ulid/spec
06:22:37 <VimDiesel> Title: GitHub - ulid/spec: The canonical spec for ulid
06:24:59 <RhodiumToad> "N+1 competing standards"
06:34:26 <loose_chainsaw> I have a system which is using zfs and I want to mount a disk to my home directory videos directory. I have this is the fstab. Everything works once the system is up and running but fails at boot time.
06:34:31 <loose_chainsaw> Anyone have any ideas
06:35:03 <RhodiumToad> fails how, and what is the fstab entry?
06:35:57 <loose_chainsaw> the mount is /dev/ada1p1  /usr/home/bdavidson/videos  ufs  rw 0 0
06:36:13 <loose_chainsaw> once i log in if I do a mount -a everything works
06:36:58 <loose_chainsaw> fails as in I have to enter single user mode and comment that line out and then restart
06:37:26 <loose_chainsaw> its just a normal ssd drive with a freebsd-ufs partition
06:38:05 <RhodiumToad> change  rw  to rw,late
06:38:11 <RhodiumToad> see if that helps
06:38:24 <loose_chainsaw> the issue with that is then I have to do a mount -o later right
06:38:28 <RhodiumToad> no
06:38:33 <loose_chainsaw> right
06:38:52 <loose_chainsaw> what does late add to the party
06:39:02 <RhodiumToad> the "late" flag just means it's mounted by the "mountlate" service on startup rather than "mountcritlocal"
06:39:12 <loose_chainsaw> ahhh
06:39:15 <loose_chainsaw> cheers
06:39:17 <loose_chainsaw> will try that
06:39:21 <loose_chainsaw> thanks heaps
06:40:03 <RhodiumToad> (it's the "noauto" option that stops it being mounted at all on boot)
06:40:27 <loose_chainsaw> cheers ill do some of my own googling for my own knowledge now
06:40:38 <loose_chainsaw> thanks RhodiumToad
06:40:44 <RhodiumToad> yw
06:40:50 <loose_chainsaw> exit
07:10:36 <The_Ringmaster> Hello I am having an issue within kde(x11) and I know this issue can happen on linux as well, but when I scroll up on my trackpad a 'back' signal is also sent. meaning that when browsing the web, when I scroll up, the browser will go back a page. Anyone have experience with that?
07:11:15 <The_Ringmaster> I found a fix many years ago but can't seem to find it anymore
07:20:03 <luser> xinput is likely the command you want to fix the issue.
07:20:40 <luser> Run xinput to view you inputs then run xinput -test <id>
07:21:07 <luser> As you scroll your trackpad you'll see which input is being triggered.
07:29:12 <The_Ringmaster> https://bsd.to/a0f7
07:29:14 <VimDiesel> Title: dpaste/a0f7 (Plain Text)
07:29:18 <The_Ringmaster> that's what I'm getting
07:30:22 <The_Ringmaster> not sure if a[0] and a[1] are different inputs
07:46:12 <luser> This is what I have for my mouse: xinput set-button-map <id> 1 2 3 4 5 0 0 0 0 0 0 0
07:47:06 <luser> My issue was when scrolling the back button would somehow get injected.
07:47:18 <luser> The above command disables the side buttons.
07:47:48 <luser> Similar to your issue
08:36:04 <luser> [6~
09:50:22 <luser> .
11:37:49 <bsdbandit> good moring everyone im running into an issues here im trying to change the font color of my freebsd box when it boots up instead of having the traditional white fg i want to have the color green fg on black bg ive added the following to the kernel confiuration file options SC_PIXEL_MODE , options VESA
11:38:12 <bsdbandit> ptions SC_NORM_ATTR=(FG_GREEN|BG_BLACK)
11:38:23 <bsdbandit> options SC_KERNEL_CONS_ATTR=(FG_WHITE|BG_RED)
11:39:22 <bsdbandit> and then did a make buildkernel KERNCONF=NEWKERNEL && make installkernel KERNCONF=NEWKERNEL but when i reboot its still the same traditional white color and im not sure what else to try
11:41:08 <RhodiumToad> the SC_* options are for syscons, which is the old console driver; I don't think the vt driver respects them
11:41:39 <RhodiumToad> for vt, there may be some usable options for loader.conf
11:43:10 <RhodiumToad> man vt   for info
11:50:04 <bsdbandit01> Yeah that is what I want to change is the sysconsole
11:50:08 <bsdbandit01> Color
13:19:51 <blu256> Hello, I have a problem with a recently updated FreeBSD 13.2 system. Is this a correct place to ask?
13:20:15 <la_mettrie> yes
13:20:35 <blu256> Good. The OS has become unbootable. During boot after the "Loading kernel..." and the "/boot/kernel/kernel" strings an error message is displayed which says "elf64_lookup_symbol: corrupt symbol table".
13:21:22 <blu256> After that the system hangs
13:21:34 <blu256> Any tips?
13:24:29 <RhodiumToad> can you get to the loader's OK prompt?
13:25:55 <blu256> I think so, give me a moment
13:26:31 <blu256> In any case the error happens after the boot loader so I should be able to
13:26:44 <RhodiumToad> try and boot from a kernel.old if there is one
13:26:56 <RhodiumToad> (i.e. /boot/kernel.old/kernel)
13:30:25 <blu256> no, same error. i'll try to boot from a freebsd iso
14:02:36 <blu256> I've booted from a freebsd bootonly iso. ldd'ing /boot/kernel/kernel shows an error about ld-elf.so.1. ls'ing /libexec shows that the file is there but all commands on it, such as stat, file, etc. say that the file does not exist
14:03:21 <blu256> moreover, I tried the same from systemrescuecd and it says that the file is a stale file handle
14:03:37 <blu256> this seems to imply that the file is corrupted, doesn't it?
14:13:34 <kevans> no
14:13:53 <kevans> ldd won't work on a kernel, it operates with rtld direct-exec to do magic
14:14:28 <kevans> ld-elf.so.1 must exist or you're running entirely out of /rescue
14:15:17 <kevans> (ld-elf.so.1 == rtld)
14:17:48 <blu256> so what is the problem in this case, the kernel or rtld?
14:19:25 * Dianora waves at kevans
14:20:12 <CrtxReavr> Hey Dianora - LTNS.
14:20:30 * kevans looks around the room to see if he's physically missing Dianora waving
14:20:33 <kevans> :-)
14:20:55 <Dianora> kevans: which talk are you in?
14:21:16 <kevans> loader themeing
14:21:26 <kevans> you?
14:21:31 <Dianora> ah I am in porting FreeBSD to Firecracker
14:21:51 <Dianora> I did some porting work at BSDi
14:21:56 <Dianora> so it interests me
14:22:06 <kevans> ah, nice! colin was nice enough to offer sending his slides last night since I was going to miss it
14:22:15 <kevans> felt obligated to sit in on loader talk
14:22:18 <Dianora> it's being recorded
14:22:27 <kevans> yeah, that may be a bit before it goes live, tho
14:22:39 <Dianora> I remember BSDOS crashing during boot due to a race condition in the serial driver...
14:22:43 <Dianora> it's.... annoying
14:23:18 <Dianora> I think I had to blink LEDs to find it
14:23:34 <kevans> hah
14:23:49 <Dianora> yes the good old outb(ch, 0x3f8)
14:23:53 <Dianora> I'VE DONE THAT!
14:24:17 <Dianora> One does outb('A', 0x3f8); etc. for each location you get to
14:24:39 <debdrup> Dianora: thanks for the talk :3
14:24:49 <Dianora> debrup: was it ok?
14:25:06 <Dianora> I am very rusty at giving talks. Been a long time.
14:25:09 <debdrup> Dianora: aside from the mic being upside down to start with
14:25:24 <Dianora> sorry about that.
14:25:30 <Dianora> I was still warming up anyway.
14:25:39 <debdrup> I wouldn't expect anyone to be professional about giving talks, because I'm sure I'd do poorly.
14:27:55 <Dianora> FreeBSD doesn't run very well without a timer early on
14:29:09 <Dianora> 16 chars is a hw buffer
14:29:12 <Dianora> weird
14:29:18 <Dianora> ah yes
14:31:41 <blu256> sorry, how do I invoke single user mode from the OK prompt?
14:32:03 <blu256> * nvm, I can use the menu
14:50:46 <V_PauAmma_V> blu256, "boot -s" IIRC.
14:53:21 <kevans> yes
14:53:48 <kevans> or if you really like pain, you can do it in two steps: set boot_single="YES", then boot
14:55:12 <blu256> the menu is nicer, but thank you
14:55:30 <blu256> I solved the original problem by copying the kernel from the bootonly medium to the system
14:56:21 <blu256> now I *only* have a corrupted ufs to deal with (sigh...)
14:56:28 <blu256> thank you everyone
15:26:22 <_xor> Dianora: You're porting to Firecracker?
15:26:34 <_xor> Where should I look if I want to keep an eye on that?
16:24:23 <CrtxReavr> What is firecracker in this context?
16:30:02 <meena> https://firecracker-microvm.github.io/
16:30:04 <VimDiesel> Title: Firecracker
16:31:58 <meena> https://www.daemonology.net/blog/2022-10-18-FreeBSD-Firecracker.html
16:32:03 <VimDiesel> Title: Announcing the FreeBSD/Firecracker platform
16:33:53 <debdrup> Someone isn't watching BSDcan, I see.
17:42:07 <CrtxReavr> I wish I had time for such fun. .
17:53:23 <CrtxReavr> Oooooh - FreeBSD in an AWS Lambda. . .
17:53:40 <CrtxReavr> wonder how that integrates with the whole IAM auth maddness.
19:34:05 <psionic> laaambdaaaaaaaaaa
19:34:11 <psionic> complex
19:34:25 <psionic> did they steal that from Black Mesa and Half Life by any chance
19:34:40 <CrtxReavr> No, that would have been a lot more fun.
19:48:38 <futune> realistically the half-life lambda is from physics and the aws lambda is from lambda calculus in computer science
19:49:33 <futune> well, this is my guess, who knows how they decided :)
19:51:31 <RhodiumToad> it's all Greek to me
20:00:18 <CrtxReavr> My first exposure to lambda in computer science, is essentially a function without a name in Python.
20:00:58 <CrtxReavr> And an AWS Lambda is essentially "serverless" function.
20:38:04 <last1> anyone using an IDS that can block an ip/subnet just for sending syn packets without follow-up ?
21:18:15 <debdrup> last1: check out syncookies(4)
21:22:42 <debdrup> See also: net.inet.tcp.syncache.rst_on_sock_fail, net.inet.tcp.syncache.rexmtlimit, and net.inet.tcp.minmss and some other OIDs in the net.inet MIB in sysctl(8)