krjst has quit [Read error: Software caused connection abort]
krjst has joined #kisslinux
<testuser[m]>
A large portion of the C++ community have been programming without pointers for years. Some can go their whole career this way.
hackexe has joined #kisslinux
<hackexe>
Okay I know what my problem was earlier with the kernel hanging on what I thought was a PCI issue
<hackexe>
Compiling in the firmware blob for the amdgpu driver
<hackexe>
Now I get the GPUs framebuffer
<testuser[m]>
Security consultant here. The fact that Dark has no negative numbers is a huge thing. I've read countless amount of code that abused negative numbers (unfortunarely developers think they have to use negative numbers all the time if they are available) and is probably completely insecure for the simple reason that very few people manage to audit/understand the code. If it negative numbers could only be used when necessary, yes, but there
<testuser[m]>
are no technical way to enforce this.
mmatongo has joined #kisslinux
hackexe has quit [Remote host closed the connection]
mmatongo has quit [Ping timeout: 260 seconds]
<wael_>
@hackexe @testuser why does amdgpu always need firmware blobs to work
<testuser[m]>
absolute proprietary
<testuser[m]>
Just like ur wifi needs blob
<wael_>
but why is it harder than nvidia to fix
<testuser[m]>
What
<testuser[m]>
It literally just needs blobs
<testuser[m]>
to exist
<wael_>
nvidia just glibc and package and just werks
<wael_>
amdgpu require all fat firmware in lib firmware or firmware blobs built into kernel for 600mb memory taken
<testuser[m]>
Lol cuz nvidia just bundles the blob in some other way, using nouveau requires blobs just like amdgpu
<testuser[m]>
That's why their driver is 300mb junk
chomwitt has joined #kisslinux
rio6 has quit [Ping timeout: 268 seconds]
rio6 has joined #kisslinux
<wael_>
Aww
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
mmatongo has joined #kisslinux
mmatongo has quit [Ping timeout: 248 seconds]
<wael_>
phoebos: testuser: if you both said that string replacement wasnt possible without sed how come fnr() in kiss exists
<testuser[m]>
Anything is possible in a turing complete language
<wael_>
so why did you both say no
<testuser[m]>
It's possible to implement a language inside posix sh aswell
<wael_>
testuser why did you say no
<testuser[m]>
CUZ THERE'S NO DIRECT WAY TO DO THAT
<wael_>
but kiss has fnr!!!!!!!!!!!!!!!!!!
<testuser[m]>
> direct
sad_plan has joined #kisslinux
<sad_plan>
o/
<wael_>
holy shit its sad_plan
<wael_>
hello sad_plan
<sad_plan>
lol, missed me wael_ ? :p
<wael_>
im ur biggest fan!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!11111111111111111
<sad_plan>
lol
<sad_plan>
is there any background setter for X that would more likely be able to build statically linked? Ive been using bgs for a while, but it errors out when built statically linked for some reason..
<testuser[m]>
no
<sad_plan>
hm
<wael_>
patch bgs
<wael_>
try xwallpaper
<testuser[m]>
Also u should show the errors instead of saying there's an error
<sad_plan>
I dont have the skills
<sad_plan>
I was just going to. according to what it links to, it seems to be better. less extra stuff
<phoebos>
wael_: it doesn't matter, but when i said no i was replying to a different statement
<wael_>
oh ok
mmatongo has joined #kisslinux
<sad_plan>
wael_: were you planning on doing the work to create a CI for tinyx?
<wael_>
i dont use tinyx so why would i
<wael_>
actually
<wael_>
why dont we have a codeberg/github CI for all community/repo packages that use autoconf
<testuser[m]>
no
<sad_plan>
why not testuser[m] ? dont we all more or less hate autotools?
<wael_>
i do
<illiliti>
persuade upstream to pregenerate configure script
<sad_plan>
the old guidelines also said something about removing the need for autotools aswell
<sad_plan>
illiliti: I dont think thatll happen tbh :p
<sad_plan>
tinyx hasnt recieved any updates in a while
<testuser[m]>
I don't think anyone would mind, just write that trivial gh action
dilyn has joined #kisslinux
<illiliti>
wait
<illiliti>
how tinyx is related to community repo in the first place? community is wayland-only
<mmatongo>
I use hsetroot
<sad_plan>
illiliti: the use of autotools. there are several in the community which uses it.
<sad_plan>
mmatongo: does it use anything in particular except xlibs?
<mmatongo>
Hi @dilyn
<dilyn>
o/
<mmatongo>
imlib2
<mmatongo>
so imlib2 and libjpeg-turbo
<sad_plan>
which in turn require cmake. which I was trying to avoid atm. bgs uses the same stuff.
<sad_plan>
seems xwallpaper is a better option
<mmatongo>
why are you avoiding cmake
<sad_plan>
I didnt wanna bother with cmake in this project. not atm anyway.
<sad_plan>
I have a little project going on, with getting kiss properly working on oasis. mainly to build tinyx and some other stuff, but I wanna build everything up to this statically linked
<sad_plan>
I might switch kiss for something else though. ive been eying the old morpheus mk based buildsystem too
<mmatongo>
I see
<sad_plan>
yeah. having reproducable builds is also a massive hurdle for me. alot of times, things just break upon rebuild some time afterwards.. suddnely they dont build, due to missing references, which is immensly annoying with static linking :p
<mmatongo>
why the need for a statically linked os
<sad_plan>
for fun mostly, but I also just hate when things break due to api changes on libs, which breaks stuff.
<sad_plan>
having things statically linked avoids all of that stuff.
<sad_plan>
I know I cant hope to have a whole OS statically linked, due to browsers being a shitshow now days, but more or less up to that, should probably work
<dilyn>
the problem with static linking is that everything is all deps are make deps:P
<sad_plan>
how is that a problem? I see that as a benefit. makes me able to remove everything else than exacly what I need. its amazing
<mmatongo>
sorry to digres but does anyone know how to use tinyalsa
<sad_plan>
I do
<sad_plan>
doesnt it work for you?
<mmatongo>
cant seem to increase my volume
<mmatongo>
tinymix set 0 100
<mmatongo>
-> Error: invalid value (100)
<sad_plan>
did you enable master?
<sad_plan>
master playback switch
<sad_plan>
else no volume works at all
<mmatongo>
how do i do that from it, it was already enabled so no idea
<sad_plan>
then you can adjust the master volume to, well adjust the volume
<sad_plan>
for me its: tinymix -D 1 set 13 1
<sad_plan>
-D is for card, 1 is my card
<illiliti>
check /dev/snd permissions
<sad_plan>
13 is the ctl
<sad_plan>
14 is switch I mean. 13 is master volume
<sad_plan>
to adjust the volume from there; tinyxmid -D <card> set 13 5+ or 5-
<mmatongo>
okay it was the permissions
<mmatongo>
working now
<mmatongo>
Thanks sad_plan & illiliti
<illiliti>
nice
<sad_plan>
youre welcome C:
mmatongo has quit [Remote host closed the connection]
litharge has quit [Quit: restarting]
litharge has joined #kisslinux
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
mmatongo has joined #kisslinux
<mmatongo>
is someone checking on ehawkvu
<mmatongo>
they are trying to build a bsd kiss
<mmatongo>
I am both excited and concerned
<sad_plan>
he isnt trying. he has already done it. the building of it is just abit wonky atm
<sad_plan>
why concerned? :p imo, thats great news, getting kiss-bsd
<sad_plan>
theres been talk of it for a long time now
<sad_plan>
im waiting for a tarball release, and I wanna test it out tbh
<mmatongo>
I can't imagine the hardware support would be all that great
<mmatongo>
*expansive
<sad_plan>
freebsd isnt that bad, is it?
<sad_plan>
I know not all bsds has great hardware support, but iirc, freebsd isnt that bad. openbsd i.e. is afaik worse
<mmatongo>
It's not, got a chance to use it a few months back
<dilyn>
sad_plan: my point is that any update will always take substantially longer on a static system because you have to avoid problems like missing symbols
<dilyn>
it's a bad thing in the sense that it takes longer and is less efficient, but that's not a "bad thing" so much as a "consequence of a design decision which is sound in principle"
<mmatongo>
is oasis entirely static or just some parts of it?
<sad_plan>
mmatongo: cool. ive yet to try any bsd tbh.
<sad_plan>
all of it
<sad_plan>
dilyn: thats a price Im willing to pay. most software Ive built statically linked anyway, isnt all that big, so rebuilding it doesnt really take all that long tbh
<illiliti>
freebsd is the only os where you can disable ipv4. i'm tempted see how old shit breaks on it :) it's great feeling
<mmatongo>
I imagine everything would break
<mmatongo>
Disastrously
<sad_plan>
why do you insist on not using ipv4 again, illiliti ? Ive forgotten
<sad_plan>
I personally dont even use ipv6, due to sdhcp not supporting it at all
<wael_>
i dont care about either i just want internet
<illiliti>
i have many reasons to drop ipv4
<sad_plan>
wael_: I dont really care all that much either, or rather, I dont understand it enough, to have an informed oppinion on it.
<illiliti>
for example, isp's dpi only works for ipv4
<illiliti>
ipv6 is 100x faster because of that
<sad_plan>
ah
<dilyn>
but how will you connect to canonical.com without ipv4 illiliti
<dilyn>
sad_plan: you're talking the person who insisted on building a fully-static system :P
<dilyn>
just the trades you make. not a bad thing, just a thing
<illiliti>
nat64 dilyn
<illiliti>
necessary evil
<mmatongo>
canonical.com :D
<sad_plan>
I would want a fully static system, if I were able to do so. I got a long way, but was met with gtk+3 needing mesa to build... so couldnt build webkit2gtk
<illiliti>
my isp plans to setup nat64 for everyone, so i can drop mine
<mmatongo>
What country are you from
<mmatongo>
My ISP can't even give me a stable 4 connection
<illiliti>
ru
<illiliti>
but my isp is the only one that pushes ipv6