00:44:18 <polyex> 14.1 shaping up to be the best release ever
00:44:46 <jbo> glad to hear that
00:44:49 <jbo> hopefully no ZFS drama
00:45:06 <polyex> ya that could be bad
00:45:26 <polyex> zfs rewrite in rust would be gold
00:45:48 <jbo> stop
00:46:53 <polyex> well it helps catch bugs
03:36:22 <polarian> polyex: heresy, does this look like Linux?
05:28:20 <polyex> you mean successful? progressively not, no. rust is better than C there's just no debating it
07:13:36 <edenist> polyex: I'm not against rust from a language perspective. My main issue with it is portability and bootstrapping it, which currently is a real pain
07:17:21 <polyex> ya i think its compiler is like 75mb. just got an idea, what if there was a really naive simple compiler distributed instead of the official one
07:17:38 <polyex> like 5mb and just doesn't make as fast code but it can bootstrap
07:17:54 <polyex> maybe that's what cranelift is
07:21:40 <rennj> https://en.wikipedia.org/wiki/Commodore_BASIC bill gates got the shaft, "I'm already married,"
07:21:41 <VimDiesel> Title: Commodore BASIC - Wikipedia
07:21:48 <rennj> basic in rom
07:21:53 <rennj> vic20 style
08:32:32 <hubertm> after installing gdb on raspberry pi 4 and trying to start it, i just get "command not found" and if i try its file /usr/local/share/gdb i get "permission denied" (even though permissions are OK)
10:52:57 <crest> has anyone used varnish as an on-site cache for the official package mirrors?
11:04:18 <montar> anyone knows how can I directly access LPT port to use it as GPIO, is it even possible?
11:04:19 <dch> crest: not to my knowledge, I have done this in the past https://forums.freebsd.org/threads/local-cache-for-pkgs.60859/#post-365296
11:04:20 <VimDiesel> Title: Local cache for PKGs? | The FreeBSD Forums
11:04:52 <dch> stupid question of day, given a panic & subsequent crash dump how do I "connect" to it?
11:05:21 <crest> dch: one reboot the system should save the core it dumped to swap to a file
11:05:25 <crest> *on reboot
11:05:35 <crest> iirc via the savecore rc.d script
11:05:43 <dch> crest: yeah I have that file
11:05:56 <dch> I want to do `bt` and stuff in it
11:06:13 <dch> this is 14.1-RC1 crapping its pants on airport wifi
11:06:45 <dch> aah https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-gdb
11:06:46 <VimDiesel> Title: Chapter 10. Kernel Debugging | FreeBSD Documentation Portal
11:06:48 <dch> kgdb
11:07:15 <crest> iirc the (k)gdb file command is what you're looking for
11:07:37 <crest> to point it at the kernel
11:07:46 <crest> and the core command to point it at a specific kernel dump
11:10:14 <dch> ok in panicmail I see `  Panic String: sleeping thread`
11:34:49 <dch> looks like a linuxkpi / iwlwifi issue again
11:38:56 <crest> does iwlwifi depend on linuxkpi and its incomplete reimplementation of the linux driver APIs or does it just clash in general to annoy you^^ ?
11:39:28 <crest> did you encounter this on amd64 or arm64?
11:40:05 <crest> if it only happens on arm64 it could be an other example of code expecting the more restrictive x86 memory model
11:40:37 <crest> TSO (total store order) instead of whatever your specific arm64 core would do
11:56:22 <dch> crest: this is my boring laptop and it needs intel wifi which is either old if_iwm, or new iwlwifi which requires linuxkpi
11:56:53 <dch> its super annoying, I'm continually on the verge of installing almost anything else, just to have usable wifi speeds :-(
11:56:55 <crest> does if_iwm still limit you to 802.11n throughput?
11:57:10 <crest> dch: how about openwrt inside bhyvE?
11:57:26 <crest> there is a ready to use port for that
11:57:30 <dch> crest: not doing that path as a matter of principle
11:57:59 <dch> if we dont eat the dogfood then freebsd-as-a-{desk,lap}-top is dead
11:58:39 <crest> agreed, but sometimes you need a workaround for the annoying 5% to get to enjoy the other 95%
11:59:50 <crest> dch: i have varnish working as a PoC
12:00:21 <crest> it's nice to have curl fetch packages at line rate (even more locally)
12:02:03 <crest> the next question would be should i be honest and update the pkg.conf on every system or should i just hijack the names and run them through a transparent cache?
12:07:58 <dch> definitely the latter
12:08:43 <dch> I wish we'd gone the path of collaborating with netbsd and openbsd on their reimplementation of wifi
12:09:12 <dch> but as I'm only testing the code, not writing it, my wishes are not really relevant
12:43:13 <jbo> lw, ping
13:54:29 <polarian> hmm... chromium has a lot of CVEs being reported https://dpaste.org/7fuTj
13:54:30 <VimDiesel> Title: dpaste/7fuTj (Python)
13:54:45 <polarian> still no port update for it
13:54:57 <polarian> firefox is being updated though... so I assume firefox is easier/better maintained?
13:55:27 <crest> dch: did you verify that your nginx cache really works and serves cached packages?
13:57:00 <crest> i'm asking because pkg.freebsd.org will serve packages with Cache-Control: max-age=0 and Cache-Control: private
13:58:39 <crest> which disables shared caches in a more or less sane default configuration
13:59:48 <crest> because it's both already stale and should only added to private caches which neither nginx nor varnish should consider themselves
14:32:11 <polarian> how do you set a gtk4 theme on FreeBSD... I have tried in the config but its just ignored, the only thing that seems to work is setting GTK_THEME
14:32:23 <polarian> but this only works if you launch from the shell
14:32:28 <polarian> using a launcher you cant do this
14:34:01 <trashboat> my friend, set the env var
14:34:10 <trashboat> in your .profile or somewhere
14:34:23 <polarian> trashboat: launchers do not pick up on these
14:34:33 <trashboat> well then your launcher sucks
14:34:45 <trashboat> put it in /etc/environment or equivalent
14:34:47 <polarian> I beleive I already tried .profile with rofi
14:34:57 <trashboat> try .bashrc?
14:35:02 <polarian> I am not using bash
14:35:05 <polarian> this isn't Linux
14:35:13 <trashboat> ..what!? where am i??
14:35:17 <trashboat> oh yeah.
14:36:24 <trashboat> .cshrc?
14:36:35 <trashboat> thats what youre looking for.
14:37:13 <trashboat> setenv GTK_THEME adwaita or whatevs
14:45:00 <polarian> hmm
14:46:18 <polarian> I am using sh not csh
14:46:34 <polarian> BUILTIN(1) states sh doesn't support setenv
14:53:12 <trashboat> i dont even know what you mean by "launcher"...but it sounds like its a script. put it there.
14:53:13 <debdrup> Yea, setenv is a Cshell-ism. With anything related to Bourne, you just set it by typing it: ENVVAR=foobar
14:53:39 <trashboat> debdrup: where would you put it so that it is set on login?
14:54:10 <trashboat> you could also change your shell to csh
14:54:28 <debdrup> ~/.shrc
14:55:17 <debdrup> you can also use ~/.login if you want something that gets applied to all shells, but you need to ensure what you're doing is compatible with both Bourne and C-derived shells
14:56:05 <debdrup> for an example of the default .shrc that freebsd provides (which has at least one environment variable), check /usr/share/skel/dot.shrc
14:56:10 <tmp_> Depending on setup, .shrc may be called everytime you run a shell. If you want something to run once, on login: .profile
14:57:22 <debdrup> oh right, ~/.profile is also a thing
14:57:44 <trashboat> eh said that wasnt working
14:57:53 <trashboat> s/eh/they
14:58:33 <debdrup> what wasn't working?
15:02:41 <polarian> trashboat: rofi
15:03:05 <voy4g3r2> then you throw in zsh and there is the whole ~/.config/zsh stuff :)
15:03:28 <debdrup> ...
15:03:35 <polarian> debdrup: I am not sure if rofi will pick up on the env variables though
15:04:28 <debdrup> that seems like a rofi issue then
15:05:20 <llua> zsh doesn't read files from there thankfully
15:06:25 <debdrup> procstat(1) can show which environment variables have been set for a given process
15:06:47 <debdrup> thank fuck for whoever wrote the stats(7) page, because that's how i found it :D
16:23:29 <polarian> trashboat and debdrup sticking GTK_THEME in .profile or .shrc doesn't have any affect on rofi
16:26:46 <trashboat> polarian: how are you calling rofi?
16:26:54 <trashboat> init script?
16:26:57 <trashboat> put it there
16:27:05 <polarian> hm
16:27:21 <polarian> its a keybind
16:28:47 <trashboat> put it in the commad line that calls rofi, wherever it is
16:29:04 <polarian> trashboat: doesn't work attempting to change the keybind in i3 config will not work
16:29:21 <polarian> bindsym $mod+d exec --no-startup-id rofi -show drun -font "Ubuntu Mono 10" -theme "gruvbox-dark" -show-icons
16:29:43 <trashboat> put setenv in there
16:29:57 <polarian> where...
16:30:03 <trashboat> sorry ENVAR
16:30:11 <trashboat> whatever makes it work
16:30:21 <polarian> try sticking it before exec breaks exec
16:30:28 <polarian> after exec breaks
16:30:34 <trashboat> i would try right be rofi
16:30:43 <trashboat> and maybe it will need quotes
16:31:00 <trashboat> i'm not the expert just thinking of how i would accomplish what you are after
16:31:24 <trashboat> *right before rofi -sorry
16:32:06 <trashboat> but wait
16:32:17 <trashboat> what user is i3 running as?
16:32:39 <trashboat> i guess you were trying with that user
16:33:29 <polarian> trashboat: thanks worked
16:34:40 <trashboat> excellent
16:35:02 <polarian> I don't get why specifying the font in the gtk config work s
16:35:07 <polarian> but specify a theme doesn't
16:35:13 <polarian> gtk such a pain in the arse
16:35:22 <polarian> and my configs have too many linuxisms in it currenttly
16:35:22 <trashboat> 100%
16:35:32 <polarian> seen as they were used on Linux and adapted for BSD
16:35:33 <trashboat> qt even worse
16:35:56 <polarian> welp it works now, so thats all that matters :P
16:36:07 <trashboat> cheers
16:36:22 <polarian> and gtk3 applications still use the gtk3 theme as I wanted... perfect
17:25:50 <al1r4d> I just bought #FreeBSD from Indonesia VPS Provider with the following specs:
17:25:51 <al1r4d> 1 GB of RAM, 1 vcpu, 10 GB NVMe SSD
17:25:51 <al1r4d> If you have similar VPS, how can you tune performance and harden the server?
17:43:28 <polarian> well you can start off by reading the handbook on it: https://docs.freebsd.org/en/books/handbook/security/
17:43:29 <VimDiesel> Title: Chapter 16. Security | FreeBSD Documentation Portal
17:47:07 <polarian> its not exactly mandatory... its always about trade off between usability and security
17:49:54 <polarian> there is a whole heap of sysctl stuff you can do but some have major performance impact
18:18:00 <debdrup> meena: are you around for the devsummit?
20:30:12 <makr> are binary packages being updated more frequently now?
20:31:22 <makr> `pkg upgrade` seems to suggest upgrades more frequently now
20:35:48 <rwp> It might depend upon if you are on Quarterly or Latest.
20:38:56 <makr> rwp: i'm on latest
20:39:17 <rwp> I would expecdt Latest would have more updates more frequently than Quarterly.
20:39:35 <polarian> chromium obviously isn't :P
20:39:40 <polarian> its been vulnerable for like a week now
20:39:51 <makr> rwp: yes, but i've been on latest for a while
20:40:01 <makr> last couple of weeks or so updates are more frequent
20:40:05 <polarian> how stable is latest compared to quarterly
20:40:17 <makr> previously you'd get updates like once a week max
20:40:30 <polarian> makr: firefox is updated very often it seems on quarterly
20:40:30 <makr> very stable
20:40:47 <makr> possibly security updates
20:41:03 <polarian> most firefox updates are security updates :P
20:41:13 <makr> haha
20:41:22 <rwp> I am on Quarterly and get frequent Firefox updates.
20:41:24 <polarian> it must cost a fortune to pay for the amount of compute to build for all the different versions and the different branches (latest/quartly etc)
20:41:34 <polarian> rwp: do you use chromium?
20:48:58 <rwp> I have Chromium installed but I only use it when a site requires Chromium.  Otherwise I use Firefox all of the rest of the time.
20:49:48 <rwp> 85% of the world is using a Google Chromium based web browser.  That's not a healthy ecosystem.  Wish things were better.
21:03:14 <polarian> rwp: that is what I do, but if you have done pkg audit -F
21:03:20 <polarian> chromium has been vulnerable for a while now
21:24:44 <rwp> One of the problems with CVEs is that people now use them for complaints about stupid things.  "rm removed my file, I think that's a security problem, CVE!"  And so now I just don't know if a CVE indicates a real problem or just someone being stupid.
22:07:05 <voy4g3r2> rwp: can't it just be retracted.. reason for closure: stupidity?
22:32:38 <rwp> voy4g3r2, We could only hope.  We could only hope.