<riteo>
I henceforth invoke the power of timezones to say "happy birthday" to kris_ despite it being 5 AM here
<riteo>
happy bday kris_!!!! x333
<kiedtl>
latest firefox build is up
<kiedtl>
actually, what browsers do folks use in here? I know midfav uses palemoon, does anyone at all use a qt5-webengine browser? the package was seemingly broken for a while
denshi has quit [Quit: denshi]
_whitelogger has joined #kisslinux
<midfavila>
kiedtl: i don't use pale moon
<midfavila>
i use links2
<midfavila>
i haven't used a graphical browser in years
<midfavila>
outside of firefox in a vm or container
<midfavila>
for like, government shit
<midfavila>
although come to think of it i could probably use surf for that
<midfavila>
also aaaaaaaaaaaaaaaaaaaaaaaaa holy shit everything is so fucking expensive
<midfavila>
a single pair of halfway decent work slacks is a hundred dollars
* midfavila
dies
<midfavila>
entire day's wages
_whitelogger has joined #kisslinux
fultilt has quit [Quit: Leaving]
<Vova>
hi everyone, what's your tactic to manage the kernel, do you create a package an put your .config in, or do you manage it externally like get the sources in /usr/src/Linux or something and just make && make install
<sewn>
vova
<sewn>
you're using kiss
<sewn>
why would you still use /usr/src
<sewn>
make a linux package blehhh
riteo has quit [Ping timeout: 260 seconds]
<Vova>
because let's say you're on 6.15.2 and you don't update for a while, now you decide to upgrade to 6.??, what do you do, you just change the source and the version and you shove your .config and just make && make install ? because maybe there's new kernel options and so on, so you need to make a make oldconfig to see what's new
denshi has joined #kisslinux
denshi has quit [Client Quit]
<sewn>
uhuh
<sewn>
the package can do that for u
<kiedtl>
genuine question, what would make you update the kernel?
<kiedtl>
for me it'd just lie there for 2 years until I realize it's super out of date, and then lie there for another 2 years before I finally convince myself to update it
<thomas_adam>
CVEs, version bumps, GKH told me to...
<kiedtl>
thing is
<kiedtl>
I don't really care that much about CVEs
<kiedtl>
unless it's open to the internet
<kiedtl>
like, unless it's a bugfix that's actually affecting me, or some cool new perf improvements...?
<thomas_adam>
That's OK -- you've chosen to decide for yourself -- but I would say: s/kernel/$ANOTHER_PROGRAM/, and it's the same question.
<kiedtl>
fair. I still have ptsd from windows.
<Vova>
tbf, I don't have a strong reason to update the kernel, I guess once every 6 months is good enough
* kiedtl
only updates void/arch installs once the package manager starts complaining about conflicts
* kiedtl
hasn't updated their windows laptop since 2022
<thomas_adam>
You also likely won't have the requisite knowledge to decide; besides, updating the kernel is one thing, but do you reboot? I don't, and hence, I've taken the update, but it's not applied. So it's all moot.
<kiedtl>
lol
<kiedtl>
true about the prereq knowledge
<kiedtl>
I guess for other stuff, like firefox or aseprite, I'm more likely to hear about some feature I want and decide to upgrade
<thomas_adam>
So don't treat it any different; an update is just an excuse for a distro to bundle changes together, is one reboot really going to harm things? I doubt it, and you'll be reaping the benefits without really worrying about it.
<thomas_adam>
There's been a research project going on for years about noexex (ISTR) where kernel updates happen in-situ so you don't need to reboot. So if/when that happens, you'll have no excuse. :)
<kiedtl>
true :)
<kiedtl>
though for kiss there's a little extra friction (i.e. building)
<thomas_adam>
Oh indeed.
<thomas_adam>
But that comes with the decison to use Kiss, and doesn't affect the points above.
<kiedtl>
fair enough
<thomas_adam>
kiedtl: I could tell you that $PROGRAMX segfaults if you used it on a Wednesday. I could fix that, put an update out, and let distros package it. If you used $PROGRAMX, would you accet the fix or not? It might not be that clear in the release notes. Same for the kernel, I couldn't tell you what's worthy of a rebuild or not, but it's the acceptance of using a compiled distro which means you
<thomas_adam>
likely can't decide.
<thomas_adam>
Anyway, I know you get the point. :)
<kiedtl>
that's true
<kiedtl>
for me if I encounter a bug I'll usually keep tabs on the changelogs for that package
<kiedtl>
or use something different
<kiedtl>
but yeah for a compiled distro it's just whatever the maintainers decide for sure :)
<thomas_adam>
:)
fultilt has joined #kisslinux
oceanicc has joined #kisslinux
oceanicc has quit [Remote host closed the connection]
phinxy has quit [Quit: WeeChat 4.5.1]
<kris_>
riteo thanks
phinxy has joined #kisslinux
<kris_>
Vova generally that's more or less what i do, i just use some other distros config typically though