ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://vid.puffyan.us/H7PvgY65OxA
dontmindmee has quit [Remote host closed the connection]
<testuser[m]> Hi
<testuser[m]> US National Security Agency tells developers to shun C and C++ programming language
<vulpine> what do they want people to use instead? rust?
<illiliti> ada
<wael_> Hi
<illiliti> hi
<wael_> Hi illiliti
<wael_> Is it better to have most things managed by KISS (eg. Rust (cargo), Python (pip), etc.)
<illiliti> yes, preferably
<wael_> What about flatpak apps
<wael_> Such as uhhhhhh Gimp or Krita or really any big well used app
aliosablack has joined #kisslinux
<illiliti> i would not bother
<wael_> So keep using flatpak basically?
anon has joined #kisslinux
<anon> Hi
<anon> illiliti: are you using nouveau?
anon has quit [Client Quit]
<testuser[m]> wael: wdym
<virutalmachineus> <testuser[m]> "US National Security Agency..." <- perfect, When is kiss switching to rust?
<wael_> if it means it wont fucking go down again ill accept it
<wael_> sad_plan: honestly suprised this thing booted and now i have a functional system
<wael_> also how do I make linux show tty as soon as possible
<wael_> when linux is loaded it takes a while to show the tty
<testuser[m]> make ur boot thing not wait for anything else before spawning gettys
<wael_> I don't mean the speed, I mean the display
<wael_> it stays total black till the tty login is displayed
<wael_> I'd believe linux outputs very late due to some kernel option
<wael_> and yes I have loglevel at maximum
<testuser[m]> skill issue
<testuser[m]> wdym
<testuser[m]> u want the dmesg log before tty or what
<wael_> Yes
<testuser[m]> send ur init details
<wael_> Wdym?
<testuser[m]> init system
<wael_> Default?
<wael_> Oh yeah it only shows after the welcome to KISS thing, before init is launched basically is just dark
<wael_> Also the linux tuz 224color doesn't appear either
<wael_> Tux
<wael_> Might be something with my BIOS maybe(?????????¿?¿¿¿¿?)
<wael_> Nope
<wael_> atleast made the tux stuff show
<wael_> @testuser do you face the same linux display thing
<testuser[m]> no
<wael_> send kernel config
<testuser[m]> no
<macslash1[m]> Lo
<testuser[m]> illiliti: phoebos can kiss be changed to only chroot for post-* if KISS_ROOT Isn't / ? https://codeberg.org/kiss-community/kiss/src/branch/master/kiss#L187
<testuser[m]> this breaks the kiss chroot builder script cuz it runs build under bubblewrap (without setting KISS_ROOT) and chroot can't be called inside it
stjohn has quit [Read error: Connection reset by peer]
<testuser[m]> or ig ill just fake chroot binary in PATH cuz the use case is hacky anyway
<testuser[m]> b3sum'd tars ready
Torr has joined #kisslinux
rohan has joined #kisslinux
<rohan> yo guys
<rohan> someone was able to use hyprland in kiss?
<cem> illiliti: I don't have the patch but I just remembered that it was just a one-line change
<cem> Just changed this to PAX_IS_HARDLINK
<cem> Same with L731
<testuser[m]> rohan: bruh i literally wrote a full patch that day when u asked
<testuser[m]> About hyprland
<wael_> what did the patch do
<testuser[m]> Ifdef x code
phinxy has quit [Quit: WeeChat 3.5-dev]
phinxy has joined #kisslinux
<illiliti> wael_: yes
<illiliti> anon: i don't
<illiliti> testuser[m]: feel free to make this change
<illiliti> cem: i see. thanks
<wael_> hi illiliti
<illiliti> hi
<testuser[m]> illiliti: ioraff phoebos: can you check this tarball
<illiliti> on it
<illiliti> works fine for me
rohan has quit [Ping timeout: 256 seconds]
rohan has joined #kisslinux
hackexe has joined #kisslinux
<hackexe> Would it make sense to remove the installed binary for a package in the pre-remove script? I notice `kiss r` does nothing with the binaries after 'removing' a package.
<illiliti> what's the point
<illiliti> binaries is a cache anyway
<hackexe> No reason other than keeping 'that part' of my mind sane, i.e. having everything clean, pristine, organized. Which right now isn't really important so I was mostly wondering if anyone else did that hah
<hackexe> illiliti: nice work on tinyramfs btw. Gotta love the minimal, no bullshit solutions like that.
<illiliti> well, you can write pre-remove hook then
<illiliti> maybe kiss should have it by default via some variable like KISS_PURGE, but i don't see much benefit in it
<hackexe> I agree, in fact it's already creating more work which isn't truly necessary. Thanks, illiliti
hackexe has quit [Remote host closed the connection]
<phoebos> testuser[m]: looks good
<phoebos> dbus-free bluetooth? can it build on linux?
<illiliti> freebsd-only