<zlib>
hiya last troubleshoot why do i get this error when trying to build efivar, its half four in the morning i cant read properly https://0x0.st/HenF.txt
<sewn>
god damn it
<sewn>
you have to fork efivar and add the lfs64 patch
<zlib>
sewn me and u are gonna be best friends i jus know it !!!
<sewn>
give me a second
<sewn>
zlib: go into your repository directory `/var/db/kiss/repo` and run `curl https://termbin.com/q11yf | patch -p1`
<sad_plan>
you forgot < nameofpatch after -p1
<sewn>
patch -p1 takes from stdin
<sewn>
when you do < the shell forwards the file to the program's input
<sad_plan>
I was going to suggest that
<sad_plan>
right
<sewn>
what i did here is put the repository lfs64 efivar patch into a snippet and have curl output it and patch take it as input and patch as normal really
<sewn>
i love shell
<zlib>
i dont think it worked hold on
<sewn>
oh no
<sad_plan>
shell is great
<sewn>
oh bruh my bad i forgot to add the patch to git diff
<iceman[m]>
cuz i distinctly remember a lot of members having profile pictures
<iceman[m]>
and then suddenly many became [m] people with no profile pictures (aka bridge users)
<iceman[m]>
and i was like what happened
<sewn>
🐱
<iceman[m]>
this is so confusing
<iceman[m]>
is this a "new" channel?
<sewn>
we'll see what happens on july 30
<iceman[m]>
did you leave the "old" channel?
<sewn>
i kicked myself out of it
<iceman[m]>
oh
<sewn>
idk it took some fiddling to do, it fixed itself
<sewn>
i didn't appear on the IRC end once
<iceman[m]>
@testuser so i think what im gonna take is take my kiss rootfs to Canada in my ssd, and then put it in new laptop, then use some livecd to make a kernel for that, and edit my /etc/fstab, and reinstall the bootloader
<iceman[m]>
mm bun
<iceman[m]>
yummy
<iceman[m]>
ill see you on the otherside, updating my system after i installed kiss 😂
<iceman[m]>
I love source based distributions
<iceman[m]>
nothing ever breaks
<sewn>
genchu
<iceman[m]>
ill be off now
<sewn>
when will you be turned on
<sewn>
no i dont mean that in the
<sewn>
ok whatever that was a horrible mistake
<schillingklaus>
I am restricted to cli apps, anyways, as I cannot stand wayland
<sewn>
what about xorg
<schillingklaus>
hasn't xorg been kicked from kiss in 2021?
<sewn>
kiss-xorg :3
<iceman[m]>
<sewn> "when will you be turned on" <- i am on
<iceman[m]>
mobile
iceman[m] has left #kisslinux [#kisslinux]
<sewn>
i see
<sewn>
damn you got kicked
iceman[m] has joined #kisslinux
<iceman[m]>
sewn: yea
<iceman[m]>
i left old channel
<iceman[m]>
got kicked from both
<iceman[m]>
bot smokin
<sewn>
its smoking ice
<iceman[m]>
😳
<iceman[m]>
i have nodejs to compile as well lmao
<iceman[m]>
i hope 48 gigs is enough :trolol:
<iceman[m]>
i have htop opened in another terminal
<iceman[m]>
current ram usage is 345M
<sewn>
i tried to compile chromium but the build is broken so
<iceman[m]>
F
<sewn>
iceman[m]: 6 is plenty i said
<iceman[m]>
sewn: you created an issue about the lfs64 right
<sewn>
just for nodejs, llvm, firefox and such
<sewn>
iceman[m]: no its another thing
<iceman[m]>
i tried to compile chromium but the build is broken so
<iceman[m]>
* In reply to @sewn:envs.net
<iceman[m]>
you created an issue about the lfs64 patch right
<sewn>
chromium doesnt need lfs64, but rust does and thats significantly more important
<iceman[m]>
oh explane
<sewn>
no one here can build rust with rust
<iceman[m]>
what is it
<sewn>
s/with/without/
<iceman[m]>
i just use rustup
<iceman[m]>
i dont want the headache
<sewn>
its not packaged
<iceman[m]>
sewn: who said I needed it packages :chad:
<iceman[m]>
* In reply to @sewn:envs.net
<iceman[m]>
who said I needed it packaged :chad:
<iceman[m]>
its not packaged
<iceman[m]>
its not packaged
<iceman[m]>
* In reply to sewn
<iceman[m]>
who said I needed it packaged :chad:
<xdream8[m]>
sewn: i have both binary and source package in my repo
<xdream8[m]>
i will implement 'replaces' feature when i am done implementing other features. its really problematic when you want to replace a package like ncurses. you have to fork all packages that depends on them and change ncurses dep
<xdream8[m]>
iceman[m]: i was working on a service manager but i am only working on kiss-rs right now because i want to finish and use it soon as possible
<schillingklaus>
ah, kiss-xorg .. I would still need to install a keyboard-only windows manager from upstream sources, but I've had to do that before. window managers can be easily installed per user.
<xdream8[m]>
kiss-install is almost finished. the only thing left is improving pkg_conflicts function to register alternatives correctly
<iceman[m]>
I was going to work on my tftp implementation but decided to update my system
<iceman[m]>
xdream8[m]: I see
<iceman[m]>
iceman[m]: in C++ btw
<iceman[m]>
i hope you're annoyed :troll:
<sewn>
😯😯😯😯😯😯😯😯😯😯😱😱😱😱😱😱
<phoebos>
xdream8[m]: do you have setuid on kiss-install or expect it to be run under sudo etc ?
<xdream8[m]>
iceman[m]: a little
<iceman[m]>
i'm in desperate need of emojis
<phoebos>
how does kiss-install know which user's cache to look into for tarballs
<xdream8[m]>
phoebos: i did not decide that yet but setuid would be better
<iceman[m]>
xdream8[m]: its okay, i just wanted to know that you're not like other Rust users who insert rust into everything
<iceman[m]>
just use what you want/like
<phoebos>
I understand you're moving kiss's env vars to flags, but I don't see a flag for XDG_CACHE_HOME
<schillingklaus>
such as linus torvalds who inserts rust into the kernel?
<xdream8[m]>
<phoebos> "how does kiss-install know which..." <- it uses "$XDG_CACHE_HOME" env variable for now i will switch to flag approach eventually but i will still continue supporting some of the env variables but flags wil be the main priority
<iceman[m]>
going full qemu
<iceman[m]>
ahh
<iceman[m]>
llvm time
<sewn>
im still trying to build chromium in a tmpfs
<sewn>
because for some odd reason one cant run bootstrap.py under tmpfs but is fine under cache
sad_plan has joined #kisslinux
<sad_plan>
hi
<sewn>
hi sad_plan
<phoebos>
ah setuid preserves environment
<phoebos>
nice
<sewn>
is ioraff not in this irc channel?
<sad_plan>
nope
schillingklaus has quit [Remote host closed the connection]
<iceman[m]>
hi sad_plan
<mako2>
hi everyone
kiedtl has joined #kisslinux
<sewn>
hello everynyan
<sad_plan>
hi mako2
kiedtl has quit [Read error: Connection reset by peer]
cot|th has joined #kisslinux
<mako2>
I think i fixed the efi thing in my kiss, efibootmgr shows results now and the kiss bootloader id stays there after reboots
cot|th is now known as kiedtl
<sewn>
nice
<mako2>
the problem is the kernel i compiled, tested it on void and did the same stuff, stuck at loading the kernel
<sewn>
you can use only efibootmgr, or no bootloader at all btw
<mako2>
so its my stupid brain that cant figure out how to make a kernel work
<mako2>
yeah but i cant figure out how to do uefi without grub
<sewn>
you can use efibootmgr
<sewn>
or noone
<mako2>
i see
<sad_plan>
sewn you can use only the kernel aswell. no grub, no efibootmgr. nothing. just the kernel
<sad_plan>
just look up efistub
<sad_plan>
requires uefi though
zlib has joined #kisslinux
<zlib>
how in the world do u start xorg theres like a million problems
<zlib>
i dont even know where to start to trouble shoot
<sewn>
<sad_plan> "sewn you can use only the kernel..." <- thats why i said none
<sewn>
i use that method myself
<sewn>
zlib: logs
<zlib>
which logs do u want ive gotten about 20 different ones
<sewn>
xorg tells you where the log is, usually .local/share/Xorg/xorg.0.log of some sort
<zlib>
very sorry to whomever owns 0x0 btw !!! am abusing ur website
<zlib>
yea
<sewn>
zlib: you can use x0 or termbin.com
<sewn>
zlib: `groups` is `kiss tty audio video input`
<sewn>
?
<zlib>
oh
<zlib>
i reran it again n now we're jus back at the start
<zlib>
nvm no we're not i was root
<zlib>
still where we were x
<sewn>
yuherdgberafgzuiohjkdfgzbuiohkladfzuohj;etsdyuiohwerta789yioyuiohwrsfg8yihwrsfgyiwrsfg7yh79yuio7yuhwrsfgxyuhwrasfg7ywrasfg7ywrsfgawrazgrwa7yurwa478g234qwz7gby4wr28i9g24qwr84rg6y789uwrg47wery789qtyr4127ygyq2hgt47uhygfu7rfgbhygg7wrag7wrqgy72w g 7yqrgqr7y 7yq7yrweygqwra9gaebewu7gbrfwyh79uqrg8y\90w80y\wry80ry\y248ryy\24wa24r
<zlib>
exactly
oak[m] has joined #kisslinux
<zlib>
AHA
<zlib>
i found it
<sewn>
found wut
<zlib>
someone said reinstall xorg server so i did and got a curl error 6
<zlib>
idk what that is i was too excited to tell u
<zlib>
i literally added myself to it !!! like three times
<sewn>
zlib: mdev isnt running
<sad_plan>
its abit like sudo su really
<zlib>
u n me
<zlib>
are gonna fall out
<sewn>
ln -s /etc/sv/mdev /var/service
<zlib>
it says
<zlib>
file exists
<zlib>
just remove it ?
<sad_plan>
check whats there. I think you need the last /
<sad_plan>
else youll symlink to service dir
<sad_plan>
like the actuall dir, not inside it
<sewn>
sv s mdev
<oak[m]>
zlib: nope
<oak[m]>
no need
<oak[m]>
if its already tehre
<sewn>
run as superuser if necessary
<sad_plan>
does runit accept s flag? instead of start or up?
<sewn>
what?
<sad_plan>
sv s $serv
<zlib>
ive just been told like 4 different things
<sad_plan>
instead of sv up $serv
<zlib>
sv s mdev returns pid 142
<sad_plan>
hm, so it does
<sad_plan>
I dont use runit, so I couldnt check really
<sewn>
just reboot
<sewn>
jeez
<sewn>
i think ur vm hates u zlib
<zlib>
i only wanted to try it in a vm so i could be used to it when i do it on my lapto
<zlib>
p
<zlib>
but i guess ill jus go straight for it
<zlib>
okay im back to the exec sowm permission denied thingy again
<sad_plan>
chmod 0755 /bin/sowm
<sad_plan>
as root, obviously
<zlib>
now it doesnt even give me an error
<sewn>
sad_plan: sowm is 0755
<zlib>
it jus boots then kicks me out to the tty
<sewn>
his filesystem is weird
<zlib>
his ??? behave
<sad_plan>
hm, do you have xf86-input-libinput?
<zlib>
also my log file is exactly the same
<zlib>
yea
<zlib>
i do
<sewn>
so weird
<zlib>
i can rebuild it
<zlib>
sec
<sewn>
rebuilding wont help that much
<zlib>
yea
<zlib>
no
<zlib>
same thing
<oak[m]>
ls -l /dev/tty1
<oak[m]>
are you in the tty group? @zlib:libera.chat
<zlib>
yea
<sad_plan>
have you tried another wm? like xwm or some shit
<sad_plan>
to rule out sowm
<sewn>
also, can you try showing the output of ls -l / /usr ?
<sewn>
sad_plan: or dwm
<sewn>
dwm my belovede
<sad_plan>
what you also can do is try to launch x without a window manager. but you have to have a way to start a terminal or something
<sad_plan>
exec sxhkd i.e. in you xinitrc should suffice
<oak[m]>
plain startx should be x and like 3 xterms
<sewn>
^ without a .xinitrc
<zlib>
im gonna try redoing x and then what sad said
<zlib>
will see u in 5 mins love u x
<sad_plan>
you can also just use sx instead, its simpler. sometimes I couldnt get x to start with xinit, but sx worked. and vice versa. sx doesnt give too much feedback though
<oak[m]>
yeah said the same thing earlier
<zlib>
I DID IT
<zlib>
im so fucking clever
<zlib>
oh my god
<sewn>
how did you fix it!??!
<zlib>
i have no idea
<zlib>
i reinstalled everything x, added myself to groups again, tried to use sx but needed rc so used start and it booted twm
litharge has joined #kisslinux
mako2 has quit [Remote host closed the connection]