<midfavila>
^alpha of my http client if anyone wants to look at it
<midfavila>
super not-good but it *does* seem to work reliably with small files, at the very least. caveats: only implements super basic HTTP1.0 GET, doesn't validate URIs properly, doesn't have TLS support yet
<wael_>
Hi
sad_plan has quit [Quit: nyaa~]
<phoebos>
mid: looks like a nice start, you have better overall design than me; I tend to just dump everything in main and only make structs when absolutely necessary
<phoebos>
btw recv(2) can return -1 on error, but your for loop will ignore that
<phoebos>
so it enters an infinite loop for me
<midfavila>
do you happen to use glibc?
<phoebos>
no
<midfavila>
hmmmmmmm
<phoebos>
that's POSIX
<midfavila>
yeah, I know
<midfavila>
only asking 'cause someone else mentioned the same thing to me
<midfavila>
anyway, main's layout is going to be overhauled once I implement TLS -- i threw it together in like five minutes
<midfavila>
should be fine then
<phoebos>
also, your Makefile has a bug: fetch is built because BIN is the default target, but `make all` will dereference a ${B} variable that doesn't exist
<midfavila>
yep
<midfavila>
also something i threw together without thinking
<phoebos>
no worries
<phoebos>
just mentioning it in case
* midfavila
nod-nods
<midfavila>
it also doesn't help that i don't know how to write makefiles lmao
<midfavila>
but yeah, from the get go I wanted to make the design as generic as I could
<midfavila>
it should be easy to extend it to handle other protocols
<phoebos>
looks like what hurl wanted to do
<phoebos>
in terms of code layout
<midfavila>
that's high praise :p
<phoebos>
:v hurl is a mess
<midfavila>
i need to replace the calls to open and write with fopen and fwrite at some point too
<midfavila>
and yeah hurl is a clusterfuck
<phoebos>
one function per protocol, every one essentially the same
<midfavila>
bleh
<wael_>
macslash1:
<phoebos>
i can't stand your syntax style, though :p
<midfavila>
yeah it seems to be a controversial thing
<midfavila>
whitesmith>knr though
<midfavila>
i can't stand KnR style
<midfavila>
makes it way too hard to follow the shape of the program
<phoebos>
i'm accustomed to using K&R as a visual aid, but I can imagine it just depends on what you're used to
<midfavila>
almost certainly
<midfavila>
i'm used to programming in scheme, where indentation is like
<midfavila>
the *only* reflection of the procedure's evolution
<midfavila>
so if it's not a somewhat lispy style of indentation i get lost really fast
<phoebos>
the first program i wrote in scheme i tried to indent like K&R C
<phoebos>
one thing that confused me was the whole stuff about shutdown and recv returning EOF, but skimming through a TCP textbook helped with that
<testuser[m]>
> very minor potential for a segfault here
<midfavila>
i never said it was gooooooooooooooooooooooooooooooooooooood-
<phoebos>
doesn't have to be good, i hope you enjoy fiddling around learning and digging up bugs
<midfavila>
well, hope is that it'll eventually become good
<midfavila>
i kinda need it to :v
<phoebos>
:v
<midfavila>
can't build any decent http clients on my latest rootfs sooooooo
<phoebos>
if you want a patch to fix things lmk
<midfavila>
maybe once it's beta quality
<midfavila>
will keep in mind
<phoebos>
sure; if it were me, I'd rather be left to figure it out
<phoebos>
anyway, goodnight \o
fitrh has joined #kisslinux
trunc88 has joined #kisslinux
Torr has quit [Remote host closed the connection]
fitrh has quit [Quit: fitrh]
<testuser[m]>
Personally, I wish they would step back and stop adding hacks on top of mmap. The API is seriously flawed because it conflates a load of things: allocating virtual address space, permissions on that address space, and backing store. It does all of these things with no permission model. OpenBSD would be in a good position to design and ship a deconflation of these. Brooks Davis proposed a ‘cookie mmap’ a few years ago that started
<testuser[m]>
this, where the call to allocate address space returned a capability that then gave you the rights to change the mapping, you could only do mprotect or MAP_FIXED-like things if you had that capability. Once you have such a model, it becomes quite easy to add a richer set of permissions, including dropping the right to subsequently modify the mapping.
<testuser[m]>
How should sandbox be handled for go/rust packages (network) or pgo packages (filesystem)
<testuser[m]>
i mean foot pgo / firefox pgo
<testuser[m]>
Also ccache
chomwitt has joined #kisslinux
<illiliti>
sandbox should not allow network access for go/rust packages. it is out of question
<illiliti>
instead, packages should provide tarballs with vendored dependencies
<illiliti>
filesystem sandboxing is harder yeah
<illiliti>
maybe there should be some hook to dynamically add path exceptions
<illiliti>
dunno
<testuser[m]>
Ye that's wat i thoight
fdkol1 has quit [Ping timeout: 260 seconds]
<testuser[m]>
Same here, I would rather trust my data with our own government instead of the Chinese or US ones.
zlg has quit [Ping timeout: 268 seconds]
zlg has joined #kisslinux
aelspire has joined #kisslinux
zlg has quit [Ping timeout: 248 seconds]
zlg has joined #kisslinux
saturn[m] has quit [Quit: Bridge terminating on SIGTERM]
psydroid has quit [Quit: Bridge terminating on SIGTERM]
testuser[m] has quit [Quit: Bridge terminating on SIGTERM]
macslash1[m] has quit [Quit: Bridge terminating on SIGTERM]
virutalmachineus has quit [Quit: Bridge terminating on SIGTERM]
konimex has quit [Quit: Bridge terminating on SIGTERM]
wael_ has quit [Quit: Bridge terminating on SIGTERM]
saturn[m] has joined #kisslinux
wael_ has joined #kisslinux
testuser[m] has joined #kisslinux
psydroid has joined #kisslinux
konimex has joined #kisslinux
virutalmachineus has joined #kisslinux
macslash1[m] has joined #kisslinux
wael[m] has joined #kisslinux
<wael[m]>
testuser you scammed me
<testuser[m]>
what
<wael[m]>
wait i think it works
<testuser[m]>
bruh u cant see history for irc rooms
<testuser[m]>
cuz of settings
<wael[m]>
oh yea ru
<wael[m]>
well it DOES work fluffychat lied to me
<wael_>
yeah u right
<testuser[m]>
lol does this channel have no modertators
<wael[m]>
ioraff is the irc moderator technically
<testuser[m]>
only acheam is according to the bridge
<wael[m]>
who dat
<illiliti>
testuser[m]: speaking of pgo, do you think it is good idea to move foot-pgo to community?
<illiliti>
because i don't believe it should be in main repo. we already have general-purpose foot package after all; i don't see why we should maintain foot-pgo
<wael[m]>
hi illiliti
<illiliti>
hi
<testuser[m]>
all variations of a given pkg should probably be in the same repo as the original
<illiliti>
the point is, does it really bring so much value to be in main repo?
<illiliti>
or alternatively, who uses it?
<testuser[m]>
me
<testuser[m]>
its easier to keep in sync
<illiliti>
ok
<illiliti>
i will never understand these micro-optimizations, especially for small programs
<testuser[m]>
ye i dont think it has any benefit lol
<testuser[m]>
you're not catting /dev/urandom constantly
<testuser[m]>
should probably be rmeoved
<wael[m]>
should probably be meowed
<illiliti>
i can undertand the need for pgo'd firefox or chromium. there it will have a use, but foot... i'll never understand that
aelspire has left #kisslinux [#kisslinux]
wael[m] has left #kisslinux [#kisslinux]
wael[m] has joined #kisslinux
wael[m] has left #kisslinux [#kisslinux]
wael[m] has joined #kisslinux
midfavila-mobile has joined #kisslinux
<midfavila-mobile>
holy shit you guys, i actually *slept* last night- feel like i'm gonna live forever
<wael_>
do you not sleep
<midfavila>
i do not
<wael_>
well you gotta have some sleep
<wael_>
its very important for you
<midfavila>
yes I know :v
<midfavila>
it's not for lack of trying
<wael_>
can you re-phrase that
aelspire has joined #kisslinux
<aelspire>
Hi, I've managed to make touchpad working in linux kernel. It was hellish ride. Much more problematic than my root drive missing due to lack od VMD. And now my kernel config is a mess. Anyone have idea how to nicely organize kernel config? I consider something like git repo containing empty config and in separate commits I'm adding more functionality for e.g commit: Make touchpad working. Anyone have better idea?
<aelspire>
Main problem with git repo will be config changes due to new kernel versions
Guest98 has joined #kisslinux
midfavila has quit [Remote host closed the connection]
midfavila has joined #kisslinux
Guest98 has quit [Quit: Client closed]
fdkol1 has joined #kisslinux
van2022 has joined #kisslinux
<van2022>
How assemble from parts kisslinux-live.iso?
<van2022>
I myself found
van2022 has quit [Remote host closed the connection]
van2022 has joined #kisslinux
midfavila has quit [Remote host closed the connection]
trunc88 has quit []
midfavila has joined #kisslinux
<van2022>
I have kiss-chroot.tar.xz file. How can I make an iso? github.com/kiss-community/kiss-live
<aelspire>
van2022: Why You want iso?
fdkol1 has quit [Ping timeout: 260 seconds]
<van2022>
to write it to a flash drive
<aelspire>
van2022: I guess You want to install KISS and want Live USB?
<aelspire>
kiss-chroot is just root without linux kernel it won't boot
<aelspire>
You need liveCD from other distro to install KISS
van2022 has quit [Remote host closed the connection]
<aelspire>
it is possible to steal kernel with firmware and modules from other distro and repack kiss-chroot via cpio as initramfs and boot it
van2022 has joined #kisslinux
<aelspire>
but it's rather cumbersome
<van2022>
the iso file will weigh many megabytes?
<aelspire>
you was offline so I repeat: "it is possible to steal kernel with firmware and modules from other distro and repack kiss-chroot via cpio as initramfs and boot it"
<aelspire>
bare chroot will not boot
<aelspire>
as it has no linux kernel
<aelspire>
you should use other distro's LiveCD to unpack this kiss-chroot on freshly formatted disk
<aelspire>
follow official instalation guide and use other LiveCD, I suggest to use something with the same linux kernel version as You want
<van2022>
I'll finish this job tomorrow. leaving the chat
van2022 has left #kisslinux [#kisslinux]
aelspire has left #kisslinux [#kisslinux]
sad_plan has joined #kisslinux
<sad_plan>
o/
<sad_plan>
aelspire: what issue do you suppose is there when having your kernel config tracked with git? I do this, and tbh, its a great way to keep track of it. however I have in a kiss repo, and have kiss build my kernel for me instead of doing it manually