ChanServ changed the topic of #kisslinux to: KISS Linux | https://kisslinux.xyz | logs: https://k1sslinux.org/irc#2.0 | please read: https://k1sslinux.org/news/20210712a
<dilyn> `make install` is just a long way to type cp
<sad_plan> I suppose it is. its way more convinient anyway
<sad_plan> in any case, its been fruitless as of yet.
<claudia> what is the problem?
<sad_plan> the package im trying to create is onetrueawk. and it only produces an executable called a.out.
<sad_plan> currently now its this bs permissions as always. cp cant create the dir it needs. classic
claudia_ has joined #kisslinux
<claudia_> when using 'cp' in a buildfile, you need to create the dir first
<claudia_> mkdir -p "$1/fofoofofo"
<sad_plan> that ive done
<sad_plan> looksie here
<claudia_> cp a.out "$1/usr/bin/onetrueawk"
<sad_plan> how could I forget.
<claudia_> when double clicking on a link in foot, it just selects everything but the https://
<sad_plan> I must say, the filename is rather unfortunate. I cant open it or anything. lol
<dilyn> ln -sf a.out /usr/bin/awk that's just a broken link
<dilyn> you renamed a.out
<sad_plan> had to redownload and rename it beforehand
<sad_plan> aah
<claudia_> has one maybe found a config option, to select all? This is one thing I like very on 'st'
<dilyn> foot recently had a rework on links and interacting with them. or something
<dilyn> i don't know, i didn't read the changelog lol
<claudia_> I use the keybind to open in browser extensively.
<dilyn> ew
<claudia_> :(
<sad_plan> so I have to rename it first, then symlink? I want it to work with kiss a anyway
<sad_plan> fuckin hell, the file you sent is really annoying. its called -VmW.sh. I cant seem to either rename, remove it or anything..
<illiliti> rm -- -VmW.sh
<sad_plan> amazing
<sad_plan> what are the -- for? I mean, what do they do? havent seen them before in any help files or anything
<dilyn> they specify that the next parts of the argument are not option flags
<sad_plan> cool
<dilyn> so if you avoid install, just mkdir -p "$1/usr/bin", cp (or mv) a.out "$1/usr/bin/nawk", ln -s nawk "$1/usr/bin/awk"
<claudia_> 'show-urls-copy=' is what I am looking for.
<sad_plan> it worked. cheers again
<sad_plan> dilyn: when building statically, Ive notied that alot of buildscripts in your repos, sometimes only use --disable-shared, while not using --enable-static. is it sufficient to just disable shared, or whats the reason for the difference? package breakage?
<dilyn> it just depends on what the authors of the package's build system sets as the default options
<dilyn> some set both --enable-{static,shared}, some set --enable-static & --disable-shared, some set --enable-shared & --disable-static
<dilyn> so you just have to check
<dilyn> more often than not the default is to build both though, so you just need --disable-shared
<sad_plan> ah, I was under the impression that most of the time its built only dynamically, but oh well. probably why Ive had alot of breakage when trying to build gcc/binutils statically earlier. usually just ended up with ld not working..
<dilyn> of course that's only for building the library itself; if you want the binary to be built statically you'll have to pass -static or --static, sometimes there's an option in the build system to build the binary statically (less common)
<dilyn> yeah building a static gcc and binutils is... not obvious
<dilyn> :)
claudia has quit [Ping timeout: 268 seconds]
<sad_plan> is those listed in the configure scripts help list, or do I need to open it, and find it manually?
<sad_plan> I figured as much. spent way too much time trying to build anything after building them, and not being able to.
<dilyn> USUALLY you can find all the build options available by passing ./configure --help (or meson configure, or... cmake has one, i forget what it is tho; -G or something?)
<sad_plan> was peeking at wyverkiss' llvm script, and got abit sad, as it was already set to static. felt like cheating tbh :p and here I am trying to build binutils/gcc statically when theres a massive shortcut right there
<dilyn> other times you'd have to look through it yourself to see what it checks for...
<sad_plan> nice
<dilyn> ah, llvm is harder to build statically than you might think
<sad_plan> but someone else had already configured it so, so I wouldnt have to. altough Im unfamiliar with other building systems, so Id probably got stuck before Ive even began anyway :p
<dilyn> it got 'easier' with llvm 12 because now libc++abi can just be static and built into libc++, which is great. but building any libLLVM* statically can be hard (specifically LTO, Remarks, a few others)
<dilyn> it's mostly just trial and error to force a static object out of a build system lmao
<dilyn> CFLAGS=-static didn't work? Try --static! libtool fucking womps
<sad_plan> thats nice though. always great when updates actually makes things easier for oneself, and not the other way around.
<sad_plan> is lto/pgo even harder with static linking? I seem to recall statically linking was mentioned when I was reading about it the other day..
<sad_plan> I dont recall, but I did a quick build of some packages in a wyverkiss chroot, with -static as CFLAGS, and I was just sitting there, wondering; where are all the errors? why is nothing failing? lol
<dilyn> they shouldn't really be any harder, I don't know specifics on how it would impact performance
<dilyn> if I understand LTO/PGO correctly, things should *only* get EVEN faster
<sad_plan> even better
<dilyn> ah, that's because nothing cares about libLLVM :P just libc++ and libc. it's pretty neat
<dilyn> it's all very wonky. I don't trust people who make Makefiles any more.
<sad_plan> well looks like im going in for a nice ride when I eventually go over to llvm/clang instead of binutils/gcc. instead of a bumpy ride I mean.
<dilyn> sometimes it's just easier to make all the objects files and ar them yourself lmfao
<dilyn> llvm is the way :V
<sad_plan> I get that. makefiles are messy sometimes
<sad_plan> yeah :D
<konimex> > it's all very wonky. I don't trust people who make Makefiles any more.
<konimex> hear hear
<sad_plan> do you even use clang for that much stuff? I noticed clang isnt even packaged in the wyverkiss' repo.
<konimex> clang is a part of llvm
<sad_plan> aah
claudia_ has quit [Quit: zzz]
<sad_plan> ok so im peeking binutils help page, and is it safe to assume when a feature is listed, the oposite is default? i.e. --enalbe-lto is listed, but its disabled by default, yes?
<sad_plan> unless its specified on the text i mean
humky has joined #kisslinux
<dilyn> i usually assume that when they list --enable-foo, foo is disabled by default. though some will list whether or not it's on or off by default
<dilyn> a lot of things default to auto and do a check of some kind as well
<sad_plan> yeah, I noticed static libs were auto, or something, for gcc I belive, or both, I dont recall at the top of my head
<sad_plan> dilyn, do you use CFLAGs -static, or do you run without it? does it even matter really? I mean, its specified in the buildscript anyway, so wouldnt it be redundant to have it both places?
<dilyn> -static in CFLAGS is fun
<dilyn> so it depends on whether or not I have shared libraries on my system, and if the thing I'm building is a shared library
<dilyn> you can specify linking against a static library (CFLAGS=-l:libfoo.a), though this results in a lot of unecessary (unused for smart linkers) flags
<dilyn> but there isn't a one-flag-is-all-you-need rule. for instance, vim
<dilyn> if I only specify -static in CFLAGS for vim's build, I get this when I ldd /usr/bin/vim http://ix.io/3tod
<dilyn> if i use -static in LDFLAGS, however, I get "ldd: /usr/bin/vim: Not a valid dynamic program"
<sad_plan> Ive notied that some builds have specific cflags exported in their buildscripts, so I figured.
<sad_plan> so even though you specify cflags -static, it still doesnt?
<dilyn> the real kicker is that -static is a linker flag ;)
<dilyn> so if -static never gets passed to your linker in whatever way, the linker won't... do the thing
<sad_plan> lemme get this straight, setting -static as cflags i.e. for vim in this case, does not make it buid static libs, so its basically useless, but if you use it as LDFLAGS instead, it works?
<dilyn> I should have written all this down when I was embarking on this madlad of a project huh
<sad_plan> yep
<sad_plan> :p
<dilyn> so -static is a linker flag that specifies the ways in which an object should be linked
<dilyn> a static library is literally just an archive full of object files which contain symbols; a shared library is more like... a pointer, though that is the wrong (confusing) word
<dilyn> a static library will have all the symbols a program which links to it would need in order to execute all of the things that program would expect to have access to by linking to that library
zenomat has quit [Ping timeout: 255 seconds]
<dilyn> as such, -static is simply a command for the linker. so sometimes, adding -static to CFLAGS works because $CFLAGS get prepended to $LDFLAGS, or get added to the $(LD) command in a Makefile.
<dilyn> but not everyone does that (some Makefiles you'll see things like $(LD) $CFLAGS $CXXFLAGS $LDFLAGS, others you'll just see $(LD) $LDFLAGS, or whatever)
<dilyn> you can use something like '-Wl,' to pass a flag directly to the linker, in which case you might have been better off just using LDFLAGS (though NOT ALWAYS)
zenomat has joined #kisslinux
zenomat has quit [Changing host]
zenomat has joined #kisslinux
<dilyn> for instance, CFLAGS="$CFLAGS -Wl,-static" in our vim example also doesn't work
<sad_plan> why not?
<dilyn> I'm not sure; I'd have to read the Makefile to see what's going on; presumably the build system isn't calling cc for the link step, but rather ld directly
<dilyn> if clang is called during the link step, it's plenty smart and will do all the magic for you
<dilyn> to get even more fucky with you, -static doesn't guarantee that the outcome of your operation will be static in the case of a library. you can slam static objects into shared libraries if you like
<dilyn> it doesn't go the other way, however, unless you compile that shared library with -fPIC
<sad_plan> I was compiling stuff with that flag, what exacly does that do? I seem to recall it being about shared libs
<dilyn> to get a standard library out of your building, that's when something like --disable-shared during the configure step is useful. because now if the build system supports that option, the build system will avoid making a shared object and JUST create your static archive
<dilyn> it's for position independent code; it's a whole other thing I don't quite understand
<dilyn> on a surface level it makes your compiled objects bigger :P
<dilyn> it 'avoids the limits of the global offset table', which means roughly that all of your symbol locations are now relative to this table instead of being set while building
<dilyn> the linker does a LOT of work. it's the unsung hero of our modern era
<sad_plan> ok :p I have a feeling that statically linking is an absolute mess. Im also starting to get why mcf bypasses the makefiles altogether. so he doesnt have to mess with peoples bs makefiles :p
<dilyn> oh almost certainly that is a part of the reason why he did it...
<dilyn> it's only a mess because nobody knows how to write proper Makefiles :'(
<sad_plan> for sure. ive been starting to view alot of makefiles as of late, seeing as Im trying to package stuff from time to time, and theyre an aboslute mess all of them..
<sad_plan> should be a somewhat of a standard instead. oor that would perhaps just make people create more standards, and we be in the same situation as with some package managment software... im looking at you red hat..
<necromansy> yeah idk about making a standard but rather reinforcing a good base template for simple products
<necromansy> then making sane extensions :P
<necromansy> makefiles are neat in concept but a fucking mess irl
<dilyn> honestly meson is pretty fucking tight
<dilyn> very readable
<noocsharp> is that boson fork ready yet?
<noocsharp> first repo when you visit sr.ht: https://butts.tech/
<dilyn> amazing
<dilyn> muon is more ready than boson afaik
<sad_plan> necromansy: that would be a great start obviously :p
<sad_plan> dilyn, is that why you use meson in your repo?
<dilyn> eh
<dilyn> i use meson when it makes sense to or when I want to avoid gmake
<dilyn> for instance if I can usually guarantee that meson will already be available when building some package, i'll default to using meson for it
<sad_plan> and how does one know if you can use meson for said package or not?
<dilyn> if it has a dependency that requires meson I'll take that as being sufficient
<dilyn> this is a very loose sense of 'guarantee'
<sad_plan> sounds resonable :p
<sad_plan> why are you using gmake anyway? when make is bsd licences anyway
<sad_plan> or rather bmake is..
<dilyn> because some people don't know how to write makefiles!
<dilyn> ifneq is not understood by bmake (:
<sad_plan> I see
<necromansy> is there actually any reason that people choose certain makes?
<dilyn> portability, pretension...
<dilyn> choose your indoctrination
<necromansy> i thought make was very portable?
<dilyn> I feel like a god
<necromansy> i mean im just asking out of legit curiosity
<necromansy> ive only ever written barebones make files for simple C and groff projects
<dilyn> gmake, like most GNU things, has gnuisms that are not shared by other *makes
* necromansy shrugs
<dilyn> gmake is... perhaps more powerful, especially for larger projects
<dilyn> I don't know enough about make to really be able to tell you; I imagine it has very good build-order dependency resolution, but I don't know how much better that could be over something like bmake
<dilyn> i just know that gmake has a larger syntax than bmake, and a lot of makefiles leverage that syntax whether out of ignorance or fanboyism i do not know :X
<dilyn> konimex: maybe knows what gmake can do better than bmake
<necromansy> fair fair
<noocsharp> dilyn: are you a fucking animal?
<noocsharp> put return types on your functions
<dilyn> k&r baybeee
<dilyn> ALE is not a fan :V
<dilyn> int main() so boring tho
<dilyn> the next question is a histogram for character frequency instead of word length and I want to be an absolute mad lad and use divide and conquer to determine which letter it is instead of like... a sane way
<sad_plan> where did you find that course? :') it looks.. simple :p
<dilyn> I'm just reading through K&R
<necromansy> picking up where mid left off
<dilyn> lmao
<sad_plan> k&r?
<sad_plan> ¯\_(ツ)_/¯
<dilyn> for now, at least. I might find something very interesting to do before I finish and switch to a different book
<dilyn> the c programming language by kernighan and ritchie
<sad_plan> aaah
<dilyn> it's been in my backpack or on my desk for about two years, and i'm finally cracking it open
<sad_plan> about time :p
<dilyn> xD
<noocsharp> i was gonna say, the only way you can justify using it to use c is if you own a physiscal copy
<noocsharp> to learn c*
<dilyn> c#
<noocsharp> c--
<sad_plan> D!
riteo has joined #kisslinux
<riteo> hiiiii!
<necromansy> heyhey
<sad_plan> hey
<dilyn> o/
<riteo> does anybody know if there's a POSIX solution to disable pipe buffering?
<riteo> I'm trying to make curl's output nicer by passing it through some filter, but even with just tee piped right after it the output comes out in chunks
<dilyn> http://ix.io/3tox this is... slightly off
<riteo> I feel like this could be shorter and simpler, somehow
<dilyn> perhaps
<dilyn> most of the character counts are right, and some are wrong. which I find hilarious.
<dilyn> oh no, it's right
<dilyn> smfh i conflated A and a. vim is just case sensitive with its search
<dilyn> am dumb
<riteo> epic
<riteo> so the offness you were talking about was about the result?
<riteo> I thought it was about the code itself, like, in the way it read
<dilyn> oh, no the result lol
<riteo> oh
<dilyn> I was staring at all these indices and loops for so long and couldn't figure it out, and then i put a A in the code and realized my mistake XD
<riteo> lol
<dilyn> i'm so proud of me
<dilyn> next step, a compiler
<riteo> yes
<riteo> I should properly learn C too
<riteo> probably I'll make minek lol
<dilyn> lol
<dilyn> you learn about file operations in chapter 7 of k&r. soooooo...
<dilyn> this is gonna be a while i think
<riteo> it's gonna be worth it though
<riteo> just imagine: a minecraft launcher slightly faster than a properly optimized script, at hundreds time the size
<riteo> aren't you exited?
<riteo> s/exited/excited/
<noocsharp> i imagine it will be hundreds of times faster if properly optimized
<riteo> we'll see
<noocsharp> i think you underestimate the toll that an interpreter takes
<riteo> yes
<riteo> but I have no sense of scale yet
<riteo> writing c programs will probably help me allieviate that
micr0 has quit [Remote host closed the connection]
<riteo> now I feel like I'll start earlier than expected, you actually made me properly question my perception of shell scripts and C programs
<riteo> thanks!
<noocsharp> no problem: remember an interpreter has to convert the language to machine code on the fly, and then execute the machine code
<noocsharp> an executable just has to run the machine code
<riteo> I know that, but now I feel like I really understated that
<riteo> thinking about it I already got said something similar not too long ago
<riteo> epic
<testuser[m]> Hi
<riteo> hi!
<riteo> god is pipe buffering even defined in the POSIX standard
<riteo> http://expect.sourceforge.net/example/unbuffer.man.html >bugs: the man page is longer than the program
<riteo> lmao
sad_plan has quit [Quit: ]
<riteo> I'm starting to feel like that any attempt of prettyfing in real time any command's output on POSIX alone is impossible
<noocsharp> such things may require a real programming language
<riteo> well, in that case you might ditch altoghether the command being prettified
<riteo> and just use a lib or w/e
<riteo> fuck it, I'll keep the output chunky
<testuser[m]> Riteo where's the minekiss repo
<riteo> repo?
<riteo> oooh right
<dilyn> i got to what i thought was about halfway through that answer and... not even a quarter lmao
<riteo> I'm dumb, I though like, kiss the package manager's concept of repos
<riteo> it's still not out yet
<riteo> it's still bad
<riteo> if you want I can share it though
<riteo> let me make a gitdab account and I'll share the link
<testuser[m]> Why not put it on shithub directly
<testuser[m]> No one is gonna bully you
<riteo> well because I wanted to slowly migrate to gitdab
<riteo> exactly because shithub's what it is, shit
<riteo> ok I'll put it on shithub
<testuser[m]> which one is gonna survive longer than the next 10 years though
<riteo> right
<riteo> with or without the whole extra shitty repo history?
<acheam> sr.ht
<acheam> because its foss
<acheam> and emails last forever
<testuser[m]> With history
<riteo> ohoh prepare for shit
<acheam> gitlab dies when they run out out of venture capital
<riteo> acheam you don't get it
<riteo> it's gitdab
<riteo> with a d
<riteo> it's an actual service based on git tea
<acheam> oh yeah you linked that earlier
<dilyn> >emails last forever
<dilyn> I delete all of my emails
<acheam> yeah gitdab is the dabbity dabbity
<riteo> dilyn forgot to mention that he does that obliterating time itself
<dilyn> truly
<dilyn> the world was created on a thursday, and is destroyed every wednesday
<acheam> dilyn: do you also shred your bills?
<dilyn> ofc
<testuser[m]> I delete all of my emails too
<dilyn> the past is a hindrance to all future progress
<riteo> god I feel so anxious
<noocsharp> dilyn: i don't think that argument would hold up in court
<dilyn> no mortal laws can contain me
<riteo> that's because court doesn't foster the power of simplicity as dilyn does
<riteo> exactly
<dilyn> I am a fractal of the universe
<riteo> dilyn is a rationalization of the power of the universe in a form that our puny human brains can comprehend
<noocsharp> dilyn: irc xor acid
<dilyn> i am a way for the cosmos to know itself
<riteo> aaaaaaaaaa I'm gonna make the repo public
<riteo> why is it so hard
<testuser[m]> i see you stole mid's joke about shithub statuses
<dilyn> you are the only hindrance to yourself
<dilyn> man is condemned to be free
<riteo> testuser[m]: not quite, I actually started it if we're talking about the same one
<riteo> mid surely added something to it though
<riteo> the scariest thing is that I have no memory if I left anything that shouldn't be published into the repo
<riteo> it doesn't look like that, expecially since I wrote the script and the commit messages in english
<riteo> in case you find my nudes or something like that tell me
<riteo> ok here it goes
<riteo> it's live now
<testuser[m]> Nice
<riteo> btw, would you mind if while it downloaded the game assets the output would be... chunky?
<riteo> like, buffered?
<riteo> or would you prefer a less user-friendly but interactive output?
<noocsharp> riteo: link?
<riteo> you see, I'm making an optimization which makes the assets downloading way faster at the cost of a trickier output to manage, and in order to prettify it while parsing the assets names from the hashes the output gets buffered
<riteo> noocsharp: aaaaaaaaaaaa here it comes
<riteo> it's still in alpha quality
<testuser[m]> How does it look like when buffered
<riteo> 30/40 lines of
<riteo> aaaa entered to quickly
<riteo> I said:
<riteo> *silence* 30/40 lines of "downloaded x" *silence* and so on
<testuser[m]> Seems fine
<riteo> meanwhile the other option could be: "downloaded *undecipherable hashes*"
<riteo> so, who will try it?
<noocsharp> i would if i had java on this system
<testuser[m]> I don't play minecraft i just wanted to see what your launcher looked like :p
<riteo> I see
<riteo> noocsharp: kiss linux install?
<riteo> I actually plan after doing this to work both on the nvidia drivers and java support on kiss
<riteo> I'll make kiss linux the minecraft distro
<riteo> wew, this was so sudden
<riteo> I literally gave you my intimate relationship with one of my project all of a sudden
<riteo> also, I've already been working on it for more than a month
<riteo> "what did you do in summer?" "I made a shitty minecraft launcher in POSIX shell"
<riteo> bruh there are literally duplicate entries into the asset index
<riteo> ok I'll ditch directly the chunky prettifying for now, get ready for undeciferable sha1sums
<riteo> testuser[m]: was it you that was working on the package linter?
<testuser[m]> GalaxyNova
<riteo> oh ok
<noocsharp> riteo: indeed
<riteo> indeed what
<riteo> noocsharp: indeed what
<msk[m]> "kiss linux install?" ?
<testuser[m]> indeed
<noocsharp> msk[m]: indeed
<riteo> indeed
PickleGG has joined #kisslinux
PickleGG has quit [Quit: Client closed]
illiliti has quit [Quit: leaving]
<testuser[m]> is 'mv dir1 dir2 /destdir/' portable ? Is the last directory treated as the target in all implementations of mv ?
GalaxyNova has joined #kisslinux
<GalaxyNova> yay
<GalaxyNova> sway is broken now after the update :D
<testuser[m]> define broken
<GalaxyNova> the keyboard seems to not be responding
<GalaxyNova> I can't open anything
<necromansy> check the config file/defaults
<GalaxyNova> i hightly doubt it's the config
<GalaxyNova> it was working just fine before
<GalaxyNova> here's the sway log https://0x0.st/-VBN.log
<GalaxyNova> everything looks normal
<riteo> oh hi GalaxyNova!
<GalaxyNova> hey
<GalaxyNova> on tty rn
<riteo> how's that package linter going?
<GalaxyNova> it works!
<riteo> cool!
<GalaxyNova> ye
<riteo> I don't remember if you cared, but I published the code for minekiss on github
<GalaxyNova> oh cool
<GalaxyNova> link?
<testuser[m]> Galaxynova is this regular sway or sway-tiny or no-seat
<GalaxyNova> Unfortunately for me I have a nvidia card so performance will probably be trash
<GalaxyNova> testuser[m]: regular sway
<GalaxyNova> seatd is running
<testuser[m]> Hmm
<testuser[m]> So it launches and then just exits ?
<GalaxyNova> riteo: nevertheless I'll still check it out when I get sway to work
<riteo> epic
<GalaxyNova> testuser[m]: No, I killed it because there was no other way
<GalaxyNova> the exit keybind didn't work
<testuser[m]> Stuck on a blanks screen ? You gave the log but not what the issue is
<testuser[m]> Ah
<GalaxyNova> the keyboard doesn't work
<testuser[m]> Sorry didnt read
<testuser[m]> So it displays your wallpaper and stuff
<testuser[m]> Might be related to dylan's new iteration of the libevdev patch
<testuser[m]> It was changed to fix audio keyss
<GalaxyNova> oof
<GalaxyNova> that's what i was suspecting too
<testuser[m]> Raise it on kisslinux/repo
<GalaxyNova> guess I should roll back my repository
GalaxyNova has quit [Quit: Whoooooshh]
GalaxyNova has joined #kisslinux
<GalaxyNova> ok
<GalaxyNova> rolled back to an old version of the repositories
<GalaxyNova> the keyboard still doesn't work
<GalaxyNova> this must be my fault
<riteo> bruh
* GalaxyNova sighs
<GalaxyNova> SWAY ISN'T GIVING ANY ERRORS
<GalaxyNova> AHHHHHHHHHHHHHHHHH
<riteo> can you recall anything recent you did with the device manager?
<GalaxyNova> I didn't touch the device manager at all
<riteo> wait, how did you roll back?
<GalaxyNova> all i did was enable the seatd service
<GalaxyNova> git checkout
<riteo> and?
<GalaxyNova> and it's the same
<riteo> I mean
<riteo> after git checkout did you rebuild the packages or run kiss update?
<GalaxyNova> rebuild the packages
<riteo> ok
<riteo> did it rebuild their libraries too?
<GalaxyNova> yes
<riteo> I see
<riteo> so the issue is seatd
<riteo> right?
<GalaxyNova> idk
<GalaxyNova> before i was just running "doas seatd &"
<GalaxyNova> then manually chowning /run/seatd.sock to my user
<GalaxyNova> because i was too lazy to enable the service
<riteo> have you looked into the service?
<riteo> what does it do?
<riteo> maybe it does something differently
<GalaxyNova> it runs seatd -g video
<GalaxyNova> that shoudn't matter though because i am in the video group anyway
<GalaxyNova> what's annoying me is that there are no error messages whatsoever
<riteo> that sounds horrible
<riteo> does sway have a debug option?
<GalaxyNova> yes
<GalaxyNova> it's how it generated the log
<riteo> bruh
<GalaxyNova> I'll try plugging in a PS2 keyboard to see if that works
<GalaxyNova> the mouse works just fine
<riteo> wait, is the mouse ps/2
<GalaxyNova> it's a USB mouse
<riteo> this is confusing
<GalaxyNova> idk maybe it's some weird driver thing
<GalaxyNova> didn't touch my kernel though
<riteo> so usb works but not for the keyboard and only on sway
<riteo> s/sway/tty/
<GalaxyNova> the keyboard works on tty
<GalaxyNova> is there any way I can open a program inside sway?
<GalaxyNova> from the tty
<riteo> could it be that the seat doesn't have a keyboard defined?
<GalaxyNova> tried removing sway and installing sway-no-seat, same result
<GalaxyNova> i'll try that again actually
<GalaxyNova> brb
GalaxyNova has left #kisslinux [WeeChat 3.2]
GalaxyNova has joined #kisslinux
<GalaxyNova> riteo: Ok
<GalaxyNova> installed sway-no-seat, same effect
<GalaxyNova> removed my config file, same effect
<riteo> wtf
<riteo> you installed the older version of sway-no-seat, right?
<necromansy> completely off the cuff suggestion, try rebuilding libxkbcommon?
<GalaxyNova> no, the new one
<riteo> necromansy: GalaxyNova is on wayland
<necromansy> yeah
<necromansy> its a wayland dep too
<riteo> oh
<necromansy> yeah dw its one of two x packages thats been moved to wayland
<GalaxyNova> installed the old version of sway-no-seat, same effect
<GalaxyNova> wtf
<GalaxyNova> is my install borked???
<riteo> > installed debian, same effect
<GalaxyNova> rebuild libxkbcommon and that didn't make a difference either
<GalaxyNova> riteo: lmao
schillingklaus has joined #kisslinux
<GalaxyNova> it was working fine yesterday
<necromansy> heck
<GalaxyNova> time to install Ubuntu
<GalaxyNova> kek
<riteo> red hat won again
<riteo> GalaxyNova: rollback to a few days ago and rebuild everything
<riteo> if even then it doesn't work, red hat hacked your cpu to make it work only on fedora
<schillingklaus> make what work only on fetor-a?
<GalaxyNova> bruuhh
<GalaxyNova> that's going to take hours
<GalaxyNova> i have firefox installed
* GalaxyNova cries
<riteo> well, then build everything except firefox
<testuser[m]> no
<testuser[m]> rebuild only stuff from repo/ayyland
<necromansy> ^
<riteo> yeah, good idea
<riteo> mine was like, the last resort
<testuser[m]> thats the windows way riteo
<riteo> yeah, you're right
<GalaxyNova> oh wait
<GalaxyNova> kiss-depends libinput returns libevdev
<GalaxyNova> is that bad?
<testuser[m]> yes
<testuser[m]> rebuild it
<testuser[m]> purge evdev
<testuser[m]> have you been doing partial upgrades
<GalaxyNova> maybe
<riteo> oh my god
<riteo> is the ascii art character on kiss' website tux?
<testuser[m]> yeah
<riteo> why did it took so long for me to figure that out
<riteo> I always thought it was someone like, talking with an exaggerated open mouth, you know, cartoonishly
GalaxyNova has quit [Quit: Whoooooshh]
<riteo> I feel so dumb rn
<riteo> oh dylan updated the quote from "A camel is a horse designed by a commitee." to "A camel is still a horse designed by a commitee."
<riteo> lmao
<riteo> that's a really nice touch
<riteo> well, gtg, bye everyone!
riteo has quit [Quit: epic public minekiss moment]
dilyn has quit [Quit: Ping timeout (120 seconds)]
<schillingklaus> a dilyn is a dylan designed by a test user
mobinmob has joined #kisslinux
<schillingklaus> the famous mobinmob who wrote many comments for sysdfree... i remember the disputev with cynwulf
<testuser[m]> Wat
<travankor> is schillingklaus midfavila in disguise?
<schillingklaus> no, I have nothing in common with midfavila
mrlix has joined #kisslinux
claudia has joined #kisslinux
<claudia> yes, this distro is developed, maintained and used, all by one person.
<testuser[m]> ?
<schillingklaus> and this person is?
<mrlix> I'm pretty sure there's at least 5 kiss linux users
<schillingklaus> as opposed to netbsd, where the sets of users and of developers is almost disjoint
<travankor> that's sort of true for all bsd's
<travankor> especially freebsd
konimex has quit [Quit: Bridge terminating on SIGTERM]
phoebos[m] has quit [Quit: Bridge terminating on SIGTERM]
kqz has quit [Quit: Bridge terminating on SIGTERM]
jstnas has quit [Quit: Bridge terminating on SIGTERM]
E5ten[m] has quit [Quit: Bridge terminating on SIGTERM]
felinae has quit [Quit: Bridge terminating on SIGTERM]
rgybmc[m] has quit [Quit: Bridge terminating on SIGTERM]
msk[m] has quit [Quit: Bridge terminating on SIGTERM]
testuser[m] has quit [Quit: Bridge terminating on SIGTERM]
phoebos[m] has joined #kisslinux
E5ten[m] has joined #kisslinux
konimex has joined #kisslinux
felinae has joined #kisslinux
kqz has joined #kisslinux
testuser[m] has joined #kisslinux
msk[m] has joined #kisslinux
rgybmc[m] has joined #kisslinux
jstnas has joined #kisslinux
claudia has quit [Read error: Connection reset by peer]
Uks2 has quit [Ping timeout: 255 seconds]
Uks2 has joined #kisslinux
<mrlix> and yet freebsd has less bugs and poorly made libraries
claudia has joined #kisslinux
dilyn has joined #kisslinux
mrlix has quit [Ping timeout: 246 seconds]
<claudia> Hey, I use 'kiss a' to swap all alternatives to toybox, but get the following error: ERROR File '/usr/bin/[' exists on filesystem but isn't owned
<claudia> Can sombody reproduce?
<necromansy> yes
<necromansy> got it with sbase
<necromansy> you on version 5.5.9?
<claudia> kiss b foo/ gives the same.
<claudia> yes 5.5.9
<claudia> I think dylan prohibet usage of special signs as input.
<testuser[m]> Seems like a nonportable grep pattern
<necromansy> looks like an issue needs to be raised
<claudia> on it
claudia has quit [Ping timeout: 246 seconds]
soliwilos has quit [Quit: nyaa~]
<necromansy> i just
<necromansy> what
michalsieron has joined #kisslinux
<dilyn> lmfaooooooo
<cot> ...
<testuser[m]> their other issues are like that too
<testuser[m]> probably troll
<dilyn> When your nit-picky opinions aren't even clearly conveyed because you can't be bothered to use quotes or linebreaks
<cot> >What is an information tool? That phrase is way, way, way too vague
<cot> LOL
<necromansy> omg they do this to other people too?
<necromansy> for sure a troll then
necromansy has quit [Quit: necromansy]
necromansy has joined #kisslinux
<testuser[m]> how much time have they got lol they're writing pages worth of comments
<cot> >I have never made a pull request in my life. I'm not an engineer. I've never used pfetch nor
<cot> do I intend to use it. I'm not even sure what pfetch does. I simply contributed some
<cot> editorial changes after glancing at Pfetch: Everyone's Favourite System Info Tool.
<dilyn> "What about an empty black screen with a blinking cursors screams I am a point and grunt interface suitable for gorillas to you?" dude gets fucking bodied in a github comment
<necromansy> im crying ahah
<testuser[m]> > You have been blocked. Dont let the door hit your fat ass on the way out.
<testuser[m]> lol
<cot> hah
<cot> LOL @ them telling a commenter that one of the sentences in their messages is a run-on sentence
<cot> 13yo grammar police on steroids
<necromansy> either a troll or a very self-absorbed prick
<necromansy> either way
<necromansy> some late night hilarity
<dilyn> this dude has to be like, 65 years old
<cot> nah, 12-13
<cot> I can't imagine an adult acting like that.
<necromansy> oh man
<necromansy> you sweet summer child
<cot> lol
<testuser[m]> seen ddevault ?
<cot> ddevault's behaviour is, um, more adult-y, for lack of a better term.
<schillingklaus> i am 55 and can act worse
<cot> This guy reminds me too much of some young adolescents I've met in the past.
<necromansy> well i now no longer feel like an old fart
<necromansy> thank you schillingklaus
soliwilos has joined #kisslinux
<dilyn> finally, i am a young one
<necromansy> ^
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
mrlix has joined #kisslinux
schillingklaus has quit [Quit: ERC (IRC client for Emacs 26.3)]
<raph_ael> youth is a question of mind
<dilyn> my mind old as fuq dude
<necromansy> big mood
<dilyn> some times I think about learning something new and I'll remember that because I'm not 9 anymore my brain has become super inelastic and it will only be orders of magnitude harder for me to learn and so i resign myself to cursing my age
<dilyn> life is ruff
<necromansy> i more so think about how taking the time to overcome that new learning difficulty eats into my other things
<necromansy> :<
<dilyn> 'do one thing and do it well', because you're old as fuck and won't be able to do more than one thing in the 24 hours you've got
<necromansy> precisely
konimex[m] has quit [Read error: Connection reset by peer]
konimex[m] has joined #kisslinux
rio6 has joined #kisslinux
humky has quit [Remote host closed the connection]
humky has joined #kisslinux
ecs has quit [Changing host]
ecs has joined #kisslinux
<acheam> > awk is gone.
<acheam> :(
micro_O has joined #kisslinux
<dilyn> say what
<dilyn> rip awk
<testuser[m]> Gone ?
<testuser[m]> Wat
<testuser[m]> Where'd it go
<dilyn> dylan eliminated its need in `kiss`
<dilyn> can we implement such a thing in irc
<testuser[m]> you can implement what you want but no use if none's gonna follow it :p
<dilyn> :'(
claudia has joined #kisslinux
<acheam> hmm dylan took down the guidestones
<micro_O> interesting, awk never was part of the base image anyway. gotta check that all my depends are in order
<micro_O> also I guess any build scripts that use awk need to add it to their depends as well? or can we assume busybox awk will still be available
riteo has joined #kisslinux
<riteo> hiiiii!
<micro_O> o/
<acheam> micro_O: because awk is in busybox
<acheam> yeah it will still be in the busybox package im sure
<acheam> its posix, after all
<acheam> its usage was just removed from the package manager
<dilyn> http://ix.io/3trz noocsharp: are you happy now
<dilyn> micro_O: i went by the rule that anything provided by busybox could be assumed; a competent coreutils is... important to have in general
<dilyn> users who don't have awk should know it, or will find out quick lmfao
<noocsharp> about time
<acheam> oh no
<acheam> dilyn doesn't put return type on a new line
<dilyn> ?
<acheam> is this the causal.agency style?
<acheam> like this: https://l.armaanb.net/tmp
<noocsharp> hey, at least he's putting return types in now
<acheam> lol
<cem> awk is specified by POSIX after all, and I don't expect any POSIX to come without awk installed
<acheam> it lets you grep for function definitions easily
<dilyn> why the FUCK would i do an abomination like int\ main(void)
<dilyn> int\n*
<dilyn> that can go directly to hell
<acheam> because then you can grep '^main'
<acheam> and find the definition nice and quick
<dilyn> no
<acheam> instead of just where its called
<cem> Yeah, it's super useful when you are actually debugging code
<dilyn> vim foo.c; /main(
<cem> And I hate it whenever someone doesn't do that
<acheam> for main that works
<acheam> but for other functions it wont
<acheam> say you call a function 15 times
<dilyn> this is disgusting syntax and I will never obey it
<acheam> you'll have to search through 15 instances to find the definition
<acheam> have fun
<cem> dilyn: you don't deserve to code in C
<dilyn> you're all criminals
<acheam> just clang-format this SOB
<cem> no YOU are
<dilyn> :(
<cem> I'll sue you
<riteo> what are my eyes seeing
<cem> dilyn: wow okay huh easy there
<dilyn> no
<dilyn> i have strong feelings about this
<riteo> I don't see either why one would do this
<dilyn> i'm a real programmer, finally
<cem> you have wrong strong feelings
<dilyn> that's just like, your opinion man
<cem> and that's the worst kind of strong feelings
<cem> dilyn: it's the law
<riteo> I mean, if you want to find the definition just make a regex that looks for main and an ending {
<dilyn> if the law is unjust, the only just thing to do is to be a criminal
<cem> I agree with the sentiment
<cem> but no
<acheam> riteo: that wont necesarily work
<acheam> what about "if (function()) {"
<acheam> also { belong on a separate line, dont @ me
<acheam> int\nmain(void)\n{
<riteo> ok now I lost all respect for you
<acheam> this is the way!
<noocsharp> ^
<cem> acheam: I agree 100 percent
<acheam> although i've been considering switching to just using the Linux style
<testuser[m]> { on newline only for functions
<acheam> which is int main(void)\n{
<acheam> so you can still grep it easily
<riteo> are we and dilyn the only ones here to not put everything in a newline
<dilyn> main() { printf("Eat my shorts"); }
<riteo> based
<dilyn> newlines are bloat
<dilyn> compilers don't read them, why do i need them
<dilyn> save the char
<noocsharp> says the animal using spaces for indentation
<dilyn> it's for the disrespect
<riteo> dilyn does WHAT
<acheam> spaces for indent isn't /that/ bad
<testuser[m]> What's the rationale for putting return type newline function name
<acheam> because then its consistent at least
<acheam> testuser[m]: easy grepability
<acheam> grep '^function'
<acheam> to find the definition
<acheam> it also makes it stand out a bit more
<testuser[m]> Use zero width spaces for indentation
<acheam> wut
<acheam> no
<riteo> this is the right choice
<riteo> couldn't agree more
<dilyn> there is no choice
<dilyn> it's the only option
<cem> dilyn: newlines are good because someone will need to read your crappy code eventually?
<riteo> cem I think dilyn was joking
<cem> I'm also joking
<acheam> single line ifs are nice
<riteo> fuck
<cem> lmao
<acheam> they're good for quick checks
<acheam> like seeing if a malloc failed
<riteo> yes
<acheam> if (!var) exit(1);
<acheam> as compared to
<riteo> the 80 char rule shall apply once again
<acheam> if (!var) {
<acheam> exit(1);
<acheam> }
<acheam> here's the real question
<acheam> 80 char
<acheam> or 79 char
<noocsharp> you don't need braces on that
<acheam> noocsharp: i know
<acheam> but some style guides enforce no single line ifs, and no braceless ifs
<riteo> why would you want 79 chars?
<acheam> idk python does it
<riteo> if you need extra space for stuff use 72
<acheam> maybe to leave room for the newline char?
<riteo> I thought 80 chars included it
<noocsharp> i use 80 chars most of the time, and 150 chars when it's convenient
<acheam> when is that ever convinient!
<acheam> go away
<acheam> leave this place!
<riteo> I think when you use variable names which are 30 chars long each
<noocsharp> like wayland
<acheam> tbf, it was near impossible in some places to make 80char lines in chorizo
<acheam> because some of the webkitgtk function names were literally 50 chars long
<acheam> add in 16 chars of indent
<acheam> and you dont have all that much room
<dilyn> fight me
<acheam> my man just hit J a bunch of times
<riteo> the definitive code
<dilyn> we can make it one line if we try harder
<riteo> remove all whitespace that can be removed
<riteo> new idea: a c compiler that switches spaces with _
<riteo> so you can have variables with space
<riteo> s/space/spaces/
<acheam> that would break
<acheam> so
<acheam> much
<acheam> stuff
<riteo> yes
<riteo> that's part of the learning experience
<riteo> learn its quirks
<acheam> "First off, I'd suggest printing out a copy of the GNU coding standards, and NOT read it. Burn them, it's a great symbolic gesture.
<acheam> "
<riteo> embrace the power
<cem> dilyn: curl -L http://0x0.st/-VQx.c | gcc -x c - -o crap
<cem> Technically oneline
<acheam> above is from linus torvalds
<acheam> why tf do you know the gcc flags that well
<cem> I just read the manpage
<cem> I don't
<cem> Alright, here it is
<acheam> now do it with a line width of 20
<riteo> you forgot something
<riteo> wait
<riteo> I'm dumb
<riteo> curl https://termbin.com/yzzy | sh
<cem> Reminds me of my favourite one-line project
<testuser[m]> Ijit
<testuser[m]> Init
<cem> license and readme is generated from the code too
<noocsharp> wow, very impressive
<riteo> absolutely crazy
<riteo> lmao the end part
<riteo> "please install systemd"
<cem> truly minimalist
<noocsharp> not sure how one expects to have proper service management on linux without systemd
<cem> not possible
<noocsharp> for what systemd does, it is extremely minimal
<testuser[m]> schillingklaus:
<noocsharp> people who say that systemd is bloat just don't understand the sophistication underlying system
<riteo> systemd is the ideal software
<riteo> it is the pinnacle of computing
<riteo> anything past it is all downhill
<mrlix> yikes
<riteo> did you even have to share that link
<riteo> it is the first thing everybody thinks when someone says systemd
<mrlix> lol
<cem> It does NOT reflect on the entire softwareeee
<cem> It's the only problem
<cem> trust me
<testuser[m]> Why is the discovery of a vulnerability a problem
<mrlix> I hate how dependent on systemd a lot of stuff is becoming
<testuser[m]> Fork that stuff then
<cem> eresolved
<mrlix> theres already forks for it
<testuser[m]> Or provide youe own alternatives
<riteo> testuser[m]: the problem isn't the vulnerability itself, but its nature
<riteo> how does a service manager mess up so badly with a dns server?
<riteo> this shows a greater picture
<cem> riteo: It doesn't affect the service manager part
<dilyn> calling systemd "a service manager" is a disingenuous portrayal of systemd
<riteo> cem: that's the issue lmao
<riteo> it isn't a service manager anymore
<riteo> it's an operating system framework
<riteo> lmao
<dilyn> that's like saying the dictionary provides the definition for words from albacore to apple
<dilyn> you're not wrong, but you're certainly wrong
<mrlix> arch linux uses systemd-boot by default instead of grub now
<riteo> bruh
<dilyn> as one should
<mrlix> you can change it by just pressing a number but hmm
<dilyn> grub is garbagio
<riteo> true
<mrlix> you can rice grub tho
<riteo> the real based option is efi
<mrlix> I saw someone on unix porn make it like anime girls and stuff
<riteo> the only option I might dare to say
<dilyn> mmm yes let me rice the thing i never want to see
<cem> systemd can be defined as a suite of system management tools sharing the same namespace
claudia has quit [Ping timeout: 246 seconds]
<riteo> didn't they all depend on one another?
<dilyn> presumably not
<cem> Not really
<dilyn> considering they tout its 'modularity', they'd be outright lying if that were true
<cem> they all depend on init
<dilyn> which is reasonable
<cem> because systemd is built upon abusing PID 1 permissions
<cem> and that's why it's an insecure crap
<mrlix> honestly
<mrlix> I see systemd branching out and making their own shit in the future
<mrlix> like making utilities like busybox
<cem> systemd-kerneld
<testuser[m]> coreutilsd
<dilyn> like s6
<cem> s6 is how systemd should have been
<mrlix> imagine a systemd display server
<cem> I can
<cem> logind
<cem> why not displayd
<mrlix> it would definitely take some hate out of x11
<noocsharp> systemd-xorgd
<dilyn> lmfao kiss is sitting at exactly 1k loc
<riteo> the rule shall not be broken
<noocsharp> i installed the latest kiss today and it appears KISS_SU has to be set now
<dilyn> indeed
<dilyn> dylan droped the KISS_SU:- line
<riteo> it was worth it though
<msk[m]> dilyn, I force-removed libressl you said, but now I'm getting errors building qt5-webengine, which I think is related (http://0x0.st/-VQG.txt)
<msk[m]> s/you said/like you said/
<nerditup> NAS appliance suggestions?
<riteo> appliance as in machine?
<dilyn> this is a python problem msk
<dilyn> kiss-depends python ?
<msk[m]> kiss-depends python: http://0x0.st/-VQk.txt
<msk[m]> should I recompile python?
<dilyn> perhaps...
<dilyn> hmmm
<dilyn> what happens if you open up a python interpreter and try to import md5 yourself?
<dilyn> 'import hashlib'
<msk[m]> in python3, both "import hashlib" and "from hashlib import md5" worked
<dilyn> interesante
<msk[m]> in python2, neither
<msk[m]> and the log seems to mention python2 a lot
<dilyn> so _md5 should be built into python. fascinating
<dilyn> oh yes qt5-webengine does require some python2
<dilyn> kiss-depends python2 ?
<msk[m]> bzip2, sqlite, zlib
<dilyn> can you import hashlib in python2?
<dilyn> so strange
<dilyn> the sick irony is this error happened almost immediately in your build log and yet it continued to almost the end XD
<msk[m]> nope, import hashlib fails
<msk[m]> wait
<msk[m]> oh
<msk[m]> I was recompiling both python3 and python2 as we went, and now, after recompiling, python2 lets me import
<msk[m]> I'll try doing qt5-webengine again
<dilyn> nice
<msk[m]> thanks dilyn
<dilyn> i live to troubleshoot
<testuser[m]> Same
<acheam> dilyn: have you played with building llvm sans python
<dilyn> it's not easy
<acheam> but possible?
<dilyn> python is a big part of their build system
<dilyn> i mean... you'd have to do a lot of work
<acheam> nah
<dilyn> lol okay
<dilyn> let's check for the shebang, shall we...
<cem> There is more python in llvm than C
<acheam> lol
<dilyn> f
<acheam> is there any C?
<dilyn> uh, still grepping
<acheam> besides maybe some cross compatible header files?
<cem> yes, 88 files C
<acheam> nice
<cem> 227 files python
<acheam> dilyn: ug or ag is the way
<cem> 3167 c++
<cem> 2477 headers
<dilyn> what a beautiful concoction
<dilyn> still better than webkit
<cem> That's not even all
<acheam> dont even mention webkit
ChanServ changed the topic of #kisslinux to: KISS Linux | https://kisslinux.xyz | logs: https://k1sslinux.org/irc#2.0 | please read: https://k1sslinux.org/news/20210712a | thing of the day: https://invidious.zapashcanon.fr/Mynzbmrtp9I
<acheam> cem: whats that?
<cem> That's llvm source code cloc
<acheam> oh I pasted the wrong link
<acheam> > Swift
<noocsharp> > OCaml
<acheam> > Windows.*
<acheam> pascal too?
<acheam> wtf is this?
<noocsharp> only 17k lines of python
<noocsharp> not too bad
<acheam> how tf do they have that much yaml?
<cem> And people start throwing crap at me when I say I like gcc better
<cem> I mean they are both monstrous, but gcc is slightly less monstrous
<acheam> i dont like llvm honestly
<dilyn> this is roughly a list of the python scripts that are probably involved in building my llvm pkg http://ix.io/3trN
<acheam> like, me avoiding gnu is more just for fun
<acheam> thats a lot
<dilyn> you can maybe cut out many of */utils/* files
<cem> gcc supports like a bajillion languages, yet C is still a bigger portion of the compiler
<dilyn> 'many' would be like, less than half i think
<dilyn> cem: but have you considered: GNU
<cem> I did
<cem> I'm just not into namespace circlejerk
<dilyn> :'(
<cem> I'll switch to cproc, I promise
<cem> one day
<acheam> i only have 5 c++ packages
<acheam> which makes it even more annoying to keep around llvm for
<noocsharp> the problem with cproc is that many c programs aren't compliant with the spec
<dilyn> new goal
<cem> yeah, that's annoying
<cem> but musl had similar issues when it first came about
<cem> now webkit natively supports musl!
<noocsharp> who woulda thunk it
<noocsharp> also cproc can't build shared libraries afaik
<acheam> thats a shame
<cem> I see that as an absolute win
<noocsharp> i guess it's the linkers job actually...
<micro_O> cem acheam I would be really surprised if a good chunk of all the languages were actually in test code
<acheam> yeah but lfortran and swift and stuff aren't mainline llvm right?
<acheam> so why should they be there
<acheam> screw downstream, amirite?
<micro_O> for projects this big (llvm, firefox, gcc, etc), I think it takes a bit of time to familiarize yourself with the codebase as simple 'find/grep/cloc' doesn't really paint the whole picture, or at least misrepresents it.
<micro_O> for instance, oil-shell has i think 3 different 'lines of code' counts, because it doesn't make sense to count just whats checked into git for that project
<cem> Yeah, I mostly agree with that
<dilyn> i feel like when you're dealing with a codebase that large, you're better off doing things like profiling the code more than just doing a surface-level gaze at what makes it up
<dilyn> plus you're like... NEVER working with large chunks of that code
<cem> It's mostly divided in subprojects
<cem> Similar to the kernel
micro_O has quit [Quit: micro_O]
micro_O has joined #kisslinux
mrlix has quit [Quit: Client closed]
akira01 has joined #kisslinux
akira01 has quit [Ping timeout: 268 seconds]
mrlix has joined #kisslinux
claudia has joined #kisslinux
micro_O has quit [Remote host closed the connection]
sad_plan has joined #kisslinux
sad_plan has quit [Remote host closed the connection]
claudia has quit [Quit: zzz]
sad_plan has joined #kisslinux
<acheam> wait
<acheam> openbsd 6.7 introduced support for my wifi card
<acheam> see ya Linux!
<sad_plan> hello kiss-bsd much? :p
<acheam> maybe
<acheam> id like to learn the openbsd way first
<sad_plan> that would be an idea, yeah :p
<acheam> burning an iso right now
<sad_plan> cool. ive been wanting to try out a bsd myself, but im a bit busy messing with kiss :p
<sad_plan> did you even try sdhcp? the simple dhcp client. listed at the suckless site.
<sad_plan> oasis linux also uses it apearantly
<acheam> its been on my todo list
<acheam> noocsharp has used it, if you have any questions
<sad_plan> I am a bit curious about how its used. I mean, it doesnt run as a service, like dhcpcd does.
<sad_plan> havent delwed too deep tbh. just recently packaged it into one of my repos
akira01 has joined #kisslinux
<sad_plan> oh, while I remember. iirc you seem to enjoy suckless' software, correct? perhaps check out svc. its a service manager. seeing as you also talked about switching out busybox earlier aswell, youd need service manager, unless your sticking with runit's
<acheam> im sticking with busybox for now
<acheam> otherwise, next in line might be s6
<sad_plan> ah ok
<sad_plan> why exacly s6?
<acheam> no real reason
<acheam> lol
<acheam> i haven't looked into it that much
<sad_plan> artix has a small wiki page on it anyway, for some minor info anyway.
<soliwilos> s6 is nice.
<akira01> Anyone knows a good music streaming for terminal?
<acheam> mpd
<acheam> and mpv
<dilyn> can you imagine my fucking surprise when I discovered that K&R is outdated?
<dilyn> chapter 1 section 9, 'make a function named getline()'
<dilyn> added to stdio in 2010 https://c-for-dummies.com/blog/?p=1112 rip
<akira01> acheam: how can i stream with this?
claudia has joined #kisslinux
<akira01> hi claudia 0/
<claudia> hola
<sad_plan> o/
<noocsharp> sad_plan: wdym it doesn't run as a service? are you saying it doesn't fork into the background?
<sad_plan> no, I meant a service like you can start/restart/stop with service manager. or Im I just plain wrong here?
<sad_plan> ¯\_(ツ)_/¯
<sad_plan> I know it forks into backround or w/e. as its stated in the man page.
<noocsharp> any program can be a service, so you're just plain wrong here :P
<sad_plan> I stand corrected :p
<noocsharp> you just need to make a suitable service file for it if you're using busybox sv
<sad_plan> I am currently using busybox, yes. Im not sure how I write a service file for it, but Im sure I could eventually figure that out :p
<noocsharp> look at the other files in /etc/sv as examples
<noocsharp> that's what i do if i need to write on
<noocsharp> one
<sad_plan> nice. does it require any configuration of sorts? appart from creating a service file.
<noocsharp> ^
<noocsharp> just a resolv.conf
<dilyn> my favorite about sdhcp is that "It ignores most of the DHCP options it understands."
<dilyn> surprised nobody has submitted sdhcp to community :o
<sad_plan> lol, yeah I noticed.
claudia has quit [Ping timeout: 265 seconds]
<sad_plan> people probably dont bother with it
<sad_plan> do I need the supervise dir and its file? I noticed vim cant even open some of those files. it just freezes instantly
<acheam> akira01: mpv <URL of stream>
<dilyn> supervise is created by sv
<sad_plan> ah ok, so just the run script then
<dilyn> you just need /etc/sv/foo/run; ln -sv /etc/sv/foo/run /var/service
<dilyn> run will probably just be something like sdhcp -d, or whatever sdhcp's option to not daemonize is
<sad_plan> yep
<dilyn> don't let that sucker fork :P
<sad_plan> otherwise itll just eat up all my ram? :p
<noocsharp> it won't die if you stop the service
<sad_plan> ah, itll just keep going. that would be unfortunate
<dilyn> sv would try to constantly restart it
<sad_plan> I see
sad_plan has quit [Quit: ]
sad_plan has joined #kisslinux
sad_plan has quit [Quit: ]
sad_plan has joined #kisslinux
<sad_plan> it worked :D
<dilyn> how big id sdhcp?
<sad_plan> 22.3k I belive
michalsieron has quit [Ping timeout: 255 seconds]
<dilyn> itsy bitsy
<sad_plan> yeah
<sad_plan> vs dhcpcd's 580kb
<noocsharp> is it static or dynamically linked?
<sad_plan> I didnt specify that in my buildfile, so im guessing dyamically, if thats default
<dilyn> probably static
<dilyn> ldd /usr/bin/sdhcp?
<noocsharp> i would imagine it's at least linked to libc
<sad_plan> yep. libc.so
<dilyn> ah, they don't have -static :o smh
<dilyn> suckless devs water u doin
<mrlix> guys
<cem> Are you even suckless if you don't force -static flag on the Makefile
<cem> like LDFLAGS += -static
<sad_plan> lol
<mrlix> kqueue is a million times better than epoll
<dilyn> something something not portable?
<mrlix> so much cleaner so much simpler so beautiful
<cem> dilyn: have you heard of #ifdef tho
<dilyn> you give CPP too much power
<cem> just delete all #include's too I guess?
<dilyn> indeed
<dilyn> write your own functions you lazy bums
<cem> macros were a mistake
<cem> revert
<sad_plan> ls
<sad_plan> ffs, wrong terminal
mobinmob has quit [Quit: Connection closed for inactivity]
<sad_plan> the executable gets way bigger if you use -static. its 22.3k vs 70.9k
<dilyn> that's how static works
<sad_plan> yeh
<dilyn> can't always be strictly better :'(
<sad_plan> I knoow :c
mrlix has quit [Quit: Client closed]
claudia has joined #kisslinux
sad_plan has quit [Read error: Connection reset by peer]
claudia has quit [Read error: Connection reset by peer]
claudia has joined #kisslinux
mrlix has joined #kisslinux