<micr0>
grr, this device doesn't show up on my pi, my laptop, or my windows desktop :/
m3g has joined #kisslinux
<noocsharp>
have you considered plugging it in?
micr0 has quit [Ping timeout: 264 seconds]
AAAA has joined #kisslinux
<AAAA>
hi! I just finished the base install of kiss and booting, I will press the option to load the kernel and I get "Loading kernel <INS version number>...." and nothing else will happen
sad_plan has quit [Read error: No route to host]
<Sweets>
AAAA: The loading kernel version message is done by the bootloader, nothing else happening could be a few reasons
<midfavila>
thanks, but I already packaged it myself - unrelated, what are your recommendations for a debloated emacs experience, acheam?
<midfavila>
is there any way to remove the three different calculators and all the games?
<rio6>
emacs come with 3 calculators and games? lol
<midfavila>
also a web browser, shell, psychologist, IRC client...
<midfavila>
if I could have *just* the editing functions, I'd be much happier
<rio6>
<insert joke of emacs lack a good text editor>
<midfavila>
the text editor is alright, honestly - if I could have a stripped-down GTK2 emacs without all the extraneous crap, that would be awesome. I just want to have its LISP-related functionality.
<AAAA>
is this an error I should worry abt? grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=kiss
<AAAA>
Installing for x86_64-efi platform.
<AAAA>
modprobe: can't change directory to '5.8.0-25-generic': No such file or directory
<acheam>
midfavila: how did you package it?
<acheam>
compared to minr
zenomat has quit [Ping timeout: 268 seconds]
<midfavila>
right now it's kind of shit, but I added a step to check for if there's a pre-existing SBCL or ECL on the system
<midfavila>
in the future, if there isn't, I'm going to have the package bootstrap a temporary ECL toolchain
<acheam>
ah nice
<midfavila>
yeah
<midfavila>
ECL is so fucking slow, dude
<acheam>
I just hard make depped on ecl
zenomat has joined #kisslinux
zenomat has quit [Changing host]
zenomat has joined #kisslinux
<rio6>
AAAA: if grub finishes with 0 and it boots then maybe not :P
<midfavila>
i'm starting to hate quicklisp
<AAAA>
I am currently trying to find out why it is not booting :(
midfavila-laptop has joined #kisslinux
<midfavila-laptop>
Anyone getting a segfault on the community Emacs package?
AAAA has quit [Quit: Client closed]
sad_plan has joined #kisslinux
AAAA has joined #kisslinux
<AAAA>
ok im back
<AAAA>
and I dug around
<AAAA>
and the issue seems to be when i try to boot
<AAAA>
I get ``error: no suitable video mode found``
<sad_plan>
did you compile the correct drivers for your hardware though?
<AAAA>
i have amdgpu firmware in /usr/lib/firmware and I have it compiled as a module in my kernel
<sad_plan>
recompile, but not as module.
<AAAA>
ok
<sad_plan>
its not loading the modules, because the system doesnt know it needs them. you can use modules, but its adviced against doing so. with kiss anyway that is.
<sad_plan>
you can use modules, but you just have to configure your system to start them on boot. its just alot easier to compile them straight into the kernel.
<sad_plan>
how do I make a package read the file in files dir inside builddir? im trying to package the kernel for easier upgrading it, but it doesnt read the file.. just complains that it isnt there
<AAAA>
okay I rebuilt amdgpu directly into the kernel
<AAAA>
rebooting
AAAA has quit [Quit: Client closed]
midfavila-laptop has quit [Ping timeout: 244 seconds]
<noocsharp>
sad_plan: did you add it to the sources file?
<sad_plan>
no, I did not. perhaps thats the issue. but now that you mention it. Ive seen it in several places. Ill dig into that right away!
<sad_plan>
yeah that was indeed it. cheers
GalaxyNova has joined #kisslinux
<GalaxyNova>
What are some good IRC clients in the repositories?
<noocsharp>
catgirl
micr0 has joined #kisslinux
<sad_plan>
GalaxyNova: kirc or irssi is also in the repos. both written in C afaik. theres also birch, which is just a bash script. I personally use birch
sad_plan has quit [Read error: No route to host]
micr0 has quit [Ping timeout: 244 seconds]
<testuser[m]1>
Hi
<dilyn>
o/
schillingklaus has joined #kisslinux
smartin has joined #kisslinux
GalaxyNova has quit [Read error: Connection reset by peer]
<testuser[m]1>
dilyn: there seems to be a checksum mismatch with tiff
<dilyn>
absolutely love when they do stuff like that
<schillingklaus>
that's all HatRed's fault
<dilyn>
hmmm
<dilyn>
there doesn't seem to be?
<testuser[m]1>
Lol
<testuser[m]1>
it broke 2 times
<testuser[m]1>
worked on the 3rd download
<dilyn>
also love that :v
<schillingklaus>
is it possible that a mismatch exisrts only for amd64 but not for the rpi architecture, or v.v.?
Uks2 has quit [Ping timeout: 272 seconds]
Uks2 has joined #kisslinux
chaffity has joined #kisslinux
mulc has joined #kisslinux
gtms has joined #kisslinux
claudia has joined #kisslinux
<claudia>
jedavies: I had no luck also to build serious-engine. It fails at 40% ish at "libentitiesMP" with _uint64 something.
<chaffity>
claudia thanks for the fix to love by the way, I did the same in my own repository, but wasn't sure if there were unwritten rules about using archives vs releases from GitHub
<jedavies>
claudia: I got it to build, had to patch Engine/Base/Types.h: http://0x0.st/-LYH.txt . However nothing happens when I run ssam. Maybe missing data files?
<jedavies>
This is with clang though
<testuser[m]1>
did you try an strace ?
<claudia>
chaffity: I think what ever works. And gnu configure is preferred over cmake because one less dep to build stuff. Honestly I had not looked deep into it before <.<
<claudia>
jedavies: It still fails. I have to get clang and llvm then.
<claudia>
As I understand you need th *.gro files from the install CD.
<claudia>
I have packaged bchunk and bin2iso if you have your game as .bin .cue available.
<jedavies>
Thanks, will try building with the data files as in the readme. Think I have a copy of the game somewhere around here...
Sweets has joined #kisslinux
<Sweets>
yonk
<claudia>
jedavies: This is the build failing with gcc. http://ix.io/3pV1 The clang build fails at the end while linking. http://ix.io/3pV4
<jedavies>
For the clang one, looks like it needs "-lc++abi -lc++". But that's what I'd do since I'm on libc++, not sure about libstdc++/gcc.
<testuser[m]1>
Did you export CXX to clang by mistake instead of clang++?
<claudia>
testuser[m]1: yes (:
<testuser[m]1>
lol
snakedye has joined #kisslinux
soliwilos has quit [Quit: nyaa~]
<Sweets>
snakedye: wo
<snakedye>
hello sweets
<testuser[m]1>
hi
<snakedye>
hi
<snakedye>
I don't even use kiss but birch brought me here
<Sweets>
who
<Sweets>
and I don't use kiss either, not actively anyways
<snakedye>
I think birch is dylan's irc client
<Sweets>
interesting
<Sweets>
I might try it out
<Sweets>
sec
Sweets has quit [Quit: leaving]
<claudia>
jedavies: Ok nice. I have got it to build and start. Its just missing some level stuff for now.
illiliti has joined #kisslinux
<claudia>
Build succeded with clang.
Sweets has joined #kisslinux
<Sweets>
test?
<Sweets>
hello?
<snakedye>
hi
<Sweets>
wo it works
<snakedye>
:)
<Sweets>
interesting. I didn't need to message the nickserv?
<Sweets>
weird
<snakedye>
don't really know how to dping someone with birch.
<Sweets>
dping?
<snakedye>
ping
<Sweets>
o
<Sweets>
idk
<Sweets>
I like this a lot more than irssi tho
<Sweets>
snakedye: I just put their name in front, like so
<snakedye>
Sweets like this?
<Sweets>
yuh
<snakedye>
nice
<snakedye>
It's comfy. I prefer it to weechat
<Sweets>
it's actually one of the nicer ones I've used
<Sweets>
simplistic in it's ui, normally the other clients just throw a bunch of dog shit on the screen and call it good
<snakedye>
weechat is probably one of the worst offender. the default config is disgusting
<Sweets>
idk man, irssi is pretty fuckin bad
<snakedye>
i'll check it out
<Sweets>
I can send you a screenshot
<snakedye>
sure
<Sweets>
pinged on discord
<chaffity>
I love how Dylan put so much effort into making KISS and other projects shell agnostic, but also wrote incredible things like Birch in Bash
<Sweets>
all in good fun
<snakedye>
yeah it's insane. he's a bash magician
<Sweets>
irc client in C isn't all that impressive; irc is just connecting to a socket and follow an extremely simple protocol
<chaffity>
It's less than 500 SLOC, including comments, what a legend
<Sweets>
irc in a shell is quite hard, most shells don't provide methods of creating a socket connection... bash does though ;)
necromansy has joined #kisslinux
<snakedye>
ohhh is dylan back?
<snakedye>
his gh has been active recently
<chaffity>
*nods*
<Sweets>
yo wait a fuckin minute
<Sweets>
he's back?
<Sweets>
where he at then
<chaffity>
@sweets is Bash the only shell you can do that in? Birch is writing to /dev/tcp, which any other shell could do, right?
<Sweets>
no, they can't
<testuser[m]1>
its created by bash
<Sweets>
\/dev/tcp is not a real device mounted by the kernel
<chaffity>
Learn something every day
<Sweets>
it's virtually created by bash
<Sweets>
and only exists in the bash run time
Uks2 has quit [Quit: Byee]
Uks2 has joined #kisslinux
claudia has quit [Quit: zzz]
<phoebos>
midfavila: git.sdf.org's SSL cert has expired :p
<illiliti>
we concluded that he needs some time to reunite with the community
chaffity has quit [Quit: Client closed]
<midfavila>
phoebos yeah, I know
<midfavila>
tell that to SDF membership, I can't do anything about it
<midfavila>
it's prolly already been reported
m3g has joined #kisslinux
chaffity has joined #kisslinux
soliwilos has joined #kisslinux
midfavila-laptop has joined #kisslinux
mulc has quit [Quit: WeeChat 3.1]
mulc has joined #kisslinux
<Sweets>
making a wm for macos is so much more fun than for linux
<Sweets>
it's more like a puzzle, since there's no api you can use to make one
<midfavila-laptop>
sounds more like a pain, to me......
<Sweets>
not at all
<schillingklaus>
i guess a keyboard-only wm is impossible on maco$$$$
<Sweets>
I mean, sure, but if you're programming and you don't ever encounter something that requires more than 2 brain cells, are you really programming?
<Sweets>
schillingk: It's completely possible
<midfavila-laptop>
Fair enough, Sweets.
<midfavila-laptop>
One of the things I'd like to try (no idea how successful it would be...) would be hooking up a Geiger counter to my PC via i2c
<midfavila-laptop>
use it as a source of additional entropy, or whatever
<schillingklaus>
near tchernobul ?
<midfavila-laptop>
Not even on the same continent.
<midfavila-laptop>
But it would be a good exercise
m3g has quit [Ping timeout: 272 seconds]
<schillingklaus>
can hummingbird be ported to OSX?
<omanom>
testuser[m]1 thanks! I'll try it out at some point!
<testuser[m]1>
np
snakedye has quit [Ping timeout: 244 seconds]
Sweets has quit [Ping timeout: 264 seconds]
<acheam>
midfavila-laptop: No, com.unity emacs works for me
<omanom>
hey guys i finished the kiss package manager in python, little more complex than i was hoping but the performance is VERY close to shell version
<phoebos[m]>
wow looks like you got most of the same functionality, im impressed
<midfavila-laptop>
very impressive work
<midfavila-laptop>
very terse
<omanom>
i thought you'd be impressed, mid. only a couple hundredths of a second difference now!
<midfavila-laptop>
i'm so impressed, in fact, that I've now decided to become a python evangelist
<midfavila-laptop>
you've shown me the light
<midfavila-laptop>
speaking of "seeing the light"
<omanom>
you are now an honorary lizard person! ... whoops i mean python person ...
<midfavila-laptop>
after playing with stumpwm for a bit, I think I see why people like tilers
<omanom>
next you're gonna start using gaps between your windows
<midfavila-laptop>
that would be cringe and reddit-pilled
<midfavila-laptop>
so no
<omanom>
this is truly the strangest timeline
<midfavila-laptop>
i'm not
<midfavila-laptop>
only reason I'm considering switching on my laptop is because a:
<midfavila-laptop>
1366x768 is a criminal resolution
<midfavila-laptop>
and b: it's an excuse to learn Common Lisp
<omanom>
tilers are essentially tmux for graphical applications, i can understand their appeal for sure
<omanom>
stumpwm configuration is lisp?
<midfavila-laptop>
the whole thing is lisp
<midfavila-laptop>
written in lisp, configured in lisp
<omanom>
oh nice!
<midfavila-laptop>
it's designed to be integrated with - bleh - emacs
<midfavila-laptop>
which I can't use even if I wanted to, since the package segfaults for me
<omanom>
oh my interest just disappeared
Uks3 has joined #kisslinux
<testuser[m]1>
gdb it
<omanom>
it would still be useful to read through its code though
<midfavila-laptop>
although tbf omanom I don't know *how* it's "integrated"
<midfavila-laptop>
it might just be because it shares command chord-style controls
<midfavila-laptop>
nah, like, the build itself segfaults. I can't even get a binary, testuser[m]1
<testuser[m]1>
Lol
<testuser[m]1>
Wtf
<midfavila-laptop>
welcome to the weird, weird world of my system
Uks2 has quit [Ping timeout: 272 seconds]
<midfavila-laptop>
i've had packages segfault so badly that they boot me out of X
<midfavila-laptop>
crash their window, crash my WM, crash my DM
<midfavila-laptop>
and finally crash X
<midfavila-laptop>
it's kind of impressive
<Erus_Iluvatar>
Cascading failure
<midfavila-laptop>
mhm
<midfavila-laptop>
oh, okay, I see what's going on with emacs
<midfavila-laptop>
it builds a bootstrapper and then the *bootstrapper* is what segfaults
<midfavila-laptop>
nice
<midfavila-laptop>
much clearer and easier to fix.
<chaffity>
Is it because you're booting an OS in your OS...
micr0 has joined #kisslinux
<chaffity>
KVM or Qemu might be helpful
<midfavila-laptop>
>mfw not sure if you're meming
<midfavila-laptop>
emacs isn't an OS.
<chaffity>
I am
phoebos[m] has quit [Ping timeout: 244 seconds]
testuser[m]1 has quit [Ping timeout: 244 seconds]
jstnas has quit [Read error: Connection reset by peer]
rgybmc[m] has quit [Read error: Connection reset by peer]
psydroid has quit [Read error: Connection reset by peer]
konimex has quit [Read error: Connection reset by peer]
E5ten[m] has quit [Read error: Connection reset by peer]
testuser[m] has quit [Read error: Connection reset by peer]
testuser[m] has joined #kisslinux
konimex has joined #kisslinux
psydroid has joined #kisslinux
E5ten[m] has joined #kisslinux
rgybmc[m] has joined #kisslinux
jstnas has joined #kisslinux
testuser[m]1 has joined #kisslinux
phoebos[m] has joined #kisslinux
<micr0>
oh, sls got renamed ssu?
<midfavila-laptop>
yeah, a while ago
<midfavila-laptop>
it tripped me up too
<micr0>
also i dont see it packaged in community...
<micr0>
maybe my community is pointing to the wrong place...
<kernelc_>
what is causing following errors: https://0x0.st/-LEM.txt? I have all packages mentioned in install section installed, including liberation-fonts
<testuser[m]1>
It's harmless
<testuser[m]1>
There is not ${prefix}/ dir
<testuser[m]1>
There's not supposed to be
<testuser[m]1>
Is the server not starting ?
<kernelc_>
Yes :( maybe because of error from first line?
<kernelc_>
oh, sorry for wasting your time, I done `kiss reset` and I forgot about enabling eudev :(
<testuser[m]1>
Lol
<acheam>
kiss rese
<acheam>
t?
<testuser[m]1>
It uninstalls everything
<testuser[m]1>
Except core
<midfavila-laptop>
i don't even install reset
<kernelc_>
"reset Remove all packages except for the base"
<acheam>
oh
<midfavila-laptop>
or most of the extensions, honestly
psydroid has joined #kisslinux
psydroid has quit [Changing host]
<midfavila-laptop>
...that reminds me, has the new dependency resolution code in kiss been upstreamed yet?
<midfavila-laptop>
if so I need to rebase my fork...
<testuser[m]1>
Soon
<testuser[m]1>
There's some bug
<testuser[m]1>
s
<midfavila-laptop>
plural
<midfavila-laptop>
bug
<midfavila-laptop>
s
<midfavila-laptop>
got it
<midfavila-laptop>
if I knew more about graph theory I'd poke at it
<midfavila-laptop>
bleh, emacs still won't compile and climacs doesn't work. this is disappointing
<chaffity>
"i don't even install reset" midfavila-laptop what's the difference between reset and clear, I had no idea reset was a thing
<ang>
mid's talking about kiss-reset
<ang>
the difference between clear and reset is that clear only clears the screen, while reset puts the terminal (back) into a sane state
<ang>
cat a binary file and see how useful your terminal is afterwards
<chaffity>
A la tput --reset? Colours and what not?
<chaffity>
Shucks, just tput reset, I tried
<ang>
no, tty settings and such
<kernelc_>
testuser[m]1: actually I had udevd enabled… and yes, xf86-input-libinput is installed
<illiliti>
midfavila-laptop: graph theory is easy. tricky part was to implement it in shell without pointers/structures/arrays
<illiliti>
also unlike recursive DFS, BFS algo is harder to implement because it requires inline modification of graph, but still possible though
<testuser[m]1>
kernelc_ does it work as root ?
<kernelc_>
I had modified versions of some packages, probably they were cached. I removed local repo from KISS_PATH, and then I done `kiss reset`. Is it possible that after reset modified packages from cache were installed?
<testuser[m]1>
If you do kiss i without kiss b then whatever binary is present in ~/.cacke/kiss/bin is used
<testuser[m]1>
It can be garbage (just needs a valid /var/db/kiss), just the version needs to match
<testuser[m]1>
It can't check if it belongs to the current repo in path
<kernelc_>
I think I done 'kiss b' every time, but I will recompile everything
<testuser[m]1>
Well it can but doesn't
gtms has quit [Remote host closed the connection]
raph_ael has quit [Quit: WeeChat 3.1]
raph_ael has joined #kisslinux
<micr0>
illiliti should i be using your eiwd fork?
<illiliti>
yes
<illiliti>
if you don't mind gcc dep
<kernelc_>
'kiss r' can't remove dwm, interesting
<illiliti>
however, dylan's eiwd has some CVE's afaik
<omanom>
you can manually remove the folder from installed too, if you're sure its ready to be gone
<kernelc_>
manifest file is empty but /usr/bin/dwm binary is presented
<testuser[m]1>
Something messed up yoyr manifest file then
<testuser[m]1>
Kiss just removes everything present in that file
<testuser[m]1>
So if it's empty it eon't do anything
<kernelc_>
maybe bug in 'kiss reset'?
<testuser[m]1>
No its just supposed to call kiss remove
riteo has joined #kisslinux
<riteo>
hiii!
GalaxyNova has joined #kisslinux
GalaxyNova has quit [Read error: Connection reset by peer]
<testuser[m]1>
Hi
<riteo>
2 days ago or so I tried installing KISS linux on a usb drive in order to finish my little project of running the nvidia drivers on it, it was great! Also that efistub thing is very nice, it was way easier to install than grub! It really went well until I tried to use a fstab... I tried using PARTUUID which seems to be supported but to no avail. I tried removing the quotes and putting it in all
<riteo>
lowercase, but the boot sequence always fails telling me that it can't parse it properly... Am I doing something wrong?
<riteo>
extra long message today
<noocsharp>
post your grub config
<riteo>
I didn't use grub
<illiliti>
post logs
<noocsharp>
wow i am bad at reading
<riteo>
does it save them somewhere?
<riteo>
noocsharp: no worries
<omanom>
dmesg might give some info
<riteo>
so I should boot the usb stick, right?
<testuser[m]1>
You don't need an fstab btw if you just want to mount the rootfs
<testuser[m]1>
root=/ whatever should be passed in efistub
<riteo>
testuser[m]1: I know, but I wanted to mount the boot partition too since it's what I plan to do in my actual install when I'll switch
<riteo>
and anyways I want to know what I'm doing wrong since on the web it looks like people done it
<dilyn>
dumpsterfire is a proper description of the work being done here
snakedye has quit [Quit: ]
<micr0>
added hovercats/kiss-dumpsterfire to my repos/repo xD
<acheam>
testuser[m]1: because i'm on my arch laptop right now, using flameshot
<acheam>
within a week or so, it will be running kiss though
riteo has joined #kisslinux
<riteo>
I'm back!
<acheam>
hi
<acheam>
dilyn: how would you feel about a binary chromium package?
<riteo>
ok, so apparently only UUID works, I haven't tried LABEL but I feel like it works too. I'm still curious on why PARTUUID or PARTLABEL don't work
<riteo>
though
<acheam>
what's hovercat's alter ego again?
<riteo>
hovercat?
<testuser[m]1>
sad_plan
<acheam>
ah right thanks
<acheam>
we should have a telnet user directory or something lol
<riteo>
did you accidentally focus your IRC window while editing a file?
<riteo>
that looks like vi style navigation to me
<acheam>
its the navigation of a loser, they over shot by one line and had to go back up
<acheam>
ugh
<acheam>
what a waste of a keypress
mulc has quit [Ping timeout: 252 seconds]
<kiedtl>
?
<kiedtl>
Oh
<kiedtl>
Tried typing before the terminal came up ;(
<kiedtl>
The /10 was something I typed into this window when the internet dropped... weird that it came afterwards the 'jjk'
riteo has quit [Quit: epic messed up /dev moment]
riteo has joined #kisslinux
<riteo>
ok now after some quick scouring through the system files and some manual pages I'm 100% sure now that busybox simply didn't implement nothing more than UUID and LABEL for its block identifiers
<riteo>
that's why fstab didn't support them
<riteo>
dilyn: do you thing that it's something worth noting in the wiki or should we just keep it as a reminder to anyone here encountering a similar problem?
mahmutov has joined #kisslinux
<acheam>
can't find any modern qi/ph nameservers :(
<acheam>
have to use a centos 7 docker container
<acheam>
couldn't get it to compile on debian 10
<micr0>
huh weird, firefox 87 isn't building for me, oh well
<acheam>
build log?
<micr0>
guess im on an old version for a while longer
<omanom>
I never got LABEL to work, so I'm not convinced even that is in there :/
<acheam>
there is a bin in kiss-community
<riteo>
omanom maybe it's because you've changed the name of the GPT partition and not of the filesystem?
<micr0>
i wonder if I should be using git-bruh/kiss-repo instead of the kiss-wayland one from himmalerin...
<testuser[m]1>
It's much more up to date
<testuser[m]1>
Just beware of the wlroots package it's patched for nvidia, you can package it yourself
<micr0>
yeah im not on nvidia so that would be frustrating
<micr0>
guess I just fork it
<micr0>
oh but i also dont want lto
<micr0>
oh wait, LTO is fine, I just didnt want to do PGO
<micr0>
also not a big fan of all the modifications we make removing xpi's and whatnot. i just want as upstream firefox as possible.
<micr0>
guess thats enough reasons to fork
<testuser[m]1>
If you don't want lld and stuff just remove the `--enable-lto=cross` and `--enable-linker=lld`
<dilyn>
micr0: you can also use my repo; master is wayland-only
<dilyn>
acheam: somebody else could always supply a binary of chromium :v it can be in community as chromium-bin
<dilyn>
riteo: I feel like busybox's failure here is documented... somewhere...
<dilyn>
hm perhaps not.
<dilyn>
ah. i'm remembering a conversation I had elsewhere :v
<riteo>
no worries
<riteo>
so this was already discussed before?
<dilyn>
it can be mentioned here i suppose https://k1sslinux.org/wiki/storage/disks#4.0 though it's a fair bit out of the way, it's the only mention of fstab we really have
<dilyn>
I imagine it was discussed in IRC long, long ago, but it's never really come up too often (how many people even use fstabs? I certainly don't...)
<omanom>
>Devices can be referred to either by their /dev pathname, by a label, by UUID, or by Part-UUID.
<omanom>
if this is 100% busybox not implementing Part-UUID then that wiki entry should be updated
<riteo>
oh so it's already there... Kind of
<riteo>
the source there is archlinux's wiki, that's why it says that
<riteo>
the issue is that fstab is loaded from mount, which has different implementations
<riteo>
I wonder if POSIX says something about that
<dilyn>
POSIX probably doesn't mention implementing too many specific ways to refer to devices
<illiliti>
^
<riteo>
I can't even find mount in the posix shell & utilities section
<riteo>
but that makes sense
<dilyn>
also need to clarify another line in that page referring to fdisk; some implementations (toybox) don't support gpt lmfao
<thebuzzing>
Hmm? What happen now?
<dilyn>
but busybox fdisk does iirc
<riteo>
the weird thing is that busybox's lsblk can print PARTUUID and PARTLABEL
<testuser[m]1>
thebuzzing: nothing, a bot just freaked out
<riteo>
lmao
<riteo>
maybe we could also just report that to upstream and/or patch this feature in? It feels something that can and should be there
<illiliti>
riteo: lsblk isn't implemented by busybox, it's util-linux thing
<riteo>
oh
<illiliti>
lsblk: applet not found
<riteo>
sorry, my bad
<thebuzzing>
Oh, right. Back to sleeping then.
<riteo>
well then yeah, we should add a disclaimer about different mount implementations and their supported identifier
<riteo>
s/identifier/identifiers/
<omanom>
acheam just really wanted to say hi thebuzzing
<acheam>
hehe sorry
<thebuzzing>
Hey, I'm always open to saying hi! It's not like I'm being useful otherwise. Hah.
<riteo>
if you scroll more it talks about an android package
<riteo>
ah no ok it's zlib with a funky name
<dilyn>
smh
<riteo>
smh my head indeed
<dilyn>
alsa project pushed their bug fix releases. seem to work fine on my end, let me know if there are any problems :v
<dilyn>
they take a very annoying approach to versioning (:
<omanom>
i'm gonna start versioning my stuff like v0.1-alpha-preblend-dynamo-beta-fixed-final-static-2.5
<omanom>
v1.0-jk-fuck-you-its-0.1.a
<omanom>
perpetual v0.0-0, you have to go by the release date instead
<acheam>
lol
schillingklaus has quit [Quit: schillingklaus]
<riteo>
lmao
GalaxyNova has joined #kisslinux
test8765 has joined #kisslinux
<micr0>
dilyn I don't see firefox on master in dilyn/kiss-me, should I be looking somewhere else?
mulc has joined #kisslinux
<micr0>
dilyn I don't see firefox on master in dilyn/kiss-me, should I be looking somewhere else?
<micr0>
oh sorry for the double spam
mulc has quit [Client Quit]
<testuser[m]1>
He meant general ayyland stuff
<riteo>
ayyland is my new favourite word
<riteo>
I just imagine this land full of aliens saying "ayy lmao"
<riteo>
acheam we have to bring the word of the day back
micr0 has quit [Quit: micr0]
micr0 has joined #kisslinux
<micr0>
anyone packaging podman and other container stuff? I'm sure my repo is out of date and would rather contribute to a community effort if possible
<GalaxyNova>
most complicated thing about it would be the dependency checking
<Sweets>
though I used to be a freelance dev kiedtl
<GalaxyNova>
omanom: wow
<noocsharp>
lmao
<kiedtl>
Sweets: ah, nice
<Sweets>
no, :(
<omanom>
oh no i forgot shebang line dammit, sorry guys
<Sweets>
freelance developing is such a pain in the ass
<GalaxyNova>
omanom: you should get a job at google
<Sweets>
especially when clientelle don't even know what _they_ want
<kiedtl>
Sweets: I mean its nice that your current job isn't computing related
<noocsharp>
omanom: you forgot the dependency on kiss
<Sweets>
true
<kiedtl>
I'll probably refrain from getting a computer-related job myself
<omanom>
references plz
<Sweets>
I hated being a dev
<kiedtl>
Don't want to burnout, lol
<Sweets>
That's exactly why I quit
<kiedtl>
computing as hobby is fun though
<omanom>
noocsharp that's one of those implicit dependencies which are assumed to be on all systems though
<Sweets>
when you have to put food on the table with your hobby, it is immediately no longer a hobby
<GalaxyNova>
I hate implicit dependencies
<GalaxyNova>
no dependencies should be implicit imo
<GalaxyNova>
unless it's for general things that are standards compliant
<GalaxyNova>
omanom
<omanom>
they're implicit from a "your KISS Linux install should have this. if it doesn't, you broke it either on purpose to use an alternative (in which case you theoretically know what you're doing) or you broke it on accident and should get it resolved"
<omanom>
consider core KISS packages "standards compliant" -- they comply to the set of packages that are standard for a KISS Linux install
<riteo>
I actually agree with the "all dependencies must be explicit part"
<GalaxyNova>
KISS doesn't have a system profile
<riteo>
wait I quoted part too
<Sweets>
arbitrary standards are dum
<GalaxyNova>
omanom: No, a KISS install shoudn't be assumed to have any package (idealy)
<GalaxyNova>
of course we still assume git and tar are installed
<dilyn>
i mean if you don't have tar...
<dilyn>
you're doing something magical
<Sweets>
dilynnnn babeeeeyyy
<dilyn>
;)
<riteo>
time to make kiss7z
<omanom>
KISS Linux (core) is essentially a set system. Repos outside of core are not essential KISS Linux
<omanom>
so anything in core can be assumed to exist on a KISS Linux install, otherwise technically it's not KISS Linux
<riteo>
I actually always saw kiss linux as only the package manager really
<riteo>
cause that's it
<GalaxyNova>
grub is in core
<GalaxyNova>
you can't push bootloaders down people's throats
<omanom>
ffs ok pick out an exception to invalidate the concept, sure
<Sweets>
yeah honestly fuck grub being in core
<riteo>
GalaxyNova: I think omanom meant what's by default in the rootfs tarball
<Sweets>
bootloaders shouldn't be in core I don't think
<GalaxyNova>
indeed
<GalaxyNova>
I too believe grub should be moved somewhere else
<Sweets>
there should be like a separate bootloader repo, or like a "boot" repo that includes loaders and inits
<dilyn>
ew
<Sweets>
do most people even use busybox init
<Sweets>
honestly
<riteo>
regarding implicit dependencies it's way simpler than you think guys
<omanom>
grub is the stated default bootloader of KISS Linux, anyways
<dilyn>
i'd wager most people stick with the base tbh
<Sweets>
i never do when i use kiss, but I'm biased so i use hummingbird
<riteo>
dilyn very recently made a very short list of implicit deps
Sweets_ has joined #kisslinux
<Sweets>
wot
<GalaxyNova>
I am confusion
<dilyn>
I mean I'm not evening using KISS lmfao
<Sweets>
I am confusion
<Sweets>
not you
<dilyn>
wyverkiss or die
<Sweets>
im using macos
<Sweets>
like a real trooper
<dilyn>
mvp
<riteo>
wait what's happening
<riteo>
why is everybody confused
<riteo>
you're making me confused too
<Sweets>
Sweets_
<riteo>
what
<riteo>
how
<Sweets>
I think it might just be a ghost socket
<riteo>
how does that happen
<Sweets>
I opened a few connections to the channel because I couldn't connect
<GalaxyNova>
i aggree with riteo that KISS is everything that uses the KISS packaging systemm
<Sweets>
but anyways, @ dilyn
<riteo>
Sweets_: give us a sign if you're listening us
<Sweets>
I think we should have a separate repo for boot sequence programs, since those are very much based on what the user wants
<Sweets>
both bootloader and init
<riteo>
well, as I said, the list is very short
<GalaxyNova>
no
<Sweets>
also technically neither are necessary to boot into kiss
<GalaxyNova>
that would be poitless and it would add confusion
<Sweets>
just saying
<riteo>
git, binutils, gcc, make, musl and busybox is all that's implicit
<riteo>
that's all
<GalaxyNova>
maybe somewhere ine xtra
<GalaxyNova>
extra
<Sweets>
throw back to way back in the day when kiss didn't use busybox init
<Sweets>
fun fact kiss originally shipped with hummingbird
<Sweets>
now we sad
<GalaxyNova>
riteo: wyverkiss doesn't even have binutils or gcc
<GalaxyNova>
so doesn't that break things?
<riteo>
that's why they're implicit I guess
chaffity has quit [Quit: Client closed]
<rio6>
I think the goal of core is to contain everything that needs for a bootable system
<rio6>
so it kinda needs a bootloader
<Sweets>
rio6 yeah but neither a bootloader nor an init are needed for a bootable system
<riteo>
rio6: that's not true
<riteo>
you can use efistub
<omanom>
users who install wyverkiss know that they have a different system, and know that packages built for wyverkiss might need tweaking
<Sweets>
you can use efistub, and an initramfs
<omanom>
it falls under "does the user know what they're doing" in my opinion
<rio6>
not every computer has uefi
<riteo>
right
<Sweets>
you can still use a boot sector
<Sweets>
also uefi != efi
<GalaxyNova>
rio6: you can boot without those packages technically
<riteo>
btw I'm pretty sure that it's in the style guide to prefer $CC over gcc
<rio6>
technically maybe, but realistically?
<Sweets>
anyways, I won't say it's mindless to include _a_ bootloader in core, but it's also contrary to the whole user-choice of kiss
<GalaxyNova>
idk if gcc is called directly in repositories anyway
<riteo>
I don't think it is
<GalaxyNova>
Sweets: definetly should be moved to extra imo
<Sweets>
I agree
<riteo>
oh I agree
<riteo>
grub is definetly extra in 2021
<Sweets>
people are slowly gravitating away from grub
<Sweets>
finally
<rio6>
give it 4 more years then maybe
<Sweets>
grub is very much "legacy" now
<dilyn>
people have been saying that for a very long time
<Sweets>
and people have been right
<omanom>
>The repositories (excluding Community) must remain a useful base containing everything up to a Graphical session with a browser and media player. They shall go no further
<riteo>
Sweets: it was actually harder to configure grub than efistub for me on my test kiss install
<Sweets>
people use it less each year
<GalaxyNova>
grub2 exists
<riteo>
I literally gave up and configured efistub in like nothing
<Sweets>
yeah because grub was made for a different time riteo
<zola>
What is used instead of grub, if grub is legacy?
<Sweets>
back in the day it was simple
<dilyn>
the point of baseinit and grub being in core is that they are 1) sane to include because init is important and a bootloader is valuable, and 2) baseinit is small, 3) grub is *known*
<Sweets>
GalaxyNova we're assuming grub2 when we say just "grub"
<riteo>
GalaxyNova: I think that the "2" was implic there
<riteo>
s/implic/implicit/
<GalaxyNova>
zola: rEFInd is pretty cool
<GalaxyNova>
not exactly KISS but it's cool
<dilyn>
the only time I ever installed grub in the last two years was when we had that bug recently with 2.04. I've never used it with KISS. you don't have to.
<Sweets>
also grub is pointless on u/efi systems
<illiliti>
iirc Dylan stated that grub, busybox init, etc are just defaults. There is no lock-in to use something different
<dilyn>
there's a reason I have my own separate repository I use entirely, rather than just forks and symlinks
<omanom>
the install guide mentions that too
<omanom>
illiliti
<GalaxyNova>
technically git can also be replaced
<dilyn>
we don't need a separate place for them because it already exists: community, and user repositories.
<Sweets>
you literally make an EFI entry that points to grub, which then just starts the kernel. hence you shouldn't even bother with grub on efi,since efi can just execute the kernel image
<dilyn>
you don't need git at all for kiss
<omanom>
it's more a "here's some defaults in case you don't have something in mind already"
<GalaxyNova>
i don't think it would be hard to patch KISS to use rsync or something
<dilyn>
Sweets, you're very correct. grub is useful in only small circumstances, and in the average/most general use case it is just a needless middleman
<rio6>
don't force kiss to be efi only
<micr0>
i thought i was efistub only but for some reasons it boots into grub anyway TT
<riteo>
Sweets: wasn't it like EFI's objective to make bootloaders redundant
<dilyn>
GalaxyNova: not hard at all! cpt uses rsync, fossil, and git
<Sweets>
yes. To an extent.
<Sweets>
Which it very much succeeds in.
<micr0>
i was always partial to fossil, it made sense to throw a wiki and issue tracker in with the code
<micr0>
now if only the code management was as solid as I hope pijul to be
<Sweets>
also, if someone could pass on the message to schilling if/when he gets on again, you could technically use hummingbird for macos, but it would be a bad idea since the macos init is quite good, compared to linux options
<Sweets>
im about to go back to work from my lunch break
<Sweets>
:(
<riteo>
I'm just thinking someone connecting on IRC while at work and that sounds cool af for some reason
<riteo>
not only on IRC, but on #kisslinux
<Sweets>
yeah im cool'
<Sweets>
what of it
<GalaxyNova>
"Nobody is born cool except of course..."
<Sweets>
people who join kisslinux during working hours
<GalaxyNova>
lol
aws has joined #kisslinux
<Sweets>
trying to decide what my next blog post will be on
<GalaxyNova>
that's seriously one of the best WindowsXP rices I've seen
j0hnny has joined #kisslinux
<jedavies>
It's just the xp theme from icewm
<jedavies>
The fan in that thing is loud
claudia has joined #kisslinux
<claudia>
re sticking to base: I use busybox vi :D
<zola>
Busybox vi is great
<claudia>
syntax hilighting is just distraction.
<claudia>
Use Xorg in s/w mode.
Sweets_ has quit [Ping timeout: 272 seconds]
test8765 has quit [Quit: zzz]
<claudia>
jedavies, We share same wallpaper :D
zola has quit [Ping timeout: 244 seconds]
<acheam>
busybox vi is nice, but I need visual mode
<jedavies>
Heh I don't really use the machine like that, was just messing around with the new install. Had enough of windows xp the first time around!
<noocsharp>
jedavies: how's the performance? i have a very poor idea of how risc-v performs
<noocsharp>
acheam: vis
<acheam>
is that the lua one?
<noocsharp>
well lua is optional if you want plugins
<acheam>
I have no need for it anyhow, my setup is busybox vi for quick edits, emacs for code, etc
<jedavies>
Haven't tried building anything on it yet, will try something now
<noocsharp>
cool, will be interesting to find out i think
<dilyn>
the lack of 'cw' in busybox vi really grinds my gears
<dilyn>
I install vim in every chroot I use because of it lmfao
<dilyn>
that and visual mode is also mandatory. Every time I have to use an editor without visual mode I get irrationally angry
mcpcpc-hkp has quit [Ping timeout: 244 seconds]
<GalaxyNova>
busybox vi is still much better than regular vi
<GalaxyNova>
they have backspace
<noocsharp>
dilyn: im telling you, vis is the way
<GalaxyNova>
I personally use Neovim
<GalaxyNova>
it's great
<dilyn>
i'm just too into the five plugins I use with vim
<dilyn>
though I don't leverage vim nearly enough to justify using it
<noocsharp>
i switched to vim and realized that i didn't actually use any of the plugins that i thought i did
<noocsharp>
vis*
<dilyn>
gah it's gonna make me do actual work to install it with netbsd curses huh
<dilyn>
smh
<dilyn>
i've already lost interest
<noocsharp>
tf? i use ncurses with it
<GalaxyNova>
Seriously though Neovim 0.5 is amazing
<noocsharp>
i switched from neovim to vis
<GalaxyNova>
why?
<noocsharp>
turns out i don't actually use any neovim features
<GalaxyNova>
I use the terminal emulator all the time
<noocsharp>
i always forget which combo to press to leave the terminal mode
<GalaxyNova>
lol same
<dilyn>
^ neovim is just too much for me. I used it for a while
<GalaxyNova>
you can map it to any key though
<noocsharp>
ik... but i really only ever opened the terminal emulator for the novelty of it
<GalaxyNova>
regular vim also has a terminal emulator btw
<GalaxyNova>
it's just less well known
<noocsharp>
i like opening my editor in terminal emulators, not my terminal emulators in editors
claudia has quit [Remote host closed the connection]
claudia has joined #kisslinux
<GalaxyNova>
I depends for what you want to use it for
<ang>
busybox vi is quite bad
<ang>
it's undo can corrupt your file
<GalaxyNova>
noocharp: I agree that for config file editing Neovim is overkill, but if you want to use it like an IDE then it's features are really useful
<GalaxyNova>
specifically the LSP integration
<noocsharp>
ive never been an lsp person
gtms has joined #kisslinux
<GalaxyNova>
You don't use any LSP or completion engine?
<GalaxyNova>
it's a crutial part of any editor imo
<noocsharp>
no, in fact i feel like relying on completion is a bad habit
<GalaxyNova>
it saves lots of time
<GalaxyNova>
why would it be a bad habit
<noocsharp>
for me at least, it becomes hard to write code without completion
<GalaxyNova>
that's because it's so useful
<noocsharp>
and knowing the names of things in your code is a good idea
<noocsharp>
i do end up copying and pasting function declarations when it's painful to type it out
<dilyn>
clangd is bae :v
<dilyn>
ale is an heru
<GalaxyNova>
yes clangd is amazing
<noocsharp>
also it causes me mental anguish when my editor doesn't respond immediately, and making editors "smarter" tends to do that
claudia has quit [Read error: Connection reset by peer]
<riteo>
I'm a bit late into the discussion but kakoune gang rise up
claudia has joined #kisslinux
<GalaxyNova>
riteo: why do you need a completely different program to open a terminal when you can just do super+enter
<claudia>
ang, The undo corrupt thing has been improved since last? relase. Happens very rarely now. There has been much work on vi this year it seems.