💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2020-12-28.txt captured on 2024-05-10 at 14:30:14.

View Raw

More Information

⬅️ Previous capture (2021-12-17)

-=-=-=-=-=-=-

2020-12-28T02:55:41 #kisslinux <acheam> i'm working on a fork of https://github.com/bionade24/abs_cd for KISS
2020-12-28T02:56:47 #kisslinux <acheam> micr0: you just missed my message, but i'm working on a fork of https://github.com/bionade24/abs_cd for KISS
2020-12-28T03:05:41 #kisslinux <kiedtl|lurch> Well... if only freenode's IRCd had channel history
2020-12-28T03:05:57 #kisslinux <kiedtl|lurch> s/$/ playback/
2020-12-28T03:06:00 #kisslinux <kissbot> <kiedtl|lurch> Well... if only freenode's IRCd had channel history playback
2020-12-28T03:06:13 #kisslinux <acheam> gotta get Quassel
2020-12-28T03:06:19 #kisslinux <acheam> its a dream
2020-12-28T03:32:00 #kisslinux <acheam> should I develop this new CD system on kiss-community or my sr.ht?
2020-12-28T07:16:00 #kisslinux <dilyn> the only static libraries on my system are libc, libgm, libgles, libegl, libvulkan, and libglapi (musl, mesa)
2020-12-28T07:16:04 #kisslinux <dilyn> was it worth it, you may ask?
2020-12-28T07:16:06 #kisslinux <dilyn> hell no.
2020-12-28T07:17:24 #kisslinux <dilyn> six binaries link against libc and I really really *really* don't wanna bother. Why does pango-view refuse to be static? who tf knows. This isn't worth it, nobody should build a static system. It's untenable. Thank you for coming to my TED talk.
2020-12-28T07:48:57 #kisslinux <testuser[m]> acheam: i think github is more apt for KISS related stuff, but i don't think it matters that much
2020-12-28T08:08:00 #kisslinux <eudaldgr> https://dylan.k1ss.org/ anyone know what's this?
2020-12-28T08:29:41 #kisslinux <aws> o/
2020-12-28T08:29:45 #kisslinux <testuser[m]> hi
2020-12-28T08:30:04 #kisslinux <aws> How are you all ?
2020-12-28T08:30:08 #kisslinux <aws> How's Dylan ?
2020-12-28T08:32:28 #kisslinux <travankor> o/
2020-12-28T08:39:23 #kisslinux <testuser[m]> eudaldgr: https://github.com/dylanaraps/dylan.k1ss.org/commit/66e96f278cbb207632accabcc3ec7723725b404f#diff-0eb547304658805aad788d320f10bf1f292797b5e6d745a3bf617584da017051
2020-12-28T08:41:44 #kisslinux <eudaldgr> yeah i see the commit
2020-12-28T08:42:00 #kisslinux <testuser[m]> not sure what thats supposed  to mean though
2020-12-28T08:43:53 #kisslinux <eudaldgr> that's my question, thanks
2020-12-28T10:13:34 #kisslinux <testuser[m]> danteissaias: could you fix shellcheck for  `lua-lpeg` and PR to kiss-community ?
2020-12-28T12:18:12 #kisslinux <eudaldgr> i can't build icu from community
2020-12-28T12:18:14 #kisslinux <eudaldgr> https://termbin.com/3ejl
2020-12-28T12:19:03 #kisslinux <eudaldgr> why they say that there is no c compiler compatible?
2020-12-28T12:24:18 #kisslinux <testuser[m]> eudaldgr `KISS_DEBUG=1 kiss b icu` and upload the config.log from build directory
2020-12-28T12:55:50 #kisslinux <eudaldgr> icu needs clang
2020-12-28T14:44:14 #kisslinux <claudia02> eudalgr : Re you icu issue: have a look here: https://freenode.logbot.info/kisslinux/20200715#c4400989 .
2020-12-28T15:16:09 #kisslinux <aosync> hey !
2020-12-28T15:16:18 #kisslinux <aosync> Does anyone know what happened to Dylan ?
2020-12-28T15:21:44 #kisslinux <midfavila> No idea
2020-12-28T15:21:49 #kisslinux <midfavila> He's been gone for over a month at this point
2020-12-28T15:22:08 #kisslinux <midfavila> been a semi-regular topic of discussion in here
2020-12-28T15:22:48 #kisslinux <aosync> Has anyone tried to contact his mother or brother or something ?
2020-12-28T15:22:58 #kisslinux <aosync> or himself, by email ?
2020-12-28T15:23:07 #kisslinux <midfavila> I wouldn't know, myself
2020-12-28T15:23:22 #kisslinux <midfavila> But I don't think it'd be the right time to call up his mum or something :v
2020-12-28T15:23:38 #kisslinux <midfavila> just poking dylan himself would be fine I imagine
2020-12-28T15:23:41 #kisslinux <aosync> lmao
2020-12-28T15:24:44 #kisslinux <midfavila> then again if he's not logging on to IRC I dunno if he'd be checking his email either...
2020-12-28T15:25:30 #kisslinux <midfavila> Looking at his commit schedule this year, an extended break isn't entirely unprecedented
2020-12-28T15:25:37 #kisslinux <midfavila> the timeframe makes sense too, imho
2020-12-28T15:27:07 #kisslinux <soliwilos> If he lives away from his family, he might've traveled there for christmas / new years? Maybe he also just needs some time to refresh.
2020-12-28T15:27:14 #kisslinux <midfavila> That's what I'm thinking
2020-12-28T15:27:27 #kisslinux <midfavila> Commits stopped rolling in around 'murican Thanksgiving
2020-12-28T16:28:51 #kisslinux <aarng> yeah, we should only start worrying about dylan after a couple weeks into the new year
2020-12-28T16:33:16 #kisslinux <testuser[m]> Yep
2020-12-28T16:40:25 #kisslinux <acheam> testuser[m]: I ended up putting it on my sr.ht, but I could move it at some point. https://sr.ht/~armaan/kiss_cd
2020-12-28T16:40:42 #kisslinux <micr0> acheam i think its good to be conservative over whats kiss-community produces
2020-12-28T16:40:50 #kisslinux <acheam> micr0: yeah for sure
2020-12-28T16:41:03 #kisslinux <acheam> im making good progress on this, I think it will finally be the scalable solution we are looking for
2020-12-28T16:41:36 #kisslinux <acheam> And if it isn't, then at least I learned some Django :)
2020-12-28T16:43:45 #kisslinux <testuser[m]> acheam: yeah i checked your sourcehut repo, it can be mirrored to github later anyways if required
2020-12-28T16:43:57 #kisslinux <acheam> testuser[m]: sounds good!
2020-12-28T16:44:03 #kisslinux <testuser[m]> Also, great work :)
2020-12-28T16:45:12 #kisslinux <micr0> I feel so dumb not thinking of the fact that building binaries should first look at other binaries already build lol
2020-12-28T16:45:59 #kisslinux <micr0> scalable => we get to piggyback off the arch work xD
2020-12-28T16:46:14 #kisslinux <midfavila> Hey, nothing wrong with that :p
2020-12-28T16:46:20 #kisslinux <micr0> it looks cool, though I have frustrations with python whats most important is that it does the thing
2020-12-28T16:54:10 #kisslinux <aarng> anyone using nvi?
2020-12-28T17:43:10 #kisslinux <nerditup> is anyone able to explain what is happening on this line? https://github.com/kisslinux/kiss/blob/master/kiss#L45 -- I am trying to understand, why is $* passed in? why use a new file descriptor instead of just stdin? and finally, why redirect /dev/tty into stdin?
2020-12-28T17:45:53 #kisslinux <micr0> nerditup i can't look at the code / answer those questions, but i wonder if cross-references the pure posix and pure bash repos that dylan made would help
2020-12-28T17:46:01 #kisslinux <micr0> if you can see the same patterns they might explain things
2020-12-28T17:47:49 #kisslinux <nerditup> I am beginning to think that the busybox su implementation isn't strictly posix so it provides some niceties, for example doesn't cleanenv (hence $* is passed in)
2020-12-28T17:48:04 #kisslinux <nerditup> I'm comparing against the suckless su.c source
2020-12-28T17:48:25 #kisslinux <nerditup> s/cleanenv/clearenv
2020-12-28T17:48:29 #kisslinux <micr0> nerditup I think it would be awesome, if you do find out why any line works the way it does, to submit a PR with comments explaining what you find
2020-12-28T17:48:37 #kisslinux <micr0> no matter how small the understanding is
2020-12-28T17:50:29 #kisslinux <nerditup> ah my limited understanding would be exposed haha
2020-12-28T17:58:25 #kisslinux <aarng> I can explain *what* is happening, but not *why*
2020-12-28T17:59:05 #kisslinux <aarng> stdin is duplicated to file descriptor 3, stdin is then set to /dev/tty
2020-12-28T17:59:34 #kisslinux <aarng> the command to run with "$su" get's file descriptor 3 as its stdin
2020-12-28T18:01:05 #kisslinux <aarng> or rather: "the current stdin is backed up to file descriptor 3 [...]"
2020-12-28T18:04:08 #kisslinux <aarng> I would assume it's just so that the $su program can still read the password from the tty, while the program ran by $su retains the original stdin (e.g. when stdin is a pipe)
2020-12-28T18:05:22 #kisslinux <aarng> nerditup ^
2020-12-28T18:07:34 #kisslinux <nerditup> aarng: thank you for the explanation, I think the why might be better explained here, in this special case: https://github.com/kisslinux/kiss/blob/master/kiss#L1463
2020-12-28T18:09:01 #kisslinux <aarng> that does not explain it at all if you ask me
2020-12-28T18:13:19 #kisslinux <nerditup> what is `env $*` used for in this case?
2020-12-28T18:14:52 #kisslinux <aarng> it's the command run by the $su program
2020-12-28T18:14:57 #kisslinux <nerditup> I think that is where I thought the above link is useful, since it sets the environment of the su -c command to be whatever is set in file descriptor 3?
2020-12-28T18:15:19 #kisslinux <aarng> `env` in case any of the functions arguments are environment variable assignments
2020-12-28T18:15:30 #kisslinux <aarng> no
2020-12-28T18:15:50 #kisslinux <nerditup> "env(1) is to run a program in a modified environment" - maybe I'm misunderstanding
2020-12-28T18:16:06 #kisslinux <aarng> if I call `as_root HOME=/dev/null whoami -x`
2020-12-28T18:16:39 #kisslinux <aarng> the function calls `$su env HOME=/dev/null whoami -x <&3`
2020-12-28T18:17:07 #kisslinux <aarng> but yeah, the `env` program is to call programs with a modified environment
2020-12-28T18:17:56 #kisslinux <aarng> hope that makes sense :D
2020-12-28T18:18:02 #kisslinux <nerditup> what would be an example of something that wouldn't work if env $* wasn't there?
2020-12-28T18:19:06 #kisslinux <aarng> well the $* is always necessary, otherwise the function wouldn't pass the program to run to whatever $su is
2020-12-28T18:20:32 #kisslinux <aarng> the `env` I'm not so sure about. I guess it depends on how the su program calls other programs (if a shell is involved)
2020-12-28T18:20:53 #kisslinux <nerditup> ignorant me is thinking, what's wrong with `su -c "$1" "$2"` :D
2020-12-28T18:22:35 #kisslinux <nerditup> as_root "HOME=/dev/null id -u" someuser, in my ignorant case
2020-12-28T18:25:02 #kisslinux <aarng> yeah, the latter should be possible
2020-12-28T18:25:08 #kisslinux <aarng> no idea why it's done that way
2020-12-28T18:25:38 #kisslinux <aarng> the former is not possible because there is still the trailing user argument
2020-12-28T18:28:00 #kisslinux <aarng> but then you could also do `su "$user" "$@"` I guess
2020-12-28T18:29:58 #kisslinux <nerditup> aarng: thanks for entertaining my inquiries, appreciate the help
2020-12-28T18:31:22 #kisslinux <aarng> I enjoy figuring out things like this too, so np :)
2020-12-28T18:41:59 #kisslinux <nerditup> aarng: you're right! the file descriptor juggling act is to allow the user to enter in the password without getting overwritten by the stdout
2020-12-28T18:42:28 #kisslinux <aarng> yup
2020-12-28T18:43:13 #kisslinux <aarng> the question is, when would that function (or the entire kiss script for that matter) not have the tty as its stdin
2020-12-28T18:43:16 #kisslinux <nerditup> I did a quick test between `su -c "$*"` and `su -c "$* <&3" 3<&0 </dev/tty`
2020-12-28T18:43:55 #kisslinux <nerditup> yeah, planning ahead I guess
2020-12-28T18:44:14 #kisslinux <aarng> that's what I thought too
2020-12-28T18:45:25 #kisslinux <nerditup> I think that makes me more confident in the why, as much as we can guess without asking him of course