13:16 <Vova> Hi everyone, do you know if this is normal or not, in mdev.conf, I can't match against PRODUCT, I checked the uevent of the device I want to match and the PRODUCT appears in it, so I put a catch all rule inside mdev to execute "env > /tmp/$$" (inside a shell script) to see what env were passed, and there's no PRODUCT env, only a SUBSYTEM, MDEV and ACTION env

13:19 <Vova> mdevd works tho

14:54 <kris_> i tried to make waffles today and discovered that waffles and pancakes require different recipes

14:54 <kris_> (i failed horribly)

16:15 <Vova> busybox or sbase+ubase or toybox ?

16:23 <midfavila> ubase+sbase :3

16:23 <midfavila> kris_: yeah

16:23 <midfavila> i hope they were still tasty tho

16:29 <kiedtl> toybox is missing a lot iirc

17:15 <thomas_adam> Yes, toybox is still unfinished, and isn't that comparable to busybox.

17:15 <thomas_adam> Even Alpine hasn't switched to it.

18:04 <kmf> kisslinux fries my laptop, help pls

18:10 <Vova> under clock the cpu

18:13 <kmf> I did the cpu scaling thing and installed and configured TLP too, But it is still too hot and I can't handle it.

18:16 <kmf> I'm logging out, must put my laptop to sleep, open the lid and keep blowing until it cools down again, pls help me.

19:02 <riteo> Vova: TIWAGOS but I think that PRODUCT might be like nonstadard or something

19:03 <riteo> I needed to make a script for that, with a bunch of subsystem-specific subscripts or something

19:08 <riteo> https://codeberg.org/Riteo/kiss-scripts/src/branch/main/doc/managing-devices.md

19:21 <Vova> riteo thanks for your link, it contains some very useful stuff !

19:23 <Vova> BTW if you want a "lighter" and cleaner dbus you can use dbus-broker

19:24 <Vova> it should be compatible with dbus ootb

19:24 <Vova> https://github.com/bus1/dbus-broker

19:40 <sewn> Vova: requires systemd to be useful

19:40 <sewn> libdbus is fine

19:41 <sewn> no reason to swirch

19:45 <Vova> what ?

19:45 <Vova> I thought you could use dbus-broker with systend

19:46 <Vova> systemd*

19:48 <sewn> arch does

19:48 <sewn> kiss can't because it needs libsystemd

19:49 <Vova> ah fuck

19:51 <Vova> sewm are you sure it depends on libsystemd ?

19:51 <Vova> https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/testing/dbus-broker/APKBUILD

19:51 <sewn> sewm

19:51 <sewn> yeah

19:51 <sewn> the launcher

19:52 <Vova> and on their readme it's stated that libsystemd is only required for the launcher

19:52 <sewn> and to run your Wayland session in dbus

19:52 <sewn> you use launcher

19:52 <sewn> lmao

19:52 <sewn> dbus-launch sway

19:52 <Vova> I won't lie I know jack shit about dbus

19:52 <Vova> I just know it's required for notifications

19:54 <sewn> lmao

19:54 <sewn> vova its just easy ipc

19:55 <sewn> to share info and call things to do things

19:57 <Vova> yeah I know but why is it needed

19:57 <Vova> why peoples decided to use it

20:00 <sewn> the peoples use systemd vova

20:00 <Vova> true

20:00 <Vova> also, anyone here uses sndio ?

20:02 <sewn> I'll eat them

20:04 <Vova> sewn do you use fnott or any notifications displayer ?

20:05 <sewn> I use mako

20:05 <sewn> fnott doesn't work with chromium so

20:05 <Vova> mako requires dbus ?

20:05 <Vova> so you use the dbus or libdbus with it ?

20:07 <Vova> and speaking of, it seems that chromium finally fixed their thing for fnott sewn, https://codeberg.org/dnkl/fnott/issues/85

20:08 <sewn> oh right

20:08 <sewn> well fnott still sucks either way lol

20:08 <sewn> Vova: mako uses basu

20:08 <sewn> which is a libdbus but not suck

20:08 <sewn> you need to know dbus-broker is not a dbus implementation

20:08 <sewn> it is a dbus server

20:09 <sewn> so many projects can still depend on libdbus

20:10 <Vova> I don't understand anything :sob:, so a "dbus" implementation needs a "manager" (or a "server", idk how it's called), and the app using it will send their messages to the "manager", and manager will route the messages to the corresponding destinations right ?

20:11 <Vova> libdbus is a low level dbus implementation, which is just a lib right ?

20:12 <Vova> so even if I install libdbus for something that needs libdbus I'd still need to have a manager ? and to start the manager (either system wise, or user wise with dbus-run-session for example)

20:16 <sewn> suuure

20:16 <sewn> its a client-server model

20:17 <sewn> its like wayland

20:17 <Vova> yeah I see

20:17 <sewn> there is libwayland and then waylanndd ccomposiitors

20:17 <sewn> thheye implemennr rserverr sides of wayland

20:17 <sewn> and ccliennrs ccan use libbwayland

20:17 <sewn> or usee sommething else

20:18 <Vova> so what do you use for the "dbus server" ?

20:18 <Vova> oh wait I just saw, basu is a dbus "server" right ?

20:27 <sewn> Vova: the one from libdbus, dbus-daemon

20:27 <sewn> much like a Wayland's Weston

20:27 <sewn> Vova: no, basu is a libdbus

20:27 <sewn> not a dbus server

20:27 <Vova> alright

20:27 <sewn> I don't choose lol

20:27 <sewn> it just is de facto

20:28 <sewn> kiss-dbus as well

20:28 <Vova> I thought libdbus was just providing a lib for communicating with a dbus server

20:29 <sewn> correct

20:29 <sewn> its precisely that

22:21 <midfavila> oh my gooooooooooooooooooooood i hate summer

22:21 <midfavila> it's way too hot

23:46 <oceanicc> what exactly are the differences between gkiss and kiss tarballs? like the stuff in /usr/ and /etc and stuff

23:47 <oceanicc> all I know is that musl is swapped out for glibc idrk anything beyond that

23:56 <oceanicc> I kinda tried just running a diff between both the extracted tarballs, but the diff file is 169mb soooo