<cruxbridge>
<pitillo (@pitillo:crux.nu)> r0ni: I’ve hit the lz4 problem on my main desktop…. I finished removing it and rebuilding the system…. A port pick it up and everything got linked to it
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Btw, with the M4 and the crux-rootfs repo, with the dockerize.sh script optimised builds are done in 45 minutes…
crux-arm-bot has joined #crux-arm
<crux-arm-bot>
[ core-arm64/3.8 ]: ninja: update to 1.13.0
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot>
[ core-arm/3.8 ]: ninja: update to 1.13.0
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot>
[ core-arm64/3.8 ]: pkgconf: update to 2.5.0
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot>
[ opt-arm/3.8 ]: nss: update to 3.113
crux-arm-bot has left #crux-arm [#crux-arm]
<r0ni>
i had downloaded docker, logged into my acct, downloaded the crux-arm container but it won't start.
<r0ni>
tbh it been close to 5-6 years since i've even touched docker so maybe i'm doing it wrong lol
<pitillo>
it's easier than that r0ni..... git clone and check tools/dockerize.sh
<r0ni>
clone the repo on macos, and then run dockerize script?
<pitillo>
as root: tools/dockerize.sh bootstrap
<pitillo>
yes, that's enought if you have docker/podman installed
<r0ni>
huh ok, i'll check it out then
<pitillo>
check variables if you want to build an optimized release and pass them to the script
<r0ni>
yeah the goal is opt rpi5 rootfs so i can see if the repo actually works lmao (I've never tested it on crux)
<r0ni>
i know the kernel and such is good, i build it on slackware, but I need to know if the pieces fit
<pitillo>
so you want to add a new colection to the device optimized device (raspberrypi5.mk)?
<r0ni>
oh no, it already exists
<r0ni>
I maintain it lol
<pitillo>
no no, you mantaine the overlay....
<r0ni>
yeah thats what I mean heh
<pitillo>
I mean, do you want that overlay to be built with crux-rootfs?
<r0ni>
oh yeah
<r0ni>
i know i'll have to change some things in the dockerize to build properly
<r0ni>
i'm pretty confident the system works, but I still want to make sure there's no gotchas
<pitillo>
so if you want to do that (it isn't implemented, so you'll need to touch) you need to check raspberrypi5.mk file and check defined collections there (you will see only core-arm64, core and the device overlay).
<pitillo>
the dockerize script just calls to the Makefile, so probably you will need to touch the logic to add a full opt collection build (or blacklist ports from that collection....)
<pitillo>
and that doesn't sound like an easy task
<pitillo>
why not building directly a rootfs/container and then inside it, build all opt ports?
<r0ni>
oh no sorry when I said "opt" I meant optimized
<r0ni>
no yeah i just want to build core, with the rpi5 overlay
<r0ni>
optimized for rpi5 heh
<r0ni>
i just have to call DEVICE_OPTIMIZATION with the script I assume
<beerman>
yea
<r0ni>
i need to install irc on the m4, having one sole device with irc kinda irks me
<r0ni>
using xcode and all the damn app signing really really annoys me, hate hate hate toward apple for this stuff
<pitillo>
don't you have another linux computer to ssh in and use an irc client there? I have screen hanging with irssi on the "server"
<cruxbridge>
<jaeger (@jaeger:crux.nu)> You could also try asahi on the mac, I guess :)
crux-arm-bot has joined #crux-arm
<crux-arm-bot>
[ opt-arm/3.8 ]: tevent: update to 0.17.0
crux-arm-bot has left #crux-arm [#crux-arm]
<r0ni>
ok, so I looked at the dockerize script and reading the repo says i need to run it in the container... but the container won't start on macos... not sure what up with that
<pitillo>
probably it's wrong explained
<pitillo>
running the dockerize script from outside the container will handle the build process inside the container
<pitillo>
the dockerize script is used to create a container and throw inside it the make bootstrap (or whatever option you pass to it)
<r0ni>
jbl$ sudo ./dockerize.sh
<r0ni>
./dockerize.sh: line 59: $1: unbound variable
<r0ni>
those vars are debug and shell
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Ummm you need to specify a stage to build
<cruxbridge>
<pitillo (@pitillo:crux.nu)> That probably can be improved
<r0ni>
so then bootstrap I assume
<r0ni>
ooh i have action
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Bootstrap will make a full build, but if you want to debug or test, you can go ahead setup by step (by stages)
<r0ni>
gotcha so like stage0 stage1 etc
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Yes, “dockerize.sh bootstrap” will call make bootstrap inside the container
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Yeah
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Remember to pass the variable for the optimisation
<r0ni>
yeah i set it in the file first
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Ah, it should work passing the variable instead of overwriting it, but it’s fine too
<cruxbridge>
<pitillo (@pitillo:crux.nu)> This morning the CI pipe finished right building a bootstrap
<r0ni>
yeah, i just figured I'd change it so i could "guarantee" what I'd get lol
<cruxbridge>
<pitillo (@pitillo:crux.nu)> XD
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Hope it works as expected and as always, any feedback, comment, patch or whatever is welcome
<r0ni>
for sure, once i'm a a little more familiar here I'll check out some more things with it
<r0ni>
see where this goes for now, this is only the beginning I assume ;)
<cruxbridge>
<pitillo (@pitillo:crux.nu)> I have the feeling that this could be a very nice base for experiments xD
<r0ni>
i sure hope so, lxc has proven tempermental lately so i hope this fares better
<cruxbridge>
<pitillo (@pitillo:crux.nu)> It’s working right for X86_64, ARM and RiscV…. So I hope it works for you too and that it can indeed be a good basis for a good start
<cruxbridge>
<pitillo (@pitillo:crux.nu)> I’m using LXC on armhf and it works like a charm too
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Two LXC containers to keep up to date 3.7 and 3.8 on the odroidxu4
<r0ni>
lxc works, just something wrong with cgroups in my kernel or something that causing me greif with things
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Have you checked out the readme file on the port? That helped me a lot
<r0ni>
i build kernel with gentoo patches on arm64 usually, it been wonky lately on 6.12
<r0ni>
i'll have to look it over, maybe things have changed as of late
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Ummm no idea about rpi5 current development
<r0ni>
oh no, i mean for my arm64 VMs, i use standard build with added gentoo patchset, but something seems off with it, i may need to use a diff config
<r0ni>
i stole config from gentoo arm64 iso system
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Ummmmm
<cruxbridge>
<pitillo (@pitillo:crux.nu)> I’ve never touched a kernel for VM, that could be interesting
<r0ni>
wowrks great in vmware normally, but 6.12 has been weird
<cruxbridge>
<pitillo (@pitillo:crux.nu)> May be trying 6.15 ?
<cruxbridge>
<pitillo (@pitillo:crux.nu)> So many patches
<r0ni>
thats just their "base" patchset applied to all arches
<r0ni>
i figure it can't hurt lol
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Are they strictly needed? I mean, have you tried a base test of 6.15 without all those patches?
<cruxbridge>
<pitillo (@pitillo:crux.nu)> With your current config, make oldconfig, setup new stuff as default, and make to give it a try
<r0ni>
no, they aren't strictly needed, it builds and runs without them with just the right config
<r0ni>
i figure if gentoo is patching the kernel on a source based distro... it may be wise to follow suit on another source based distro heh
<cruxbridge>
<pitillo (@pitillo:crux.nu)> I’d probably give a try to last mainline stable version without all that stuff…. Then if something is wrong or not working as expected, I’d try to look for a patch…. But starting with that is a bit messy for me
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Yeah, I see the point, but it’s another distro, not CRUX, and probably checking those patches to see what they do, how they could affect CRUX, could be the best way to go ahead, but it’s just my opinion
<r0ni>
yeah I'll have to try it later after this rootfs builds, maybe things better without
<beerman>
wrt irc client: use a matrix bridge and call it a day :p
<r0ni>
i had an issue for weeks with elogind but only on crux-arm, not on intel and i couldn't figure out what was diff in my systems... turned out being a typo in a pam config causing my issue sooo... i'm def prone to errors heh
<beerman>
r0ni: how was lxc tempramentful for you?
<beerman>
oops for the typo, that sucks, but you found it, which is great
<r0ni>
i didn't even think about matrix, couldve used that in my browser
<r0ni>
beerman: it been fine, but something with the cgroups is failing now upon boot, never had issues on 3.7 or other installs, just this one (maybe another typo ;)
<beerman>
v2 is the way to go imo. Also lxc never threw a tantrum here, its rock solid in that regard :)
<r0ni>
I need to give it a deeper look, I've just been avoiding it heh
<r0ni>
works fine on 3.7 install
<r0ni>
hrm searching my kernel config 2 out of 4 of those cgroup kernel options are missing, so I may need to do some work there
<beerman>
if you go the pam way, it might be another pam config error
<beerman>
these are easy to come by, which certainly makes room for valid criticism ;) the config errors
<beerman>
and missing options are a good pointer also :P but still, do the v2 way, and stop worrying
<beerman>
as long as you dont have legacy software needed v1 stuff you should be fine, both docker and lxc
<beerman>
s/needed/needing/
<cruxbridge>
<pitillo (@pitillo:crux.nu)> But check kernel support, it must be satisfied (at least for what I have tested)
<r0ni>
yeah nothing i use needs v1 so I'll have to go ahead and make sure v2 is good
<beerman>
if you find that readme.md useful, I might need to replace the current lxc readme with it. But I suspect most people don't really notice those anyway
<cruxbridge>
<pitillo (@pitillo:crux.nu)> I vote for it xD
<beerman>
ofc xD it was made literally for you xD
<r0ni>
I do check for readmes with some software, guess it just depends on how familiar i am with it, but I think they are useful
<r0ni>
theres always things that may have a crux-specific quirk
<r0ni>
guess i can remove this other container, this one seems to be trucking along and should be done soon
<r0ni>
started 48 mins ago... gotta be close to the end
<r0ni>
it's building gcc tho, and this being a mbair, may be slower with the passive cooling
<beerman>
i am not sure what pitillo meant when he said 50 minutes earlier :P I am sure he forgot that the runner uses cache and does not need to redownload distfiles. It's closer to 2h, I'm sorry to say :p
<r0ni>
oh man hahaha
<r0ni>
thats alright, it can take as long as it needs lol
<r0ni>
it's already hot in here, its rare to feel this laptop heat up tho, so I know it's putting in the work
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Yeah, around 50min by stage, my bad xD
<cruxbridge>
<pitillo (@pitillo:crux.nu)> In beerman’s case it will depend on download sources speed if they aren’t cached 😂
<beerman>
i can't help it, sourceware is really slow for me :/
<beerman>
r0ni: should be there about now, how's it looking?
<r0ni>
still cookin
<r0ni>
gcc (again?!)
<beerman>
again, two stages, and thats cheap
<beerman>
:P
<r0ni>
ahh heh, it sure is warm tho heh
<r0ni>
176 F cpu
<r0ni>
thats toasty lol
<r0ni>
sorry for my USA
<beerman>
thats 80 degrees in freedom units ;p
<beerman>
sorry for my european
<beerman>
scnr
<r0ni>
i could cook eggs on the bottom i bet heh
<beerman>
i wanted to joke to grill on it earlier, might as well
<r0ni>
there is some hacks for cooling it better but i'm lazy, need to get one of those bottom things
<r0ni>
maybe some medical ice packs would help lol
<beerman>
stuff it in the freezer :D
<r0ni>
not going to lie, I've done that many times with my intel one
<beerman>
heh, how is the WAF about that?
<r0ni>
heh come again? whats WAF?
<beerman>
wife acceptance factor :D
<r0ni>
omg hah she don't ask questions, always assumes I'm hacking the gov or something when i'm "nerding it up"
<r0ni>
but i wait until shes asleep before placing laptops in the coolers lol
<beerman>
😂👍️
<r0ni>
I limit vmware to like 8 cores and 16gb ram so it don't get this toasy using VMs, this is def the bottest its been
<r0ni>
should be done soon tho, i's think
<beerman>
nice :)
<beerman>
reminds me that I wanted to try the bootstrap for 3.7 with a 3.6 builder image.
<cruxbridge>
<jloc0> The rpi5 rootfs did build successfully but we keep having rolling power outages so I figure I’ll leave it for later. I need to find an usb drive to test it with later yet but rootfs was success