00:26:13 <mcrane> anyone trying out the nanopi r5s
00:27:49 <mcrane> https://personalbsd.org/?p=1202
00:27:50 <VimDiesel> Title: PersonalBSD.org » FriendlyElec NanoPi R5S
00:28:54 <mcrane> FreeBSD has support for the NanoPI r4s
00:29:31 <mcrane> but the R5S is a nice upgrade from the R4S
00:30:17 <mcrane> whats so cool about this little ARM device
00:30:37 <mcrane> 3 Ethernet ports and NVME
00:31:14 <mcrane> anyone have docks on how to go about adding support for a new ARM device
00:32:35 <mcrane> the device is slightly larger than a Raspberry Pi only bi a few extra mm
00:34:23 <mcrane> there is also a new nanopi R6s with 8K HDMI and two quad core CPUs
00:45:04 <mcrane> FreeBSD working good on the Raspberry Pi4. Just they are too popular for their production rates.
01:19:14 <Chargen> re
02:20:02 <RoyalYork> is the file resolvconf.conf suppose to be in /etc ? or is it in another directory?
02:28:16 <RoyalYork> Okay, so it looks like resolvconf.conf is suppose to be in /etc and it looks like I removed it by mista...i mean it disappeard
02:28:35 <RoyalYork> Where can I find a copy of the default resolvconf.conf
02:45:40 <rtprio> RoyalYork: it should be in /usr/src
02:46:06 <rtprio> like /usr/src/contrib/openresolv/resolvconf.conf
02:46:06 <rtprio>  
02:49:31 <RoyalYork> Thanks. I never installed the source files or though to check there online
02:49:36 <RoyalYork> i'll have a look
02:51:22 <RoyalYork> got it thanks. According to resolvconf(8), the file should be in /etc. A straight copy and paste into etc should suffice?
03:00:26 <rtprio> yah
03:01:24 <zykotick9> I'd just like to extend a big "thank you" to someone who I don't remember the nick of...  a couple of days ago LLVM compiling on systems with < 16GB RAM came up, today I can confirm with 16GB RAM on an amd64 compile it fails, when there is 64GB of RAM it works.  Someone in this channel was BANG ON <- again, thank you to that mystery person.
03:03:59 * zykotick9 notes compiling LLVM (which was the problem) & chromium & a small handfull of other packages took approximately 8 hours :(  - on a xeon 12core 2.5Ghz machine
03:03:59 <RoyalYork> Thanks for your assistance with getting the resolvconf.conf file
03:04:49 <RoyalYork> zykotick9: I must have missed the original conversation. Why did you opt to compile and wait as opposed to getting a package?
03:07:53 <zykotick9> RoyalYork: I have two "identical" machines (minus RAM, one with 64GB one with 16GB) I use pkg on one, and ports on the other...  my allocation of RAM was teporarily reversed for need (usually the big RAM is used for ZFS with some dedeup) but this LLVM compiling issue with 16GB showed up - and someone noted it!
03:09:00 <RoyalYork> wow
03:10:10 <zykotick9> wow, is right.  I hope the FreeBSD univers can extend my gratitude to that person.
03:28:16 <RoyalYork> Night all
07:34:16 <tuaris> Why did this port build with PHP 7.4 even though I had 8.0 set as the default version: https://pkg.ny-us.morante.net/poudriere/data/12amd64-default-saturn/2022-12-09_01h36m10s/logs/php74-pear-channel-horde-20160602.log
07:36:47 <meena> zykotick9: which part of LLVM are you specialising, that you need to compile your own port?
09:05:36 <meena> tuaris: Flavour != Version
09:06:22 <meena> tuaris: https://docs.freebsd.org/en/books/porters-handbook/book/#flavors
09:06:25 <VimDiesel> Title: FreeBSD Porter's Handbook | FreeBSD Documentation Portal
11:41:47 <meena> it's funny that the original malloc(3) paper from phk is available on the new docs pages https://docs.freebsd.org/44doc/papers/malloc.html but the "new" one is only available via https://papers.freebsd.org/2006/bsdcan/evans-jemalloc/
11:41:48 <VimDiesel> Title: malloc
11:44:19 <meena> has anyone here attempted to tune jemalloc(3) via /etc/malloc.conf?
12:08:21 <mictty> wut
12:09:14 <meena> mictty: which part is causing you confusion?
12:10:59 <mictty> meena: any word, xlloc, excites me
12:13:48 <meena> well, have fun reading papers and man pages
12:15:27 <meena> oh, right, now i remember how i got here, https://github.com/hercules-team/augeas/pull/792
12:15:29 <VimDiesel> Title: Remove `#include <malloc.h>` by ZhongRuoyu · Pull Request #792 · hercules-team/augeas · GitHub
12:18:40 <mictty> meena: is some of my code wrong and are you advising me? if so can you be more specific. I am afraid if i am missing out
12:34:05 <meena> mictty: that pull request is how i got to wondering if we have malloc.h, and what our current malloc implementation even is.!
12:39:03 <mictty> meena: I didn know meena. I had to read both llvm and freebsd codebase
12:41:17 <mictty> meena: oh, that `#include <malloc.h>` PR. it is not mine
12:42:17 <mictty> meena: i was confused with mine. you are talking about augeas
14:11:58 <clapont> hi, everyone! how are the things?
14:23:27 <RoyalYork> clapont: we're good today
15:01:44 <mictty> fg
15:01:53 <mictty> oh it was right
15:02:11 <mictty> sorry i think i am sleepy. Bye
15:04:12 <RoyalYork> :help
15:15:31 <_xor> Can I run `gpart resize -i 3 ada0 && pool set autoexpand=on && zpool online -e zroot ada0p3`
15:15:37 <_xor> on a live system?
15:16:20 <_xor> I think I remember expanding before without issue, but don't remember if I booted into single-user first. Obviously would be safer to do it in single-user, but just wondering if it's no big deal to do on my current system.
15:17:34 <RoyalYork> Quite the question. I'd like to see what the experts here have to say on it too
15:22:20 <debdrup> _xor: Using autoexpand and autoreplace, I've pulled disk(s) from my SAS chassis and inserted new ones, and had it automatically detect and use the new disks for replacements.
15:22:44 <debdrup> autoreplace is basically just a handler for zfsd, iirc
15:22:57 <_xor> Worked fine.
15:23:32 <debdrup> Also note, set autoexpand=on before you do anything, and ZFS should expand as soon as you resize the partition.
15:23:46 <debdrup> Setting autoexpand after you've expanded means it won't work.
15:24:42 <_xor> Right, it'll do it after zpool online -e ...
15:24:55 <_xor> I had autoexpand on though and it filled it as soon as I resized it.
15:24:58 <debdrup> That'll force the expansion irrespective of whether autoexpand is on or not.
15:25:24 <debdrup> _xor: might've missed a camcontrol reprobe or rescan
15:25:55 <debdrup> That can sometimes be necessary when dealing with disks with partitions.
15:26:18 <debdrup> https://freshbsd.org/freebsd/src/commit/f0878da03b374e3fa3578b363f02bfd50ac0e5bd A commit that's more comment than code is always nice.
15:26:20 <VimDiesel> Title: FreeBSD / src / f0878da03b374e3fa3578b363f02bfd50ac0e5bd - FreshBSD
15:27:45 <Helper> i thought he was a Linux kernel guru
15:27:57 <Helper> alan cox
15:29:35 <Demosthenex> Helper: i think he's just a guru =]
15:29:52 <Helper> indeed he is.
15:30:12 <Helper> I wonder what ever happened to Richard stallman and his coding lifestyle.
15:30:35 <debdrup> Probably not the right channel for that conversation.
15:31:54 <debdrup> alc@FreeBSD is a different Alan Cox than whoever you're talking about, I'm pretty sure.
15:32:28 <Helper> lol
15:41:55 <RoyalYork> I was about to buy the book Absolute FeeBSD 3rd Edition for $70. But then found it at my local library. When I went to pick it up, it looks like I was the first to check the book out
15:42:25 <RoyalYork> I can renew this thing forever (until someone else decies they want to be the next in line)
17:18:22 <laidback_01> first link on Google for Absolute FreeBSD takes me to Amazon.  First link on Yandex takes me to a readable PDF on ihatefeds.com  remember to check multiple search engines, the results differ amazingly...
19:56:33 <_xor> LOL
19:57:14 <_xor> So I just managed to figure out why my keyboard media keys (e.g. play, pause, etc) weren't working. Fixed it and then bound them to invoke playerctl.
19:57:53 <_xor> playerctl takes the -a argument to specify "all players"
19:58:09 <rwp> _xor, What did you need to do for your keyboard media keys?
19:58:31 <_xor> I was just listening to a song on YouTube and testing out the buttons to check if they were setup. Well...
19:59:12 <_xor> I hit play/pause (which toggles it, obviously), and the song stopped playing through my headphones. Great, it works, but then...
20:00:05 <_xor> I heard some faint audio coming from outside my headphones. I took off my headphones and noticed that my PHONE is now resuming playback of a video of a TV episode I was watching earlier.
20:00:16 <_xor> No, my phone isn't connected to my desktop.
20:00:53 <_xor> playerctl is possessed by something that emerged from the obvious rip in the space-time fabric I somehow created.
20:01:46 <_xor> (Obviously, it's either connected via WiFi somehow or the media system I'm using is getting the playback event somehow and broadcasting it to my phone app)
20:03:04 <_xor> rwp: I didn't need to do anything, but I wanted to because I have too many key chord bindings which are global and taking up space unnecessary when the keyboard is capable of sending specific keycodes for those actions.
20:08:21 <_xor> Oh, figured it out. It was KDE Connect.
20:08:42 <_xor> Didn't know that it implemented MPRIS.
23:51:05 <rwp> _xor, That would be pretty freaky to pause the play and then have it resume elsewhere.  Poltergeists!
23:52:01 <rwp> But I think that it should have *paused* not *disconnected*.  If I disconnect my bluetooth phone headphones then I expect the phone to resume it.
23:52:06 <rwp> But if I am playing audio and pause the audio and then turn off the headphone then I don't expect audio play to resume.
23:52:19 <rwp> Glad you got it figured out.  That kind of thing would be surprising.