#kisslinux

Unofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://yewtu.be/watch?v=S81bNIK4MaE
Earlier messages
<sewn>report it!
<sewn>personally I'm sick and tired of kiss ash
<sewn>on alpine my shell history is thousands of lines long
<dilyn>i certainly will. just gotta test it
<dilyn>:v
<dilyn>too many
<sewn>on kiss it lasts only 100 commanrs
<sewn>let alone 50
<sewn>and I reuse them a lot especially on alpinr
<dilyn>cd
<dilyn>ope
...
<sewn>huh
<dilyn>OPE
<dilyn>loksh is *also* effected, as it turns out? confused.
ghodawalaamanjoined
<ghodawalaaman>I see #kisslinux is revived by the community, I thought it's dead, sorry for my ignorance
<ghodawalaaman>currently flashing gentoo livegui to install kisslinux
ghodawalaamanquit (Quit: coming back after booting into live usb)
Guest8joined
<Guest8>hello
<Guest8>I just booted into Gentoo live image
<Guest8>now trying to install kisslinux
<Guest8>why there is two chroot tarballs in the release page?
<Guest8>which one should I use?
<Guest8>just extracted the first chroot tar ball and everything looking fine so far
Guest8quit (Quit: Client closed)
<sewn>there are two?
<sewn>one of them is a shasum
<sewn>endigmng with .tar.xz is da real one
<dilyn>there's one with -2, description in the notes says some folx reported errors with the original tarball
<dilyn>I'd recommend using the second one...
<sewn>ahh
dilynquit (Ping timeout: 240 seconds)
<riteo>oof wanted to say something to dilyn right now
<riteo>in doubt, I'll start writing now and let the logs do their stuff
<riteo>dilyn regarding stack smashing note that musl has a TINY default stack size
<riteo>I had issues with ffmpeg and vulkan decode because it assumed that it could casually dump 123KB of stuff in the stack just for that
<riteo>can recompile with `--extra-ldflags='-Wl,-z,stack-size=SIZE` or I think there's some library function for increasing the stack size I think
<riteo>(FTR, musl has a 128k stack)
<sewn>never had stacking problems lol
<sewn>till I enabled it
<riteo>maybe they made it more efficient lately for unrelated reasons
<riteo>the problematic struct was `StdVideoH264ScalingLists`
<riteo>which was getting statically allocated 32 times
...
fultiltquit (Quit: Leaving)
...
phinxyquit (Ping timeout: 276 seconds)
dilynjoined
<dilyn>riteo an excellent point; on glibc however (ubuntu) I get a message about being unable to alloc
<dilyn>so I think it's a ksh problem here
<sewn>born to use kiss forced to use ubuntu
Later messages