<dilyn>
it became too cumbersome moving files between my desktop, qemu, and my laptop
<dilyn>
but i'm managing my own kernel and there's no grub so I can dual boot easily :v soon, wayland-only ubuntu. once I have the time
midfavila has left #kisslinux [#kisslinux]
ella-0_ has joined #kisslinux
ella-0 has quit [Ping timeout: 255 seconds]
<noocsharp>
how to do you keep stuff up to date on ubuntu, or do you not
<dilyn>
debian actually has a really large ecosystem for packaging and maintenance
<dilyn>
I mean, a ton of it is legacy cruft or things you wouldn't use to maintain your own system
<dilyn>
apt will fetch sources for packages or build dependencies for you, you can use dpkg-* scripts to automate building things (just the library, just the binary, etc). Modifying builds is just editing a makefile, you can directly push to a PPA pretty easily, you can have launchpad do the package build for you...
<dilyn>
granted it's a LOT to learn so the curve can be quite steep
<noocsharp>
makes sense
<jslick>
I have used junest + manual compile at work, but will probably switch to gentoo-prefix soon. keeps the stuff that I care about up-to-date (such as tmux, neovim, ripgrep)
<testuser[m]>
Hi
illiliti has joined #kisslinux
jslick has quit [Ping timeout: 244 seconds]
jslick has joined #kisslinux
pomekoon has joined #kisslinux
soliwilos has quit [Quit: zzz]
soliwilos has joined #kisslinux
<phoebos>
> 1040 packages
<phoebos>
good going
<phoebos>
is that because everything is split into a -lib, -bin, -dev etc
<dilyn>
that's a joke tho. It's because I've got about five full kernel trees in ~ :v
dilyn has quit [Quit: Connection closed]
<soliwilos>
An alpine system I have for kodi entertainment uses a total of 5.5GB.. It's not setup for full desktop usage, but still, that would not add much I'd guess.
omanom has quit [Remote host closed the connection]
omanom has joined #kisslinux
<omanom>
:/ ipv6 issues, what year is it?!
omanom has quit [Client Quit]
omanom has joined #kisslinux
dilyn has joined #kisslinux
<dilyn>
phoebos: after a small amount of cleaning and moving... /dev/nvme0n1p3 98G 13G 81G 13% /
<dilyn>
not terrible
<dilyn>
and yeah they're full-blown git trees, each with at least three branches
<dilyn>
I've been doing a lot of kernel work lately:)
<phoebos>
cool
<dilyn>
you say cool but I say "I am not a kernel developer"
progenyx has joined #kisslinux
<phoebos>
have you been doing riscv stuff
<dilyn>
I have!
<dilyn>
I got Ubuntu Core to run on a $25 board
<dilyn>
that work is getting presented at embedded world
<phoebos>
that _is_ cool
<phoebos>
what kind of things did you have to do
<dilyn>
well I had to learn all about the boot process for riscv, which is actually quite sane when compared to arm
<dilyn>
had to build u-boot and opensbi, for my board specifically I had to take in some patches from someone elses work, and the kernel I used was a very barebones kernel with ubuntu's patches to get things like e.g. apparmor to work
<dilyn>
it was surprisingly simple, once you learned a bunch of prior art stuff
<omanom>
>actually quite sane when compared to arm -- good to hear!
<omanom>
part of why i stopped trying to get kiss on my rpi is because i didn't feel like dealing with that
<dilyn>
The pi is maybe one of the most opaque bits of hardware...
<dilyn>
Who'd have thought that Western Digital of all companies would drive standardizing the early boot stages of an entire hardware platform! thank you WD for making riscv nice
<testuser[m]>
<dilyn> "it became too cumbersome..." <- What about having uwuntu on external ssd or something and sharing /home on that
<noocsharp>
wtf is happening, a few days ago i talked to a guy in real life who worked on risc-v at wd
<dilyn>
they're pushing the most common implementation of SBI! it's great
<dilyn>
testuser[m]: ew
<dilyn>
I mean I could, but
<dilyn>
i've got oodles of space on this nVME anyways and I needed to do a full disk wipe already
<noocsharp>
yesterday i started trying to get a little bare metal program running on opensbi
<noocsharp>
no success yet
<dilyn>
is it a problem with loading it or the actual execution?
<dilyn>
you should just be able to build opensbi with a payload and Just Twerk
<noocsharp>
i'm pretty sure loading, might be loading things at the wrong address
<dilyn>
probably
<dilyn>
there are three different ways to get to execution and you use them all for different reasons :v
<noocsharp>
since i got it working in qemu virt without opensbi
<dilyn>
are you sure?
<dilyn>
on KISS?
<dilyn>
qemu carries around its own OpenSBI afaik so if you don't specify a BIOS it'll just load its own
<noocsharp>
no, i loaded my bare metal program as the bios
<dilyn>
ah i see i see
<noocsharp>
weird coincidence that you bring this up since i was literally reading about all this stuff yesterday
<noocsharp>
i sent a pr to opensbi since they were using find `-iname` when `-name` would work just fine in their Makefile
<dilyn>
nice!
<noocsharp>
we'll see if it ever actually gets merged
dilyn has quit [Quit: Connection closed]
dilyn has joined #kisslinux
<noocsharp>
what board did you get ubuncu core running on?
<dilyn>
the sipeed lichee rv with the dock
<dilyn>
just a cheap $25 dev board haha
<dilyn>
there's a bigger and better version (the nezha) and my coworker is going to take my work and try to get Core on there
<noocsharp>
did you have to like port any programs, or was it relatively straightforward?
<dilyn>
luckily all of the main components (snapd, core20) are already built for riscv64, so I didn't have to build those myself (though it shouldn't have been hard...)
<dilyn>
building the kernel was tricky just because I wanted to try and get an ubuntu kernel
<dilyn>
there aren't many snaps available as of now tho so anything else I'd want to run I'd have to build myself
dilyn has quit [Client Quit]
dilyn has joined #kisslinux
<dilyn>
sorry for the noise trying to get my mic and speakers working in Ubuntu...
<dilyn>
Everything is so much harder on distros that aren't KISS. God I feel like a boomer
<noocsharp>
noise?
<dilyn>
logging in/out
progenyx has quit [Ping timeout: 240 seconds]
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
rohan has joined #kisslinux
<rohan>
man
<rohan>
just a question
<rohan>
if i use the gentoo kernel with same configs and the linux default kernel in kiss
<rohan>
will be the same performance?
<dilyn>
does the gentoo kernel apply patches to the kernel?
<rohan>
yeah
<illiliti>
those are minor afaik
<rohan>
is because i dont know why John the ripper have less performance with kiss compared to other distros
<dilyn>
what do you mean it has less performance
<rohan>
more time to crack the same filr
<dilyn>
like, 50% longer? or 2%
<rohan>
like 30% i dont remember well
<rohan>
but is a good difference
<rohan>
not like 10 seconds and 11 seconds
<dilyn>
well
<dilyn>
is your CPU running at the same speed in both cases?
<rohan>
i think so
<rohan>
i set the same parameters in gentoo
<dilyn>
sure
<dilyn>
I'm just saying it's possible that your CPU is getting throttled at some point during this process, either from the governor or a pstate or thermal throttler...
<dilyn>
it's hard to know without... watching...
<rohan>
yeah maybe thats it
<dilyn>
you can certainly test if it's *just* how the kernel is configured/patched by doing what you suggested and using the gentoo kernel, but that isn't sufficient because it's possible some other part of gentoo is helping things (for instance, udev might load a certain module which you aren't doing on KISS)
<rohan>
udev maybe a point
<rohan>
i will do some more testing
<illiliti>
no, "udev" should not be a problem if you compiled kernel with builtin modules, which is recommended way for kiss
<dilyn>
I'm saying they didn't do that illiliti:P
<dilyn>
or they possibly enabled two governors that conflict with each other